Error activating XKB configuration. Probably internal X server problem
Hello XFree devel list I am the maintainer of the Yoper distro and we are loyal to XFree. Our Gnome 2.6.1 setup (all latest libraries across the board) is currently producing an error upon login that says Error activating XKB configuration. Probably internal X server problem then it suggests to run xprop -root | grep XKB and gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb The output of is which returns: _XKB_RULES_NAMES(STRING)=xfree86,pc104,us,, and respective gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb After spending nights (literally) hunting down the bug within Gnome I have found the only relevant postings regarding a similar bug in Xorg with the hint that it was fixed by upgrading libxklavier. After doing that I and the brave users who use Gnome in Yoper still had the same error. My programming skills are low compared to my sysadmin skills, so all I could do is try out Xorg in form of SuSE's src rpm and here you go .. the error message is gone. Now all I can think at this point is that xorg has the bug and XFree hasn't but I might be very much wrong. I assume it has something to do with loading the keymap's correctly. Since I am no programmer I can only offer practical help here to fix it as I really intend to stay loyal to XFree, I hope that one of you XFree guru's could lend me 10 fingers :) and find the possible Bug in XFree or at least exclude once in for all that it is XFree. Thanks in advance Regards Andreas Girardet Yoper principal maintainer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86Io.c, libos.a GetTimeInMillis() change.
Tyler Retzlaff wrote: Just want to confirm something, xc/programs/Xserver/hw/xfree86/common/xf86Io.c,v 3.58 has had GetTimeInMillis() removed from it, the commit message doesn't say anything specific about it but is the copy of GetTimeInMillis() from libos.a the one that linked into the XFree86 server from now on? I can't speak in place of David, but I think it's a good thing to finally get rid of this duplicate definition, which has mostly caused problems when building oher X servers in addition to the XFree86 one. There are probably a few more cleanings that could be done now that XFree86 uses the libos version (and builds it). -- Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
DMX has broken binary compatibility
DMX unconditionally changed MAXFORMATS in misc.h which modified the ScreenRec and broke binary compatiblity. No third party drivers will work with XFree86 after the DMX integration. I think it was a mistake to unconditionally break binary compatibility in this way. DMX should be a build option and off by default so that third party drivers will still work. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DMX has broken binary compatibility
On Sat, Jul 17, 2004 at 12:59:04PM -0700, Mark Vojkovich wrote: DMX unconditionally changed MAXFORMATS in misc.h which modified the ScreenRec and broke binary compatiblity. This can be very easily changed back, which I have now done. In the future, if you find other areas where the code has caused ABI problems, please let me know and I will fix the problems. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Error activating XKB configuration. Probably internal X server problem
Hello Ignore my message ... 2 nights without sleep made me not see the obvious! Found the fix and it is gnome related and not XFree related. Andreas ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
