From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Bug in glib update 2.74.0
Date: Tue, 20 Sep 2022 18:34:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39390@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
New issue by bugcrazy on void-packages repository
https://github.com/void-linux/void-packages/issues/39390
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64 AuthenticAMD notuptodate rrrmDDDDDDDDDDDDDDDDDDDDFFFFFF
### Package(s) Affected
glib-2.74.0_1.x86_64.xbps
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266466
https://github.com/lxqt/lxqt-build-tools/commit/4991811d9212ec1176af6d1cbe88aa37efad4836
### Expected behaviour
The updated package should maintain compatibility with applications that use it, but do not start, after updated.
### Actual behaviour
Due to changes in the source code in the last version, applications do not start, they are broken.
FreeBSD bugzilla and LXQT commit explain a little of the problem.
### Steps to reproduce
Open chromium at the terminal
Returns this error, it is not started, other applications do not return error, simply do not start:
[19642:19642:0920/025933.330207:ERROR:browser_main_loop.cc(267)] GLib: g_log_set_writer_func() called multiple times
next reply other threads:[~2022-09-20 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 16:34 bugcrazy [this message]
2022-09-20 16:59 ` paper42
2022-09-20 17:47 ` bugcrazy
2022-09-20 18:01 ` lxlml
2022-09-20 18:05 ` lxlml
2022-09-20 18:23 ` paper42
2022-09-20 18:34 ` paper42
2022-09-20 18:41 ` lxlml
2022-09-20 18:49 ` paper42
2022-09-20 18:53 ` paper42
2022-09-20 21:46 ` mojamuto
2022-09-20 22:16 ` paper42
2022-09-20 22:16 ` [ISSUE] [CLOSED] " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39390@inbox.vuxu.org \
--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).