| Summary: | kde system settings crash 20.04 | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Andrey <autoxarkov> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate, odeeno, stuart |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.24.5 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-20965-0.html
attachment-25590-0.html New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Andrey
2022-05-16 14:12:42 UTC
No KDE code is implicated in the backtrace. What were you doing when it crashed? Created attachment 148890 [details] attachment-20965-0.html I just run system settings. Video: https://youtu.be/BtJ_Z2Lw4ug пн, 16 мая 2022 г. в 21:20, Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=453892 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > CC| |nate@kde.org > Component|general |generic-crash > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham <nate@kde.org> --- > No KDE code is implicated in the backtrace. > > What were you doing when it crashed? > > -- > You are receiving this mail because: > You reported the bug. Darn, that seems bad. Unfortunately I am unsure how to proceed because the backtrace doesn't suggest that any KDE code is at fault. I suspect a local installation issue, or else an upstream Qt issue. Created attachment 148894 [details] attachment-25590-0.html 2 weeks ago. I was running out of space in the /user directory. Found the directory in which there was a database. It kept growing and occupied the entire disk. I had to remove it. After that everything works well. Problems with the settings menu just now noticed. ~/.local/share/kactivitymanagerd/resources/ Perhaps this is related... пн, 16 мая 2022 г. в 22:15, Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=453892 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #3 from Nate Graham <nate@kde.org> --- > Darn, that seems bad. > > Unfortunately I am unsure how to proceed because the backtrace doesn't > suggest > that any KDE code is at fault. I suspect a local installation issue, or > else an > upstream Qt issue. > > -- > You are receiving this mail because: > You reported the bug. Created attachment 149077 [details]
New crash information added by DrKonqi
systemsettings (5.24.5) using Qt 5.15.2
- What I was doing when the application crashed:
Nothing: the system settings application simply crash when I try to startup it. This occours after the last kde update.
- Unusual behavior I noticed:
Seems nothing of unusual.
- Custom settings of the application:
Nothing in particular.
-- Backtrace (Reduced):
#4 0x00007f6473081ee0 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
[...]
#6 0x00007f6471b96590 in QV4::ExecutableCompilationUnit::loadFromDisk(QUrl const&, QDateTime const&, QString*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
[...]
#9 0x00007f6471c60748 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x00007f6471c60ec2 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x00007f6471c61d30 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
Created attachment 149785 [details]
New crash information added by DrKonqi
systemsettings (5.24.5) using Qt 5.15.3
- What I was doing when the application crashed:
I open any settings dialog - shortcuts, search plugins, power settings it immediately crashes.
- Unusual behavior I noticed:
Listing out all issues seen even though it's unlikely that all or even any are connected:
Like the original reporter, I also noticed a problem with database-wal in kactivitymanagerd growing uncontrolled until all disk space is consumed - 225GB most recently. I've taken to killing kactivitymanagerd just to prevent this issue.
Also having issues with taskbar becoming unresponsive requiring a plasmashell restart.
Media and 'windows' key no longer working.
The desktop becomes completely unusable after resuming from sleep - very weird render buffer issues it seems like, desktops on two monitors continually switching places and being rendered mirrored in both x and y axis - although it seems even more complex that this as certain (backwards and upside down) characters are also substituted e.g. s becomes e
-- Backtrace (Reduced):
#11 0x00007f76263cc38f in QV4::CompiledData::CompilationUnit::setUnitData(QV4::CompiledData::Unit const*, QV4::CompiledData::QmlUnit const*, QString const&, QString const&) () from /lib64/libQt5Qml.so.5
#12 0x00007f76264b6c15 in QV4::ExecutableCompilationUnit::loadFromDisk(QUrl const&, QDateTime const&, QString*) () from /lib64/libQt5Qml.so.5
#13 0x00007f7626532627 in QQmlTypeData::tryLoadFromDiskCache() () from /lib64/libQt5Qml.so.5
#14 0x00007f7626537603 in QQmlTypeData::dataReceived(QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
#15 0x00007f762658407b in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
So I played a hunch based on the backtrace and completely wiped everything in the .cache folder. Following this I could no longer reproduce the crash. Since I deleted everything I can't narrow down exactly what file(s) were causing issues and why (doh). Possibly files were in an unexpected format after the upgrade or corrupted somehow (when system ran out of space due to kactivitymanager bug?). Either way, root cause seems to be a KDE bug and lack of sanity checking and error handling obviously needs to be addressed. Thank you for the bug report, and I'm sorry we weren't able to get to it yet. Andrey, a lot has changed since it was reported; can I ask you to see if this is still an issue with Plasma 6.4 or later? Thanks a lot! 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |