I’ve run into a serious anomaly. This if for the MNJ-ARC KDE.
Upgraded my gfx card from an RX 480 to a RX 7600. During this time, my PC was dormant for 4 months.
Obviovsly, couldnt perform any updates etc…
This was due to a motherboard 12v short, that in turn also shortrd my Corsair 750 W PSU. And since I was getting a new PSU, I decided to get a new gfx card as well.
After upgrading the gfx card, I tried to boot to MNJ (I have a dual boot setup. Both OS’es boot from their individual hard disks.
I see the screen of the (xxxx/xxxxx) files cleaned & so on, but the graphical interface doesnt load at all. The terminal is accessible via ALT+F2, F3,…
I had also noticed an xserver error.
Upon startx, it returns with:
init: giving up
unable to connect to X server: Connection refued. (attached).
I then decided to boot MNJ through a LIVE ISO setup. Its an older image I had burnt on an USB.
Still did not go all the way through. The LIVE-ISO screen freezes on:
‘failed to start Light Display Manager’
My Windows 10 boots just fine.
Please let me know if I can provide with more details.
Could anyone help me with this situation? That’ll be great!
What sort of an inconsistency is this? Very strange!
I had a couple of months off my main machine a while back… I’m not sure if anyone’s going to chime in here with a quick dirty fix - I’d probably be lazy to recover it and opt to go with a fresh installation and recover settings from the last backup.
If you don’t have that, then you just learned the lesson - and can appreciate why I always check that I have BTRFS snapshots running to keep a couple of ‘instant’ snapshots on my main disk, as well as an rsync backup to keep something more wholesome on my storage disk.
Failing this, get yourself a fresh ISO, and use that to recover any valuable stuff from your existing system before doing a clean install.
Have you tried chrooting into your installed system and running the upgrade from there? manjaro-chroot -a sudo pacman-mirrors -f sudo pacman -Syyu (I think the second “y” might be needed)
Pacman may report errors due to the installation being stale (dependency issues etc.). In that case, you can try adding the --nodeps option.
There is a lack of information and a lot of similarity with an xyproblem - where you seek solution for a failed attempt to solve which makes it inherently difficult to understand and difficult to provide any meaningful response
why is it you are referring to LightDM display manager when using Plasma?
did you manage to LightDm working before the change of hardware
what is the output from (as text please - with codefence - not quote - but codefence)
Assuming you had the unusual lightdm working as displaymanager for plasma before the change of hardware - so I won’t say anything about that.