Unable to log in after update, both X and Wayland. (First time in more than two years!)

[anon51566685]

@Mirdarthos

…gave me an error that $DISPLAY wasn’t set

DISPLAY=:0 startplasma-x11

[Mirdarthos]

Tried that. I get:

Authorization required, but no authorization protocol specified

I’m thinking it’s a group?

[Olli]

maybe a small hack but it might work. let’s say you’re actual at stable branch: set pacman-mirrors to unstable and update to unstable branch (same vice-versa if you’re on unstable, switch to stable). with this changing of branches a lot of curious configs are reset.
this trick saved my ass once as i struggled in middle of nowhere.
you can reverse it easy if it doesn’t effect.

[Mirdarthos]

This was actually something I considered, but decided since I have the free time, so I’d rather try and fix it…

[anon51566685]

No, that’s fine. There’s just other sh*t missing. Try logging with new user with sddm. After that try in tty again. Either way, there is something wrong with your config, so start nuking (ok, moving) files to -bak and test test test.

[Mirdarthos]

Yes, I figured this.

I am now logged in to the new user x11…(I tried it previously, but it didn’t work?)

Any specific files or so that I should test removing for mt user’s x11? I don’t really know where to begin…

[Mirdarthos]

The reason for the nouveau driver is because that was in a live environment.

[Olli]

@Mirdarthos

but decided since I have the free time, so I’d rather try and fix

ot but all my respect that you’re such bullheaded !

btw: there is the kde-forum and the devs of kde are more communication-friendly than the devs of manjaro. maybe some of them can give a step into the right direction ? i would give it a try,

KDE Discuss

[Mirdarthos]

@Olli

ot but all my respect that you’re such bullheaded !

Not really. It’s taking a lot of self-discipline not to just reinstall.

@Olli

devs of kde are more communication-friendly than the devs of manjaro

I find this hard to believe, since Manjaro’s is the most friendly forum I’ve come across. Yeah, maybe I don’t get out much, but that is my experience. And besides, I “know” the people here, and they “know” me, so it is a much more…comfortable(?) experience…

[anon51566685]

@Mirdarthos

Any specific files or so that I should test removing for mt user’s x11?

Just one example: Check new user’s dotfiles under home, backup those under your user and copy new user’s over to you. If still not working, repeat, but this time backup and remove any other dotfile.

[Mirdarthos]

FWIW, here is a Xorg log file where I tried logging in with my broken user, followed by logging in with my working user. As of now, I’m still unable to use it…

/var/log/Xorg.0.log

/var/log/Xorg.1.log

journalctl --boot -1 --no-hostname --no-pager | curl -F'file=@-' https://0x0.st

journalctl --boot 0 --no-hostname --no-pager | curl -F'file=@-' https://0x0.st

[MrLavender]

Trouble is, the logs are not giving any real clue about what is causing the problem.

I’d start in ~/.local/share/plasma. Backup and delete (or rename or move) the contents of that directory.

[anon51566685]

You already have all the info you need… and a working system. As I said few times already, start renaming/moving files.

This topic is dragging way longer than it should already and in the end you’ll figure all you had to do was remove .Xauthority or something else which was already in archwiki.

[Mirdarthos]

I couldn’t find the post, just now, but I believe it was @Ben who said that Manjaro is stable, and that any problems that come is because he was unstable.

Well, this is just another case of that. As @zbe also said

@zbe

in the end you’ll figure all you had to do was remove .Xauthority or something else which was already in archwiki.

…and well, no it wasn’t. _{In the Archwiki that is.}

BUT I FOUND IT!!!

_{(And my PC is my biattch again, not me its.)}

As also pointed out by @zbe, my config, (L)user customization was the cause.

I have a problem that my compositor (kwin) crashes, or rather misbehaves when I lock my PC. a Simple restart fixes it, so it’s not the end of the world. Trryiung to automate the process of restarting the compositor on wakeup from suspoend, I created a bash script in:

~/.config/plasma-workspace/env

…to restart the compositor on unlocking my computer.

Well, it turns out I never restarted the computer until about a week later. And by then I’d comp-letely forgotten about the script obviously.

During my attemps to locate the problem, by going through and removing/renaming the files changed within the last 2 weeks, I noticed aand remembered about said script. So, I deleted it, and held my thumbs and rebooted.

I almost burst out in tears when I could actually log in again. But all my settings and customizations were gone. So I decided to restore from Timeshift again, and just deeletee the script beefore rebooting.

AND IT WORKED!!!

I’m back with a working PC again!

Thank you everybody! @zbe, @megavolt, @MrLavender, @bedna, @Olli, @stargazer, @Wollie and anyone I might have missed! You have absolutely NO how much this means to me, or how happy it makes me!

(I chose to award the solution to @zbe because he suggested what I was busy with when I found the problem.)

[MrLavender]

Congrats, glad you got there in the end!

[cscs]

The usual ‘my plasma is weird’ would have applied:
KDE - ArchWiki