Fedora plans to set up QR bases #kernel panics together with a web-service "that provides users with an accessible, user-friendly interface for understanding kernel panic information and facilitating bug reports through Bugzilla integration."
-
Fedora plans to set up QR bases #kernel panics together with a web-service "that provides users with an accessible, user-friendly interface for understanding kernel panic information and facilitating bug reports through Bugzilla integration." This is driven by @jose_exposito.
For details see: https://fedoraproject.org/wiki/Changes/DrmPanicFrontend To quote on small section:
"""The DRM Panic Frontend is a web application that bridges the gap between technical kernel panic data and user-friendly presentation. When users scan a QR code from a DRM Panic screen with their mobile device, they are directed to a Fedora-hosted web interface that:
1. Provides contextual information - Explains what happened in accessible language
2. Decodes and displays panic information - Presents kernel version, architecture, and error traces in a structured, readable format
3. Facilitates bug reporting - Offers streamlined integration with Fedora Bugzilla, pre-filling bug reports with relevant system information and error traces
4. Improves user experience - Uses PatternFly design patterns to provide interface consistent with #Fedora's design language"""
-
Fedora plans to set up QR bases #kernel panics together with a web-service "that provides users with an accessible, user-friendly interface for understanding kernel panic information and facilitating bug reports through Bugzilla integration." This is driven by @jose_exposito.
For details see: https://fedoraproject.org/wiki/Changes/DrmPanicFrontend To quote on small section:
"""The DRM Panic Frontend is a web application that bridges the gap between technical kernel panic data and user-friendly presentation. When users scan a QR code from a DRM Panic screen with their mobile device, they are directed to a Fedora-hosted web interface that:
1. Provides contextual information - Explains what happened in accessible language
2. Decodes and displays panic information - Presents kernel version, architecture, and error traces in a structured, readable format
3. Facilitates bug reporting - Offers streamlined integration with Fedora Bugzilla, pre-filling bug reports with relevant system information and error traces
4. Improves user experience - Uses PatternFly design patterns to provide interface consistent with #Fedora's design language"""@kernellogger @jose_exposito would be ironic if we get nice experience for reporting kernel bugs while the tools for doing the same for userspace crashes are dropped ...
-
@kernellogger @jose_exposito would be ironic if we get nice experience for reporting kernel bugs while the tools for doing the same for userspace crashes are dropped ...
@decathorpe @jose_exposito yeah, but that's how it is sometimes; but if there is demand/interest, then some revived or brand-new solution will show up sooner or later. I for one still miss kerneloops.org (https://lwn.net/Articles/298596/ ) and still hope that someone will revive this sooner or later (abrt could do this, but it was not used much, among others because it was too distro-specific).
-
@decathorpe @jose_exposito yeah, but that's how it is sometimes; but if there is demand/interest, then some revived or brand-new solution will show up sooner or later. I for one still miss kerneloops.org (https://lwn.net/Articles/298596/ ) and still hope that someone will revive this sooner or later (abrt could do this, but it was not used much, among others because it was too distro-specific).
@kernellogger right now it feels like Red Hat it silently neglecting abrt but hugging it close until it's dead
even announcing that they no longer want to invest in it and would hand the project over to community maintainers would be better than silently letting it die and then removing it from Fedora "because it's dead"
