Version: 3.5.1 (using KDE 3.5.1, Kubuntu Package 4:3.5.1-0ubuntu0breezy1 ) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15.1-p4-s2-ll I viewed a folder in konqueror using the photobook view. This folder had ~120 photos (100MB in total). It displayed the photos correctly. However when I added new photos and did a refresh the new photos did not show. When changed to a new file: directory with only a few files, the progress wheel continued spinning indefinately but never actually loaded. Loading http: and ftp: directories also stalled (although they load fine in firefox, and loaded fine before I used the photobook view.) Closing and restarting konqueror did not help. Changing the view back to an icon view did not help. Changeing the view to the radial map did cause the to load however (the radial map is added by the filelight package). After changing the view back to icon view, Konqueror crashed. I have included a backtrace at: http://www.dansted.org/konqueror_backtrace.txt.gz Unfortunately Ubuntu does not include symbols for all libraries, so I am not sure how useful this trace will be. After konqueror crashed, I restarted it and everything worked fine. Opening the photobook view did not reproduce the bug. Adding an additional file while the photobook view was open also did not reproduce the bug.
Konq crashed again. I was using a vertical split. Both splits were viewing the same directory. Every second or so, an additional picture was being added to this directory. I was selecting good pictures, and dragging them to the "good" directory. Konq suddenly crashed. The new backtrace is at: http://www.dansted.org/konqueror_backtrace2.txt.gz
Pasting the first backtrace: [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb7d159b1 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7d172c9 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb7d496ea in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6 #10 0xb7d4ff54 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6 #11 0xb7d502ca in free () from /lib/tls/i686/cmov/libc.so.6 #12 0xb7effc71 in operator delete () from /usr/lib/libstdc++.so.6 #13 0xb497f3d6 in KParts::GenericFactory<Filelight::Part>::~GenericFactory () from /usr/lib/kde3/libfilelight.so #14 0xb7898b7b in KLibrary::~KLibrary () from /usr/lib/libkdecore.so.4 #15 0xb785e0bd in KLibrary::slotTimeout () from /usr/lib/libkdecore.so.4 #16 0xb785e179 in KLibrary::qt_invoke () from /usr/lib/libkdecore.so.4 #17 0xb72eb929 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #18 0xb72ec3c4 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0xb764cf9a in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #20 0xb7310c19 in QTimer::event () from /usr/lib/libqt-mt.so.3 #21 0xb7282f80 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #22 0xb7283172 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #23 0xb79150cc in KApplication::notify () from /usr/lib/libkdecore.so.4 #24 0xb7213db7 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #25 0xb727499b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #26 0xb7227a84 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #27 0xb729acfb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #28 0xb729ac1e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #29 0xb7281c13 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #30 0xb67d06dc in kdemain () from /usr/lib/libkdeinit_konqueror.so #31 0xb7f88540 in kdeinitmain () from /usr/lib/kde3/konqueror.so
> Product|konqueror |filelight I suspect that this is not filelight related since the Konq stopped responding before I switched to the filelight view the first time, and the second time I did not use the filelight view. However, if this is any use, filelight was version 1.0-beta4.
The BT suggests Filelight, but the symptons suggest otherwise. The KPart switching mish-mash is complex so it's possible it tried to free the filelight part twice or somethingg. I'd have to look into the deeper parts of Konqi to figure it out. I'll check it out.
*** Bug 130797 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 124997 ***