6631419 gtk-update-icon-cache dies on first boot after install/upgrade
Workaround:
run the following commands as root:
---8<---
for d in /usr/share/icons/*; do
[ -d $d ] &&
gtk-update-icon-cache --force $d;
done
---8<---
Laca
On Thu, 2008-03-13 at 12:40 -0700, Artem Kachitchkine wrote:
> Fresh installed build 85 in a VMware virtual machine. I am unable to log
> into GNOME.
>
> On the first attempt, I was spammed with a number of applet crash/bug
> buddy popups (Volume Control, Panel application, Open folder). After
> killing the session and running gnome-cleanup, all subsequent attempts
> to log in result in the session crashing and returning me to the login
> screen. A core file is left in the home directory:
>
> -bash-3.2$ mdb core
> Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
> > ::status
> debugging core file of gnome-session (32-bit) from aknv85
> file: /usr/bin/gnome-session
> initial argv: /usr/bin/gnome-session
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault)
> > $c
> libc.so.1`strcmp+0x15f(c91fffff, 81e4998)
> libgtk-x11-2.0.so.0.1200.3`get_directory_index+0xc8(81e4b78, 81e4998)
> libgtk-x11-2.0.so.0.1200.3`find_image_offset+0x14e(81e4b78, 80e1948,
> 81e4998)
> libgtk-x11-2.0.so.0.1200.3`_gtk_icon_cache_get_icon_flags+0x22(81e4b78,
> 80e1948
> , 81e4998)
> libgtk-x11-2.0.so.0.1200.3`theme_dir_get_icon_suffix+0x29(80d9410,
> 80e1948, 0)
> libgtk-x11-2.0.so.0.1200.3`theme_lookup_icon+0x1a8(80e03c8, 80e1948, 30,
> 1, 4)
> libgtk-x11-2.0.so.0.1200.3`choose_icon+0xaa(809c058, 8046f74, 30, 4)
> libgtk-x11-2.0.so.0.1200.3`gtk_icon_theme_lookup_icon+0x14b(809c058,
> 80e1948, 30
> , 4)
> libgtk-x11-2.0.so.0.1200.3`gtk_icon_theme_load_icon+0xa0(809c058,
> 80e1948, 30, 0
> , 0)
> get_splash_icon+0x90(80c5808, 806e1bc)
> splash_widget_add_icon+0x80(80c5808, 8257108)
> splash_update+0x4c(8257108)
> run_command_prop+0x10c(80bad50, 806c3c4, 80bab08)
> run_command+0x24(80bad50, 806c3c4)
> start_client+0x3f(80bad50)
> update_save_state+0x87(0, 8254120, ccdd8000, d12abb63, d1399910, 8254120)
> register_client+0x284(8254120, 8254798, 0)
> libSM.so.6`_SmsProcessMessage+0x14b7(8253dd0, 8254120, 1, 1, 0)
> libICE.so.6`IceProcessMessages+0x15f(8253dd0, 0, 0)
> libgnomeui-2.so.0.2000.1`process_ice_messages+0x22(8253e48, 1, 8253dd0)
> libglib-2.0.so.0.1400.4`g_io_unix_dispatch+0x3b(8253e90, cd34814c, 8253dd0)
> libglib-2.0.so.0.1400.4`g_main_dispatch+0x1e2(809ef48)
> libglib-2.0.so.0.1400.4`g_main_context_dispatch+0x85(809ef48)
> libglib-2.0.so.0.1400.4`g_main_context_iterate+0x3ce(809ef48, 1, 1, 80a1308)
> libglib-2.0.so.0.1400.4`g_main_loop_run+0x1b8(8119748)
> libgtk-x11-2.0.so.0.1200.3`gtk_main+0xb2(80474e0, 80473d4, d13fc7cc, 0,
> 805f9b4
> , 0)
> main+0x5cf(1, 8047418, 8047420)
> _start+0x7a(1, 8047548, 0, 804755f, 8047578, 80475d9)
>
>
>
> Related SMF services are healthy:
>
> $ svcs postrun dbus hal
> STATE STIME FMRI
> online 12:26:18 svc:/system/dbus:default
> online 12:26:53 svc:/system/hal:default
> online 12:26:54 svc:/system/postrun:default
>
>
> Any suggestions?
>
> -Artem
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
