After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 172587 - Gnome-Panel crash after run OpenOffice "powerpoint" on a files in a usbdisk
Gnome-Panel crash after run OpenOffice "powerpoint" on a files in a usbdisk
Status: RESOLVED FIXED
Product: libegg
Classification: Other
Component: recent-files
unspecified
Other other
: High critical
: ---
Assigned To: Emmanuele Bassi (:ebassi)
Libegg maintenance
: 301050 303095 303127 303683 303978 304038 304320 305050 306524 312888 317287 319975 323477 323825 326215 328634 331124 333520 333954 334352 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-04 08:59 UTC by Maurizio Moriconi
Modified: 2006-03-12 22:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
.recently-used after bug (1.95 KB, text/plain)
2005-04-06 08:02 UTC, Maurizio Moriconi
Details
.xsession-errors (3.14 KB, text/plain)
2005-04-06 08:04 UTC, Maurizio Moriconi
Details

Description Maurizio Moriconi 2005-04-04 08:59:12 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 ()

Thread 2 (Thread -1225114704 (LWP 10481))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall




------- 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.

Comment 1 Elijah Newren 2005-04-04 14:18:18 UTC
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?
Comment 2 Vincent Untz 2005-04-04 15:08:41 UTC
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.
Comment 3 Maurizio Moriconi 2005-04-05 08:06:44 UTC
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 ()

Thread 2 (Thread -1225114704 (LWP 8723))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall

Comment 4 Vincent Untz 2005-04-05 20:41:05 UTC
Thanks, this is definitely useful. Do you have some warnings in
~/.xsession-errors too?

I'll try to look at this tomorrow.
Comment 5 Maurizio Moriconi 2005-04-05 20:57:45 UTC
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'.
Comment 6 Vincent Untz 2005-04-06 07:06:05 UTC
Can you attach your ~/.recently-used file to this bug? I'll probably be able to
reproduce the  crash with it.
Comment 7 Maurizio Moriconi 2005-04-06 08:02:38 UTC
Created attachment 39738 [details]
.recently-used after bug
Comment 8 Maurizio Moriconi 2005-04-06 08:04:11 UTC
Created attachment 39739 [details]
.xsession-errors

Look at error in gnome-panel:7193
Comment 9 Vincent Untz 2005-04-06 08:14:01 UTC
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.
Comment 10 Kjartan Maraas 2005-04-18 12:22:41 UTC
*** Bug 301050 has been marked as a duplicate of this bug. ***
Comment 11 Olav Vitters 2005-05-05 19:55:29 UTC
*** Bug 303095 has been marked as a duplicate of this bug. ***
Comment 12 Olav Vitters 2005-05-05 19:56:33 UTC
*** Bug 303127 has been marked as a duplicate of this bug. ***
Comment 13 Elijah Newren 2005-05-11 01:30:22 UTC
*** Bug 303683 has been marked as a duplicate of this bug. ***
Comment 14 Elijah Newren 2005-05-13 05:13:49 UTC
*** Bug 303978 has been marked as a duplicate of this bug. ***
Comment 15 Elijah Newren 2005-05-14 00:30:33 UTC
*** Bug 304038 has been marked as a duplicate of this bug. ***
Comment 16 Elijah Newren 2005-05-17 03:39:05 UTC
*** Bug 304320 has been marked as a duplicate of this bug. ***
Comment 17 Elijah Newren 2005-05-29 00:37:19 UTC
*** Bug 305050 has been marked as a duplicate of this bug. ***
Comment 18 Sebastien Bacher 2005-06-05 14:46:19 UTC
*** Bug 306524 has been marked as a duplicate of this bug. ***
Comment 19 Sebastien Bacher 2005-08-08 16:20:48 UTC
*** Bug 312888 has been marked as a duplicate of this bug. ***
Comment 20 Vincent Untz 2005-08-24 14:12:56 UTC
This is definitely a libegg thing.
This might already be fixed, though (since I can't reproduce).
Comment 21 Emmanuele Bassi (:ebassi) 2005-08-24 14:42:21 UTC
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?
Comment 22 Vincent Untz 2005-10-01 09:10:39 UTC
*** Bug 317287 has been marked as a duplicate of this bug. ***
Comment 23 Emmanuele Bassi (:ebassi) 2005-10-20 15:23:26 UTC
it seems that this is all openoffice's fault:

  <seb128>  openoffice2 doesn't get the "&amp," 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 "&amp;" by "&", which
makes the panel unhappy
Comment 24 Emmanuele Bassi (:ebassi) 2005-10-20 15:55:43 UTC
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.
Comment 25 Emmanuele Bassi (:ebassi) 2005-11-28 17:55:45 UTC
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.
Comment 26 Sebastien Bacher 2005-12-07 18:08:18 UTC
*** Bug 323477 has been marked as a duplicate of this bug. ***
Comment 27 Vincent Untz 2005-12-14 22:11:49 UTC
I updated the code. I think we can close this bug.
Comment 28 Vincent Untz 2005-12-14 22:13:57 UTC
*** Bug 323825 has been marked as a duplicate of this bug. ***
Comment 29 Vincent Untz 2005-12-15 08:15:59 UTC
*** Bug 319975 has been marked as a duplicate of this bug. ***
Comment 30 Vincent Untz 2006-01-08 17:25:07 UTC
*** Bug 326215 has been marked as a duplicate of this bug. ***
Comment 31 Vincent Untz 2006-01-26 10:12:51 UTC
*** Bug 328634 has been marked as a duplicate of this bug. ***
Comment 32 Karsten Bräckelmann 2006-03-05 20:32:00 UTC
*** Bug 333520 has been marked as a duplicate of this bug. ***
Comment 33 Vincent Untz 2006-03-06 20:27:02 UTC
*** Bug 331124 has been marked as a duplicate of this bug. ***
Comment 34 Karsten Bräckelmann 2006-03-08 23:55:03 UTC
*** Bug 333954 has been marked as a duplicate of this bug. ***
Comment 35 Sergej Kotliar 2006-03-12 22:16:58 UTC
*** Bug 334352 has been marked as a duplicate of this bug. ***