[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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




Reply to: