Booting to a blank screen (just with a mouse pointer)

Support
1

namo vaH!

Booting to a blank screen with just a mouse pointer. I need to do Ctrl Alt F2, log into the text console and run startx.

Problem remains even if I install and switch to lxdm.

Please help :pray:

More Logs here (from manjaro-log-helper ) - dpaste DOT ORG / 50WnS
but summary below:

journalctl -b 0 -p err 

Jan 10 21:28:23 vvasuki-1803 (udev-worker)[376]: event16: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
Jan 10 21:28:23 vvasuki-1803 (udev-worker)[376]: event16: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
Jan 10 21:28:23 vvasuki-1803 (udev-worker)[376]: event16: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
Jan 10 21:28:23 vvasuki-1803 (udev-worker)[376]: event16: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
Jan 10 21:28:23 vvasuki-1803 (udev-worker)[376]: event16: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
Jan 10 21:28:24 vvasuki-1803 kernel: 
Jan 10 21:28:24 vvasuki-1803 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  545.29.06  Thu Nov 16 01:59:08 UTC 2023
Jan 10 21:28:26 vvasuki-1803 colord-sane[731]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Jan 10 21:28:29 vvasuki-1803 kernel: nvme0n1: Read(0x2) @ LBA 108282976, 256 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) 
Jan 10 21:28:29 vvasuki-1803 kernel: critical medium error, dev nvme0n1, sector 108282976 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
Jan 10 21:28:29 vvasuki-1803 kernel: nvme0n1: Read(0x2) @ LBA 108283000, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) 
Jan 10 21:28:29 vvasuki-1803 kernel: critical medium error, dev nvme0n1, sector 108283000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Jan 10 21:28:29 vvasuki-1803 kernel: nvme0n1: Read(0x2) @ LBA 108283000, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) 
Jan 10 21:28:29 vvasuki-1803 kernel: critical medium error, dev nvme0n1, sector 108283000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Jan 10 21:28:30 vvasuki-1803 kernel: nvme0n1: Read(0x2) @ LBA 108283000, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) 
Jan 10 21:28:30 vvasuki-1803 kernel: critical medium error, dev nvme0n1, sector 108283000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Jan 10 21:28:30 vvasuki-1803 kernel: nvme0n1: Read(0x2) @ LBA 108283000, 8 blocks, Unrecovered Read Error (sct 0x2 / sc 0x81) 
Jan 10 21:28:30 vvasuki-1803 kernel: critical medium error, dev nvme0n1, sector 108283000 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Jan 10 21:28:30 vvasuki-1803 systemd-coredump[835]: [🡕] Process 827 (mutter-x11-fram) of user 120 dumped core.
                                                    
                                                    Stack trace of thread 828:
                                                    #0  0x00007fa07e00c07c n/a (libfreetype.so.6 + 0x9707c)
                                                    #1  0x00007fa07dfc53db n/a (libfreetype.so.6 + 0x503db)
                                                    #2  0x00007fa07dfa4b31 n/a (libfreetype.so.6 + 0x2fb31)
                                                    #3  0x00007fa07df87b04 n/a (libfreetype.so.6 + 0x12b04)
                                                    #4  0x00007fa07df8d764 n/a (libfreetype.so.6 + 0x18764)
                                                    #5  0x00007fa07df8e140 FT_New_Face (libfreetype.so.6 + 0x19140)
2

Some of the files needed for the display manager may not be readable anymore, causing it to fail.
Whatever the case, the above looks alarming to me.
Your disk may be on it’s way out.
Back up your data if you have not done so already.

1 Like
3

Some of the files needed for the display manager may not be readable anymore, causing it to fail.

Never touched those files. How to fix??

4

Do backup before it is to late !

After that it may be time to search for the reason.

5

You have errors reading random files from your nvme “disk”.
This looks like the hardware is broken.
But that is just speculation.
Focus on getting your data off the disk, then think about checking it.

I do not know how to check the disk for errors - probably use smartctl in some form.

6

You have errors reading random files from your nvme “disk”.

Well, I’ve been doing lot of editing on the very same disk without any problems; and have been running startx off it, typing this message on chrome which I run off it etc… I was hoping that reinstalling something (already tried gdm) should suffice to solve the login problem.

7

Well, if you’d rather gamble - go right ahead.
It’s your system and your data.
I have nothing more to say.

8

Did you power off your system with the power button instead of shutdown?
You may use a live Cd, do a fsck on it and afterwards a smartctl -H /dev/nvme0n1

It happened to me once, that X didnt start anymore after a forced shutdown, but fsck did help.
Else, if your ssd passes at smartctl, you may have to reinstall some files.

And btw, backups are never a wrong thing.

9

I might’ve … sometimes after not shutting down for many days/ weeks, the computer acts up and I’m forced to (hard) reboot.

Done, here are the results:

    ~  sudo fsck /dev/nvme0n1p1                                                                     8 ✘ 
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
/dev/nvme0n1p1: 0 files, 1/523262 clusters
    ~  sudo fsck /dev/nvme0n1p2                                                                       ✔ 
fsck from util-linux 2.38.1
    ~  sudo fsck /dev/nvme0n1p3                                                                       ✔ 
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
/dev/nvme0n1p3: clean, 889179/17301504 files, 20830233/69206016 blocks
    ~  sudo fsck /dev/nvme0n1p4                                                                       ✔ 
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
/dev/nvme0n1p4: clean, 6142154/42852352 files, 146856438/171407872 blocks

    ~  sudo smartctl -H /dev/nvme0n1p1                                                                ✔ 
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.60-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

    ~  sudo smartctl -H /dev/nvme0n1p2                                                                ✔ 
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.60-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

    ~  sudo smartctl -H /dev/nvme0n1p3                                                                ✔ 
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.60-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

    ~  sudo smartctl -H /dev/nvme0n1p4                                                                ✔ 
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.60-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Didn’t mind this -

sudo e2fsck /dev/nvme0n1                                                                       ✔ 
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

How??

Important files are all backed up - I just hope I don’t have reinstall the operating system.

10

Each time when you dont soft shutdown your system, fsck will run. Thats somehow an advantage from EXT4, that its always in good shape. But when you dont run it, it also can prevent it that the system loads normal.
If you Desktop acts weird after a while, you can try to switch to a tty with ctl+alt+F1 - F6
and type there reboot or systemctl reboot or systemctl halt or the classic shutdown -r now
Then it should cause lesser problems at restart.

Do it. From a live usb.

e2fsck -b 8193 /dev/nvme0n1
or
e2fsck -b 32768 /dev/nvme0n1

That one really can cause, that it doesnt load your system and only drops you to this emergency terminal.

For may damaged files was a topic here how to check the integrity.
I got lately a similar problem with my files and used pacman -Qkk |less and did reinstall over a second terminal the files, even as mentioned, it gives a few false positives, but pacman -Dk seems is a good way too.
https://forum.manjaro.org/t/is-there-a-command-or-program-that-check-the-integrity-of-the-installation-files/155123/2

Well, reinstalling isnt a big problem for me anymore.
I got my /home on a seperate partition, at the installation, i do manually partitioning, bind my home partition and a swap partition to the system, use the same user and password and you will get the same as you had before, only with a new installation with the same desktop settings, what takes about 10 minutes with the faster hdd’s.

11 
e2fsck -b 8193 /dev/nvme0n1
or
e2fsck -b 32768 /dev/nvme0n1

That one really can cause, that it doesnt load your system and only drops you to this emergency terminal.

Both return the same Bad magic number stuff. Please note that I am not dropped into the emergency terminal. I just need to do Ctrl Alt F2, login and do startx.

pacman -Qkk

Only these altered files were noted:

audit: 208 total files, 7 altered files
bluez: 51 total files, 1 altered file
bolt: 32 total files, 1 altered file
cdrtools: 148 total files, 4 altered files
backup file: cups: /etc/cups/printers.conf (Modification time mismatch)
backup file: cups: /etc/cups/printers.conf (Size mismatch)
backup file: cups: /etc/cups/subscriptions.conf (Modification time mismatch)
backup file: cups: /etc/cups/subscriptions.conf (Size mismatch)
cups: 942 total files, 13 altered files
cups-pdf: 17 total files, 1 altered file
dbus: 91 total files, 1 altered file
expat: 32 total files, 2 altered files
backup file: filesystem: /etc/crypttab (Modification time mismatch)
backup file: filesystem: /etc/crypttab (Size mismatch)
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (MD5 checksum mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (MD5 checksum mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/hostname (Modification time mismatch)
backup file: filesystem: /etc/hostname (Size mismatch)
backup file: filesystem: /etc/hostname (MD5 checksum mismatch)
backup file: filesystem: /etc/hostname (SHA256 checksum mismatch)
backup file: filesystem: /etc/hosts (Modification time mismatch)
backup file: filesystem: /etc/hosts (Size mismatch)
backup file: filesystem: /etc/hosts (MD5 checksum mismatch)
backup file: filesystem: /etc/hosts (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (MD5 checksum mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (MD5 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (MD5 checksum mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
filesystem: 125 total files, 7 altered files
backup file: gdm: /etc/gdm/custom.conf (Modification time mismatch)
backup file: gdm: /etc/gdm/custom.conf (Size mismatch)
backup file: gdm: /etc/gdm/custom.conf (MD5 checksum mismatch)
backup file: gdm: /etc/gdm/custom.conf (SHA256 checksum mismatch)
gdm: 517 total files, 6 altered files
geoclue: 116 total files, 1 altered file
ghc-libs: 1447 total files, 1 altered file
backup file: glibc: /etc/locale.gen (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Size mismatch)
backup file: glibc: /etc/locale.gen (MD5 checksum mismatch)
backup file: glibc: /etc/locale.gen (SHA256 checksum mismatch)
gnome-control-center: 599 total files, 1 altered file
backup file: grub: /boot/grub/grub.cfg (Modification time mismatch)
backup file: grub: /boot/grub/grub.cfg (Size mismatch)
backup file: grub: /etc/default/grub (Modification time mismatch)
backup file: grub: /etc/default/grub (Size mismatch)
backup file: grub: /etc/default/grub (MD5 checksum mismatch)
backup file: grub: /etc/default/grub (SHA256 checksum mismatch)
grub: 1350 total files, 1 altered file
gutenprint: 542 total files, 1 altered file
gvfs: 333 total files, 1 altered file
hplip: 2408 total files, 2 altered files
intellij-idea-ultimate-edition: 2458 total files, 615 altered files
intellij-idea-ultimate-edition-jre: 483 total files, 73 altered files
java-runtime-common: 21 total files, 2 altered files
libutempter: 20 total files, 1 altered file
libxext: 100 total files, 3 altered files
backup file: lightdm: /etc/lightdm/lightdm.conf (Modification time mismatch)
backup file: lightdm: /etc/lightdm/lightdm.conf (Size mismatch)
backup file: lightdm: /etc/lightdm/lightdm.conf (MD5 checksum mismatch)
backup file: lightdm: /etc/lightdm/lightdm.conf (SHA256 checksum mismatch)
lightdm: 388 total files, 1 altered file
linux515: 6638 total files, 10 altered files
linux66: 7185 total files, 10 altered files
m17n-db-indic: 624 total files, 28 altered files
manjaro-firmware: 260 total files, 133 altered files
manjaro-zsh-config: 91 total files, 1 altered file
backup file: mkinitcpio: /etc/mkinitcpio.conf (Modification time mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (Size mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (MD5 checksum mismatch)
backup file: mkinitcpio: /etc/mkinitcpio.conf (SHA256 checksum mismatch)
networkmanager: 514 total files, 1 altered file
nfs-utils: 124 total files, 4 altered files
openssh: 63 total files, 1 altered file
backup file: pacman: /etc/pacman.conf (Modification time mismatch)
backup file: pacman: /etc/pacman.conf (Size mismatch)
backup file: pacman: /etc/pacman.conf (MD5 checksum mismatch)
backup file: pacman: /etc/pacman.conf (SHA256 checksum mismatch)
backup file: pacman-mirrors: /etc/pacman-mirrors.conf (Modification time mismatch)
backup file: pacman-mirrors: /etc/pacman-mirrors.conf (Size mismatch)
backup file: pacman-mirrors: /etc/pacman-mirrors.conf (MD5 checksum mismatch)
backup file: pacman-mirrors: /etc/pacman-mirrors.conf (SHA256 checksum mismatch)
pacman-mirrors: 356 total files, 1 altered file
backup file: pam: /etc/environment (Modification time mismatch)
backup file: pam: /etc/environment (Size mismatch)
backup file: pam: /etc/environment (MD5 checksum mismatch)
backup file: pam: /etc/environment (SHA256 checksum mismatch)
pam: 563 total files, 1 altered file
backup file: polkit: /etc/pam.d/polkit-1 (Modification time mismatch)
backup file: polkit: /etc/pam.d/polkit-1 (Size mismatch)
backup file: polkit: /etc/pam.d/polkit-1 (MD5 checksum mismatch)
backup file: polkit: /etc/pam.d/polkit-1 (SHA256 checksum mismatch)
polkit: 217 total files, 1 altered file
sanskrit-fonts: 115 total files, 12 altered files
backup file: shadow: /etc/default/useradd (Modification time mismatch)
backup file: shadow: /etc/default/useradd (Size mismatch)
shadow: 588 total files, 2 altered files
backup file: sudo: /etc/pam.d/sudo (Modification time mismatch)
backup file: sudo: /etc/pam.d/sudo (Size mismatch)
backup file: sudo: /etc/pam.d/sudo (MD5 checksum mismatch)
backup file: sudo: /etc/pam.d/sudo (SHA256 checksum mismatch)
sudo: 239 total files, 1 altered file
system-config-printer: 487 total files, 1 altered file
systemd: 1455 total files, 2 altered files
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Modification time mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (Size mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (MD5 checksum mismatch)
backup file: texlive-basic: /etc/texmf/web2c/fmtutil.cnf (SHA256 checksum mismatch)
vlc: 1084 total files, 1 altered file
zziplib: 70 total files, 0 altered files

I got my /home on a seperate partition, at the installation, i do manually partitioning, bind my home partition and a swap partition to the system, use the same user and password and you will get the same as you had before, only with a new installation with the same desktop settings, what takes about 10 minutes with the faster hdd’s.

I can do the same, but I fear for the wasted time setting up all the extra software + python etc… libraries I’ve installed and configured separately. Is there a way to avoid formatting the root partition while reinstalling?

12

You packages dont look bad. These errors are only, because some files are changed after they been installed like config files. I would say, thats not a problem. You still can do a pacman -Dk and see, what it says.

But try again fsck dev/nvme0n1
You did fsck the partitions P1-P4 on your sdd, but not the main drive.
If you are starting from it, you have no other chance as to make a live usb, start from there, and then run fsck, because it always will be mounted.

if it complains then again then try to run e2fsck -b 32768 /dev/nvme0n1
because the first choice is to use fsck or e2fsck without the backups, and if the superblock is corrupt, then use the one what is stored at 8193 or 32768.
There should be still more, but usually the one at 32768 works most of the time.

What desktop are you using, because for XFCE you use startxcfe4.
Not sure if that will load your desktop, also, seems you have 2 display manager installed.
Are you sure they load?
You can check it with systemctl status lightdm
Not sure, if you want switch to gdm, since you have installed it, but you would have to activate it via systemctl

But first, see if you can fsck it and it does not have errors.

You can make a backup list from your installed packages, even its maybe not optimal, since you write, you have changed some libs by yourself.
At section 2,5, 2,6 ist more about that
https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#List_of_installed_packages

13

Haven’t yet run fsck, but in the meantime, I’ve temporarily got past the problem by simply setting up automatic login on gdm (I had tried a couple of other DMs, including lightdm IIRC - but failed to get past the “stuck at cursor” problem; also tried uncommenting # WaylandEnable=false, but failed ).

Here’s what my /etc/gdm/custom.conf looks like:

# GDM configuration storage

[daemon]
AutomaticLoginEnable=True
AutomaticLogin=MYUSERNAME
# Uncomment the line below to force the login screen to use Xorg
# WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

So, the problem seems to be software related, rather than anything to do with hardware.

(The automatic login solution is not ideal - don’t want burglers or kids messing under my username - but I’m stuck! Atleast I wont have to run gnome-keyring-daemon manually every time after startx and make do with “upload file” dialogs on browsers not working etc…)

14

You may can reinstall your displaymanager and see if it fix it.
You could also save all your packages to a file and reinstall them as at the link above.
You also can manually activate a display manager like here
https://wiki.manjaro.org/index.php?title=Install_Display_Managers

I could think on more things, what did go wrong, broken Kernel, broken video modules, broken displaymanager.

But mainly try to do the fsck first and make sure, the drive has no errors, because if there is a problem, it can cause more problems by installing anything else.

15

Already done - no use.

I could think on more things, what did go wrong, broken Kernel, broken video modules, broken displaymanager.

Let’s move on to this then, if you don’t mind (I am, at this point, skeptical about a hardware problem and am tired of the reboots now that I have a temporary solution. )

16 
e2fsck -b 8193 /dev/nvme0n1
or
e2fsck -b 32768 /dev/nvme0n1

This can’t work.

You try to run the command on the whole device instead of a partition on it.
Also it will only work when the file system on the partition actually is ext2/3/4.

17

Ah - got it. All checked then. For reference, the disk is as shown:

image
image717×429 31.1 KB