Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error

Bug #430705 reported by Martin von Gagern
4
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Wishlist
Unassigned
Declined for Karmic by Sebastien Bacher

Bug Description

Binary package hint: gnome-settings-daemon

As mentioned in bug #328980 comment #5, it would be a good idea to have users include their ~/.xsession-errors when reporting errors with their keybord konfiguration. This is because errors from xkbcomp end up in that file. These would be particularly useful in diagnosing and resolving bugs like bug #67188.

I therefore would ask you to add that file or its tail to the list of information requested by the activation_error function in plugins/keyboard/gsd-keyboard-xkb.c. Requesting the result of "tail -n50 ~/.xsession-errors" has the benefit of avoiding excessively large posts. It also reuses the wording of the other requests, making it simple to adjust most translations even if you don't speak the language. Requesting only command output, as opposed to command output and file contents, should be easier for users as well.

Unfortunately I don't think there is a reliable word to grep for, so we'll have to request more information unless we want users to look for appropriate error messages themselves.

Revision history for this message
Martin von Gagern (gagern) wrote :

OK, this patch does implement the request as outlined above.

I even adjusted the message files, except for the Azerbaijani (az) one, as that uses different wording for the two existing lines, and I have no clue why that's the case. Some other languages were changed from fixed command strings to %s as in the message template.

None of this got tested by me, but I expect things to work nevertheless. You might, however, want to give one of the RTL languages, e.g. Arabic (ar), a try, just to make sure my editor didn't garble something.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, the easier way would probably to make apport (ubuntu-bug) to add the .xsession-errors to the bugs

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Martin von Gagern (gagern) wrote :

apport would make sense, yes. Should I file another report for this, or shall we mark this one here as affecting apport?

Revision history for this message
Sebastien Bacher (seb128) wrote :

could be a good idea to open an apport request about that if there is not one already yes

Revision history for this message
Sebastien Bacher (seb128) wrote :

bug #431807 has been opened after discussion with the apport maintainer on IRC

Revision history for this message
Martin von Gagern (gagern) wrote :

Bug #431807 in its current form doesn't help with the situation I'm concerned with here. The errors I have in mind come from the xkbcomp executable, and don't match the format of glib errors. I just updated to Karmic Beta and made sure that the relevant lines are still missing from the report. Matching for all xkbcomp errors using regular expressions is very difficult if not outright impossible. So for these errors, apport 1.9.2-0ubuntu1 won't give you all the required informations, and therefore this request here is still outstanding.

Revision history for this message
Martin Pitt (pitti) wrote :

FYI, as discussed in bug 431807 I added "^Error: .*No Symbols named" to the regexp matching. I don't think it's a good idea to generally submit the entire .xsession-errors, given how many privacy complaints were already even raised by things like "exposes my current working directory and thus project names I'm working on", etc.

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the request, that's not really something we should hardcode in gsd, we should rather known useful patterns to the ubuntu-bug (apport) regexp filters so they get added to all bugs where they could be useful

Changed in gnome-settings-daemon (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.