microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
9.91k stars 296 forks source link

Gnumeric crash due to the Wayland protocol error #646

Open parrenin opened 2 years ago

parrenin commented 2 years ago

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Your Distribution version: [On Debian or Ubuntu run `lsb_release -r` in WSL]
Your WSLg version: [Open 'Apps and Features' and check the version of 'Windows Subsystem for Linux GUI app support', e.g: 0.2.3.13]

Microsoft Windows [version 10.0.22000.434] debian release 11 Version WSL : 0.51.2.0 Version du noyau : 5.10.81.1 Version WSLg : 1.0.30 Version de Windows : 10.0.22000.434

Steps to reproduce

WSL logs:

You can access the wslg logs using explorer at: \\wsl$\<Distro-Name>\mnt\wslg (e.g.: \\wsl$\Ubuntu-20.04\mnt\wslg)

Expected behavior

Steps to reproduce:

Actual behavior

Gnumeric should not crash

Livre1.xlsx

hideyukn88 commented 2 years ago

@parrenin, thanks for reporting the issue, I comfirmed the crash and it is hitting below error.

ev wl_display@1.error(xdg_wm_base@18, 4, "xdg_surface buffer (1128 x 998) does not match the configured maximized state (1128 x 716)")

At my environment, output is configured as below.

interface: 'zxdg_output_manager_v1', version: 2, name: 4
        xdg_output_v1
                output: 20
                name: 'rdp-0'
                logical_x: 0, logical_y: 0
                logical_width: 1128, logical_height: 752

And because Windows's taskbar, workarea is reduced to 716 height.

Translated workarea:(0,0)-(1128,716) at rdp-0:(0,0)-(1128,752)

Thus, I'm not sure yet where the buffer height of 998 came from, I will continue to look into. Thanks!

hideyukn88 commented 2 years ago

Running under X11 mode, window gets maximized after opening second instance of the file, without crash.

GDK_BACKEND=x11 gnumeric

MTRNord commented 1 year ago

Running under X11 mode, window gets maximized after opening second instance of the file, without crash.

GDK_BACKEND=x11 gnumeric

This workaround doesnt seem to work for me with the re.sonny.Workbench flatpak as it results in this error:

❯ GDK_BACKEND=x11 flatpak run re.sonny.Workbench

Note that the directories 

'/var/lib/flatpak/exports/share'
'/home/marcel/.local/share/flatpak/exports/share'

are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the
session is restarted.

(re.sonny.Workbench:4): Gtk-WARNING **: 12:31:37.300: cannot open display: 
MTRNord commented 1 year ago

Actually it seems to work if I start the flatpak as the root user. Meaning you first do sudo -i and then GDK_BACKEND=x11 flatpak run re.sonny.Workbench

ahmedyarub commented 1 year ago

This worked for me running qemu thank you!

addiment commented 1 year ago

I'm getting this with Nautilus after having updated to Debian bookworm. Didn't have this issue before, so messing with my system must have shuffled something about. Log:

wl_display@1.error(xdg_wm_base@16, 4, "xdg_surface buffer (887 x 685) does not match the configured maximized state (0 x 0)")

Edit: using X11 as the GDK backend seems to work for me

jonaskuske commented 3 months ago

I'm getting this with Nautilus after having updated to Debian bookworm. Didn't have this issue before, so messing with my system must have shuffled something about. Log:

wl_display@1.error(xdg_wm_base@16, 4, "xdg_surface buffer (887 x 685) does not match the configured maximized state (0 x 0)")

Seeing the same issue on Ubuntu 23.xx :(