GNOME Bugzilla – Bug 172587
Gnome-Panel crash after run OpenOffice "powerpoint" on a files in a usbdisk
Last modified: 2006-03-12 22:16:58 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: critical Version: GNOME2.10.0 2.10.x Gnome-Distributor: Ubuntu Synopsis: Gnome-Panel crash after run OpenOffice "powerpoint" on a files in a usbdisk Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. Insert a usbdisk 2. Load a powerpoint files from nautilus 3. Exit from openoffice Expected Results: Gnome-panel crash and its not possible to recover gnome-panel How often does this happen? 2 times of 2, 100% Additional Information: There is an hint to restore gnome-panel, if i reboot the problem is still present. 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1221979424 (LWP 10470)] [New Thread -1225114704 (LWP 10481)] (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 57680
Thread 2 (Thread -1225114704 (LWP 10481))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-04 04:59 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was bugman@tiscali.it. 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.
Looks like the stack trace in bug 170655, which is a duplicate of bug 157723, which should have been fixed. What version of gnome-vfs do you have? Did you upgrade recently without restarting gnome-vfs-daemon by chance?
This can be related to bug #170660 too. Could you install gnome-panel-dbg? If the crash happens again, please paste the debugging informations from bug-buddy here.
Hi! I upgrade gnome-panel to 2.10.1 and install gnome-panel-dbg but the problem is still continue, these are the debug info from bug-buddy: Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1221979424 (LWP 8688)] [New Thread -1225114704 (LWP 8723)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 57723
Thread 2 (Thread -1225114704 (LWP 8723))
Thanks, this is definitely useful. Do you have some warnings in ~/.xsession-errors too? I'll try to look at this tomorrow.
Yes there is an error in my language (italian) its say that there is a parse error at line 4 with a character i don't remember well but i think is 'A'.
Can you attach your ~/.recently-used file to this bug? I'll probably be able to reproduce the crash with it.
Created attachment 39738 [details] .recently-used after bug
Created attachment 39739 [details] .xsession-errors Look at error in gnome-panel:7193
Thanks! The problem is the first URI: it contains a & that was not encoded in & for some reason. It should not crash though... You can remove ~/.recently-used if you don't want to see the crash again.
*** Bug 301050 has been marked as a duplicate of this bug. ***
*** Bug 303095 has been marked as a duplicate of this bug. ***
*** Bug 303127 has been marked as a duplicate of this bug. ***
*** Bug 303683 has been marked as a duplicate of this bug. ***
*** Bug 303978 has been marked as a duplicate of this bug. ***
*** Bug 304038 has been marked as a duplicate of this bug. ***
*** Bug 304320 has been marked as a duplicate of this bug. ***
*** Bug 305050 has been marked as a duplicate of this bug. ***
*** Bug 306524 has been marked as a duplicate of this bug. ***
*** Bug 312888 has been marked as a duplicate of this bug. ***
This is definitely a libegg thing. This might already be fixed, though (since I can't reproduce).
we already call g_markup_escape_text() to escape the UTF-8 URI in egg-recent-model.c:(egg_recent_model_write), and that should escape any found & into &. if the terminal and/or nautilus are set to a UTF-8 locale, '&' is automatically escaped to '%26'. and I too can't reproduce the bug. maurizio, can you please report the locale setting that you're using?
*** Bug 317287 has been marked as a duplicate of this bug. ***
it seems that this is all openoffice's fault: <seb128> openoffice2 doesn't get the "&," variant and rewrite the .recently-used with an "&" which breaks the panel <shaunm> certainly any ampersand in the query string, other than the ones used for field seperators, have to be escaped as %26 <seb128> shaunm: so for .recently-used that's correct? <shaunm> seb128: yes <seb128> that's for a filename <seb128> k, thanks * seb128 bugs on openoffice <shaunm> oo puts an & into xml without escaping it? <seb128> right * shaunm spanks OO.o <shaunm> bad xml-processing application! bad! <seb128> it rewrites .recently-used and replaces the "&" by "&", which makes the panel unhappy
the panel shouldn't crash, though, so this means adding a few more integrity checks on the EggRecentModel parser code. the changes are not that hard (force setting the items list as NULL every time the parser barfs up, and double checking into subsequent calls for an empty list), but I'm already a bit lagged behind by work and university; I could add the 'gnome-love' keyword, since, as I said, the changes aren't that hard.
vincent, could youn please re-sync with recent-files HEAD? I've tried to make the parser a bit more robust. now, if it hits badly-formed XML, it should ignore the file until someone actually fixes it; side-effect: the recent documents list will be empty (but a message will be sent to the console or .xsession-errors). I think it's the best we can do: GMarkup quits parsing if finds badly formed XML and we can't guarantee any of the data we have if that happens.
*** Bug 323477 has been marked as a duplicate of this bug. ***
I updated the code. I think we can close this bug.
*** Bug 323825 has been marked as a duplicate of this bug. ***
*** Bug 319975 has been marked as a duplicate of this bug. ***
*** Bug 326215 has been marked as a duplicate of this bug. ***
*** Bug 328634 has been marked as a duplicate of this bug. ***
*** Bug 333520 has been marked as a duplicate of this bug. ***
*** Bug 331124 has been marked as a duplicate of this bug. ***
*** Bug 333954 has been marked as a duplicate of this bug. ***
*** Bug 334352 has been marked as a duplicate of this bug. ***