** Also affects: onboard
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title:
On every startup Onboard asks for enab
I observe the same behaviour as in comment #19.
Clean installation 13.10x64, up to date.
cat .xsession-errors
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: Proces at-spi2-registryd main został zakończony, ponowne uruchamianie
ini
Luke, could you have a look to this bug and see if that's something we
should work on
** Changed in: onboard (Ubuntu)
Assignee: (unassigned) => Luke Yelavich (themuso)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-d
** Changed in: onboard (Ubuntu)
Milestone: ubuntu-13.10 => saucy-updates
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: ubuntu-13.10 => saucy-updates
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon
I get a black screen for 5-10 seconds every time I logon after upgrading
to 13.10. I have this in ~/.xsession-errors
thnov@thnov-desktop:~$ cat .xsession-errors
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: at-spi2-registryd main
I have now tried more three times and the dialog still appears.
"gsettings get org.gnome.settings-daemon.plugins.a11y-settings active"
still gives "false".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Now I have rebooted due to a Bluetooth problem and after rebooting after
every login starting Onboard does not pop up the dialog any more. Seems
that the reboot has fixed this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-setting
You might see the dialog one more time after turning the plugin off.
Does it still show after repeated logins?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title
I think we should simply stay in a11y mode all the time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title:
On every startup Onboard asks for enabling accessi
I have done "gsettings set org.gnome.settings-daemon.plugins.a11y-
settings active false" currently and I have checked that it is actually
set this way via "gsettings get org.gnome.settings-daemon.plugins.a11y-
settings active", but when starting Onboard after login the dialog
asking whether I want
Nothing found in the logs.
I had also further login failures later, so probably the problems are
independent.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title
I can't reproduce the login problems here, no good idea why that happens
for you. I must be missing something, but the plugin really doesn't seem
to do a lot.
Is there anything in the other log files?
sudo grep -r at-spi2-registryd /var/log/*
--
You received this bug notification because you are
For the at-spi2 messages I have also reported bug 1228567.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title:
On every startup Onboard asks for enabling acces
I have made another important observation:
If I run
gsettings set org.gnome.settings-daemon.plugins.a11y-settings active
false
the dialog asking to activate accessibility goes away, but the login
very often fails, I have to enter my password in lightdm 5 or 6 times
until succeeding a login.
Aft
OK, thank you, it is indeed g-s-d then. I've opened an upstream bug report here:
https://bugzilla.gnome.org/show_bug.cgi?id=708506
I'll mark the Onboard task as "incomplete" until we know more about the
prospect for g-s-d changes. Feel free to change this.
** Bug watch added: GNOME Bug Tracker #7
Now, after doing it again and again, it started to work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1227173
Title:
On every startup Onboard asks for enabling accessi
Problem was that I have entered the gsettings commands SSHed in from
another machine. Now I have tried again on the machine's own screen and
the switching works, but now I cannot log in any more. .xsession-errors
contains
Script for cjkv started at run_im.
Script for default started at run_im.
ini
This does not work at all, the setting change is silently rejected:
till@till-twist:~$ gsettings get
org.gnome.settings-daemon.plugins.a11y-settings active
true
till@till-twist:~$ gsettings set
org.gnome.settings-daemon.plugins.a11y-settings active false
till@till-twist:~$ gsettings get
org.gno
We could set 'toolkit-accessibility' silently in Onboard's startup, but
that should be the last option. I'd prefer not to fight with gnome-
settings-daemon over that key. It would still be an incomplete solution,
since 'screen-keyboard-enabled' can be reset any time afterwards, taking
down a11y for
So for tablet mode one could perhaps activate auto-hide and
accessibility mode via gsettings, so that the question does not appear
at all, as users would not know what this is good for.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnom
As marmuta said above, the auto-show (auto-hide) needs the accessibility
framework to be enabled. In fact, it is the accessibility framework that
informs onboard about when to appear and hide. Thus, it is not possible
to use the auto-show feature without enabling the accessibility
framework.
We mi
As I use Onboard as stabdard way to do text input in tablet (=touch-
screen-only) mode the onscreen keyboard is not an accessibility feature
but a facility for all users. This means that it should not require any
special accessibility settings.
I start it with a script which gets triggered by the
Hi Till, how do you start Onboard? Is it auto-started by the Universal Access
setting in gnome-control-center?
gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled
Apparently if neither screen-keyboard nor screen-reader are enabled,
gnome-settings-daemon may turn a11y off ri
23 matches
Mail list logo
