Bug 133298

Summary:	Crash when returning from Storage Media
Product:	[Unmaintained] systemsettings-kde3	Reporter:	jg
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	andresbajotierra, info
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jg 2006-08-30 22:44:24 UTC

Version:            (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
OS:                Linux

Reproducable

Assumptions: System Settings -> Storage Media "Advanced" tab has "Enable medium application autostart after mount" ticked.


1) Open "System Settings"

2) Click "Storage Media" button

3) Click "Advanced" tab

4) Untick "Enable medium application autostart after mount"

5) Click the Blue left arrow "Show All" at the top left of the window.

6) View the crash. Occured 2/2.

Backtrace

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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 -1231333696 (LWP 7740)]
(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)
(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)
[KCrash handler]
#6  0xb7256b3e in QGDict::unlink_int () from /usr/lib/libqt-mt.so.3
#7  0xb7256bfe in QGDict::take_int () from /usr/lib/libqt-mt.so.3
#8  0xb66a6c66 in DBusQt::Internal::Integrator::removeWatch ()
   from /usr/lib/libdbus-qt-1.so.1
#9  0xb66a6ccc in DBusQt::Internal::dbusRemoveWatch ()
   from /usr/lib/libdbus-qt-1.so.1
#10 0xb66d3318 in dbus_watch_handle () from /usr/lib/libdbus-1.so.2
#11 0xb66d089f in dbus_watch_set_data () from /usr/lib/libdbus-1.so.2
#12 0xb66b9028 in dbus_connection_set_watch_functions ()
   from /usr/lib/libdbus-1.so.2
#13 0xb66a7b32 in DBusQt::Internal::Integrator::Integrator ()
   from /usr/lib/libdbus-qt-1.so.1
#14 0xb66a5ad0 in DBusQt::Connection::Private::setConnection ()
   from /usr/lib/libdbus-qt-1.so.1
#15 0xb66a6143 in DBusQt::Connection::dbus_connection_setup_with_qt_main ()
   from /usr/lib/libdbus-qt-1.so.1
#16 0xb6728336 in HALBackend::MainLoopIntegration ()
   from /usr/lib/kde3/kded_mediamanager.so
#17 0xb672b532 in HALBackend::InitHal ()
   from /usr/lib/kde3/kded_mediamanager.so
#18 0xb671beca in MediaManager::loadBackends ()
   from /usr/lib/kde3/kded_mediamanager.so
#19 0xb671c22f in MediaManager::qt_invoke ()
   from /usr/lib/kde3/kded_mediamanager.so
#20 0xb6f59eb9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0xb72ed29a in QSignal::signal () from /usr/lib/libqt-mt.so.3
#22 0xb6f77630 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#23 0xb6f7f120 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#24 0xb6eefe56 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#25 0xb6ef0052 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#26 0xb7697d7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#27 0xb6e81157 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#28 0xb6ee1843 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#29 0xb6e94f67 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#30 0xb6f08947 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#31 0xb6f0886a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#32 0xb6eee965 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#33 0xb7fb9450 in kdemain () from /usr/lib/libkdeinit_kded.so
#34 0xb7d90ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x080483b1 in ?? ()

Comment 1 jg 2006-08-30 23:36:51 UTC

The KDE crash handler is not very clear, it seems the actual application which crashed was: KDE Daemon (kded) SIGSEGV  Why dont they put this info at the top of the backtrace log!?

So perhaps this should be set to the kded package instead of systemsettings?
 
JG

Comment 2 Andreas Kling 2006-08-31 10:02:30 UTC

Perhaps this is fixed by rev 566466. Is your D-BUS daemon running when you do this? Could you try this on the current 3.5 branch?

Comment 3 jg 2006-08-31 14:32:17 UTC

Hi Andreas,

Thanks for your reply.

Yes, D-BUS seems to be running. Below is the process info. Unfortunately I'm too short of time to upgrade for the forseeable future unless the Kubuntu guys put out the updates.  If it is most likely fixed by your change (I cant see it as http://www.commit-digest.org/issues/2006-07-30/moreinfo/566466/ is down) should we mark this as RESOLVED?

Kind regards
Jon

104       4201  0.0  0.0   2188   808 ?        Ss   13:00   0:00 /usr/bin/dbus-daemon --system
now3d     4903  0.0  0.0   4332   692 ?        Ss   13:00   0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager
now3d     4906  0.0  0.0   2708   640 ?        S    13:00   0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
now3d     4907  0.0  0.0   2076   420 ?        Ss   13:00   0:00 dbus-daemon --fork --print-pid 8 --print-address 6 --session

Comment 4 Dario Andres 2009-10-02 03:39:02 UTC

HAL, and Qt-Dbus changed a lot (HAL integration is now part of Solid, Dbus is now integrated inside Qt4). Closing as WORKSFORME. KDE3 is not going to get a new release.
If KDE4 is still crashing in some similar place, please file a new bug report.
Regards