[Bug 311917] New: Konqueror Kfind Crashes shortly after starting a search for a single word in contents of any file

brindamo rblinux at telus.net
Wed Dec 19 02:38:22 GMT 2012


https://bugs.kde.org/show_bug.cgi?id=311917

            Bug ID: 311917
          Severity: crash
           Version: 2.0
          Priority: NOR
          Assignee: unassigned-bugs at kde.org
           Summary: Konqueror Kfind Crashes shortly after starting a
                    search for a single word in contents of any file
    Classification: Unclassified
                OS: Linux
          Reporter: rblinux at telus.net
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: general
           Product: kfind

Application: kfind (2.0)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Linux Mint 12 KDE

-- Information about the crash:
- What I was doing when the application crashed: In Konqueror I selected Cntl F
to search. Find appeared. I cleared the "Named" field on the Name/Location tab.
I selected the Contents tab and entered a single word in the "File Type:" field
then selected Find.  After more than 2 minutes I see a couple of results in the
list then I get the crash. I've repeated it twice with the same result after
about the same amount of time. I don't have any USB or other removable media
connected.

The crash can be reproduced every time.

-- Backtrace:
Application: KFind (kfind), signal: Aborted
[Current thread is 1 (Thread 0x7f9e0b349780 (LWP 10601))]

Thread 2 (Thread 0x7f9df9292700 (LWP 10602)):
#0  0x00007f9e08555e63 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f9e04f98f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f9e04f99429 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f9e08cbef3e in QEventDispatcherGlib::processEvents (this=0x1222950,
flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f9e08c92cf2 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f9e08c92ef7 in QEventLoop::exec (this=0x7f9df9291dd0, flags=...) at
kernel/qeventloop.cpp:201
#6  0x00007f9e08baa27f in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:498
#7  0x00007f9e08c75cbf in QInotifyFileSystemWatcherEngine::run (this=0x1570c60)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f9e08bacd05 in QThreadPrivate::start (arg=0x1570c60) at
thread/qthread_unix.cpp:331
#9  0x00007f9e0546aefc in start_thread (arg=0x7f9df9292700) at
pthread_create.c:304
#10 0x00007f9e08561f8d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f9e0b349780 (LWP 10601)):
[KCrash Handler]
#6  0x00007f9e084b33e5 in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f9e084b6b4b in __GI_abort () at abort.c:92
#8  0x00007f9e088dbd7d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f9e088d9f26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f9e088d9f53 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f9e088da096 in __cxa_rethrow () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f9e08c9302e in QEventLoop::exec (this=<optimized out>,
flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007f9e09b4b2d6 in QDialog::exec (this=0x7fffa5111190) at
dialogs/qdialog.cpp:552
#14 0x0000000000413d37 in main (argc=2, argv=0x7fffa5111888) at
../../kfind/main.cpp:74

Possible duplicates by query: bug 311748, bug 311589, bug 311441, bug 311040,
bug 310887.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list