Also I just found this bug report talking about Plymouth not handing off properly. Although a lot of people in that bug report were saying that removing rhgb worked for them. So no idea if that would be realted to your issue. Just taking a shot in the dark. It’s how my mind works. I hope you got it sorted out.
wdym “to use kde iso”?
to update system via live iso?
I did a fresh installation of Fedora 43 KDE using the respun ISO that I linked in my post, and my black screen issue was solved. I have not tested upgrading from earlier Fedora versions with it.
I see but that’s not a genuine solution for us. No need to back up entire user files, settings and fresh install which is against the philosophy of Fedora.
Regardless of how Fedora should work, this is one of a few possible solutions for this specific case when it doesn’t, especially for new users.
The KWin package has been patched to fix the particular cause of the black screen on my end, so you may try upgrading directly from your package frontend to see if it works for you as well. Again, I have not tested this.
Hi, I just upgraded from 6.17.7-300fc43.x86_64 43 KDE Plasma to 6.17.12-300.fc43.x86_64 KDE Plasma and got this bug of getting stuck in a black screen, I have no “rhgb” in my boot arguments, neither I can’t start a virtual terminal with Ctrl + Alt + F1…F6.
My kwin version is: 6.5.4
I have a PC with an AMD GPU Radeon R7240/340 that was working fine in 6.17.7-300fc43.x86_64 43 KDE Plasma and that’s the only way I can make use of it by selecting this version at GRUB because if I do 6.17.12-300.fc43.x86_64 it goes to black out.
If booting from the older kernel fixes it, then it’s likely to be a different issue from the one we’re talking about in this thread (which wasn’t a kernel problem).
You may have the same problem as this user:
Ah! Thank you! yes! the post you shared does apply to my issue .
I am still having this issue as of today when rhgb is in the kernel argument. Using the workaround to remove rhgb does work for me, and I’m okay with this, however the topic is marked as resolved with an up to date kwin and wanted to report this isn’t the case for me. kwin is 6.5.4-2 and all packages are up to date from the fedora repos.
My spec (if relevant) is:
CPU: AMD Ryzen 5 7600x
RAM: 32GB DDR5-6000 (EXPO Enabled)
GPU: Intel Arc B570 (iGPU disabled in BIOS)
Storage: 1TB Samsung 970 EVO Plus
Board: Gigabyte B650 Eagle AX
Also may be worth noting I have three monitors connected, 1x HDMI monitor and 2x DVI (DP to DVI adapter) monitors
@chakiki97 You probably need to report a new KDE bug (into the KDE upstream tracker) in that case.
So I’m not sure if I’m having the same issue or if it’s an unrelated similar problem. I just started with Fedora KDE from Windows, full wipe and install.
Turning on or restarting the system boots with my main monitor working fine and the second monitor on and recognized but black. Unplugging the monitor power and plugging back in solves the issue for the session.
Ryzen 5 7600x and an RX 7800 XT
I am also having this problem intermittently when an external display is connected on Fedora 43 Plasma KDE. Kernel Just installed it a day ago after a windows wipe. Sometime it states "Nvidia kernel failed, defaulting to something else " after a few attempts at booting.
Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.18.16-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 5900HS with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G14 GA401QM_GA401QM
System Version: 1.0
ASUS G14 from ~2020 or so, 9800HS & RTX 3060.
@kparal
This issue is NOT resolved. Had a friend on an arc graphics laptop have the issue, then I was able to replicate it on my Framework 13 after a fresh Fedora KDE install. Booted and unencrypted my drive when connected to the external monitor just fine, but KDE would not launch and the PC became unresponsive. Suggesting edits or not using an external monitor are not acceptable solutions. The bugzilla page also lists this as “closed as duplicate”, while the main bug report is about gentoo/nvidia. I’m not a dev so I don’t know the proper channel to report this too, can you please help get eyes on this?
OS: Fedora Linux 43 (KDE Plasma Desktop Edition) x86_64
Host: Laptop 13 (AMD Ryzen 7040Series) (A5)
Kernel: Linux 6.19.8-200.fc43.x86_64
DE: KDE Plasma 6.6.2
WM: KWin (Wayland)
CPU: AMD Ryzen 5 7640U (12) @ 4.97 GHz
GPU: AMD Radeon 760M Graphics [Integrated]
Don, fresh installs can’t be fixed by definition, we don’t publish updated installation images (but there are unofficial ones). The common issue description also says:
Both issues should be fixed as of kwin 6.5.2, which has been the stable version for some time now. So the issues should be resolved on installed systems that are up to date.
Is that not the case?
In the bugzilla, people speak about some ACL issue. But that’s likely a new bug, so it should be filed and handled separately.
Suggesting edits or not using an external monitor are not acceptable solutions
Please be nice. There are more bugs than people, and we’re not developers either. We can’t do much better than offer workarounds. At this point I suggest reporting a new separate bug with as much details as you can (because the original bug seems resolved), and hopefully a developer can look into it.
Same here with an Asus Vivobook M1502YA Ryzen 7 5825U after an update. Relevant logs (i think):
abr 23 01:07:10 F680V9.0 sddm[1880]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
abr 23 01:07:10 F680V9.0 sddm[1880]: Auth: sddm-helper (--socket /tmp/sddm-auth-16082676-a576-4cea-b9bc-b50ca58d2eae --id 1 --start /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user biah) crashed (exit code 1)
abr 23 01:07:10 F680V9.0 sddm[1880]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
abr 23 01:07:10 F680V9.0 sddm[1880]: Auth: sddm-helper exited with 1
abr 23 00:55:10 fedora sddm-helper-start-wayland[1547]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
abr 23 00:55:11 fedora sddm-helper-start-wayland[1547]: "kwin_core: Failed to open /dev/dri/card1 device (Device or resource busy)\nkwin_wayland_drm: failed to open drm device at \"/dev/dri/card1\"\nkwin_wayland_drm: No suitable DRM devices have been found\n"
abr 23 00:55:11 fedora sddm-helper-start-wayland[1547]: "QThreadStorage: entry 7 destroyed before end of thread 0x558eed9cd070\nQThreadStorage: entry 1 destroyed before end of thread 0x558eed9cd070\nQThreadStorage: entry 0 destroyed before end of thread 0x558eed9cd070\n"
abr 23 00:55:11 fedora sddm-helper-start-wayland[1547]: Stopping... "/usr/bin/sddm-greeter-qt6"
abr 23 00:55:11 fedora sddm-helper[1499]: pam_unix(sddm-greeter:session): session closed for user sddm
abr 23 00:55:11 fedora audit[1499]: AUDIT1106 pid=1499 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=success'
abr 23 00:55:11 fedora audit[1499]: AUDIT1104 pid=1499 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=success'
abr 23 00:55:11 fedora systemd[1]: session-c1.scope: Deactivated successfully.
abr 23 00:55:11 fedora systemd[1]: session-c1.scope: Consumed 138ms CPU time, 85M memory peak.