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

Atoms when closing inactive workspace - floating sticky window #3696

Closed
Riyyi opened this issue May 3, 2019 · 0 comments · Fixed by #3697
Closed

Atoms when closing inactive workspace - floating sticky window #3696

Riyyi opened this issue May 3, 2019 · 0 comments · Fixed by #3697
Assignees
Labels
4.16 bug reproducible A bug that has been reviewed and confirmed by a project contributor

Comments

@Riyyi
Copy link

Riyyi commented May 3, 2019

Bug related to #3126

Current behavior

https://i.imgur.com/pxV8hGZ.png

As you can see, when moving from workspace 2 to 3, the active workspace is reported incorrectly.
Moving from workspace 2 to 1 does work however.

Reproducing the problem

  • Open a window in workspace 1, 3 and 4, but not 2.
  • Open another window and make it sticky + floating.
  • Go to workspace 1.
  • Go to workspace 2.
  • Go to workspace 3.
  • Go to workspace 4.
  • Go to workspace 3.

Environment

- i3 version

$ i3 --moreversion 2>&- || i3 --version

Binary i3 version:  4.16.1-169-g60a6d149 (2019-04-11, branch "gaps-next") © 2009 Michael Stapelberg and contributors
Running i3 version: 4.16.1-169-g60a6d149 (2019-04-11, branch "gaps-next") (pid 20934)
Loaded i3 config: /home/user/.config/i3/config (Last modified: Fri 03 May 2019 12:06:06 AM CEST, 38855 seconds ago)

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3

- i3 config

set $ws1  "1 "
set $ws2  "2 "
set $ws3  "3 "
set $ws4  "4 "
set $ws5  "5"
set $ws6  "6"
set $ws7  "7"
set $ws8  "8"
set $ws9  "9"
set $ws10 "10"

bindsym $mod+1 workspace $ws1
bindsym $mod+2 workspace $ws2
bindsym $mod+3 workspace $ws3
bindsym $mod+4 workspace $ws4
bindsym $mod+5 workspace $ws5
bindsym $mod+6 workspace $ws6
bindsym $mod+7 workspace $ws7
bindsym $mod+8 workspace $ws8
bindsym $mod+9 workspace $ws9
bindsym $mod+0 workspace $ws10

bindsym $mod+Shift+f fullscreen disable, floating enable, sticky enable

- Software

  • xprop
  • xdotool
  • wmctrl
  • lemonbar

Log

$ reboot
$ i3-msg 'debuglog on; shmlog on; reload'

Perform steps here.

$ DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- https://logs.i3wm.org

Link: https://logs.i3wm.org/logs/5631048062861312.bz2

Distro

  • updated Arch
  • no compositor
@i3bot i3bot added the 4.16 label May 3, 2019
@Airblader Airblader added the bug label May 3, 2019
@orestisfl orestisfl added the reproducible A bug that has been reviewed and confirmed by a project contributor label May 3, 2019
@orestisfl orestisfl self-assigned this May 3, 2019
orestisfl added a commit to orestisfl/i3 that referenced this issue May 3, 2019
The testcase is changed because it was actually incorrect. Easy to
verify because:
> _NET_CURRENT_DESKTOP
> …
> The index of the current desktop. This is always an integer between 0
> and _NET_NUMBER_OF_DESKTOPS - 1.

Fixes i3#3696.
Also updates the viewports.

Finally, fixes an issue with _NET_CURRENT_DESKTOP not being updated
after a workspace rename. Example:
- workspaces 1, 2, 3
- rename workspace 1 to 5
- All workspaces changed their index but _NET_CURRENT_DESKTOP was not
updated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.16 bug reproducible A bug that has been reviewed and confirmed by a project contributor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants