*** 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/1058941/+attachment/3357482/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357484/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357487/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357488/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357489/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357491/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1058941/+attachment/3357492/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 621048
mission-control-5 crashed with SIGSEGV in __libc_start_main()
** Visibility changed to: Public
** 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/1058941
Title:
mission-control-5 crashed with SIGSEGV in __libc_start_main()
Status in “telepathy-mission-control-5” package in Ubuntu:
New
Bug description:
Ubuntu 12.10
I just started my pc and I got this message and bug report.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-mission-control-5 1:5.13.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Sun Sep 30 00:04:11 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic
root=UUID=0972b258-e0ef-4a49-afd5-5e0433564cf1 ro quiet splash
SegvAnalysis:
Segfault happened at: 0x410530: mov 0x18(%rdi),%rdi
PC (0x00410530) 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 quantal on 2012-09-28 (1 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/1058941/+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
