Open clottes opened 2 months ago
@clottes, thank you for the bug report. I did find a possible cause of the problem: the extension's disable() method was returning before its call to destroy() completed.
I have never encountered the problem. If you are encountering it fairly often, you are welcome to try a new version of All Windows SRWP's extension.js file. As well as the fix, it has debug logging turned on (which isn't that verbose). The file is at https://github.com/jkavery/all-windows/blob/master/extension.js . If you wish, I could send you the extension zip file.
If you don't wish to test the new version, I will go ahead and submit a new version of the extension for review and release.
Error: Extension point conflict: there is already a status indicator for role all-windows-srwp@jkavery.github.io
Believe this may happen after returning from a lock screen, I'd have to do more testing, believe it's active when I first boot no problem. Saw this written somewhere, dont' know if it's related: Looks like GNOME Shell tries to enable the extension for a second time, or that the extension didn't cleanup after itself. GNOME Shell disables extensions in lock screen mode and re-enables them when going back - I assume it is then when it happens.
running: Ubuntu 24.04.1 LTS GNOME Shell 46.0