XBMC crash on debian squeeze
#1
Hi,

since the latest upgrade of Debian Squeeze, XMBC (latest GIT and SVN versions, removed .xbmc) XBMC crashes right after the splash screen.

It seems to be a DBUS problem when XBMC is stopped and started again.

Last lines of logfile are:

13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.ConsoleKit on /org/freedesktop/ConsoleKit/Manager with interface org.freedesktop.ConsoleKit.Manager and method CanStop
13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.DeviceKit.Disks on /org/freedesktop/DeviceKit/Disks with interface org.freedesktop.DeviceKit.Disks and method EnumerateDevices
13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.ConsoleKit on /org/freedesktop/ConsoleKit/Manager with interface org.freedesktop.ConsoleKit.Manager and method CanStop

After restarting DBUS everything is fine till the next shutdown of XBMC.

This could be a DBUS bug or an interfacing problem.
Can anyone confirm this behavoiur ?

Regards S.
Reply
#2
we have seen it but cannot reproduce it on will. if u can, please install the symbols for the lib and PASTEBIN a backtrace
Reply
#3
Hi,

I did a backtrace - hope that helps...

http://xbmc.pastebin.com/m386b6c0c

If I stop the dbus service XBMC starts without crashing.

Best regards, S.
Reply
#4
I've installed XBMC 9.11 on ubuntu 9.10 and it crashes after the splash screen. After 10 attempts it may open , without doing anything else. Tried killing the dbus service , but the desktop disappeared. How do I do a backtrace?
Reply
#5
Use the gdb debugger for backtracing.

But I'm not sure if the developers have enough information to fix this bug.
A recent upgrade and a switch to 2.6.32.3 does not solve the problem.

SVN Revision: 26589
Reply
#6
Knete Wrote:Hi,

since the latest upgrade of Debian Squeeze, XBMC (latest GIT and SVN versions, removed .xbmc) XBMC crashes right after the splash screen.

It seems to be a DBUS problem when XBMC is stopped and started again.

Last lines of logfile are:

13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.ConsoleKit on /org/freedesktop/ConsoleKit/Manager with interface org.freedesktop.ConsoleKit.Manager and method CanStop
13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.DeviceKit.Disks on /org/freedesktop/DeviceKit/Disks with interface org.freedesktop.DeviceKit.Disks and method EnumerateDevices
13:32:18 T:3025647488 M:3256659968 DEBUG: DBus: Creating message to org.freedesktop.ConsoleKit on /org/freedesktop/ConsoleKit/Manager with interface org.freedesktop.ConsoleKit.Manager and method CanStop

After restarting DBUS everything is fine till the next shutdown of XBMC.

This could be a DBUS bug or an interfacing problem.
Can anyone confirm this behavoiur ?

Regards S.

I can confirm.

Here is gdb screenshot:

(gdb) run
Starting program: /usr/local/stow/xbmc-9.11/share/xbmc/xbmc.bin
[Thread debugging using libthread_db enabled]
[New Thread 0xb61a9b70 (LWP 4562)]
[Thread 0xb61a9b70 (LWP 4562) exited]
[New Thread 0xb2f5cb70 (LWP 4563)]
[Thread 0xb2f5cb70 (LWP 4563) exited]
[New Thread 0xb2f5cb70 (LWP 4564)]

Program received signal SIGSEGV, Segmentation fault.
0xb6b579f3 in strlen () from /lib/i686/cmov/libc.so.6
(gdb) bt
#0 0xb6b579f3 in strlen () from /lib/i686/cmov/libc.so.6
#1 0xb6e31822 in ?? () from /lib/libdbus-1.so.3
#2 0xb6e1ce1f in ?? () from /lib/libdbus-1.so.3
#3 0xb6e21c0c in dbus_message_new_method_call () from /lib/libdbus-1.so.3
#4 0x0821b194 in CDBusMessage (this=0xbfffed4c, destination=0x7e67114 <Address 0x7e67114 out of bounds>,
object=0x7e67134 <Address 0x7e67134 out of bounds>, interface=0x88d6098 "org.freedesktop.DBus.Properties", method=0x8938da8 "Get")
at DBusMessage.cpp:28
#5 0x0821a344 in CDBusUtil::GetVariant (destination=0x7e67114 <Address 0x7e67114 out of bounds>,
object=0x7e67134 <Address 0x7e67134 out of bounds>, interface=0x7e67114 <Address 0x7e67114 out of bounds>,
property=0x7e66fa4 <Address 0x7e66fa4 out of bounds>) at DBusUtil.cpp:37
#6 0x0821a5c1 in CDBusUtil::GetBoolean (destination=0x7e67114 <Address 0x7e67114 out of bounds>,
object=0x7e67134 <Address 0x7e67134 out of bounds>, interface=0x7e67114 <Address 0x7e67114 out of bounds>,
property=0x7e66fa4 <Address 0x7e66fa4 out of bounds>) at DBusUtil.cpp:26
#7 0x08219b12 in CConsoleDeviceKitPowerSyscall (this=0x95c88d0) at ConsoleDeviceKitPowerSyscall.cpp:40
#8 0x0854c03d in CPowerManager::Initialize (this=0x8aaa6f0) at PowerManager.cpp:73
#9 0x082de116 in CApplication::Initialize (this=0x8aa8f40) at Application.cpp:1319
#10 0x082db07f in CApplication::Create (this=0x8aa8f40, hWnd=0x0) at Application.cpp:741
#11 0x08506dd7 in main (argc=1, argv=0xbffff7c4) at xbmc.cpp:131
(gdb)

Addresses that are "out of bounds" are addresses of literal C strings, so I guess it is something with the compiler version, probably compiler bug. Debian/squeeze uses g++ 4.3.4.

After recompiling file xbmc/linux/ConsoleDeviceKitPowerSyscall.cpp with gcc-4.4.2 (kind of dirty hack, I know) xbmc runs well.

Any comments are welcome.
Reply
#7
und123 Wrote:I can confirm.
After recompiling file xbmc/linux/ConsoleDeviceKitPowerSyscall.cpp with gcc-4.4.2 (kind of dirty hack, I know) xbmc runs well.

Any comments are welcome.
Nice.
Reply
#8
Currently, I'm short of time and simply disabled this feature.

http://forum.xbmc.org/showpost.php?p=496...stcount=10

Has anyone tried to use an older g++ for compiling the whole code ?
Reply
#9
Any news on this problem Huh
There is any bug posted for this at xbmc developers Huh

I'm having random crashes (every time, trying any addon) using xbmc git compiled in debian squeeze.
Reply

Logout Mark Read Team Forum Stats Members Help
XBMC crash on debian squeeze0