So after running sudo pacman -Syu, uninstalling kde plasma 5, and installing lxqt my arch installation simply will not boot, giving me this log:
New picture upload limit is super annoying. I recommend uploading to somewhere else first and pasting a link.
Have you tried other shells? Seems like maybe you broke your current shell.
did you enable the display manager in Systemctl? when switching Desktop enviornments you have the option to choose a display manager.. it doesn't enable itself by default. you must enable it via systemctl.
I think i tried sh (though I am not sure. Just to be sure ill try again later), i havent tried zsh yet
And @Kat I disabled sddm before i removed it with plasma. It doesnt seem to be the dm as it doesnt even start the terminal login shell
SDDM is a display manager lol.
if you installed lxqt then type in
then
Dont worry I know that sddm is a display manager. My point was that because i have no dm enabled, it should take me to the command line login but it doesnt even do that. In fact it doesnt even start the ssh daemon. And because pacman wont do anything, i cant reinstall sddm (i think i competely removed it for the time being), and because almost nothing in chroot works im sure i wont be able to use systemd to enable it either but ill try
https://wiki.archlinux.org/index.php/Linux_Containers#root_login_fails
If your journalctl output is different I'm sure some else could help.
@eidolonFIRE,
I have now tried zsh, sh, and bash and none of them seem to be working
@Kat,
Just like I thought, I am unable to access systemd from the chroot Environment, though I forgot that this is the case with chroots in general
@blorgajork Ill try this tomorrow as today there may not be enough time. However I've had lxc containers disabled for a while now and its only the lxc bridge that I havent been able to competely disable but it has caused any issues. I thinks its probably not the problem but at this point Id try anything
Are you per chance using AMD Crimson?
This did start as soon as you uninstalled KDE and disabled SDDM?
Why would you need to uninstall KDE?
he uninstalled KDE and disabled SDDM. that will take him to BASH everytime he loads up his PC.
Yes indeed. I uninstalled KDE, disabled SDDM, and installed LXQt
Because I want to give LXQt a try and I prefer to have as few DEs on my system as possilbe. And no, I'm not using AMD Crimson, I'm using the open source amdgpu driver
If logind is unable to start, neither do emacs and pacman, maybe they've got an underlying issue. libresolv is missing. If you're able to, could you run an journalctl -xe (which I doubt will work)? It will probably point out that the issue is with libresolve missing.
Are you certain that your upgrade actually worked?
edit: one possible solution (should at least give you something to work with) could be to reinstall the base group (mount the root partition, pacstrap /mnt base).
emacs has quite a few dependencies, it is very likely that removing those packages might have removed something important. Can you look at the pacman log file in /var?
Damn, installing the base system worked! Thank you so much!
So did you got LXQT to boot?
It's not the base system per se. base is a package group containing multiple packages, which includes glibc, which provides libresolve.
When I realised that libresolve is a part of glibc I thought you might be missing more packages, or have some corrupt libraries/programs, so you might as well reinstall base to have... well, a base.
glibc is the GNU libc -- or c standard library. Try running running pacman -Qi glibc | egrep 'Required By.*', and you'll see what packages require glibc. Then for giggles you can try run pacman -Qi linux | egrep 'Required By.*' to see which require linux ;)
I did but I just encountered another problem. Firefox and chrome/chromium won't start. When I try to run chromium in the terminal (I haven't tried it yet for firefox though I'm assuming it's probably similar) it gives me the following error:/usr/lib/chromium/chromium: error while loading shared libraries: libsmime3.so: cannot open shared object file: No such file or directory
However I think I'll able to fix these on my own though I'll say something if I need help or if I've fixed it.
And @kiipa base group is the word I was looking but thanks a lot for the explanation
