GNOME Bugzilla – Bug 363437
gnome-panel crash to gtkrecentmanager code
Last modified: 2007-07-08 08:16:46 UTC
That bug has been described on https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/66189 "All of a sudden gnome-panel cannot start, it crashed every time. This did not start to happen after an update (gnome-panel has been restarted since the last update and worked fine), it just started out of the blue. Now I'm sure this is something I did but I can't remember fiddling with anything that would break it, anyways I have attached the backtrace, thanks in advance. http://librarian.launchpad.net/4843387/gnome-panel-bugreport.txt gnome-panel-dbg backtrace gnome-panel-dbg backtrace ... > Thanks for your bug. That looks like a GTK issue, could you get a backtrace with libgtk2.0-0-dbg libglib2.0-0-dbg installed? ... http://librarian.launchpad.net/4891010/gnome-panel-bugreport.txt backtrace with debug here is my backtrace with all the debugging symbols. ... Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 805541600 (LWP 11943)] 0x0f16b334 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 77168
*** Bug 351704 has been marked as a duplicate of this bug. ***
thanks for the stack trace.
*** Bug 377754 has been marked as a duplicate of this bug. ***
*** Bug 377755 has been marked as a duplicate of this bug. ***
fixed in both HEAD and the stable branch. 2006-11-22 Emmanuele Bassi <ebassi@gnome.org> * gtk/gtkrecentmanager.c: (get_uri_shortname_for_display): g_filename_from_uri() might fail; catch the failure and fall back to the non-local URI case. (#363437)
*** Bug 378448 has been marked as a duplicate of this bug. ***
*** Bug 379863 has been marked as a duplicate of this bug. ***
*** Bug 386102 has been marked as a duplicate of this bug. ***
*** Bug 394599 has been marked as a duplicate of this bug. ***
*** Bug 397020 has been marked as a duplicate of this bug. ***
*** Bug 397258 has been marked as a duplicate of this bug. ***
*** Bug 358044 has been marked as a duplicate of this bug. ***
*** Bug 406978 has been marked as a duplicate of this bug. ***
*** Bug 417829 has been marked as a duplicate of this bug. ***
*** Bug 421073 has been marked as a duplicate of this bug. ***
*** Bug 421488 has been marked as a duplicate of this bug. ***
*** Bug 423152 has been marked as a duplicate of this bug. ***
*** Bug 412655 has been marked as a duplicate of this bug. ***
*** Bug 438226 has been marked as a duplicate of this bug. ***
*** Bug 454672 has been marked as a duplicate of this bug. ***