This bug was fixed in the package gwibber - 3.5.90-0ubuntu2
---
gwibber (3.5.90-0ubuntu2) quantal-proposed; urgency=low
* debian/patches/lp_1051801.patch
- Fixed SIGSEGV in gwibber-service (LP: #1051801)
gwibber (3.5.90-0ubuntu1) quantal-proposed; urgency=low
* New upstream
** Branch linked: lp:ubuntu/quantal-proposed/gwibber
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051801
Title:
gwibber-service crashed with SIGSEGV
To manage notifications about this bug go to:
** Branch linked: lp:~ken-vandine/gwibber/lp_1051801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051801
Title:
gwibber-service crashed with SIGSEGV
To manage notifications about this bug go to:
** Description changed:
random crash
+
+ I believe this is due to thread-unsafe usage of libdbus, care of glib
+ implicitly spawning a thread for gdbus. A call to
+ dbus_threads_init_default() early in main should fix this.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gwibbe
** Changed in: gwibber (Ubuntu)
Status: Invalid => Confirmed
** Changed in: gwibber (Ubuntu)
Importance: Undecided => High
** Changed in: gwibber (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1051801
Title:
gwibber-service crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchp