Glipper crashes panel on system reboot

[crjackson]

After adding the Glipper Panel applet to the panel, the panel crashes when loading after a reboot. The applet had to be completely removed on my system before rebooting, otherwise the system would just lock up and be unresponsive. I would have to do a hard reset several times to get the desktop to respond to a mouse click. Even a ctrl+alt+bkspace would fix the desktop.

This issue got worse after installing recent proposed updates on 5/3/2008. The problem already existed, but got worse after the updates. I'm not sure if it's a panel but or a glipper bug.

[marco.pallotta (marco-pallotta)]

I also have the same problem on hardy heron x86-64. The difference with what crjackson posted is that I haven't to remove the applet before rebooting because the system doesn't lock up and isn't unresponsive. To resolve the issue (until next reboot) is to logout and re-login. In fact I logout and login again the applet works ok.

[marco.pallotta (marco-pallotta)]

I also have the same problem on hardy heron x86-64. The difference with what crjackson posted is that I haven't to remove the applet before rebooting because the system doesn't lock up and isn't unresponsive. To resolve the issue (until next reboot) is to logout and re-login. In fact I logout and login again the applet works ok.

[marco.pallotta (marco-pallotta)]

I have to add an info about this bug: not at every boot this bug happens (at least in my system)

[marco.pallotta (marco-pallotta)]

I tested glipper either in Ubuntu x86-64 or in x86 and, after 2 months from the first post in this bug, with systems in full update:
- in x86_64 glipper crashes at every reboot (but if you logout and the login, X starts glipper with no problem until next reboot)
- in x86 glipper crashes not at every reboot

[crjackson (crjackson)]

Seems no one is working on this.

[marco.pallotta (marco-pallotta)]

@crjackson I marked this bug as duplicate of bug 213494 becuase the error you posted (Screenshot-Error.png) fits the issue related this last even if your error description is not properly the same.
Please reopen it if you think your bug is not a duplicate of bug 213494 and excuse me if I was wrong.