Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report:
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1 outdated debug symbol package for kbd: package version 1.15.3-9ubuntu1 dbgsym version 1.15.2-3ubuntu4 outdated debug symbol package for wpasupplicant: package version 1.0-2ubuntu3 dbgsym version 0.7.3-6ubuntu2 outdated debug symbol package for libecryptfs0: package version 100-0ubuntu1 dbgsym version 96-0ubuntu3 outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11.1 outdated debug symbol package for usbutils: package version 1:005-3 dbgsym version 1:005-1 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1047267/+attachment/3297889/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1047267 Title: gwibber-service crashed with SIGSEGV Status in “gwibber” package in Ubuntu: Invalid Bug description: This crash occurred while I tried to open unread status messages in gwibber... ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gwibber-service 3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 15:36:40 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gwibber-service InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gwibber-service SegvAnalysis: Segfault happened at: 0xb6ca3fd9: mov 0x4(%eax),%edx PC (0xb6ca3fd9) ok source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gwibber StacktraceTop: ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 Title: gwibber-service crashed with SIGSEGV UpgradeStatus: Upgraded to quantal on 2012-07-29 (39 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1047267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
