gnome-panel crashes because of recent files

Bug #18759 reported by Danilo Piazzalunga
30
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

This one could be related to #11147. After opening a SXW file with
OpenOffice.org, the Gnome panel started crashing.

Before crashing, it reported these weird looking errors (using it_IT.UTF-8 locale):

** (gnome-panel:10918): WARNING **: Error in parse: Errore alla riga 1218: Il
carattere '%' non è valido all'interno di
un nome di entità

** (gnome-panel:10918): WARNING **: Errore alla riga 1218: Il carattere 'on è
valido all'interno di un nome di entità

Note that in the second warning, part of the message (the actual character, the
closing quote, the space and the 'n') is missing. For comparison, the output
with LANG=C is:

** (gnome-panel:10299): WARNING **: Error in parse: Error on line 1218:
Character '%' is not valid inside an entity name** (gnome-panel:10299): WARNING
**: Error on line 1218: Character '-1073745380s not valid inside an entity name

** (gnome-panel:10299): WARNING **: Error in parse: Error on line 1218:
Character '%' is not valid inside an entity name** (gnome-panel:10299): WARNING
**: Error on line 1218: Character '-1073745348s not valid inside an entity name

Note that it is still mangled. But, with the C locale, the panel does not crash
at all.

Unfortunately, I forgot to make a copy of my "buggy" ~/.recently-used before
deleting it. I hope a crash dump will still be useful.

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

Created an attachment (id=2924)
gnome-panel backtrace with debug libs installed

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

Created an attachment (id=2925)
The reported message with its translation in Italian

This is to show that both strings are well formed and that the bug isn't
triggered by a bad string in the translation. This was obtained using msgunfmt
on the .mo installed on my system.

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

Er... I forgot to mention that I am using Hoary.

Revision history for this message
Sebastien Bacher (seb128) wrote :

thanks for your bug. The backtrace is useful, but having the .recently-used or
the filename would be better. Can you reproduce the bug when opening the file
again? Some such issues are fixed with the 2.11 versions of gnome-panel which
has some libegg fixes.

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

The filename is
"file:///home/danilo/Dati/Universita/GeoStat/trunk/doc/GeoStat.sxw", but
unfortunately I cannot reproduce the bug anymore. I will be on lookout to see if
it shows up again...

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

I opened the file attached in bug #17435 and I am now able to reproduce the same
bug. The backtrace at crash time is exactly the same, and now I can provide a
clean .recently-used file. Additionally, I obtained a backtrace some time before
the garbled warning is produced: I hope this is useful to track down the crash.

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

Created an attachment (id=2999)
A clean .recently-used file which triggers the bug

Revision history for this message
Danilo Piazzalunga (danilopiazza) wrote :

Created an attachment (id=3000)
A backtrace obtained before emitting the garbled warning

I don't know whether the garbled warning is another sign of this bug or if this
is an unrelated one, but I hope this is useful.

Revision history for this message
Corey Burger (corey.burger) wrote :

*** Bug 17435 has been marked as a duplicate of this bug. ***

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the file. It doesn't crash with the current GNOME 2.11.5 packages,
this is probably one if the libegg issues fixed since GNOME 2.10/hoary. I'm
closing this bug. Feel free to reopen if you disagree.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.