Hi there, I'm running Jaunty and are (since Hardy) experiencing the same problems.
I followed this thread which I only found today (luckily). I spent some two hours to dig a little into the problem and found that its got to do (as others above pointed out already) with some little gnome inside the code ;) I first suspected gobject.threads_init() as other resources pointed out, that time and order of calls matter in PyGTK. Then, as a first step, I added logging to see how far Glipper would fare: It is merely starting up before it crashes. Being intrigued by this and by the fact that it really only happens at boot time, I started to write this patch (see attachment). For now after the first successful (re-)boot (done a far few by now) test, Glipper *did not* crash with this code in place! I'd be really curious whether it'll help others, so please give it a try! Best regards, Udo ** Attachment added: "Logs to $HOME/glipper.log or whatever you set log_file to..." http://launchpadlibrarian.net/27691894/glipper.patch -- Glipper dies when desktop starting https://bugs.launchpad.net/bugs/213494 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
