From: Oleander via Bug reports for GNU Guix <bug-guix@gnu.org>
To: ludo@gnu.org
Cc: 73249@debbugs.gnu.org
Subject: bug#73249: Recovering journal at boot time after reconfiguring the system with Sway and EXWM
Date: Tue, 29 Oct 2024 11:05:43 +0000 [thread overview]
Message-ID: <HHG9donEMANhdWsFse884uc05oRkz9e2lmz4JZh3ItZ3Qv6r5zLxisWRPV0BJNGhJqsr-FZ1cvGxC5HONeIPXBj74bJmWZBL7iS-7J632a0=@protonmail.com> (raw)
In-Reply-To: <plZJO1_sK1JSkOLFRQfMJsAB4-IhCH4ohG6w017YIg8cVm1Ua_Hyxuj3qf-T7kd-4oTUaQRQDjO3Evhc6dmueKcyuT8vccTyvqWzAYopQr8=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
Hi,
I'm experiencing the same issue with exwm.
Regards,
-------- Original Message --------
On Sep 19, 2024, 15:48, Oleander wrote:
> Hi Ludo,
> yes, it's only after guix system reconfigure.
>
> Thank you!
>
> -------- Original Message --------
> On Sep 19, 2024, 15:13, Ludovic Courtès wrote:
>
>> Hi, Oleander skribis: > I'm running Guix with Sway (v1.9) and ext4. When guix system reconfigure is performed, a filesystem check is triggered on next boot, showing the message: "Recovering journal" and then "clean...". After this, the system boots just fine. > > I reboot/poweroff with loginctl reboot/poweroff (elogind). I think I’ve seen that “Recovering” message recently too, though I’m not sure when that happens (I’m on ext4 but I don’t use Sway). FWIW, the ‘root-unmount’ system test, which ensures root is properly unmounted, currently passes: https://ci.guix.gnu.org/build/5806700/details So maybe it’s only after reconfigure that the file system isn’t properly unmounted? Can you confirm this? Ludo’.
[-- Attachment #2: Type: text/html, Size: 1240 bytes --]
prev parent reply other threads:[~2024-10-29 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 13:15 bug#73249: Recovering journal at boot time after reconfiguring the system with Sway Oleander via Bug reports for GNU Guix
2024-09-19 13:13 ` Ludovic Courtès
2024-09-19 13:48 ` Oleander via Bug reports for GNU Guix
2024-10-29 11:05 ` Oleander 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='HHG9donEMANhdWsFse884uc05oRkz9e2lmz4JZh3ItZ3Qv6r5zLxisWRPV0BJNGhJqsr-FZ1cvGxC5HONeIPXBj74bJmWZBL7iS-7J632a0=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=7059548@protonmail.com \
--cc=73249@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).