Bug 233755 - Kmix crashes after resuming from hibernate
Summary: Kmix crashes after resuming from hibernate
Status: RESOLVED WORKSFORME
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-04-08 18:16 UTC by Luis Motta Campos
Modified: 2018-10-21 04:56 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luis Motta Campos 2010-04-08 18:16:47 UTC
Application that crashed: kmix
Version of the application: 3.5
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-generic-pae i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: KMix (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb32cd92b in ?? () from /usr/lib/libkdeinit4_kmix.so
#7  0xb32ce7b5 in ?? () from /usr/lib/libkdeinit4_kmix.so
#8  0xb7622263 in QMetaObject::activate (sender=0x9be3a78, from_signal_index=5, to_signal_index=5, argv=0xbfec7c38) at kernel/qobject.cpp:3113
#9  0xb7622ec2 in QMetaObject::activate (sender=0x9be3a78, m=0xb3309b24, local_signal_index=1, argv=0xbfec7c38) at kernel/qobject.cpp:3187
#10 0xb32f71d3 in ?? () from /usr/lib/libkdeinit4_kmix.so
#11 0xb32f72db in ?? () from /usr/lib/libkdeinit4_kmix.so
#12 0xb32f84bf in ?? () from /usr/lib/libkdeinit4_kmix.so
#13 0xb7622263 in QMetaObject::activate (sender=0x9bd1720, from_signal_index=5, to_signal_index=5, argv=0xbfec7d98) at kernel/qobject.cpp:3113
#14 0xb7622ec2 in QMetaObject::activate (sender=0x9bd1720, m=0xb5b587c8, local_signal_index=1, argv=0xbfec7d98) at kernel/qobject.cpp:3187
#15 0xb5b047e3 in Solid::DeviceNotifier::deviceRemoved (this=0x9bd1720, _t1=...) at ./devicenotifier.moc:88
#16 0xb5b0661c in Solid::DeviceManagerPrivate::_k_deviceRemoved (this=0x9bd1720, udi=...) at ../../../solid/solid/devicemanager.cpp:186
#17 0xb5b06a75 in Solid::DeviceManagerPrivate::qt_metacall (this=0x9bd1720, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfec7f38) at ./devicemanager_p.moc:74
#18 0xb7622263 in QMetaObject::activate (sender=0x9bd2c68, from_signal_index=5, to_signal_index=5, argv=0xbfec7f38) at kernel/qobject.cpp:3113
#19 0xb7622ec2 in QMetaObject::activate (sender=0x9bd2c68, m=0xb5b59878, local_signal_index=1, argv=0xbfec7f38) at kernel/qobject.cpp:3187
#20 0xb5b19203 in Solid::Ifaces::DeviceManager::deviceRemoved (this=0x9bd2c68, _t1=...) at ./ifaces/devicemanager.moc:88
#21 0xb5b3e432 in Solid::Backends::Hal::HalManager::slotDeviceRemoved (this=0x9bd2c68, udi=...) at ../../../solid/solid/backends/hal/halmanager.cpp:219
#22 0xb5b3e51a in Solid::Backends::Hal::HalManager::qt_metacall (this=0x9bd2c68, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfec810c) at ./backends/hal/halmanager.moc:72
#23 0xb5c887b4 in QDBusConnectionPrivate::deliverCall (this=0x9bd2c78, object=0x9bd2c68, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:891
#24 0xb5c90197 in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib/libQtDBus.so.4
#25 0xb761c5fe in QObject::event (this=0x9bd2c68, e=0x9d5fef0) at kernel/qobject.cpp:1111
#26 0xb6285f54 in QApplicationPrivate::notify_helper (this=0x9b19238, receiver=0x9bd2c68, e=0x9d5fef0) at kernel/qapplication.cpp:4056
#27 0xb628d67c in QApplication::notify (this=0x9b18210, receiver=0x9bd2c68, e=0x9d5fef0) at kernel/qapplication.cpp:3603
#28 0xb6cd5bfa in KApplication::notify (this=0x9b18210, receiver=0x9bd2c68, event=0x9d5fef0) at ../../kdeui/kernel/kapplication.cpp:302
#29 0xb760c6cb in QCoreApplication::notifyInternal (this=0x9b18210, receiver=0x9bd2c68, event=0x9d5fef0) at kernel/qcoreapplication.cpp:610
#30 0xb760d2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9a8be48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9a8be48) at kernel/qcoreapplication.cpp:1247
#32 0xb760d47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#33 0xb76373ff in QCoreApplication::sendPostedEvents (s=0x9b1b310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#34 postEventSourceDispatch (s=0x9b1b310) at kernel/qeventdispatcher_glib.cpp:210
#35 0xb5e89e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#36 0xb5e8d730 in ?? () from /lib/libglib-2.0.so.0
#37 0xb5e8d863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#38 0xb763702c in QEventDispatcherGlib::processEvents (this=0x9a8da58, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#39 0xb6326be5 in QGuiEventDispatcherGlib::processEvents (this=0x9a8da58, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#40 0xb760ac79 in QEventLoop::processEvents (this=0xbfec8874, flags=) at kernel/qeventloop.cpp:149
#41 0xb760b0ca in QEventLoop::exec (this=0xbfec8874, flags=...) at kernel/qeventloop.cpp:201
#42 0xb760d53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#43 0xb6285dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#44 0xb32cafe3 in kdemain () from /usr/lib/libkdeinit4_kmix.so
#45 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x9add486 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x80511a5 "0") at ../../kinit/kinit.cpp:677
#46 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#47 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#48 0x0804fbaf in main (argc=2, argv=0xbfec9154, envp=0xbfec9160) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2010-04-08 18:35:53 UTC
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdemultimedia-dbg" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks
Comment 2 Luis Motta Campos 2010-04-08 20:00:30 UTC
Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=233755
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |andresbajotierra@gmail.com
>          Resolution|                            |BACKTRACE
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2010-04-08 18:35:53 ---
> - If you can reproduce the crash at will (or you experience this regularly),
> can you install the "kdemultimedia-dbg" package and post a complete backtrace
> here? (you can get more information at
> http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting )
> Thanks
> 

I experience this regularly, but I cannot reproduce it at will. I was
not able to determine which package contained debugging symbols for
kmix, so I didn't install it before.

I will post more information to this bug as soon as I get it happening
again.

Thank you for your time and attention, Dario.
Comment 3 Andrew Crouthamel 2018-09-20 22:02:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:56:03 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!