Version: (using KDE KDE 3.1.93) Installed from: Compiled From Sources In some applications, the file open dialog crashes on accessing a device through the kio devices protocol. Some applications that do crash: JuK, Find Files And some applications that don't: kwrite, konqueror, kate The application crashes when I do the following: I open the application, and open the Open File dialog (or equivalent), and go to the devices directory using the shortcut on the left. I click on a mounted device (in my case the hard disk hdd8) and *poof* the application is gone. Clicking on an unmounted device (my CD-Rom is the only unmounted device) disk doesn't seem to crash. Unfortunately I can't tell whether it crashes after the mounting, because my user isn't allowed to do that (I could change that if that would be required to track this down). The backtrace from the crash handler: (a lot of no debugging symbols found) (no debugging symbols found)...0x41853a66 in waitpid () from /lib/libpthread.so.0 #0 0x41853a66 in waitpid () from /lib/libpthread.so.0 #1 0x40e9c784 in KCrash::defaultCrashHandler(int) () from /home/kdetest/kde3.2-beta1/lib/libkdecore.so.4 #2 0x41852695 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x40a3a973 in KFileTreeBranch::addItems(QPtrList<KFileItem> const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #5 0x40a3df69 in KFileTreeBranch::qt_invoke(int, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #6 0x41273cac in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #7 0x409588fd in KDirLister::newItems(QPtrList<KFileItem> const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #8 0x4095799b in KDirLister::emitItems() () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #9 0x4094e33b in KDirListerCache::slotEntries(KIO::Job*, QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #10 0x40959610 in KDirListerCache::qt_invoke(int, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #11 0x41273cac in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #12 0x408a4f94 in KIO::ListJob::entries(KIO::Job*, QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #13 0x408956e3 in KIO::ListJob::slotListEntries(QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #14 0x408a5232 in KIO::ListJob::qt_invoke(int, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #15 0x41273cac in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #16 0x408817dd in KIO::SlaveInterface::listEntries(QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #17 0x4087e858 in KIO::SlaveInterface::dispatch(int, QMemArray<char> const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #18 0x4087d940 in KIO::SlaveInterface::dispatch() () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #19 0x4087a928 in KIO::Slave::gotInput() () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #20 0x4087d0a8 in KIO::Slave::qt_invoke(int, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #21 0x41273cac in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #22 0x41273e0d in QObject::activate_signal(int, int) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #23 0x41592232 in QSocketNotifier::activated(int) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #24 0x4128fc30 in QSocketNotifier::event(QEvent*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #25 0x412184df in QApplication::internalNotify(QObject*, QEvent*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #26 0x41217aeb in QApplication::notify(QObject*, QEvent*) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #27 0x40e039ff in KApplication::notify(QObject*, QEvent*) () from /home/kdetest/kde3.2-beta1/lib/libkdecore.so.4 #28 0x4120821a in QEventLoop::activateSocketNotifiers() () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #29 0x411c56b8 in QEventLoop::processEvents(unsigned) () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #30 0x4122bcc8 in QEventLoop::enterLoop() () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #31 0x41218791 in QApplication::enter_loop() () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #32 0x413f4310 in QDialog::exec() () from /home/kdetest/kde3.2-beta1/lib/libqt-mt.so.3 #33 0x40a408cb in KDirSelectDialog::selectDirectory(QString const&, bool, QWidget*, QString const&) () from /home/kdetest/kde3.2-beta1/lib/libkio.so.4 #34 0x080d435c in static_QUType_QString () #35 0x00000001 in ?? () Unfortunately no line numbers, sorry for that. I hope this provides enough information to track this crash down. PS: Since it seems to crash explicitly on the devices protocol, I placed the report here.
Confirmed with KFind.
Confirmed as well with current CVS.
*** Bug 73393 has been marked as a duplicate of this bug. ***
*** Bug 78762 has been marked as a duplicate of this bug. ***
*** Bug 81189 has been marked as a duplicate of this bug. ***
*** Bug 78599 has been marked as a duplicate of this bug. ***
KFileTreeView doesn't handle the redirections of the lan:/ and devices:/ URLs correctly. Fixed the crashes and disabled lan:/ + devices:/ for KDE 3.3 Needs some major design changes for KDE 4 and combination with sidebar and konqueror listview treeviews to remove the code duplication.
Suse 9.1 Pro I installed 3.3.1 last week. I noticed this bug yesterday when I tryed to boot up into root. Got the following message: Could not start process unable to create io-slave Klauncher said: unknown protocol 'devices' I found configure desktop behavior device icon turned on cause message. Was not seeing it under un user account since device icons was turned off for the desktop. I did install Kbear yesterday before noticing this problem. Kbear does work but seems to effect the task bar sizing. I am new to Linux so I need to find out how to do a back trace if you need additional information. Simular to bug 67737
Is the bug I mentioned on 10-20-04 ever going to be fixed? I am now on KDE 3.3.2 Level"a" and still hve this problem. It also occurs as a user if the device icons are turned on in the control center (Desktop/Behavior Device Icons tab. I cannot see my windows partitions from the desktop as root, and only from my computer as user.
*** Bug 97138 has been marked as a duplicate of this bug. ***
Not sure if the bug still exist. But it does, it is now a media: KIO slave problem.
Hmm, can't reproduce it anymore in the current 3.5 branch. On the other hand, by looking at the comments it seems to be linked to redirection not devices:/ or media:/ themselves. Hence why I keep it open and reassign to kio general.
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
It look that it have been a loong time since someone could confirm it. Should we do something about it?
On KDE 4 the problem is not reproducible. Moreover I'm not able to reproduce it on KDE 3.5.10 too. Are KIO developers still fixing/mantaining KDE 3 code?
Nope.
@David: does have any sense to do a bugday for triaging old kio bugs?