Bug#242258: gnome-panel crashes on invalid .recently-used entry

Alexander Winston Alexander Winston <alexander.winston@comcast.net>, 242258@bugs.debian.org
Mon, 05 Apr 2004 12:42:20 -0400


--=-0L+Mvb5b0IXLaO/jP63U
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

tags 242258 + fixed-upstream
stop

On Mon, 2004-04-05 at 17:55 +0200, Vincenzo Gervasi wrote:
> Package: gnome-panel
> Version: 2.4.2-4
> Severity: important
>=20
> gnome-panel crashes upon finding XML encoding problems in .recently used.
> In particular, I had the following entry (created by OpenOffice.org):
>=20
> <RecentItem>
>   <URI>file:///home/gervasi/REFSQ04/Reviews/06%20&%2022%20Rolland.doc</UR=
I>
>   <Mime-Type>application/msword</Mime-Type>
>   <Timestamp>1080897663</Timestamp>
>   <Groups>
>     <Group>OpenOffice.org</Group>
>   </Groups>
> </RecentItem>
>=20
> As you can notice, the encoding of the file name "06 & 22 Rolland.doc" wa=
s
> incorrect, in that the ampersand was not encoded as it should. However, i=
t
> is not acceptable that the panel crashes (in an endless loop, due to the
> session manager re-launching it every time) just because an application o=
r a
> user has used an unusual file name. XML parsing errors at this stage shou=
ld
> be harmless -- at the worst, the offending entry should be dropped from
> the recent files menu.
>=20
> In my case, the problem was fixed by (manually) rewriting the entry as
> follows:
>=20
> <RecentItem>
>   <URI>file:///home/gervasi/REFSQ04/Reviews/06%20&%2022%20Rolland.doc</UR=
I>
>   <Mime-Type>application/msword</Mime-Type>
>   <Timestamp>1080897663</Timestamp>
>   <Groups>
>     <Group>OpenOffice.org</Group>
>   </Groups>
> </RecentItem>
>=20
> Notice how & was encoded to &amp; (whereas the previous &%2022 was an
> illegal entity name).
>=20
> Thanks for your excellent work,
> -Vincenzo

I have good news Vincenzo! :) This bug has already been found and fixed
upstream, as you can see at
<http://bugzilla.gnome.org/show_bug.cgi?id=3D133257>. I am running
gnome-panel 2.5.92 and I haved confirmed that it has been fixed using
your example file.

Thank you for reporting the bug nonetheless!

--=-0L+Mvb5b0IXLaO/jP63U
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAcYxqDEidtQ6Z/WURAja0AKCNPuYz9DIoQw81HococX13Hc5iewCeNgjL
i1l5xMXp7JyHQxc99Ch+Vqc=
=P4Se
-----END PGP SIGNATURE-----

--=-0L+Mvb5b0IXLaO/jP63U--