I did not use selinux. It was vanilla ubuntu, I suppose.

m!

2014-03-26 16:45 GMT+01:00 Sebastien Bacher <seb...@ubuntu.com>:
> Thank you for your bug report. Are you using selinux? If some how did
> you enable/configure it? Looking to upstream reports there was a mention
> that it could happening with buggy selinux configurations...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (820204).
> https://bugs.launchpad.net/bugs/621048
>
> Title:
>   mission-control-5 crashed with SIGSEGV in __libc_start_main()
>
> Status in "telepathy-mission-control-5" package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Binary package hint: telepathy-mission-control-5
>
>   1. lsb_release -rd
>   Description:  Ubuntu maverick (development branch)
>   Release:      10.10
>
>   2. apt-cache policy telepathy-mission-control-5
>   telepathy-mission-control-5:
>     Installed: 1:5.5.3-1
>     Candidate: 1:5.5.3-1
>     Version table:
>    *** 1:5.5.3-1 0
>           500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
>           100 /var/lib/dpkg/status
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 10.10
>   Package: telepathy-mission-control-5 1:5.5.3-1
>   ProcVersionSignature: Ubuntu 2.6.35-16.22-generic 2.6.35.2
>   Uname: Linux 2.6.35-16-generic x86_64
>   Architecture: amd64
>   Date: Fri Aug 20 14:19:14 2010
>   ExecutablePath: /usr/lib/telepathy/mission-control-5
>   ProcCmdline: /usr/lib/telepathy/mission-control-5
>   ProcEnviron:
>    SHELL=/bin/bash
>    PATH=(custom, no user)
>    LANG=en_US.utf8
>   SegvAnalysis:
>    Segfault happened at: 0x40eb70:      mov    0x18(%rdi),%rdi
>    PC (0x0040eb70) 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/libc.so.6
>    ?? ()
>    ?? ()
>   Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
>   UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
> powerdev pulse pulse-access sambashare scanner video
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/621048/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/621048

Title:
  mission-control-5 crashed with SIGSEGV in __libc_start_main()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/621048/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to