Linux @lemmy.ml dysprosium @lemmy.dbzer0.com 9 mo. ago

Manjaro GNOME immediately logs out after logging in (via GUI)

EDIT: I kinda solved it by installing Wayland (with Nvidia card, Ouch!) to replace Xorg. Not sure if this is gonna last though. Perhaps Manjaro is the one I'm gonna throw out FIRST if anything happens from now on.

What should be the first line of defense? Timeshift?

This happened after I installed AUR package masterpdfeditor and 2 applications from github (some hashing algorithm programs, I think they were "Dilithium" and "Latice-based-cryptography-main", one of them was provided by NIST.)

If using GUI: I login, black screen for few seconds, then back at login screen.

If going to ctrl+alt+f2, login successful, then startx, see picture provided (higher quality).

I tried adding a new user, but result is the same.

I have a live usb to do the Timeshift. (I can also chroot if necessary... But I'm not extremely professional)

81 comments

ah classic mistake of installing AUR packages on manjaro. been there done that. check your logs and search for errors, it probably overwrote/deleted some xorg config that you must either manually add back or regenerate. sorry i can't help further im a linux noobie but that was my issue when this happened to me.
- Why would a package called "masterpdfcreator" overwrite the x conf? I don't think the AUR packages have anything to do with the problem.
  
  ah sorry it's more accurate to say it can "break" your xorg config cause that was my case. looking at this package it has libgl as one of its dependencies. as i have said i'm not familiar with how exactly it works but it can probably mess with your graphics drivers.
Most stable Manjaro experience
Start by not using Manjaro. Seriously this won't be the first time this happens to you. It's not a great distro. Consider EndevourOS if you want Arch without the command line install.
- Have you even looked at the picture they posted or do you just reply with nonsense by default when you see the word "Manjaro"?
  
  Yeah the picture looks exactly like my experiences with Manjaro. Thanks
One of your steps should be to throw Manjaro in the trash and install EndeavourOS instead.
- How would their problem be any different on Endeavour? They are circumventing the normal X greeter and starting a custom X session.
- Classic, never fix anything, just change to <my preferred distro>, you wouldnt have experienced any problems, ever
  
  I would usually agree but Manjaro is a broken piece of garbage. Use Arch or Endeavour if you want to gain experience on an arch based distro.
  
  This issue is more than likely caused by Manjaro itself.
  
  So yeah, probably would not have experienced this issue on EndeavourOS, that's right.
If you have it setup timeshift should work...

But please know that the AUR + Manjaro is not a supported or recommend combination. The AUR is intended to be used with the official Arch repos; Manjaro repos are often weeks or sometimes even up to a month behind. Even the Manjaro devs put a warning for this reason.
Not only that, the Manjaro base packages often aren't even built with the same flags as Arch base packages; which is probably what happened here.
Consider using EndeavorOS or archinstall , else this won't be the last time something like this happens.
Manjaro is not up-to-date with Arch repos. Using AUR in Manjaro is a huge mistake.

If you wanna use AUR, I suggest you to go all in with Arch itself

However I still recommend you to use AUR as less as possible, cause too many AUR can mess even with Arch
- I'm using 75 AUR packages without any issues and I've been using Manjaro for 4 years. But I'm really worried now that you've said that. 😬 When should I begin to expect AUR trouble? Does it happen on the 5th year? What if I reinstall, do I get another 4 years?
  
  Good for you. Have you heard about anecdotal evidence already?
- However I still recommend you to use AUR as less as possible, cause too many AUR can mess even with Arch
  
  Based on what?
  
  Based on Arch USER Repository.
  
  AUR packages are maintained by users and can install and overwrite packages in your system and if you install AUR enough, you'll certainly install a package that corrupts your system.
I'm not usually one to blame the distro but... as another comment here has stated, "Most stable manjaro experience". Try EndeavorOS, it's manjaro but not bad.
Have you checked the log files under /var/log/xorg.0....log?

Also see https://wiki.archlinux.org/title/Xorg#Troubleshooting

If you want to get your graphical session back quickly, maybe try setting up GNOME with wayland (https://wiki.archlinux.org/title/GNOME#Wayland_sessions)
- You can also check /var/log/pacman.log for the packages you installed, then pacman -Ql the packages to list what files they might have changed
- I second the wayland option. Then you at least have a working gui with all your settings and recent work intact while you try to find the glitch in your Xorg install.
Ok so clearly none of the people commenting here have even bothered to look at your picture or have no idea what you are doing so feel free to ignore them.

Question 1: what's in your .xinitrc?

Question 2: why are you starting X this way? It's not for beginners, and from your question it doesn't sound like you're an advanced user.
- so I kinda solved it by switching to Wayland. Not sure it lasts since im on proprietary nvidia drivers
- Question 1: what’s in your .xinitrc?
  
  https://www.dropbox.com/scl/fo/ei9hajgzugfs4qnmg9r1f/h?rlkey=bnedoohvpuilvuzqvgmhi7pda&e=2&dl=0
  
  It also contains the logs people mentioned I should check. The Xorg.0* files are from the day of the crash, and 2 days later, when I booted again, the other files were created: Xorg.1*
  
  Question 2: why are you starting X this way?
  
  I was under the impression that startx would just start the GUI regardless what display manager I use (lightdm? not sure), or display server (xorg, x11 in my case) I have installed.
  
  EDIT: it took me wayyy too long to copy these files. Apparently ls -lh does not show hidden files ... I thought my whole laptop went nuts.
  
  it doesn’t sound like you’re an advanced user.
  
  You're god damn right
Don't use startx to start X, use the display manager: systemctl restart lightdm
- It said I not found or something. I'll try again tomorrow for full error message
  
  Permanently Deleted
  
  If you’re using GNOME and not something like xfce, you’re likely using gdm rather than lightdm. GDM is the display manager that ships with GNOME by default
  
  Try ‘systemctl restart gdm’
  
  You can also try ‘systemctl status gdm’ to see what’s going on with your display manager.
- Why?
The problem is that you used Manjaro to begin with. The whole point of being on an arch based distro is to use the AUR. Manjaro tries to make arch more stable by holding back packages, but then because of that, if you install packages from the AUR (which again is the whole point of being on arch), you make Manjaro less stable than Arch itself. So it's a lose lose situation.

If you want to stick to Arch based, either go vanilla Arch or EndeavourOS. Or if you don't care about the AUR but still want updated packages, I can not recommend OpenSuse Tumbleweed enough.
- Please kindly shut up if you're not even going to attempt to help OP. Their issue had nothing to do with the distro.
  
  Allrighty, let's try turning it into "helping". When one finds themselves using manjaro, they should:
  
  Prepare a flash drive with recent arch iso flashed (that shouldn't be strictly necessary, but just in case);
  
  Go to the pacman's mirrorlist and replace their repos with the proper ones (i.e. from arch);
  
  Do a -Syyuu base --overwrite=*;
  
  (optional) In case of trouble, boot to the drive flashed at step 0, make necessary mounts, arch-chroot, solve the problems. One can also try pacstrap-ing instead.
  
  This is a rather high-level overview off the top of my head, and one would likely have to make a few tweaks here and there. Still, I hope it helps :)
https://forum.endeavouros.com/t/graphical-session-doesnt-start-first-time-invalid-mit-magic-cookie-1/5947/8

Check /etc/hostname

This is based on the image, the best you can do it check the logs like other comments said, it's better if the error is identified through the log.
- It's not about the host name. They clearly have invalid mappings in their ~/.Xmodmap (if you'd care to look at the picture).
  
  My comment is based on MIT-MAGIC-COOKIE-1 from the log in the picture. Look at it again and there's also SocketCreateListener() failed. So OP may check this as well
  
  https://wiki.archlinux.org/title/xorg#SocketCreateListener_error
How did you go about installing the other two packages from git? Do you know what directory they were first cloned to? Did you build from source or run an executable like an appimage? Did any of these actions occur prior to the install of masterpdfeditor?
If nothing else, run weston. It's not an amazing wayland server, but it's something.
Run this before startx maybe:

xhost +local:
Check your RAM for errors.
Master PDF Editor is on Flathub. If anything can be installed as a flatpak, I would try that first. If a program fits in a sandbox, consuming the files that I give it and drawing in its own little window, Flatpak has that down cold. If a program wants the ability to stick its hands into the guts of other programs and system services and shared libraries - that should happen at the distro level or not at all.
Broken xorg. Did this appear after changing driver, xorg config, or desktop environment?
If you have LightDM as your display manager, try some other display managers.

You've viewed 81 comments.