gwibber-daemon Segmentation fault

[Nathaniel Dube]

Binary package hint: gwibber

The first log was from running gwibber-daemon -d > gwibber_debug.txt. There was more information printed in the Terminal that for some reason didn't make it into the debug file. So I copied and paste it into a separate file that I'll upload after this initial post. I can only upload one file right now.

I'm running Gwibber 2.0.0 on Ubuntu 9.10 64 bit. Not much else to say except the gwibber-daemon crashes after running for some time. The gwibber settings are optimized for use with indicator-applet 0.1 So when I click X on gwibber to close the main window, the gwibber-daemon remains running in the indicator-applet. Which I'm fine with. I don't leave the main Gwibber window open long enough to see if it to would crash.

[Victor Vargas (kamus)]

What exactly version of gwibber are you using? can you try to reproduce this issue in latest version of gwibber? maybe another instance of gwibber running and is causing the crashed.

[Nathaniel Dube (z3ro3x-deactivatedaccount)]

In Synaptic it says Version: 2.0.0~bzr476-0ubuntu3. I just added the daily repo from https://launchpad.net/~gwibber-daily/+archive/ppa to my sources and updated gwibber to 2.0.0~bzr478-0ubuntu2~daily1. So I'll need some time for testing to let you know if the issue still exist in the new version or not.

[Nathaniel Dube (z3ro3x-deactivatedaccount)]

This time around I used the command "gwibber-daemon -d > gwibber_daemon.log 2>&1". I have no idea what the 2>&1 part does but I remembered seeing it in a command from a site I went to for help on debugging a pulseaudio problem I'm currently having. Anyway, I thought I'd try that extra part with debugging gwibber to see what it would do out of curiosity. To my surprise it causes all the other garbage in shell to be stored in the log, where as the prior command didn't. So this new command might be useful for anyone else debugging some issue or another. I was running version 2.0.0~bzr478-0ubuntu2~daily1 of gwibber when I created this log.

Same issue as before, upgrading the version didn't help.

[Nathaniel Dube (z3ro3x-deactivatedaccount)]

I sent the last log prematurely. I had the last post written and ready to send the moment the gwibber-daemon crashed. I got side tracked with other stuff and sent the post and forgot to wait for the daemon to crash. The last log looked like it had errors in it so it might be useful anyway. In spit of that, here's a log with the crash running the same version as mentioned above.

[Nathaniel Dube (z3ro3x-deactivatedaccount)]

Now running gwibber - 2.0.0~bzr486-0ubuntu1~daily1~karmic and segmentation fault still occurs.

Command used for debugging...
gwibber-daemon -d > gwibber_daemon_25_11_2009.log 2>&1

[Patrick (pschoeb)]

I have this same problem with gwibber-daemon, though I didn't notice it at first. When I first used qwibber it crashed once, disappearing from the notification panel, but now it seems to stay running. I didn't think much of that crash, because I first stated gwibber from gnome do, but then noticed an entry in ubunutu's new notification applet, but the entry was in the format that it didn't think qwibber was running, so I clicked on the qwibber entry under the notification applet, it crashed sometime latter, but from then on I always started it from the notification applet.

I noticed the segfaults in my logs when I was looking into evolution locking up periodically. Qwibber application seems to stay up and running despite the segfault, what I have noticed though is that it doesn't update, and then I hit refresh and a whole slew of updates come in. So refresh must restart the daemon?

Also I have noticed that sometimes, the entry in the notification applet appears to think qwibber is not running, even though I can still access the application, so the notification applet must be linked to the daemon for this reporting.

It's possible there is a linkage to my evolution problem, as there is some synchronicity with the two problems. If evolution has locked up, then I usually notice a segfault in qwibber-daemon has occurred recently. So far qwibber has been segfaulting about once a day, and evolution locks up once a day. I'm going to try not running qwibber to see if it solves my evolution lock ups.

[Patrick (pschoeb)]

My segfault has gone away after I did several things to my computer, I'm not sure which was the fix, because I did them at about the same time.

1.) Besides the evolution lock up I noticed some very subtle X windows weirdness, the weather icon sometimes failing to display in panel, mouse pointer very occasionally jumping. It seemed possible that this was a subtle hardware problem, and since there were several updates to my bios, i updated my bios and these subtle problems disappeared.

2.) Evolution was loading at boot up from a saved session, I thought that maybe this was causing a problem and so cleared this and started it manually.

3.) There was a bug with evolution-indicator where it won't change the envelope icon in the indicator-applet if the mail is in your local Inbox, I installed a fix for evolution-indicator from Karmic-proposed, though it still doesn't fix the bug, I assume it might have other differences from the original.

So now I haven't had a segfault in two days, where before it would happen at least once a day, also evolution no longer locks up, which was happening with similar frequency.

[Omer Akram (om26er)]

Thanks for taking time to report this bug and help make ubuntu better. In gwibber 2.0 gwibber-daemon crashed atleast twice in an hour for me. But in gwibber 2.29.xx I have not had even a single crash for gwibber-daemon can you please try the development release of gwibber and see if the problem still exists. Thanks again.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Lucid version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!