Summary: | Dolphin crashes while trying to mount HDD | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | matchmielu <matchmielu> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | a.nolting, aaugusto, ahepas1999, alther, austiniste, bill_d17, bzflater, cfeck, eddieg80, eggert, fabricio.valadares, frank78ac, gadgetsteve, gared.herdrichsen, ietzel, junk.jermany, jwmurphy, kdelibs-bugs, marco.righi, mauromol, mickey.mouse-1985, mosley.frank, nate, ofbugsandmen, orasionseis, pleasecanyounotspamme, r.c.bruno.andre, rafael00.tb, sainthyoga2003, sitter, skoll.cs, stefan.bruens, underline, zagniroberto67, zeedorq |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kdelibs/9437d7700cff0331ccdcfff2875faa4a8b98cd82 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: |
log.txt
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
matchmielu
2013-05-19 10:03:02 UTC
Thanks for the bug report. You could help us to possibly find the cause of the crash by running Dolphin in Valgrind: 1. valgrind dolphin 2> log.txt (note that Dolphin will run very slowly). 2. Reproduce the crash. 3. Attach 'log.txt' here. Thanks for your help. Created attachment 80027 [details] log.txt Thanks for your reply. So, when I run Dolphin with valgrind, the Dolphin didn't crash, but when I run Dolphin without valgrind, I can always reproduce the crash. I try it 3-4 times. I attach the log.txt file here. 2013/5/22 Frank Reininghaus <frank78ac@googlemail.com>: > https://bugs.kde.org/show_bug.cgi?id=320006 > > --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report. You could help us to possibly find the cause of the > crash by running Dolphin in Valgrind: > > 1. valgrind dolphin 2> log.txt > (note that Dolphin will run very slowly). > > 2. Reproduce the crash. > > 3. Attach 'log.txt' here. > > Thanks for your help. > > -- > You are receiving this mail because: > You reported the bug. Thanks. The Valgrind log shows only invalid reads, not writes, so I don't know if the reported errors (none of which come from Dolphin itself) have anything to do with the problem. It might have something to do with the stuff that is going on in the other threads - their backtraces are incomplete and look strange. In particular, it's very strange that there are frames from libQtDeclarative.so.4 in there. I'm not aware of anything in Dolphin that makes use of QtDeclarative. Unfortunately, I don't have any idea what else could be done to find out more about the problem. However, it seems unlikely that the crash is Dolphin's fault. *** Bug 322275 has been marked as a duplicate of this bug. *** *** Bug 324726 has been marked as a duplicate of this bug. *** *** Bug 325332 has been marked as a duplicate of this bug. *** Created attachment 83423 [details]
New crash information added by DrKonqi
dolphin (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4
- What I was doing when the application crashed:
Just plugged in an external HDD. After that Dolphin crashed.
-- Backtrace (Reduced):
#6 0x00007f63309c87c7 in QDomNode::toElement (this=this@entry=0x7ffff1a74460) at dom/qdom.cpp:7281
#7 0x00007f6330d9e67b in KBookmarkGroup::findToolbar (this=this@entry=0x7ffff1a74590) at ../../kio/bookmarks/kbookmark.cc:253
#8 0x00007f6330da5b41 in KBookmarkManager::saveAs (this=this@entry=0x1636a40, filename=..., toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:415
#9 0x00007f6330da5cc1 in KBookmarkManager::save (this=this@entry=0x1636a40, toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:398
#10 0x00007f6330da8d48 in KBookmarkManager::emitChanged (this=0x1636a40, group=...) at ../../kio/bookmarks/kbookmarkmanager.cc:553
*** Bug 327593 has been marked as a duplicate of this bug. *** I don't think that this is a Dolphin issue. I see nothing related to Dolphin in the backtrace. Moreover, the crashes only started with KDE SC 4.10, and there were, to my knowledge, no Places-related changes between 4.9 and 4.10 in Dophin. However, I do see a change in kdelibs prior to 4.10 which changes the way KBookmarkManager deals with toolbars: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/92d2484a4b0ba692a78faa83ceca851a6511f4f5 It appears that this commit might be related to the cause of these crashes. I'll CC Stefan Brüns, who committed that change. I see one possible problem here, QDomNode::toElement returns a NULL element if it is e.g. a AttributeNode or TextNode, so e.tagName(...) might crash. Patch is available at https://git.reviewboard.kde.org/r/113866/ Reporters: Can you attach your bookmarks file, so I can verify if this is possibly the cause of the crash? The file is located under: ~/.kde4/share/apps/kfileplaces/bookmarks.xml If you have privacy concerns, this will remove the critical information: sed -e '{s/href="\([^:]*\):.*"/href="\1:XXX"/g}' ~/.kde4/share/apps/kfileplaces/bookmarks.xml > bookmarks_cleaned.xml *** Bug 328804 has been marked as a duplicate of this bug. *** I tried to create a testcase, but even inserting bogus content (e.g a textnode) in the bookmarks file has not triggered the crash, so most likely a failing toElement() is out. But unfortunately none of the reporters has provided a bookmarks file, so this can not be ruled out completely. As the crash seems to happen randomly, can we rule out any threading issues? *** Bug 329693 has been marked as a duplicate of this bug. *** Git commit 9437d7700cff0331ccdcfff2875faa4a8b98cd82 by Albert Astals Cid, on behalf of Stefan Brüns. Committed on 11/01/2014 at 16:32. Pushed by aacid into branch 'KDE/4.12'. kio bookmarks: Only iterate over element nodes in findToolbar() Only iterate over element nodes, and filter on <folder> tag. findFirstChild/nextSibling might return a node which is not an QDomElement. toElement will return NULL and accessing it will crash. Possible fix for 320006 Acked by dfaure REVIEW: 113866 M +5 -14 kio/bookmarks/kbookmark.cc http://commits.kde.org/kdelibs/9437d7700cff0331ccdcfff2875faa4a8b98cd82 *** Bug 329862 has been marked as a duplicate of this bug. *** *** Bug 329885 has been marked as a duplicate of this bug. *** We are still seeing this crash with 4.12.2 (which ought to contain the latest commit) on the automatic Ubuntu error tracker. This time it crashes in: QDomNode::isElement() const () from /usr/lib/x86_64-linux-gnu/libQtXml.so.4 QDomNode::firstChildElement(QString const&) const () from /usr/lib/x86_64-linux-gnu/libQtXml.so.4 KBookmarkGroup::findToolbar() const () from /usr/lib/libkio.so.5 https://bugs.launchpad.net/kde-baseapps/+bug/1284052 Created attachment 85578 [details]
New crash information added by DrKonqi
dolphin (4.12.3) on KDE Platform 4.12.3 using Qt 4.8.5
* Opened Dolphin
* Navigated to a folder in my home directory
* Split the view
* plugged in a flash drive
* Clicked on the "Removable Media" in the Devices area in the left pane of the window
* Crash
-- Backtrace (Reduced):
#6 0x00000039a4c145eb in QDomNode::isElement (this=this@entry=0x7fffdd6f00c0) at dom/qdom.cpp:2823
#7 0x00000039a4c17ed8 in QDomNode::firstChildElement (this=this@entry=0x7fffdd6f0240, tagName=...) at dom/qdom.cpp:2951
#8 0x0000003484fc5127 in KBookmarkGroup::findToolbar (this=this@entry=0x7fffdd6f0240) at /usr/src/debug/kdelibs-4.12.3/kio/bookmarks/kbookmark.cc:251
#9 0x0000003484fccc51 in KBookmarkManager::saveAs (this=this@entry=0x1f8e6c0, filename=..., toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.12.3/kio/bookmarks/kbookmarkmanager.cc:415
#10 0x0000003484fccdd1 in KBookmarkManager::save (this=this@entry=0x1f8e6c0, toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.12.3/kio/bookmarks/kbookmarkmanager.cc:398
*** Bug 332266 has been marked as a duplicate of this bug. *** *** Bug 332861 has been marked as a duplicate of this bug. *** *** Bug 333004 has been marked as a duplicate of this bug. *** *** Bug 333406 has been marked as a duplicate of this bug. *** *** Bug 333974 has been marked as a duplicate of this bug. *** *** Bug 335167 has been marked as a duplicate of this bug. *** *** Bug 335807 has been marked as a duplicate of this bug. *** *** Bug 336762 has been marked as a duplicate of this bug. *** my apologies - it has just been explained to me that: open source is a meritocracy And now I Understand why michael young warned against the rise of the meritocracy http://books.google.co.uk/books/about/The_rise_of_the_meritocracy.html?id=e_rTyIMJR9kC because its no different from any other form of: small secret society corruption of who are you? of what have you contributed? of why should I treat you with any respect? So I guess i shouldn't be surprised that open sources is not new - its just the same old pigs in the masters clothing On 26/06/14 18:33, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=320006 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |pleasecanyounotspamme@gmail > | |.com > > --- Comment #26 from Christoph Feck <christoph@maxiom.de> --- > *** Bug 336762 has been marked as a duplicate of this bug. *** > Please do not mail privately. When comparing the backtraces of this bug (the 4.11 version of it), and bug 336762, you will see that they are identical, even if the steps are different. As such, we mark those bugs as duplicates. In case there is something I missed, please add a comment here. *** Bug 337030 has been marked as a duplicate of this bug. *** Created attachment 87759 [details]
New crash information added by DrKonqi
dolphin (4.11.5) on KDE Platform 4.11.5 using Qt 4.8.5
- What I was doing when the application crashed:
I just plug a USB pen on my laptop and dolphin crashed
-- Backtrace (Reduced):
#6 0x00007fb40dced377 in QDomNode::toElement (this=this@entry=0x7fffb60f8970) at dom/qdom.cpp:7281
#7 0x00007fb40683828b in KBookmarkGroup::findToolbar (this=this@entry=0x7fffb60f8aa0) at /usr/src/debug/kdelibs-4.11.5/kio/bookmarks/kbookmark.cc:253
#8 0x00007fb40683f6c1 in KBookmarkManager::saveAs (this=this@entry=0xc18600, filename=..., toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.11.5/kio/bookmarks/kbookmarkmanager.cc:415
#9 0x00007fb40683f841 in KBookmarkManager::save (this=this@entry=0xc18600, toolbarCache=toolbarCache@entry=true) at /usr/src/debug/kdelibs-4.11.5/kio/bookmarks/kbookmarkmanager.cc:398
#10 0x00007fb4068427c8 in KBookmarkManager::emitChanged (this=0xc18600, group=...) at /usr/src/debug/kdelibs-4.11.5/kio/bookmarks/kbookmarkmanager.cc:553
*** Bug 337888 has been marked as a duplicate of this bug. *** *** Bug 340832 has been marked as a duplicate of this bug. *** Application: dolphin (4.13.3) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-43-generic x86_64 Distribution: Linux Mint 17 Qiana -- Information about the crash: - What I was doing when the application crashed: Just connected my Kobo Aura HD to the USB port, while Calibre was open. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff60ad477c0 (LWP 4365))] Thread 4 (Thread 0x7ff5ed286700 (LWP 4366)): #0 0x00007ff60a622ad4 in pthread_mutex_lock (mutex=0x7ff5e8000a60) at forward.c:192 #1 0x00007ff6015b8981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ff601576fca in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ff6015770ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ff6066767be in QEventDispatcherGlib::processEvents (this=0x7ff5e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x00007ff6066480af in QEventLoop::processEvents (this=this@entry=0x7ff5ed285de0, flags=...) at kernel/qeventloop.cpp:149 #6 0x00007ff6066483a5 in QEventLoop::exec (this=this@entry=0x7ff5ed285de0, flags=...) at kernel/qeventloop.cpp:204 #7 0x00007ff606544c5f in QThread::exec (this=this@entry=0x100e9c0) at thread/qthread.cpp:537 #8 0x00007ff606629823 in QInotifyFileSystemWatcherEngine::run (this=0x100e9c0) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x00007ff60654732f in QThreadPrivate::start (arg=0x100e9c0) at thread/qthread_unix.cpp:349 #10 0x00007ff601a56182 in start_thread (arg=0x7ff5ed286700) at pthread_create.c:312 #11 0x00007ff60a614efd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7ff5ec925700 (LWP 4367)): #0 0x00007ff60a607bad in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007ff601576fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ff6015770ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ff6066767be in QEventDispatcherGlib::processEvents (this=0x7ff5e00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x00007ff6066480af in QEventLoop::processEvents (this=this@entry=0x7ff5ec924e20, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007ff6066483a5 in QEventLoop::exec (this=this@entry=0x7ff5ec924e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007ff606544c5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537 #7 0x00007ff60654732f in QThreadPrivate::start (arg=0x1325660) at thread/qthread_unix.cpp:349 #8 0x00007ff601a56182 in start_thread (arg=0x7ff5ec925700) at pthread_create.c:312 #9 0x00007ff60a614efd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7ff5e7987700 (LWP 4368)): #0 0x00007ff60a607bad in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007ff601576fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ff6015770ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ff6066767be in QEventDispatcherGlib::processEvents (this=0x7ff5dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x00007ff6066480af in QEventLoop::processEvents (this=this@entry=0x7ff5e7986de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007ff6066483a5 in QEventLoop::exec (this=this@entry=0x7ff5e7986de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007ff606544c5f in QThread::exec (this=this@entry=0x134a140) at thread/qthread.cpp:537 #7 0x00007ff606629823 in QInotifyFileSystemWatcherEngine::run (this=0x134a140) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007ff60654732f in QThreadPrivate::start (arg=0x134a140) at thread/qthread_unix.cpp:349 #9 0x00007ff601a56182 in start_thread (arg=0x7ff5e7987700) at pthread_create.c:312 #10 0x00007ff60a614efd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7ff60ad477c0 (LWP 4365)): [KCrash Handler] #6 0x00007ff60818038b in QDomNode::isElement (this=this@entry=0x7fff45814cf0) at dom/qdom.cpp:2823 #7 0x00007ff608183a28 in QDomNode::firstChildElement (this=this@entry=0x7fff45814e70, tagName=...) at dom/qdom.cpp:2951 #8 0x00007ff60855c457 in KBookmarkGroup::findToolbar (this=this@entry=0x7fff45814e70) at ../../kio/bookmarks/kbookmark.cc:251 #9 0x00007ff608563981 in KBookmarkManager::saveAs (this=this@entry=0xfeec20, filename=..., toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:415 #10 0x00007ff608563b01 in KBookmarkManager::save (this=this@entry=0xfeec20, toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:398 #11 0x00007ff608566b88 in KBookmarkManager::emitChanged (this=0xfeec20, group=...) at ../../kio/bookmarks/kbookmarkmanager.cc:553 #12 0x00007ff60a93c4c1 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #13 0x00007ff60a93ef75 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #14 0x00007ff60665d87a in QMetaObject::activate (sender=0x15d6f30, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #15 0x00007ff606661a31 in QObject::event (this=0x15d6f30, e=<optimized out>) at kernel/qobject.cpp:1156 #16 0x00007ff60703be2c in QApplicationPrivate::notify_helper (this=this@entry=0xf3faf0, receiver=receiver@entry=0x15d6f30, e=e@entry=0x7fff45815400) at kernel/qapplication.cpp:4567 #17 0x00007ff6070424a0 in QApplication::notify (this=this@entry=0x7fff458157a0, receiver=receiver@entry=0x15d6f30, e=e@entry=0x7fff45815400) at kernel/qapplication.cpp:4353 #18 0x00007ff607d46d1a in KApplication::notify (this=0x7fff458157a0, receiver=0x15d6f30, event=0x7fff45815400) at ../../kdeui/kernel/kapplication.cpp:311 #19 0x00007ff6066494dd in QCoreApplication::notifyInternal (this=0x7fff458157a0, receiver=0x15d6f30, event=0x7fff45815400) at kernel/qcoreapplication.cpp:953 #20 0x00007ff606679323 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #21 QTimerInfoList::activateTimers (this=0xf40120) at kernel/qeventdispatcher_unix.cpp:621 #22 0x00007ff606676629 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:193 #23 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:240 #24 0x00007ff601576e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x00007ff601577048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x00007ff6015770ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007ff6066767a1 in QEventDispatcherGlib::processEvents (this=0xf0aa00, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #28 0x00007ff6070ddbb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00007ff6066480af in QEventLoop::processEvents (this=this@entry=0x7fff45815670, flags=...) at kernel/qeventloop.cpp:149 #30 0x00007ff6066483a5 in QEventLoop::exec (this=this@entry=0x7fff45815670, flags=...) at kernel/qeventloop.cpp:204 #31 0x00007ff60664db79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #32 0x00007ff60a9305e7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #33 0x00007ff60a53bec5 in __libc_start_main (main=0x4006d0, argc=5, argv=0x7fff458158d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff458158c8) at libc-start.c:287 #34 0x00000000004006fe in _start () The reporter indicates this bug may be a duplicate of or related to bug 320006. Possible duplicates by query: bug 337888, bug 337030, bug 335807, bug 332861. *** Bug 342400 has been marked as a duplicate of this bug. *** Created attachment 90411 [details]
New crash information added by DrKonqi
dolphin (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
Mounted USB flash and chosen to open with Dolphin.
It happens quite often with other USB storages.
-- Backtrace (Reduced):
#6 0x00007f49ddeb0392 in QDomNode::isElement (this=this@entry=0x7fffc80e9f60) at dom/qdom.cpp:2823
#7 0x00007f49ddeb3a28 in QDomNode::firstChildElement (this=this@entry=0x7fffc80ea0e0, tagName=...) at dom/qdom.cpp:2951
#8 0x00007f49de289967 in KBookmarkGroup::findToolbar (this=this@entry=0x7fffc80ea0e0) at ../../kio/bookmarks/kbookmark.cc:251
#9 0x00007f49de290e91 in KBookmarkManager::saveAs (this=this@entry=0xa7cf20, filename=..., toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:415
#10 0x00007f49de291011 in KBookmarkManager::save (this=this@entry=0xa7cf20, toolbarCache=toolbarCache@entry=true) at ../../kio/bookmarks/kbookmarkmanager.cc:398
Would this patch help? http://www.davidfaure.fr/2015/kbookmarkgroup.diff Otherwise I would need a valgrind log. *** Bug 345576 has been marked as a duplicate of this bug. *** *** Bug 346367 has been marked as a duplicate of this bug. *** *** Bug 349548 has been marked as a duplicate of this bug. *** *** Bug 352443 has been marked as a duplicate of this bug. *** *** Bug 363343 has been marked as a duplicate of this bug. *** *** Bug 392366 has been marked as a duplicate of this bug. *** Can someone experiencing this crash please provide their ~/.local/share/user-places.xbel ~/.local/share/user-places.xbel.tbcache I am about to close this one as WORKSFORME. There have been several requests for the bugreporters to provide feedback, but none have. Bug reports are not one-way, and bug reports are not a popularity vote. If you can not be bothered to report back, refrain from filing one in the first place, you are just adding useless noise. Been 4 years since I reported my crash in Dolphin, but I'm not able to reproduce it now. Plug USB drive in/out, Dolphin already open/not open, sitting in USB directory when unpluggged. Dolphin handled all those scenarios. I'm currently running: Dolphin 17.0.4.1 KDE Frameworks: 5.44.0 Qt: 5.9.4 Kernel: 4.15.17 Legacy KDE 4.x or Qt 4.x (or even old kernel) bug? @ Rick Alther: Thanks for the feedback! Note, in 2014 you still might have been affected by a bug, where the code called .toElement() on a non-element. This has been fixed in 2014. Thanks for checking, Rick! Let's say it's been fixed. If we get any new reports, we can re-evaluate. (In reply to Stefan Brüns from comment #44) > There have been several requests for the bugreporters to provide feedback, > but none have. > > Bug reports are not one-way, and bug reports are not a popularity vote. If > you can not be bothered to report back, refrain from filing one in the first > place, you are just adding useless noise. Just to say that it's not fair to complain about missing feedback in 2018 when the back was originally reported in 2013 (5 years ago!) and most reports are dated 2013-2014-2015, often created with the automated error reporting system DrKonqi. People may have changed system, Linux version, Linux distribution, KDE version and so on. Additionally, consider this bug was not systematic, at least for me. I personally experienced it a couple of times and DrKonqi led me here. This said, I can say it has been a long time since I've last encountered this problem and I agree it can be considered fixed for now. (In reply to Mauro Molinari from comment #48) > (In reply to Stefan Brüns from comment #44) > > There have been several requests for the bugreporters to provide feedback, > > but none have. > > > > Bug reports are not one-way, and bug reports are not a popularity vote. If > > you can not be bothered to report back, refrain from filing one in the first > > place, you are just adding useless noise. > > Just to say that it's not fair to complain about missing feedback in 2018 > when the back was originally reported in 2013 (5 years ago!) and most > reports are dated 2013-2014-2015, often created with the automated error > reporting system DrKonqi. People may have changed system, Linux version, > Linux distribution, KDE version and so on. Additionally, consider this bug > was not systematic, at least for me. I personally experienced it a couple of > times and DrKonqi led me here. > > This said, I can say it has been a long time since I've last encountered > this problem and I agree it can be considered fixed for now. First of all i reported the problem not to long ago from kdecrash application and i thought it will include the logs since it had some options for it (at least thats what i thought it was saying) this was the first time i used the program. When i saw it getting marked as a duplicate and the first report being 2013 i uninstalled the kde from my arch. Since i dont have the logs now i can tell you what i was doing: I was connecting to a Synology Diskstation (mount with cifs) thats where the problems was starting and there where many of them. on idle with split view on thats when this bug happen But there was other crashes from time to time when i was exploring on diskstatio and opening the folders with big images (around 100-500mb each mostly corel and psd). it would never happen if i was on my own 2 disks (but i didnt had a lot of images on my disks). I switched to i3 and i am using thunar again with 0 problems (In reply to Mauro Molinari from comment #48) > (In reply to Stefan Brüns from comment #44) > > There have been several requests for the bugreporters to provide feedback, > > but none have. > > > > Bug reports are not one-way, and bug reports are not a popularity vote. If > > you can not be bothered to report back, refrain from filing one in the first > > place, you are just adding useless noise. > > Just to say that it's not fair to complain about missing feedback in 2018 > when the back was originally reported in 2013 (5 years ago!) and most > reports are dated 2013-2014-2015, [...] I asked for feedback in 2014, and I asked again in 2018. > This said, I can say it has been a long time since I've last encountered > this problem and I agree it can be considered fixed for now. You are apparently able to give feedback now. Why haven't you provided information any earlier, either details how to reproduce, or stating you can no longer reproduce the bug? (In reply to Stefan Brüns from comment #50) > I asked for feedback in 2014, and I asked again in 2018. So, by "several requests" for feedback you mean twice, the second time 4 years after the first one? > You are apparently able to give feedback now. Why haven't you provided > information any earlier, either details how to reproduce, or stating you can > no longer reproduce the bug? I can't see your feedback request in 2014. I see you worked on this bug in 2013 and, if I understand it correctly, this bug should have been fixed in KDE 4.12. My first report here (that is, when I learnt about this problem) is AFTER your fix and I experienced this in KDE 4.13, which, I would say, should not have the problem. Now, your latest request (and the only one since I've been here) is dated 2018-04-17, that is less than a week ago, in a bug report that is more than 5 years old. I don't think it's so much time... I didn't give feedback before yesterday because: 1) I didn't have time to write here before yesterday 2) saying that I can't reproduce NOW (and within your less-than-a-week time frame you have given us) a problem which is intermittent, is not very informative... unless, of course, you're seeking a (not so strong) reason to close this without any further investigation |