Hide Forgot
Created attachment 837704 [details] issues with kernel oops reports There's a number of problems with the ABRT kernel oops reports which basically make them completely useless for further diagnosis. First problem covers the use of taint flags without detecting which they are: See the attached screen shot. The W (Warning) taint kernel option doesn't necessarily mean that the kernel developers are "unable to diagnose tainted reports. It just means that there was more than one Warning. The taint flag G means 'GPL module loaded' which again is perfectly diagnosable. The types of taint can be found here starting at line 215: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/kernel/panic.c So abrt should correctly detect the types of taint. Second problem is that once the kernel is classed as tainted there is no way to access the full debug. It gives you a view of a useless single line of the crash (which I can't even select) and even if I shouldn't report it as a bug I should be able to view the full output of the kernel oops so I can investigate it myself or make an educated decision as to what to do with the crash. Not sure the best component to report this against: abrt-2.1.10-1.fc20.x86_64 abrt-addon-ccpp-2.1.10-1.fc20.x86_64 abrt-addon-kerneloops-2.1.10-1.fc20.x86_64 abrt-addon-pstoreoops-2.1.10-1.fc20.x86_64 abrt-addon-python-2.1.10-1.fc20.x86_64 abrt-addon-vmcore-2.1.10-1.fc20.x86_64 abrt-addon-xorg-2.1.10-1.fc20.x86_64 abrt-dbus-2.1.10-1.fc20.x86_64 abrt-desktop-2.1.10-1.fc20.x86_64 abrt-gui-2.1.10-1.fc20.x86_64 abrt-gui-libs-2.1.10-1.fc20.x86_64 abrt-java-connector-1.0.6-1.fc20.x86_64 abrt-libs-2.1.10-1.fc20.x86_64 abrt-plugin-bodhi-2.1.10-1.fc20.x86_64 abrt-python-2.1.10-1.fc20.x86_64 abrt-retrace-client-2.1.10-1.fc20.x86_64
1) ABRT understands tainted flags - your report is intentionally not reportable because of 'W' flag - see #805337. An oops with a single 'G' flag is reportable (it says 'Not tainted' in the oops). 2) I agree that selectable description would be useful, but that's just a UI change - let's track it in #1043968. If you want full access to raw data, you can always right-click the problem in the menu and "Open problem's data directory". The raw oops is stored as 'backtrace'.
Any reason why you can't view the data through the app? If I have to go and browse it in the file system it makes the app mostly pointless as I'll just use a terminal and view it directly. I seem to remember you use to be able to do this in older versions of the app
(In reply to Peter Robinson from comment #2) > Any reason why you can't view the data through the app? Because it was too expensive for implementation and only a small portion of users want to explore problem's data. We can reconsider our assumption. > I seem to remember you use to be able to do this in older versions of the app It has never been possible to explore the data in abrt-gui itself instead you had to "Open" problem data in report-gtk and you still can do that. Just single out the problem you want to explore and hit "Ctrl+Alt+Return". Or run "gnome-abrt -x" and you should see "Analyze" button next to "Delete" and "Report" buttons.
> It has never been possible to explore the data in abrt-gui itself instead > you had to "Open" problem data in report-gtk and you still can do that. Just > single out the problem you want to explore and hit "Ctrl+Alt+Return". Or run > "gnome-abrt -x" and you should see "Analyze" button next to "Delete" and > "Report" buttons. It was this functionality I was thinking of. Any means of making this an option I can enable so I get it by default when abrt pops up a notification?
(In reply to Peter Robinson from comment #4) > > It has never been possible to explore the data in abrt-gui itself instead > > you had to "Open" problem data in report-gtk and you still can do that. Just > > single out the problem you want to explore and hit "Ctrl+Alt+Return". Or run > > "gnome-abrt -x" and you should see "Analyze" button next to "Delete" and > > "Report" buttons. > > It was this functionality I was thinking of. Any means of making this an > option I can enable so I get it by default when abrt pops up a notification? ??
(In reply to Peter Robinson from comment #5) > (In reply to Peter Robinson from comment #4) > > > It has never been possible to explore the data in abrt-gui itself instead > > > you had to "Open" problem data in report-gtk and you still can do that. Just > > > single out the problem you want to explore and hit "Ctrl+Alt+Return". Or run > > > "gnome-abrt -x" and you should see "Analyze" button next to "Delete" and > > > "Report" buttons. > > > > It was this functionality I was thinking of. Any means of making this an > > option I can enable so I get it by default when abrt pops up a notification? > > ?? You have to modify 'report-gui' event. This command will do that for you. $ cd /etc/libreport/events.d/ $ sed -i 's/report-gtk --/report-gtk -x --/' ccpp_event.conf python_event.conf python3_event.conf vmcore_event.conf koops_event.conf ruby_event.conf java_event.conf