Cannot set size of window on Ubuntu 22.04 (heigh and width is 0) #1517

skamensky · 2022-07-01T20:34:19Z

Description

When running wails, both in dev and build mode on Ubuntu, the height and width are zero. I ran the same exact code on MacOS and it works.

It's stuck at (seemingly) 0 width and 0 height. If you pass it the Fullscreen argument in app initialization, or call runtime.WindowFullscreen(ctx) from go, you still start off with 0 widht and 0 height, but it becomes resizable via the GUI.

OS Version:

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04 LTS
Release:	22.04
Codename:	jammy

To Reproduce

Initialize project: wails init -n wails_issue_repro -t react-ts
Run wails dev or run wails build and execute build executable

Expected behaviour

Window respects size of initial app config and is programatically resizable.

Screenshots

Attempted Fixes

Search through github and did not find any fixes or same issues

System Details

~/tmp/wails-issue-repro/wails_issue_repro$  wails doctor
Wails CLI v2.0.0-beta.38


Scanning system - Please wait (this may take a long time)...Done.

System
------
OS:		Ubuntu
Version: 	22.04
ID:		ubuntu
Go Version:	go1.18.1
Platform:	linux
Architecture:	amd64

Wails
------
Version: 		v2.0.0-beta.38
Package Manager: 	apt

Dependency	Package Name		Status		Version
----------	------------		------		-------
*docker		docker.io		Installed	20.10.17
gcc		build-essential		Installed	11.2.0
libgtk-3	libgtk-3-dev		Installed	3.24.33-1ubuntu2
libwebkit	libwebkit2gtk-4.0-dev	Installed	2.36.3-0ubuntu0.22.04.1
npm		npm			Installed	8.5.1~ds-1
*nsis		nsis			Installed	v3.08-2
pkg-config	pkg-config		Installed	0.29.2

* - Optional Dependency

Diagnosis
---------
Your system is ready for Wails development!


If Wails is useful to you or your company, please consider sponsoring the project:
https://github.com/sponsors/leaanthony

Additional context

No response

The text was updated successfully, but these errors were encountered:

skamensky · 2022-07-01T20:37:03Z

After posting this I saw maintainers asking whether issues occur when using the vanilla template. I tried again with the vanilla template and I'm still seeing the same issue.

skamensky · 2022-07-01T22:05:56Z

I added a printf to see if maybe the window sizes were getting borked, but it seems okay

printf:

wails/v2/internal/frontend/desktop/linux/window.go

Line 529 in 36ce636

printf("m.width=%i,scale=%i,m.height=%i\n",m.width,scale,m.height);

output in terminal:

m.width=1280,scale=2,m.height=720

Another thing.

When setting the GTK_DEBUG environment with the following value
export GTK_DEBUG=interactive

I see the width-request and height-request as -1 values in the interactive debugger. When fiddling with those to larger values, it does indeed change the size of the window as expected.

When setting the GTK_DEBUG environment with the following value
export GTK_DEBUG=size-request

I see this output in the terminal (trimmed for brevity)

Gtk-Message: 01:04:24.464: [0x1eba780] WebKitWebView	height for width: -1 is minimum 0 and natural: 0 (hit cache: no)

Gtk-Message: 01:04:24.464: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: no)

Gtk-Message: 01:04:24.464: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.464: [0x1eba780] WebKitWebView	width for height: -1 is minimum 0 and natural: 0 (hit cache: no)

Gtk-Message: 01:04:24.464: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: no)

Gtk-Message: 01:04:24.464: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.465: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1eba780] WebKitWebView	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1eba780] WebKitWebView	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.465: [0x1eba780] WebKitWebView	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.466: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.466: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.466: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.466: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.467: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.467: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.467: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.467: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.467: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.467: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1eba780] WebKitWebView	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1eba780] WebKitWebView	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1eba780] WebKitWebView	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	height for width: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	height for width: -1 is minimum 0 and natural: 200 (hit cache: no)

Gtk-Message: 01:04:24.496: [0x1f8a150] GtkBox	width for height: -1 is minimum 0 and natural: 0 (hit cache: yes)

Gtk-Message: 01:04:24.496: [0x1f7e290] GtkWindow	width for height: -1 is minimum 0 and natural: 200 (hit cache: no)

leaanthony · 2022-07-01T22:36:21Z

Hi! Thanks for your persistence with this and having a good crack at working out what's wrong. There is another ticket for this behaviour and we thought it may be a Wayland issue.
#1471
This is the other ticket and mentions a fix: #1420

Let us know if this helps. Would love to get this fixed!

skamensky · 2022-07-01T23:02:14Z

Thanks for the quick response @leaanthony , the fix mentioned in your comment here #1420 (comment) did not work for me (as per the commentor's follow up, I ensured the the environment variabl wasn't set in any other way as well).

However, I did find a different workaround in the meantime.

If you call runtime.WindowSetMaxSize(ctx, 100000, 100000) it allows you to subsuquently call runtime.WindowSetSize(ctx,500,500) (or whatever values you want there). However, it does not let you call other API's, such as runtime.WindowMaximise(ctx) or runtime.WindowFullscreen(ctx)

Strangely, if you set up your App with large MaxHeight and MaxWidth properties, all API's that I've tested work.

err := wails.Run(&options.App{
		Title: "learn-wails",
		MaxHeight:        100000,
		MaxWidth:         100000,
		Width:            500,
		Height:           1500,
		Assets:           assets,
		OnDomReady:       app.OnDomReady,
		BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 1},
		OnStartup:        app.startup,
		Bind: []interface{}{
			app,
		},
	})

leaanthony · 2022-07-02T03:02:17Z

Thanks for testing again. Perhaps this is a genuine resizing bug (it sounds like it). I'll install 22.04 in a VM and try. Do you run it in a VM? I'm wondering if that'll affect whether Wayland runs or not.

skamensky · 2022-07-02T06:09:24Z

No, I'm not running in a VM. It's running on real hardware.

leaanthony · 2022-07-02T08:05:16Z

Right, that might affect my testing but we'll see 👍

leaanthony · 2022-07-04T10:21:01Z

Can confirm 21.10 does not have this issue when run in a VM:

At least in a VM, 22.04 works fine:

Looks like wayland is being used too:

lea@ubuntu:~/GolandProjects/wails_issue_repro$ echo $XDG_SESSION_TYPE
wayland
lea@ubuntu:~/GolandProjects/wails_issue_repro$

Don't know what to suggest at this point.

skamensky · 2022-07-04T10:36:12Z

I never checked the value of XDG_SESSION_TYPE. Maybe it's wonky? I'll check it out when I'm on my personal computer next.

skamensky · 2022-07-04T15:39:06Z

My XDG_SESSION_TYPE is x11, does that change anything?

ianmjones · 2022-07-04T21:06:29Z

I just created a clean Svelte template app with Wails v2.0.0-beta.38, and then added some functions to test using both the JS and Go versions of WindowGetSize() and WindowSetSize(). It's intentionally very simple in its implementation, see attached:

wails-v2-b38.tgz

If you download this test app to test it yourself, please ensure you wails build -clean as the binary was built on NixOS unstable and will very likely not work for you.

This app worked fine on NixOS with i3-wm under X11 (my main machine).

I then used an Ubuntu 22.04 QEMU VM to test the same app under both X11 and Wayland.

I found that it crashed due to a bug (#1443) that has already been fixed (#1464). So I checked out master, installed, and set replace in the app's go.mod as per https://wails.io/docs/guides/bleeding-edge.

I then used wails dev to check all was well, and then wails build -clean to test the binary version, both worked fine.

In the following (silent) screen capture you can see me testing the binary on X11, logging out, switching to a Wayland session, and then testing again:

wails-test-with-wayland-and-x11.mp4

Maybe this app would be a good start for exploring where the problem is on your system @skamensky, and @acheong08 you may also find it useful for testing your issue (#1471).

If the app does not work for you after setting up against master, please provide as much info as possible.

If the app does work for you after setting up against master, are you then able to adjust either the JS or Go code to get the same problems you reported and share your changes so we can determine where the problem is?

leaanthony · 2022-07-04T22:55:09Z

Thanks so much for taking the time to look at this @ianmjones ❤️ 👍 🚀

acheong08 · 2022-07-07T15:52:42Z

I have built the app on both Ubuntu 20.04 (Server) and 22.04 (Desktop). Attempting to run either of the executable results in height and width of 0 on Ubuntu 22.04. The issue is thus most likely with possible changes I have made to my computer rather than the project itself. Will test on a fresh installation when possible.

acheong08 · 2022-07-07T16:24:49Z

Thanks for the quick response @leaanthony , the fix mentioned in your comment here #1420 (comment) did not work for me (as per the commentor's follow up, I ensured the the environment variabl wasn't set in any other way as well).

However, I did find a different workaround in the meantime.

If you call runtime.WindowSetMaxSize(ctx, 100000, 100000) it allows you to subsuquently call runtime.WindowSetSize(ctx,500,500) (or whatever values you want there). However, it does not let you call other API's, such as runtime.WindowMaximise(ctx) or runtime.WindowFullscreen(ctx)

Strangely, if you set up your App with large MaxHeight and MaxWidth properties, all API's that I've tested work.
err := wails.Run(&options.App{
		Title: "learn-wails",
		MaxHeight:        100000,
		MaxWidth:         100000,
		Width:            500,
		Height:           1500,
		Assets:           assets,
		OnDomReady:       app.OnDomReady,
		BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 1},
		OnStartup:        app.startup,
		Bind: []interface{}{
			app,
		},
	})

This seems to be a genuine workaround. It works properly when MaxHeight and MaxWidth are set

leaanthony · 2022-07-07T22:48:40Z

This really does sound like a calculation error but nobody can reproduce 😳 Any chance you could add a bunch of printfs to the code around these calculations and determine what is causing this? Would be great to find an edge case to fix.

acheong08 · 2022-07-08T05:24:16Z

Works on a fresh installation of Ubuntu 22.04. This is likely an issue when upgrading from 21.10 to 22.04.

alekodad · 2022-07-13T08:33:40Z

Thanks for the quick response @leaanthony , the fix mentioned in your comment here #1420 (comment) did not work for me (as per the commentor's follow up, I ensured the the environment variabl wasn't set in any other way as well).
However, I did find a different workaround in the meantime.
If you call runtime.WindowSetMaxSize(ctx, 100000, 100000) it allows you to subsuquently call runtime.WindowSetSize(ctx,500,500) (or whatever values you want there). However, it does not let you call other API's, such as runtime.WindowMaximise(ctx) or runtime.WindowFullscreen(ctx)
Strangely, if you set up your App with large MaxHeight and MaxWidth properties, all API's that I've tested work.
err := wails.Run(&options.App{
		Title: "learn-wails",
		MaxHeight:        100000,
		MaxWidth:         100000,
		Width:            500,
		Height:           1500,
		Assets:           assets,
		OnDomReady:       app.OnDomReady,
		BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 1},
		OnStartup:        app.startup,
		Bind: []interface{}{
			app,
		},
	})
This seems to be a genuine workaround. It works properly when MaxHeight and MaxWidth are set

This method solved my problem,,But I think it's a scaling issue
ubuntu:setting->screen display->scale:100%

leaanthony · 2022-07-13T08:45:42Z

Oooh, that's an interesting angle. Are you saying that when the screen scale (DPI related?) is not 100%, this bug happens?

stffabi · 2022-07-13T08:47:50Z

That might be the issue, seems like scaling is only done in the Fullscreen code path but not when setting min/max. According to the code.

leaanthony · 2022-07-13T09:23:19Z

@alekodad @acheong08 @skamensky - Please try the linked PR. I've added scaling code when setting min/max height and am hoping this is enough. We potentially also need to consider scale when using WindowSetPos and WindowSetSize so if you are able to test those, that would be amazing. Thank you @alekodad for the tip! 🙏

acheong08 · 2022-07-13T14:03:28Z

Wails
------
Version: 		v2.0.0-beta.38
Revision:		ddc157e8cbbe5d9245d8ed64fa53e02945518730
Modified:		false
Package Manager: 	apt

Branch does not fix issue. The fact that the max width and height calculates to zero probably means multiplying the scale won't work. x*0 = 0

ubuntu:setting->screen display->scale:100%

This does indeed work. Can confirm it as a scaling issue.

acheong08 · 2022-07-13T14:21:29Z

Even manually setting all instances of max size to 10000 does not work.

skamensky · 2022-07-14T15:42:29Z

@leaanthony , your new code was giving me compilations errors on ubuntu. I created a PR for the changes that enabled me to compile with no errors or warnings

#1567

In any case, this did not fix the issue. The workaround with the new code still works, however.

leaanthony · 2022-07-15T07:15:17Z

Bah, I didn't have time to test just pushed it out. I'll do some proper debugging on this over the weekend.

leaanthony · 2022-07-16T07:20:36Z

Ok, update: It looks like it's some weird GTK bug when the scale is not 100%. You can see it working kinda fine if you do: GDK_SCALE=1 ./build/bin/your_app
The buttons etc will have weird sizes but you can see the size of the window is fine. I've added logging for every time the position / size is set/changed.
After it was said that setting the max size to some reasonable value made it work i experimented with these values. It occurred to me that perhaps MAX_INT was invalid when scaling is applied, because if GTK takes scaling into account, then this number will essentially overflow valid sizes. So I set it to the current monitor's width/height by default and that seems to have fixed it. Please try the linked PR again and let me know how it goes 👍 #1557

acheong08 · 2022-07-16T07:39:08Z

Issue unresolved

Revision:		764dadc8f44ea47107ca4d91d1df11db6b58bb48

leaanthony · 2022-07-16T08:28:09Z

Did you use replace to use the branch?

skamensky · 2022-07-16T09:49:03Z

Hey @leaanthony , the changes in 764dadc are a partial fix for this!

In app attributes:

app attribute Fullscreen: does not work
app attribute Width: works
app attribute Height: works
call to runtime.WindowFullscreen(ctx): works (yay!)

Debug output: (startup line is from the OnStartup function)

SetMinMaxSize - min: (0,0) max: (1280,720)
SetSize:  1024 768
startup
Center: 128x0

This is what it looks like when I set the app attribute Fullscreen to true

acheong08 · 2022-07-16T10:56:26Z

Did you use replace to use the branch?

I did git clone https://github.com/wailsapp/wails --branch=bugfix/linux_scaling_issues and cd wails/v2/cmd/wails && go install

leaanthony · 2022-07-16T10:57:32Z

Yeah, nice testing! I know we aren't dealing with scaling at all. The fix is just to get the window displayed. Thanks for looking at the different scenarios. Let's see if we can nail this 👍

leaanthony · 2022-07-16T11:00:45Z

Did you use replace to use the branch?

I did git clone https://github.com/wailsapp/wails --branch=bugfix/linux_scaling_issues and cd wails/v2/cmd/wails && go install

Go projects need to update go.mod if you want to use non-module code: https://wails.io/docs/guides/bleeding-edge

acheong08 · 2022-07-16T11:13:54Z

Did you use replace to use the branch?

I did git clone https://github.com/wailsapp/wails --branch=bugfix/linux_scaling_issues and cd wails/v2/cmd/wails && go install

Go projects need to update go.mod if you want to use non-module code: wails.io/docs/guides/bleeding-edge

Thank you. It works now.

leaanthony · 2022-07-17T05:48:13Z

@skamensky - App attribute fullscreen works for me. What's interesting is that there are different sizes for MAX in the console...

alekodad · 2022-07-18T05:48:22Z

Ok, update: It looks like it's some weird GTK bug when the scale is not 100%. You can see it working kinda fine if you do: GDK_SCALE=1 ./build/bin/your_app The buttons etc will have weird sizes but you can see the size of the window is fine. I've added logging for every time the position / size is set/changed. After it was said that setting the max size to some reasonable value made it work i experimented with these values. It occurred to me that perhaps MAX_INT was invalid when scaling is applied, because if GTK takes scaling into account, then this number will essentially overflow valid sizes. So I set it to the current monitor's width/height by default and that seems to have fixed it. Please try the linked PR again and let me know how it goes 👍 #1557

I tested this PR and now it opens in 200% scale without setting MaxHeight and MaxWidth

leaanthony · 2022-07-21T10:57:13Z

@skamensky any updates?

skamensky · 2022-07-22T09:00:31Z

@leaanthony will look at this today. I'll try and play around with my scaling settings to see if there's some machine specific configuration that's changing things around. Also will explore the discrepancy we saw with MAX.

skamensky · 2022-07-22T16:41:01Z

@leaanthony

The SetSize: 1024 768 is coming from the the default options; set here

wails/v2/pkg/options/default.go

Lines 9 to 15 in 449d345

    
           var Default = &App{ 
        
           	Width:              1024, 
        
           	Height:             768, 
        
           	Logger:             logger.NewDefaultLogger(), 
        
           	LogLevel:           logger.INFO, 
        
           	LogLevelProduction: logger.ERROR, 
        
           }

Also, I've tracked down the issue with fullscreen. There seems to be some conflation between the WindowStartState and Fullscreen options.

With the current code from 449d345

Setting WindowStartState: options.Fullscreen in the app config successfully sets the screen to full on startup but setting Fullscreen: true does not work.

err := wails.Run(&options.App{
		Title:            "learn-wails",
		WindowStartState: options.Fullscreen,
		Assets:           assets,
		OnDomReady:       app.OnDomReady,
		BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 1},
		OnStartup:        app.startup,
		Bind: []interface{}{
			app,
		},
	})

However, if we make this change

https://github.com/skamensky/wails/blob/ea6ad2de6dbe6664ee62d649b47d647927e81d74/v2/internal/frontend/desktop/linux/window.go#L818-L820

Then setting Fullscreen does work

err := wails.Run(&options.App{
		Title:      "learn-wails",
		Fullscreen: true,
		Assets:           assets,
		OnDomReady:       app.OnDomReady,
		BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 1},
		OnStartup:        app.startup,
		Bind: []interface{}{
			app,
		},
	})

Where is WindowStartState computed? It seems it's not getting updated properly on startup.
Maybe we should set it in MergeDefaults ?

wails/v2/pkg/options/options.go

Line 75 in 449d345

func MergeDefaults(appoptions *App) {

leaanthony · 2022-07-23T00:58:58Z

Oh good catch. Fullscreen is deprecated. I need to sort that out 👍

leaanthony · 2022-07-23T07:15:54Z

Thanks everyone for the amazing testing and feedback! This is now merged 🙏

leaanthony · 2022-08-03T11:09:06Z

@skamensky would it be possible for you to try this PR and ensuring min/max size work as expected for your scaled environment? 🙏 #1656

skamensky · 2022-08-04T06:28:07Z

I'm on vacation without internet. Will look at this next week!

@leaanthony

skamensky added the Bug Something isn't working label Jul 1, 2022

leaanthony added this to the v2.0.0 milestone Jul 3, 2022

leaanthony self-assigned this Jul 3, 2022

leaanthony added the WIP The issue is currently under development label Jul 3, 2022

leaanthony added this to Wails Backlog Jul 3, 2022

leaanthony moved this to 🆕 TODO in Wails Backlog Jul 3, 2022

leaanthony moved this from 🆕 TODO to 🏗 In progress in Wails Backlog Jul 3, 2022

acheong08 mentioned this issue Jul 7, 2022

Broken display on Linux (v2) #1471

Closed

leaanthony closed this as completed Jul 8, 2022

leaanthony mentioned this issue Jul 13, 2022

Use scaling when setting min/max window #1557

Merged

leaanthony reopened this Jul 13, 2022

leaanthony mentioned this issue Jul 14, 2022

Nothing shown at all on Linux in latest 2.0 beta #1563

Closed

This comment was marked as off-topic.

Sign in to view

leaanthony added this to Known Bugs Jul 21, 2022

leaanthony moved this to In Progress in Known Bugs Jul 21, 2022

leaanthony removed this from Wails Backlog Jul 21, 2022

leaanthony closed this as completed Jul 25, 2022

Repository owner moved this from In Progress to Done in Known Bugs Jul 25, 2022

Cannot set size of window on Ubuntu 22.04 (heigh and width is 0) #1517

Cannot set size of window on Ubuntu 22.04 (heigh and width is 0) #1517

Comments

skamensky commented Jul 1, 2022

Description

To Reproduce

Expected behaviour

Screenshots

Attempted Fixes

System Details

Additional context

skamensky commented Jul 1, 2022

skamensky commented Jul 1, 2022

leaanthony commented Jul 1, 2022

skamensky commented Jul 1, 2022 • edited Loading

leaanthony commented Jul 2, 2022

skamensky commented Jul 2, 2022

leaanthony commented Jul 2, 2022

leaanthony commented Jul 4, 2022

skamensky commented Jul 4, 2022

skamensky commented Jul 4, 2022

ianmjones commented Jul 4, 2022 • edited Loading

leaanthony commented Jul 4, 2022

acheong08 commented Jul 7, 2022 • edited Loading

acheong08 commented Jul 7, 2022 • edited Loading

leaanthony commented Jul 7, 2022 • edited Loading

acheong08 commented Jul 8, 2022

alekodad commented Jul 13, 2022

leaanthony commented Jul 13, 2022

stffabi commented Jul 13, 2022

leaanthony commented Jul 13, 2022

acheong08 commented Jul 13, 2022

acheong08 commented Jul 13, 2022

skamensky commented Jul 14, 2022

leaanthony commented Jul 15, 2022

leaanthony commented Jul 16, 2022

acheong08 commented Jul 16, 2022

This comment was marked as off-topic.

leaanthony commented Jul 16, 2022

skamensky commented Jul 16, 2022 • edited Loading

acheong08 commented Jul 16, 2022

leaanthony commented Jul 16, 2022

leaanthony commented Jul 16, 2022

acheong08 commented Jul 16, 2022

leaanthony commented Jul 17, 2022

alekodad commented Jul 18, 2022

leaanthony commented Jul 21, 2022

skamensky commented Jul 22, 2022

skamensky commented Jul 22, 2022

leaanthony commented Jul 23, 2022

leaanthony commented Jul 23, 2022

leaanthony commented Aug 3, 2022 • edited Loading

skamensky commented Aug 4, 2022

skamensky commented Jul 1, 2022 •

edited

Loading

ianmjones commented Jul 4, 2022 •

edited

Loading

acheong08 commented Jul 7, 2022 •

edited

Loading

acheong08 commented Jul 7, 2022 •

edited

Loading

leaanthony commented Jul 7, 2022 •

edited

Loading

skamensky commented Jul 16, 2022 •

edited

Loading

leaanthony commented Aug 3, 2022 •

edited

Loading