-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polybar misplacement #13
Comments
Tried restarting, reverting to Awesome and polybar default config, but the problem is still there. I don't know if this has to do with picom or something related. |
Can you share the config you're using currently? |
Here's my rc.lua config. Polybar and picom are the same as the ones in your repo. -- Importing libraries
local gears = require('gears')
local awful = require('awful')
local wibox = require('wibox')
require('awful.autofocus')
local beautiful = require('beautiful')
local keys = require('keys')
-- Variables
theme_path = string.format('%s/.config/awesome/themes/%s.lua', os.getenv('HOME'), 'default')
beautiful.init(theme_path)
-- Layouts
awful.layout.layouts = {
--awful.layout.suit.fair,
awful.layout.suit.tile,
--awful.layout.suit.spiral.dwindle,
awful.layout.suit.max,
--awful.layout.suit.magnifier,
--awful.layout.suit.tile.bottom,
--awful.layout.suit.tile.top,
--awful.layout.suit.corner.nw,
--awful.layout.suit.fair.horizontal,
--awful.layout.suit.spiral,
--awful.layout.suit.max.fullscreen,
--awful.layout.suit.corner.ne,
--awful.layout.suit.corner.sw,
--awful.layout.suit.corner.se,
awful.layout.suit.floating,
}
-- Virtual desktops/ Tabs
awful.screen.connect_for_each_screen(function(s)
local tagTable = {}
for i = 1, keys.tags do
table.insert(tagTable, tostring(i))
end
awful.tag(tagTable, s, awful.layout.layouts[1])
end)
awful.rules.rules = {
-- All windows
{ rule = { },
properties = {
border_width = beautiful.border_width,
focus = awful.client.focus.filter,
raise = true,
keys = keys.clientkeys,
buttons = keys.clientbuttons,
screen = awful.screen.preferred,
placement = awful.placement.no_overlap+awful.placement.no_offscreen,
--size_hints_honor = false,
},
-- Floating exceptions
{ rule_any = {
class = {'Lxappearance', 'qt5ct'},
name = {'Event Tester'}, --xev
role = {'pop-up', 'GtkFileChooserDialog'},
type = {'dialog'}
},
properties = {floating = true}
}
}
-- Enable sloppy focus
client.connect_signal('mouse::enter', function(c)
c:emit_signal('request::activate', 'mouse_enter', {raise = false})
end)
-- Autostart
-- awful.spawn.with_shell('redshift -x && redshift -O 4000K')
awful.spawn.with_shell('$HOME/.config/polybar/launch.sh')
awful.spawn.with_shell('killall dunst; dunst')
awful.spawn.with_shell('picom -b')
-- awful.spawn.with_shell('feh --bg-fill -r -z $HOME/Immagini/wallpapers/0330.jpg')
awful.spawn.with_shell('feh --bg-center $HOME/Immagini/wallpapers/0330.jpg')
-- Garbage Collection
collectgarbage('setpause', 110)
collectgarbage('setstepmul', 1000)
|
Ohk, try this it will start polybar again and not with awesome, as It happened to me earlier but then it just stopped, so I interpreted as if it was cause it was spawning at the same time..., if running that renders polybar at bottom of the screen, you can try spawning it with other methods instead of
|
Tried commenting out I'll try in some days when I reinstall Arch from scratch, maybe the issue will disappear someway. I'll keep you updated if u want. |
Can you check if the issue is due to the config, and nothing else? |
@nuzzzen The issue is with polybar Edit: BTW I have asked about this issue on reddit, if you want to add comments to the issue, please do. |
Thanks @WitherCubes well that does helps close this issue, Moreover I must start being up to date with the changes/releases made to the programs I use... |
I'm having issues with polybar on Awesome WM. The bar fails to assume correct position. In my case I tried to set the bar on top, and it kinda works but as you can see on the screenshot, it's in the middle of the way and overlaps windows.
I tried applying the polybar default and your config, both top and bottom position, but results didn't change.
On HerbstluftWM (my prev WM) this problem doesn't exist, therefore I think this is related to the Awesome config, but can't figure out what to edit, since I'm relatively new to this WM.
The following is
bottom = false
This one is
bottom = true
I can post my
rc.lua
config if needed, but I didn't change almost anything from the one in the repo.Hope someone can point me to the correct solution.
The text was updated successfully, but these errors were encountered: