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)
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
One of your steps should be to throw Manjaro in the trash and install EndeavourOS instead.
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.
How would their problem be any different on Endeavour? They are circumventing the normal X greeter and starting a custom X session.
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
I’ve always suspected that Manjaro detractors might be mostly Linux beginners who do stupid stuff then give up at the first sign of trouble.
You’re not exactly doing your best to change my mind.
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.
So what if they’re behind. AUR packages have dependency requirements too. They won’t install if dependencies are not met. Unless you force it — but that wouldn’t be their fault.
So how can an AUR package break something if it’s not installed?
It’s called a -bin AUR package being complied against the latest dependencies, but when run it finds an old version that makes the program in question have undefined behavior.
Not even single AUR package has=requirements defined properly in the PKGBUILD, it’s just the nature of the AUR.
There’s all kinds of bugs that can & do occur when a package expects one thing, but finds another. It’s really just that simple.
Not only that, the Manjaro base packages often aren’t even built with the same flags as the Arch base packages; which is probably what happened here.
I’ve even had to create special patching mechanisms myself do to flag incompatibilities in base packages.If an installed AUR package breaks due to distro binary package shift, you rebuild it and that’s it.
If it’s an AUR package that downloads a binary, those binaries are typically made to work on a wide variety of environments.
Not even single AUR package has >= requirements defined properly in the PKGBUILD, it’s just the nature of the AUR.
“What if the package has incorrect dependencies” — seriously, that’s your argument?
Well it would have been a crappy package anyway, no? It will break sooner or later, on Arch or Manjaro or any distro. You rebuild it and move on.
First of all generalizing about this is totally wrong, depending on what software/libraries a program depends on for build makes a huge difference. If it is good old C that is backwards compatible (hence the size of glibc) it will work all the time. Show me one debian or arch official package that is written in C and says for glibc >=2.35
On other software proposing a library to be >=ver-xxx means the packager speculates that future editions will NOT break the build.
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
deleted by creator
Check your RAM for errors.
deleted by creator
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 trypacstrap-inginstead.
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 :)
What you described would ruin a perfectly good install. It’s like installing Ubuntu then switching the repos to Debian and force overwriting installed files. Why not just install Debian (or Arch, in this case)?
I wonder how many people follow “well meaning” advice like this then blame Manjaro.
Well, that’s kinda how I once converted my artix to arch (skipping a few f-ups on my part and the caveats of switching init), so I’m pretty sure it can work… Although I can try this in a VM if I have some spare time
It may work but there’s no point in doing it. You get something that’s neither proper Arch nor Manjaro.
Manjaro is built around a branch which doesn’t exist in Arch, unlike other Arch derivates, and mixing the installed Manjaro packages with Arch packages can lead to unpredictable results.
That’s why you change the repos, tho, instead of mixing those from arch and manjaro, and do overwrites to avoid trouble with their configs. Also, I have a feeling pacman tells you when a package managed by it is no longer in the repos, so you just remove it to not accidentally take part in another round of ddos-ing aur or whatever manjaro’s packages currently do for fun.
As for why, that’s just to avoid setting up everything from scratch
Check
/etc/hostnameThis 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-1from the log in the picture. Look at it again and there’s alsoSocketCreateListener() failed. So OP may check this as wellhttps://wiki.archlinux.org/title/xorg#SocketCreateListener_error
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
startxwould 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 -lhdoes 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
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.
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 orarchinstall, else this won’t be the last time something like this happens.Run this before startx maybe:
xhost +local:If nothing else, run weston. It’s not an amazing wayland server, but it’s something.
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?
If you have LightDM as your display manager, try some other display managers.
