Closed andythedude closed 12 months ago
Thanks for taking time to fill in all these informations.
I tried to install burn my windows extension. So far I can't reproduce, but I'm on a very different environment from your's (GNOME 43.2). Unfortunately keeping backward compatibility with GNOME is a chore and I don't have time to support older versions.
From the logs it looks like burn my windows fiddles with the notifications code, but I don't know why. Of course you could "fix" this by renouncing to notifications and commenting out the call to notify that makes the extension crash.
Describe the bug
Seems to be in conflict with burn my windows plugin https://extensions.gnome.org/extension/4679/burn-my-windows/ doesn't consistently reload or show description test until you shut off burn my windows
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the two plugins would work along side each other.
Screenshots
If applicable, add screenshots to help explain your problem.
Operating system with version
GNOME Shell version You can see your GNOME shell version from Settings->Details or
gnome-shell --version
.Installation method
Logs <- VERY IMPORTANT
Please paste below the relevant parts of
journalctl -f -o cat /usr/bin/gnome-shell
. If you don't use systemd, you have to find where the logs are stored and paste them here.Extension's settings
Some errors might be triggered by a spefic set of settings. The command below outputs all of the extension settigs that were changed from the default value.
Otherwise it is:
gsettings --schemadir ~/.local/share/gnome-shell/extensions/nasa_apod@elinvention.ovh/schemas/ list-recursively org.gnome.shell.extensions.nasa-apod
.