| Summary: | Lots of crashes at login and logout with this version of KDE and openSUSE Leap 42.2 | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kcoreaddons | Reporter: | Aaron Digulla <digulla> |
| Component: | general | Assignee: | Michael Pyne <mpyne> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kdelibs-bugs, lbeltrame, mnpmodel, nate, nico.kruber |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.28.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Aaron Digulla
2016-11-28 22:48:04 UTC
Crash is in KSharedDataCache. Very unlikely to be related to 3D libraries. Check that the filesystem has free space, that it's not corrupted and that all files are owned by you. Reassigning to framework which contains KSharedDataCache. I have 100GB free on /home and 160GB on root. My guess is that this is the /home file system which could be corrupt. Any idea which folder? ~/.kde4/? *** Bug 373634 has been marked as a duplicate of this bug. *** *** Bug 376510 has been marked as a duplicate of this bug. *** @Luca: Could you have a look and comment on this? What's also important to note is that the frameworks version is "old". I am aware of the fact that it was decided to stay with KDE Frameworks 5.26, but the thing is that this is a combination that (from a KDE perspective) is rather untested. Maybe this could lead to this kind of issues? Just a guess.. *** Bug 416836 has been marked as a duplicate of this bug. *** *** Bug 417010 has been marked as a duplicate of this bug. *** Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! 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! I can't provide any more information since I gave up on KDE a long time ago but there are duplicate bugs from 2 years ago. I would guess the bug is still alive. For the short term, please add logging or error messages around the lines in the many reported stacktraces which contain the offending path. That would help to track this bug down. Since you aren't in a position to reproduce the issue anymore, and all duplicates are over 2 years old, there aren't a lot of debugging options. Let's close it. |