Bug 116532 - Konqueror sometimes crash after deleting files
Summary: Konqueror sometimes crash after deleting files
Status: RESOLVED DUPLICATE of bug 96405
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-16 23:33 UTC by dju`
Modified: 2005-11-16 23:48 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 dju` 2005-11-16 23:33:51 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.14-ck5 i686) 
OS:                Linux

When deleting (not moving to Trash) file(s) with the hotkey in the filemanager profile, konqueror sometimes crashes. The files are actually deleted before it crashes. Here is the backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1234270544 (LWP 8649)]
[KCrash handler]
#4  0xb7cf3e0f in QValueList<KIO::UDSAtom>::begin (this=0x6c0070)
    at qvaluelist.h:475
#5  0xb7da6a98 in KFileItem::localPath (this=0x878cb00) at kfileitem.cpp:315
#6  0xb7da9e02 in KFileItem::mostLocalURL (this=0x878cb00, local=@0xbfe56abf)
    at kfileitem.cpp:950
#7  0xb7da71dd in KFileItem::determineMimeType (this=0x878cb00)
    at kfileitem.cpp:438
#8  0xb7da713f in KFileItem::mimetype (this=0x6c0070) at kfileitem.cpp:430
#9  0xb7dce974 in KIO::PreviewJob::startPreview (this=0x8786220)
    at previewjob.cpp:177
#10 0xb7dcdf62 in KIO::PreviewJob::qt_invoke (this=0x8786220, _id=7, 
    _o=0xbfe56e30) at previewjob.moc:137
#11 0xb6ef3ab4 in QObject::activate_signal (this=0x83ac6a8, clist=0x878be70, 
    o=0xbfe56e30) at qobject.cpp:2355
#12 0xb72d6f4f in QSignal::signal (this=0x83ac6a8, t0=@0x83ac6d0)
    at moc_qsignal.cpp:100
#13 0xb6f15973 in QSignal::activate (this=0x83ac6a8) at qsignal.cpp:212
#14 0xb6f1f880 in QSingleShotTimer::event (this=0x83ac680) at qtimer.cpp:286
#15 0xb6e8363d in QApplication::internalNotify (this=0xbfe57670, 
    receiver=0x83ac680, e=0xbfe57180) at qapplication.cpp:2635
#16 0xb6e82880 in QApplication::notify (this=0xbfe57670, receiver=0x83ac680, 
    e=0xbfe57180) at qapplication.cpp:2358
#17 0xb76e754c in KApplication::notify (this=0xbfe57670, receiver=0x83ac680, 
    event=0xbfe57180) at kapplication.cpp:549
#18 0xb7f290f5 in QApplication::sendEvent (receiver=0x6c0070, event=0xbfe56c60)
    at qapplication.h:491
#19 0xb6e6eae7 in QEventLoop::activateTimers (this=0x81e3df0)
    at qeventloop_unix.cpp:556
#20 0xb6e1f0e5 in QEventLoop::processEvents (this=0x81e3df0, flags=4)
    at qeventloop_x11.cpp:389
#21 0xb6e9abe1 in QEventLoop::enterLoop (this=0x81e3df0) at qeventloop.cpp:198
#22 0xb6e9aafa in QEventLoop::exec (this=0x81e3df0) at qeventloop.cpp:145
#23 0xb6e837df in QApplication::exec (this=0xbfe57670) at qapplication.cpp:2758
#24 0xb649c9c4 in kdemain (argc=7078000, argv=0x6c0070) at konq_main.cc:206
#25 0x0804dc8e in launch (argc=2, _name=0x81c2b9c "konqueror", 
    args=0x81c2baf "\001", cwd=0x0, envc=1, envs=0x81c2bc0 "", 
    reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x6c0070 <Address 0x6c0070 out of bounds>) at kinit.cpp:625
#26 0x0804f1f5 in handle_launcher_request (sock=8) at kinit.cpp:1189
#27 0x0804f77d in handle_requests (waitForPid=0) at kinit.cpp:1392
#28 0x08050855 in main (argc=2, argv=0xbfe57d84, envp=0x6c0070)
    at kinit.cpp:1848
Comment 1 dju` 2005-11-16 23:35:23 UTC
Oh, I forgot to post my CXXFLAGS="-march=pentium3 -O2 -pipe".
Comment 2 Maksim Orlovich 2005-11-16 23:48:11 UTC
That's fixed now, in 3.4.2, I think. Thank you for your report

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