Skip to content
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

Switching to an empty workspace is broken after v3.1.0 #41

Open
tkapias opened this issue Jan 29, 2025 · 2 comments
Open

Switching to an empty workspace is broken after v3.1.0 #41

tkapias opened this issue Jan 29, 2025 · 2 comments

Comments

@tkapias
Copy link

tkapias commented Jan 29, 2025

OS : Debian Testing
WM : i3wm, single display

I had to downgrade to v3.0.0, because with v3.1.0 or v3.1.1 I could not switch to an empty workspace anymore.

Using mod+2 from workspace 1 just gives a flicker on the screen.

Also, I use a script to toggle some windows from the scratchpad to the current workspace and back, but after v3.1.0 the toggling does not respect the current workspace and can send me to another one randomly.

My i3wsr config:

[general]
display_property = "instance"
separator = "  "
empty_label = ""

[options]
no_icon_names = true
no_names = false
remove_duplicates = true

[aliases.class]
"firefox-esr" = "Firefox"

[icons]
Firefox = "󰈹"
KeePassXC = ""
mpv = "󰐍"
Pcmanfm = ""
Qalculate-gtk = "󰃬"
scrcpy = "󰓷"
Kitty-Quake = ""
@roosta
Copy link
Owner

roosta commented Jan 29, 2025

Hi @tkapias, thanks for reporting. I think this might be related to this, and the fixes done to resolve that. I've experienced similar issues when debugging that issue. I'll be sure to let you know as soon as it's been resolved, it's a long standing issue, but if I have to revert out the fix, it's still preferable to what you're reporting.

roosta added a commit that referenced this issue Jan 31, 2025
This got manngled in the sway refactor, it's only suppose to set class
if the cmd arg is provided, overruling the config, but the way it was
working would force it to use class regardless of what was in the
config when no arg was provided.

I found this issue while debugging #41
@roosta
Copy link
Owner

roosta commented Jan 31, 2025

Hi again, I was unable to reproduce your issue with the same config, monitor count, and i3 and the latest version of i3wsr. Not the scratchpad or flickering you mention. Could you tell me your i3 version, and try to run v3.1.1 or git with the flag --verbose, and see if the log output can tell us more (it's gonna be very verbose, so it's easiest to run a minimal reproducible setup)

I was however able to fix a different issue, when I was running your config, I noticed that display_property when set to instance wasn't actually using the instance. I doubt its related to your issue, but glad I caught it never the less.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants