From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Issues with resizing X11/XWayland gtk4 windows on first login after restart
Date: Wed, 17 Apr 2024 07:57:18 +0200 [thread overview]
Message-ID: <20240417055718.29C852380A@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: 1206 bytes --]
Closed issue by Jaymz665 on void-packages repository
https://github.com/void-linux/void-packages/issues/49575
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.22_1 x86_64 GenuineIntel notuptodate rrrmFFFF
### Package(s) Affected
gtk4-4.14.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://gitlab.gnome.org/GNOME/gtk/-/issues/6558
### Expected behaviour
It is expected that on windows open, for example, on the same qt, you can change the size by simply dragging the left mouse button over the edges and corners.
### Actual behaviour
At the moment, on gnome 45.5 and gnome 46.0 (compiled from murge templates), it is noticed that when you first log into the shell, windows opened in qt or wine do not interact correctly. It is impossible to change the window size using the usual mouse action (edge or corner). Windows are open in wine as if they physically have the wrong size (when displayed correctly) and the mouse, when interacting, seems to go beyond the edges of the window.
Corrected by relogin.
### Steps to reproduce
Run gnome-45.5 or higher
Launch an application written in qt
prev parent reply other threads:[~2024-04-17 5:57 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
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 ` oreo639 [this message]
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=20240417055718.29C852380A@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).