From: biopsin <biopsin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Bug in glib update 2.74.0 (part II)
Date: Thu, 29 Sep 2022 10:56:32 +0200 [thread overview]
Message-ID: <20220929085632.Xkx2FySUleHhlnRlchh01boOW3UCLswynk6OtitIeks@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: 915 bytes --]
Closed issue by biopsin on void-packages repository
https://github.com/void-linux/void-packages/issues/39523
Description:
### Is this a new report?
Yes
### System Info
Linux voidx 5.10.145_1 #1 SMP Sat Sep 24 09:55:29 UTC 2022 x86_64 GNU/Linux
### Package(s) Affected
Any GTK3+ (firefox-esr, scite)
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Unknown
### Expected behaviour
no issues
### Actual behaviour
After a reboot upgrading kernel from 5.4 -> 5.10 and also a update to glib-2.74.0 trying to launch any gtk3 applications (firefox-esr, scite) ends up in a Trace/breakpoint trap.
However I have spacefm (gtk2) and it has no issues.
Downgrading to glibc-2.72. resolves my issue, but I will further do a rebuild of GTK3+ as there seems to be more oddities going on after update.
### Steps to reproduce
launch any gtk3 application from terminal
next prev parent reply other threads:[~2022-09-29 8:56 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 [this message]
2022-09-29 8:56 ` 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
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=20220929085632.Xkx2FySUleHhlnRlchh01boOW3UCLswynk6OtitIeks@z \
--to=biopsin@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).