@Noel Thanks for that.
The pacman log is very useful.
I also used:
ls -l /var/cache/pacman/pkg/lightdm*
inspired by your command to revert the lightdm version, and that showed Feb 6 for the version…2.
I don’t know if there is any overall way to be able to revert the whole system (excluding user data) to a known good point that is commonly or easily used, because of the unintended consequences conundrum, so your pointers are very important, and are noted!
Found the use of this sort of command very useful:
systemctl status lightdm.service | curl -F [email protected] https://ptpb.pw/?u=1
and wondered if they are well used or if there are alternatives.
Also, when grappling with how to get more info, tried
command and saw some text then a black screen, and wanted to know if there is a way to see that text. It probably wasn’t helpful anyway, but still…
After applying latest updates today, after reboot:
Failed to start Light Display Manager
Computer is lenovo R500 (7-8 years old?)
linux is 4.20.6
systemctl status lightdm.service
doesn’t reveal much other than an error has occured
First time there’s been a problem in this area so would like any pointers to finding out how to fix or resolve.
Can get into alt-f2 and log in.
@joekamprad hi just reminded myself that chroot fails as per previous message:
Thought it would be worth trying out the first few commands:
mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot
these worked ok
got the error message:
failed to run command ’ /bin/bash’: Input/output error
Just to check - my system will not boot at all at the moment (panic…)
I am using the laptop with an antergos boot usb stick
I think your two instructions both require the system to be booted normally, not with a usb boot.
Do I somehow have to get the system to boot before I can do anything else or…
I am running antergos very well on an old thinkpad, but I seem to have fallen into a pit of despair with this lenovo ideapad Z710 recently. When I first installed antergos it ran on this laptop perfectly but since a certain time something has changed in the way linux etc is running on it. To my knowledge I haven’t done anything except use it.
If I want to leave a few files in my /home downloads folder can I try to install latest antergos from scratch as a last go before I just take it on the chin and re-install windows 10. I do like to learn but all this is teaching me is that when something goes completely pear shaped you have to know when to throw it away and start afresh.
Here’s my plan…
Anything I can do with my current situation. I am using chromium on the affected laptop right now using antergos usb stick to boot and everything is working perfectly, so I’m happy it’s not a hardware glitch. Do we actually know what the original error means and can I diagnose it further to pin it down? Is the arch-chroot failure I experienced a similar clue to the underlying problem?
Advice on reinstalling antergos over the existing system whilst retaining the /home downloads folder?
Other linux distros that may work better with my setup e.g. manjaro?
back to windows 10.
hi there, I was completely diverted away from computers, and I am just reviewing your last responses. The computer that had the problem has been sitting there exactly as it was, and I just have to get my head round it, and backtrack.
Thanks for your help, and I will resume here shortly.
sudo mount /dev/sda1 /mnt
Oh, I see what you mean - my partition system has /boot on a different partition - doh!
sudo umount /mnt
[[email protected] /]$ sudo mount /dev/sda1 /mnt
[[email protected] /]$ ls
arch bin boot dev etc home lib lib64 mnt opt proc root run sbin srv sys tmp usr var
[[email protected] /]$ cd /mnt
[[email protected] mnt]$ ls
grub initramfs-linux.img initramfs-linux-lts.img lost+found vmlinuz-linux
initramfs-linux-fallback.img initramfs-linux-lts-fallback.img intel-ucode.img memtest86+ vmlinuz-linux-lts
[[email protected] mnt]$
I modified your command to capture the whole file:
[[email protected] boot]$ ls -la /mnt
drwxr-xr-x 18 root root 4096 Mar 12 17:15 .
drwxr-xr-x 1 root root 140 May 13 14:39 …
lrwxrwxrwx 1 root root 7 Jan 5 19:17 bin -> usr/bin
drwxr-xr-x 2 root root 4096 Nov 25 18:05 boot
drwxr-xr-x 2 root root 4096 Nov 25 18:09 dev
drwxr-xr-x 91 root root 4096 May 7 13:42 etc
drwxr-xr-x 4 root root 4096 Nov 25 21:03 home
lrwxrwxrwx 1 root root 7 Jan 5 19:17 lib -> usr/lib
lrwxrwxrwx 1 root root 7 Jan 5 19:17 lib64 -> usr/lib
drwx------ 2 root root 16384 Nov 25 18:04 lost+found
drwxr-xr-x 2 root root 4096 Mar 26 2017 mnt
drwxr-xr-x 6 root root 4096 Feb 11 10:39 opt
drwxr-xr-x 2 root root 4096 Nov 25 18:09 proc
drwxr-xr-x 19 root root 4096 Mar 16 16:59 root
drwxr-xr-x 2 root root 4096 Nov 25 18:09 run
lrwxrwxrwx 1 root root 7 Jan 5 19:17 sbin -> usr/bin
drwxr-xr-x 4 root root 4096 Nov 25 18:09 srv
drwxr-xr-x 2 root root 4096 Nov 25 18:09 sys
drwxr-xr-x 9 root root 4096 Nov 27 14:04 timeshift
drwxr-xr-x 2 root root 4096 Nov 25 18:09 tmp
drwxr-xr-x 10 root root 4096 May 5 18:07 usr
drwxr-xr-x 12 root root 4096 Apr 23 15:46 var