Version: 3.1.1 (using KDE 3.1.1) Installed from: compiled sources Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98) OS: Linux (i686) release 2.4.17 I simply klicked on a smb-mounted directory (which worked already and also after a konqueror restart works again), and konqi crashed: [New Thread 1024 (LWP 2216)] 0x4102b669 in __wait4 () from /lib/i686/libc.so.6 #0 0x4102b669 in __wait4 () from /lib/i686/libc.so.6 #1 0x410a7154 in __DTOR_END__ () from /lib/i686/libc.so.6 #2 0x40eeb523 in waitpid (pid=3361, stat_loc=0x0, options=0) at wrapsyscall.c:172 #3 0x405acf98 in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:235 #4 0x40ee98d5 in pthread_sighandler (signo=11, ctx= {gs = 7, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 49168, edi = 1, esi = 3221215760, ebp = 3221215816, esp = 3221215728, ebx = 1080432804, edx = 140130240, ecx = 140207759, eax = 280415551, trapno = 14, err = 4, eip = 1079712102, cs = 35, __csh = 0, eflags = 66183, esp_at_signal = 3221215728, ss = 43, __ssh = 0, fpstate = 0xbfffd770, oldmask = 2147483648, cr2 = 280415551}) at signals.c:97 #5 <signal handler called> #6 trailingSlash (_trailing=1, path=@0xbfffda60) at /opt/qt3.1/include/qstring.h:259 #7 0x405b1f00 in KURL::path (this=0x847b328, _trailing=1) at kurl.h:250 #8 0x405b10a4 in KURL::equals (this=0x847b328, _u=@0xbfffdec0, ignore_trailing=true) at kurl.cpp:913 #9 0x405b1054 in KURL::cmp (this=0x847b328, u=@0xbfffdec0, ignore_trailing=true) at kurl.cpp:903 #10 0x401d1579 in KDirLister::slotJobToBeKilled (this=0x852d578, url=@0xbfffdec0) at ../kio/jobclasses.h:373 #11 0x401d2314 in KDirLister::qt_invoke (this=0x852d578, _id=7, _o=0xbfffdc00) at /opt/qt3.1/include/private/qucom_p.h:312 #12 0x4097fe37 in QObject::activate_signal (this=0x852d578, clist=0x852d7a8, o=0xbfffdc00) at kernel/qobject.cpp:2212 #13 0x401d1a5b in KDirLister::completed (this=0x852d578, t0=@0xbfffdec0) at kdirlister.moc:241 #14 0x401cc271 in KDirListerCache::slotUpdateResult (this=0x8514fe8, j=0x85b66c8) at kdirlister.cpp:1294 #15 0x401d2ad0 in KDirListerCache::qt_invoke (this=0x8514fe8, _id=10, _o=0xbfffdf90) at /opt/qt3.1/include/private/qucom_p.h:312 #16 0x4097fe37 in QObject::activate_signal (this=0x85b66c8, clist=0x85a7920, o=0xbfffdf90) at kernel/qobject.cpp:2212 #17 0x40149803 in KIO::Job::result (this=0x85b66c8, t0=0x85b66c8) at jobclasses.moc:156 #18 0x4013630e in KIO::Job::emitResult (this=0x85b66c8) at job.cpp:183 #19 0x40137969 in KIO::SimpleJob::slotFinished (this=0x85b66c8) at job.cpp:501 #20 0x4013e34a in KIO::ListJob::slotFinished (this=0x85b66c8) at job.cpp:1675 #21 0x4014b93e in KIO::ListJob::qt_invoke (this=0x85b66c8, _id=16, _o=0xbfffe350) at jobclasses.moc:1350 #22 0x4097fe37 in QObject::activate_signal (this=0x844e1e8, clist=0x8464ee8, o=0xbfffe350) at kernel/qobject.cpp:2212 #23 0x4097fcea in QObject::activate_signal (this=0x844e1e8, signal=6) at kernel/qobject.cpp:2186 #24 0x4012dad5 in KIO::SlaveInterface::finished (this=0x844e1e8) at /opt/qt3.1/include/qmetaobject.h:261 #25 0x4012a8e2 in KIO::SlaveInterface::dispatch (this=0x844e1e8, _cmd=104, rawdata=@0xbfffe930) at slaveinterface.cpp:256 #26 0x4012a4bc in KIO::SlaveInterface::dispatch (this=0x844e1e8) at slaveinterface.cpp:192 #27 0x40127bf1 in KIO::Slave::gotInput (this=0x844e1e8) at slave.cpp:221 #28 0x40129ded in KIO::Slave::qt_invoke (this=0x844e1e8, _id=4, _o=0xbfffeab0) at slave.moc:113 #29 0x4097fe37 in QObject::activate_signal (this=0x80cc118, clist=0x85d83b0, o=0xbfffeab0) at kernel/qobject.cpp:2212 #30 0x409800ca in QObject::activate_signal (this=0x80cc118, signal=2, param=15) at kernel/qobject.cpp:2277 #31 0x40c0daec in QSocketNotifier::activated (this=0x80cc118, t0=15) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #32 0x4099a5ce in QSocketNotifier::event (this=0x80cc118, e=0xbfffed70) at kernel/qsocketnotifier.cpp:268 #33 0x409322b2 in QApplication::internalNotify (this=0xbffff3d0, receiver=0x80cc118, e=0xbfffed70) at kernel/qapplication.cpp:2350 #34 0x4093165e in QApplication::notify (this=0xbffff3d0, receiver=0x80cc118, e=0xbfffed70) at kernel/qapplication.cpp:2112 #35 0x4053809e in KApplication::notify (this=0xbffff3d0, receiver=0x80cc118, event=0xbfffed70) at kapplication.cpp:455 #36 0x40c52c66 in QApplication::sendEvent (receiver=0x80cc118, event=0xbfffed70) at kernel/qapplication.h:478 #37 0x40914c33 in QEventLoop::activateSocketNotifiers (this=0x80ab3a8) at kernel/qeventloop_unix.cpp:544 #38 0x408f12eb in QEventLoop::processEvents (this=0x80ab3a8, flags=4) at kernel/qeventloop_x11.cpp:307 #39 0x40943fd9 in QEventLoop::enterLoop (this=0x80ab3a8) at kernel/qeventloop.cpp:191 #40 0x40943efc in QEventLoop::exec (this=0x80ab3a8) at kernel/qeventloop.cpp:138 #41 0x4093244b in QApplication::exec (this=0xbffff3d0) at kernel/qapplication.cpp:2471 #42 0x412911fd in main (argc=3, argv=0x805c670) at konq_main.cc:130 #43 0x0804cb2c in launch (argc=3, _name=0x805c064 "konqueror", args=0x805c0af "", cwd=0x0, envc=0, envs=0x805c0b3 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x804f4aa "0") at kinit.cpp:547 #44 0x0804d873 in handle_launcher_request (sock=7) at kinit.cpp:1030 #45 0x0804dd1a in handle_requests (waitForPid=0) at kinit.cpp:1196 #46 0x0804ec33 in main (argc=3, argv=0xbffffc44, envp=0xbffffc54) at kinit.cpp:1547 #47 0x40f8d507 in __libc_start_main (main=0x804e650 <main>, argc=3, ubp_av=0xbffffc44, init=0x804a8c8 <_init>, fini=0x804f364 <_fini>, rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffffc3c) at ../sysdeps/generic/libc-start.c:129
where did you click on it? Do you have the sidebar open? Are there many items in the dir?
Subject: Re: konqueror crash on opening SMB mounted directory On Thursday 22 May 2003 12:58, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=58795 > > > > > ------- Additional Comments From coolo@kde.org 2003-05-22 12:57 ------- > where did you click on it? I had konqi open with sidebar and detailed list view mode. I clicked double on a directory in the detailled list view. > Do you have the sidebar open? yes. > Are there many items in the dir? The directory I saw has only 3 subdirs - one of which I double clicked and crashed. The problem is, I can not reproduce it, but I thought maybe the dump gives a hint.
*** Bug 58957 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 50149 ***