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

A solution related to Orca and aplication executed as a root user



Dear core developers,
 
While i have intensively tested Yours first Alpha 1 release of Debian Squeeze, i started to think about realistic solution, which would enable users of Debian live Gnome to use applications with The root privileges with Orca and other related at-spi assistive technology.
Here is my constructive suggestion.
 
I Am looking forward to a discussion with us.
1. Use existing code build in The su-to-root script.
Several lines should be copied to The every Bash shell script, which are being responsible for launching Gparted and other applications. Todays issue is, that su-to-root -c gparted
Can be used only from Gnome-terminal or from The run application dialog window of Gnome. And if using from this run dialog window, i must press The toggle button which will enable me to combine two commands, su-to-root -c gparted.
Triing to edit main menu, administration sub menu and triing to edit The startup command for Gparted is not good idea. GNome algorithms will not allow me to execute two command at The same line. Only when executing Bash shell script from Nautilus or while recalling run application dialog window.
This problem is also The cause of problems with Debian live installer desktop link. In The debian Alpha squeeze.
In Alpha 1 release, i could login and logout as root and if i logged as root user and when i have performed all Orca setup questions, i could use Orca as a root user also after system restart.
Thank's to this ammazing setting, The code inside su-to-root script can be used for launching administration applications including synaptic package manager. If user is logged as a non root user and if su-to-root -c synaptic
command is specified from Gnome-terminal or from The run application dialog window in Gnome.
Conclusions.
1. Gksu script can not enable users of at-spi assistive technology to use administration applications, eventhough Orca configuration is stored in The right place and eventhough Orca can be usable while using root user account.
 
But issue is:
How complex would be for You to include those Orca settings for root user account to squash image?
 
Which command can be used for adding, removing or renaming files stored in The The squash files?
 
 

Reply to: