XsessionErrors should include X errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
See https:/
The current bug lacks the info we need, it was added in a comment:
"(gnome-
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 723 error_code 8 request_code 143 minor_code 22)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)"
The interesting lines there are:
"The program 'gnome-
...
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 723 error_code 8 request_code 143 minor_code 22)"
i.e the fact it's an xerror, the error type (BadMatch) and the codes
Changed in apport (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in apport (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
the .xsession-errors was added manually in the bug pointed before, https:/ /launchpad. net/bugs/ 907149 is an example with an apport XsessionErrors which lacks the pointed infos