Skip to content

[BUG] Gnome startup stucks with Super Key extension enabled #320

Description

@lurepheonix

Describe the bug
When launching system with vertical-workspaces and Super Key extensions enabled, GNOME shows black screen with cursor instead of loading properly.

To Reproduce
Steps to reproduce the behavior:

  1. Install Super key (either from GitHub or extensions.gnome.org).
  2. Enable it with V-Shell.
  3. Load GNOME.

(NOTE: system will be unusable after such a launch, can't even switch to another TTY. I was logging out over SSH from other machine using loginctl while debugging the issue.)

Expected behavior
Gnome loads normally.

Source of the bug
Was introduced in d1af61c, line 103:

// Skip default startup animation
St.Settings.get().slow_down_factor = 0;

Reverting this line fixes the break, tested on release 50.4 (latest release at this time).
This change seems to introduce some subtle incompatibility that affects startup. Actually, I'm worried more about this than the break of the Super Key extension, so I'm submitting a bug report instead of PR.

Screenshots
Can't make a screenshot in that state, so here is a very-poor-quality photo of a screen:
Image

System:

  • OS: CachyOS (ID_LIKE=arch, BUILD_ID=rolling)
  • Version of V-Shell extension: 50.4
  • Source of installation: extensions.gnome.org, GitHub

Extensions

~ gnome-extensions list --enabled
super-key@tommimon.github.com
appindicatorsupport@rgcjonas.gmail.com
Vitals@CoreCoding.com
dash-to-dock@micxgx.gmail.com
copyous@boerdereinar.dev
vertical-workspaces@G-dH.github.com
drive-menu@gnome-shell-extensions.gcampax.github.com
native-window-placement@gnome-shell-extensions.gcampax.github.com
places-menu@gnome-shell-extensions.gcampax.github.com
status-icons@gnome-shell-extensions.gcampax.github.com
user-theme@gnome-shell-extensions.gcampax.github.com
windowsNavigator@gnome-shell-extensions.gcampax.github.com
pop-shell@system76.com
vertical-workspaces@G-dH.github.com
  Name: V-Shell
  Description: Customize your GNOME Shell UX to suit your workflow, whether you like horizontally or vertically stacked workspaces.
  Path: /home/kotiara/.local/share/gnome-shell/extensions/vertical-workspaces@G-dH.github.com
  URL: https://github.com/G-dH/vertical-workspaces
  Version: 50.4
  Enabled: Yes
  State: ACTIVE

super-key@tommimon.github.com
  Name: Super Key
  Description: Fork of Pop Launcher Super-Key: Bind the Super-Key to a custom action
  Path: /home/kotiara/.local/share/gnome-shell/extensions/super-key@tommimon.github.com
  URL: https://github.com/tommimon
  Version: 10
  Enabled: Yes
  State: ACTIVE

System log output
Can't see anything here that is related to the issue.

Running GNOME Shell (using mutter 50.3) as a Wayland display server
MESA: warning: Support for this platform is experimental with Xe KMD, bug reports may be ignored.
Thread 'KMS thread' will be using high priority scheduling
Device '/dev/dri/card0' prefers shadow buffer
Added device '/dev/dri/card0' (xe) using atomic mode setting.
Created gbm renderer for '/dev/dri/card0'
GPU /dev/dri/card0 selected primary from builtin panel presence
Obtained a high priority EGL context
Using public X11 display :0, (using unix:/tmp/.X11-unix/X1 for managed services)
Using Wayland display name 'wayland-0'
Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Registering session with GDM
Will monitor session 54
Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Gio.DesktopAppInfo has been moved to a separate platform-specific library. Please update your code to use GioUnix.DesktopAppInfo instead.
0 get() ["resource:///org/gnome/gjs/modules/core/_common.js":190:42]
1 <TOP LEVEL> ["file:///home/kotiara/.local/share/gnome-shell/extensions/dash-to-dock@micxgx.gmail.com/locations.js":113:4]
2 anonymous() ["resource:///org/gnome/shell/ui/init.js":20:20]

[Copyous] Using Gda 6.0 database
soup_message_new_from_uri: assertion 'soup_uri_is_valid (uri)' failed
[Copyous] Failed to get link image
loading default theme (Adwaita)
Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ConflictConflict with other extensionfixedFix already available in the repository

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions