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

Extension crashes after screen lock #26

Closed
mvolf opened this issue May 11, 2017 · 4 comments
Closed

Extension crashes after screen lock #26

mvolf opened this issue May 11, 2017 · 4 comments
Labels

Comments

@mvolf
Copy link

mvolf commented May 11, 2017

I love this extension but it crashes for me whenever I lock the screen on my laptop. It's impossible to reload it without complete gnome shell restart. If using Wayland gnome shell restart is not available so I need to log out and log in after every screen lock.

@kgshank
Copy link
Owner

kgshank commented May 11, 2017

I have not tested the extension in Wayland yet. I will check. May take a week or more as I am traveling

@kgshank kgshank added the bug label May 11, 2017
@mvolf
Copy link
Author

mvolf commented May 11, 2017

Hi @kgshank I have the same issue in X server and Wayland. I was just stating that it's even worse in Wayland since Gnome shell doesn't support shell restart under Wayland which means that I can't enable crashed extension without logging out.
But the crash happens both under X server and Wayland.

@mvolf
Copy link
Author

mvolf commented May 14, 2017

@kgshank I found this error in logs:
May 14 10:37:13 hostname gnome-shell[1142]: JS WARNING: [/home/user/.local/share/gnome-shell/extensions/sound-output-device-chooser@kgshank.net/convenience.js 219]: reference to undefined property port.profiles May 14 10:37:13 hostname gnome-shell[1142]: Extension "sound-output-device-chooser@kgshank.net" had error: TypeError: port.profiles is undefined

This error happened around the time the screen got unlocked, so I presume that this is the reason why extension crashed. I hope this helps.

@mvolf
Copy link
Author

mvolf commented Jun 9, 2017

@kgshank When can we expect fix of this bug? Or at least some information? It was added a month ago.
Similar thing was reported in this issue: #27

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

No branches or pull requests

2 participants