[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
Sennaista, you might want to have a look at ~/.xsession-errors, see if there is an error message in there that might be related to your keyboard layout configuration. -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
RedVivi schrieb: I encountered the same problem with my integrated MacBookPro keyboard. What version of Ubuntu? Have you tried with Karmic? Have you had a look at your ~/.xsession-errors file, to check whether there are any messages there related to keyboard layout configuration? -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430705] Re: Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
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. -- 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 Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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 understandable and useful, and to be a good description of the cause of the error, not a mere technical detail. But I have to concede that I'm no average user, and my ideas of how they would react to such a message might be completely wrong. Of course, I agree that it would be even better if such error messages would not occur in the first place, and bug #327963 is aiming at avoiding the error message I just quoted. That might not be the only possible error, though. -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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 likely to be useful to developers, as THEY can find the xbcomp errors. This one here is about displaying the xkbcomp errors directly to user himself, which should be our final goal. So if the user encounters some xkbcomp error, some window pops up and mentions the full error message, just as xkbcomp reported it on its standard error. The user himself can then decide whether that information is useful to him in resolving the issue all by himself, or whether he needs to file a bug report. In short, the difference is between being told a file likely to contain the error message, or being told the error message itself. The first is easy to implement, and bug #430705 has a patch. The latter, which this bug here is about, is much more difficult. I guess there are two general approaches. One would pass the error message using normal function call interfaces. As the function was originated by the xkbcomp execution in libxklavier, libxklavier would be the resonable place to pick up this error message and pass it up the chain. Therefore I marked all packages in the chain as affected, and am still not sure why exactly you believe that these are not useful. The second approach to fixing this bug here would be to have gnome- settings-daemon redirect its stderr somewhere else (like a pipe, a temporary file, or something similar) before calling out to libgnomekbd. Then, if something went wrong, it could use that captured error output and display it to the user. Feels a bit hackish to redirect stderr of the current process just to get error messages of some child forked off by some lib. But this solution could in fact be implemented in gsd alone, without libxklavier or libgnomekbd. I guess I prefer the first approach, as it's much cleaner and more flexible in the long run. -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
So let me get this right: you're now working with a USB keyboard plugged into your MacBook Pro? Is it a Mac keyboard, or some other, more PCish keybord? If the latter, then Generic is most definitely the way to go, I'd say. When you claim that a Generic 102 keyboard was the only way, have you tried configuring a Mac model with a simple (i.e. not mentioning mac) US layout, as I suggested? I know little about VirtualBox, but I assume that it the ransfer of key events from the host OS to the guest OS works on the level of scan codes, not characters. I don't know whether these scan codes are passed dirctly as received, or rather generated according to some kind of virtual keyboard the guest sees. In any case, I assume that keyboard layout configured in the host should have little to do with this. Instead, twaking configuration options in the guest OS might help. But I suggest you ask these questions using the launchpad question facility, some mailing list, or similar. -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
OK, now gladly disregarding VB and your external keyboard. My advice is to 1. change keyboard layout from USA Mac to USA and 2. change keyboard model from Generic to Apple/MacBook/MacBook Pro. Order is relevant if you want to avoid error messages in between. If that works for you, then bug 327963 applies. If not, contents of ~/.xsession-errors could be useful. -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430705] [NEW] Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
Public bug reported: 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. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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 Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430705] Re: Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
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. ** Attachment added: lp430705a_mention_xsession-errors.patch http://launchpadlibrarian.net/31899226/lp430705a_mention_xsession-errors.patch -- 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 Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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 this will make it into karmic... -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 430705] Re: Ask for .xsession-errors in gsd-keyboard-xkb.c function activation_error
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 of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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 moment rather unlikely. The upstream gnome report might be better suited to deal with this. If you can resolve this as LATER, that would be great. If not, decide for yourself whether keeping this open is in any way useful to getting a proper solution implemented and included into Ubuntu in the long run. -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
spbrereton, if what you experience is in fact bug #327963, then I believe that you should set the MODEL to something mac (e.g. macintosh_vndr/ch) and the LAYOUT to a variant not mentioning mac (e.g. de, not de_mac). The reason is that the layout files for mac models simply don't mention any specific mac layout variants, as all the mac model layouts are for mac. In other words, the macintosh_vndr/ch file describes a layout called de which fits the default swiss mac layout, but no layout called de_mac. Bug #327963 has been turned into a request to introduce the latter as an alias to the former, in order to avoid this confusion. If you want to support that, subscribe to that bug and/or mark it as affecting you as well. The other way, using a generic MODEL with a *_mac LAYOUT does work as well, as far as the configuration files are concerned. The result is probably not optimal, though, as that configuration is intended to simulate mac-like behaviour on a non-mac keyboard. So if your keyboard was built by apple, the other approach is preferable. Further discussion on the speific issue of mac keyboard models with mac layout variants should probably go to bug 327963 as well, as that bug is more specific, while this one here does deal with several other and probably unrelated issues as well. -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 raketenman wrote: Error:No Symbols named de_mac in the include file macintosh_vndr/ch Same as my bug #327963, I guess. You can either have a Macintosh Swiss keyboard model with a German layout, or you can have a generic keyboard model with a special Macintosh German layout. As the former uses the keys as labeled out on the Mac, it's probably what you want. So simply change the layout from de_mac to de, and you should be all right. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpohM8ACgkQRhp6o4m9dFvvcQCfW9YR48QkH5Fevy9Gz7pP7OOJ cEoAnjLmPOolFNB2fDJLg1pXtMBb8tPZ =x4FP -END PGP SIGNATURE- -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
** 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.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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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=015e92a82c6bd19b4d3fcbcbe6ebf950790aba24 This changeset might proove difficult to backport to intrepid, though, because it builds on the following one: http://git.gnome.org/cgit/gnome-settings-daemon/commit/?id=3be2d805d369f0812882e18792e51cb1bd8bf1c5 So either both would need to be backported, or the second argument of daemon(3) should be changed to 1 to give similar behaviour. All assuming that you want to backport this kind of usability fix in the first place. For the not so technically inclined user, finding the error message is probably still rather difficult. As an alternative, I'd suggest changing the error dialog generated by the activation_error function in plugins/keyboard/gsd-keyboard-xkb.c of the gnome-settings-daemon sources. That error message already tells users to include some information if they wish to file a bug, namely the result of xprop -root | grep XKB and the result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd. In my opinion, it would make a lot of sense to ask them for the contents of ~/.xsession-errors as well. Will the gnome-settings-daemon admins from ubuntu tale it from here, or should I file a separate bug for the change of this error message? Do you need a patch? -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
Starting with Jaunty, people seeing this Error activating XKB configuration dialog might have a look at the .xsession-errors file in their home directory. Error messages from xkbcomp will end up there, and others might as well. Maybe the information from these files can be used to differentiate the huge number of bugs duped here, and identify the actual causes. -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] Re: xkbcomp errors should be displayed
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 might have to revert their change or introduce some artificial problem with the xkeyboard-config data. Or use some unfixed aspect of bug #67188. do you get that at the session start or when using the capplet? Both. When using gnome-keyboard-properties it happens, and when leaving the broken settings, it happens again at session start. -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328980] [NEW] Pass error messages from xkbcomp to Gnome user
Public bug reported: Binary package hint: gnome-settings-daemon When the user runs gnome-keyboard-properties and some of his settings cause xkbcomp to fail, the user gets a general error message about Error activating XKB configuration and some obscure hints as to where the cause might lie. The same holds for starting a Gnome session with a broken configuration. This leads to little information available in bugs like the often-duped bug #67188. 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-daemon is where the current error dialog is generated, but the actual call to xkbcomp seems to be in libxklavier, with libgnomekbd in between. I'll try to mark this bug as affecting all these packages. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: libgnomekbd (Ubuntu) Importance: Undecided Status: New ** Affects: libxklavier (Ubuntu) Importance: Undecided Status: New ** Also affects: libgnomekbd (Ubuntu) Importance: Undecided Status: New ** Also affects: libxklavier (Ubuntu) Importance: Undecided Status: New -- Pass error messages from xkbcomp to Gnome user https://bugs.launchpad.net/bugs/328980 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 327963] Re: Error activating XKB configuration with MacBook keyboard model
Getting a better error message for the Gnome UI is a GNOME issue obviously, not xkeyboard-config's duty, and really ought to be filed separately against the appropriate GNOME component. I agree, just filed bug #328980 for this. It's a bit tricky, as it involves multiple packages. As to the secondary bug of the error activating XKB, that's a well known issue so will dupe to that. Undupe (and clarify) if you'd like something differently done. I had bug #67188 considered before filing mine, but the mention of editing xorg.conf in the headline didn't seem to apply to me at all, so I filed a new one. Now that I've read all the comments in #67188, I get the feeling that it is a large collection of bugs with quite different reasons, but all looking the same due to missing error messages. Some, like bug #67188 comment #38, are the same as this one here, while others have different causes, for which I don't know the reason. For lack of information, I expect #67188 to remain open for quite a long time. In contrast to this, the scope of what I request for here is much clearer, and a fix is possible. Therefore I'd undupe and ask that you 1. make macintosh_vndr/de(mac_nodeadkeys) an alias for macintosh_vndr/de(nodeadkeys) 2. Do the same for the deadkeys variant 3. Do the same for languages other than de with similar configuration The attached patch tries to follow this approach. I grepped fro 'mac' in symbols/* and then made sure the same variants were included as aliases in symbols/macintosh_vndr/*. Not tested yet. You might, on the other hand, be of the opinion that having different names for the same symbols is not the way to go, and that instead of providing these aliases at the xkb-data level, the user interface should prevent the user from selecting such combinations. In that case, another bug for the Gnome control-center would be in order, while you might mark this as invalid for xkeyboard-config. ** Attachment added: Add aliases for mac layouts http://launchpadlibrarian.net/22577721/bug327963a.diff ** This bug is no longer a duplicate of bug 67188 Error activating XKB configuration. - Requires manual xorg.conf editing -- Error activating XKB configuration with MacBook keyboard model https://bugs.launchpad.net/bugs/327963 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee (via bug 67188). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 67188] Re: Error activating XKB configuration. - Requires manual xorg.conf editing
I have the feeling that this bug here might be a collection of several distinct issues, which all look the same due to lack of precise error messages. I filed bug #328980 asking for error messages to be displayed to the user. Until then, you might use the attached script to learn more about this kind of error. Download it, and then call sudo bash DownloadedScriptName install in order to install a wrapper around xkbcomp. Then reproduce the issue, and have a look at /tmp/xkb.*/* for more details about xkbcomp invocations, especially /tmp/xkb.*/err for standard error messages. Once you are done, you can invoke the script with sudo bash DownloadedScriptName uninstall to remove the wrapper and sudo bash DownloadedScriptName clean to delete the collected data. With such a wrapper, you can get additional information, like shown in bug #327963 for my own Mac-related issue. Maybe with this information it becomes possible to distinguish the different causes of xkb error messages, and address them appropriately. ** Attachment added: Install debug wrapper around xkbcomp http://launchpadlibrarian.net/22579754/debug67188.sh -- Error activating XKB configuration. - Requires manual xorg.conf editing https://bugs.launchpad.net/bugs/67188 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
