Bug 108158 - Konqueror 3.4 crash in KDE 3.4
Summary: Konqueror 3.4 crash in KDE 3.4
Status: RESOLVED DUPLICATE of bug 103795
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-26 15:01 UTC by FF
Modified: 2005-06-26 16:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash (4.66 KB, text/plain)
2005-06-26 15:03 UTC, FF
Details

Note You need to log in before you can comment on or make changes to this bug.
Description FF 2005-06-26 15:01:59 UTC
Version:           KDE 3.4 (using KDE KDE 3.4.0)
Installed from:    Debian stable Packages
OS:                Linux

Hello I am John Barkas.
In knoppix 3.9 konqueror 3.4 suddenly crashed,so I sent you the crash log.I HOPE IT IS USEFULL!
IT HAS BEEN REPEATED 2 TIMES,IN BOTH IT HAD ICON VIEW MODE AND I USED KSnapshot 0.7 .The first time I was using Ksnapshot to capture the KSysGuard process table because when knoppix is shut down it always says that some processes seem to hang,while it crashed.IN THE FIRST TIME I ORDERED IT TO SAVE THE LOG TO THE FLOPPY DRIVE AND IT SAID IT CAN SAVE ONLY TO LOCAL FILES(I DO NOT UNDESTAND WHY FLOPPY IS NOT LOCAL????).THIS WOULD NOT BE SUCH A HUGE PROBLEM IF IT STAYED OPEN,BUT IN MY CASE IT CLOSED AND LOST IT TOGETHER WITH MY TEMPER!!IF YOU KNOW IT CANNOT SAVE TO A FLOPPY DON'T SHOW IT AT ALL IN THE SAVE MENU,JUST SHOW THE ALLOWED ONLY!!!.The second time occured 2-3 weeks after the first and I was using Ksnapshot AGAIN to capture the desktop as I found another bug AGAIN while it crashed.THIS TIME I COPIED TO THE CLIPBOARD FIRST...(I have clicked the Floppy disk icon on the desktop before KSnapshot had finished.I did not do it on purpose as it remembered to write to the floppy after 5 minutes).

ALSO THE WINDOW WITH THE BOMB HAS A GREAT ERROR.WHEN BACKTRACING THE "BUTTON" WHICH NAVIGATES USERS UP AND DOWN TO THE RIGHT SLIDING BAR STARTS,IT STARTS WITH 2mm HEIGHT THEN IT GOES TO 1cm AND SO ON FOR 100 TO 200 TIMES.As you understand it should start 2cm and if the backtrace starts to grow bigger in lines it should PROGRESSIVELY SHRINK.PLEASE FIX THIS AS IT IS TRULLY ANNOYING!!!
Comment 1 FF 2005-06-26 15:03:17 UTC
Created attachment 11591 [details]
crash

The backtraced file
Comment 2 Maksim Orlovich 2005-06-26 16:42:00 UTC
[KCrash handler]
#3  0xb7299e48 in QGList::first () from /usr/lib/libqt-mt.so.3
#4  0xb7b9408b in KDirListerCache::slotUpdateResult ()
   from /usr/lib/libkio.so.4
#5  0xb7b98db4 in KDirListerCache::qt_invoke () from /usr/lib/libkio.so.4
#6  0xb6fe171c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#7  0xb7ae8e3a in KIO::Job::result () from /usr/lib/libkio.so.4
#8  0xb7ad113c in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#9  0xb7ad265c in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#10 0xb7adb6ae in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.4
#11 0xb7aec293 in KIO::ListJob::qt_invoke () from /usr/lib/libkio.so.4
#12 0xb6fe171c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb6fe1544 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb7ac734e in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4
#15 0xb7ac5eb1 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#16 0xb7ac53b9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#17 0xb7ac2deb in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#18 0xb7ac4b08 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#19 0xb6fe171c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb6fe187d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0xb7321452 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#22 0xb6ffdf00 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#23 0xb6f84e1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#24 0xb6f8441e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0xb7545ac5 in KApplication::notify () from /usr/lib/libkdecore.so.4
#26 0xb6f7481a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#27 0xb6f2dcb3 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb6f971d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb6f850d1 in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3
#30 0xb716c0c0 in QDialog::exec () from /usr/lib/libqt-mt.so.3
#31 0x08054cce in ?? ()
#32 0xbfffed10 in ?? ()
#33 0x0814ffc0 in ?? ()
#34 0xbfffed00 in ?? ()
#35 0x081344d8 in ?? ()
#36 0x0805b615 in _IO_stdin_used ()
#37 0x00000001 in ?? ()
#38 0xbfffecb8 in ?? ()
#39 0xb6f48a8f in QRegion::operator= () from /usr/lib/libqt-mt.so.3
#40 0x0805685a in ?? ()
#41 0x081344d8 in ?? ()
#42 0xb7e19840 in __after_morecore_hook () from /lib/tls/libc.so.6
#43 0xb7d59e24 in mallopt () from /lib/tls/libc.so.6
#44 0xb6fe171c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#45 0xb6fe1544 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#46 0x0805a37e in ?? ()
#47 0x081659e8 in ?? ()
#48 0x00000003 in ?? ()
#49 0xbfffef08 in ?? ()
#50 0x0805a48c in ?? ()
#51 0x081659e8 in ?? ()
#52 0x00000000 in ?? ()
#53 0x0000009b in ?? ()
#54 0xb744953c in ?? () from /usr/lib/libqt-mt.so.3
#55 0x08149718 in ?? ()
#56 0xbfffef80 in ?? ()
#57 0xbfffef58 in ?? ()
#58 0xb6fe171c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
Comment 3 Maksim Orlovich 2005-06-26 16:44:50 UTC

*** This bug has been marked as a duplicate of 103795 ***