Bug 29201 - MC dies on empathy startup, empathy does not start
Summary: MC dies on empathy startup, empathy does not start
Status: RESOLVED INVALID
Alias: None
Product: Telepathy
Classification: Unclassified
Component: mission-control (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-21 11:53 UTC by Julian Sikorski
Modified: 2010-07-21 11:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Julian Sikorski 2010-07-21 11:53:12 UTC

    
Comment 1 Julian Sikorski 2010-07-21 11:55:29 UTC
Sorry, clicked too fast. It was originally reported in Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=614991

ABRT shows the following backtrace here:
warning: core file may not match specified executable file.
[New Thread 2428]
Core was generated by `/usr/libexec/mission-control-5'.
Program terminated with signal 11, Segmentation fault.
#0  mcd_service_run (self=0x0) at mcd-service.c:195
195	mcd-service.c: No such file or directory.
	in mcd-service.c

Thread 1 (Thread 2428):
#0  mcd_service_run (self=0x0) at mcd-service.c:195
No locals.
#1  0x000000000040b9e8 in main (argc=<value optimized out>, 
    argv=<value optimized out>) at mc-server.c:81
        mcd = 0x0
From                To                  Syms Read   Shared Object Library
0x0000003856a090f0  0x0000003856a19b78  Yes         /usr/lib64/libmcclient-5.4.3.so
0x000000386ea29eb0  0x000000386eac2758  Yes         /usr/lib64/libtelepathy-glib.so.0
0x000000385d619b60  0x000000385d6812c8  Yes         /lib64/libgio-2.0.so.0.2400.1
0x000000385b601080  0x000000385b601fc8  Yes         /lib64/libgmodule-2.0.so.0.2400.1
0x0000003864e09060  0x0000003864e19878  Yes         /usr/lib64/libdbus-glib-1.so.2
0x000000385ba07090  0x000000385ba2e4c8  Yes         /lib64/libdbus-1.so.3
0x0000003856e05640  0x0000003856e10e48  Yes         /lib64/libpthread-2.12.so
0x000000385a608d20  0x000000385a632a78  Yes         /lib64/libgobject-2.0.so.0.2400.1
0x0000003859a01590  0x0000003859a029f8  Yes         /lib64/libgthread-2.0.so.0.2400.1
0x0000003857a02140  0x0000003857a055a8  Yes         /lib64/librt-2.12.so
0x000000386b006d70  0x000000386b015bd8  Yes         /usr/lib64/libgnome-keyring.so.0
0x0000003857e155c0  0x0000003857e99d58  Yes         /lib64/libglib-2.0.so.0.2400.1
0x000000385661e9a0  0x000000385672b820  Yes         /lib64/libc-2.12.so
0x0000003857200de0  0x0000003857201998  Yes         /lib64/libdl-2.12.so
0x00000038592038c0  0x0000003859212528  Yes         /lib64/libresolv-2.12.so
0x0000003857601ef0  0x000000385760d228  Yes         /lib64/libz.so.1
0x0000003858605550  0x0000003858615038  Yes         /lib64/libselinux.so.1
0x0000003856200af0  0x0000003856218904  Yes         /lib64/ld-2.12.so
0x0000003866606d00  0x0000003866650078  Yes         /lib64/libgcrypt.so.11
0x0000003865e007f0  0x0000003865e00d58  Yes         /lib64/libgpg-error.so.0
$1 = 0x0
$2 = 0x0
rax            0x0	0
rbx            0x0	0
rcx            0x33	51
rdx            0x20c30a0	34353312
rsi            0x20d4400	34423808
rdi            0x0	0
rbp            0x0	0x0
rsp            0x7fff05893ae8	0x7fff05893ae8
r8             0x10	16
r9             0x0	0
r10            0xa0	160
r11            0x1	1
r12            0x40b860	4241504
r13            0x7fff05893bd0	140733286267856
r14            0x0	0
r15            0x0	0
rip            0x40ba50	0x40ba50 <mcd_service_run>
eflags         0x10206	[ PF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x0	0
gs             0x0	0
Dump of assembler code for function mcd_service_run:
=> 0x000000000040ba50 <+0>:	mov    0x18(%rdi),%rdi
   0x000000000040ba54 <+4>:	jmpq   0x40b6a8 <g_main_loop_run@plt>
End of assembler dump.
Comment 2 Julian Sikorski 2010-07-21 11:57:14 UTC
Looks like it was a SELinux issue. Sorry for the noise.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.