Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[wayland] qtile crashes (segfaults) on chrome tab drag n drop

See original GitHub issue

The issue:

When I start dragging a tab qtile immediately crashes. (newest qtile and chrome versions). No log output, direct segfault in qtile (dmesg). I would expect - even if this is a chrome issue - qtile to not crash 😄)

I expected this to be a common wayland bug, since chrome (and electectron) is notoriously annoying there 😛 However after scouring the internet for potential fixes all bug reports I found have been fixed (for e.g. swaywm). Also the qtile issues relating this never describe this particular bug and are solved for the most part (#408 #1257).

How is drag-n-drop with other programs: firefox: works, but only shows drag hints, does not actually drag the tab, same for vscode

Thus: did I miss some magic setting or is this a kown bug? (I get the behavior with the default config as well) The way I start chrome: google-chrome --ozone-platform-hint=auto --enable-features=WebRTCPipeWireCapturer

Chrome: Version 106.0.5249.119 (Official Build) (64-bit) Qtile: 0.22.2.dev9+g946908b9

Required:

I have searched past issues to see if this bug has already been reported.

Issue Analytics

State:
Created a year ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

m-colcommented, Oct 28, 2022

OK got it. Chrome isn’t providing us with an icon for dragging, which I guess it tries to do with another protocol, as it prints this:

[73649:73649:1028/231327.794618:ERROR:wayland_window_drag_controller.cc(145)] zcr_extended_drag_v1 extension not available! Window/Tab dragging won't be fully functional.

We aren’t accounting for this situation but should do. We’re accessing an icon that can be NULL in pywlroots and that’s why we’re segfaulting. See this patch for pywlroots: https://github.com/flacjacket/pywlroots/pull/107

With the next pywlroots release we can use this for this PR which fixes this: https://github.com/qtile/qtile/pull/3935

1reaction

m-colcommented, Oct 28, 2022

Scratch that - I was running chrome directly without the flags, so it was probably using XWayland. Running with those flags causes a crash, which does not happen on sway. Will investigate! 😃

Top Results From Across the Web

Google Chrome/Chromium tab drag 'n drop isn't working #408

Usually one can move a browser tab from one window to another by ... [wayland] qtile crashes (segfaults) on chrome tab drag n...

[wayland/intel graphics] If I move a tab in Chromium (ozone ...

[wayland/intel graphics] If I move a tab in Chromium (ozone), the whole session crashes. (segfault 11) ... It happened with wlroots 14 and...

Segfault in wayland with chrome and mpv - mutter - GitLab

Segfault crash when I exit mpv ... Run chrome (from flatpak) with wayland ozone backend. Run mpv with -vo=gpu --gpu-context=wayland.

896640 - [ozone/wayland] Add tab drag support - Monorail

Wayland, which must be addressed in order to get chrome tab dragging working: ... To tackle this, a Wayland Drag'n'Drop session can be...

Index of Desktop Environments - Gentoo Forums

And segfault. ... Page:1 · "Firefox tab crashes when trying to play video [SOLVED]" Page:1 ... "2020-06-24-xorg-server-dropping-default-suid" Page:1 ...