All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219078] New: Filesystem is not responding; file manager crashes; detected buffer overflow; steam won't start
Date: Sun, 21 Jul 2024 19:10:32 +0000	[thread overview]
Message-ID: <bug-219078-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=219078

            Bug ID: 219078
           Summary: Filesystem is not responding; file manager crashes;
                    detected buffer overflow; steam won't start
           Product: File System
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: madeisbaer@arcor.de
        Regression: No

Created attachment 306601
  --> https://bugzilla.kernel.org/attachment.cgi?id=306601&action=edit
Filesystem is not responding; file manager crashes; detected buffer
overflowFilesystem is not responding; file manager crashes; detected buffer
overflow; steam won't start

The problem occurs with kernel 6.10.0-3-cachyos and 6.10.0-arch1-1. The file
manager crashes on launch. Steam no longer starts. With 6.9.9-1-cachyos-echo
everything works fine.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2024-07-21 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 19:10 bugzilla-daemon [this message]
2024-07-21 21:02 ` [Bug 219078] Filesystem is not responding; file manager crashes; detected buffer overflow; steam won't start bugzilla-daemon

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=bug-219078-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.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 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.