Starting a snapshot doesn't start Gnome

Because of the recent issues I had with Gnome not starting, I want to make sure the snapshots are working correctly. When I tried starting a snapshot I got saw a few errors from Tor I think and that was it. Gnome didn't start.

I was able to CTRL+ALT+F2 to go into another text only login prompt to log in.

Are the snapshots supposed to boot into the Gnome GUI?

System:
  Kernel: 6.0.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=746085a3-1efd-44d0-9e3f-bea3af666d4d rw [email protected]
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3 nvidia-drm.modeset=1
    ibt=off
  Desktop: GNOME v: 43.1 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 43.0
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: X470 AORUS ULTRA GAMING v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: X470 AORUS ULTRA GAMING-CF v: x.x
    serial: <superuser required> UEFI: American Megatrends v: F3
    date: 08/08/2018
CPU:
  Info: model: AMD Ryzen 5 2600X bits: 64 type: MT MCP arch: Zen+ gen: 2
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 2370 high: 3623 min/max: 2200/3600 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3124 2: 3623
    3: 2077 4: 2077 5: 2144 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200
    12: 2200 bogomips: 86395
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    disabled, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2070] vendor: Micro-Star MSI
    driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-10) arch: Turing code: TUxxx
    process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none off: DP-2,HDMI-A-1
    empty: DP-1,DP-3,Unknown-1 bus-ID: 09:00.0 chip-ID: 10de:1f02
    class-ID: 0300
  Device-2: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-10:7 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5
    compositor: gnome-shell driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: 0
  Monitor-1: DP-2 model: Acer X34 serial: <filter> built: 2013
    res: 3440x1440 dpi: 109 gamma: 1.2 size: 798x335mm (31.42x13.19")
    diag: 865mm (34.1") modes: max: 3440x1440 min: 640x480
  Monitor-2: HDMI-A-1 model: Sony TV 01 serial: <filter> built: 2013
    res: 1920x1080 dpi: 47 gamma: 1.2 size: 1040x585mm (40.94x23.03")
    diag: 1193mm (47") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  OpenGL: renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA
    520.56.06 direct render: Yes
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel bus-ID: 1-10:7 v: kernel chip-ID: 046d:082d pcie:
    gen: 3 class-ID: 0102 serial: <filter> speed: 8 GT/s lanes: 16
    bus-ID: 09:00.1 chip-ID: 10de:10f9 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0b:00.3
    chip-ID: 1022:1457 class-ID: 0403
  Device-3: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo
  Sound API: ALSA v: k6.0.7-zen1-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.75 TiB used: 477.74 GiB (17.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 1B2QEXP7
    temp: 41.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDH3 2T00
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 00RL scheme: GPT
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 238.87 GiB
    (12.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 580 KiB
    (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 238.87 GiB
    (12.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 238.87
    GiB (12.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 238.87
    GiB (12.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 62.75 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 376 Uptime: 11m wakeups: 1 Memory: 62.75 GiB used: 7.79 GiB
  (12.4%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.2.0 alt: 11 Packages: 2552 pm: nix-default pkgs: 138
  pm: nix-sys pkgs: 0 pm: nix-usr pkgs: 490 libs: 132 pm: pacman pkgs: 1924
  libs: 472 tools: pamac,paru pm: flatpak pkgs: 0 Shell: fish v: 3.5.1
  running-in: tmux: inxi: 3.3.22
e[1;34mGaruda (2.6.9-1):e[0m
e[1;34m  System install date:e[0m     2021-12-26
e[1;34m  Last full system update:e[0m 2022-11-05
e[1;34m  Is partially upgraded:  e[0m No
e[1;34m  Relevant software:      e[0m NetworkManager
e[1;34m  Windows dual boot:      e[0m Probably (Run as root to verify)
e[1;34m  Snapshots:              e[0m Snapper
e[1;34m  Failed units:           e[0m bluetooth-autoconnect.service 

Snapshots boot to a previous state of your system. By default your system is pre-configured to generate a new snapshot when certain events happen, for example updating your system or installing a new package.

The snapshots are taken regardless of the state your system is in at the time. In your case, it sounds like you have restored the version of Gnome that was broken for you (it was only thirteen hours ago you reported the issue fixed by an update: My Gnome+Wayland+Nvidia Destop will not start after update - #22 by josephmendoza). Any time you have a broken system, just be mindful you probably have some broken snapshots too.

If you would like to test the snapshotting feature, try installing or removing some packages and then roll back. Restoring a broken system after you have already fixed it is...not that useful. :smirk:

1 Like

I think my snapshot should have been good actually. It didn't fail the same way it did when the Gnome bug occurred. I'm wondering if snapshots work for starting Gnome.

Anyway, as long as I get the system back to a state were I can use the terminal or SSH into then it should be fine.

Yes, booting into snapshots works just fine with Gnome.

You don't need to make any special effort to get back to your working system if you booted a snapshot without restoring it--just reboot, and you'll be right back where you started before booting the snapshot.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.