polybar: [Bug]: i3: Failed to reconnect socket

Checklist

  • I have read the appropriate section in the contributing guidelines
  • I believe this issue is a problem with polybar itself and not a misconfiguration on my part
  • I have searched for other open and closed issues that may have already reported this problem
  • I have checked the known issues page for this problem.
  • I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce

  1. polybar
  2. Wait for it to fail (random?)

Minimal config

; Init
[settings]
screenchange-reload = true
pseudo-transparency = true

[colors]
background = #000000
background-alt = #000000
foreground = #C5C8C6
primary = #5fdbf6
secondary = #076b81
tertiary = #ec4795
alert = #f0ad19
disabled = #444444
invisible = #00000000

[bar/bottom]
font-0 = FiraCode Nerd Font Mono;2
width = 100%
height = 2.5%
radius = 12
padding-right = 1
padding-left = 0

module-margin = 1
line-size = 3
background = ${colors.background}
foreground = ${colors.foreground}
border-size = 1
border-color = ${colors.invisible}

separator = |
separator-foreground = ${colors.tertiary}
modules-left = xworkspaces xwindow
cursor-click = pointer
cursor-scroll = ns-resize
enable-ipc = true
tray-position = right
bottom = true

wm-restack = i3

; override-redirect = true
[module/xworkspaces]
type = internal/i3
format = <label-state>
label-focused = %name%
label-focused-background = ${colors.primary}
label-focused-foreground = ${colors.background}
label-focused-underline= ${colors.secondary}
label-focused-padding = 1
label-empty = %name%
label-empty-foreground = ${colors.disabled}
label-empty-padding = 1

Polybar log

polybar|notice:  Parsing config file: /home/ging/.config/polybar/config.ini
polybar|notice:  Listening for IPC messages (PID: 2297951)
polybar|notice:  Loading module 'xworkspaces' of type 'internal/i3'
polybar|notice:  Loading module 'xwindow' of type 'internal/xwindow'
polybar|notice:  Loading module 'filesystem' of type 'internal/fs'
polybar|notice:  Loading module 'ram' of type 'internal/memory'
polybar|notice:  Loading module 'swap' of type 'internal/memory'
polybar|notice:  Loading module 'cpu' of type 'internal/cpu'
polybar|notice:  Loading module 'wlan0' of type 'internal/network'
polybar|notice:  Loading module 'wlan1' of type 'internal/network'
polybar|error: Disabling module "wlan1" (reason: Invalid network interface "wlan1")
polybar|notice:  Loading module 'fanspeed' of type 'custom/script'
polybar|notice:  Loading module 'pulseaudio' of type 'internal/pulseaudio'
polybar|notice:  pulseaudio: using default sink alsa_output.pci-0000_e6_00.3.codec-output
polybar|notice:  Loading module 'temperature' of type 'internal/temperature'
polybar|notice:  Loading module 'battery' of type 'internal/battery'
polybar|notice:  Loading module 'date' of type 'internal/date'
polybar|notice:  Loaded 12 modules
polybar|notice:  Loaded font "FiraCode Nerd Font Mono" (name=FiraCode Nerd Font Mono, offset=2, file=/home/ging/.local/share/fonts/NerdFonts/Fira Code Regular Nerd Font Complete Mono.ttf)
polybar|warn:  Ignoring restack of i3 window (not needed when `override-redirect = false`)
polybar|error: Failed to query _XEMBED_INFO, removing client... (XCB_WINDOW (3))
polybar|warn:  module/xworkspaces: Attempting to reconnect socket (reason: Unexpected EOF while reading header)
polybar|notice:  Received signal(15): Terminated
polybar|notice:  Termination signal received, shutting down...
polybar|error: module/xworkspaces: Failed to reconnect socket (reason: Unexpected EOF while reading header)

Expected behavior

Polybar doesn’t crash.

Actual behavior

Polybar either loses the xworkspaces module or just disappears and requires a restart.

Window Manager and Version

i3-gaps v4.20.1

Linux Distribution

EndeavourOS

Polybar version

polybar 3.6.3-45-g1ee11f7c

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/sbin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -O3 -DNDEBUG -Wall -Wextra -Wpedantic -Wsuggest-override
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wall -Wextra -Wpedantic -Wsuggest-override  -Wall -Wextra -Wpedantic -Wsuggest-override

Additional Context / Screenshots

i am stumped, i’ll happen to look down where polybar usually is and realize either A: the xworkspaces module is missing, or B: the entire bar is just gone. It’s taken about two weeks just to get it to happen again.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 18 (3 by maintainers)

Most upvoted comments

I’m observing a similar issue on Arch after upgrading to i3-wm 4.22-2. However, my polybar doesn’t crash completely, but instead stops updating the module (i.e. it highlights whichever workspace it was on when it lost the socket and then doesn’t update it when I switch workspaces).

Log attached

So, bug seems to be fixed in some commit after release 3.6.3 On arch linux I used the AUR polybar-git package. This will build polybar 3.6.3-87-gfc423c09. The error will then disapppear. @patrick96 maybe you can make a new release? The current one is 9 month old.