Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve xserver abrt reports #612

Open
ofourdan opened this issue Sep 10, 2019 · 0 comments
Open

Improve xserver abrt reports #612

ofourdan opened this issue Sep 10, 2019 · 0 comments

Comments

@ofourdan
Copy link

Currently, for Xserver crashes, abrt is reporting:

  • A backtrace, apparently taken from the Xserver's own backtrace feature
  • cpuinfo
  • dmesg
  • dso_list
  • etc_X11_xorg_conf_d.tar.gz
  • usr_share_xorg_conf_d.tar.gz

But that's missing an important bit, the actual logs.

Unfortunately, depending on the type of Xserver (Xorg or Xwayland which are the two main Xservers we're interested in), the logs are not found at the same location...

For Xorg, the Xorg.<x>.log (where is the display number) are found either in /var/log/ or in ~/.local/share/xorg/

For Xwayland, there is no log file, everything is sent to stderr which ends up in journalctl under the gnome-shell domain (when gnome-shell/mutter is the Wayland compositor, which is the case in Fedora).

Also, previously, the Xserver would catch all crashes and generate the backtrace itself. However, recent versions of the Xserver (1.19) will not prevent a coredump anymore (https://gitlab.freedesktop.org/xorg/xserver/commit/9c7288793) so ideally abrt should use that with gdb to get a much better backtrace than the Xserver itself can provide.

So, long story short, I think for the Xserver (either Xorg or Xwayland), we'd need:

  • the Xorg logs (even if irrelevant for Xwayland)
  • journalctl /usr/bin/gnome-shell around the time of the crash (like a 5 mins before and after window)
  • A gdb backtrace of the crash instead of the Xserver's own backtrace which is incomplete and often misleading.
@xsuchy xsuchy transferred this issue from abrt/abrt Apr 9, 2020
@xsuchy xsuchy added this to Needs triage in Issue review via automation Apr 9, 2020
@xsuchy xsuchy moved this from Needs triage to Maybe in Issue review Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Issue review
  
Maybe
Development

No branches or pull requests

2 participants