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. -- gwibber-daemon Segmentation fault https://bugs.launchpad.net/bugs/479852 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
