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

Breaks window management after screen is locked. #431

Closed
luisbc92 opened this issue Mar 9, 2024 · 4 comments
Closed

Breaks window management after screen is locked. #431

luisbc92 opened this issue Mar 9, 2024 · 4 comments
Labels
bug Something isn't working GNOME The bug is specific to GNOME

Comments

@luisbc92
Copy link

luisbc92 commented Mar 9, 2024

Describe the Bug

When the extension is enabled and the desktop is locked and unlocked, the desktop becomes unstable. Some windows can be minimized but the image of the window does not actually go away. Some other windows cannot be handled at all. Eventually the whole desktop might become unresponsive.

The bug does not always occur the first time the system is locked and unlocked.

Steps to reproduce the behavior:

  1. Enable extension and one or more of the effects.
  2. Lock the screen.
  3. Unlock the screen.
  4. Try to move, minimize, un-minimize, close windows.

Please let me know what other information I can provide to help debug this issue. Attached is a screen recording.

Note that I do have some other extension enabled at time of recording, however this issue occurs with only Burn My Windows enabled.

System

Please complete the following information:

@luisbc92 luisbc92 added the bug Something isn't working label Mar 9, 2024
@Schneegans Schneegans added the GNOME The bug is specific to GNOME label Mar 9, 2024
@Schneegans
Copy link
Owner

Hi there! Thanks for the report. I am on pretty much the same system. Ubuntu 23.10, GNOME Shell 45.2, and Wayland. I do not experience any of these issues. Have you really tried this with all extensions disabled? Also the Ubuntu-specific build-in extensions?

I am using the vanilla GNOME desktop session, so this could be a difference.

You could run journalctl -f -o cat in a terminal and open a glitchy window and see if any error messages are printed. Also, you could explore the logs since the last boot with journalctl -b -e -o cat. Remember what the last few lines are, lock the screen, unlock the screen, and run the command once again and see if any error was printed in the mean time.

Does this produce anything meaningful?

@ahears
Copy link

ahears commented Mar 10, 2024

@luisbc92: I have the same issue. I found the extension "Dash to Dock" may be the culprit. It does not re-enable correctly after unlocking/un-suspend on Ubuntu 22.04 and the button to turn it on and off works in reverse after crashing. Turning it off seems to correct the problem for me and my system returns to normal and becomes responsive again. Note the desktop crashed and I was working on the CLI to reopen the gnome-extensions-app to address this issue. I have not verified if this issue exists only while using the extensions combined with @Schneegans extensions or if this issues exists regardless. Also note the problem was also intermittent and the desktop didn't crash or become unresponsive every time after unlocking/un-suspend. I put the output below and highlighted an area of interest because this error does not appear after disabling the "Dash to Dock" extensions as you can see. I apologize in advance for my inability to make this output shorter. This post may be better handled by the developer of "Dash to Dock".

LOG OUTPUT AFTER CRASH

USER@MYDESKTOP:~$ journalctl -b -e -o cat

_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1713:60
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1713:60
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1713:60
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1713:60
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_ensureLocations/<@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1713:60
_create/object[name]@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:296:68
_redisplay@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/dash.js:745:39
resetAppIcons@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/dash.js:1038:14
_init/<@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:370:29
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
updateCustomTheme@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/theming.js:233:14
_initialize@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:460:28
_init/<@/home/USER/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/docking.js:398:39

(--) NVIDIA(GPU-0): DFP-0: disconnected
(--) NVIDIA(GPU-0): DFP-0: Internal TMDS
(--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-1: disconnected
(--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-1: 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-2: disconnected
(--) NVIDIA(GPU-0): DFP-2: Internal TMDS
(--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-3: disconnected
(--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-3: 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-4: disconnected
(--) NVIDIA(GPU-0): DFP-4: Internal TMDS
(--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): CSO (DFP-5): connected
(--) NVIDIA(GPU-0): CSO (DFP-5): Internal DisplayPort
(--) NVIDIA(GPU-0): CSO (DFP-5): 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
[session uid=1000 pid=195857] Successfully activated service 'org.gnome.ArchiveManager1'
DING: Detected async api for thumbnails
DING: GNOME nautilus 42.6
JS ERROR: Impossible to enumerate trash children: TypeError: this.location is null
_updateTrash@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:668:40
async*_init@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:597:14
LocationAppInfo@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:95:4
TrashAppInfo@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:564:1
_ensureApp@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:1099:22
getApp@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:1105:14
wrapFileManagerApp@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/locations.js:1049:22
_ensureLocations@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1708:50
DashToDock_DockManager@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1606:14
conditionallyenabledock@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/extension.js:52:23
enable@/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/extension.js:27:5
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:183:32
_onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:532:35
_onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:532:14
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:665:14
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_sync@resource:///org/gnome/shell/ui/sessionMode.js:206:14
popMode@resource:///org/gnome/shell/ui/sessionMode.js:174:14
_continueDeactivate@resource:///org/gnome/shell/ui/screenShield.js:581:30
deactivate/<@resource:///org/gnome/shell/ui/screenShield.js:572:44
finish@resource:///org/gnome/shell/gdm/authPrompt.js:682:13
finish@resource:///org/gnome/shell/ui/unlockDialog.js:863:26
deactivate@resource:///org/gnome/shell/ui/screenShield.js:572:26
ScreenShield/</<@resource:///org/gnome/shell/ui/screenShield.js:118:57
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47
_convertToNativeSignal@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152:19>

LOG OUTPUT WHEN DASH TO DOCK IS DISABLED (with extension disabled):

USER@MYDESKTOP:~$ journalctl -b -e -o cat

#19 55ef86b3a4a0 i resource:///org/gnome/shell/ui/unlockDialog.js:863 (2b57fb0e6b50 @ 59)
#20 55ef86b3a418 i resource:///org/gnome/shell/ui/screenShield.js:572 (2b57fb0bcfb0 @ 50)
#21 55ef86b3a390 i resource:///org/gnome/shell/ui/screenShield.js:118 (2b57fb0bc470 @ 13)
#22 7ffcf1221c20 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (29017b7d3920 @ 433)
#23 55ef86b3a2e8 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (29017b7cd470 @ 39)
== Stack trace for context 0x55ef4cbd6190 ==
#0 7ffcf121e4c0 b /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:147 (357e57a1f970 @ 358)
#1 7ffcf121e630 b /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/utils.js:78 (357e57a1f5b0 @ 501)
#2 7ffcf121ed90 b /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:2049 (357e57a1e1a0 @ 348)
#3 55ef86b3ac50 i /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1917 (357e57a1de20 @ 516)
#4 55ef86b3abb8 i /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:1610 (357e57a1ce70 @ 629)
#5 55ef86b3ab20 i /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/extension.js:52 (357e57a098d0 @ 98)
#6 55ef86b3aa88 i /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/extension.js:27 (357e57a09830 @ 51)
#7 55ef86b3a9c8 i resource:///org/gnome/shell/ui/extensionSystem.js:183 (2e620b4a790 @ 561)
#8 55ef86b3a940 i resource:///org/gnome/shell/ui/extensionSystem.js:532 (2e620b4afb0 @ 15)
#9 7ffcf121fa00 b self-hosted:202 (29017b7e2e70 @ 272)
#10 55ef86b3a8b8 i resource:///org/gnome/shell/ui/extensionSystem.js:532 (2e620b4af10 @ 67)
#11 55ef86b3a830 i resource:///org/gnome/shell/ui/extensionSystem.js:665 (2e620b50510 @ 17)
#12 7ffcf1220630 b self-hosted:1178 (29017b7b0a10 @ 423)
#13 7ffcf1220730 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (29017b7d3920 @ 433)
#14 7ffcf1220eb0 b resource:///org/gnome/shell/ui/sessionMode.js:206 (2b57fb0c89c0 @ 283)
#15 55ef86b3a6d8 i resource:///org/gnome/shell/ui/sessionMode.js:174 (2b57fb0c88d0 @ 142)
#16 55ef86b3a648 i resource:///org/gnome/shell/ui/screenShield.js:581 (2b57fb0bf0b0 @ 79)
#17 55ef86b3a5c0 i resource:///org/gnome/shell/ui/screenShield.js:572 (2b57fb0bf060 @ 17)
#18 55ef86b3a530 i resource:///org/gnome/shell/gdm/authPrompt.js:682 (2b57fb0d1ba0 @ 64)
#19 55ef86b3a4a0 i resource:///org/gnome/shell/ui/unlockDialog.js:863 (2b57fb0e6b50 @ 59)
#20 55ef86b3a418 i resource:///org/gnome/shell/ui/screenShield.js:572 (2b57fb0bcfb0 @ 50)
#21 55ef86b3a390 i resource:///org/gnome/shell/ui/screenShield.js:118 (2b57fb0bc470 @ 13)
#22 7ffcf1221c20 b resource:///org/gnome/gjs/modules/core/_signals.js:114 (29017b7d3920 @ 433)
#23 55ef86b3a2e8 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (29017b7cd470 @ 39)
Initializing nautilus-image-converter extension
Initializing
[1710048932.3045] agent-manager: agent[255a67305d3c450b,:1.1287/org.gnome.Shell.NetworkAgent/1000]: agent registered
[session uid=1000 pid=195857] Successfully activated service 'org.freedesktop.FileManager1'
unable to update icon for software-update-available
unable to update icon for livepatch
unable to update icon for variety
[session uid=1000 pid=195857] Activating service name='org.gnome.ArchiveManager1' requested by ':1.7504' (uid=1000 pid=426865 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined")
(--) NVIDIA(GPU-0): DFP-0: disconnected
(--) NVIDIA(GPU-0): DFP-0: Internal TMDS
(--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-1: disconnected
(--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-1: 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-2: disconnected
(--) NVIDIA(GPU-0): DFP-2: Internal TMDS
(--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-3: disconnected
(--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-3: 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): DFP-4: disconnected
(--) NVIDIA(GPU-0): DFP-4: Internal TMDS
(--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
(--) NVIDIA(GPU-0): CSO (DFP-5): connected
(--) NVIDIA(GPU-0): CSO (DFP-5): Internal DisplayPort
(--) NVIDIA(GPU-0): CSO (DFP-5): 2670.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0):
[session uid=1000 pid=195857] Successfully activated service 'org.gnome.ArchiveManager1'
DING: Detected async api for thumbnails
DING: GNOME nautilus 42.6
Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

@luisbc92
Copy link
Author

I had not tried disabling built-in extensions, so I gave that a try and sure enough the issue went away.

However, now it does not occur at all! Not sure if anything updated through this whole process.

@Schneegans
Copy link
Owner

According to micheleg/dash-to-dock#2169, this could be an issue caused by Ubuntu Dock and Dash-to-Dock being enabled at the same time. I'll close this for now. Please drop a note here if this happens again!

@Schneegans Schneegans closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working GNOME The bug is specific to GNOME
Projects
None yet
Development

No branches or pull requests

3 participants