From: Jaymz665 <Jaymz665@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gnome-core: update to 46.0.
Date: Thu, 28 Mar 2024 07:47:27 +0100 [thread overview]
Message-ID: <20240328064727.16D6721319@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49428@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
New comment by Jaymz665 on void-packages repository
https://github.com/void-linux/void-packages/pull/49428#issuecomment-2024480652
Comment:
@oreo639 yes, of course, but let's first find out exactly what the problem is, because on @chrysos349 advice, I rolled back to gtk4-4.12.5 and the problem disappeared (although the console stopped working). So I think we need to understand where the error lies. My local 45.4 had no errors, the current 45.5 and (honestly stolen templates) on 46.0 have it. So far, it really looks like gtk4, but since you reproduced the error, does it mean there is something else?
upd: I created issue, I'm not sure how well https://github.com/void-linux/void-packages/issues/49575
next prev parent reply other threads:[~2024-03-28 6:47 UTC|newest]
Thread overview: 122+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 14:45 [PR PATCH] " fanyx
2024-03-21 14:46 ` [PR PATCH] [Updated] " fanyx
2024-03-21 15:18 ` fanyx
2024-03-21 17:17 ` oreo639
2024-03-21 17:19 ` oreo639
2024-03-21 17:25 ` [PR PATCH] [Updated] " fanyx
2024-03-21 17:26 ` fanyx
2024-03-22 11:40 ` [PR PATCH] [Updated] " fanyx
2024-03-22 12:20 ` fanyx
2024-03-22 12:23 ` [PR PATCH] [Updated] " fanyx
2024-03-22 14:31 ` [PR REVIEW] " fanyx
2024-03-22 14:51 ` [PR PATCH] [Updated] " fanyx
2024-03-22 21:20 ` oreo639
2024-03-23 8:18 ` [PR PATCH] [Updated] " fanyx
2024-03-23 8:18 ` fanyx
2024-03-23 8:20 ` [PR PATCH] [Updated] " fanyx
2024-03-23 8:32 ` fanyx
2024-03-23 14:36 ` fanyx
2024-03-23 14:40 ` fanyx
2024-03-23 14:52 ` fanyx
2024-03-23 15:14 ` fanyx
2024-03-23 15:14 ` fanyx
2024-03-23 22:55 ` [PR REVIEW] " oreo639
2024-03-23 22:56 ` oreo639
2024-03-24 11:39 ` [PR PATCH] [Updated] " fanyx
2024-03-24 11:39 ` [PR REVIEW] " fanyx
2024-03-24 11:40 ` [PR PATCH] [Updated] " fanyx
2024-03-26 13:54 ` Jaymz665
2024-03-26 13:55 ` Jaymz665
2024-03-26 14:07 ` Jaymz665
2024-03-26 14:32 ` chrysos349
2024-03-26 14:32 ` chrysos349
2024-03-28 3:42 ` oreo639
2024-03-28 3:42 ` oreo639
2024-03-28 3:43 ` oreo639
2024-03-28 3:53 ` oreo639
2024-03-28 4:26 ` oreo639
2024-03-28 4:34 ` oreo639
2024-03-28 4:39 ` oreo639
2024-03-28 4:39 ` oreo639
2024-03-28 4:39 ` oreo639
2024-03-28 6:18 ` Jaymz665
2024-03-28 6:47 ` Jaymz665 [this message]
2024-04-16 22:41 ` [PR REVIEW] " oreo639
2024-04-17 11:29 ` [PR PATCH] [Updated] " fanyx
2024-04-18 8:52 ` fanyx
2024-04-18 8:53 ` fanyx
2024-04-18 8:57 ` [PR PATCH] [Updated] " fanyx
2024-04-18 8:57 ` fanyx
2024-04-18 9:03 ` fanyx
2024-04-18 9:06 ` oreo639
2024-04-18 9:09 ` oreo639
2024-04-18 9:32 ` fanyx
2024-04-18 9:32 ` [PR PATCH] [Updated] " fanyx
2024-04-18 9:33 ` fanyx
2024-04-18 9:40 ` [PR PATCH] [Updated] " fanyx
2024-04-18 9:49 ` fanyx
2024-04-18 11:53 ` chrysos349
2024-04-18 11:55 ` oreo639
2024-04-18 11:59 ` fanyx
2024-04-18 12:00 ` oreo639
2024-04-18 12:00 ` oreo639
2024-04-18 12:01 ` oreo639
2024-04-18 12:01 ` oreo639
2024-04-18 12:04 ` fanyx
2024-04-18 12:11 ` [PR PATCH] [Updated] " fanyx
2024-04-18 12:16 ` fanyx
2024-04-19 9:07 ` fanyx
2024-04-19 9:12 ` oreo639
2024-04-19 9:14 ` oreo639
2024-04-19 9:16 ` fanyx
2024-04-19 9:18 ` oreo639
2024-04-19 9:20 ` oreo639
2024-04-19 9:20 ` oreo639
2024-04-19 9:25 ` [PR PATCH] [Updated] " fanyx
2024-04-19 9:26 ` oreo639
2024-04-19 9:26 ` oreo639
2024-04-19 9:26 ` oreo639
2024-04-19 9:27 ` [PR REVIEW] " oreo639
2024-04-19 9:39 ` [PR PATCH] [Updated] " fanyx
2024-04-19 9:42 ` fanyx
2024-04-19 9:45 ` fanyx
2024-04-19 9:47 ` oreo639
2024-04-19 9:51 ` fanyx
2024-04-19 9:53 ` oreo639
2024-04-19 9:53 ` oreo639
2024-04-19 9:56 ` [PR PATCH] [Updated] " fanyx
2024-04-19 10:04 ` fanyx
2024-04-19 10:06 ` [PR PATCH] [Updated] " fanyx
2024-04-19 10:07 ` fanyx
2024-04-19 10:11 ` [PR PATCH] [Updated] " fanyx
2024-04-19 15:12 ` chrysos349
2024-04-19 15:14 ` fanyx
2024-04-19 15:21 ` fanyx
2024-04-19 15:36 ` chrysos349
2024-04-19 16:12 ` fanyx
2024-04-20 1:53 ` oreo639
2024-04-20 11:12 ` [PR PATCH] [Updated] " fanyx
2024-04-20 13:28 ` [PR PATCH] [Updated] gnome: " fanyx
2024-04-21 3:14 ` [PR REVIEW] " oreo639
2024-04-21 3:14 ` oreo639
2024-04-21 3:14 ` oreo639
2024-04-21 7:01 ` [PR PATCH] [Updated] " fanyx
2024-04-21 19:46 ` chrysos349
2024-04-21 21:13 ` fanyx
2024-04-21 21:56 ` [PR PATCH] [Updated] " fanyx
2024-04-22 4:46 ` chrysos349
2024-04-22 8:12 ` [PR PATCH] [Updated] " fanyx
2024-04-22 9:36 ` fanyx
2024-04-22 9:37 ` fanyx
2024-04-22 13:35 ` chrysos349
2024-04-22 13:56 ` chrysos349
2024-04-22 14:12 ` [PR PATCH] [Updated] " fanyx
2024-04-26 12:03 ` chrysos349
2024-04-30 11:44 ` [PR PATCH] [Updated] " fanyx
2024-04-30 11:48 ` fanyx
2024-04-30 11:48 ` fanyx
2024-04-30 12:39 ` [PR PATCH] [Updated] " fanyx
2024-05-02 9:54 ` chrysos349
2024-05-03 10:36 ` chrysos349
2024-05-05 10:36 ` [PR PATCH] [Updated] " fanyx
2024-05-12 17:56 ` fanyx
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=20240328064727.16D6721319@inbox.vuxu.org \
--to=jaymz665@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).