Version: (using KDE KDE 3.5.0) Installed from: Compiled From Sources Compiler: gcc version 3.4.4 OS: Linux Easy to reproduce, as long as konqueror preloading is enabled like it is by default media:/ Click a device, mount Open Medium System Folder Close the window that opens Unmount device, can't, it's busy. The other konqueror instance stays loaded but not visible, and you cannot unmount the device until you kill the PID.
i hope this can be fixed for KDE 3.5.1?!? a bummer for newbies, for sure, even for many advanced users... (like the error you get when you try to unmount a device you just mounted but which isn't in the fstab)
(no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1500391744 (LWP 4151)] [KCrash handler] #4 0xa686feb5 in ZipArch::unarchFileInternal () from /usr/kde/3.5/lib/kde3/libarkpart.so #5 0xa687b84f in Arch::slotExtractExited () from /usr/kde/3.5/lib/kde3/libarkpart.so #6 0xa687bba6 in Arch::qt_invoke () from /usr/kde/3.5/lib/kde3/libarkpart.so #7 0xa686e7bb in ZipArch::qt_invoke () from /usr/kde/3.5/lib/kde3/libarkpart.so #8 0xa70a8c84 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #9 0xa7709e3d in KProcess::processExited () from /usr/kde/3.5/lib/libkdecore.so.4 #10 0xa7709eac in KProcess::processHasExited () from /usr/kde/3.5/lib/libkdecore.so.4 #11 0xa770d5fc in KProcessController::slotDoHousekeeping () from /usr/kde/3.5/lib/libkdecore.so.4 #12 0xa770d668 in KProcessController::qt_invoke () from /usr/kde/3.5/lib/libkdecore.so.4 #13 0xa70a8c84 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #14 0xa70a924a in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #15 0xa73fd8e0 in QSocketNotifier::activated () from /usr/qt/3/lib/libqt-mt.so.3 #16 0xa70c595f in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3 #17 0xa70448ff in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 #18 0xa7044a9c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 #19 0xa76be856 in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4 #20 0xa7037ce3 in QEventLoop::activateSocketNotifiers () from /usr/qt/3/lib/libqt-mt.so.3 #21 0xa6fef0cd in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 #22 0xa705b080 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 #23 0xa705afd6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 #24 0xa7043a1f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 #25 0xa7f09b8f in kdemain () from /usr/kde/3.5/lib/libkdeinit_ark.so #26 0x080486ce in ?? () #27 0x00000001 in ?? () #28 0xaff2eb74 in ?? () #29 0x080497cc in ?? () #30 0xa6a32ff4 in ?? () from /lib/tls/libc.so.6 #31 0x00000000 in ?? () #32 0xa7f30ca0 in ?? () from /lib/ld-linux.so.2 #33 0xaff2eb48 in ?? () #34 0xa6934f31 in __libc_start_main () from /lib/tls/libc.so.6 #35 0xa6934f31 in __libc_start_main () from /lib/tls/libc.so.6 #36 0x08048611 in ?? ()
What is this backtrace for?
Sorry, it was supposed to be for bug 119056. It can be ignored.
First, this bug doesn't belong to kio/media IMO. From the report, the closed konqueror window would hold a file:/media/foo directory (note the "Open Medium System Folder"), not a media:/ or system:/ URL. It would be better assigned to konq, or kio/general. And second, IMHO it is an invalid... I can't reproduce it on my system. And yes, I double checked preloading is enabled. It looks like everybody is a good citizen and release everything correctly.
I just tested again. It seems to happen with my USB SD card, but not my CD. Make sure preload on KDE startup is disabled. Set # of konqs to keep preloaded to 1. Kill all instances of konqueror. Open konqueror media:/ right click device, mount browse to system folder close the window that opens now try to demount the device, in a term or konq, konq still has it open in the background and it won't let you killall konqueror Now it unmounts. /dev/sda1 /mnt/sd auto users That's my entry in my fstab, if that helps at all.
It's holding /mnt/sd, as far as I can tell. If I don't click browse to system folder, it's fine. It also does it if I put in /mnt/sd manually and close out konq.
Also, the problem goes away if you set it to keep 0 konq's preloaded. As to why it only happens with my thumbdrive, that's pretty weird, but it is konqueror/preloading related.
*** This bug has been marked as a duplicate of 75202 ***