Ran into a problem of black screen at boot (after plymouth screen).
I’m using KDE and sddm seems to have a little bug now that it doesn’t open in the right tty, so some users might be able to switch tty (most like to the second with Ctrl+Alt+F2) to go into graphical interface.
For my part, I couldn’t switch ttys. It simply stayed a black screen.
Disabling sddm-plymouth and enabling sddm didn’t help, but when I downgraded sddm to one version back, it finally booted for me (as the new bug has been introduced in the now-upstream version).
I did this with chrooting into my installation and execute these commands inside my manjaro-chroot:
su
wget https://archive.archlinux.org/packages/s/sddm/sddm-0.19.0-4-x86_64.pkg.tar.zst
pacman -U sddm-0.19.0-4-x86_64.pkg.tar.zst
rm sddm-0.19.0-4-x86_64.pkg.tar.zst
Then exiting chroot and rebooting into my installed system. Worked fine then. I currently have work to do, so I can’t further investigate this issue (whether it really solved it or it was just a lucky boot). I might investigate more these days.
I hope I could help another user with the same problem.
This was the site which gave me the idea to downgrade this package: bugs . archlinux.org /task/70528
Everything looks ok excepts the AMD GPU Driver issue I’ve been facing the later 3 updates. Changing Kernels and kernel/Mesa updates din’t fix the issue wet.
Got this error 5min ago, and as pointed previously, it crashes my PC and requires reset button to be pushed.
Let me know how and where I could better report this issue, I’ve been using linux for 2 months
KDE with kernel 5.10.32 LTS, systemd-boot and SDDM. Everything seems to work, but I noticed some strange things during startup after upgrade (rebooted multiple times, the issue exists):
After entering volume decryption password at boot (got encrypted main drive with custom partitioning + encrypted RAID1), boot manager starts displaying all the usual messages, including UUID of disk drives. And now one of UUID is displayed incorrectly - a question mark is added instead of one of characters. Before update:
UUID=a1b92429-9eda-4260-8099-204a151d8e3f
After update: UUID=a1b92429-9eda-?260-8099-204a151d8e3f (notice ? instead of “normal” character).
both fstab and crypttab contain valid entries and RAID is automatically decrypted during boot just fine. It’s just that glitch with ? mark…
When boot ends and it’s time to start GUI (I have auto-login enabled in SDDM) instead of displaying KDE desktop immediately, system displays black window that has blinking _ symbol at the top. Just like command line. After a second or two, it disappears and desktop is displayed.
Not sure if this is issue with Manjaro or KDE/SDDM itself, but I have it for 2 months already, and it’s still not fixed. If there are multiple keyboard input languages installed and lock screen is displayed (either after screensaver or manual locking), keyboard icon is displayed at the bottom as usually, but language icon is missing; therefore, it’s impossible to know which language you use to enter password. The only way to find out - enter password and “reveal” it by clicking the corresponding icon in password field. Not a very big problem, but language selector worked for years and it’s now broken.
Upgraded today with “pacman -Suy”, without issues, and after reboot the system seems to be fine, BUT:
when I try to access (i.e. mount) a partition on an internal HDD (which is not used right-away, but is just a destination for occasional backups) Thunar refuses with error message
“Der Datenträger >xxx< konnte nicht eingehängt werden. No object for D-Bus interface.”
Mounting partionitions on this HDD manually with mount -t ext4 /dev/sdc1 /mnt it works, without errors.
Apparently no log entries relating to this issue (tried journalctl -f), no boot issues (tried dmesg)
Any ideas?? Thx.
LightDM will no longer start reliably with the 5.10 kernel on my AMD 3900x with AMD 5600xt graphics. I’ve reverted to the 5.4 LTS, but now I’m also having issues with the audio output being very distorted, tinny and scratchy. Killing pulseaudio seems to work for a while. Anyone else having audio issues?
After the update, including kernel 5.12 update, all of my VirtualBox guests, Windows and Linux, now have distorted, crackling, reverberant sound.
EDIT: Same with kernel 5.11, so it is caused by regular software update.
EDIT2: It’s an issue of VirtualBox 6.1.20 as stated in VirtualBox forum. After I downgraded to 6.1.18, the sound is normal again.
All good, except that the first time I opened a Konsole, I was greeted with a very unwelcome and intrusive new toolbar, which also had the effect of forcing the window to be much wider than usual.
After a lot of random right-clicking and trying options, I found that I could get rid of it, though annoyingly I can’t remember the precise sequence so can’t leave a solution here. But it was to do with showing toolbars in some way…
I have issue with Firefox Developer Edition. When I start it, it crashes graphically, I see just fragments of the image shown in it. I downgraded it for now to a previous version…
After the update, the login manager does not start, and I can’t switch to a text console (e.g. Ctrl-Alt-F2 doesn’t work). I’ve tried several of the kernels installed on that machine (5.12, 5.11, 5.10 and 5.11 fallback), with no joy.
I know it has Intel graphics and a 4-core Intel processor, but since I can’t get in I don’t have other details. (It’s an old-style Zareason media station for what that’s worth).
I’ll try to find an install USB stick and try to boot it off that, and check the H/W.
On initial reboot, I had a similar issue with my primary machine (AMD/Radeon hardware) but after pressing reset it came up fine the second time.
I rebooted with Linux kernel 5.4.114-1, and Thunar now mounts the partitions on my spare drive without errors.
Strange
After that, I rebooted with 5.10.32-1 again, and now the error has gone away. Didn’t change anything, apart from 2 reboots.
Should anybody have an idea: more than welcome. Will keep it “under further investigation”
EEEK!!!
Now I can’t get the system running off the USB, comes up with the boot menu but just gives a black screen on booting. Even though it was working just fine for the update (and was booted for that so it seem unlikely to be a harware issue).
Running memtest anyway.
