Re: starting orca on oneiric
Hy, Luke, own purpose I tryed customize an oldest Oneiric live CD (date is 2011-09-07). I setted the active session with gnome-fallback session after I installed gnome-session-fallback package. Accessibility related configurations is proper setted when live CD is booted, because I putted required config directoryes and files with /etc/skel folder. The desktop is launched properly, but Orca 3.1.91 version can't start. In GNOME Terminal I see following error message: Gtk-Message: Failed to load module gail ** (orca:3714): WARNING **: Invalid object type create /usr/lib/python2.7/dist-packages/gi/module.py:123: Warning: cannot register existing type `EventType' wrapper = enum_register_new_gtype_and_add(info) ** (orca:3714): CRITICAL **: pyg_enum_add: assertion `typename != NULL' failed Cannot start Orca because it cannot connect to the Desktop. Please make sure the DISPLAY environment variable has been set. ubuntu@ubuntu:~$ Why can not possible connecting Orca with the desktop? Why not setting automaticaly with the DISPLAY environment with :0.0 variable? If I remember right, oldest releases this environment automaticaly setted. I not looked yet the latest available daily live CD, now downloading the latest iso. Attila -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: starting orca on oneiric
One more thought, is there an easy way to choose unity 2d to see if that yields any better results? On 09/07/2011 07:50 PM, Guy Schlosser wrote: Hi all, I have a question concerning getting orca started in Oneiric. After I installed the latest package updates, I rebooted, logged in and when I launched Orca, I was able to get through the setup, and accessibility was finally enabled. Now when I log out and back in, I get no speech. Is there something I'm not doing? Any help would be greatly appreciated. Thanks, Guy -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: starting orca on oneiric
Hy, Luke, when I booted latest Oneiric daily live cd with access=v3 boot parameter, the GSettings related accessibility properties I think is not setted with casper a11y related module (/usr/bin/casper-a11y-enable script). Not happening this because dbus is not running when casper try setting the required GSettings properties? Required GSettings keys is following for example with blindness profile: org.gnome.desktop.a11y.applications screen-reader-enabled true, org.gnome.Empathy.conversation theme classic, org.gnome.desktop.interface toolkit-accessibility true, org.gnome.yelp show-cursor true When I launch manual Orca, presented Orca text setup. I answered all question. Because Orca doesn't logged out me automaticaly when setup process is finished, I restart manual LightDm login manager in console with following command: sudo service lightdm restart Unfortunately doesn't happen any changes. For example, if I looked Orca version number, I see only a terminated message. I try ask for example the org.gnome.desktop.applications screen-reader-enabled GSettings key, this GSettings key value is false. If I try manual set this GSettings key with true value, nothing changed. This is a known bug now, or changed the blindness profile required boot parameter and I not known right boot parameter? When I some months ago try doing a custom Oneiric live CD, I see chroot environment doesn't possible setting required GSettings keys. I think this key changes working only if I created the machine-id file with /var/lib/dbus directory with following command in chroot environment: dbus-uuidgen var/lib/dbus/machine-id Attila -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
