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: Tue, 16 Apr 2024 01:13:54 +0200 [thread overview]
Message-ID: <20240415231354.486E3246DE@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: 995 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49575#issuecomment-2024576714
Comment:
> Gnome 45.5 is a problem with windows not based on gtk
It is the exact opposite, it specifically affects gtk4 windows.
(SSDs and auto-started applications)
> Launch an application written in qt
This happens for qt applications using SSDs which uses gtk4 in gnome 44+.
This issue only applies to X11, and not Wayland (although it does affect XWayland, which if you are seeing SSDs, the application is using XWaland).
This is the upstream issue: https://gitlab.gnome.org/GNOME/gtk/-/issues/6558
~~It might have to do with some dbus activation not having finished yet.~~ It has to do with a timer being initialized to zero being compared to a monotonic (microseconds from startup) resulting in the comparison failing until 15 seconds after start up.
EDIT: Another upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/3417
next prev parent reply other threads:[~2024-04-15 23:13 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
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 [this message]
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=20240415231354.486E3246DE@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).