Manjaro doesnt shut down correctly

When I shutdown, some apps still remain open (I think the one im focued on?) and the rest is just a black screen. If I close the open apps, there is just a black screen and my mouse, but manjaro doesnt seem to shut down.

Random logs that might maybe be helpful?

$ journalctl -b -1

(Removed beginning due to char limit, but I shut down my pc at 21:16:00 and left it running until 21:20:00 at which point I forced a shutdown)

Oct 28 21:16:01 chris systemd[855]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Oct 28 21:16:01 chris systemd[855]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Oct 28 21:16:03 chris systemd[855]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Oct 28 21:16:03 chris systemd[855]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Oct 28 21:16:03 chris kded6[948]: Service  ":1.44" unregistered
Oct 28 21:16:03 chris msm_kde_notifier[1137]: Shutting down MSM Notifier...
Oct 28 21:16:03 chris kded6[948]: Service  ":1.46" unregistered
Oct 28 21:16:03 chris plasmashell[963]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot read property 'screenGeometry' of null
Oct 28 21:16:03 chris systemd[855]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 21:16:03 chris systemd[855]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Oct 28 21:16:03 chris systemd[855]: app-pamac\x2dtray\x2dplasma@autostart.service: Consumed 611ms CPU time, 69.2M memory peak.
Oct 28 21:16:03 chris plasmashell[963]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot read property 'plasmoid' of undefined
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_output.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.analog-stereo"
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_output.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.analog-stereo"
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_output.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.analog-stereo"
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_output.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.analog-stereo"
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_input.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.mono-fallback"
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_output.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.analog-stereo"
Oct 28 21:16:03 chris plasmashell[963]: org.kde.pulseaudio: No object for name "alsa_input.usb-Macronix_Razer_Barracuda_Pro_2.4_1234-00.mono-fallback"
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris plasmashell[963]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 28 21:16:03 chris systemd[855]: plasma-plasmashell.service: Consumed 6.954s CPU time, 283.3M memory peak.
Oct 28 21:16:03 chris ksmserver[946]: org.kde.kf6.ksmserver: Connection rejected: ksmserver is shutting down
Oct 28 21:16:07 chris systemd[855]: app-org.xfce.mousepad@1be55a2dda9d4f7e8bdb6c3435a89046.service: Consumed 3.992s CPU time, 25.2M memory peak.
$ inxi -Fza

System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=17112bd4-5fab-4b45-be7d-a3d5e93e61ea rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B360-F GAMING v: Rev 1.xx
    serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
    UEFI: American Megatrends v: 2301 date: 07/10/2020
CPU:
  Info: model: Intel Core i3-8350K bits: 64 type: MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xB (11) microcode: 0xF6
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> 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: 4000 min/max: 800/4000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 4000 2: 4000 3: 4000 4: 4000 bogomips: 32013
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  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: IBRS; IBPB: conditional; STIBP: disabled;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA AD104 [GeForce RTX 4070 SUPER] driver: nouveau v: kernel
    non-free: 550.xx+ status: current (as of 2024-09) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1
    empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:2783 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: nouveau gpu: nouveau display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.83x15.00")
    s-diag: 987mm (38.84") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: Samsung S34J55x serial: <filter> built: 2020
    res: 3440x1440 dpi: 110 gamma: 1.2 size: 797x333mm (31.38x13.11")
    diag: 864mm (34") modes: max: 3440x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: NV194 device-ID: 10de:2783
    memory: 11.67 GiB unified: no
  API: Vulkan v: 1.3.295 layers: N/A device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 4070 SUPER (NVK AD104) driver: mesa nvk
    v: 24.2.4-arch1.0.1 device-ID: 10de:2783 surfaces: xcb,xlib
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl, snd_soc_avs, snd_sof_pci_intel_cnl
    bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA AD104 High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
  Device-3: Razer USA Barracuda Pro 2.4
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-6.1:3 chip-ID: 1532:053a class-ID: 0301
    serial: <filter>
  API: ALSA v: k6.10.13-3-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.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: br-a36a7d871616 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 25.47 TiB used: 28.96 GiB (0.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 34.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST22000NT001-3LS101
    size: 20.01 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: EN01
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD20EURX-63T0FY0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
Partition:
  ID-1: / raw-size: 1.73 TiB size: 1.7 TiB (98.37%) used: 28.93 GiB (1.7%)
    fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 30.8 MiB (32.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 2.62 GiB (8.4%)
  Processes: 225 Power: uptime: 3m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.48 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1186 libs: 328 tools: pamac pm: flatpak pkgs: 0
    Compilers: N/A Shell: Zsh v: 5.9 default: Bash v: 5.2.37 running-in: konsole
    inxi: 3.3.36

Any input would be appreciated, thanks

I tried reverting to kernal 6.6.54-2 but same error occurs, this is a fresh install with the latest iso

Do you use saved session?
Have you tried without?

See 986987987907 other threads

1 Like

This has nothing to do with your problem right now, but 6.10 is EOL… switch to 6.6 LTS or 6.11 is recommend right now.

1 Like

“When session was manually saved” is what it was set to, ill try it with an empty session

Looks like that fixed it, thanks

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