[Solved] Waybar not appearing because of connection refused

LaurentMercier · 2025-12-28 11:43:51

Hi,

I've had this bug on and off for a while now and sometimes my waybar appears and sometimes it doesn't after a reboot. I was modifying my config, thinking it was a problem with waybar itself, but I now think it is caused by pipewire-pulse. I think the connection refused error in waybar is actually the one from pipewire-pulse. So far, I've reinstalled waybar, pipewire-pulse and pipewire-alsa, and done a full system upgrade, with no luck. If it matters, I have hyprland on my machine, which is a Lenovo Thinkpad P16s Gen 2.

Here is the output of "waybar -l debug":

[2025-12-28 12:27:30.954] [debug] Try expanding: $XDG_CONFIG_HOME/waybar/config
[2025-12-28 12:27:30.954] [debug] Try expanding: $XDG_CONFIG_HOME/waybar/config.jsonc
[2025-12-28 12:27:30.954] [debug] Try expanding: $HOME/.config/waybar/config
[2025-12-28 12:27:30.954] [debug] Try expanding: $HOME/.config/waybar/config.jsonc
[2025-12-28 12:27:30.954] [debug] Try expanding: $HOME/waybar/config
[2025-12-28 12:27:30.954] [debug] Try expanding: $HOME/waybar/config.jsonc
[2025-12-28 12:27:30.954] [debug] Try expanding: /etc/xdg/waybar/config
[2025-12-28 12:27:30.954] [debug] Try expanding: /etc/xdg/waybar/config.jsonc
[2025-12-28 12:27:30.954] [debug] Found config file: /etc/xdg/waybar/config.jsonc
[2025-12-28 12:27:30.954] [info] Using configuration file /etc/xdg/waybar/config.jsonc
[2025-12-28 12:27:30.954] [error] Could not connect: Connection refused

Here is the output of "pipewire-pulse start":

[E][12:33:12.886337] mod.rt       | [     module-rt.c:  294 pw_rtkit_bus_get()] Failed to connect to session bus: Failed to connect to socket /run/user/1000/bus: Connection refused
[W][12:33:12.895199] mod.protocol-pulse | [        server.c:  639 start_unix_server()] server 0x55c75429d6b0: unlinking stale socket '/run/user/1000/pulse/native'
[E][12:33:12.895379] spa.dbus     | [          dbus.c:  333 impl_connection_get()] Failed to connect to session bus: Failed to connect to socket /run/user/1000/bus: Connection refused
[E][12:33:12.896215] mod.fallback-sink | [module-fallback-:  426 pipewire__module_init()] can't connect: Host is down
[E][12:33:12.896281] default      | [           cmd.c:   51 do_cmd()] can't run command load-module module-always-sink: Host is down

Here is the output of "dmesg": https://0x0.st/Pity.txt.

Here is the output of "journalctl -b": https://0x0.st/Pit3.txt.

If you need any other output, I can provide them also. Thank you!

Last edited by LaurentMercier (2026-01-12 12:41:11)

system72 · 2025-12-28 15:24:57

on reboot is your fs being mounted ro, just from the logs it kinda feels that way

also what is 99-thinkpad-input.rules?

Dec 28 12:17:31 LaptopLM (dbus-broker-launch)[848]: dbus-broker.service: Failed to set up standard input: Permission denied
Dec 28 12:17:31 LaptopLM (dbus-broker-launch)[848]: dbus-broker.service: Failed at step STDIN spawning /usr/bin/dbus-broker-launch: Permission denied
Dec 28 12:17:31 LaptopLM (pipewire)[849]: pipewire.service: Failed to set up standard input: Permission denied
Dec 28 12:17:31 LaptopLM (pipewire)[849]: pipewire.service: Failed at step STDIN spawning /usr/bin/pipewire: Permission denied
Dec 28 12:17:31 LaptopLM systemd[766]: dbus-broker.service: Main process exited, code=exited, status=208/STDIN
Dec 28 12:17:31 LaptopLM systemd[766]: dbus-broker.service: Failed with result 'exit-code'.
Dec 28 12:17:31 LaptopLM systemd[766]: Failed to start D-Bus User Message Bus.

Dec 28 12:17:32 LaptopLM (systemctl)[871]: dbus.socket: Failed to set up standard input: Permission denied
Dec 28 12:17:32 LaptopLM (systemctl)[871]: dbus.socket: Failed at step STDIN spawning /usr/bin/systemctl: Permission denied

Dec 28 12:17:39 LaptopLM polkitd[1148]: Error opening /dev/null: Permission denied

LaurentMercier · 2025-12-28 15:41:37

system72 wrote:

on reboot is your fs being mounted ro, just from the logs it kinda feels that way
also what is 99-thinkpad-input.rules?

For the 99-thinkpad-input.rules it was an AI-provided fix for my keyboard since it would just shutdown and be not usable while playing Minecraft and I would have to reboot, it did help but I had this shutdown problem randomly the other day too so I'm not that sure if it works. For the file system I don't think it is being mounted ro, here is the output of "mount"

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=14171972k,nr_inodes=3542993,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p2 on / type btrfs (rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64,usrquota)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot,memory_hugetlb_accounting)
none on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=42,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=8318)
none on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-resolved.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=14180552k,nr_inodes=1048576,inode64,usrquota)
/dev/nvme0n1p2 on /.snapshots type btrfs (rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=260,subvol=/@.snapshots)
/dev/nvme0n1p2 on /home type btrfs (rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home)
/dev/nvme0n1p2 on /var/cache/pacman/pkg type btrfs (rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@pkg)
/dev/nvme0n1p2 on /var/log type btrfs (rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@log)
/dev/nvme0n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=2836108k,nr_inodes=709027,mode=700,uid=1000,gid=1000,inode64)
tmpfs on /run/user/968 type tmpfs (rw,nosuid,nodev,relatime,size=2836108k,nr_inodes=709027,mode=700,uid=968,gid=968,inode64)
overlay on /var/lib/docker/overlay2/b44e13c22946ec0c044968db1131a9fa60ff1eacf41db0da1f5d8d79308e0207/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/E7W544RDNJXWRX7NVNPD644XW7:/var/lib/docker/overlay2/l/DPQFEMDAQSXJXILJBWH6FMSZT2:/var/lib/docker/overlay2/l/PH4LZLYIIPNG2CTZRGHAYCBHFC:/var/lib/docker/overlay2/l/RPR4WSILLTKICWW4OJTUMM2NA3:/var/lib/docker/overlay2/l/PM5OK2EBSGFUFEWSYZLO524D64:/var/lib/docker/overlay2/l/XWZ5FKZ2D3TZHGGRGB62AW4VEM:/var/lib/docker/overlay2/l/2ZRLLBU3GQFPRFLUDCPUBUHNKB:/var/lib/docker/overlay2/l/BVNSPUQU6U7S4LU2GB5EJCQUXO:/var/lib/docker/overlay2/l/PLV4SPGUL5WRG6342UUHD5INJD:/var/lib/docker/overlay2/l/W3P7KNYZSTI4YF5RPQRXFKAYXB:/var/lib/docker/overlay2/l/4ZM5PJKZWBY4KDVAG4Y6PQTTRG:/var/lib/docker/overlay2/l/ZLCUSLSDVZWRACXCTDKW2XXGA2:/var/lib/docker/overlay2/l/WQWOX56PE3VM5WSIVWJPTHLFCW:/var/lib/docker/overlay2/l/ZEHGHA4LR57BAVUKROL27CDA76:/var/lib/docker/overlay2/l/ZTN6U4VG556AIEA7G7QN3D5GIY,upperdir=/var/lib/docker/overlay2/b44e13c22946ec0c044968db1131a9fa60ff1eacf41db0da1f5d8d79308e0207/diff,workdir=/var/lib/docker/overlay2/b44e13c22946ec0c044968db1131a9fa60ff1eacf41db0da1f5d8d79308e0207/work,index=off)
overlay on /var/lib/docker/overlay2/746c60fe385c4901ef97e249ee9f005c5385b1f2e84e72b5c1fbb6e408e4b33b/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/S3VZSOYLYZI4HNJXM3K5YQMMIC:/var/lib/docker/overlay2/l/DPQFEMDAQSXJXILJBWH6FMSZT2:/var/lib/docker/overlay2/l/PH4LZLYIIPNG2CTZRGHAYCBHFC:/var/lib/docker/overlay2/l/RPR4WSILLTKICWW4OJTUMM2NA3:/var/lib/docker/overlay2/l/PM5OK2EBSGFUFEWSYZLO524D64:/var/lib/docker/overlay2/l/XWZ5FKZ2D3TZHGGRGB62AW4VEM:/var/lib/docker/overlay2/l/2ZRLLBU3GQFPRFLUDCPUBUHNKB:/var/lib/docker/overlay2/l/BVNSPUQU6U7S4LU2GB5EJCQUXO:/var/lib/docker/overlay2/l/PLV4SPGUL5WRG6342UUHD5INJD:/var/lib/docker/overlay2/l/W3P7KNYZSTI4YF5RPQRXFKAYXB:/var/lib/docker/overlay2/l/4ZM5PJKZWBY4KDVAG4Y6PQTTRG:/var/lib/docker/overlay2/l/ZLCUSLSDVZWRACXCTDKW2XXGA2:/var/lib/docker/overlay2/l/WQWOX56PE3VM5WSIVWJPTHLFCW:/var/lib/docker/overlay2/l/ZEHGHA4LR57BAVUKROL27CDA76:/var/lib/docker/overlay2/l/ZTN6U4VG556AIEA7G7QN3D5GIY,upperdir=/var/lib/docker/overlay2/746c60fe385c4901ef97e249ee9f005c5385b1f2e84e72b5c1fbb6e408e4b33b/diff,workdir=/var/lib/docker/overlay2/746c60fe385c4901ef97e249ee9f005c5385b1f2e84e72b5c1fbb6e408e4b33b/work,index=off)
nsfs on /run/docker/netns/3381b2b5ec35 type nsfs (rw)
nsfs on /run/docker/netns/6688207399c3 type nsfs (rw)

And the output of "findmnt -n -o OPTIONS /":

rw,relatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@

Last edited by LaurentMercier (2025-12-28 15:43:10)

system72 · 2025-12-28 15:47:16

try removing that udev rule file and rebooting

LaurentMercier · 2025-12-28 16:02:24

system72 wrote:

try removing that udev rule file and rebooting

Hey you might be onto something there, I removed these rules and others from other bs AI-provided fixes, rebooted and I have my waybar now. However, I'm not sure if this is a permanent fix as I had these rules before and sometimes my waybar would appear after reboot and sometimes it wouldn't, I wonder if it related to something else also.

system72 · 2025-12-28 16:28:52

maybe try rebooting a couple times to see if you can still reproduce now that you've removed the problematic file

LaurentMercier · 2025-12-28 17:03:44

system72 wrote:

maybe try rebooting a couple times to see if you can still reproduce now that you've removed the problematic file

Still working after 5 reboots, I guess I'll wait and see if it happens again in the future and post the logs and journals then. Thanks for the help!

Arch Linux

#1 2025-12-28 11:43:51

[Solved] Waybar not appearing because of connection refused

#2 2025-12-28 15:24:57

Re: [Solved] Waybar not appearing because of connection refused

#3 2025-12-28 15:41:37

Re: [Solved] Waybar not appearing because of connection refused

#4 2025-12-28 15:47:16

Re: [Solved] Waybar not appearing because of connection refused

#5 2025-12-28 16:02:24

Re: [Solved] Waybar not appearing because of connection refused

#6 2025-12-28 16:28:52

Re: [Solved] Waybar not appearing because of connection refused

#7 2025-12-28 17:03:44

Re: [Solved] Waybar not appearing because of connection refused

Board footer