Hi everyone, Thanks for the positive feedback.
Replying to some of the topics raised: On Mon, Feb 16, 2026 Benson Muite wrote: > [...] > The panic screen should give an indication of where the QR code will direct > you since server logs of what ip addresses are visiting the site are not great > ways to give end users choices in what information they want to keep private. I don't think it can be configured at the moment, the DRM Panic message is hardcoded in the kernel. About privacy concerns: The frontend doesn't store any information, cookies or any other information. The encoded trace is not sent to the server. It is part of the URL hash and that information is never sent to the server, it is only processed by your browser: https://stackoverflow.com/a/3664324 Only when/if the user decides to create a bug, the trace is shared. Therefore, the only information that the server receives is a request for the HTML/CSS/JS resources. I don't think that would be a problem to most users. Every time you navigate to any web page that's the very minimum information you share. Also, Fedora users share similar information when using dnf to update their packages, so I don't think this should be a problem. > Is it possible to log the information somewhere on disk and ask on reboot > if one would like to create a bugzilla report? Not everyone may have a > smartphone available. Ubuntu has some default crash dump settings: > > https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/index.html > > Based on > https://fedoraproject.org/wiki/Changes/coredumpctl > https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes > probably something similar can be done in Fedora. I guess something like that is possible, but it is out of the scope of this tool. Maybe something to look into as a follow up? On Mon, Feb 16, 2026 at 6:40 PM Kevin Fenzi <[email protected]> wrote: > On Mon, Feb 16, 2026 at 11:09:13AM +0100, José Expósito wrote: >> [...] > > - Configuring it to report issues to Bugzilla, the configuration is simple > > [2] > > So these would be kernel bugs reported by an anonymous user? At the moment, yes. It'd be reported by a user/token created to be used by the DRM Panic Frontend. > I don't think thats very ideal. Could result in a easy DDOS of bugzilla, > and unless folks were careful to follow and cc themselves it would be > hard to get additional information. > > Could it instead ask the user to go login to bugzilla and then populate > a new bug with the info thats using the users existing auth? That was my initial approach, showing a dialog with a link to a URL with some fields filled: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=kernel&version=<VERSION> And information about how to copy and paste the trace. As pros, this approach makes it easier for the user to share additional feedback in Bugzilla. The cons are that the user would need to create an account and can forget to include important information to the bug report, like the trace. It is not implemented at the moment, but the create-bug API: https://bugzilla.redhat.com/docs/en/html/api/core/v1/bug.html#create-bug Accepts a CC field. The frontend could ask the user for their email. None of the solutions is perfect, let's see what other people think. Jose -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
