Bug 311917 - Konqueror Kfind Crashes shortly after starting a search for a single word in contents of any file
Summary: Konqueror Kfind Crashes shortly after starting a search for a single word in ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kfind
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 299940 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-19 02:38 UTC by brindamo
Modified: 2018-11-30 03:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.79 KB, text/plain)
2013-12-17 00:09 UTC, Kamesh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description brindamo 2012-12-19 02:38:22 UTC
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
Comment 1 Jekyll Wu 2013-03-04 08:01:23 UTC
*** Bug 299940 has been marked as a duplicate of this bug. ***
Comment 2 Kamesh 2013-12-17 00:09:01 UTC
Created attachment 84132 [details]
New crash information added by DrKonqi

kfind (2.0) on KDE Platform 4.11.2 using Qt 4.8.4

Kfind crashes when I try and search for a single word from the Contents tab, Containing text field.

-- Backtrace (Reduced):
#6  0x00007f6aeb3aff77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f6aeb3b35e8 in __GI_abort () at abort.c:90
[...]
#12 0x00007f6aebbbead6 in QEventLoop::exec (this=this@entry=0x7ffff3a681e0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f6aeca5738c in QDialog::exec (this=this@entry=0x7ffff3a68300) at dialogs/qdialog.cpp:554
#14 0x0000000000413e0f in main (argc=1, argv=0x7ffff3a68488) at ../../kfind/main.cpp:74
Comment 3 Andrew Crouthamel 2018-10-31 03:52:11 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-15 10:39:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-30 03:52:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!