bumblebee-status: `Could not parse JSON` error on boot, resolves after i3 refresh
Bug Report
Description
Affected module: All Version used: AUR
<description> On first boot I get this error displayed in the i3 bar:
After I reload i3 everything works as expected, it only happens just after I start the computer
How to reproduce
Config File used:
[core]
modules=spotify,sensors2,cpu,memory,disk,datetime,pulseout,dunst
autohide=cpu,memory,disk,sensors2
theme=custom-powerline
[module-parameters]
disk.format={left}
memory.format={percent:05.02f}%
cpu.format={:05.02f}%
datetime.format=%d/%m/%y %H:%M
cpu.percpu=true
sensors2.chip_include=coretemp, acpitz
sensors2.showcpu=false
sensors2.showname=true
spotify.format={artist}-{title}
Theme file used:
{
"icons": [ "awesome-fonts" ],
"colors": [{
"red": "#BF616A",
"orange": "#D08770",
"yellow": "#EBCB8B",
"green": "#A3BE8C"
}],
"defaults": {
"warning": {
"fg": "#2E3440",
"bg": "#D08770"
},
"critical": {
"fg": "#2E3440",
"bg": "#BF616A"
},
"separator-block-width": 0
},
"cycle": [
{ "fg": "#D4E4F1", "bg": "#260273"},
{ "fg": "#D4E4F1", "bg": "#150140"}
],
"dnf": {
"good": {
"fg": "#A3BE8C",
"bg": "#2E3440"
}
},
"apt": {
"good": {
"fg": "#A3BE8C",
"bg": "#2E3440"
}
},
"pacman": {
"good": {
"fg": "#A3BE8C",
"bg": "#2E3440"
}
},
"battery": {
"charged": {
"fg": "#2E3440",
"bg": "#A3BE8C"
},
"charging": {
"fg": "#2E3440",
"bg": "#81A1C1"
}
},
"pomodoro": {
"paused": {
"fg": "#2E3440",
"bg": "#D08770"
},
"work": {
"fg": "#2E3440",
"bg": "#EBCB8B"
},
"break": {
"fg": "#A3BE8C",
"bg": "#2E3440"
}
}
}
i3 bar command:
bar {
status_command bumblebee-status
font pango:DejaVu Sans Mono, FontAwesome 10
tray_output primary
tray_padding 4
#mode hide
colors {
background #090126
focused_workspace #EFB893 #EFB893 #150140
active_workspace #260273 #260273 #ffffff
inactive_workspace #150140 #150140 #ffffff
}
}
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 18 (8 by maintainers)
Commits related to this issue
- [main] fix i3 protocol buf on error messages ("could not parse JSON") Errors during startup currently cause bumblebee-status to mistakenly output the first line of output (the "version" line) of the ... — committed to tobi-wan-kenobi/bumblebee-status by tobi-wan-kenobi 2 years ago
- [core] log exceptions to enable error investigation, log exceptions. see #940 — committed to tobi-wan-kenobi/bumblebee-status by tobi-wan-kenobi 2 years ago
- [modules/pulsectl] fix case when no devices are available no devices lead to an exception that completely stopped bumblebee-status from processing data. handle this case more gracefully by defaultin... — committed to tobi-wan-kenobi/bumblebee-status by tobi-wan-kenobi 2 years ago
Thank you! Works like a charm now. It indeed displays 0 for maybe a second but then it kicks in nicely.
Glad that this is resolved!
I have a pipewire setup, and I believe the module works there. But I will investigate, thank you kindly!
installing
pulseaudioand removingpipewire-pulseresolved the issue… sorry for the big circle!Is there a module that works with pipewire? I can see there’s amixer but it doesn’t seem as fleshed out. As far as I thought pipewire was supposed to be a drop-in replacement for pulseaudio… perhaps there’s a way to make pulseout/pulsein compatable or a pipewire version if there’s not one already? That’s just me tossing out thoughts but I can work around this now.
Thanks so much for the help and I really love the work on bumblebee-status!