Version: (using KDE KDE 3.1) Installed from: Debian stable Packages OS: Linux Just installed packages for debian and encounter problems. I cannot start the konqueror filemanager by clicking on its icon. This mostly takes effect on home dir but i tried to create and start further icons for / or /var with same result. The crash occurs everytime. The window shows up and then comes down with a crash dialog. For some reason i can start the file manager from the "Quick-Access" Menu in the kicker. There i can go through my filesystem without any problem. Web- and filebrowsing in general are not affected. It seems just to be a problem with start up. I started with kfmclient like in default and as url file:/home/christian. Ok. Finally the backtrace. Sorry for lack of symbols but i am not able to get debug version. Best regards. Christian --BACKTRACE-- (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)...[New Thread 1024 (LWP 28333)] (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)... 0x40eaea59 in wait4 () from /lib/libc.so.6 #0 0x40eaea59 in wait4 () from /lib/libc.so.6 #1 0x40f25e48 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40d71453 in waitpid () from /lib/libpthread.so.0 #3 0x4055a6ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40d6ef54 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40e376b8 in sigaction () from /lib/libc.so.6 #6 0x41724b59 in _init () from /usr/lib/libvorbisenc.so.0 #7 0x40009cc7 in call_init () from /lib/ld-linux.so.2 #8 0x40009e1d in _dl_init () from /lib/ld-linux.so.2 #9 0x40f04d3d in getutmpx () from /lib/libc.so.6 #10 0x40009acb in _dl_catch_error () from /lib/ld-linux.so.2 #11 0x40f04e37 in _dl_open () from /lib/libc.so.6 #12 0x40633ee4 in _KDE_IceProtocols () from /lib/libdl.so.2 #13 0x40009acb in _dl_catch_error () from /lib/ld-linux.so.2 #14 0x406342ef in dlerror () from /lib/libdl.so.2 #15 0x40633f1f in dlopen () from /lib/libdl.so.2 #16 0x405e97b3 in lt_dlseterror () from /usr/lib/libkdecore.so.4 #17 0x405ea015 in lt_dlexit () from /usr/lib/libkdecore.so.4 #18 0x405ea2cf in lt_dlexit () from /usr/lib/libkdecore.so.4 #19 0x405eaf56 in lt_dlopen () from /usr/lib/libkdecore.so.4 #20 0x4056b3f7 in KLibLoader::library () from /usr/lib/libkdecore.so.4 #21 0x4056ba45 in KLibLoader::factory () from /usr/lib/libkdecore.so.4 #22 0x4113276a in KonqIconViewWidget::startImagePreview () from /usr/lib/libkonq.so.4 #23 0x41388874 in KonqKfmIconView::mimeTypeDeterminationFinished () from /usr/lib/kde3/konq_iconview.so #24 0x4138caf5 in KMimeTypeResolver<KFileIVI, KonqKfmIconView>::slotProcessMimeIcons () from /usr/lib/kde3/konq_iconview.so #25 0x40193f7e in KMimeTypeResolverHelper::qt_invoke () from /usr/lib/libkio.so.4 #26 0x4089eef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #27 0x4089ee3e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #28 0x40b01878 in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #29 0x408b98fb in QTimer::event () from /usr/lib/libqt-mt.so.3 #30 0x4084cb53 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #31 0x4084c954 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #32 0x404fb48a in KApplication::notify () from /usr/lib/libkdecore.so.4 #33 0x4082f383 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #34 0x4081137c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #35 0x4085e31e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #36 0x4085e27b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #37 0x4084ccaa in QApplication::exec () from /usr/lib/libqt-mt.so.3 #38 0x411abb4c in main () from /usr/lib/konqueror.so #39 0x0804d3fd in strcpy () #40 0x0804e0fb in strcpy () #41 0x0804e545 in strcpy () #42 0x0804f316 in strcpy () #43 0x40e2714f in __libc_start_main () from /lib/libc.so.6
Additional note: I just found out that loading the directory view from konqueror webbrowser is possible. but changing the filebrowser view from menu is the reason for the crash.
This looks like some sort of a weird installation problem -- BTwise, the crash occurs in the initializers of libvorbisenc.so.0 -- this is no Konqueror code, just Konqueror calling dlopen on a lib that depends on vorbisenc, and the latter crashing. Are you sure that all depepndencies are met?
You were right. It was a version mismatch. Packager used older vorbislibs than my system. I set them to hold and now everything (at least kde) works fine. Thank you for you tip. This bug can be closed. ;)
Thanks for the quick follow up -- that's not the kind of bug one wants to be real.
comment for debian users with same problem. Problem are the libvorbis and libogg libraries from adrian bunk. You have to remove them from system (e.g. dpkg --force-depends xxx) and reinstall from woody. Now you have to set them to hold you are able to use apt sources of adrian without breaking kde. Don't use dselect to set the packages as hold. use dpkg --get-selections/dpkg --set-selections for this task. Enjoy kde...
A question: I am not using debian, but gentoo instead. I am having the same problem, but in order to fix it, I need to know the correct version of the vorbislibs to use. Gentoo allows several versions of libraries to exists. Just saying "reinstall from woody" doesn't help me :)