From: OoLunar <OoLunar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] PlasmaShell segfaults on boot
Date: Fri, 17 May 2024 20:12:15 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50393@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]
New issue by OoLunar on void-packages repository
https://github.com/void-linux/void-packages/issues/50393
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.30_1 x86_64 AuthenticAMD uptodate rrrmFFFFFF
### Package(s) Affected
Unknown
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
None found.
### Expected behaviour
- I successfully boot up my laptop
- SDDM's login screen appears
- I successfully login
- My desktop appears (fails)
### Actual behaviour
Once I login through SDDM, my desktop appears for 1-3 seconds before crashing. KCrash appears to try to launch `plasmashell` again as my desktop will appear one more time for another half second before crashing once more. Once everything settles, I am left with a black screen, completely unable to access my system tray or any of my desktop applications.
I am currently able to access my applications through a desktop shortcut. I launch `flameshot` and take a screenshot of my black desktop, attempt to save the file. Once `nemo` prompts me where to save the file, I click "Open location" via the right click menu. Once `nemo` fully launches, I'm able to open up `gnome-terminal` and start `firefox` or whatever other applications I may need.
Ctrl+C and Ctrl+V (copy and paste) are still very unreliable (may be unrelated).
When any application attempts to use `libnotify` (or presumably attempts to send a desktop notification in any sense), the application will freeze before it's forced to be killed by me.
Alt+Tab still works as expected.
### Steps to reproduce
1. Update from KDE5 to KDE6
2. While I did not take any explicit actions, there may be other steps that were performed without my knowledge. While I was upgrading, a lot of packages failed to upgrade due to package conflicts caused by the Void packaging servers not having certain versions of packages available, such as `plasma-nm`. Additionally a lot of packages were removed without my prior knowledge, such as `NetworkManager` and `dialog`. I personally believe this may have significantly contributed to the problem, though I have no proof.
Please let me know if any additional information is required. I am considering switching away from Void to Arch, however I happen to very much enjoy using Void and would prefer to resolve this issue first.
next reply other threads:[~2024-05-17 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 18:12 OoLunar [this message]
2024-05-17 18:13 ` OoLunar
2024-05-17 18:25 ` OoLunar
2024-05-17 18:31 ` OoLunar
2024-05-17 18:32 ` OoLunar
2024-05-17 19:43 ` TheDoubleB
2024-05-17 21:56 ` TheDoubleB
2024-05-18 20:08 ` bvdeenen
2024-05-19 2:36 ` sgn
2024-05-19 3:34 ` OoLunar
2024-05-19 3:42 ` classabbyamp
2024-05-19 3:48 ` classabbyamp
2024-05-19 14:51 ` TheDoubleB
2024-05-19 16:04 ` OoLunar
2024-05-19 16:04 ` [ISSUE] [CLOSED] " OoLunar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50393@inbox.vuxu.org \
--to=oolunar@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).