crash to iconcache code when using gtk-qt theme

Bug #67086 reported by Lubos Kolouch
4
Affects Status Importance Assigned to Milestone
GTK+
Unknown
Critical
gtk-qt-engine (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

When logging in to gnome (latest edgy) nautilus keeps starting and immediately crashing.
(endless loop)

therefore it is not possible to use gnome at all

strace ends with :

stat64("/home/kolcon", {st_mode=S_IFDIR|0755, st_size=16384, ...}) = 0
uname({sys="Linux", node="nbwork", ...}) = 0
gettimeofday({1161334830, 971938}, NULL) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
write(3, "\1\30\r\0\27\0\200\2]\0\0\0\0\0\0\0\0\5 \3\0\0\1\0#\0\0"..., 684) = 684
write(3, " \30\2\0\0\0\0\0", 8) = 8
write(3, "%\30\1\0+\0\1\0", 8) = 8
read(3, "\34\263\213\0\27\0\200\2\360\0\0\0\t8\363d\0007\363dX`"..., 32) = 32
read(3, "\34\263\214\0\27\0\200\2\'\0\0\0\t8\363d\0008\363dX`N\10"..., 32) = 32
read(3, "\34\263\215\0\27\0\200\2\357\0\0\0\t8\363d\0008\363dX`"..., 32) = 32
read(3, "\34\263\216\0\27\0\200\2%\0\0\0\t8\363d\0008\363dX`N\10"..., 32) = 32
read(3, "\34\263\217\0\27\0\200\2C\0\0\0\t8\363d\0008\363dX`N\10"..., 32) = 32
read(3, "\34\263\220\0\27\0\200\2\353\0\0\0\t8\363d\0008\363dX`"..., 32) = 32
read(3, "\34\263\224\0\27\0\200\2(\0\0\0\t8\363d\0\0\0\0X`N\10\t"..., 32) = 32
read(3, "\34\263\225\0\27\0\200\2$\0\0\0\t8\363d\0008\363dX`N\10"..., 32) = 32
read(3, "\34\263\226\0\27\0\200\2\352\0\0\0\t8\363d\0008\363dX`"..., 32) = 32
read(3, "\34\263\227\0\27\0\200\2\361\0\0\0\t8\363d\0008\363dX`"..., 32) = 32
read(3, "\34\263\230\0\27\0\200\2\350\0\0\0\t8\363d\0008\363dX`"..., 32) = 32
read(3, "\34\263\232\0\27\0\200\2\371\0\0\0\t8\363d\0008\363d\330"..., 32) = 32
read(3, "\34\263\235\0\27\0\200\2\372\0\0\0\t8\363d\0008\363d\240"..., 32) = 32
read(3, "\1\2\241\0\0\0\0\0[\0 \2\0\0\0\0\0\0\0\0\4\0\0\0<\25\34"..., 32) = 32
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xb6d876f8) = 9381
waitpid(9381, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 9381
--- SIGCHLD (Child exited) @ 0 (0) ---
exit_group(1) = ?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Could you install nautilus-dbg and get a backtrace of the crash:
- gnome-session-remove nautilus
- gdb nautilus
(gdb) run
... crash
(gdb) thread apply all bt

Changed in nautilus:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Lubos Kolouch (lubos-kolouch) wrote :
Download full text (3.6 KiB)

$ gdb nautilus
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1226537296 (LWP 10371)]
[New Thread -1288483936 (LWP 10378)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226537296 (LWP 10371)]
0xb74466a8 in strcmp () from /lib/tls/i686/cmov/libc.so.6
(gdb) thread apply all bt

Thread 2 (Thread -1288483936 (LWP 10378)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb76d7a8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7307113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3 0x082cf8e0 in ?? ()
#4 0x08196480 in ?? ()
#5 0xb33343b8 in ?? ()
#6 0xb7307265 in ?? () from /usr/lib/libgthread-2.0.so.0
#7 0x082cf8e0 in ?? ()
#8 0x00000000 in ?? ()

Thread 1 (Thread -1226537296 (LWP 10371)):
#0 0xb74466a8 in strcmp () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7b70ff9 in _gtk_icon_cache_has_icon () from /usr/lib/libgtk-x11-2.0.so.0
#2 0xb7b712a1 in _gtk_icon_cache_add_icons ()
   from /usr/lib/libgtk-x11-2.0.so.0
#3 0xb7b71537 in _gtk_icon_cache_get_icon_flags ()
   from /usr/lib/libgtk-x11-2.0.so.0
#4 0xb7b76bf3 in gtk_icon_info_get_type () from /usr/lib/libgtk-x11-2.0.so.0
#5 0xb7b77adf in gtk_icon_theme_get_icon_sizes ()
   from /usr/lib/libgtk-x11-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#6 0xb7ccf538 in gtk_window_get_default_icon_list ()
   from /usr/lib/libgtk-x11-2.0.so.0
#7 0xb7ccfb62 in gtk_window_get_default_icon_list ()
   from /usr/lib/libgtk-x11-2.0.so.0
#8 0xb7cd79fc in gtk_window_new () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x0809b256 in nautilus_window_realize (widget=0x81f0010)
    at nautilus-window.c:741
#10 0x08071ecf in realize (widget=0x81f0010) at nautilus-desktop-window.c:224
#11 0xb76fcb29 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#12 0xb76edfb9 in g_value_set_boxed () from /usr/lib/libgobject-2.0.so.0
#13 0xb76ef79b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#14 0xb770002a in g_signal_chain_from_overridden ()
   from /usr/lib/libgobject-2.0.so.0
#15 0xb77010b7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#16 0xb7701279 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#17 0xb7cc848a in gtk_widget_realize () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x0806a91c in nautilus_application_open_desktop (application=0x81afa90)
    at nautilus-application.c:788
#19 0xb774dcd0 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#20 0x08067889 in Nautilus_Shell_start_desktop (_obj=0x81d7608, ev=0xbf9911f4)
    at nautilus-shell-interface-stubs.c:144
#21 0x0806b418 in nautilus_application_startup (application=0x81afa90,
---Type <return> to continue, or ...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the backtrace. That looks like an issue to GTK, could you install libc6-dbg libgtk2.0-0-dbg and get a backtrace this way?
- gnome-session-remove nautilus
- LD_LIBRARY_PATH=/usr/lib/debug gdb nautilus
(gdb) run
... get the crash
(gdb) thread apply all bt

Revision history for this message
Lubos Kolouch (lubos-kolouch) wrote :
Download full text (4.3 KiB)

Hi, thanks for taking care for this bug.

Here is the trace you requested :

$ LD_LIBRARY_PATH=/usr/lib/debug gdb nautilus
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/usr/lib/debug/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1226987856 (LWP 6458)]
[New Thread -1288918096 (LWP 6469)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226987856 (LWP 6458)]
*__GI_strcmp (p1=0x1d287f6d <Address 0x1d287f6d out of bounds>,
    p2=0x823dc10 "8x8/emblems") at strcmp.c:38
38 strcmp.c: No such file or directory.
        in strcmp.c
(gdb) thread apply all bt

Thread 2 (Thread -1288918096 (LWP 6469)):
#0 0xb7650602 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /usr/lib/debug/libpthread.so.0
#1 0xb7296113 in ?? () from /usr/lib/libgthread-2.0.so.0
#2 0x082cf9d8 in ?? ()
#3 0x08196480 in ?? ()
#4 0xb32ca3b8 in ?? ()
#5 0xb7296265 in ?? () from /usr/lib/libgthread-2.0.so.0
#6 0x082cf9d8 in ?? ()
#7 0x00000000 in ?? ()

Thread 1 (Thread -1226987856 (LWP 6458)):
#0 *__GI_strcmp (p1=0x1d287f6d <Address 0x1d287f6d out of bounds>,
    p2=0x823dc10 "8x8/emblems") at strcmp.c:38
#1 0xb7aeaff9 in get_directory_index (cache=<value optimized out>,
    directory=0x823dc10 "8x8/emblems") at gtkiconcache.c:181
#2 0xb7aeb2a1 in find_image_offset (cache=0x823dbd0,
    icon_name=0x819eeb0 "gnome-fs-directory",
    directory=0x823dc10 "8x8/emblems") at gtkiconcache.c:246
#3 0xb7aeb537 in _gtk_icon_cache_get_icon_flags (cache=0x823dbd0,
    icon_name=0x819eeb0 "gnome-fs-directory",
    directory=0x823dc10 "8x8/emblems") at gtkiconcache.c:267
---Type <return> to continue, or q <return> to quit---
#4 0xb7af0bf3 in theme_dir_get_icon_suffix (dir=<value optimized out>,
    icon_name=0x823dc10 "8x8/emblems", has_icon_file=0x0)
    at gtkicontheme.c:1847
#5 0xb7af1adf in IA__gtk_icon_theme_get_icon_sizes (icon_theme=0x8191588,
    icon_name=0x819eeb0 "gnome-fs-directory") at gtkicontheme.c:1499
#6 0xb7c49538 in icon_list_from_theme (widget=<value optimized out>,
    name=0x819eeb0 "gnome-fs-directory") at gtkwindow.c:2767
#7 0xb7c49b62 in gtk_window_realize_icon (window=0x81f0010)
    at gtkwindow.c:2851
#8 0xb7c519fc in gtk_window_realize (widget=0x81f0010) at gtkwindow.c:4384
#9 0x0809b256 in nautilus_window_realize (widget=0x81f0010)
    at nautilus-window.c:741
#10 0x08071ecf in realize (widget=0x81f0010) at nautilus-desktop-window.c:224
#11 0xb7676b29 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#12 0xb7667fb9 in g_value_set_boxed () from /usr/lib/libgobject-2.0.so.0
#13 0xb766979b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#14 0xb767a02a in g_signal_chain_from_overridden ()
   from /usr/lib/libgobject-2.0.so.0
#15 0...

Read more...

Revision history for this message
Lubos Kolouch (lubos-kolouch) wrote :

I believe we can close this bug as it seems to be duplicate of 36256

At least I could solve it like how they say

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you give details of your previous comment? you were using the gtk-qt theme when having the issue? what did you do to fix it?

Revision history for this message
Lubos Kolouch (lubos-kolouch) wrote :

Yes, I was using it. Actually the problems started about the time I installed KDE to test it.

I did the following to fix it:

1) created new user
2) logged in to gnome with this user
3) gnome crashed
4) remove the gtk-qt theme as described in the other bug (actually removed whole kde
by apt-get remove kdelibs)
5) deleted all gnome folders (.gnome, .gconf, ...) - simply all that were created after 2)
6) logged in to gnome again
7) gnome started OK

I do not remember exactly if I changed the default theme in KDE, it is quite possible

Hope it helps.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the informations, the backtrace seems to indicate a GTK bug anyway, I've forwarded it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=365128. The bug might be triggered by the icon theme, do you remember which one you were using when having the issue? Maybe it's still installed? What themes do you have to /usr/share/icons and .icons? Did you change it or install some theme before getting the crash?

Changed in nautilus:
importance: Undecided → Medium
status: Needs Info → Confirmed
Changed in gtk:
status: Unknown → Unconfirmed
Revision history for this message
Lubos Kolouch (lubos-kolouch) wrote :

I did not change the KDE theme when I tried it... maybe I changed an icon or something...
my /usr/share/icons :

16x16 Industrial
32x32 kdeclassic
48x48 kids
Amaranth kubuntu
application-default-icon.png LargePrint
Cedega.xpm locolor
Crux Locolor
crystalsvg LowContrast
default LowContrastLargePrint
default.kde Lush
gnome Mist
gnomedev Nuvola
Gorilla redglass
handhelds slick
hicolor SphereCrystal
HighContrast sun-java5.png
HighContrastInverse sun-java5.xpm
HighContrastLargePrint Tangerine
HighContrastLargePrintInverse Tango
HighContrast-SVG Wasp
Human whiteglass
ikons

there is nothing in my .icons

Revision history for this message
Sebastien Bacher (seb128) wrote :

maybe that's something kubuntu specific, let we know if you have the issue again

Changed in gtk:
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

comment from upstream: "Sounds like a bug in the gtk-qt theme then.", reassigning

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Still an issue in Intrepid?

Changed in gtk-qt-engine:
assignee: desktop-bugs → nobody
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gtk-qt-engine:
status: Incomplete → Invalid
Changed in gtk:
importance: Unknown → Critical
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.