compiled Terminal 0.4.8 under redhat 5 update 7 with the rest of the xfce 4.8 source packages. Terminal runs fine for weeks or even months at a time until something happens on the system (not sure what yet) and all the Terminal windows of a certain user will completely hang and become unresponsive. If we use another solution like mrxvt the users aren't affected. Here is a run down 1) if I run an ltrace on the Terminal process in question here is the output (over and over): g_object_unref(0x2f5a0a0, 0, 0x40ae88, 0, 0x2f638d8) = 1 g_object_unref(0x2f5a0a0, 0, 0x40ae88, 0, 0x2f638d8) = 1 2) I can minimize and maximize but the main window, including scrolling just doesn't work any more at all.. I can still see the last entered text in the window, but it will not refresh at all. 3) process in question is running without any special args: altee 8817 1 0 Jan24 ? 00:18:30 /opt/xfce-4.8.0/bin/Terminal 4) we think there might be a slight interruption to the NFS filer where the user's home resides.. we're hoping terminal can cope with a brief outage??? 5) strace output which might be valuable to determine the problem: [pid 8817] ioctl(4, FIONREAD, [32]) = 0 [pid 8817] read(4, "\6\0\36\206a\215\257\2415\0\0\0{\242\245\1\0\0\0\0\22\3\341\0\371\1b\0 \0\1\0", 32) = 32 [pid 8817] write(2, "\n(Terminal:8817): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed\n", 114) = 114 [pid 8817] ioctl(4, FIONREAD, [0]) = 0 [pid 8817] poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=3, events=POLLIN}, {fd=123, events=POLLIN}, {fd=84, events=POLLIN}, {fd=183, events=POLLIN}, {fd=126, events=POLLIN}, {fd=208, events=POLLIN}, {fd=48, events=POLLIN}, {fd=63, events=POLLIN}, {fd=29, events=POLLIN}, {fd=135, events=POLLIN}, {fd=55, events=POLLIN}, {fd=53, events=POLLIN}, {fd=23, events=POLLIN}, {fd=56, events=POLLIN}, {fd=192, events=POLLIN}, {fd=24, events=POLLIN}, {fd=15, events=POLLIN}, {fd=94, events=POLLIN}, {fd=66, events=POLLIN}, {fd=19, events=POLLIN}, {fd=108, events=POLLIN}, {fd=87, events=POLLIN}, {fd=92, events=POLLIN}, {fd=189, events=POLLIN}, {fd=168, events=POLLIN}, {fd=12, events=POLLIN}, {fd=8, events=POLLIN}, {fd=99, events=POLLIN}, {fd=59, events=POLLIN}, {fd=41, events=POLLIN}, {fd=186, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=30, events=POLLIN}, {fd=37, events=POLLIN}, {fd=113, events=POLLIN}], 39, 499) = 0 (Timeout) [pid 8817] ioctl(4, FIONREAD, [0]) = 0 [pid 8817] poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=3, events=POLLIN}, {fd=123, events=POLLIN}, {fd=84, events=POLLIN}, {fd=183, events=POLLIN}, {fd=126, events=POLLIN}, {fd=208, events=POLLIN}, {fd=48, events=POLLIN}, {fd=63, events=POLLIN}, {fd=29, events=POLLIN}, {fd=135, events=POLLIN}, {fd=55, events=POLLIN}, {fd=53, events=POLLIN}, {fd=23, events=POLLIN}, {fd=56, events=POLLIN}, {fd=192, events=POLLIN}, {fd=24, events=POLLIN}, {fd=15, events=POLLIN}, {fd=94, events=POLLIN}, {fd=66, events=POLLIN}, {fd=19, events=POLLIN}, {fd=108, events=POLLIN}, {fd=87, events=POLLIN}, {fd=92, events=POLLIN}, {fd=189, events=POLLIN}, {fd=168, events=POLLIN}, {fd=12, events=POLLIN}, {fd=8, events=POLLIN}, {fd=99, events=POLLIN}, {fd=59, events=POLLIN}, {fd=41, events=POLLIN}, {fd=186, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=30, events=POLLIN}, {fd=37, events=POLLIN}, {fd=113, events=POLLIN}], 39, 1) = 0 (Timeout) [pid 8817] ioctl(4, FIONREAD, [0]) = 0 [pid 8817] poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=3, events=POLLIN}, {fd=123, events=POLLIN}], 5, 0) = 0 (Timeout) [pid 8817] write(4, "(\2\4\0{\242\245\0015\0\0\0\0\0\0\0", 16) = 16 [pid 8817] read(4, 0x7fff29138c40, 32) = -1 EAGAIN (Resource temporarily unavailable) [pid 8817] poll([{fd=4, events=POLLIN}], 1, -1) = 1 ([{fd=4, revents=POLLIN}]) [pid 8817] read(4, "\1\1\37\206\0\0\0\0Z\v\310\0\31\1\177\0\0\0\0\0&\0\0\0\260(\5\32\0\0\0\0", 32) = 32 [pid 8817] ioctl(4, FIONREAD, [0]) = 0 I can keep the open Terminal process that is currently acting up running for a bit longer, but please get back to me as soon as you can... please let me know if there is any other data I can collect for you. Would there be any way to fix existing Terminals with this bug? Can we work on a patch to avoid this bug? thanks, Mike Ciccarelli
Just wondering if anyone looked at this one yet or has a chance to look at this request? thanks, Mike
No idea, seem like a vte issue tho. People try with the vte app or gnome-terminal first.
Does this bug still occur? Absent further feedback, this bug will be closed on the next housekeeping run...
No response, closing.