GNOME Bugzilla – Bug 165231
Panel started crashing!
Last modified: 2005-07-03 12:48:55 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: critical Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Panel started crashing! Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Out of nowhere the panel started crashing and now crashes everytime I login. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088101440 (LWP 24640)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 54913
Thread 1 (Thread 1088101440 (LWP 24640))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-25 15:53 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace. Could you attach your ~/.recently-used file?
Yup, that was it... I was editing the .recently-used file and deleted one start-tag. It's a bit weird though, gnome-panel should survive something like this.
I can reproduce this. Opened .recently-used and removed the first two tags from the first entry and restarted the panel. This is using 2.8.x. I'll try 2.9.x now...I even updated with the latest egg-recent changes in CVS and it still crashes... 2.10.0 material? Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1208116576 (LWP 25394)] 0x00b827a2 in ?? () at rtld.c:577 from /lib/ld-linux.so.2 577 relocate_doit (void *a)
+ Trace 54923
Thread 1 (Thread -1208116576 (LWP 25394))
This is most probably a bug in libegg and not the panel.
Yes, it seems that the egg-recent code just assumes the .recently-used file is going to be valid XML and does no checking on whether tags are missing or broken at all.
Moving to libegg. Someone really need to look at these eggrecent severe bugs.
I can't stop 2.10 for a bug whose reproduction instructions include hand-editing an XML file to break it. If we see reports in the wild of invalid XML being generated, I'll make it a release showstopper again, but until then merely marking urgent and a total and complete embarassment to the recent files code ;)
Created attachment 38040 [details] [review] patch
applied to HEAD.