Bug 160709 - crash of konqueror during unmount activity
Summary: crash of konqueror during unmount activity
Status: RESOLVED REMIND
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 145526 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-04-11 15:01 UTC by Elmar Stellnberger (AT/K)
Modified: 2008-07-31 13:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2008-04-11 15:01:44 UTC
Version:           3.5.9 (using 3.5.9 "release 53.4" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.54-0.2.3-default

Überprüfung der Systemkonfiguration beim Start deaktiviert.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230510416 (LWP 30178)]
[KCrash handler]
#6  0xb786064f in QGList::next () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb7e4815e in KDirListerCache::slotUpdateResult ()
   from /opt/kde3/lib/libkio.so.4
#8  0xb7e484ae in KDirListerCache::qt_invoke () from /opt/kde3/lib/libkio.so.4
#9  0xb75a9ded in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb7d751de in KIO::Job::result () from /opt/kde3/lib/libkio.so.4
#11 0xb7db5cfd in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4
#12 0xb7dd618e in KIO::SimpleJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#13 0xb7dd651d in KIO::ListJob::slotFinished () from /opt/kde3/lib/libkio.so.4
#14 0xb7ddf80e in KIO::ListJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#15 0xb75a9ded in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb75aaa4d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb7d7124c in KIO::SlaveInterface::finished ()
   from /opt/kde3/lib/libkio.so.4
#18 0xb7de1a45 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#19 0xb7dc6ada in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#20 0xb7d8662c in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#21 0xb7dc82e0 in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#22 0xb75a9ded in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb75aa952 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb78e4c00 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb75c8000 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb754a867 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb754b631 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb7bd38b3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#29 0xb753f184 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb74f9474 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb7561688 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb756151e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb754a41f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb67ca705 in kdemain () from /opt/kde3/lib/libkdeinit_konqueror.so
#35 0xb68e5524 in kdeinitmain () from /opt/kde3/lib/kde3/konqueror.so
#36 0x0804e2bf in launch ()
#37 0x0804eb4a in handle_launcher_request ()
#38 0x0804eecf in handle_requests ()
#39 0x080500c3 in main ()
Comment 1 Florian Reinhard 2008-06-02 12:28:37 UTC
could you please give some more information what you were trying to do? step-by-step instructions to reproduce that bug would be really helpful.
Comment 2 Florian Reinhard 2008-07-07 10:11:36 UTC
Danke für den Bugreport, aber da der Bug in 3.5.9 auftrat und die stabile Serie bereits bei 4.0 ist, wird dieser Bug vermutlich nicht gefixt. Falls er in einer neueren Version wieder auftritt kannst du den Bug erneut öffnen.
Comment 3 A. Spehr 2008-07-31 13:26:49 UTC
*** Bug 145526 has been marked as a duplicate of this bug. ***