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
Gnome crashing on Ubuntu 20.04LTS #70
Comments
Hi Dave, thanks for going to the effort to report this bug, much appreciated. Bugs that crash GNOME can be a real pain, but will take a look. |
Hi Dave, are you able to walk me through this. Looking at the output I can't see what in particular is causing the bug. The extension should only really be active 1 minute after startup, and around midnight in your region.
(The above command switches on debug logging within the extension, so it dumps a whole lot of information on to the system journal.) Then after a reboot or shell restart, you can create a text dump all the debug messages with this command:
You can attach that debug log here or email it to me at ineffable@gmail.com and I'll take a look. |
bingdebuglog.txt |
Thanks, much appreciated. Debug logging is only for the extension itself, so if you've uninstalled it you don't need to worry about it. If you reinstall, it'll still have debug mode on, but you can disable it with this command:
|
Greeting 😄 I'm also experimenting this issue today: gnome-shell crash after one minute if I'm logging in before 9AM (Switzerland time). |
This is an old bug, but probably linked to an issue with Wayland and some of the things the extension was doing that was not entirely "officially sanctioned". #82 could be related, this has some what been mitigated when Wayland is detected on newer versions of the extension. |
Installing bing wallpaper extension on 20.04 causes crash although system still usable and wallpaper does change
Ubuntu bug reported https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876681
Uninstall the extension and there are then no problems.
Nice to have it fixed.
The text was updated successfully, but these errors were encountered: