Bug#435684: xserver-xorg: Error activating XKB configuration
Kristis Makris wrote: > I upgraded to Debian Etch. `apt-get dist-upgrade` > >From Sarge, I guess ? > I *can* upgrade the X packages to testing or unstable, but I *don't > want to*, given the current track record. e.g. the fact that upgrading > will bring down a ton of other ***unnecessary dependencies that > Well, you know, these dependencies may bring new features, bug fixes, better documentation, higher speed, make coffee, ... > could have been avoided if the testing packages had been compiled > against the minimum dependencies (http://www.mkgnu.net/?q=node/103) of > the software. This URL does not work. But anyway, there is no point in building testing packages against old dependencies. backports.org takes care of building for older systems, but it does look not ready on the X.org side yet. >> Does it help if you comment XkbLayout and XkbVariant out? >> > > I just tried this but it does not help. I still get the same error message. > Since it's a Gnome window, it might just be Gnome related. I asked some Gnome guys. It looks like there are bugs in the XKB libs, and there is no easy way to workaround them. For now you should change your keyboard layout in Gnome until the XKB libs accept them. Try resetting to a default layout first (until the warning disappears) and then applying your required changes. If Gnome refuses because of the above message, you might have to change directly in the gconf database, we'll see. >>> (II) LoadModule: "speedo" >>> (WW) Warning, couldn't open module speedo >>> (II) UnloadModule: "speedo" >>> (EE) Failed to load module "speedo" (module does not exist, 0) >>> >>> >> (unrelated) Remove speedo there too. >> > > (unrelated) I just removed it. Of course, *I* never added those > modules there. The X tools did. If they are not loading, why don't the > X tools resolve this ? > Because it just a warning. Modifying your config file automatically from a script is not trivial (because people tweak them), so it's not necessary worth doing it for such a warning. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435684: xserver-xorg: Error activating XKB configuration
Hi Brice, I'm frustrated with upgrades and Debian. On 8/5/07, Brice Goglin <[EMAIL PROTECTED]> wrote: > Kristis Makris wrote: > > Every time I start x I get the following error message showing up in a > > gnome window: > > > > When did this problem start to occur? Did you upgrade some packages at > this point? /var/log/dpkg.log and/or /var/log/aptitude might help. I upgraded to Debian Etch. `apt-get dist-upgrade` > Did you configure some keyboard stuff in gnome earlier? Are you running > a plain Etch or do you have anything older or more recent? Your X > packages seem to be from Etch. What about gnome? Can you upgrade the X > packages to testing or unstable? I'm running a plain Etch gnome and X. I *can* upgrade the X packages to testing or unstable, but I *don't want to*, given the current track record. e.g. the fact that upgrading will bring down a ton of other ***unnecessary dependencies that could have been avoided if the testing packages had been compiled against the minimum dependencies (http://www.mkgnu.net/?q=node/103) of the software. Not to mention that for the past 4 years after I start X if I switch back to a text console the text looks jagged, permanently (but not if the system is just booting). At this point I want things to work as expected. It was working with Debian 3.0. It should work now. > > Section "InputDevice" > > Identifier "Generic Keyboard" > > Driver "kbd" > > Option "CoreKeyboard" > > Option "XkbRules" "xorg" > > Option "XkbModel" "pc104" > > Option "XkbLayout" "dvorak" > > Option "XkbVariant""dvorak" > > EndSection > > > > Does it help if you comment XkbLayout and XkbVariant out? I just tried this but it does not help. I still get the same error message. > (unrelated) Remove GLcore from the module sections of your xorg.conf, it > will loaded automatically when needed. (unrelated) I just removed it. > > (II) LoadModule: "speedo" > > (WW) Warning, couldn't open module speedo > > (II) UnloadModule: "speedo" > > (EE) Failed to load module "speedo" (module does not exist, 0) > > > > (unrelated) Remove speedo there too. (unrelated) I just removed it. Of course, *I* never added those modules there. The X tools did. If they are not loading, why don't the X tools resolve this ? > > (II) I810(0): [drm] DRM interface version 1.2 > > (II) I810(0): [drm] created "i915" driver at busid "pci::00:02.0" > > (II) I810(0): [drm] added 8192 byte SAREA at 0xf04dd000 > > (II) I810(0): [drm] mapped SAREA 0xf04dd000 to 0xb7b59000 > > (II) I810(0): [drm] framebuffer handle = 0xf002 > > (II) I810(0): [drm] added 1 reserved context for kernel > > (WW) I810(0): i830 Kernel module detected, Use the i915 Kernel module > > instead, aborting DRI init. > > > > (unrelated) Are look loading the i830 kernel module explicitly in > /etc/modules or so? You should remove it, i915 will be loaded > automatically instead and it will give you DRI. (unrelated) I just removed it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435684: xserver-xorg: Error activating XKB configuration
Kristis Makris wrote: > Every time I start x I get the following error message showing up in a > gnome window: > When did this problem start to occur? Did you upgrade some packages at this point? /var/log/dpkg.log and/or /var/log/aptitude might help. > ++ > Error activating XKB configuration. > It can happen under various circumstances: > - a bug in libxklavier library > - a bug in X server (xkbcomp, xmodmap utilities) > - X server with incompatible libxkbfile implementation > > X server version data: > The X.org Foundation > 70101000 > > If you report this situation as a bug, please include: > - The result of xprop -root | grep XKB > - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd > ++ > Did you configure some keyboard stuff in gnome earlier? Are you running a plain Etch or do you have anything older or more recent? Your X packages seem to be from Etch. What about gnome? Can you upgrade the X packages to testing or unstable? > Section "InputDevice" > Identifier "Generic Keyboard" > Driver "kbd" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc104" > Option "XkbLayout" "dvorak" > Option "XkbVariant""dvorak" > EndSection > Does it help if you comment XkbLayout and XkbVariant out? > (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so > dlopen: /usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol: > _glapi_Dispatch > (EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so > (II) UnloadModule: "GLcore" > (EE) Failed to load module "GLcore" (loader failed, 7) > (unrelated) Remove GLcore from the module sections of your xorg.conf, it will loaded automatically when needed. > (II) LoadModule: "speedo" > (WW) Warning, couldn't open module speedo > (II) UnloadModule: "speedo" > (EE) Failed to load module "speedo" (module does not exist, 0) > (unrelated) Remove speedo there too. > (II) I810(0): [drm] DRM interface version 1.2 > (II) I810(0): [drm] created "i915" driver at busid "pci::00:02.0" > (II) I810(0): [drm] added 8192 byte SAREA at 0xf04dd000 > (II) I810(0): [drm] mapped SAREA 0xf04dd000 to 0xb7b59000 > (II) I810(0): [drm] framebuffer handle = 0xf002 > (II) I810(0): [drm] added 1 reserved context for kernel > (WW) I810(0): i830 Kernel module detected, Use the i915 Kernel module > instead, aborting DRI init. > (unrelated) Are look loading the i830 kernel module explicitly in /etc/modules or so? You should remove it, i915 will be loaded automatically instead and it will give you DRI. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
