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

Crashes under Wayland #88

Open
EvanWashkow opened this issue Dec 1, 2020 · 1 comment
Open

Crashes under Wayland #88

EvanWashkow opened this issue Dec 1, 2020 · 1 comment
Assignees
Labels

Comments

@EvanWashkow
Copy link

Describe the bug
It appears that when starting a Wayland session that the extension crashes, with the error gdkDisplay is null

To Reproduce
Steps to reproduce the behavior:

  1. Start a Wayland session
  2. Observe the problem

Expected behavior
No error

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Distro: Arch
  • Gnome-version: 3.38.2
  • Extension-version 1.6.0 (?)
  • Wayland

Additional context
Add any other context about the problem here.

Error logs

Dec 01 13:05:20 xps-15-9550 gnome-shell[9736]: JS ERROR: Extension [email protected]: TypeError: gdkDisplay is null
                                               _updateCurrentMonitor@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:546:37
                                               enable@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:271:10
                                               _updateWindowGeometry@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:585:22
                                               throttle/func._throttlingId<@/home/evan/.local/share/gnome-shell/extensions/[email protected]/convenience.js:72:10
Dec 01 13:09:37 xps-15-9550 gnome-shell[12713]: JS ERROR: Extension [email protected]: TypeError: gdkDisplay is null
                                                _updateCurrentMonitor@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:546:37
                                                enable@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:271:10
                                                _updateWindowGeometry@/home/evan/.local/share/gnome-shell/extensions/[email protected]/extension.js:585:22
                                                throttle/func._throttlingId<@/home/evan/.local/share/gnome-shell/extensions/[email protected]/convenience.js:72:10
@brknkfr
Copy link

brknkfr commented Apr 1, 2021

I have the same problem. Running on a multi monitor setup with https://extensions.gnome.org/extension/921/multi-monitors-add-on/.

I found a workaround, which is not really comfortable. You can remove the extension under https://github.com/bigbn/drop-down-terminal-x and re-enable it, then it's working again.

Somehow it seems, that gdkDisplay is not correctly initialized on a first login with multi-monitor?

Update: Disabling "Multi-monitor mode" in Drop-Down-Terminal-X helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants