From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Issues with resizing X11/XWayland gtk4 windows on first login after restart
Date: Thu, 28 Mar 2024 09:42:21 +0100 [thread overview]
Message-ID: <20240328084221.D38DD215B8@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49575@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49575#issuecomment-2024656370
Comment:
> Not in my case. gtk4 windows are not affected at all.
>
> It looks like the bug affects apps run under XWayland (run xlsclients to determine which apps run under XWayland).
Hence why I specified X11/XWayland gtk4 windows (and applications using GNOME's SSDs which use gtk4). It doesn't affect Wayland gtk4 windows.
> When maximized, the apps can't be closed with the mouse, but clicking on the close button instead switches to the window in the background.
Thanks for pointing this out, I've run in to that issue for a while with auto-started applications using SSDs. Recently, I noticed that simply closing the window and reopening it doesn't work around it anymore, which is consistent with the behavior I noticed regarding the resizing issue.
> the gtk3 app
What application is this?
next prev parent reply other threads:[~2024-03-28 8:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 6:33 [ISSUE] Gnome 45.5 is a problem with windows not based on gtk Jaymz665
2024-03-28 7:30 ` oreo639
2024-03-28 7:32 ` oreo639
2024-03-28 7:37 ` oreo639
2024-03-28 7:46 ` Issues with resizing X11/XWayland gtk4 windows on first login after restart oreo639
2024-03-28 7:48 ` Jaymz665
2024-03-28 8:07 ` chrysos349
2024-03-28 8:21 ` oreo639
2024-03-28 8:26 ` oreo639
2024-03-28 8:26 ` oreo639
2024-03-28 8:27 ` oreo639
2024-03-28 8:29 ` oreo639
2024-03-28 8:34 ` oreo639
2024-03-28 8:42 ` oreo639 [this message]
2024-03-28 8:43 ` chrysos349
2024-03-28 8:46 ` chrysos349
2024-03-28 8:47 ` chrysos349
2024-03-28 8:57 ` oreo639
2024-03-28 9:11 ` chrysos349
2024-03-28 9:35 ` oreo639
2024-03-28 9:35 ` oreo639
2024-03-28 9:36 ` oreo639
2024-03-28 9:39 ` oreo639
2024-03-28 9:39 ` oreo639
2024-03-28 9:47 ` oreo639
2024-03-28 9:48 ` oreo639
2024-03-28 9:53 ` oreo639
2024-03-28 9:54 ` oreo639
2024-03-28 9:58 ` chrysos349
2024-03-28 10:05 ` oreo639
2024-03-28 10:05 ` oreo639
2024-03-28 10:06 ` oreo639
2024-03-28 10:16 ` oreo639
2024-04-04 7:21 ` chrysos349
2024-04-07 17:12 ` mblouka
2024-04-07 22:49 ` oreo639
2024-04-07 22:56 ` oreo639
2024-04-07 22:59 ` oreo639
2024-04-07 22:59 ` oreo639
2024-04-15 23:12 ` oreo639
2024-04-15 23:13 ` oreo639
2024-04-16 7:54 ` oreo639
2024-04-16 7:57 ` oreo639
2024-04-16 7:57 ` oreo639
2024-04-16 8:47 ` oreo639
2024-04-16 10:18 ` oreo639
2024-04-16 18:33 ` oreo639
2024-04-16 20:48 ` oreo639
2024-04-17 5:21 ` chrysos349
2024-04-17 5:55 ` Jaymz665
2024-04-17 5:57 ` [ISSUE] [CLOSED] " oreo639
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240328084221.D38DD215B8@inbox.vuxu.org \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).