gnome-theme-manager hangs, stops updating UI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtk-qt-engine (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I've just dist-upgraded from dapper to edgy. If I log in and run gnome-theme-
gdb backtrace:
0xb78fad67 in g_main_
(gdb) bt
#0 0xb78fad67 in g_main_
#1 0xb78fb4a5 in g_main_
#2 0xb78fbb89 in g_main_loop_run () from /usr/lib/
#3 0xb7c5d574 in gtk_main () from /usr/lib/
#4 0x08052384 in main ()
(gdb) thr
[Current thread is 1 (Thread -1225488720 (LWP 5618))]
strace shows it looping in:
5678 read(5, "", 1024) = 0
5678 ioctl(3, FIONREAD, [0]) = 0
5678 gettimeofday(
5678 poll([{fd=6, events=POLLIN}, {fd=3, events=POLLIN}, {fd=10, events=POLLIN|PO
LLPRI}, {fd=13, events=
ents=POLLIN|
ts=POLLIN|POLLPRI}, {fd=5, events=POLLIN, revents=POLLHUP}], 10, 0) = 1
5678 read(5, "", 1024) = 0
5678 ioctl(3, FIONREAD, [0]) = 0
5678 gettimeofday(
5678 poll([{fd=6, events=POLLIN}, {fd=3, events=POLLIN}, {fd=10, events=POLLIN|PO
LLPRI}, {fd=13, events=
ents=POLLIN|
ts=POLLIN|POLLPRI}, {fd=5, events=POLLIN, revents=POLLHUP}], 10, 0) = 1
5678 read(5, "", 1024) = 0
5678 ioctl(3, FIONREAD, [0]) = 0
....[etc]
Looking at the strace, it appears the loop is ignoring an EOF from a subprocess it had forked earlier. That subprocess has died with a SEGV. I'll attach the trace.
Changed in gtk-qt-engine: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
here's the strace. search for SEGV around line 15010.