*** This bug is a duplicate of bug 621048 ***
https://bugs.launchpad.net/bugs/621048
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #621048, so is being marked as such. Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869331/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869333/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869335/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869336/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869337/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869339/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1237505/+attachment/3869340/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 621048
mission-control-5 crashed with SIGSEGV in __libc_start_main()
** Information type changed from Private Security to Public Security
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1237505
Title:
mission-control-5 crashed with SIGSEGV in __libc_start_main()
Status in “telepathy-mission-control-5” package in Ubuntu:
New
Bug description:
apport broken
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu6
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 9 17:26:30 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-02-25 (226 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic
root=UUID=8a97b2a5-e1ba-44c0-9068-47b95d9f676c ro quiet splash vt.handoff=7
ProcEnviron:
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x410260: mov 0x18(%rdi),%rdi
PC (0x00410260) ok
source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed
readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
?? ()
?? ()
__libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
?? ()
Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-07-18 (83 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1237505/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
