From: "Ben Kohler" <bkohler@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: releases/specs/amd64/livegui/
Date: Thu, 15 Feb 2024 20:40:06 +0000 (UTC) [thread overview]
Message-ID: <1708029600.601cd9fd8c7a2865444e74c859ccd05ccf16a521.bkohler@gentoo> (raw)
commit: 601cd9fd8c7a2865444e74c859ccd05ccf16a521
Author: Ben Kohler <bkohler <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 15 20:34:32 2024 +0000
Commit: Ben Kohler <bkohler <AT> gentoo <DOT> org>
CommitDate: Thu Feb 15 20:40:00 2024 +0000
URL: https://gitweb.gentoo.org/proj/releng.git/commit/?id=601cd9fd
amd64/livegui/livegui-stage2.spec: add secureconsole to bootargs
There seems to be a race condition occurring when livecd-tools
"fixinittab" script enables autologin on tty1-6 by default. This is
racing with sddm's autostart & autologin on tty2, causing hiccups in the
elogind session and preventing user shutdown, networking, etc.
Adding secureconsole will limit fixinittab to only autologin on tty1,
avoiding this race.
Bug: https://bugs.gentoo.org/915217
Signed-off-by: Ben Kohler <bkohler <AT> gentoo.org>
releases/specs/amd64/livegui/livegui-stage2.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/releases/specs/amd64/livegui/livegui-stage2.spec b/releases/specs/amd64/livegui/livegui-stage2.spec
index 5a887bb6..9792e01c 100644
--- a/releases/specs/amd64/livegui/livegui-stage2.spec
+++ b/releases/specs/amd64/livegui/livegui-stage2.spec
@@ -7,7 +7,7 @@ snapshot: @TIMESTAMP@
source_subpath: default/livecd-stage1-amd64-plasma-@TIMESTAMP@
portage_confdir: @REPO_DIR@/releases/portage/livegui
-livecd/bootargs: overlayfs nodhcp
+livecd/bootargs: overlayfs nodhcp secureconsole
livecd/depclean: no
livecd/fstype: squashfs
livecd/iso: livegui-amd64-@TIMESTAMP@.iso
next reply other threads:[~2024-02-15 20:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 20:40 Ben Kohler [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-02 15:24 [gentoo-commits] proj/releng:master commit in: releases/specs/amd64/livegui/ Andreas K. Hüttel
2024-07-03 15:28 Ben Kohler
2024-06-26 12:57 Ben Kohler
2024-05-13 15:40 Ben Kohler
2024-05-13 15:40 Ben Kohler
2024-03-31 11:21 Andreas K. Hüttel
2024-02-27 19:18 Ben Kohler
2023-11-06 17:46 Ben Kohler
2023-07-23 17:39 Ben Kohler
2023-05-15 12:01 Ben Kohler
2023-03-21 17:31 Andreas K. Hüttel
2023-02-17 19:08 Andreas K. Hüttel
2023-02-17 18:18 Andreas K. Hüttel
2022-12-22 18:18 Andreas K. Hüttel
2022-10-31 16:26 Andreas K. Hüttel
2022-10-11 19:45 Matt Turner
2022-09-18 19:48 Ben Kohler
2022-08-27 4:49 Andreas K. Hüttel
2022-07-17 20:17 Ben Kohler
2022-04-14 17:53 Andreas K. Hüttel
2022-04-10 11:46 Andreas K. Hüttel
2022-04-10 11:46 Andreas K. Hüttel
2022-04-10 11:41 Andreas K. Hüttel
2022-04-03 19:32 Andreas K. Hüttel
2022-04-02 19:22 Andreas K. Hüttel
2022-03-14 21:23 Andreas K. Hüttel
2022-03-14 15:04 Andreas K. Hüttel
2022-03-09 0:20 Andreas K. Hüttel
2022-03-06 15:36 Andreas K. Hüttel
2022-03-01 15:53 Ben Kohler
2022-02-20 19:47 Andreas K. Hüttel
2022-02-16 20:46 Ben Kohler
2022-02-16 16:10 Ben Kohler
2022-02-15 12:25 Ben Kohler
2022-02-15 12:25 Ben Kohler
2022-02-11 16:31 Ben Kohler
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=1708029600.601cd9fd8c7a2865444e74c859ccd05ccf16a521.bkohler@gentoo \
--to=bkohler@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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