Minor: Incompatible with Chromebook Linux (Crostini) Wayland

[cjbrooking-kr]

Version: 26.1.1-x86_64.AppImage
OS: Chromeos 149.0.7827.232

To reprouduce just run appimage (see attached)

Running ends with
The Wayland connection broke. Did the Wayland compositor die?

However minor as you can just specify X.11 in the environment

QT_QPA_PLATFORM=xcb /home/chris/applications/novelwriter.AppImage

[vkbo]

I'll have a look at it. ChromeOS isn't officially supported, but maybe I can reproduce it in some other way. Could you copy/paste the wayland errors into the ticket? It's hard to work with a screenshot.

The other messages are also interesting. The Qt font loader is struggling to resolve all the Unicode characters in the selected font too I see.

[cjbrooking-kr]

Here's the output:

chris@penguin:$ cd applications/
chris@penguin:/applications$ ./novelwriter-26.1.1-x86_64.AppImage
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'novelwriter'")
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'novelwriter'")
qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen6" screen model: "unknown" This is most likely a bug in the compositor.
WARNING Font mismatch: Requested 'Sans Serif', but got 'DejaVu Sans'
WARNING Font mismatch: Requested 'Sans Serif', but got 'DejaVu Sans'
WARNING No glyph U+2e42 in font
WARNING No glyph U+300c in font
WARNING No glyph U+300d in font
WARNING No glyph U+300e in font
WARNING No glyph U+300f in font
WARNING No glyph U+2e42 in font
WARNING No glyph U+300c in font
WARNING No glyph U+300d in font
WARNING No glyph U+300e in font
WARNING No glyph U+300f in font
WARNING Font mismatch: Requested 'Sans Serif', but got 'DejaVu Sans'
The Wayland connection broke. Did the Wayland compositor die?
chris@penguin:~/applications$

[vkbo]

I've looked at this some more, and I'm not sure how to solve this one. Do AppImages usually work on ChromeOS, especially with Qt apps?

I'm considering abandoning AppImages in general, because there are so many issues with libraries. There's always some new variation of this type of bugs. The plan is to move to Flatpak instead.

[cjbrooking-kr]

Most work, though its a common enough occurrence for the fix of using the x11 compositor was first in my search results. I've run with WAYLAND_DeBUG=1 and this is the output. I wouldn't spend much time on it, as the QT_QPA_PLATFORM=xcb works, I really reported it so that you are aware if anyone else reports issues running it in the Chromebook linux subsystem.

For info:
ChromeOS use a Google built wayland compositor called Exo, and and a nested compositor called Sommelier to provide compatibility for the Linux subsystem. I suspect that as it is forked and customised code there is some incompatibility with more standard implementations.

[ 864821.275] {Default Queue}  -> wl_surface#27.commit()
[ 864821.384] {Default Queue}  -> xdg_toplevel#24.destroy()
[ 864821.391] {Default Queue}  -> xdg_surface#23.destroy()
[ 864821.399] {Default Queue}  -> wl_surface#20.attach(nil, 0, 0)
[ 864821.415] {Default Queue}  -> wl_surface#20.commit()
[ 864821.441] {Default Queue}  -> wl_surface#20.destroy()
[ 864821.449] {Default Queue}  -> wl_display#1.sync(new id wl_callback#36)
[ 864821.469] {Default Queue}  -> wp_viewport#22.destroy()
[ 864821.473] {Default Queue}  -> wp_fractional_scale_v1#21.destroy()
[ 864821.556] {Default Queue}  -> wl_shm_pool#29.destroy()
[ 864821.568]  -> wl_buffer#30.destroy()
[ 864821.596] {Default Queue}  -> wl_shm_pool#25.destroy()
[ 864821.605]  -> wl_buffer#26.destroy()
[ 864821.644] {Default Queue} wp_fractional_scale_v1#28.preferred_scale(150)
[ 864821.654] {Default Queue}  -> wp_viewport#31.set_destination(1542, 809)
[ 864822.552] {Default Queue}  -> xdg_toplevel#34.set_min_size(600, 480)
[ 864822.568] {Default Queue}  -> xdg_toplevel#34.set_max_size(16777221, 16777248)
The Wayland connection broke. Did the Wayland compositor die?
chris@penguin:~/applications$ 

[vkbo]

Sure, I'll add it to the installation help page then.