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

Blocking action causes Sway/Wayland UI timeout #135

Open
mxmilkiib opened this issue Jun 27, 2019 · 2 comments
Open

Blocking action causes Sway/Wayland UI timeout #135

mxmilkiib opened this issue Jun 27, 2019 · 2 comments

Comments

@mxmilkiib
Copy link

Expected Behavior

That the app should remain running.

Current Behavior

After a time, switching back to the Sway workspace that the app is on causes the app to close.

This is references in these issues;

Possible Solution

Threading.

Steps to Reproduce (for bugs)
  1. Use Sway Wayland compositor
  2. Run pavucontrol-qt
  3. Use another app on another workspace for a time
  4. Switch back to workspace with app
Context

I have to restart the app each time I want to readjust things.

System Information
@yan12125
Copy link
Member

Is there a backtrace for which action is blocking?

I never got crashed pavucontrol on wayfire/weston/kwin. Not sure if it is related to the workspace feature of sway.

@sandsmark
Copy link

can you test https://github.com/sandsmark/pavucontrol-qt/ ? I cleaned up the event loop integration there (removed glib). the glib event loop has had problems causing unresponsiveness before (too many events caused some events to not be delivered, e.g. qterminal/konsole/etc. would choke if running something that printed too much).

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