Summary: | Plasmashell crashing on boot | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | lincoln.backed470 |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kdedev, nate, sinatosk |
Priority: | NOR | Keywords: | drkonqi |
Version: | 6.1.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
lincoln.backed470
2024-09-29 10:55:45 UTC
Is there a way to reinstall plasmashell without nuking my computer? I too was experiencing this and knew it was a configuration problem but I didn't know where, eventually I found it was the way I configured pipewire some days ago ( didn't reboot until today ) which later plasma was failing to start and wasn't telling me it's failing to communicate/initiate with an audio server. inside my "pipewire.conf", "pipewire-pulse.conf" and "client.conf" I set the options mem.warn-mlock = true mem.allow-mlock = true mem.mlock-all = true inside "context.properties" I'm not sure which option it is ( my guess is mem.mlock-all ) and commented out all 3 of them and now plasma again starts for me ( I was toying around with the configs ) lincoln dot backed470 at passmail dot net it may not be pipewire and you may have configured something that KDE is indirectly or directly using ( for that was pipewire ) I just created a new user account and I do not get the same issue on the new account. The new account is working as expected. I believe this confirms that it is a configuration issue. How can I go about tracking down exactly what needs to be changed to fix it? *** This bug has been marked as a duplicate of bug 463648 *** This issue resolved itself with a recent system update I did. I didn't write down everything which was updated so I'm not sure of the details but it did include a kernel update. Not sure how/why but it is now resolved. |