Bug 188690 - KBluetooth4 crashes on suspend/resume
Summary: KBluetooth4 crashes on suspend/resume
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde-bluetooth
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Tom Patzig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 23:12 UTC by erpo41
Modified: 2009-11-04 17:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description erpo41 2009-04-02 23:12:18 UTC
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Ubuntu Packages

I'm using the http://ppa.launchpad.net/kubuntu-experimental/ubuntu repository for Ubuntu 8.10.

When I log into a KDE session and suspend (i.e. suspend to RAM) the computer, it appears to suspend normally. When I resume the computer, I see a notice that KBluetooth4 has segfaulted. My bluetooth mouse continues to function anyway. Here is the stack trace:



This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f3f025f06f0 (LWP 6641)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00007f3efe9986b0 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 6641)]

Thread 1 (Thread 0x7f3f025f06f0 (LWP 6641)):
#0  0x00007f3efe9986b0 in nanosleep () from /lib/libc.so.6
#1  0x00007f3efe998507 in sleep () from /lib/libc.so.6
#2  0x00007f3f01bcedff in ?? () from /usr/lib/libkdeui.so.5
#3  0x00007f3f01bcf70a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0x00007f3efec5dab0 in ?? () from /lib/libc.so.6
#6  0x00007f3f000c6cc7 in QObject::property () from /usr/lib/libQtCore.so.4
#7  0x00007f3f003c3d5e in ?? () from /usr/lib/libQtDBus.so.4
#8  0x00007f3f003c4791 in ?? () from /usr/lib/libQtDBus.so.4
#9  0x00007f3f003c4aa8 in ?? () from /usr/lib/libQtDBus.so.4
#10 0x00007f3f000c3da5 in QObject::event () from /usr/lib/libQtCore.so.4
#11 0x00007f3eff5dc34a in QApplication::event () from /usr/lib/libQtGui.so.4
#12 0x00007f3eff5d6c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#13 0x00007f3eff5de9ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0x00007f3f01b6971b in KApplication::notify () from /usr/lib/libkdeui.so.5
#15 0x00007f3f000b4d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#16 0x00007f3f000b59fa in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#17 0x00007f3f000dd4d3 in ?? () from /usr/lib/libQtCore.so.4
#18 0x00007f3efb5bad5b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f3efb5be52d in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f3efb5be6eb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f3f000dd15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#22 0x00007f3eff668a6f in ?? () from /usr/lib/libQtGui.so.4
#23 0x00007f3f000b3682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0x00007f3f000b380d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0x00007f3f003c6f5d in ?? () from /usr/lib/libQtDBus.so.4
#26 0x00007f3f003b1933 in QDBusConnection::call () from /usr/lib/libQtDBus.so.4
#27 0x00007f3f003cfd5f in QDBusAbstractInterface::callWithArgumentList () from /usr/lib/libQtDBus.so.4
#28 0x00007f3f003d1aac in QDBusAbstractInterface::call () from /usr/lib/libQtDBus.so.4
#29 0x0000000000420e8e in _start ()
#0  0x00007f3efe9986b0 in nanosleep () from /lib/libc.so.6
Comment 1 Juha Tukkinen 2009-04-07 18:31:38 UTC
Same behavior with Thinkpad T60 running also Kubuntu 8.10 with same PPA repository. No external bluetooth devices in use.
Comment 2 Marek 2009-04-21 17:20:28 UTC
I also suffer a similar crash. When resuming from "suspend to ram" in Kubuntu 9.04 RC, KBluetooth4 consistently produces the following error:

"""
A Fatal Error Occurred
The application KBluetooth4 - The KDE4 Bluetooth Framework (kbluetooth4) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.
"""

There is a "details" expansion, which unfortunately says only:

"""
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
"""

The error can be reproduced by first suspending to ram and then resuming, it then produces the crash report.

The KBluetooth4 applet, version 0.3 KDE 4.2.2, is running when this happens, and continues to run even after the SIGSEGV report. 

I don't know what other relevant information to post for the developers. If a developer leaves a comment as to what else is needed I will happily post the information.
Comment 3 kaido kert 2009-05-05 08:38:00 UTC
Im getting the same thing. Disabled the KDE crash handler and enabled core dumps, this is the backtrace that i got, culprit appears to be 
	session->call(QDBus::BlockWithGui, "Stop");
at obexserver.cpp:100. DBUS connection is prolly somehow dropped during suspend or something.

#0  0x00000000 in ?? ()                                                                                                                        
(gdb) thread apply all bt

Thread 1 (process 11910):
#0  0x00000000 in ?? ()  
#1  0xb74cec43 in QDBusConnectionPrivate::activateCall (this=0x8a57720, object=0x8aaa1b8, flags=273, msg=@0x8aa8f50) at qdbusintegrator.cpp:753
#2  0xb74cf501 in QDBusConnectionPrivate::activateObject (this=0x8a57720, node=@0x8aa8f3c, msg=@0x8aa8f50, pathStartPos=18) at qdbusintegrator.cpp:1375
#3  0xb74cf9fa in QDBusActivateObjectEvent::placeMetaCall (this=0x8aa8f10) at qdbusintegrator.cpp:1469                                                 
#4  0xb73c53a0 in QObject::event (this=0xbfa39370, e=0x8aa8f10) at kernel/qobject.cpp:1118                                                             
#5  0xb73b43db in QCoreApplication::event (this=0xbfa39370, e=0x8aa8f10) at kernel/qcoreapplication.cpp:1426                                           
#6  0xb69bf409 in QApplication::event (this=0xbfa39370, e=0x8aa8f10) at kernel/qapplication.cpp:2334                                                   
#7  0xb69bbf2c in QApplicationPrivate::notify_helper (this=0x89d2630, receiver=0xbfa39370, e=0x8aa8f10) at kernel/qapplication.cpp:4084                
#8  0xb69c422e in QApplication::notify (this=0xbfa39370, receiver=0xbfa39370, e=0x8aa8f10) at kernel/qapplication.cpp:3631                             
#9  0xb7bdb95d in KApplication::notify (this=0xbfa39370, receiver=0xbfa39370, event=0x8aa8f10) at /usr/src/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#10 0xb73b4a3b in QCoreApplication::notifyInternal (this=0xbfa39370, receiver=0xbfa39370, event=0x8aa8f10) at kernel/qcoreapplication.cpp:602              
#11 0xb73b5695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89b3b38)                                                   
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213                                                                                
#12 0xb73b588d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132                                      
#13 0xb73e07ef in postEventSourceDispatch (s=0x89d4710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218                            
#14 0xb62d5b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0                                                                                
#15 0xb62d90eb in ?? () from /usr/lib/libglib-2.0.so.0                                                                                                     
#16 0xb62d9268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0                                                                               
#17 0xb73e0438 in QEventDispatcherGlib::processEvents (this=0x89ce388, flags={i = -1079803208}) at kernel/qeventdispatcher_glib.cpp:323                    
#18 0xb6a5d3f5 in QGuiEventDispatcherGlib::processEvents (this=0x89ce388, flags={i = -1079803160}) at kernel/qguieventdispatcher_glib.cpp:202              
#19 0xb73b306a in QEventLoop::processEvents (this=0xbfa383e8, flags={i = -1079803096}) at kernel/qeventloop.cpp:149
#20 0xb73b34aa in QEventLoop::exec (this=0xbfa383e8, flags={i = -1079802876}) at kernel/qeventloop.cpp:200
#21 0xb74d299c in QDBusConnectionPrivate::sendWithReply (this=0x8ab8b50, message=@0xbfa38558, sendMode=<value optimized out>, timeout=-1) at qdbusintegrator.cpp:1787
#22 0xb74bc551 in QDBusConnection::call (this=0x8a385dc, message=@0xbfa38558, mode=QDBus::BlockWithGui, timeout=-1) at qdbusconnection.cpp:516
#23 0xb74daf3b in QDBusAbstractInterface::callWithArgumentList (this=0x8acabf0, mode=QDBus::BlockWithGui, method=@0xbfa38704, args=@0xbfa38638)
    at qdbusabstractinterface.cpp:402
#24 0xb74dee8d in QDBusAbstractInterface::call (this=0x8acabf0, mode=QDBus::BlockWithGui, method=@0xbfa38704, arg1=@0xbfa386ec, arg2=@0xbfa386e0, arg3=@0xbfa386d4,
    arg4=@0xbfa386c8, arg5=@0xbfa386bc, arg6=@0xbfa386b0, arg7=@0xbfa386a4, arg8=@0xbfa38698) at qdbusabstractinterface.cpp:655
#25 0x08066ce3 in ObexServer::stop (this=0x8ac7a30) at /usr/src/kdebluetooth-0.3/src/obexserver/obexserver.cpp:100
#26 0x080556f8 in KBlueTray::offlineMode (this=0xbfa392d4) at /usr/src/kdebluetooth-0.3/src/trayicon.cpp:239
#27 0x08058e61 in KBlueTray::adapterRemoved (this=0xbfa392d4, ubi=@0xbfa38a10) at /usr/src/kdebluetooth-0.3/src/trayicon.cpp:294
#28 0x080510f0 in KBlueTray::qt_metacall (this=0xbfa392d4, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfa3889c)
    at /usr/src/kdebluetooth-0.3/obj-i486-linux-gnu/src/moc_trayicon.cpp:142
#29 0xb73caca8 in QMetaObject::activate (sender=0x8a61128, from_signal_index=5, to_signal_index=5, argv=0xbfa3889c) at kernel/qobject.cpp:3069
#30 0xb73cb932 in QMetaObject::activate (sender=0x8a61128, m=0xb7927ac8, local_signal_index=1, argv=0xbfa3889c) at kernel/qobject.cpp:3143
#31 0xb791bff3 in Solid::Control::BluetoothManager::interfaceRemoved () from /usr/lib/libsolidcontrol.so.4
#32 0xb791c302 in ?? () from /usr/lib/libsolidcontrol.so.4
#33 0xb791dc15 in Solid::Control::BluetoothManager::qt_metacall () from /usr/lib/libsolidcontrol.so.4
#34 0xb73caca8 in QMetaObject::activate (sender=0x8a84368, from_signal_index=5, to_signal_index=5, argv=0xbfa389cc) at kernel/qobject.cpp:3069
#35 0xb73cb932 in QMetaObject::activate (sender=0x8a84368, m=0xb63b7d88, local_signal_index=1, argv=0xbfa389cc) at kernel/qobject.cpp:3143
#36 0xb63b41c3 in Solid::Control::Ifaces::BluetoothManager::interfaceRemoved () from /usr/lib/libsolidcontrolifaces.so.4
#37 0xb485386b in BluezBluetoothManager::slotDeviceRemoved () from /usr/lib/kde4/solid_bluez.so
#38 0xb4854115 in BluezBluetoothManager::qt_metacall () from /usr/lib/kde4/solid_bluez.so
---Type <return> to continue, or q <return> to quit---
#39 0xb74cdd7a in QDBusConnectionPrivate::deliverCall (this=0x8a57720, object=0x8a84368, msg=@0x8ad133c, metaTypes=@0x8ad1340, slotIdx=8) at qdbusintegrator.cpp:891
#40 0xb74d6187 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8ad1310, object=0x8a84368) at qdbusintegrator_p.h:101
#41 0xb73c53a0 in QObject::event (this=0x8a84368, e=0x8ad1310) at kernel/qobject.cpp:1118
#42 0xb69bbf2c in QApplicationPrivate::notify_helper (this=0x89d2630, receiver=0x8a84368, e=0x8ad1310) at kernel/qapplication.cpp:4084
#43 0xb69c422e in QApplication::notify (this=0xbfa39370, receiver=0x8a84368, e=0x8ad1310) at kernel/qapplication.cpp:3631
#44 0xb7bdb95d in KApplication::notify (this=0xbfa39370, receiver=0x8a84368, event=0x8ad1310) at /usr/src/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#45 0xb73b4a3b in QCoreApplication::notifyInternal (this=0xbfa39370, receiver=0x8a84368, event=0x8ad1310) at kernel/qcoreapplication.cpp:602
#46 0xb73b5695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89b3b38)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#47 0xb73b588d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132
#48 0xb73e07ef in postEventSourceDispatch (s=0x89d4710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#49 0xb62d5b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#50 0xb62d90eb in ?? () from /usr/lib/libglib-2.0.so.0
#51 0xb62d9268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#52 0xb73e0438 in QEventDispatcherGlib::processEvents (this=0x89ce388, flags={i = -1079799368}) at kernel/qeventdispatcher_glib.cpp:323
#53 0xb6a5d3f5 in QGuiEventDispatcherGlib::processEvents (this=0x89ce388, flags={i = -1079799320}) at kernel/qguieventdispatcher_glib.cpp:202
#54 0xb73b306a in QEventLoop::processEvents (this=0xbfa39260, flags={i = -1079799256}) at kernel/qeventloop.cpp:149
#55 0xb73b34aa in QEventLoop::exec (this=0xbfa39260, flags={i = -1079799192}) at kernel/qeventloop.cpp:200
#56 0xb73b5959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#57 0xb69bbda7 in QApplication::exec () at kernel/qapplication.cpp:3553
#58 0x08051a5e in main (argc=1, argv=0xbfa39474) at /usr/src/kdebluetooth-0.3/src/main.cpp:77
(gdb)
Comment 4 kaido kert 2009-05-05 22:47:22 UTC
These reports :
https://bugs.kde.org/show_bug.cgi?id=182368 
http://lists.opensuse.org/opensuse-bugs/2009-01/msg10817.html
 also point to obexserver.cpp:100 ( stop ) 

The bug is easily reproducible with suspend/resume, if needed i can attach core + symbols.
The crash on my machine happens on QObject.property() call at qdbusintegrator.cpp:753, i have no idea why.
Comment 5 Alex Fiestas 2009-09-04 12:50:45 UTC
Hi
Is this bug still reproducible? I tried but I can't :/
Comment 6 Marek 2009-09-04 14:49:37 UTC
Hi Alex,

I dont have access to my computer until 28 of Sep. because Im traveling.

If its still of any use I will update and reenable bluetooth to check
when I get back on the 28th.

On Fri, Sep 4, 2009 at 7:50 AM, Alex Fiestas<alex@eyeos.org> wrote:
> https://bugs.kde.org/show_bug.cgi?id=188690
>
>
> Alex Fiestas <alex@eyeos.org> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>                 CC|                            |alex@eyeos.org
>         Resolution|                            |WORKSFORME
>
>
>
>
> --- Comment #5 from Alex Fiestas <alex eyeos org>  2009-09-04 12:50:45 ---
> Hi
> Is this bug still reproducible? I tried but I can't :/
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are a voter for the bug.
> You are on the CC list for the bug.
>
Comment 7 kaido kert 2009-09-04 16:00:44 UTC
Yes its still reproducible for me. What can i do to give you more info ?
Comment 8 Alex Fiestas 2009-09-07 06:48:53 UTC
This bug seems to be only reproducible in kubuntu, is it? Can anybody test if this still happens in the last kubuntu alphas?

I'll try to get a test environment with kubuntu in the next days.
Comment 9 Alex Fiestas 2009-11-04 17:21:50 UTC
Well, this bug seems to not be reproducible under kubuntu 9.10 which use a different method (the official one) to launch kbluetooth.

So I'm going to set it as fixed.