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

Pager displays incorrect workspaces #17

Open
jmbell128 opened this issue Dec 24, 2018 · 2 comments
Open

Pager displays incorrect workspaces #17

jmbell128 opened this issue Dec 24, 2018 · 2 comments

Comments

@jmbell128
Copy link

jmbell128 commented Dec 24, 2018

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.

  1. 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
Copy link
Owner

avivace commented Dec 27, 2018

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
Copy link

vishnumad commented Jan 22, 2019

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.

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

No branches or pull requests

3 participants