xkbcomp errors should be displayed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Settings Daemon |
Expired
|
Low
|
|||
gnome-settings-daemon (Ubuntu) |
Triaged
|
Wishlist
|
Ubuntu Desktop Bugs | ||
libgnomekbd (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
libxklavier (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: gnome-settings-
When the user runs gnome-keyboard-
Instead, I would like to see the precise error message from xkbcomp displayed to the user. At least in my original bug #327963, the information provided there was much more useful to actually locate and solve the problem.
I guess fixing this problem might include several packages. gnome-settings-
Changed in libgnomekbd (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in libxklavier (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in gnome-settings-daemon (Ubuntu): | |
status: | New → Triaged |
Changed in gnome-settings-daemon: | |
status: | Unknown → New |
Changed in gnome-settings-daemon: | |
importance: | Unknown → Low |
Changed in gnome-settings-daemon: | |
status: | New → Incomplete |
Changed in gnome-settings-daemon: | |
status: | Incomplete → Expired |
I just confirmed that the stderr of the xkbcomp invocation is redirected to /dev/null, so error messages are indeed completely lost.
A fist step towards sensible error messages would probably be to redirect stderr in libxklavier in such a way that it can be directed into the syslog. This would involve no change to interfaces or other packages, and while being far from optimal, would give users a realistic chance to see their error messages.
Once we have the message available in the current process, and sent to syslog, we could augment the interfaces to pass the message up to gnome-settings- daemon and incorporate it into the error message.