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
--
You
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 proje
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. Matc
bug #431807 has been opened after discussion with the apport maintainer
on IRC
--
Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
https://bugs.launchpad.net/bugs/430705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
could be a good idea to open an apport request about that if there is
not one already yes
--
Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
https://bugs.launchpad.net/bugs/430705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
apport would make sense, yes. Should I file another report for this, or
shall we mark this one here as affecting apport?
--
Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
https://bugs.launchpad.net/bugs/430705
You received this bug notification because you are a member o
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
--
Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
https://
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