#Logout causing black screen with blinking underscore

93 messages · Page 1 of 1 (latest)

harsh harbor
#

Logging out from kde goes to a black screen with blinking cursor.

I can access tty.

trim atlas
#

Yo yo

harsh harbor
#

Yo

#

I'm in tty

I can reboot and get into a normal desktop session if that's better tho

trim atlas
#

TTY is fine

#

Which display manager are you using?

#

Check it's status systemctl status

harsh harbor
#

Sddm

#

Running and enabled

trim atlas
#

journalctl -u sddm --since "1 hour ago"

harsh harbor
trim atlas
#

journalctl -b -1

harsh harbor
#

There's pages and pages

trim atlas
#

Lol

#

Any errors

harsh harbor
#

Duplicate entries in fstab, I'll fix that I see now.

trim atlas
#

Any display manager crashing?

#

sddm-helper crashed

#

nvidia kerne; module not fount

#

kernel*

#

xorg crashed / wayland session terminated

harsh harbor
#

I fucked up installing, genfstab'd twice.

I'll wipe it and generate a fresh one

trim atlas
#

Ok, let me know if you need any help

harsh harbor
#

Ntpd service failed to start

Looking for other errors one sec, had to let my dog out lol

trim atlas
#

ooooh

#

nice

#

Failed to read display number from pipe

#

Attempt 2 ... on vt 2 failed

#

Could not start Display server on vt 2

#

This confirms your exact issue

#

After stopping the user session, SDDM attempts to restart the display server

#

Then you've got some KWin input handling bug/error

#

nvidia-gpu i2c timeout error

#

org_kde_powerdevil (KDE’s power management daemon) is failing to access /dev/i2c-8

#

FAT-fs (nvme0n1p1): Volume was not properly unmounted - /boot

#

sudo pacman -Syu

#

Are you using a custom kernel by chance?

#

If so you'll need nvidia-dkms

#

But let's reinstall the driver and ensure it's configured properly

#

sudo pacman -S nvidia nvidia-utils

harsh harbor
trim atlas
#

sudo mkinitcpio -P After you've removed nvidia-open and installed nvidia

#

Oh btw did Syu pick anything up?

#

nvidia, sddm, kde?

#

sudo nano /etc/default/grub
Add nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT

#

sudo grub-mkconfig -o /boot/grub/grub.cfg

#

And that should honestly fix the SDDM logout restart failure

harsh harbor
#

Rebooting and testing 🤞

harsh harbor
#

Now I'm having fstab issues..

I'm in the live environment.

I open my encrypted container, mount the partitions in my LVM, I wiped my fstab clean, mounted the partitions.. genfstab and boot and it won't freaking work..

trim atlas
#

Oh shoot, well now we are in for it

harsh harbor
#

Nah it should be simple

trim atlas
#

Do you need my help or you got it?

harsh harbor
#

Idk 😅

I'm trying the steps again..

  1. Reboot into live environment.

  2. Open container, mount partitions, clear fstab.

  3. Gen fstab, re-config grub just in case, reboot

  4. Profit

#

I think I figured it out now, root= is the wrong path is grub config

#

Hey hey 👏 🙂

trim atlas
#

Yo yo

#

You get the fstab?

harsh harbor
#

I was just celebrating 🥳 but I spoke to soon

trim atlas
#

Darn give me a minute we will fix it.

harsh harbor
#

Now it's just stuck like this

#

Blinking cursor, I can get into tty

sullen phoenix
harsh harbor
#

KDE

#

Let's see on sec

trim atlas
#

Yo my bad I'm on the phone.

#

I'll brt

harsh harbor
#

startplasma-x11 says failed to connect to x server

harsh harbor
sullen phoenix
#

Can you check out xorg.log?

harsh harbor
#

I usually use Wayland, my bad I'll try Wayland too.

sullen phoenix
harsh harbor
sullen phoenix
#

Can you run this instead

startplasma-wayland > ~/kde_wayland_log.txt 2>&1

Then pastebin the log

If that’s the same output no need to upload

harsh harbor
#

nvidia_drm not nvidia-drm

My typos are going to be the death of me

sullen phoenix
#

can you run one more thing? You can take a picture of this one:

journalctl -b | grep -i wayland

trim atlas
#

Alright dude, my ba

#

bad

harsh harbor
#

🍻

#

Cheer's fella's!

#

👏👏👏

Thank you very much!

sullen phoenix
trim atlas
#

The thread disappeared until now, but congrats brother.

harsh harbor