** Changed in: gnome-settings-daemon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/328980
Title:
xkbcomp errors should be displayed
To manage notifications ab
** Changed in: gnome-settings-daemon
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/328980
Title:
xkbcomp errors should be displayed
To manage notifications about
** Changed in: gnome-settings-daemon
Importance: Unknown => Low
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@
The core problem this is trying to address is that currently errors
occur in the underlying code, but due to the nonspecific error message,
the bugs are all getting lumped together and not even getting triaged
properly, thus the bugs are failing to get fixed.
Ultimately, the real solution is to ge
the issue is that the current dialog message is of no use, the fix would
not be to add technical informations but to change it to be clear to an
average user and give useful clue on what to do not requiring techinical
skills
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/32
So you say that an error message containing some technical information
is worse than one with almost no information at all? I'm sure I disagree
for myself, as I find an error message like 'No Symbols named
"mac_nodeadkeys" in the include file "macintosh_vndr/de"' (from bug
#327963) to be both under
not sure I agree with displaying those errors to users, that would just
be non understandable dialogs, those technicals details should go in
bugs and not be showed in user's face directly where they are of no use
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You rec
The new one I opened requests that users be told to include their
.xsession-errors in bug reports, which is a first step. So if a user
encounters some xkbcomp error, and wants to report a bug about it, then
he will include a portion of that error log file, and the resulting bug
report will be more
Closing the libxklavier and libgnomekbd tasks they are not useful, how
this bug is different of the new one you opened about changing the user
dialog?
** Changed in: libgnomekbd (Ubuntu)
Status: New => Invalid
** Changed in: libxklavier (Ubuntu)
Status: New => Invalid
--
xkbcomp e
I personally would wish for the error message to be displayed to the
user in a dialog window, not only logged in some obscure file. So my
original request hasn't been dealt with in full.
However, I believe that taking the lack of manpower into account, a
solution at the distro level is at the mome
should this bug be closed now? the lack of reply is a manpower issue and
due to the fact that nobody in the ubuntu desktop team has special
interest for keyboard issues
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You received this bug notification because you are
I'll take the two months without reply from the ubuntu maintainers of
gnome-settings-daemon as a "No" to my question wherther they'd take it
from here. So I just filed a separate request, bug #430705, about
mentioning ~/.xsession-errors in the error message after a failed xkb
activation. Let's hope
Starting with Jaunty, error messages from xkbcomp end up in ~/.xsession-
errors where they can be inspected by the technically inclined user.
This is probably due to the following change in gnome-settings-daemon:
http://git.gnome.org/cgit/gnome-settings-daemon/commit/?id=015e92a82c6bd19b4d3fcbcbe6
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Triaged
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
** Bug watch added: GNOME Bug Tracker #588607
http://bugzilla.gnome.org/show_bug.cgi?id=588607
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_bug.cgi?id=588607
Importance: Unknown
Status: Unknown
--
xkbcomp errors should be displayed
https://bugs.launch
** Changed in: libgnomekbd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: libxklavier (Ubuntu)
Importance: Undecided => Wishlist
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
You received this bug notification because you are a member of Ubuntu
Des
> could you describe a way to trigger the error?
I hit this in bug #327963. So a way to reproduce is this:
1. set keyboard layout to "Germany Macintosh, no dead keys"
2. set keyboard model to "MacBook / MacBook Pro (Intl)"
This might only work until someone fixes #327963, though. After that,
you
could you describe a way to trigger the error? do you get that at the
session start or when using the capplet?
** Summary changed:
- Pass error messages from xkbcomp to Gnome user
+ xkbcomp errors should be displayed
--
xkbcomp errors should be displayed
https://bugs.launchpad.net/bugs/328980
Y
19 matches
Mail list logo
