Summary: | Plasma crashed right after booting KDE neon | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Valtteri Tarvainen <valtteri.tarvainen> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | ennereu, plasma-bugs, valtteri.tarvainen |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.16.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Valtteri Tarvainen
2019-08-03 07:54:54 UTC
Created attachment 121939 [details]
New crash information added by DrKonqi
plasmashell (5.16.4) using Qt 5.12.3
- What I was doing when the application crashed:
Once again I booted the KDE Neon and the Plasma Desktop crashed
- Unusual behavior I noticed:
Some time ago, I had needed to add myself to usergroup "kvm" for virtualization to work correctly. While I solved that problem, I made another one by I using usermod -G (or -g) and removed myself from every other group than kvm, then I added myself back to groups I thought my account previously was part of via root shell from recovery mode.
- Question regarding to user groups and suggestion:
Do I need to be part of some group to be able to use Plasma correctly? if so, it would be nice to have a notification telling me that my permissions are not correctly set.
-- Backtrace (Reduced):
#6 0x00007ff578953956 in qHash(QByteArray const&, unsigned int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007ff57944a73e in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8 0x00007ff57944979a in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#9 0x00007ff579413765 in () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x00007ff579413f98 in QOpenGLShaderProgram::link() () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=411995. Did you launched with "startx" too? *** This bug has been marked as a duplicate of bug 411995 *** |