schema override #9

New issue

Closed

opened 2016-01-22 15:12:34 +00:00 by philm · 3 comments

philm commented

2016-01-22 15:12:34 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Is there an order for sections and keys to keep?
Does somebody know?

I don't get mate or gnome to talk in sonar, but accessibility is nicely activated as separate menu.

*Created by: udeved* Is there an order for sections and keys to keep? Does somebody know? I don't get mate or gnome to talk in sonar, but accessibility is nicely activated as separate menu.

oberon commented

2016-01-22 15:14:31 +00:00

(Migrated from gitlab2.manjaro.org)

I think the order doesn't matter.

philm commented

2016-01-22 15:16:03 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: udeved

Hmm, perhaps we got to play around with the weighting of the override, even though its already highest with 99.
Some sonar settings don't get activated by default.

*Created by: udeved* Hmm, perhaps we got to play around with the weighting of the override, even though its already highest with 99. Some sonar settings don't get activated by default.

philm commented

2016-01-23 13:58:03 +00:00

(Migrated from gitlab2.manjaro.org)

Created by: ringo32

mayby is 99 To high :) if you plan a livecd gschema like to make lock screen work at first hand... lockely in livecd lockscreen works... so it stil enabled to go intoo lock..

99 get to high on number, likely a gschema for a livesession need a higher number to disable lockscreen as example

*Created by: ringo32* mayby is 99 To high :) if you plan a livecd gschema like to make lock screen work at first hand... lockely in livecd lockscreen works... so it stil enabled to go intoo lock.. 99 get to high on number, likely a gschema for a livesession need a higher number to disable lockscreen as example