System won't boot into XFCE - black screen

Support Xfce
1

Hello, last weekend my computer booted up into XFCE fine like always, this weekend I have a black screen so I ctrl+alt+F6 and see its just the GUI not loading. Installed sshd so I can go in and get this output. I searched several of the old topics around this same subject. None I could find contain the type of message I am getting. Some past topics said to use just startx with some saying to use sudo startx and also startx xfce. Sudo startx and sudo startx xfce both give the same output below. I’m not sure what to do based on this output. Thanks for the help!

$ startx
xauth:  unable to write authority file /home/will/.Xauthority-n
xauth:  unable to write authority file /home/will/.Xauthority-n

/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.
[will@silverbox ~]$ sudo startx
[sudo] password for will: 


X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux silverbox 6.6.47-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Aug 19 09:51:26 UTC 2024 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64 root=UUID=3510e7bf-8999-4434-b116-7dd601ae8f04 rw quiet apparmor=1 security=apparmor udev.log_priority=3
 
Current version of pixman: 0.43.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 29 08:54:25 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Failed to connect to bus: No medium found
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/dbus-WZmkqCElM5,guid=9f72492a888911f88acba4e266f95c12';
export DBUS_SESSION_BUS_ADDRESS;
DBUS_SESSION_BUS_PID=2599;
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
2

Not sure how, or even if you can get startx to launch your desktop environment anymore. For most distros nowadays, and Manjaro uses, display managers.

It’s most likely failing, but to launch your desktop environment, for XFCE you run sudo systemctl start lightdm.

What do you think changed from when it was working? Even just an update?

So the logs when it tries to start would help (and possibly an inxi -v8z).

Possibly useful logs such as:
journalctl -p3 -b0 - All errors or worse, from the current boot.
journalctl -u lightdm -b -1 - All logs from lightdm, from the previous boot

3

I may have run updates last weekend. I usually do each weekend. It has no new updates this morning sudo pacman -Syu.

sudo systemctl start lightdm runs but does the same thing, black screen with a cursor.

All errors and up, from the current boot.

[will@silverbox ~]$ journalctl -p3 -b0
Sep 29 08:35:45 silverbox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Sep 29 08:35:45 silverbox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Sep 29 08:35:45 silverbox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Sep 29 08:35:45 silverbox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Sep 29 08:35:45 silverbox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Sep 29 08:35:45 silverbox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Sep 29 08:35:45 silverbox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Sep 29 08:35:45 silverbox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Sep 29 08:35:47 silverbox kernel: usb 4-5: 3:1: cannot get freq at ep 0x86
Sep 29 08:35:47 silverbox kernel: usb 4-5: 3:2: cannot get freq at ep 0x86
Sep 29 08:35:47 silverbox kernel: usb 4-5: 3:3: cannot get freq at ep 0x86
Sep 29 08:35:51 silverbox systemd-coredump[1653]: [🡕] Process 1606 (cups-proxyd) of user 0 dumped core.
                                                  
                                                  Stack trace of thread 1606:
                                                  #0  0x000055a9d96f1d75 n/a (/snap/cups/1058/sbin/cups-proxyd + 0x9d75)
                                                  ELF object binary architecture: AMD x86-64
Sep 29 08:36:08 silverbox systemd[1]: Failed to start Light Display Manager.
Sep 29 09:32:03 silverbox systemd[1]: Failed to start Light Display Manager.

All logs, info and up, from LightDM, from the previous boot

[will@silverbox ~]$ journalctl -u lightdm -b -1
Sep 29 08:30:53 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:30:53 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:30:55 silverbox lightdm[1694]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:30:55 silverbox lightdm[1694]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1694) opened.
Sep 29 08:30:56 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:30:56 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:30:56 silverbox systemd[1]: lightdm.service: Consumed 605ms CPU time, 86.2M memory peak.
Sep 29 08:30:57 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Sep 29 08:30:57 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:30:57 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:30:58 silverbox lightdm[1743]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:30:58 silverbox lightdm[1743]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1743) opened.
Sep 29 08:30:58 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:30:58 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:30:59 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Sep 29 08:30:59 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:30:59 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:00 silverbox lightdm[1763]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:00 silverbox lightdm[1763]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1763) opened.
Sep 29 08:31:00 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:00 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:01 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Sep 29 08:31:01 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:01 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:02 silverbox lightdm[1783]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:02 silverbox lightdm[1783]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1783) opened.
Sep 29 08:31:02 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:02 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:03 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Sep 29 08:31:03 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:03 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:04 silverbox lightdm[1804]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:04 silverbox lightdm[1804]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1804) opened.
Sep 29 08:31:04 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:04 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:05 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Sep 29 08:31:05 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:05 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:06 silverbox lightdm[1824]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:06 silverbox lightdm[1824]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1824) opened.
Sep 29 08:31:06 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:06 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:07 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 6.
Sep 29 08:31:07 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:07 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:08 silverbox lightdm[1844]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:08 silverbox lightdm[1844]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1844) opened.
Sep 29 08:31:08 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:08 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:09 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 7.
Sep 29 08:31:09 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:09 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:10 silverbox lightdm[1864]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:10 silverbox lightdm[1864]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1864) opened.
Sep 29 08:31:10 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:10 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:11 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 8.
Sep 29 08:31:11 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:11 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:12 silverbox lightdm[1884]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:12 silverbox lightdm[1884]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1884) opened.
Sep 29 08:31:12 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:12 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:13 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 9.
Sep 29 08:31:13 silverbox systemd[1]: Starting Light Display Manager...
Sep 29 08:31:13 silverbox systemd[1]: Started Light Display Manager.
Sep 29 08:31:14 silverbox lightdm[1904]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=966) by (uid=0)
Sep 29 08:31:14 silverbox lightdm[1904]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-1904) opened.
Sep 29 08:31:14 silverbox systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 29 08:31:14 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:14 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 10.
Sep 29 08:31:14 silverbox systemd[1]: lightdm.service: Start request repeated too quickly.
Sep 29 08:31:14 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 29 08:31:14 silverbox systemd[1]: Failed to start Light Display Manager.

System Info

[will@silverbox ~]$ sudo inxi --verbosity=8 --filter --width
[sudo] password for will: 
System:
  Kernel: 6.6.47-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=3510e7bf-8999-4434-b116-7dd601ae8f04 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Console: pty pts/1 DM: LightDM v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: System76 product: Wild Dog Performance v: wilp10
    serial: N/A Chassis: type: 3 v: Desktop serial: <filter>
  Mobo: ASUSTeK model: H87-PLUS v: Rev X.0x serial: <filter> part-nu: All
    uuid: 204a8ec0-d7da-11dd-ad6b-e03f4944d631 UEFI: American Megatrends v: 0705
    date: 12/05/2013
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.56 GiB used: 609.1 MiB (3.8%)
  Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Crucial part-no: BLS8G3D1609DS1S00. serial: <filter>
  Device-2: ChannelA-DIMM1 type: no module installed
  Device-3: ChannelB-DIMM0 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: Crucial part-no: BLS8G3D1609DS1S00. serial: <filter>
  Device-4: ChannelB-DIMM1 type: no module installed
PCI Slots:
  Slot: 1 type: PCIe status: in use length: long volts: 3.3 bus-ID: 01:00.0
  Slot: 2 type: PCIe status: available length: short volts: 3.3
    bus-ID: 02:00.0
  Slot: 3 type: PCIe status: available length: short volts: 3.3
    bus-ID: ff:00.0
  Slot: 4 type: PCIe status: available length: long volts: 3.3
    bus-ID: ff:00.0
  Slot: 5 type: PCI status: available length: short volts: 3.3
    bus-ID: 05:1c.7
  Slot: 6 type: PCI status: available length: short volts: 3.3
    bus-ID: 05:1d.0
  Slot: 7 type: PCI status: available length: short volts: 3.3
    bus-ID: 05:1d.1
CPU:
  Info: model: Intel Core i7-4770 socket: BGA1155 (1150) note: check bits: 64
    type: MT MCP arch: Haswell gen: core 4 level: v3 note: check built: 2013-15
    process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 base/boost: 3400/3900 scaling:
    driver: intel_cpufreq governor: schedutil volts: 1.2 V ext-clock: 100 MHz
    cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
    bogomips: 54296
  Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2
    bts clflush cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht ibpb ibrs ida invpcid lahf_lm lm mca mce md_clear mmx
    monitor movbe msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm
    pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp rep_good
    sdbg sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xsave xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  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; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI
    driver: nouveau v: kernel non-free: 550.xx+ status: current (as of 2024-09;
    EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
    speed: 8 GT/s ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 01:00.0
    chip-ID: 10de:1c82 class-ID: 0300 temp: 39.0 C
  Device-2: Sunplus Innovation UHD Capture driver: snd-usb-audio,uvcvideo
    type: USB rev: 3.1 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 4-5:2
    chip-ID: 1bcf:2c99 class-ID: 0102
  Display: unspecified server: X.org v: 1.21.1.13 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
    tty: 190x42
  Monitor-1: HDMI-A-1 model: Dell P2217 serial: <filter> built: 2016
    res: 1680x1050 dpi: 90 gamma: 1.2 chroma: red: x: 0.635 y: 0.357 green:
    x: 0.310 y: 0.643 blue: x: 0.153 y: 0.071 white: x: 0.314 y: 0.329
    size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10
    modes: 1680x1050, 1920x1080, 1920x1080i, 1280x1024, 1152x864, 1280x720,
    1024x768, 800x600, 720x576, 720x480, 640x480, 720x400
  API: OpenGL Message: GL data unavailable in console, glxinfo missing.
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-2: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:0fb9
    class-ID: 0403
  Device-3: Sunplus Innovation UHD Capture driver: snd-usb-audio,uvcvideo
    type: USB rev: 3.1 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 4-5:2
    chip-ID: 1bcf:2c99 class-ID: 0102
  API: ALSA v: k6.6.47-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.3 status: off tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: off with: pulseaudio-alsa type: plugin
    tools: pacat,pactl,pavucontrol
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK H81M-C driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,sshd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.87 TiB used: 221.73 GiB (5.6%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 5B0Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-1CH164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC27 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST2000DM001-1CH164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC27 scheme: GPT
  Optical-1: /dev/sr0 vendor: PIONEER model: BD-RW BDR-212V rev: 1.01
    dev-links: cdrom
  Features: speed: 125 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r state: running
Partition:
  ID-1: / raw-size: 238.17 GiB size: 233.38 GiB (97.99%)
    used: 221.73 GiB (95.0%) fs: ext4 block-size: 4096 B dev: /dev/sda2
    maj-min: 8:2 label: N/A uuid: 3510e7bf-8999-4434-b116-7dd601ae8f04
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 312 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
    label: NO_LABEL uuid: 712B-FF26
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sdb1 maj-min: 8:17 size: 1.82 TiB fs: ext4 label: N/A
    uuid: 34fe4fda-de97-4e97-af31-5e9085ca4263
  ID-2: /dev/sdc1 maj-min: 8:33 size: 1.82 TiB fs: ext4 label: N/A
    uuid: a5355482-baf3-40be-95ab-391bf5f336a4
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8000
    class-ID: 0900
  Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8008
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 14 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:2 info: YICHIP Wireless Device type: keyboard,mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 3151:3020 class-ID: 0301
    serial: <filter>
  Device-2: 3-11:3 info: Alcor Micro AU6477 Card Reader Controller
    type: mass storage,HID driver: hid-generic,usb-storage,usbhid interfaces: 2
    rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 250mA
    chip-ID: 058f:6364 class-ID: 0300 serial: <filter>
  Device-3: 3-12:4 info: Shenzhen Riitek Wireless Receiver
    type: mouse,keyboard driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 50mA
    chip-ID: 1997:2466 class-ID: 0301
  Hub-6: 4-0:1 info: super-speed hub ports: 6 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 4-5:2 info: Sunplus Innovation UHD Capture type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 512mA
    chip-ID: 1bcf:2c99 class-ID: 0102
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A gpu: nouveau temp: 39.0 C
  Fan Speeds (rpm): N/A gpu: nouveau fan: 0
Repos:
  Packages: 1545 pm: pacman pkgs: 1496 libs: 469 tools: pamac pm: flatpak
    pkgs: 32 pm: snap pkgs: 17
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    8: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    9: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    10: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    11: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    12: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    13: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
    14: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    15: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    16: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    17: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    18: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    19: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    20: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
    21: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    22: http://mirror.fcix.net/manjaro/stable/$repo/$arch
    23: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    24: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 188
  1: cpu: 0.1% command: snapd pid: 792 mem: 46.8 MiB (0.2%)
  2: cpu: 0.0% command: init pid: 1 mem: 13.5 MiB (0.0%)
  3: cpu: 0.0% command: [kthreadd] pid: 2 mem: 0.00 MiB (0.0%)
  4: cpu: 0.0% command: [pool_workqueue_release] pid: 3 mem: 0.00 MiB (0.0%)
  5: cpu: 0.0% command: [kworker/R-rcu_g] pid: 4 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 188
  1: mem: 46.8 MiB (0.2%) command: snapd pid: 792 cpu: 0.1%
  2: mem: 23.7 MiB (0.1%) command: systemd-journald pid: 432 cpu: 0.0%
  3: mem: 23.1 MiB (0.1%) command: NetworkManager pid: 788 cpu: 0.0%
  4: mem: 13.5 MiB (0.0%) command: init pid: 1 cpu: 0.0%
  5: mem: 13.0 MiB (0.0%) command: ModemManager pid: 934 cpu: 0.0%
Info:
  Processes: 188 Power: uptime: 1h 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.21 GiB Init: systemd v: 256
    default: graphical tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Sudo (sudo) v: 1.9.15p5
    default: Bash v: 5.2.32 running-in: pty pts/1 (SSH) inxi: 3.3.36
[will@silverbox ~]$
4

For what it’s worth (and I was just now able to test this) I can boot into GUI XFCE using my USB live image. I was thinking hardware issue possibly but perhaps this rules that idea out?

5

I’m surprised there are no other errors are coming up, but at least there is a lot more information to go off of now.

I guess I would just double check those ACPI errors were happening before.

e.g.: journalctl -p3 --until 2024-09-15

Don’t need to see output, just to know if you did or did not have those errors before Sept 15, for example. Just a date before those updates. (I’ve seen working systems still produce similar errors, but it’s good to rule it out for sure.)

I think I would look at your kernel output next, sudo dmesg.

6

It’s got this over and over going back far as the logs go (March).

Sep 08 09:43:24 silverbox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Sep 08 09:43:24 silverbox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)

What do you want to see from dmesg? I’m not that familiar with that command. Looks likes counting up in seconds since boot on the timestamps.

7

I was hoping for any other errors there, sometimes it can be kernel or GPU related when your DE can’t start. I know there has to be errors logged somewhere for this! I’m just giving you the wrong commands. (Err, I mean, checking off the all the spots we need to look for them.)

I see you’re using the open source driver nouveau. (I usually go proprietary driver for Nvidia.) But since this was working before, I wouldn’t jump on making that change until you found what broke. Performance is the main reason I go this route anyway.

I am out of ideas, for now. But at least there’s a lot more information for others to go on.

8

Thanks. Reinstall is always an option but I hope I don’t have to on this one as I had several apps installed and setup for various things.

9

Did you log in as root?
Don’t!
Use your user account.
(I’m not assuming anything - I’m just asking and making sure.)

what you could try:

systemctl status lightdm.service

this may yield some useful error messages

then, as a check, since the file can’t be written to (info taken from your first post):

ls -al /home/will/.Xauthority*

it should only be one, it should belong to you, and be writable by you - if not: remove it

In fact, while you are at it:
ls -Al | grep root (that -Al is an A and a lower case L, not an upper case I)
nothing should come up as a response

then you could restart the display manager again:

systemctl restart lightdm.service

If it still fails - as a temporary measure:

systemctl stop lightdm.service
systemctl disable lightdm.service

then you can, logged in as your user, not as root:

startxfce4

see how it goes?

(none of this from the live USB! - all from TTY of your system, logged in as will)

10 
[will@silverbox ~]$ systemctl status lightdm.service
Ă— lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: >
     Active: failed (Result: exit-code) since Mon 2024-09-30 17:42:25 CDT; 1min>
   Duration: 1.574s
 Invocation: 2d106e96823442248d124f9c7ea816dd
       Docs: man:lightdm(1)
    Process: 1982 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 1982 (code=exited, status=1/FAILURE)

Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Scheduled restart job, r>
Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Start request repeated t>
Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Failed with result 'exit>
Sep 30 17:42:25 silverbox systemd[1]: Failed to start Light Display Manager.
lines 1-13/13 (END)...skipping...
Ă— lightdm.service - Light Display Manager
     Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Mon 2024-09-30 17:42:25 CDT; 1min 16s ago
   Duration: 1.574s
 Invocation: 2d106e96823442248d124f9c7ea816dd
       Docs: man:lightdm(1)
    Process: 1982 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
   Main PID: 1982 (code=exited, status=1/FAILURE)

Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 13.
Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Start request repeated too quickly.
Sep 30 17:42:25 silverbox systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 30 17:42:25 silverbox systemd[1]: Failed to start Light Display Manager.

I see two

[will@silverbox ~]$ ls -al /home/will/.Xauthority*
-rw------- 1 will will 0 Sep 22 14:19 /home/will/.Xauthority
-rw------- 1 will will 0 Sep 29 08:54 /home/will/.Xauthority-n

Nothing on ls -Al | grep root

Did your other commands and got to startxfce4

I got this

[will@silverbox ~]$ startxfce4
/usr/bin/startxfce4: Starting X server

/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

So I tried with sudo and it loaded up the GUI! And gave me this output. It’s pretty long.

[will@silverbox ~]$ sudo startxfce4
[sudo] password for will: 
/usr/bin/startxfce4: Starting X server


X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux silverbox 6.6.47-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Aug 19 09:51:26 UTC 2024 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64 root=UUID=3510e7bf-8999-4434-b116-7dd601ae8f04 rw quiet apparmor=1 security=apparmor udev.log_priority=3
 
Current version of pixman: 0.43.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 30 17:50:09 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
Failed to connect to bus: No medium found
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
gpg-agent[2377]: directory '/root/.gnupg/private-keys-v1.d' created
gpg-agent[2378]: gpg-agent (GnuPG) 2.4.5 started

(xfce4-session:2317): xfce4-session-WARNING **: 17:50:12.662: Unable to launch "pulseaudio-ctl-normal" (specified by autostart/pulseaudio-ctl.desktop): Failed to execute child process “pulseaudio-ctl-normal” (No such file or directory)

(xfce4-session:2317): xfce4-session-WARNING **: 17:50:12.669: Unable to launch "desktop-items" (specified by autostart/live-session.desktop): Failed to execute child process “desktop-items” (No such file or directory)

(xfce4-session:2317): xfce4-session-WARNING **: 17:50:12.678: Unable to launch "disable-dpms" (specified by autostart/disable-dpms.desktop): Failed to execute child process “disable-dpms” (No such file or directory)
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
dbus[2466]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file dbus-message.c line 2775.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Another notification daemon is running, exiting
Another notification daemon is running, exiting
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
/usr/bin/manjaro-hello:239: DeprecationWarning: 'locale.getdefaultlocale' is deprecated and slated for removal in Python 3.15. Use setlocale(), getencoding() and getlocale() instead.
  sys_locale = locale.getdefaultlocale()[0]
blueman-applet 17.50.13 WARNING  PluginManager:150 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 17.50.13 WARNING  PluginManager:150 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 17.50.13 WARNING  DiscvManager:122 update_menuitems: warning: Adapter is None
DEBUG:root:_DATA_DIR is /usr/share/application-utility
DEBUG:root:_PREF_FILE is /usr/share/application-utility/preferences.json
DEBUG:root:self.file is {'desktop': '', 'main': '/usr/share/application-utility/default.json'}
INFO:root:json to merge : /usr/share/application-utility/default.json
DEBUG:root:json : /tmp/manjaro-hello-preferences.json
** Message: 17:50:14.298: flatpak_plugin.vala:393: refreshing flathub appstream data
xfsettingsd: Another instance took over. Leaving...
WARNING:root:File not exist ? /usr/share/application-utility/xfce.json
/usr/bin/manjaro-hello:95: DeprecationWarning: Gtk.Widget.set_margin_left is deprecated
  grid.set_margin_left(5)
DEBUG:root:
--- read data.json with FILTERS ---

DEBUG:root:my desktop: xfce
DEBUG:root:filter    : 
DEBUG:root:groups    : *
DEBUG:root:	filter app: Epiphany ['advanced'] < 
DEBUG:root:	filter app: Falkon ['advanced'] < 
DEBUG:root:	filter app: Konqueror ['advanced'] < 
DEBUG:root:	filter app: Claws Mail ['advanced'] < 
DEBUG:root:	filter app: Atom ['advanced'] < 
DEBUG:root:	filter app: Vim ['advanced'] < 
DEBUG:root:	filter app: Visual Studio Code OSS ['advanced'] < 
DEBUG:root:	filter app: Gnome builder ['advanced'] < 
DEBUG:root:filter group : File Sharing ['advanced'] < 
DEBUG:root:	filter app: Grsync ['advanced'] < 
DEBUG:root:	filter app: Borg ['advanced'] < 
DEBUG:root:filter group : System Tools ['advanced'] < 
DEBUG:root:filter group : Virtual Computing ['advanced'] < 
DEBUG:root:
--- read data.json with FILTERS ---

DEBUG:root:my desktop: xfce
DEBUG:root:filter    : 
DEBUG:root:groups    : *
DEBUG:root:	filter app: Epiphany ['advanced'] < 
DEBUG:root:	filter app: Falkon ['advanced'] < 
DEBUG:root:	filter app: Konqueror ['advanced'] < 
DEBUG:root:	filter app: Claws Mail ['advanced'] < 
DEBUG:root:	filter app: Atom ['advanced'] < 
DEBUG:root:	filter app: Vim ['advanced'] < 
DEBUG:root:	filter app: Visual Studio Code OSS ['advanced'] < 
DEBUG:root:	filter app: Gnome builder ['advanced'] < 
DEBUG:root:filter group : File Sharing ['advanced'] < 
DEBUG:root:	filter app: Grsync ['advanced'] < 
DEBUG:root:	filter app: Borg ['advanced'] < 
DEBUG:root:filter group : System Tools ['advanced'] < 
DEBUG:root:filter group : Virtual Computing ['advanced'] < 
DEBUG:root:
--- read data.json with FILTERS ---

DEBUG:root:my desktop: xfce
DEBUG:root:filter    : 
DEBUG:root:groups    : *
DEBUG:root:	filter app: Epiphany ['advanced'] < 
DEBUG:root:	filter app: Falkon ['advanced'] < 
DEBUG:root:	filter app: Konqueror ['advanced'] < 
DEBUG:root:	filter app: Claws Mail ['advanced'] < 
DEBUG:root:	filter app: Atom ['advanced'] < 
DEBUG:root:	filter app: Vim ['advanced'] < 
DEBUG:root:	filter app: Visual Studio Code OSS ['advanced'] < 
DEBUG:root:	filter app: Gnome builder ['advanced'] < 
DEBUG:root:filter group : File Sharing ['advanced'] < 
DEBUG:root:	filter app: Grsync ['advanced'] < 
DEBUG:root:	filter app: Borg ['advanced'] < 
DEBUG:root:filter group : System Tools ['advanced'] < 
DEBUG:root:filter group : Virtual Computing ['advanced'] < 
Info: Gnome-layout-switcher not installed
xfsettingsd: Another instance took over. Leaving...
** Message: 17:50:43.381: updates_checker.vala:70: check updates
xfsettingsd: Another instance took over. Leaving...
** Message: 17:51:01.472: updates_checker.vala:100: 5 updates found

I can see that its running in the console so when I crtl+c it killed the GUI. I started back up the GUI again sudo startxfce4 and did a restart using the GUI just to see what would happen. The computer rebooted and at least loaded up to the CLI interface this time. Didn’t have to ctrl+alt+F6 from a blinking cursor.

Maybe we’re getting somewhere?

11

Yes - because now, the display manager is disabled and wont even try to start.
because of this previous command:

You could now try to start it again:
systemctl start lightdm.service

or - before you do that:
startxfce4

no sudo

but we know the thing works as it does kind of work when you did use sudo

Can you make sure the system is up to date?
sudo pacman -Syu

The time lag between us seems substantial - it is 3 am here right now (UTC+1) and I’m not going to return before 9 am (six hours from now).

Someone else might be … not sleeping? :sunglasses:

12

Woke up early to respond sooner. :slight_smile: Found something… First when I tried startxfce4 (no sudo) I got the same output as before. Starting the lightdm service again gave same result (black screen with blinking cursor).

When I checked for updates (I had checked before making this post and there were no updates). I got this.

:: Proceed with installation? [Y/n] 
error: Partition / too full: 309618 blocks needed, 0 blocks free
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.
[will@silverbox ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
run             7.8G  1.6M  7.8G   1% /run
efivarfs        128K   73K   51K  60% /sys/firmware/efi/efivars
/dev/sda2       234G  222G     0 100% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-udev-load-credentials.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-sysctl.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs           7.8G     0  7.8G   0% /tmp
/dev/loop0      128K  128K     0 100% /var/lib/snapd/snap/bare/5
/dev/loop4       56M   56M     0 100% /var/lib/snapd/snap/core18/2829
/dev/loop2       56M   56M     0 100% /var/lib/snapd/snap/core18/2823
/dev/loop3      176M  176M     0 100% /var/lib/snapd/snap/brave/442
/dev/loop1      176M  176M     0 100% /var/lib/snapd/snap/brave/440
/dev/loop5       64M   64M     0 100% /var/lib/snapd/snap/core20/2318
/dev/loop6       64M   64M     0 100% /var/lib/snapd/snap/core20/2379
/dev/loop7       75M   75M     0 100% /var/lib/snapd/snap/core22/1621
/dev/loop8       75M   75M     0 100% /var/lib/snapd/snap/core22/1612
/dev/loop9       67M   67M     0 100% /var/lib/snapd/snap/cups/1052
/dev/loop10      68M   68M     0 100% /var/lib/snapd/snap/cups/1058
/dev/loop11      15M   15M     0 100% /var/lib/snapd/snap/formatlab/59
/dev/loop12      15M   15M     0 100% /var/lib/snapd/snap/formatlab/62
/dev/loop13     497M  497M     0 100% /var/lib/snapd/snap/gnome-42-2204/141
/dev/loop15      92M   92M     0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop14     506M  506M     0 100% /var/lib/snapd/snap/gnome-42-2204/176
/dev/loop17     220M  220M     0 100% /var/lib/snapd/snap/k3b/23
/dev/loop16     142M  142M     0 100% /var/lib/snapd/snap/k3b/21
/dev/loop18     451M  451M     0 100% /var/lib/snapd/snap/kf5-5-108-qt-5-15-10-core22/5
/dev/loop19     439M  439M     0 100% /var/lib/snapd/snap/kf5-5-110-qt-5-15-11-core22/3
/dev/loop20     444M  444M     0 100% /var/lib/snapd/snap/kf5-5-111-qt-5-15-11-core22/7
/dev/loop21     323M  323M     0 100% /var/lib/snapd/snap/makemkv/624
/dev/loop22     326M  326M     0 100% /var/lib/snapd/snap/makemkv/627
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/loop23     163M  163M     0 100% /var/lib/snapd/snap/pyqt5-runtime-core20/9
/dev/loop24      39M   39M     0 100% /var/lib/snapd/snap/snapd/21759
/dev/loop25      39M   39M     0 100% /var/lib/snapd/snap/snapd/21465
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-vconsole-setup.service
/dev/sda1       300M  312K  300M   1% /boot/efi
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs           1.6G   88K  1.6G   1% /run/user/1000

What is all this extra lines, normally df -h is just a few lines. Not sure what to delete to start freeing up space, especially from the CLI. This computer has the one SSD (222~ GB) and two additional TB drives. I’m surprised to see the SSD full as I put files on the other drives.

sda      8:0    0 238.5G  0 disk 
├─sda1   8:1    0   300M  0 part /boot/efi
└─sda2   8:2    0 238.2G  0 part /
sdb      8:16   0   1.8T  0 disk 
└─sdb1   8:17   0   1.8T  0 part 
sdc      8:32   0   1.8T  0 disk 
└─sdc1   8:33   0   1.8T  0 part
13

This is a good candidate for your problem - your disk ist full.

There are a couple of ways to address this.
All of them aimed at creating some space.

One is to clear the pacman cache:
sudo paccache -rk1
(this will leave one copy, the newest one, in cache)
or
sudo rm -rf /var/cache/pacman/pkg/*
(this will delete all cached packages and they will need to be downloaded again for the update,
which you should run again once you have created some space)

Will only be effective if there are many packages in there - but worth a try.

Next is - if your disk is large and the file system is ext4 - to reduce the amount of space that is reserved for the root user only,
thereby giving non root users access to a bit more space:

sudo tune2fs -m 1 /dev/sda2

By default, the reserved space is 5% - this reduces that amount to 1%.

The next is to go through your installed Snap packages and remove what you do not need - there are some that are different only in version.
Typically you only need one - the newest one.

The last output you posted was from:
lsblk

You see more if you use:
lsblk -f

… see how far this get’s you

and, lastly - enable the display manager service again, we disabled it and it won’t even try to start automatically now:

systemctl enable lightdm.service
systemctl start lightdm.service

14

Thank you. That did it! Thanks so much.

1 Like
15

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