Application: nepomukservicestub (0.2) KDE Platform Version: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2)) Qt Version: 4.7.0 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Just started uploading photos from my Nikon D90 via Digikam when I received the notice that nepomukservicestub had crashed. This hasn't happened when previously uploading with the same versions so that may just be a coincidence. KDE 4.5.0 beta 2 from the Kubuntu PPA repository. Digikam 1.2.0 from the same. root@quad:~# dlocate /usr/bin/nepomukservicestub kdebase-runtime: /usr/bin/nepomukservicestub kdebase-runtime-dbg: /usr/lib/debug/usr/bin/nepomukservicestub root@quad:~# apt-cache policy kdebase-runtime kdebase-runtime: Installed: 4:4.4.85-0ubuntu1~lucid1~ppa1 Candidate: 4:4.4.85-0ubuntu1~lucid1~ppa1 Version table: *** 4:4.4.85-0ubuntu1~lucid1~ppa1 0 500 http://ppa.launchpad.net/kubuntu-ppa/beta/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 4:4.4.4-0ubuntu1~lucid1~ppa1 0 500 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu/ lucid/main Packages 4:4.4.2-0ubuntu4.1 0 500 http://mirror.linux.org.au/ubuntu/ lucid-updates/main Packages 500 http://mirrors.uwa.edu.au/ubuntu/ lucid-updates/main Packages 4:4.4.2-0ubuntu4 0 500 http://mirror.linux.org.au/ubuntu/ lucid/main Packages 500 http://mirrors.uwa.edu.au/ubuntu/ lucid/main Packages root@quad:~# apt-cache policy digikam digikam: Installed: 2:1.2.0-0ubuntu3~lucid1~ppa2 Candidate: 2:1.2.0-0ubuntu3~lucid1~ppa2 Version table: *** 2:1.2.0-0ubuntu3~lucid1~ppa2 0 500 http://ppa.launchpad.net/kubuntu-ppa/beta/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:1.2.0-0ubuntu2 0 500 http://mirror.linux.org.au/ubuntu/ lucid/main Packages 500 http://mirrors.uwa.edu.au/ubuntu/ lucid/main Packages -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault [Current thread is 1 (Thread 0x7f7cfec9d760 (LWP 4620))] Thread 2 (Thread 0x7f7cf2588710 (LWP 4625)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x00007f7cfe69bd0b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x23659d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87 #2 QWaitCondition::wait (this=<value optimized out>, mutex=0x23659d0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159 #3 0x00007f7cf27d2584 in Nepomuk::MetadataMover::run (this=0x23659b0) at ../../../../nepomuk/services/filewatch/metadatamover.cpp:163 #4 0x00007f7cfe69b14e in QThreadPrivate::start (arg=0x23659b0) at thread/qthread_unix.cpp:266 #5 0x00007f7cfe4099ca in start_thread (arg=<value optimized out>) at pthread_create.c:300 #6 0x00007f7cfc1506cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f7cfec9d760 (LWP 4620)): [KCrash Handler] #6 0x00007f7cfe7a5336 in QObjectPrivate::isSignalConnected (sender=0x236a8d0, m=<value optimized out>, local_signal_index=4, argv=0x7fff87e0d3f0) at kernel/qobject_p.h:223 #7 QMetaObject::activate (sender=0x236a8d0, m=<value optimized out>, local_signal_index=4, argv=0x7fff87e0d3f0) at kernel/qobject.cpp:3203 #8 0x00007f7cf27d4d95 in KInotify::created (this=0x6, _t1=<value optimized out>) at ./kinotify.moc:158 #9 0x00007f7cf27d6943 in KInotify::slotEvent (this=0x236a8d0, socket=<value optimized out>) at ../../../../nepomuk/services/filewatch/kinotify.cpp:336 #10 0x00007f7cf27d80a4 in KInotify::qt_metacall (this=0x236a8d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff87e0dd10) at ./kinotify.moc:117 #11 0x00007f7cfe7a5597 in QMetaObject::activate (sender=0x236f740, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3280 #12 0x00007f7cfe7f0ffe in QSocketNotifier::activated (this=0x6, _t1=12) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #13 0x00007f7cfe7aa0c3 in QSocketNotifier::event (this=0x236f740, e=0x7fff87e0e3c0) at kernel/qsocketnotifier.cpp:317 #14 0x00007f7cfc8c584c in QApplicationPrivate::notify_helper (this=0x2218120, receiver=0x236f740, e=0x7fff87e0e3c0) at kernel/qapplication.cpp:4358 #15 0x00007f7cfc8cb2ed in QApplication::notify (this=0x7fff87e0ea00, receiver=0x236f740, e=0x7fff87e0e3c0) at kernel/qapplication.cpp:4241 #16 0x00007f7cfd897f16 in KApplication::notify (this=0x7fff87e0ea00, receiver=0x236f740, event=0x7fff87e0e3c0) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x00007f7cfe78d87c in QCoreApplication::notifyInternal (this=0x7fff87e0ea00, receiver=0x236f740, event=0x7fff87e0e3c0) at kernel/qcoreapplication.cpp:732 #18 0x00007f7cfe7bbf7a in QCoreApplication::sendEvent (this=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #19 QEventDispatcherUNIX::activateSocketNotifiers (this=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:877 #20 0x00007f7cfe7bc4f5 in QEventDispatcherUNIXPrivate::doSelect (this=0x0, flags=<value optimized out>, timeout=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:305 #21 0x00007f7cfe7bcfcb in QEventDispatcherUNIX::processEvents (this=0x2200580, flags=) at kernel/qeventdispatcher_unix.cpp:919 #22 0x00007f7cfc977faf in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=) at kernel/qeventdispatcher_x11.cpp:152 #23 0x00007f7cfe78c5b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #24 0x00007f7cfe78c98c in QEventLoop::exec (this=0x7fff87e0e800, flags=) at kernel/qeventloop.cpp:201 #25 0x00007f7cfe790a3b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #26 0x0000000000403ab1 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../nepomuk/servicestub/main.cpp:152 Reported using DrKonqi
*** Bug 243536 has been marked as a duplicate of this bug. ***
*** Bug 244617 has been marked as a duplicate of this bug. ***
Created attachment 50515 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.7.0 - What I was doing when the application crashed: I had just pressed F8 in KDevelop. It saved the modified files, nepomunk crashed, and then the build started. The timing may have been coincidental, or perhaps something to do with modifiying the files? - Unusual behavior I noticed: The system was running slowly in the moments before the crash. -- Backtrace (Reduced): #6 0x00007f2dc7c78546 in QObjectPrivate::isSignalConnected (sender=0x152bf90, m=<value optimized out>, local_signal_index=4, argv=0x7fff724c2100) at kernel/qobject_p.h:223 [...] #8 0x00007f2db82507f5 in KInotify::created (this=0x6, _t1=<value optimized out>) at ./kinotify.moc:158 #9 0x00007f2db82523a3 in KInotify::slotEvent (this=0x152bf90, socket=<value optimized out>) at ../../../../nepomuk/services/filewatch/kinotify.cpp:336 #10 0x00007f2db8253b04 in KInotify::qt_metacall (this=0x152bf90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff724c2a20) at ./kinotify.moc:117 [...] #12 0x00007f2dc7cc421e in QSocketNotifier::activated (this=0x6, _t1=12) at .moc/release-shared/moc_qsocketnotifier.cpp:89
Created attachment 50757 [details] New crash information added by DrKonqi I had multiple tabs open in Firefox. I went to my system tray to open Clementine and Nepomuk crashed. It seemed very out of the ordinary and I really wan't doing anything I hadn't done a hundred times before.
Created attachment 51004 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3 - What I was doing when the application crashed: just as usual, some ssh sessions, 1 gvim session, opera running; kontact open on kmail, maybe receiving mails, i don't know sudden crash of nepomuk stub -- Backtrace (Reduced): #7 0x00007fa439f72365 in KInotify::created(QString const&) () from /usr/lib/kde4/nepomukfilewatch.so #8 0x00007fa439f731d0 in KInotify::slotEvent(int) () from /usr/lib/kde4/nepomukfilewatch.so #9 0x00007fa439f747df in KInotify::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/nepomukfilewatch.so [...] #11 0x00007fa4495b3a4e in QSocketNotifier::activated(int) () from /usr/lib/libQtCore.so.4 #12 0x00007fa44957297b in QSocketNotifier::event(QEvent*) () from /usr/lib/libQtCore.so.4
Created attachment 52633 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.6.3 - What I was doing when the application crashed: I've copied a large directory of Perl source files outside the scope of monitored directories. Besides that, nothing special was done, when suddenly Nepomuk crashed. -- Backtrace (Reduced): #6 0x00007f46b008a315 in QObjectPrivate::isSignalConnected (sender=0x7676e0, m=<value optimized out>, local_signal_index=4, argv=0x7fffc2f52900) at kernel/qobject_p.h:222 [...] #8 0x00007f46a105d539 in KInotify::created (this=0x6, _t1=<value optimized out>) at /var/tmp/portage/kde-base/nepomuk-4.5.2/work/nepomuk-4.5.2_build/nepomuk/services/filewatch/kinotify.moc:158 #9 0x00007f46a105ea7c in KInotify::slotEvent (this=0x7676e0, socket=<value optimized out>) at /var/tmp/portage/kde-base/nepomuk-4.5.2/work/nepomuk-4.5.2/nepomuk/services/filewatch/kinotify.cpp:331 #10 0x00007f46a105fea7 in KInotify::qt_metacall (this=0x7676e0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffc2f52f50) at /var/tmp/portage/kde-base/nepomuk-4.5.2/work/nepomuk-4.5.2_build/nepomuk/services/filewatch/kinotify.moc:117 [...] #12 0x00007f46b00cf9c4 in QSocketNotifier::activated (this=0x6, _t1=15) at .moc/release-shared/moc_qsocketnotifier.cpp:89
Created attachment 53396 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0 - What I was doing when the application crashed: Running amarok, Chrome, and Terminal and was switching between those applications -- Backtrace (Reduced): #7 0x00d68e56 in isSignalConnected (sender=0x97cfc48, m=0x1e8e224, local_signal_index=4, argv=0xbf8ba708) at kernel/qobject_p.h:220 [...] #9 0x01e7b0b4 in KInotify::created (this=0x97cfc48, _t1=...) at /usr/src/debug/kdebase-runtime-4.5.2/i686-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:158 #10 0x01e7bb7f in KInotify::slotEvent (this=0x97cfc48, socket=13) at /usr/src/debug/kdebase-runtime-4.5.2/nepomuk/services/filewatch/kinotify.cpp:331 #11 0x01e7cd3f in KInotify::qt_metacall (this=0x97cfc48, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbf8ba9b8) at /usr/src/debug/kdebase-runtime-4.5.2/i686-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:117 [...] [...] #14 0x00db7654 in QSocketNotifier::activated (this=0x97d3ee8, _t1=13) at .moc/release-shared/moc_qsocketnotifier.cpp:89
[Comment from a bug triager] From bug 252430: - What I was doing when the application crashed: Nothing nepomuk related: browsing the internet in Chromium and checking out some svn code in Konsole. -- Loggedn in as a freshly created user, then ran kdesrc-build
*** Bug 252430 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 262474: - What I was doing when the application crashed: I had just opened Picasa, which indexed a lot of files as it had not been opened for a long time. In picasa I selected "Create" --> "Picture Collage.." At this point (within a blink of an eye), the bug reporting tool was instigated. I tried to repeat two times unsuccessfully, but something changed as on the third time I tried to open the picasa programme, it also crashed.
*** Bug 262474 has been marked as a duplicate of this bug. ***
*** Bug 264529 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From 267520 (KDE 4.5.5): - What I was doing when the application crashed: Running Eclipse and opening a new project to start programming.
*** Bug 267520 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 269600 (KDE SC 4.5.5): - What I was doing when the application crashed: I was doing an rsync -avr from an external usb HDD to an on board SATA HDD. I then opened a terminal and sudo'd to rm -r the directory that rsync was writing into. Halfway thru the deletion process I issued CTRL-C to the terminal running rm -r. That is when nepomuk seemed to crash.
*** Bug 269600 has been marked as a duplicate of this bug. ***
*** Bug 270116 has been marked as a duplicate of this bug. ***
Created attachment 60643 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2 - What I was doing when the application crashed: Mapping a Minecraft map using Tectonius (java app) -- Backtrace (Reduced): #6 isSignalConnected (signal_index=6, this=0x8e00001154) at kernel/qobject_p.h:221 [...] #8 0x00007f5dd9ea5e45 in KInotify::created (this=<optimized out>, _t1=<optimized out>) at /usr/src/debug/kdebase-runtime-4.6.3/x86_64-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:159 #9 0x00007f5dd9ea67e2 in KInotify::slotEvent (this=0x12a9990, socket=<optimized out>) at /usr/src/debug/kdebase-runtime-4.6.3/nepomuk/services/filewatch/kinotify.cpp:365 #10 0x00007f5dd9ea82af in KInotify::qt_metacall (this=0x12a9990, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fff336662a0) at /usr/src/debug/kdebase-runtime-4.6.3/x86_64-redhat-linux-gnu/nepomuk/services/filewatch/kinotify.moc:118 [...] #12 0x00000031bd1b5e5e in QSocketNotifier::activated (this=<optimized out>, _t1=16) at .moc/release-shared/moc_qsocketnotifier.cpp:89
Created attachment 61630 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2 - What I was doing when the application crashed: In Ark, I had just finished extracting a zip after clicking near "Extract" and selected my downloads folder in the dropdown menu. -- Backtrace (Reduced): #6 0x00007f09c40ec76d in QObjectPrivate::isSignalConnected (this=0x101c027a7, signal_index=6) at ../../include/QtCore/private/../../../src/corelib/kernel/qobject_p.h:219 [...] #8 0x00007f09b3fefbdb in KInotify::created (this=0x25cd4e0, _t1=...) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3_build/nepomuk/services/filewatch/kinotify.moc:159 #9 0x00007f09b3feecdc in KInotify::slotEvent (this=0x25cd4e0, socket=17) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3/nepomuk/services/filewatch/kinotify.cpp:365 #10 0x00007f09b3fefa40 in KInotify::qt_metacall (this=0x25cd4e0, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fff38870cb0) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3_build/nepomuk/services/filewatch/kinotify.moc:118 [...] #13 0x00007f09c42bbc76 in QSocketNotifier::activated (this=0x2688be0, _t1=17) at .moc/release-shared/moc_qsocketnotifier.cpp:89
Oh wow, I just realized that Ark didn't finish extracting either. That was odd. I tried running Ark again, exactly as I had done before, and it extracted the entire thing, without any crashes.
Created attachment 61696 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2 - What I was doing when the application crashed: Simply staring at my desktop. I was mousing over icons, thinking about what I wanted to do next, when suddenly a crash dialog appeared. Before that, I had opened Eclipse, and had just refreshed all projects and ran "Project -> Clean" on all my projects. -- Backtrace (Reduced): #6 0x00007fa3a469476d in QObjectPrivate::isSignalConnected (this=0x7, signal_index=6) at ../../include/QtCore/private/../../../src/corelib/kernel/qobject_p.h:219 [...] #8 0x00007fa394598bdb in KInotify::created (this=0x1cb1850, _t1=...) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3_build/nepomuk/services/filewatch/kinotify.moc:159 #9 0x00007fa394597cdc in KInotify::slotEvent (this=0x1cb1850, socket=17) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3/nepomuk/services/filewatch/kinotify.cpp:365 #10 0x00007fa394598a40 in KInotify::qt_metacall (this=0x1cb1850, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fffa20603b0) at /var/tmp/portage/kde-base/nepomuk-4.6.3/work/nepomuk-4.6.3_build/nepomuk/services/filewatch/kinotify.moc:118 [...] #13 0x00007fa3a4863c76 in QSocketNotifier::activated (this=0x1cf7c40, _t1=17) at .moc/release-shared/moc_qsocketnotifier.cpp:89
*** Bug 272468 has been marked as a duplicate of this bug. ***
[Comment from a bug triager] From bug 279180 (KDE SC 4.6.3): - What I was doing when the application crashed: I asked Eclipse to refresh and clean all projects (about 10+ of them). This service seems to have real issues when I do something I/O-intensive like that. The crash can be reproduced some of the time. From bug 279381 (KDE SC 4.6.5): -- Information about the crash: Starting kdevelop from <Alt+F2> (Launch application widget). Crashes most everytime starting kdevelop The crash can be reproduced every time.
*** Bug 279180 has been marked as a duplicate of this bug. ***
*** Bug 279381 has been marked as a duplicate of this bug. ***
Created attachment 63690 [details] Patch to filewatch service Please apply this patch in kde-runtime/nepomuk with -p1 and see if it fixes the crash.
*** Bug 263180 has been marked as a duplicate of this bug. ***
I would if I where running from a private build. Is this patch in any current DEB? thanks. --- On Fri, 9/16/11, Sebastian Trueg <trueg@kde.org> wrote: From: Sebastian Trueg <trueg@kde.org> Subject: [Bug 241723] nepomukservicestub crash [QObjectPrivate::isSignalConnected, ..., invalid KInotify::created, KInotify::slotEvent] To: alindber@yahoo.com Date: Friday, September 16, 2011, 4:59 AM https://bugs.kde.org/show_bug.cgi?id=241723 --- Comment #26 from Sebastian Trueg <trueg kde org> 2011-09-16 09:59:40 --- Created an attachment (id=63690) --> (http://bugs.kde.org/attachment.cgi?id=63690) Patch to filewatch service Please apply this patch in kde-runtime/nepomuk with -p1 and see if it fixes the crash.
(In reply to comment #28) > I would if I where running from a private build. > > Is this patch in any current DEB? There is not. But maybe I can find some packager that can create one. Which distribution are you on with exact version?
Most DEBs from testing archive. uname: 0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux dpkg info: kdebase-runtime 4:4.6.5-1+b1 kdebase-runtime-dat 4:4.6.5-1 kdebase-runtime-dbg 4:4.6.5-1+b1 libnepomuk4 4:4.6.5-2 libnepomukquery4a 4:4.6.5-2 libnepomukutils4 4:4.6.5-2 --- On Tue, 9/20/11, Sebastian Trueg <trueg@kde.org> wrote: From: Sebastian Trueg <trueg@kde.org> Subject: [Bug 241723] nepomukservicestub crash [QObjectPrivate::isSignalConnected, ..., invalid KInotify::created, KInotify::slotEvent] To: alindber@yahoo.com Date: Tuesday, September 20, 2011, 2:54 AM https://bugs.kde.org/show_bug.cgi?id=241723 Sebastian Trueg <trueg@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trueg@kde.org --- Comment #29 from Sebastian Trueg <trueg kde org> 2011-09-20 07:54:42 --- (In reply to comment #28) > I would if I where running from a private build. > > Is this patch in any current DEB? There is not. But maybe I can find some packager that can create one. Which distribution are you on with exact version?
(In reply to comment #28) > I would if I where running from a private build. > > Is this patch in any current DEB? Sune Vuorela did it. You can find the package here: http://developer.kde.org/~sune/kde-runtime-4.6-trueg/
Created attachment 64154 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4 - What I was doing when the application crashed: I renamed a huge amount of files in batch in compiled a kernel simultanously. -- Backtrace (Reduced): #6 isSignalConnected (signal_index=6, this=0x101c027a7) at kernel/qobject_p.h:221 [...] #12 0x00007f2f5d877e0e in QSocketNotifier::activated (this=<optimized out>, _t1=14) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #13 0x00007f2f5d835ab3 in QSocketNotifier::event (this=0x13254f0, e=0x7fff96537ad0) at kernel/qsocketnotifier.cpp:317 #14 0x00007f2f5b8c77dc in QApplicationPrivate::notify_helper (this=0x10dcd60, receiver=0x13254f0, e=0x7fff96537ad0) at kernel/qapplication.cpp:4481 #15 0x00007f2f5b8cc33a in QApplication::notify (this=<optimized out>, receiver=0x13254f0, e=0x7fff96537ad0) at kernel/qapplication.cpp:4360
(In reply to comment #32) > Created an attachment (id=64154) [details] > New crash information added by DrKonqi > > nepomukservicestub (0.2) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4 > > - What I was doing when the application crashed: > I renamed a huge amount of files in batch in compiled a kernel simultanously. Please install kdebase-runtime debugging symbols and recreate the backtrace. If it is indeed the crash discussed in this bug report please apply the patch if possible.
*** Bug 285284 has been marked as a duplicate of this bug. ***
*** Bug 285959 has been marked as a duplicate of this bug. ***
*** Bug 286238 has been marked as a duplicate of this bug. ***
*** Bug 286240 has been marked as a duplicate of this bug. ***
*** Bug 289635 has been marked as a duplicate of this bug. ***
*** Bug 291195 has been marked as a duplicate of this bug. ***
*** Bug 295713 has been marked as a duplicate of this bug. ***
Has anyone tried Sebastian's patch as still experienced the crash?
(In reply to comment #41) > Has anyone tried Sebastian's patch as still experienced the crash? *and still experienced the crash?
*** Bug 296877 has been marked as a duplicate of this bug. ***
*** Bug 292291 has been marked as a duplicate of this bug. ***
*** Bug 289390 has been marked as a duplicate of this bug. ***
No-one has reported this with a KDE version > 4.7.4, and one user reported it fixed in KDE 4.9.2. I also tried to reproduce and couldn't. Someone seems to have fixed it somewhere along the line.