Public bug reported: Release of Ubuntu: Package Version: Expected Results: Actual Results: It crash but it wasn't in use.
ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gwibber-service 3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 19 16:44:15 2013 Disassembly: => 0x7fbd777bccc6: Cannot access memory at address 0x7fbd777bccc6 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gwibber-service InstallationDate: Installed on 2012-10-12 (129 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20121011) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gwibber-service SegvAnalysis: Segfault happened at: 0x7fbd777bccc6: Cannot access memory at address 0x7fbd777bccc6 PC (0x7fbd777bccc6) ok SP (0x7fff6b623ff0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gwibber StacktraceTop: ?? () ?? () ?? () Title: gwibber-service crashed with SIGSEGV UpgradeStatus: Upgraded to raring on 2012-10-13 (129 days ago) UserGroups: adm audio cdrom dialout dip disk fax fuse kvm libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video whoopsie ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring running-unity ** Information type changed from Private 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/1130194 Title: gwibber-service crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1130194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs