From: "Marek Paśnikowski via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 59512@debbugs.gnu.org
Subject: bug#59512: gtk-4.8.1 grafting fails
Date: Tue, 29 Nov 2022 12:37:32 +0000 [thread overview]
Message-ID: <Ngn8BKvdynJDYa7Z-0DctvKDipo-gzm5v7wTW10EprMID0danyQkxbYCX0sdO9k6fsp4o5kBDvu9EeD-o_abzMoHQCYxABjf4l9ILWuovQ8=@protonmail.com> (raw)
In-Reply-To: <87lenuak9t.fsf@gnu.org>
------- Original Message -------
On poniedziałek, 28 listopada 2022 21:36, Ludovic Courtès <ludo@gnu.org> wrote:
>
>
> Hi,
>
> Marek Paśnikowski marekpasnikowski@protonmail.com skribis:
>
> > grafting '/gnu/store/vp4ybqhxdrf4b2fk37c0s72g6iafqsmz-gtk-4.8.1-doc' -> '/gnu/store/7hfq1hbhfsmzjil433cjd8mngvxd05xv-gtk-4.8.1-doc'...
> > ERROR: In procedure fport_fill_input: Input/output error
>
>
> This indicates an error while writing to your storage device, which
> could be due to a failing device.
>
> Does /var/log/messages contains hints of input/output errors?
Yes, there is one node with a wrong checksum. On the internet I found [[https://forums.unraid.net/topic/92704-solved-btrfs-csum-error/][a matching topic on Unraid Forum]].
I checked RAM with Memtest (it passed) and then identified the
broken file. So far, I think I got "lucky" and had a "cosmic ray"
kind of event - I do remember a single failure of resume-from-suspend some time ago.
I should be able to heal the system by deleting the bit-flipped
file and reinstalling gtk. Does Guix have the ability to remove or
rewrite a specific file in its store? The file is rooted in the
system configuration - not in a profile.
Thank you for your help. I would also like to suggest a tweak to
the error message - to make the file system failure more obvious.
next prev parent reply other threads:[~2022-11-29 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 9:55 bug#59512: gtk-4.8.1 grafting fails Marek Paśnikowski via Bug reports for GNU Guix
2022-11-28 20:36 ` Ludovic Courtès
2022-11-29 12:37 ` Marek Paśnikowski via Bug reports for GNU Guix [this message]
[not found] ` <ynDv8mSs5lee6fcgZBylSKmMdeONoE5wxBFq-SIlPtrogPPoG3C3PB3r_nTqQFOoiYN9kUdABTNFqTZxounpc91IWlkvlZh7OCRSeiTOdw0=@protonmail.com>
2022-12-02 13:15 ` Ludovic Courtès
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='Ngn8BKvdynJDYa7Z-0DctvKDipo-gzm5v7wTW10EprMID0danyQkxbYCX0sdO9k6fsp4o5kBDvu9EeD-o_abzMoHQCYxABjf4l9ILWuovQ8=@protonmail.com' \
--to=bug-guix@gnu.org \
--cc=59512@debbugs.gnu.org \
--cc=marekpasnikowski@protonmail.com \
/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).