search

avivace / dotfiles

i3 + Plasma: using the i3 window manager on the top of KDE Plasma and other dotfiles, configurations, scripts, workarounds and practises from my Debian Sid machines.
https://www.reddit.com/r/unixporn/comments/64mihc/i3_kde_plasma_a_match_made_in_heaven/
GNU General Public License v3.0
790 stars 47 forks source link

Pager displays incorrect workspaces #17

Open jmbell128 opened 5 years ago

jmbell128 commented 5 years ago

Software Distro: Kubuntu 18.10 Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 QT Version: 5.11.1 Kernel Version: 4.18.0-13-generic OS Type: 64-bit i3 Version: 4.15 (NOT i3-gaps) Hardware Processor: i5-4690 Memory: 16 Gig

Hi, First, thanks for posting this. I've been going back and forth to your reddit post and this repo for a long time and finally decided to take the plunge because, what the hell it's Christmas! Everything works pretty well except that the pager widget is displaying the wrong workspaces/desktops.

I have dual monitors and have left i3bar up just since I just got it set up today. Issues:

  1. When on workspace 1, my left monitor and primary monitor, the pager displays that I am on workspace 2 and vice versa when I am on workspace 2.
  2. Regardless of whatever other workspace I try to switch to afterward (3-10) it will always display that I have switched to workspace 3 in the pager. i3bar gives the correct workspace number. screenshot_20181224_152446

Additional information:

  1. It may help to know that if there is a window open and maximized in a workspace the pager widget shows only half of the workspace being used. To be clear the Mod+# keys work as expected and i3bar reacts correctly. The issue seems to be pager specific.

  2. The only other thing I've noticed and it may be completely unrelated is that when I use firefox or vivaldi to open https://github.com/avivace/dotfiles/issues/8 both browsers crap out and immediately close. I have not noticed this with any other links. I can open another issue for this if you would like. But I haven't yet because I'm unsure if the issue originates with using i3 inside plasma.

I'm not a developer or anything like that but I'll try to see if I can get any more information on these issues. Thanks a lot for the setup, It's pretty awesome minus these setbacks!

avivace commented 5 years ago

Oh hey! I'm glad you finally tried! How is it going? Unfortunately I have this issue, too. This is related to the Plasma Pager widget and we would have to dig how it flags/reads the workspaces to fix or find a workaround..

vishnumad commented 5 years ago

Are you using the Pagermod plasmoid? I had a similar issue with that plasmoid. I just ended up modifying the default pager to be always visible.