[Fwd: Debugging accessible GDM in Feisty -- please help]
Brian Cameron
Brian.Cameron at Sun.COM
Tue Feb 6 08:08:26 GMT 2007
Henrik:
> Thanks Brian for the detailed directions.
>
> OK, I already had something quite similar to this. I select the Plain
> greeter, tick accessible login and restart (log out). GDM fails to come
> up, only showing the spinner and running the CPU full out, it seems.
>
> I found a log file though! /var/log/gdm/:0.log (attached) seems to show
> a conflict with the wacom tablet, which is a specific ubuntu xorg config
> (and the one causing GOK problems to crash for a long time)
>
> And sure enough ... commenting out all the wacom stuff in
> /etc/X11/xorg.conf brings GDM back to life with the old style greeter. I
> guess the wacom settings are needed to to support tablet PCs, so should
> probably be fixed though.
>
> Even the themed greeter runs now and Ctrl+o does indeed bring up Orca
> (in magnifier mode). Right, time to test the individual options in more
> detail ...
Please let me know what you find, and if you find bugs please file them
in bugzilla so we can fix them. Especially if you notice odd behavior
with specific AT programs using gdmlogin versus gdmgreeter.
Glad I was able to help!
Brian
> ------------------------------------------------------------------------
>
>
> X Window System Version 7.1.1
> Release Date: 12 May 2006
> X Protocol Version 11, Revision 0, Release 7.1.1
> Build Operating System: Linux 2.6.15.7 x86_64
> Current Operating System: Linux ubuntu-desktop 2.6.20-6-generic #2 SMP Wed Jan 31 19:04:30 UTC 2007 x86_64
> Build Date: 07 July 2006
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 5 12:52:04 2007
> (==) Using config file: "/etc/X11/xorg.conf"
> (EE) end of block range 0x3ffffff < begin 0xe0000000
> (EE) end of block range 0x3ffffff < begin 0xe0000000
> (EE) AIGLX: Screen 0 is not DRI capable
> error opening security policy file /usr/lib/xserver/SecurityPolicy
> The XKEYBOARD keymap compiler (xkbcomp) reports:
>> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>> Ignoring extra symbols
> Errors from xkbcomp are not fatal to the X server
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> (EE) xf86OpenSerial: Cannot open device /dev/wacom
> No such file or directory.
> Error opening /dev/wacom : Success
> Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
> Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
> Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
More information about the Ubuntu-accessibility
mailing list