Version-Release number of selected component: ktorrent-4.3.1-4.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/ktorrent -session 10d9cfe4e4000139657297000000016050042_1402537912_536086 crash_function: _xend executable: /usr/bin/ktorrent kernel: 3.14.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _xend at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33 #1 __lll_unlock_elision at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29 #2 unlock at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1245 #3 ~CacheLocker at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1317 #4 KSharedDataCache::find at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1608 #5 KIconLoaderPrivate::findCachedPixmapWithPath at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:854 #6 KIconLoader::loadIcon at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:1123 #7 KIconEngine::pixmap at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconengine.cpp:104 #8 QIcon::pixmap at image/qicon.cpp:684 #9 QWidgetPrivate::setWindowIcon_sys at kernel/qwidget_x11.cpp:1490
Created attachment 908294 [details] File: backtrace
Created attachment 908295 [details] File: cgroup
Created attachment 908296 [details] File: core_backtrace
Created attachment 908297 [details] File: dso_list
Created attachment 908298 [details] File: environ
Created attachment 908299 [details] File: exploitable
Created attachment 908300 [details] File: limits
Created attachment 908301 [details] File: maps
Created attachment 908302 [details] File: open_fds
Created attachment 908303 [details] File: proc_pid_status
Created attachment 908304 [details] File: var_log_messages
Thanks for your bug report. Can you give any further information when the bug struck you? Can you reproduce the crash, or did it happen only once?
It looks like a corrupted icon/pixmap cache (which can happen when disk space runs low, or under memory pressure when using default tmpfs /var/tmp)
See also upstream report, https://bugs.kde.org/show_bug.cgi?id=305654 (assuming I'm correct, the backtrace is similar but not exactly the same)
The crash happened at startup. I don't think it is a memory issue, as I have 16 GB of RAM and plenty of disk space. Lately I am experiencing crashes of various applications right at startup.
Thanks for the details. But what I failed to understand so far is: does this happen every time at startup of Ktorrekt? Or did the crash occur only once? And, since you mentioned that you have various apps crashing: have you run a memory check? Maybe one of your memory banks is faulty?
Thank you for your reply. I often have random applications crashing at startup, when I first login after powering up. You made a good point with a possible faulty RAM, so I ran a memory check with memtester (12000 MB, 3 loops) and everything is OK. I think this was the first time ktorrent crashed. I had not even opened it.
It is hard to debug a random crash. Please keep us up2date if another crash occurs and send us the debug ouput. If the debug output is similar it should be much easier to get to the core of the problem...
I have been monitoring this for a while. Ktorrent hasn't crashed again to date. I still have crashes at startup, randomly. The most frequent one seems to be kde.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.