Version: unknown (using KDE 3.1.0) Installed from: SuSE Compiler: gcc version 3.2 OS: Linux (i686) release 2.4.19-4GB In Kde 3.1 on SuSE 8.1, if you start konqueror using the kicker, or using a desktop icon, it crashes when you try to view a directory using a file:/ URL. However, if you start konqueror from the commandline from within a konsole, it works fine (you can view file URL's). Attached is a Dr Konqi crash dump: (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 20231)] (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)...0x410b08c9 in wait4 () from /lib/libc.so.6 #0 0x410b08c9 in wait4 () from /lib/libc.so.6 #1 0x4112bc90 in __DTOR_END__ () from /lib/libc.so.6 #2 0x40f0ba93 in waitpid () from /lib/libpthread.so.0 #3 0x40620b0d in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #4 0x40f0912b in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x00002522 in ?? () #7 0x40636240 in KLibrary::factory() () from /opt/kde3/lib/libkdecore.so.4 #8 0x406381a4 in KLibLoader::factory(char const*) () from /opt/kde3/lib/libkdecore.so.4 #9 0x412c34f1 in KonqIconViewWidget::startImagePreview(QStringList const&, bool) () from /opt/kde3/lib/libkonq.so.4 #10 0x41c9a66e in KonqKfmIconView::mimeTypeDeterminationFinished() () from /opt/kde3/lib/kde3/konq_iconview.so #11 0x41c9db8e in KMimeTypeResolver<KFileIVI, KonqKfmIconView>::slotProcessMimeIcons() () from /opt/kde3/lib/kde3/konq_iconview.so #12 0x401c0db0 in KMimeTypeResolverHelper::qt_invoke(int, QUObject*) () from /opt/kde3/lib/libkio.so.4 #13 0x4099e309 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #14 0x4099e1a7 in QObject::activate_signal(int) () from /usr/lib/libqt-mt.so.3 #15 0x40c7f5bb in QTimer::timeout() () from /usr/lib/libqt-mt.so.3 #16 0x409bf472 in QTimer::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #17 0x409402e4 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #18 0x4093fe4b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #19 0x405b2fc9 in KApplication::notify(QObject*, QEvent*) () from /opt/kde3/lib/libkdecore.so.4 #20 0x40919233 in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3 #21 0x408f6be4 in QEventLoop::processEvents(unsigned) () from /usr/lib/libqt-mt.so.3 #22 0x40953fa6 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #23 0x40953e48 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3 #24 0x40940511 in QApplication::exec() () from /usr/lib/libqt-mt.so.3 #25 0x413393f7 in main () from /opt/kde3/lib/konqueror.so #26 0x0804cbc5 in strcpy () #27 0x0804d87b in strcpy () #28 0x0804dd3c in strcpy () #29 0x0804eaa0 in strcpy () #30 0x4102b4a2 in __libc_start_main () from /lib/libc.so.6
Hi.. Can you please check whether you have $KDEDIR set, and to what? In an another BR, a SuSE user reported it being set to /opt/kde2, which can cause major problems indeed.
I have checked: no KDEDIR variable. I even deleted all /opt/kde2 directories, and uninstalled qt-2, and the crash still happened. However, I found out something else: /opt/kde3/bin/startkde launches kdeinit as follows: LD_BIND_NOW=true kdeinit +kcminit +knotify If I remove the LD_BIND_NOW=true variable, the crash no longer happens. Conversely, if I start konqueror as follows from a konsole, the crash does happen: LD_BIND_NOW=true konqueror Here is an strace log of konqueror just before the crash: ... open("/opt/kde3/lib/libartsflow_idl.so.1", O_RDONLY) = 14 read(14, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\2\5"..., 1024) = 1 024 fstat64(14, {st_mode=S_IFREG|0755, st_size=753980, ...}) = 0 mmap2(NULL, 757036, PROT_READ|PROT_EXEC, MAP_PRIVATE, 14, 0) = 0x41b79000 mprotect(0x41c09000, 167212, PROT_NONE) = 0 mmap2(0x41c09000, 167936, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 14, 0x8f) = 0x41c09000 close(14) = 0 open("/opt/kde3/lib/libmcop.so.1", O_RDONLY) = 14 read(14, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \260\3"..., 1024) = 10 24 fstat64(14, {st_mode=S_IFREG|0755, st_size=714160, ...}) = 0 mmap2(NULL, 714540, PROT_READ|PROT_EXEC, MAP_PRIVATE, 14, 0) = 0x41c32000 mprotect(0x41cd2000, 59180, PROT_NONE) = 0 mmap2(0x41cd2000, 61440, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 14, 0xa0) = 0x41cd2000 close(14) = 0 munmap(0x419b0000, 51772) = 0 --- SIGSEGV (Segmentation fault) ---
Another datapoint: If I remove /opt/kde3/lib/kde3/konq_sound.la, the crash no longer happens (even with LD_BIND_NOW set)
Hmm, talking to the SuSE packager: can you please make sure you have kdeaddons 3.1 installed, and not an earlier version? (53619 is the same bug, not dupe'ing since useful info on both branches)
what does "rpm -qf /opt/kde3/lib/kde3/konq_sound.*" say ? can you do an "strace -f -o logfile konqueror" and add the last ~50 lines as an attachement ? thanks
Created attachment 916 [details] Last 200 lines of strace -fo konqueror before crash Here are the last lines of strace -fo log konqueror before the crash. N.B. The crash also occurs even with all the "addons" packages installed: kdeaddons3-games-3.1-10 kdeaddons3-kicker-3.1-46 kdeaddons3-sound-3.1-46 kdeaddons3-konqueror-3.1-46 kdeaddons3-kate-3.1-46
> what does "rpm -qf /opt/kde3/lib/kde3/konq_sound.*" say ? > rpm -qf /opt/kde3/lib/kde3/konq_sound.* kdebase3-3.1-51 kdebase3-3.1-51
*** Bug 54334 has been marked as a duplicate of this bug. ***
Thanks for the info.. It's quite a good clue although the crash is still quite a mystery.. (Many people who have tried couldn't reproduce it..).. Can you please also check whether you have an up-to-date aRts instlal? *** This bug has been marked as a duplicate of 47373 ***
I hava arts-1.1-49, which I downloaded from /pub/kde/stable/3.1/SuSE/ix86/8.1/arts-1.1-49.i586.rpm . I could reproduce the problem on several SuSE installation _every_ _single_ _time_. However, the problem cannot be reproduced on another distribution (such as RedHat)