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

[BUG] Not working on arch budgie with budgie 10.5 #2

Open
botrosco opened this issue May 29, 2019 · 10 comments
Open

[BUG] Not working on arch budgie with budgie 10.5 #2

botrosco opened this issue May 29, 2019 · 10 comments

Comments

@botrosco
Copy link

Is this project still maintained if so would you be able to help me with this issue that im having.
Within arch (antergos) the plugin does not seem to work correctly, i am able to rightclick and set the number of workspaces however if clicking or using the scroll wheel while hovering over the applet nothing seems to happen.
Also if i have the default workspace applet open the setting of the number of workspaces doesnt seem to change the number of available workspaces, i am unsure if this is indended or not. I have very little python experience so i dont really know what to look for in the code or if this is an issue that was casued by the move to budgie 10.5.
I havent use this applet before so i am unaware if this ever worked on arch.

@dgaw
Copy link
Owner

dgaw commented May 30, 2019

I haven't used this applet in a while. However I just did a quick check and it seems to work fine on Solus 4.0 with budgie-desktop 10.5.

I'm not sure what might be wrong on Arch but if you feel like troubleshooting this then you can enable some debugging information in the applet by changing line:

logging.basicConfig(level=logging.INFO)

to

logging.basicConfig(level=logging.DEBUG)

and restarting the panel with

budgie-panel --replace &

On my machine this produces the following log when I switch workspaces with a left-click or scroll on the applet:

DEBUG:workspaces_compact:on_workspace_changed()
DEBUG:workspaces_compact:update_spin_button() ws count: 4
DEBUG:workspaces_compact:on_workspace_changed()
DEBUG:workspaces_compact:update_spin_button() ws count: 4
DEBUG:workspaces_compact:on_workspace_changed()
DEBUG:workspaces_compact:update_spin_button() ws count: 4
...

@botrosco
Copy link
Author

Ok so it seems that the issue i am having is not changing workstations but adding them. If i add a workstation with the default applet i am able to change between the number of workstations that are present via that applet. However i am unable to do this with your applet and ther doesnt seem to be any errors in the logs.

https://youtu.be/MlvGE7ujJSc

Here is a video of what I am experiencing

@dgaw
Copy link
Owner

dgaw commented May 30, 2019

Interesting. Perhaps there's an unwanted interaction between the default applet and my applet.

Did you try removing the default applet from your panel before changing the number of workspaces in the compact applet?

@botrosco
Copy link
Author

I have yes and have had no luck.

@dgaw
Copy link
Owner

dgaw commented May 31, 2019

I see. I did a bit more digging and it seems the following bit of code doesn't work as expected on your system:

Line 111 in workspaces_compact.py:

self.wn_screen.change_workspace_count(val)

Unfortunately it works fine here and I don't have an Arch distro handy so that's as far as I can go.

Perhaps someone experiencing the same issue can look into it further.

@Jacob-Vlijm
Copy link

Jacob-Vlijm commented May 31, 2019

You might be missing Wnck as a dependency. @botrosco @dgaw .
python3-gi gir1.2-wnck-3.0 to be precise.

@botrosco
Copy link
Author

Im not at my desktop rn so can't check atm but will give that a look when i can thanks.

@dgaw
Copy link
Owner

dgaw commented May 31, 2019

@Jacob-Vlijm Yes, it's worth checking that, although I think the applet would have crashed if the dependencies hadn't been there.

@botrosco
Copy link
Author

wnck was allready installed, I installed the python bindings for wnck from AUR and still no luck.

@Jacob-Vlijm
Copy link

@dgaw Ah, silly, you are right of course, even the import would break the applet.

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

3 participants