Version: 2.0 (using KDE 3.2.0 RC1, compiled sources) Compiler: gcc version 3.3.2 (Debian) OS: Linux (i686) release 2.6.0-test11 This may be a general kdelibs bug if the folder selection dialog is part of kdelibs and not juk specifically. When using the folder selection dialog to add a new folder to Juk's folder list, going to devices:/ and clicking on any of my hard drive partitions causes Juk to crash. Here's a backtrace: [New Thread 1101601504 (LWP 6365)] 0x418b030e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #0 0x418b030e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #1 0x40d6dab4 in KCrash::defaultCrashHandler(int) () from /home/jdarpinian/kde3.2-rc/lib/libkdecore.so.4 #2 <signal handler called> #3 0x4090dac3 in KFileTreeBranch::addItems(QPtrList<KFileItem> const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #4 0x409112f9 in KFileTreeBranch::qt_invoke(int, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #5 0x4114852c in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #6 0x4082afbd in KDirLister::newItems(QPtrList<KFileItem> const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #7 0x4082a05b in KDirLister::emitItems() () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #8 0x40820a6b in KDirListerCache::slotEntries(KIO::Job*, QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #9 0x4082bcd0 in KDirListerCache::qt_invoke(int, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #10 0x4114852c in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #11 0x40778cd4 in KIO::ListJob::entries(KIO::Job*, QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #12 0x40768533 in KIO::ListJob::slotListEntries(QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #13 0x40778f89 in KIO::ListJob::qt_invoke(int, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #14 0x4114852c in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #15 0x407540bd in KIO::SlaveInterface::listEntries(QValueList<QValueList<KIO::UDSAtom> > const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #16 0x40751138 in KIO::SlaveInterface::dispatch(int, QMemArray<char> const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #17 0x40750220 in KIO::SlaveInterface::dispatch() () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #18 0x4074d188 in KIO::Slave::gotInput() () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #19 0x4074f988 in KIO::Slave::qt_invoke(int, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #20 0x4114852c in QObject::activate_signal(QConnectionList*, QUObject*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #21 0x4114868d in QObject::activate_signal(int, int) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #22 0x41466d72 in QSocketNotifier::activated(int) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #23 0x411644b0 in QSocketNotifier::event(QEvent*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #24 0x410ecc3f in QApplication::internalNotify(QObject*, QEvent*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #25 0x410ec24b in QApplication::notify(QObject*, QEvent*) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #26 0x40cd8b7d in KApplication::notify(QObject*, QEvent*) () from /home/jdarpinian/kde3.2-rc/lib/libkdecore.so.4 #27 0x410dc97a in QEventLoop::activateSocketNotifiers() () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #28 0x41097db8 in QEventLoop::processEvents(unsigned) () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #29 0x41100498 in QEventLoop::enterLoop() () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #30 0x410ecef1 in QApplication::enter_loop() () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #31 0x412c8c10 in QDialog::exec() () from /home/jdarpinian/kde3.2-rc/lib/libqt-mt.so.3 #32 0x40913c5b in KDirSelectDialog::selectDirectory(QString const&, bool, QWidget*, QString const&) () from /home/jdarpinian/kde3.2-rc/lib/libkio.so.4 #33 0x080cac94 in static_QUType_QString () #34 0x00000001 in ?? ()
Well, first it really shouldn't even be possible to access those devices in the dialog as it's supposed to just be for local directories (and I'm unable to get it to do so). But at any rate JuK isn't actually even mentioned in the backtrace, so yes, it's a kdelibs bug.
I like the ability to access the devices ioslave in the directory chooser, because every device actually represents a local directory (when mounted). Removing the ability to access it doesn't make sense. Why even have a devices ioslave if you can't use it in many cases? Anyway, I think the reason you can't access it is because you may not have it in your Open dialog Quick Access panel (the icons on the left). It is in there by default in new installations of KDE, and it is very convenient for quick access to files that are stored on other partitions (a link to /mnt would do this too, though in a less user-friendly way). Clicking it allows you to change the list of folders to start at devices:/ even though you can't type devices:/ into the bottom of the dialog. You can also access lan:/ and floppy:/ this way, and probably others. This may be the source of the problem.
Subject: Re: crash using devices ioslave in directory selection dialog On Sunday 25 January 2004 2:13, James wrote: > I like the ability to access the devices ioslave in the directory chooser, > because every device actually represents a local directory (when mounted). > Removing the ability to access it doesn't make sense. Why even have a > devices ioslave if you can't use it in many cases? Well, it's fine for a lot of applications -- ioslaves in general that is -- but for JuK it's a bit more complicated because of the way that indexing and caching of meta-data is done. Some protocols -- i.e. devices -- might make sense, but many are more unclear (like FTP might make sense, but only on a LAN and there the implementation is still difficult because FTP isn't a random access protocol). So -- yes, this is an issue, but it's much bigger than just the dialog and it's one that I haven't figured out how I'm going to solve yet.
*** This bug has been marked as a duplicate of 67737 ***