#Polybar issues
45 messages · Page 1 of 1 (latest)
yes
there's .local but no bin inside it
if bin doesn't exist then nvm. Make a text file with the name launch-polybar.sh
#!/usr/bin/env bash
launch-polybar.sh — start Polybar under KDE Plasma 6 with a custom KWin rule
1) Define a unique class name for this bar:
CLASS_NAME="PolybarDock"
2) Kill any existing instances (optional):
killall -q polybar
sleep 0.5
3) Launch Polybar with that class:
-r : reload on config changes
--reload : same
--name : set WM_CLASS name (both instance and class)
polybar -r --reload --name "$CLASS_NAME" reactor &
4) Wait briefly for the X11 window to appear:
sleep 0.5
5) Define the rule ID and config file:
RULE_ID="polybar-dock-rule"
RULE_FILE="$HOME/.config/kwinrulesrc"
6) Write the rule into kwinrulesrc via kwriteconfig5:
For each property: "true,Force" means “enable and force it”
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key Description "Polybar dock" # 0
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key ExactWMClass "$CLASS_NAME" # 1
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key BorderLess "true,Force" # 2
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key SkipTaskbar "true,Force" # 3
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key SkipPager "true,Force" # 4
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key KeepAbove "true,Force" # 5
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key NoFocus "true,Force" # 6
7) Tell KWin to reload its configuration:
qdbus org.kde.KWin /KWin reconfigure
exit 0
holy
Princess
Compile Error! Click the
reaction for more information.
(You may edit your message to recompile.)
idk if this works, found it on an arch forum
can you put it in a codeblock please lol
yes it's a executable
use these at the beginning and end
yes on it
#
# launch-polybar.sh — start Polybar under KDE Plasma 6 with a custom KWin rule
# 1) Define a unique class name for this bar:
CLASS_NAME="PolybarDock"
# 2) Kill any existing instances (optional):
killall -q polybar
sleep 0.5
# 3) Launch Polybar with that class:
# -r : reload on config changes
# --reload : same
# --name : set WM_CLASS name (both instance and class)
polybar -r --reload --name "$CLASS_NAME" reactor &
# 4) Wait briefly for the X11 window to appear:
sleep 0.5
# 5) Define the rule ID and config file:
RULE_ID="polybar-dock-rule"
RULE_FILE="$HOME/.config/kwinrulesrc"
# 6) Write the rule into kwinrulesrc via kwriteconfig5:
# For each property: "true,Force" means “enable and force it”
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key Description "Polybar dock" # 0
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key ExactWMClass "$CLASS_NAME" # 1
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key BorderLess "true,Force" # 2
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key SkipTaskbar "true,Force" # 3
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key SkipPager "true,Force" # 4
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key KeepAbove "true,Force" # 5
kwriteconfig5 --file "$RULE_FILE" --group "$RULE_ID" --key NoFocus "true,Force" # 6
# 7) Tell KWin to reload its configuration:
qdbus org.kde.KWin /KWin reconfigure
exit 0
awesomeee
even I'm not sure if this will work, I just found it on a forum post
launch.sh: line 27: kwriteconfig5: command not found
launch.sh: line 28: kwriteconfig5: command not found
launch.sh: line 29: kwriteconfig5: command not found
launch.sh: line 30: kwriteconfig5: command not found
launch.sh: line 31: kwriteconfig5: command not found
launch.sh: line 32: kwriteconfig5: command not found
launch.sh: line 33: kwriteconfig5: command not found
launch.sh: line 36: qdbus: command not found
[caf@archlinux polybar]$```
same as before
btw do u use Plasma X11 or pure Plasma
that can't be right
cuz polybar doesn't even support Wayland
hmm must be XWayland
you should try X11 once, it won't break anything
I have a really janky idea to force the polybar to float at specific screen coordinates
but it'll be really bad
Wayland actually really sucks
yup lol
it was the only reason I stopped using KDE entirely
anyways that was the issue afterall, wayland
so if you wanna really solve it, move to X11 and it'll work like a charm