From: "���п� via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: "45360" <45360@debbugs.gnu.org>
Subject: bug#45360: Personal Experience
Date: Tue, 10 Dec 2024 10:47:58 +0800 [thread overview]
Message-ID: <tencent_4633EEC8609A563B1942AED8@qq.com> (raw)
In-Reply-To: <87v9cu4cyg.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1045 bytes --]
Hi, folks! I can see that the last comment is back in 2020.
Is there anyone involved in related development that still considers this bug? Today, in 2024, four years later, I can see the bug is not fixed.
Yesterday, I ran guix install gcl sbcl. After a logout, I was unable to login. First, I thought I messed up something by accident so I used timeshift to roll back my machine. After the fix I installed gcl and sbcl again, then when I started my machine, the same problem occured! It took my more than 5 reboots to found out that it is the sbcl installed via guix that broke gnome somehow. After guix remove sbcl, the problem is gone!
does anyone have some idea about a fix or walkaround? This is absolutely a bug, and since gnome is popular fossware, I would regard it as an urgent bug that forces people not to use sbcl via guix.
If the bug is not easily fixable in the near future, a note in the package description is needed, warning people not to use the package if they are using gnome.
--Jack
[-- Attachment #2: Type: text/html, Size: 1236 bytes --]
prev parent reply other threads:[~2024-12-11 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 5:38 bug#45360: Cannot log in to GNOME on foreign distro with Guix Evan Straw
2020-12-22 11:42 ` Carlo Zancanaro
2020-12-22 12:34 ` Ricardo Wurmus
2020-12-22 13:40 ` Nicolas Goaziou
2020-12-30 2:29 ` Evan Straw
2024-12-10 2:47 ` ���п� via Bug reports for GNU Guix [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=tencent_4633EEC8609A563B1942AED8@qq.com \
--to=bug-guix@gnu.org \
--cc=2024110144@mails.szu.edu.cn \
--cc=45360@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.