[orca-list] Orca Completely BROKEN Under GNOME 3.2!!!



After installing the gnome 3.2 stuff from the testing repository in
Arch Linux, I decided to go and try and use orca-3.2 from that same
repo.

**NOTHING** **NOTHING**!!! No speech, no nothing! I captured a
  typescript from the console where I started startx.  Maybe something
  in there can shed some light.  I even tried to manually restart Orca
  from the gnome session but I got nothing from that either.

right now, this is show stopper stuff for me; I can no longer use
gnome on my system at all!

Note that I pressed Ctrl+C to kill gnome and close out the script capture.
----- Begin startx messages -----
Script started on Thu 29 Sep 2011 05:36:54 AM PDT
steve linlap ~$ startx


X.Org X Server 1.11.1
Release Date: 2011-09-24
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.0-ARCH x86_64 
Current Operating System: Linux linlap 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64
Kernel command line: root=/dev/disk/by-uuid/19106a51-f3e6-46f0-b608-e5788006f9c5 ro
Build Date: 24 September 2011  11:17:05AM
 
Current version of pixman: 0.22.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
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: Thu Sep 29 05:37:04 2011
(==) Using config directory: "/etc/X11/xorg.conf.d"
gnome-session[1956]: WARNING: Unable to find required component 'gnome-shell'

(process:1968): GLib-GObject-CRITICAL **: gtype.c:2708: You forgot to call g_type_init()

(process:1968): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

(process:1968): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
gnome-session[1956]: WARNING: Application 'at-spi-registryd.desktop' killed by signal
GNOME_KEYRING_CONTROL=/tmp/keyring-jiHDTL
GPG_AGENT_INFO=/tmp/keyring-jiHDTL/gpg:0:1
GNOME_KEYRING_PID=1979
GNOME_KEYRING_CONTROL=/tmp/keyring-jiHDTL
GPG_AGENT_INFO=/tmp/keyring-jiHDTL/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-jiHDTL/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-jiHDTL
GPG_AGENT_INFO=/tmp/keyring-jiHDTL/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-jiHDTL/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-jiHDTL
GPG_AGENT_INFO=/tmp/keyring-jiHDTL/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-jiHDTL/ssh

(gnome-settings-daemon:1970): keybindings-plugin-WARNING **: Key binding (screenreader) is incomplete

(gnome-settings-daemon:1970): keybindings-plugin-WARNING **: Key binding (magnifier) is incomplete

(gnome-settings-daemon:1970): keybindings-plugin-WARNING **: Key binding (onscreenkeyboard) is incomplete
WARNING: no socket to connect to
[1317299833,000,xklavier.c:xkl_engine_start_listen/]    The backend does not require manual layout management 
- but it is provided by the application
common-plugin-Message: checking whether we have a device for 4: yes
common-plugin-Message: checking whether we have a device for 5: yes
common-plugin-Message: checking whether we have a device for 6: yes
common-plugin-Message: checking whether we have a device for 7: yes
common-plugin-Message: checking whether we have a device for 8: yes
common-plugin-Message: checking whether we have a device for 9: yes
common-plugin-Message: checking whether we have a device for 10: yes
common-plugin-Message: checking whether we have a device for 11: yes
common-plugin-Message: checking whether we have a device for 12: yes
Window manager warning: Failed to load theme "Clearlooks": Failed to find a valid file for theme Clearlooks

glibtop: Non-standard uts for running kernel:
release 3.0-ARCH=3.0.0 gives version code 196608

** (gnome-fallback-mount-helper:2115): DEBUG: Starting automounting manager
Failed to play sound: File or data not found
** (gnome-fallback-mount-helper:2115): DEBUG: Found ConsoleKit session at path 
/org/freedesktop/ConsoleKit/Session5
** (gnome-fallback-mount-helper:2115): DEBUG: ScreenSaver name appeared
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 1
** (gnome-fallback-mount-helper:2115): DEBUG: ScreenSaver proxy ready
** (gnome-fallback-mount-helper:2115): DEBUG: Screensaver GetActive() returned 0
** Message: applet now removed from the notification area

** (nm-applet:2091): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper 
exited with unknown return code 1.

** (nm-applet:2091): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper 
exited with unknown return code 1.

** (nm-applet:2091): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown 
return code 1
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/orca/orca.py", line 38, in <module>
    from gi.repository.Gio import Settings
ImportError: No module named gi.repository.Gio
Initializing nautilus-dropbox 0.6.7
Starting Dropbox...** Message: applet now embedded in the notification area
** Message: applet now removed from the notification area
Dropbox isn't running!
Done!

(gnome-settings-daemon:1970): power-plugin-WARNING **: failed to restore backlight to 100: out of brightness 
range: 100, has to be 10 -> 0

(gnome-settings-daemon:1970): power-plugin-WARNING **: failed to restore backlight to 100: out of brightness 
range: 100, has to be 10 -> 0
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 0
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 1
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/orca/orca.py", line 38, in <module>
    from gi.repository.Gio import Settings
ImportError: No module named gi.repository.Gio

(gnome-settings-daemon:1970): power-plugin-WARNING **: failed to restore backlight to 100: out of brightness 
range: 100, has to be 10 -> 0
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 0
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 1
** (gnome-fallback-mount-helper:2115): DEBUG: ConsoleKit session is active 0
^Cxinit: connection to X server lost

waiting for X server to shut down dropbox: Fatal IO error 104 (Connection reset by peer) on X server :0.
Server terminated successfully (0). Closing log file.
gnome-session[1956]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X 
server :0.


xinit: unexpected signal 2
steve linlap ~$ exit
exit

Script done on Thu 29 Sep 2011 05:46:28 AM PDT
----- End of startx messages -----



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