I updated to gnome 47 , I can't login to either the wayland or the X11 session

Issues & Assistance Unsupported Software (AUR & Other)
1 
System:
  Kernel: 6.6.52-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/@/.snapshots/4122/snapshot/boot/vmlinuz-linux-lts
    root=UUID=b6b92ddd-1165-4684-927f-b9ae66d45eff quiet rd.udev.log_priority=3
    vt.global_cursor_default=0 loglevel=3 sysrq_always_enabled=1 elevator=noop
    systemd.unified_cgroup_hierarchy=1 ibt=off
    rootflags=defaults,noatime,autodefrag,compress=zstd,discard=async,ssd,subvol=@/.snapshots/4122/snapshot
  Desktop: Blackbox v: 0.14.0 vt: 2 dm: GDM v: 47.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: X540LA v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: X540LA v: 1.0 serial: <superuser required> part-nu: ASUS-NotebookSKU
    uuid: <superuser required> UEFI: American Megatrends v: X540LA.303 date: 08/31/2018
Battery:
  ID-1: BAT0 charge: 25.7 Wh (96.6%) condition: 26.6/33.2 Wh (80.2%) volts: 10.8 min: 10.8
    model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: not charging cycles: 853
CPU:
  Info: model: Intel Core i3-5005U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
    note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
    microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1896 min/max: 500/1900 scaling: driver: intel_cpufreq governor: performance
    cores: 1: 1896 2: 1896 3: 1896 4: 1896 bogomips: 15968
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: ASUSTeK driver: i915 v: kernel arch: Gen-8
    process: Intel 14nm built: 2014-15 ports: active: DP-1,eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:1616 class-ID: 0300
  Device-2: IMC Networks USB2.0 VGA UVC WebCam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:5 chip-ID: 13d3:5a11 class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2 driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 1
  Monitor-1: DP-1 model: Samsung SyncMaster serial: <filter> built: 2009 res: 1600x900 dpi: 92
    gamma: 1.2 size: 443x249mm (17.44x9.8") diag: 508mm (20") ratio: 16:9 modes: max: 1600x900
    min: 720x400
  Monitor-2: eDP-1 model: ChiMei InnoLux 0x15dc built: 2015 res: 1366x768 dpi: 101 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.2-arch1.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 5500 (BDW GT2) device-ID: 8086:1616
    memory: 3.72 GiB unified: yes
  API: Vulkan v: 1.3.295 layers: 3 device: 0 type: integrated-gpu name: Intel HD Graphics 5500
    (BDW GT2) driver: mesa intel v: 24.2.2-arch1.1 device-ID: 8086:1616 surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Broadwell-U Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 class-ID: 0403
  API: ALSA v: k6.6.52-1-lts status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 4000 bus-ID: 02:00.2 chip-ID: 10ec:8136
    class-ID: 0200
  IF: enp2s0f2 state: down mac: <filter>
  Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Lite-O
n driver: rtl8723be
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:b723
    class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1:2 chip-ID: 0a12:0001 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status:
    discoverable: no pairing: no class-ID: 6c010c
  Device-2: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 2.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-4:4 chip-ID: 0bda:b721 class-ID: e001 serial: <filter>
  Report: ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 4.0 lmp-v: 6 status:
    discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 704.24 GiB used: 666.9 GiB (94.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: TeamGroup model: T253256GB size: 238.47 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 227N
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5000LPCX-80VHAT1 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 1A02 scheme: GPT
Partition:
  ID-1: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 584 KiB (0.1%) fs: vfat
    dev: /dev/sda4 maj-min: 8:4
  ID-2: /home raw-size: 9.8 GiB size: 9.8 GiB (100.00%) used: 8.38 GiB (85.5%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-3: /var/log raw-size: 24.91 GiB size: 24.91 GiB (100.00%) used: 19.98 GiB (80.2%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
  ID-4: /var/tmp raw-size: 24.91 GiB size: 24.91 GiB (100.00%) used: 19.98 GiB (80.2%) fs: btrfs
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 180 (default 60) cache-pressure: 50 (default 100) zswap: no
  ID-1: swap-1 type: zram size: 7.62 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 59.0 C pch: 54.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 3.09 GiB (40.5%)
  Processes: 267 Power: uptime: 6m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 3.04 GiB
    services: power-profiles-daemon,upowerd Init: systemd v: 256 default: graphical tool: systemctl
  Packages: 1213 pm: pacman pkgs: 1158 libs: 281 tools: gnome-software,paru pm: flatpak pkgs: 55
    Compilers: gcc: 14.2.1 Client: shell wrapper v: 5.2.32-release inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2023-11-27
  Last full system update: 2024-09-20
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            snapper-boot.service systemd-remount-fs.service

I installed the cosmic-session through tty3 just to login

2

i tried to restore a snapshot and snapper-tools doesn’t load in cosmic session , it gives me this error

Qt: Session management error: Could not open network socket
Authorization required, but no authorization protocol specified

qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
3

Can you boot into a snapshot from the grub menu during boot?

1 Like
4

i can , but i can’t restore it because i can’t login to gnome in any snapshot , i can login to cosmic but snapper-tools doesn’t open to restore the snapshot

5

I don’t know much about these aspects, but in my opinion this is the problem:

From Arch Wiki:

It was last updated November 3, 2005 with no plans for future releases

An updated version of the original CVS source plus collected patches is maintained at BlackBox GitHub and is used by the Arch package

But the commits there seem to be not so frequent, so upgrading to Gnome 47 might be a bit risky there.
This is not Gnome anymore.

3 Likes
6

i’m not using that window manager i’m using the blackbox-terminal , i’m currently on cosmic desktop , i think garuda-inxi didn’t recognize cosmic DE and set blackbox as the desktop . i was using gnome 46 before updating to gnome 47

7

I would’ve thought that the old snapshot should have the old gnome session and not the cosmic one.

8

it doesn’t even the oldest one

9

You should try to investigate and fix these:

Start checking:

systemctl status snapper-boot.service
systemctl status systemd-remount-fs.service
1 Like
10

they both failed to load

11

The output of those commands should give some additional info about why they failed.

1 Like
12

`× snapper-boot.service - Take snapper snapshot of root on boot
Loaded: loaded (/usr/lib/systemd/system/snapper-boot.service; static)
Active: failed (Result: exit-code) since Fri 2024-09-20 16:08:07 CET; 1min 57s ago
Invocation: 049afd4bf08145c7a8c6fc63c73b412b
TriggeredBy: ● snapper-boot.timer
Process: 823 ExecStart=/usr/bin/snapper --config root create --cleanup-algorithm number --description boot (code=exited, st>
Main PID: 823 (code=exited, status=1/FAILURE)
Mem peak: 3M
CPU: 53ms

Sep 20 16:08:07 garuda systemd[1]: Starting Take snapper snapshot of root on boot…
Sep 20 16:08:07 garuda snapper[823]: IO Error (subvolume is not a btrfs subvolume).
Sep 20 16:08:07 garuda systemd[1]: snapper-boot.service: Main process exited, code=exited, status=1/FAILURE
Sep 20 16:08:07 garuda systemd[1]: snapper-boot.service: Failed with result ‘exit-code’.
Sep 20 16:08:07 garuda systemd[1]: Failed to start Take snapper snapshot of root on boot.`

13

Maybe you could boot from a live USB, mount your system partition, open btrfs assistant and restore the latest working snapshot from there

2 Likes
14

can you provide steps to do that

15

After booting from the live USB, you have to mount /dev/sda1 e.g. with your file manager. I think even if you browser/open it, it will be mounted.
I’m not in front of my system at the moment, anyway, open btrfs-assistant, snapper tab and there should be a browse/restore sub-tab or button.

3 Likes
16

thank you , i will do it later tonight

2 Likes
17

My guess is those services are failing because you are booted off a snapshot.

If you did not boot into a snapshot on purpose when you posted that inxi, then it is likely you messed up your bootloader configuration by updating it from a snapshot or similar.

2 Likes
18

yeah i was in a snapshot , i did what filo said , i restored the oldest snapshot , gnome still doesn’t open and it says i’m still in a snapshot after restarting

19

You will have to manually edit /boot/grub/grub.cfg so it points to your actual installation instead of a snapshot. This old thread is a similar case:

20

I didn’t understand , the file is so confusing