glipper crashed with ValueError in load()

Bug #175490 reported by Tomasz Sterna
This bug report is a duplicate of:  Bug #213494: Glipper dies when desktop starting. Edit Remove
98
Affects Status Importance Assigned to Milestone
glipper (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: glipper

I've ried to add glipper panel applet, but it crashed not showing up.

ProblemType: Crash
Architecture: i386
Date: Tue Dec 11 09:17:32 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/glipper/glipper
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: glipper 1.0-1
PackageArchitecture: i386
ProcCmdline: python /usr/lib/glipper/glipper --oaf-activate-iid=OAFIID:Glipper_Factory --oaf-ior-fd=41
ProcCwd: /home/smoku
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/glipper/glipper', '--oaf-activate-iid=OAFIID:Glipper_Factory', '--oaf-ior-fd=41']
SourcePackage: glipper
Title: glipper crashed with ValueError in load()
Uname: Linux wing 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Tomasz Sterna (smoku) wrote :
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

I see the same in Hardy.

Linux hivepad 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu hardy (development branch)
Release: 8.04
Codename: hardy

Changed in glipper:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Smoku, please, can I set the bug public?
Normally apport set the bug as private because the report can contain sensible data which I didn't found in this bug.
You are not obligated, but this will avoid duplicates.

Revision history for this message
Tomasz Sterna (smoku) wrote :

Please do. It's ok with me.

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Thanks a lot.

Changed in glipper:
importance: Medium → Low
status: Confirmed → Triaged
Revision history for this message
Andrew Conkling (andrewski) wrote :

I contacted the developer:

On Dec 28, 2007 4:21 AM, Eugenio Depalo <email address hidden> wrote:
> This may be caused by incompatibilities with the old glipper history
> file. Try deleting the .glipper folder entirely in your home folder.

Worked for me. Hopefully we can get an update that won't crash with the old history file.

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Thank you, Andrew.
Deleting the .glipper folder has worked for me.

Revision history for this message
Thomas Novin (thomasn80) wrote :

Also had the same problem and it was also resolved by removing ~/.glipper. I'm on Hardy aswell.

Revision history for this message
madmtbbibi (simonfilgis) wrote : Re: [Bug 175490] Re: glipper crashed with ValueError in load()

It works. thank you

On Fr, 2008-01-25 at 12:00 +0000, ThomasNovin wrote:
> Also had the same problem and it was also resolved by removing
> ~/.glipper. I'm on Hardy aswell.
>

Revision history for this message
ThigU (thigu15-gmail) wrote :

It works here after i deleted the history folder.

Thank you!

Revision history for this message
Jerem (jer151) wrote :

It's maybe a problem because some users, like me, use gutsy and hardy in same time with the same /home and then, when Gutsy run, it rewrite in ~/.glipper, and the next boot on hardy redo this bug.

Revision history for this message
Andrew Conkling (andrewski) wrote :

On Tue, Mar 4, 2008 at 6:59 AM, Jeremy Soulary <email address hidden> wrote:

> It's maybe a problem because some users, like me, use gutsy and hardy in
> same time with the same /home and then, when Gutsy run, it rewrite in
> ~/.glipper, and the next boot on hardy redo this bug.
>

Yes, that would certainly make a difference.

In general, I'm not sure why some are thanking me; while I did mention a
workaround from the developer, it's just that, and doesn't help us get any
closer to resolving this bug. :-/

Revision history for this message
Jerem (jer151) wrote :

What I wanted to say is that the delete of ~ /.Glipper is not an solution (2 comments : "It works"), or it should be automatic if the glipper detects a wrong file. It was just a remark, sorry if I did not write to the right place

Revision history for this message
Andrew Conkling (andrewski) wrote :

On Tue, Mar 4, 2008 at 2:46 PM, Jeremy Soulary <email address hidden> wrote:

> What I wanted to say is that the delete of ~ /.Glipper is not an
> solution (2 comments : "It works"), or it should be automatic if the
> glipper detects a wrong file. It was just a remark, sorry if I did not
> write to the right place
>

Sorry, Jeremy, my comments were more meant for the previous comments in
total. "Upon reflection of the previous comments..." :)

Revision history for this message
michelem (michele-marcucci) wrote :

Workaround worked for me too (Hardy Alpha 6)

Revision history for this message
Louis Boldt (louieb) wrote :

Deleting .glipper solved the crash problem in Hardy beta. I did a fresh install. Have /home on a separate partition. So .glipper was from a Gutsy install.

Revision history for this message
Fredrik Normann (smartypants) wrote :

deleting .glipper worked for me to

Revision history for this message
Fredrik Normann (smartypants) wrote :

Hum, glipper still crashes on Hardy Beta even after deleting .glipper. I can start the applet, but after a while it crashes and I have to reload it

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

@Smartypants: It seems a different issue. Please look into your /ver/crash directory and double click on the glipper.crash file.

Revision history for this message
Charly Kubuntu (brennerkh) wrote :

I have deinstalled glipper and use parcellite than tihs.

There are no problems with this.

2008/3/24, Andrea Corbellini <email address hidden>:
>
> @Smartypants: It seems a different issue. Please look into your
> /ver/crash directory and double click on the glipper.crash file.
>
>
> --
> glipper crashed with ValueError in load()
> https://bugs.launchpad.net/bugs/175490
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Thomas Novin (thomasn80) wrote :

I've also switched to parcellite[1] and hadn't had any problems since...

1. http://code.google.com/p/xyhthyx/

Revision history for this message
Tomasz Sterna (smoku) wrote :

Thanks Charly & Thomas. Did so and parcellite works fine. :-)

Revision history for this message
Stefan Stasik (stefan-stasik) wrote :

I upgraded from Gutsy to Hardy, and Glipper stopped working on my Gnome desktop.

I removed the .glipper directory in my home dir as suggested above, and now I was able to add glipper as a Gnome applet to my desktop, without it crashing.

The problem was with the switch from glipper being a Binary app in gutsy, to being a Gnome applet in Hardy.

Thanks!

- Stefan Stasik

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

I also upgraded from gutsy to hardy, glipper no longer working. Removed the .glipper dir, and it was possible to add the applet, but clicking on it still crashes glipper every time, as long as I didn't have anything in my clipboard that glipper noticed. After loading the applet, selecting some text and pressing ctrl-c, glipper worked correctly.

Revision history for this message
Andrew Conkling (andrewski) wrote :

On Tue, Apr 8, 2008 at 7:05 AM, Jos Dehaes <email address hidden> wrote:

> I also upgraded from gutsy to hardy, glipper no longer working. Removed
> the .glipper dir, and it was possible to add the applet, but clicking on
> it still crashes glipper every time, as long as I didn't have anything
> in my clipboard that glipper noticed. After loading the applet,
> selecting some text and pressing ctrl-c, glipper worked correctly.
>

Same crash reported here? I'd expect that would give a different backtrace.

In general though, I wonder if Glipper responds equally poorly to an absent
history file as to an older one. :-/

Revision history for this message
goodhabit (goodhabit) wrote :

Glipper doesn't start in hardy.

Revision history for this message
niluge (flroth) wrote :

I use glipper applet

goodhabit a écrit :
> Glipper doesn't start in hardy.
>
>

Revision history for this message
Arthur (moz-liebesgedichte) wrote :

Removing .glipper/ resolved the not-starting-issue in hardy for me. It does seem to have a problem with an empty history though an crashes when trying to look at the empty list. Seems to crash from time to time "spontaneously" too.

Revision history for this message
Omk (ossi-viljakainen) wrote :

after upgrading to hardy, got the same problem. As suggested above, deleting .glipper solved the problem for me as well.

Revision history for this message
akudewan (akudewan) wrote :

Deleting ~/.glipper worked. Thanks for the fix.

Revision history for this message
Majestyx (majestyx) wrote :

i saw the solution too late. sorry for the report. after deleting ~/.glipper worked

Revision history for this message
Andii (andiibowsher) wrote :

I had to both delete .glipper file and uninstall and then reinstall glipper. But now it appears to be working.

Revision history for this message
Andrea Gamba (andrea-gamba) wrote :

The same on Hardy: glipper works only after deleting .glipper but then crashes due to the empty history file. Works again if something is pasted in.

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

I have uninstalled Glipper and deleted the folder ".glipper", but on Hardy for me the bug is still present. Every reboot the same error message and Glipper don't start.

Revision history for this message
Andrew Conkling (andrewski) wrote :

On Fri, May 2, 2008 at 8:07 AM, Nicola Jelmorini <email address hidden>
wrote:

> I have uninstalled Glipper and deleted the folder ".glipper", but on
> Hardy for me the bug is still present. Every reboot the same error
> message and Glipper don't start.
>

Please file a new bug with a crash report; this sounds like a separate (but
perhaps related) issue.If you don't mind, let me know of the new bug and
I'll see what I can make of it.

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :
Revision history for this message
Andrew Conkling (andrewski) wrote :

On Fri, May 2, 2008 at 10:24 AM, Nicola Jelmorini <email address hidden>
wrote:

> I have created a new bug here:
> https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/225739
>

Great. Can you make the bug public so I can see it? You should be able to
access the setting via the following link:
https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/225739/+secrecy.
Thanks!

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

Voilà. Now the bugreport should be public.

Revision history for this message
Rory McCann (rorymcc) wrote :

This was happening to me. Deleting the ~/.glipper folder allowed it to run again.

I suggest glipper detect this and automatically delete the offending files. One's clipboard history is not important data (i.e. if you care about it, you'll have it in a file), deleting it at startup is not a problem IMO.

Revision history for this message
bullium (wbradshaw) wrote :

I also upgraded from Hardy to Heron with glipper crashing when adding it to the panel. As other comments suggested I deleted ~/.glipper directory and could then add glipper to the panel. Although it did crash again after trying to clear the list, I then copied some text and cleared the list a second time and it did not and hasn't crashed since. So my resolution was to delete the ~./glipper folder -> add glipper to the panel -> copy text to the clipboard -> clear the list. This seems to solve the issue indefinetly for me. Thanks for the comments, launchpad is great!

Revision history for this message
bullium (wbradshaw) wrote :

I also upgraded from Hardy to Heron with glipper crashing when adding it to the panel. As other comments suggested I deleted ~/.glipper directory and could then add glipper to the panel. Although it did crash again after trying to clear the list, I then copied some text and cleared the list a second time and it did not and hasn't crashed since. So my resolution was to delete the ~./glipper folder -> add glipper to the panel -> copy text to the clipboard -> clear the list. This seems to solve the issue indefinitely for me. Thanks for the comments, launchpad is great!

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

For me the work around of @bullium don't function as the others work arounds described here.
I think that Glipper still has a problem.
It's not normal that for some users it's ok with a work around, fore some others with another work around, and for some others Glipper don't function at all.

My solution is to use Parcellite (http://www.gnomefiles.org/app.php/Parcellite) downloaded from GetDeb. Parcellite is a very rock solid alternative to Glipper.

Revision history for this message
David (gaffin) wrote :

I've tried the bullum's workaround a couple of times, but each time I do, Glipper crashes the next time I login. I get the GNOME prompt that asks if I want to delete the panel applet.

Revision history for this message
Andrew Conkling (andrewski) wrote :

On Sat, May 17, 2008 at 3:45 AM, Nicola Jelmorini <email address hidden>
wrote:

> For me the work around of @bullium don't function as the others work
> arounds described here.
> I think that Glipper still has a problem.
> It's not normal that for some users it's ok with a work around, fore some
> others with another work around, and for some others Glipper don't function
> at all.
>

Yes, it's not a *solution*, and I frankly don't understand why people keep
posting comments about the workaround. Even if it works, the bug is still
valid, and shouldn't ever get to the point that it can't understand its own
history file.

If someone else wants to make overtures upstream or fix it themselves,
that'd be great, but I don't know that continuing to comment and to discuss
the workaround on this bug is getting us anywhere.

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

Other bug subscribers

Remote bug watches

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