From: loukamb <loukamb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: screen frozen linux6.6 and 6.7
Date: Sun, 06 Oct 2024 01:33:17 +0200 [thread overview]
Message-ID: <20241005233317.AFC932669F@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48473@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
New comment by loukamb on void-packages repository
https://github.com/void-linux/void-packages/issues/48473#issuecomment-2395225941
Comment:
Bump, this is still a problem on Void with all latest base packages installed, with the current live image for installation still remaining broken and preventing users from installing Void Linux on some systems with Nvidia hardware. I decided to use Arch Linux until this issue is resolved.
next prev parent reply other threads:[~2024-10-05 23:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:57 [ISSUE] " levdopa
2024-02-01 15:47 ` abenson
2024-02-01 20:19 ` levdopa
2024-02-01 20:27 ` classabbyamp
2024-02-01 22:09 ` levdopa
2024-02-06 1:57 ` nau5ea
2024-02-06 17:24 ` mblouka
2024-02-06 17:25 ` mblouka
2024-02-06 17:26 ` mblouka
2024-02-09 18:10 ` Sapein
2024-03-09 12:17 ` Brixy
2024-03-23 17:20 ` thomasxg
2024-03-23 19:24 ` mblouka
2024-03-23 19:24 ` mblouka
2024-04-16 20:14 ` nezos
2024-08-21 1:56 ` loukamb
2024-08-22 23:46 ` classabbyamp
2024-08-22 23:49 ` classabbyamp
2024-08-22 23:50 ` classabbyamp
2024-10-05 23:31 ` loukamb
2024-10-05 23:32 ` loukamb
2024-10-05 23:33 ` loukamb [this message]
2024-10-05 23:36 ` classabbyamp
2024-10-06 2:43 ` loukamb
2024-10-06 12:23 ` loukamb
2024-10-06 12:24 ` loukamb
2024-10-06 12:25 ` loukamb
2024-10-06 12:25 ` loukamb
2024-10-07 3:19 ` classabbyamp
2024-10-07 13:56 ` loukamb
2024-10-07 13:56 ` loukamb
2024-10-07 13:57 ` loukamb
2024-10-07 13:57 ` loukamb
2024-10-15 2:54 ` [ISSUE] [CLOSED] " classabbyamp
2024-10-15 3:13 ` loukamb
2024-10-15 3:18 ` loukamb
2024-10-15 3:18 ` classabbyamp
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=20241005233317.AFC932669F@inbox.vuxu.org \
--to=loukamb@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).