** Tags added: a11y
** Tags removed: accessibility
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are a member of
** Branch linked: lp:ubuntu/gnome-orca
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are a member of Ubuntu
Luke, I tested your Orca fix.
Before I updated my system, I removed my doed .bash_logout and
/etc/gdm/PostSession/Default file modifications.
When gnome-orca package is updated, I restart my system.
First login operation is works perfect, Orca is talking fine both GDM login
screen and after
** Changed in: casper (Ubuntu)
Status: Confirmed = New
** Changed in: gnome-orca (Ubuntu)
Status: Fix Released = Confirmed
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
The casper part of this bug is fixed. The rest is not a casper problem,
its an Orca problem.
** Changed in: casper (Ubuntu)
Status: New = Fix Released
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness
Ok I understand now, you want to make sure things get cleaned up in the
case where the desktop may crash. I'll reproduce here and attempt to
make a fix.
** Changed in: gnome-orca (Ubuntu)
Status: Confirmed = Triaged
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script
This bug was fixed in the package gnome-orca - 2.30.0-0ubuntu3
---
gnome-orca (2.30.0-0ubuntu3) lucid; urgency=low
* debian/patches/08_orca_kill_speechd.patch: If speech-dispatcher is running,
forcefully kill it. Orca will reload it when needed. This is to solve the
problem
Luke, related with accessibility settings synchronisation during
installation:
I am very sorry, but unfortunately only entire tuesday I possible work
on the related need fixes with casper ubiquity-hooks/30accessibility
script, because wednesday I not in home entire day, and if I known
right,
** Package changed: speech-dispatcher (Ubuntu) = gnome-orca (Ubuntu)
** Changed in: gnome-orca (Ubuntu)
Status: Triaged = In Progress
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
This bug was fixed in the package gnome-orca - 2.30.0-0ubuntu2
---
gnome-orca (2.30.0-0ubuntu2) lucid; urgency=low
* debian/patches/08_orca_kill_speechd.patch: Rework to kill speech-dispatcher
whenever Orca is run as the gdm user, regardless of the command-line
arguments
Ok, the remaining problem in this bug is not something that should be
fixed in casper, it is a speech-dispatcher bug. I have some updates I
need to make to speech-dispatcher, so I can add this to the queue, which
I hope to have fixes uploaded for by the end of tomorrow my time.
affects
Thank you Luke, I accept this.
What happen with future with first created user accessibility settings
synchronisation with target system/etc/skel folder?
Please give me a correct fix method suggestion with Core developers sure
accept with this purpose with short time, because if accessible
This bug was fixed in the package casper - 1.231
---
casper (1.231) lucid; urgency=low
[ Jonathan Riddell ]
* Remove 37kubuntu_netbook_installer_link, now done with a patch in
kdebase-workspace
[ Colin Watson ]
* If copying live media to RAM or disk, explicitly copy
Luke, thank you apply my patch.
But now this final applyed patch not containing some importanter
modifications with fixing some Ubuntu-accessibility list described users
wroted problems and important fix with basic accessibility if v3 mode is
selected with official 10.04 Ubuntu release:
See my
** Branch linked: lp:ubuntu/casper
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are a member of Ubuntu
Bugs,
Now, have different situations with this step need or possible not need.
Luke, if we not copying .orca folder in /var/lib/gdm folder with target
system, if any user using for example a different voice speech person
because using different language, hear different voice the login screen
output
Alright, I'll get this in post beta 2, but longer term, we need to have
language detection for that stuff and have preferencres to set the gdm
settings.
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
Luke, thank you very mutch. Longer time, you are absolute right. If we
using now this patched method in Lucid, not producing problems.
Very interesting, GDM language is right (for example my system this is
hungarian.
You would like do your suggested fix with next Ubuntu developing cicle
Thanks for the patches, I will take a look later today.
Regarding the copying of the .orca directory to /var/lib/gdm, I have to
disagree with this. You may want to have the orca settings from the live
session available for login, however this is not very useful if a new
user is created, and they
Luke, Bill, I look the 2010-03-29 daily live CD with default access=v3
installation.
After installation is done, accessible login is work right after the
restart, except 30accessibility script is not copyed the .orca folder
with /var/lib/gdm folder in target system, but now this is known issue.
This is the modifyed .bash_logout and modifyed
/etc/gdm/PostSession/Default files.
Need put the modifyed .bash_logout file with target system new created
user home folder and target system/etc/skel folder, and need put the
Default file with target system/etc/gdm/PostSession folder to fix Jose
The prewious sent two attached file insertion is needed, because:
If any user setting a keybinding with kill X Server in
/system/preferences/keyboard preference tool, and press the setted key
binding (for example the Ctrl+Alt+Backspace), after the user choosing
what username would like login
I doed the final revision if not have another suggestion or request.
What changed?
Now, the patch is not used system vide GDM gconf setting method, using original
method.
The patch copying modifyed .orca folder with target system/var/lib/gdm folder.
The patch do need modifications with
Thanks, Attila! I'll add your patch to the buildvinuxiso script.
Bill
On Thu, Apr 1, 2010 at 12:02 PM, Attila Hammer hamm...@pickup.hu wrote:
I doed the final revision if not have another suggestion or request.
What changed?
Now, the patch is not used system vide GDM gconf setting method,
** Tags added: patch
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: This patch with this bugreport wroted problem with my tested
Lucid live CD.
http://launchpadlibrarian.net/42472643/30-accessibility-patch
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42471356/Dependencies.txt
--
[Lucid] need little modify the
Have you tried with the latest daily CD ISO? From what I've been told,
this issue should be fixed with the latest daily live CD.
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
I do a second revision.
Because now the 30accessibility script now not copying the .orca folder with
target system/var/lib/gdm folder, this is resulting some problems. The trivial
example is following:
For example, if a blind user using a notebook, when booting blindness profile
Hy Luke,
No, my custom live CD containing yesterday morning updates.
Just a moment, I downloading and look current daily live CD.
Your fix method using my first way patch system vide settings?
Or you use different method?
See my second patch revision with copying .orca folder with /var/lib/gdm
** Changed in: casper (Ubuntu)
Status: New = Confirmed
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part in Blindness profile
https://bugs.launchpad.net/bugs/551515
You received this bug notification because you are
Luke, what version casper source package containing your fix?
I install updates now my existing system, and upgraded casper and
ubiquity-casper version with 1.230 version.
When I look casper-1.230 source code, I not see any changes with related
this problem, or I not look enough detailed.
In
Luke, Bill Cox wroted me an ydea with related this bug:
He's ydea need copying the live user modifyed .orca folder with target
system/etc/skel folder. I absolute accept this ydea. If you accept this,
I do thursday or friday the needed patch modification, but before I
attaching the new revision,
I have not made any recent fixes to this at all. I am asking whether the
latest daily live CD still behaves incorrectly in regards to gdm
settings, and losing settings on upgrade.
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting
Ok, I understand.
I downloaded already the 2010-03-29 daily live Cd.
Tomorrow morning I look the original installation, and see what
happening when GDM is upgraded.
Attila
--
[Lucid] need little modify the ubiquity-hooks/30accessibility script with gdm
accessibility setting configuration part
Luke, yesterday Bill suggested need copying the live user .orca folder
in target system/etc/skel folder.
This is not problem, easy to do.
But, I think now original 30accessibility script is not copyed all
important another accessibility related settings to target system
/etc/skel folder if
35 matches
Mail list logo
