BSPWM / SXHKD not properly starting after pacman -Syu

After logging in after updating packages it seems my BSPWM / SXHKD aren't properly starting. I kinda cheat and run bspwm & and sxhkd & to start them up and gather these logs but it obviously leaves an ugly terminal in the corner and doesn't fix the root issue.

inxi -Faz

Please let me know what other logs may help!

Short text output do not need PrivateBin :slight_smile: and expire in 6 days.

System:    Kernel: 5.12.9-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=ee6dc5e2-c273-434a-91b0-bb79d8fa66c2 rw
           rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
           systemd.unified_cgroup_hierarchy=1 resume=UUID=6bcd8157-9eb9-450e-9e30-cf939c023754 loglevel=3
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: bspwm 0.9.10 vt: 7 dm: LightDM 1.30.0
           Distro: Garuda Linux base: Arch Linux
Machine:   Type: Laptop System: Micro-Star product: GS65 Stealth 9SG v: REV:1.0 serial: <filter> Chassis: type: 10
           serial: <filter>
           Mobo: Micro-Star model: MS-16Q4 v: REV:1.0 serial: <filter> UEFI: American Megatrends v: E16Q4IMS.118
           date: 05/18/2020
Battery:   ID-1: BAT1 charge: 55.9 Wh (96.4%) condition: 58.0/80.3 Wh (72.3%) volts: 16.2 min: 15.2 model: MSI BIF0_9
           type: Li-ion serial: N/A status: Unknown
CPU:       Info: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP arch: Kaby Lake note: check family: 6
           model-id: 9E (158) stepping: A (10) microcode: DE cache: L2: 12 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399
           Speed: 4252 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 4252 2: 4401 3: 4402 4: 4402 5: 4471 6: 4400 7: 4400
           8: 4353 9: 4500 10: 4399 11: 4347 12: 4401
           Vulnerabilities: 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: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
           Type: srbds mitigation: Microcode
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Micro-Star MSI driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b
           class-ID: 0300
           Device-2: NVIDIA TU104M [GeForce RTX 2080 Mobile] vendor: Micro-Star MSI driver: nvidia v: 465.31
           alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1e90 class-ID: 0300
           Device-3: Acer HD Webcam type: USB driver: uvcvideo bus-ID: 1-11:3 chip-ID: 5986:211c class-ID: 0e02
           Display: x11 server: X.Org 1.20.11 compositor: picom v: git-60eb0 driver: loaded: modesetting,nvidia display-ID: :0
           screens: 1
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
           Monitor-1: eDP-1-1 res: 1920x1080 hz: 240 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
           OpenGL: renderer: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 465.31 direct render: Yes
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
           alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
           Sound Server-1: ALSA v: k5.12.9-zen1-1-zen running: yes
           Sound Server-2: JACK v: 1.9.18 running: no
           Sound Server-3: PulseAudio v: 14.2 running: yes
           Sound Server-4: PipeWire v: 0.3.29 running: no
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] vendor: Rivet Networks Killer driver: iwlwifi v: kernel
           port: 5000 bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
           IF: wlo1 state: up mac: <filter>
           Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: 3000
           bus-ID: 3c:00.0 chip-ID: 1969:e0b1 class-ID: 0200
           IF: enp60s0 state: down mac: <filter>
           IF-ID-1: br-11d0ea543d18 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
           IF-ID-2: docker0 state: down mac: <filter>
           IF-ID-3: veth62d4a56 state: up speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8 bus-ID: 1-14:4
           chip-ID: 8087:0aaa class-ID: e001
           Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes
           address: <filter>
Drives:    Local Storage: total: 953.87 GiB used: 82.52 GiB (8.7%)
           SMART Message: Required tool smartctl not installed. Check --recommends
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLB1T0HALR-00000 size: 953.87 GiB block-size:
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: EXA7301Q scheme: GPT
Partition: ID-1: / raw-size: 919.29 GiB size: 919.29 GiB (100.00%) used: 82.52 GiB (9.0%) fs: btrfs dev: /dev/nvme0n1p2
           maj-min: 259:2
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1
           maj-min: 259:1
           ID-3: /home raw-size: 919.29 GiB size: 919.29 GiB (100.00%) used: 82.52 GiB (9.0%) fs: btrfs dev: /dev/nvme0n1p2
           maj-min: 259:2
           ID-4: /var/log raw-size: 919.29 GiB size: 919.29 GiB (100.00%) used: 82.52 GiB (9.0%) fs: btrfs dev: /dev/nvme0n1p2
           maj-min: 259:2
           ID-5: /var/tmp raw-size: 919.29 GiB size: 919.29 GiB (100.00%) used: 82.52 GiB (9.0%) fs: btrfs dev: /dev/nvme0n1p2
           maj-min: 259:2
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
           ID-1: swap-1 type: partition size: 34.32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
           ID-2: swap-2 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
           ID-3: swap-3 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
           ID-4: swap-4 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
           ID-5: swap-5 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
           ID-6: swap-6 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
           ID-7: swap-7 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
           ID-8: swap-8 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
           ID-9: swap-9 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
           ID-10: swap-10 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8
           ID-11: swap-11 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9
           ID-12: swap-12 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10
           ID-13: swap-13 type: zram size: 2.6 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11
Sensors:   System Temperatures: cpu: 74.0 C mobo: N/A gpu: nvidia temp: 57 C
           Fan Speeds (RPM): N/A
Info:      Processes: 328 Uptime: 10m wakeups: 1 Memory: 31.2 GiB used: 2.39 GiB (7.7%) Init: systemd v: 248 tool: systemctl
           Compilers: gcc: 11.1.0 clang: 12.0.0 Packages: pacman: 1807 lib: 506 Shell: fish v: 3.2.2 running-in: alacritty
           inxi: 3.3.04

:slight_smile:

Hardware seems fine.
IDK nothing about SXHKD (is a simple X hotkey daemon) and BSPWM, so stay tuned for help please :slight_smile:

2 Likes

I noticed the same issue after updating the other day. I just narrowed the issue down to the xfce4-session package update going from 4.16.0-1 to 4.16.0-2. I have everything else updated, just rolled this package back and added it to my IgnorePkg. Could the session manager update possibly be overwriting the settings built into Garuda?

2 Likes

Hm, I rolled back xfce4-session session back to 4.16.0-1 and added it to my IgnorePkg as well but nothing changed on reboot. But I also had to do it from Arch's Archives since my cache got cleared at some point, so perhaps I lost whatever settings required.

I highly doubt it, source didnt change and the update just changed description & URL :eyes:

2 Likes