Re: [orca-list] removal of orca's .desktop file could potentially break mate

[Luke Yelavich <luke yelavich canonical com>]

On Thu, Jul 21, 2016 at 09:14:14AM AEST, kendell clark wrote:
> hi all
> Latest orca master removes orca's .desktop file since gnome and unity
> don't need it. But this could, I'm not positive yet, break mate's
> ability to start it when it's accessibility settings are enabled.

On Thu, Jul 21, 2016 at 09:14:14AM AEST, kendell clark wrote:
> hi all
> Latest orca master removes orca's .desktop file since gnome and unity
> don't need it. But this could, I'm not positive yet, break mate's
> ability to start it when it's accessibility settings are enabled.

This reminded me that I needed to look into how Mate started assistive 
technologies because when I was messing with Mate 1.8, it didn't seem to do 
things the same as GNOME has done for a while, but it appears as of 1.14.0, 
Mate session manager essentially does the same thing as GNOME's session 
manager, which is to read in the desktop files in /etc/xdg/autostart, and act 
on them accordingly. In the case of Orca's autostart file, the desktop file 
for Orca has a statement to tell the session manager to start Orca whenever 
the GSettings key screen-reader-enabled in the schema 
org.gnome.desktop.a11y.applications is set to true. Likewise, the session 
manager kills orca if that key is set to false. This is essentially what the 
keyboard shortcut does, and 
mate-settings-daemon/gnome-settings-daemon/unity-settings-daemon listen for 
the shortcut, and when its pressed, flip the associated settings key, which 
the session manager picks up on and acts appropriately.

On Thu, Jul 21, 2016 at 09:14:14AM AEST, kendell clark wrote:
> hi all
> Latest orca master removes orca's .desktop file since gnome and unity
> don't need it. But this could, I'm not positive yet, break mate's
> ability to start it when it's accessibility settings are enabled.

On Thu, Jul 21, 2016 at 09:14:14AM AEST, kendell clark wrote:
> hi all
> Latest orca master removes orca's .desktop file since gnome and unity
> don't need it. But this could, I'm not positive yet, break mate's
> ability to start it when it's accessibility settings are enabled.

This reminded me that I needed to look into how Mate started assistive 
technologies because when I was messing with Mate 1.8, it didn't seem to do 
things the same as GNOME has done for a while, but it appears as of 1.14.0, 
Mate session manager essentially does the same thing as GNOME's session 
manager, which is to read in the desktop files in /etc/xdg/autostart, and act 
on them accordingly. In the case of Orca's autostart file, the desktop file 
for Orca has a statement to tell the session manager to start Orca whenever 
the GSettings key screen-reader-enabled in the schema 
org.gnome.desktop.a11y.applications is set to true. Likewise, the session 
manager kills orca if that key is set to false. This is essentially what the 
keyboard shortcut does, and 
mate-settings-daemon/gnome-settings-daemon/unity-settings-daemon listen for 
the shortcut, and when its pressed, flip the associated settings key, which 
the session manager picks up on and acts appropriately.

This is a long handed way to say that the desktop file that has been removed 
from Orca master is not needed for Mate.

Luke