Summary: | plasmashell crash on startup | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | bobthebillyboyo |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andy.v, duha.bugs, emil.panecki, fxpro32, gkupce+kdebug, goldug, hanseren11, johnmcloskey, jon02, kernecker, matt, nate, nicolas.fella, twielgos |
Priority: | VHI | Keywords: | drkonqi |
Version First Reported In: | 6.1.3 | ||
Target Milestone: | 1.0 | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/53674/events/f7c18d57c56546e39ca5d74a73306331/ | ||
Attachments: |
attachment-2351996-0.html
cache_files |
Description
bobthebillyboyo
2024-08-02 06:26:38 UTC
*** Bug 491157 has been marked as a duplicate of this bug. *** This is likely caused by a faulty update in Nobara. Please contact your distribution on how to fix this. https://nobaraproject.org/ https://www.reddit.com/r/NobaraProject/comments/1ei1gbu/well_this_is_happening_now/ much obliged! you can close the case. thank ye! Closing this for now. If you encounter further issues feel free to reopen. > This is likely caused by a faulty update in Nobara
What makes you think that?
(In reply to Nicolas Fella from comment #5) > > This is likely caused by a faulty update in Nobara > > What makes you think that? See the linked reddit thread and the nobara discord. Plasmashell crashes after the most recent update after login. Please reopen if you think this needs to be fixed on the KDE side. *** Bug 491201 has been marked as a duplicate of this bug. *** *** Bug 491218 has been marked as a duplicate of this bug. *** *** Bug 491198 has been marked as a duplicate of this bug. *** *** Bug 491273 has been marked as a duplicate of this bug. *** *** Bug 491260 has been marked as a duplicate of this bug. *** *** Bug 491288 has been marked as a duplicate of this bug. *** *** Bug 491317 has been marked as a duplicate of this bug. *** Reopening as new reports are coming in and this might be actionable by kde. If you are affected by this issue you can workaround this by deleting your plasma cache as described here: https://www.reddit.com/r/NobaraProject/comments/1ei1gbu/well_this_is_happening_now/ If this does not work the nobara discord provides a script to fix this issue. Please don't delete your cache; move its contents elsewhere. That way, if it fixes the issue, you can attach the contents here so we can inspect them and figure out what's going wrong. Created attachment 172322 [details] attachment-2351996-0.html I followed the recomended instructions from reddit! ( https://www.reddit.com/r/NobaraProject/comments/1ei1gbu/well_this_is_happening_now/ ) The bug was also after install and update nobara 40 steam HTPC version but now it works! Thank you, have a nice day! Nate Graham <bugzilla_noreply@kde.org> schrieb am Mo., 5. Aug. 2024, 22:27: > https://bugs.kde.org/show_bug.cgi?id=491155 > > --- Comment #15 from Nate Graham <nate@kde.org> --- > Please don't delete your cache; move its contents elsewhere. That way, if > it > fixes the issue, you can attach the contents here so we can inspect them > and > figure out what's going wrong. > > -- > You are receiving this mail because: > You are on the CC list for the bug. Your the reddit link help thanks I followed the recomended instructions from reddit! (https://www.reddit.com/r/NobaraProject/comments/1ei1gbu/well_this_is_happening_now/) The bug was also after install and update nobara 40 steam HTPC version but now it works! Created attachment 172328 [details]
cache_files
I was able to reproduce this in a VM with Nobara-40-Official-2024-07-17.iso.
Attached are the cache files before the updated, after the update when plasma is crashing and after deleting the ~/.cache/plasmashell and its working again.
*** Bug 491329 has been marked as a duplicate of this bug. *** *** Bug 491565 has been marked as a duplicate of this bug. *** *** Bug 491571 has been marked as a duplicate of this bug. *** *** Bug 491572 has been marked as a duplicate of this bug. *** This might be the same issue as https://bugs.kde.org/show_bug.cgi?id=418148 or possibly has the same root cause. Oh jeez, it is indeed. Good catch! *** This bug has been marked as a duplicate of bug 418148 *** |