Bug 211466 - kbluetooth4-devicemanager failed on start
Summary: kbluetooth4-devicemanager failed on start
Status: RESOLVED FIXED
Alias: None
Product: kbluetooth
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.4
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Tom Patzig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 19:27 UTC by Eugene Alekseev
Modified: 2010-04-15 01:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (3.17 KB, text/plain)
2010-04-15 01:06 UTC, Germano Massullo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Alekseev 2009-10-22 19:27:58 UTC
Application that crashed: kbluetooth4-devicemanager
Version of the application: 0.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30.8-64.fc11.i686.PAE i686
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
Each time when I start kbluetooth4-devicemanager, it gives out the given error message. Service "bluetooth" during this moment it is started and started "kbluetooth4".

Excuse me for bad English

 -- Backtrace:
Application: KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4-devicemanager), signal: Aborted
[KCrash Handler]
#6  0x00639416 in __kernel_vsyscall ()
#7  0x0475e7c1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0x04760092 in *__GI_abort () at abort.c:88
#9  0x0336b555 in _dbus_abort () at dbus-sysdeps.c:88
#10 0x03366ee6 in _dbus_warn_check_failed (
    format=0x33744a0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283
#11 0x0335aef4 in dbus_message_new_method_call (destination=0x8ac55f0 "org.bluez", path=0x0, interface=0x8abea80 "org.freedesktop.DBus.Introspectable", method=0x8ac55b8 "Introspect")
    at dbus-message.c:1071
#12 0x00ec2c93 in q_dbus_message_new_method_call (method=<value optimized out>, interface=<value optimized out>, path=<value optimized out>, bus_name=<value optimized out>) at ./qdbus_symbols_p.h:260
#13 QDBusMessagePrivate::toDBusMessage (method=<value optimized out>, interface=<value optimized out>, path=<value optimized out>, bus_name=<value optimized out>) at qdbusmessage.cpp:112
#14 0x00ebf7d8 in QDBusConnectionPrivate::sendWithReply (this=0x8ac2460, message=@0xbfb444dc, sendMode=1, timeout=-1) at qdbusintegrator.cpp:1746
#15 0x00ec05f2 in QDBusConnectionPrivate::findMetaObject (this=0x8ac2460, service=@0x8ac5850, path=@0x8ac5858, interface=@0x8ac585c, error=@0x8ac5860) at qdbusintegrator.cpp:2108
#16 0x00ecaf3f in QDBusInterfacePrivate::QDBusInterfacePrivate (this=0x8ac5808, serv=@0xbfb445ec, p=@0xbfb448f8, iface=@0xbfb445e8, con=@0xbfb445e4) at qdbusinterface.cpp:60
#17 0x00ecb03f in QDBusInterface::QDBusInterface(const QString &, const QString &, const QString &, const QDBusConnection &, struct QObject *) (this=0x8abe198, service=@0xbfb445ec, path=@0xbfb448f8, 
    interface=@0xbfb445e8, connection=@0xbfb445e4, parent=0x0) at qdbusinterface.cpp:121
#18 0x01b98a9f in BluezBluetoothInterface::BluezBluetoothInterface(QString const&) () from /usr/lib/kde4/solid_bluez.so
#19 0x01b931ae in BluezBluetoothManager::createInterface(QString const&) () from /usr/lib/kde4/solid_bluez.so
#20 0x00e32bf4 in ?? () from /usr/lib/libsolidcontrol.so.4
#21 0x00e336aa in Solid::Control::BluetoothManager::findBluetoothInterface(QString const&) const () from /usr/lib/libsolidcontrol.so.4
#22 0x00e2fac2 in Solid::Control::BluetoothInterface::BluetoothInterface(QString const&) () from /usr/lib/libsolidcontrol.so.4
#23 0x0804ebd9 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-22 23:27:02 UTC
@Alex: is this application "kbluetooth4-devicemanager" a new binary ?
Comment 2 Alex Fiestas 2009-11-04 16:51:38 UTC
No, is an old one part of the old "KDE bluetooth framework". 
Anyway it should be fixed in the 0.4 version.
Comment 3 Alex Fiestas 2009-11-06 00:45:06 UTC
Ok, after try to reproduce this bug unsuccessfully in 5 different environments I think that I can set this bug as fixed as it should.

Anyway use version 0.1 is a crazy thing, please tell to your distribution to upgrade the kbluetooth package.
Comment 4 Germano Massullo 2010-04-15 01:06:02 UTC
Created attachment 42794 [details]
New crash information added by DrKonqi

Everytime I try to open kbluetooth, the program fails to open and gives me back the backtrace