Hello,
I've been using Zorin OS for several years by now, mostly without issues, but after sending my Slimbook laptop to the manufacturer for a screen replacement I can no longer login into the graphical interface... On both on Wayland and Xorg it crashes and sends me back to the login page.
On tty3 I can login fine... Can someone help me? I am still not a Linux expert. :-/
I am on Zorin 17.3 Pro BTW, when the upgrade path to 18 was released the laptop was out for the repair.
Hello,
did you try to plug another screen on your laptop (TV or monitor) ?
No, but the screen works, I can see the login screen fine.
BTW, I have updated the packages from tty3, and then rebooted the system. Yet nothing changed.
OK let's see that:
Access Terminal
- Corrupted User Configuration
Very common after a hardware repair/replacement.
Broken files in ~/.config or ~/.cache
mv ~/.config ~/.config.backup
mv ~/.cache ~/.cache.backup
Then try logging in again.
- Broken GNOME Extensions
mv ~/.local/share/gnome-shell/extensions ~/.local/share/gnome-shell/extensions.backup
- Graphics Drivers (VERY likely after a screen repair).
Check:
sudo ubuntu-drivers devices
Reinstall the drivers:
sudo ubuntu-drivers autoinstall
- Broken GNOME Shell
Reinstall:
sudo apt update
sudo apt install --reinstall gnome-shell gnome-session zorin-os-desktop
1 Like
Isn't it zorin-os-desktop or zorin-os-desktop-pro for the Pro version in the last command?
yeah you are right, I made correction
I tried all of your list, but nothing worked.
About the broken GNOME Extensions, I have no file named "extensions" or "extensions.backup" in the specified path?
You can try to reinstall gdm:
sudo apt install --reinstall gdm3
Unfortunately reinstalling gdm3 did not work either...
Is it possible to upgrade to 18 from the console commands? And could doing so fix this issue?
The HAL9000 runs Linux ... I didn't know that.
But to be serious: Did You checked if in BIOS Secure Boot and Fast Boot are disabled? Do You still have a Bootstick with Zorin on it? If yes, I would suggest to start it and run it in Live Mode. then search for ''Boot Repair'' and let it run.
1 Like
Checked, both disabled. I've tried to run Zorin live from the bootstick as you suggested a do a boot repair but it returns an error.
It would be good to know the whole Output. From what You have posted, it looks like You use the zfs File System and Boot Repair doesn't like that.
Are you using Nvidia card? After a screen replacement, you would need to fully remove and reinstall the Nvidia driver.
nope, it is a laptop with an AMD APU.
this is the full output
boot-repair-4ppa2056-zorin1 [20260318_1845]
============================== Boot Info Summary ===============================
=> No boot loader is installed in the MBR of /dev/nvme0n1.
nvme0n1p1: _____________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /grub/grub.cfg /efi/BOOT/fbx64.efi /efi/BOOT/mmx64.efi
/efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi
/efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg
nvme0n1p2: _____________________________________________________________________
File system:
Boot sector type: Unknown
Boot sector info:
nvme0n1p3: _____________________________________________________________________
File system: zfs_member
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
nvme0n1p4: _____________________________________________________________________
File system: zfs_member
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sda: ___________________________________________________________________________
File system: iso9660
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.
================================ 0 OS detected =================================
================================ Host/Hardware =================================
CPU architecture: 64-bit
Video: Advanced Micro Devices, Inc. [AMD/ATI] from Advanced Micro Devices, Inc. [AMD/ATI]
Live-session OS is Zorin 64-bit (Zorin OS 17.1, jammy, x86_64)
===================================== UEFI =====================================
BIOS/UEFI firmware: SLIMH6.05(0.5) from American Megatrends Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0002
Timeout: 5 seconds
BootOrder: 0001,0002,0000
Boot0000* Windows Boot Manager VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* ubuntu HD(1,GPT,35dd375d-f724-4cc1-a7bf-22598a1fe312,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* UEFI: SMI USB DISK 1100 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(1,0)/USB(0,0)/CDROM(1,0x24c,0x9e00)..BO
1d43d986c265d8c455d020e4a1f28c52 nvme0n1p1/BOOT/fbx64.efi
1d260ff1255f189ab621209796ee2fed nvme0n1p1/BOOT/mmx64.efi
1535d97a530fe1aa6f0d87717547d309 nvme0n1p1/ubuntu/grubx64.efi
1d260ff1255f189ab621209796ee2fed nvme0n1p1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e nvme0n1p1/ubuntu/shimx64.efi
07e25dcaf57c776875f78fa36827c58e nvme0n1p1/BOOT/BOOTX64.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
nvme0n1 : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, no-os, no-wind, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
nvme0n1p1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, grubenv-ok, noupdategrub, not-far
nvme0n1p3 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme0n1p4 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
nvme0n1p2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
Partitions info (2/3): _________________________________________________________
nvme0n1p1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p4 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
Partitions info (3/3): _________________________________________________________
nvme0n1p1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p3 : is--zfs-boot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p4 : maybesepboot, with-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p2 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
fdisk -l (filtered): ___________________________________________________________
Disk nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk identifier: 8D606AF5-8B23-43EB-BE52-ABDD991D2F65
Start End Sectors Size Type
nvme0n1p1 2048 1050623 1048576 512M EFI System
nvme0n1p2 1050624 5244927 4194304 2G Linux swap
nvme0n1p3 5244928 9439231 4194304 2G Solaris boot
nvme0n1p4 9439232 3907029134 3897589903 1.8T Solaris root
Disk sda: 7.28 GiB, 7811891200 bytes, 15257600 sectors
Disk identifier: 0x37b78376
Boot Start End Sectors Size Id Type
sda1 * 0 13392287 13392288 6.4G 0 Empty
sda2 588 10699 10112 4.9M ef EFI (FAT-12/16/32)
sda3 13393920 15257599 1863680 910M 83 Linux
Disk zd0: 500 MiB, 524288000 bytes, 1024000 sectors
parted -lm (filtered): _________________________________________________________
sda:7812MB:scsi:512:512:msdos:SMI USB DISK:;
2:301kB:5478kB:5177kB:::esp;
3:6858MB:7812MB:954MB:ext4::;
nvme0n1:2000GB:nvme:512:512:gpt:Samsung SSD 980 PRO 2TB:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:2685MB:2147MB:::swap;
3:2685MB:4833MB:2147MB:zfs::;
4:4833MB:2000GB:1996GB:zfs::;
zd0:524MB:unknown:512:16384:unknown:Unknown:;
Free space >10MiB: ______________________________________________________________
sda: 5.22MiB:6540MiB:6535MiB
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda iso9660 2024-04-10-23-27-34-00 Zorin OS 17.1 Pro 64bit
├─sda1 iso9660 2024-04-10-23-27-34-00 37b78376-01 Zorin OS 17.1 Pro 64bit
├─sda2 vfat 0564-ADD8 37b78376-02
└─sda3 ext4 a87bea6c-c67a-4144-a1ef-caba4659023b 37b78376-03 writable
zd0 crypto_LUKS ec25322a-fcda-499c-959a-da27b7fb5b14
nvme0n1
├─nvme0n1p1 vfat 54EA-E164 35dd375d-f724-4cc1-a7bf-22598a1fe312 EFI System Partition
├─nvme0n1p2 71513cd8-e432-1749-9c3a-a8e8c47d72fa
├─nvme0n1p3 zfs_member 11506538145121718510 ee6f1635-cb1b-184c-a193-02548c140a64 bpool
└─nvme0n1p4 zfs_member 9023266459664424678 a5e58618-1165-9f44-9085-8a82b0c2c6d2 rpool
Mount points (filtered): _______________________________________________________
Avail Use% Mounted on
bpool/BOOT/ubuntu_tl4976 1.3G 23% /mnt/boot-sav/zfs/boot
/dev/disk/by-label/writable[/install-logs-2026-03-18.1/crash] 808.9M 1% /var/crash
/dev/disk/by-label/writable[/install-logs-2026-03-18.1/log] 808.9M 1% /var/log
/dev/nvme0n1p1 492.5M 4% /mnt/boot-sav/nvme0n1p1
/dev/sda1 0 100% /cdrom
efivarfs 78.6K 35% /sys/firmware/efi/efivars
Mount options (filtered): ______________________________________________________
====================== nvme0n1p1/grub/grub.cfg (filtered) ======================
Revert system only gnulinux-${root_dataset}-${kversion}
Revert system and user data gnulinux-${root_dataset}-${kversion}
Zorin OS 17.3 gnulinux-rpool/ROOT/ubuntu_tl4976-6.8.0-106-generic
Zorin OS 17.3, with Linux 6.8.0-106-generic gnulinux-rpool/ROOT/ubuntu_tl4976-6.8.0-106-generic
Zorin OS 17.3, with Linux 6.8.0-90-generic gnulinux-rpool/ROOT/ubuntu_tl4976-6.8.0-90-generic
END /etc/grub.d/30_os-prober
UEFI Firmware Settings uefi-firmware
END /etc/grub.d/30_uefi-firmware
=================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================
search.fs_uuid 54EA-E164 root
set prefix=($root)'/grub'
configfile $prefix/grub.cfg
================= nvme0n1p1: Location of files loaded by Grub ==================
GiB - GB File Fragment(s)
?? = ?? grub/grub.cfg 1
================= nvme0n1p3: Location of files loaded by Grub ==================
GiB - GB File Fragment(s)
?? = ?? vmlinuz
?? = ?? vmlinuz-6.8.0-106-generic
?? = ?? vmlinuz-6.8.0-90-generic
?? = ?? vmlinuz.old
?? = ?? initrd.img
?? = ?? initrd.img-6.8.0-106-generic
?? = ?? initrd.img-6.8.0-90-generic
?? = ?? initrd.img.old
================= nvme0n1p4: Location of files loaded by Grub ==================
GiB - GB File Fragment(s)
?? = ?? boot/vmlinuz
?? = ?? boot/vmlinuz-6.8.0-106-generic
?? = ?? boot/vmlinuz-6.8.0-90-generic
?? = ?? boot/vmlinuz.old
?? = ?? boot/initrd.img
?? = ?? boot/initrd.img-6.8.0-106-generic
?? = ?? boot/initrd.img-6.8.0-90-generic
?? = ?? boot/initrd.img.old
======================== Unknown MBRs/Boot Sectors/etc =========================
Unknown BootLoader on nvme0n1p2
Unknown BootLoader on sda
================================ ZFS activation ================================
dpkg-query -W -f=${Version} zfsutils-linux : 2.1.5-1ubuntu6~22.04.4
zpool export -f -a
zpool import -N -f -R /mnt/boot-sav/zfs bpool
zpool import -N -f -R /mnt/boot-sav/zfs rpool
If needed, type 'sudo zfs load-key -a' in another terminal.
zfs mount rpool/ROOT/ubuntu_tl4976
zfs mount -a
Error: could not activate ZFS. Please report this message to boot.repair@gmail.com
zpool list after activation
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
bpool 1.88G 415M 1.47G - - 0% 21% 1.00x ONLINE /mnt/boot-sav/zfs
rpool 1.81T 385G 1.44T - - 8% 20% 1.00x ONLINE /mnt/boot-sav/zfs
zfs list
NAME USED AVAIL REFER MOUNTPOINT
bpool 414M 1.34G 96K /mnt/boot-sav/zfs/boot
bpool/BOOT 413M 1.34G 96K none
bpool/BOOT/ubuntu_tl4976 413M 1.34G 413M /mnt/boot-sav/zfs/boot
rpool 386G 1.38T 192K /mnt/boot-sav/zfs
rpool/ROOT 27.8G 1.38T 192K none
rpool/ROOT/ubuntu_tl4976 27.8G 1.38T 6.62G /mnt/boot-sav/zfs
rpool/ROOT/ubuntu_tl4976/srv 192K 1.38T 192K /mnt/boot-sav/zfs/srv
rpool/ROOT/ubuntu_tl4976/usr 580K 1.38T 192K /mnt/boot-sav/zfs/usr
rpool/ROOT/ubuntu_tl4976/usr/local 388K 1.38T 388K /mnt/boot-sav/zfs/usr/local
rpool/ROOT/ubuntu_tl4976/var 21.1G 1.38T 192K /mnt/boot-sav/zfs/var
rpool/ROOT/ubuntu_tl4976/var/games 192K 1.38T 192K /mnt/boot-sav/zfs/var/games
rpool/ROOT/ubuntu_tl4976/var/lib 20.5G 1.38T 20.3G /mnt/boot-sav/zfs/var/lib
rpool/ROOT/ubuntu_tl4976/var/lib/AccountsService 244K 1.38T 244K /mnt/boot-sav/zfs/var/lib/AccountsService
rpool/ROOT/ubuntu_tl4976/var/lib/NetworkManager 580K 1.38T 580K /mnt/boot-sav/zfs/var/lib/NetworkManager
rpool/ROOT/ubuntu_tl4976/var/lib/apt 145M 1.38T 145M /mnt/boot-sav/zfs/var/lib/apt
rpool/ROOT/ubuntu_tl4976/var/lib/dpkg 80.4M 1.38T 80.4M /mnt/boot-sav/zfs/var/lib/dpkg
rpool/ROOT/ubuntu_tl4976/var/log 611M 1.38T 611M /mnt/boot-sav/zfs/var/log
rpool/ROOT/ubuntu_tl4976/var/mail 192K 1.38T 192K /mnt/boot-sav/zfs/var/mail
rpool/ROOT/ubuntu_tl4976/var/snap 6.23M 1.38T 6.23M /mnt/boot-sav/zfs/var/snap
rpool/ROOT/ubuntu_tl4976/var/spool 276K 1.38T 276K /mnt/boot-sav/zfs/var/spool
rpool/ROOT/ubuntu_tl4976/var/www 192K 1.38T 192K /mnt/boot-sav/zfs/var/www
rpool/USERDATA 357G 1.38T 192K /mnt/boot-sav/zfs
rpool/USERDATA/hal9000_vakxoc 357G 1.38T 357G /mnt/boot-sav/zfs/home/hal9000
rpool/USERDATA/root_vakxoc 1.07M 1.38T 1.07M /mnt/boot-sav/zfs/root
rpool/keystore 518M 1.38T 63.0M -
=================== findmnt (filtered) after ZFS activation ====================
SOURCE FSTYPE SIZE USED AVAIL USE% TARGET
/dev/sda1 iso9660 6.4G 6.4G 0 100% /cdrom
/dev/disk/by-label/writable[/install-logs-2026-03-18.1/log] ext4 877.5M 6M 809.9M 1% /var/log
/dev/disk/by-label/writable[/install-logs-2026-03-18.1/crash] ext4 877.5M 6M 809.9M 1% /var/crash
bpool/BOOT/ubuntu_tl4976 zfs 1.7G 412.8M 1.3G 23% /mnt/boot-sav/zfs/boot
Suggested repair: ______________________________________________________________
The default repair of the Boot-Repair utility would not act on the boot.
Confirmation request before suggested repair: __________________________________
Warning: ZFS not activated correctly. Repair will fail unless you mount the pools on /mnt/boot-sav/zfs before continuing. Please report this message to boot.repair@gmail.com
Are you sure you want to continue anyway?
I am not sure boot repair is needed. You are booting - but the AMDGPU is apparently not recognizing the screen.
You could try:
sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-amdgpu mesa-vulkan-drivers mesa-utils
But I suspect it is the EDID of the new screen...
journalctl -b | grep -i edid
on the Live Mode the journalctl command returns the following
journalctl -b | grep -i edid
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output eDP
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID Version: 1.4
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): Number of EDID sections to follow: 1
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID (in hex):
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output HDMI-A-0
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-0
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-1
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-2
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-3
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-4
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID for output DisplayPort-5
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID vendor "BOE", prod id 2872
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): Using EDID range info for horizontal sync
Mar 18 15:16:13 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): Using EDID range info for vertical refresh
Mar 19 10:48:58 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID vendor "BOE", prod id 2872
Mar 19 10:50:48 zorin /usr/libexec/gdm-x-session[4363]: (II) AMDGPU(0): EDID vendor "BOE", prod id 2872