From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bug in glib update 2.74.0 (part II)
Date: Wed, 05 Oct 2022 06:43:23 +0200 [thread overview]
Message-ID: <20221005044323.lwHz4HgAM_MOLeWXPvUSb4WidXerp9glywXJSzdRBxQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39523@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
New comment by bugcrazy on void-packages repository
https://github.com/void-linux/void-packages/issues/39523#issuecomment-1267932816
Comment:
> As I already said, if there are issues, they should be reported and fixed. I don't see any indication this (all gtk applications not starting) is an issue and you keep avoiding my question whether you can reproduce this with a official unmodified gtk+3 package. It would be nice if users could report bugs to us and not you, ~I can reproduce the issue with timeshift~. Could the user who reported it to you or you open an issue about it if they are also not using a heavily modified system?
>
> correction: I can not reproduce a crash with glib 2.74, but I see some failed assertions and there are reports upstream
>
> > If the update problem was just mine, it would be an isolated case, but there are reports in other distros, so it's not an isolated case.
>
> Could you link an issue in another distribution where all gtk applications don't start?
>
> android-tools doesn't even depend on glib, so I am not sure how that would be an issue and I can not reproduce the Thunar issue.
I will only use glib 2.74, when they release a glib version 2.74.1 or higher, which really fixes the problems, as there are no test tools on the glib if it had no bug in the gimp.
Problems in other distros are similar.
Already question of the thunar, would be a problem of stamp data/team, when copies android files to Void. Because user, it didn't open Issue in github, that's a matter of him.
next prev parent reply other threads:[~2022-10-05 4:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 8:14 [ISSUE] " biopsin
2022-09-29 8:56 ` biopsin
2022-09-29 8:56 ` [ISSUE] [CLOSED] " biopsin
2022-09-29 18:18 ` paper42
2022-09-29 18:19 ` paper42
2022-09-29 18:19 ` [ISSUE] [CLOSED] " paper42
2022-09-29 18:24 ` paper42
2022-10-01 22:51 ` bugcrazy
2022-10-01 23:38 ` paper42
2022-10-01 23:40 ` paper42
2022-10-03 1:21 ` bugcrazy
2022-10-03 7:16 ` paper42
2022-10-03 8:27 ` paper42
2022-10-03 9:08 ` q66
2022-10-03 19:55 ` bugcrazy
2022-10-03 20:23 ` paper42
2022-10-03 20:56 ` bugcrazy
2022-10-03 20:58 ` bugcrazy
2022-10-03 21:16 ` bugcrazy
2022-10-03 21:24 ` paper42
2022-10-03 21:28 ` paper42
2022-10-05 4:43 ` bugcrazy [this message]
2022-10-05 8:03 ` paper42
2022-10-05 21:50 ` bugcrazy
2022-10-05 22:42 ` paper42
2022-10-05 22:44 ` paper42
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=20221005044323.lwHz4HgAM_MOLeWXPvUSb4WidXerp9glywXJSzdRBxQ@z \
--to=bugcrazy@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).