Re: KDE - How to disable the Switch User and Lock in Leave Menu ?

2018-03-12 Thread Kevin Krammer
Hi,

On Freitag, 9. März 2018 21:55:52 CET Zaiwen Gong wrote:
> Hi,
> 
> I am using KDE 4.10.
> 
> I would like to find out how to disable the Switch User and Lock in
> Leave Menu.
> 
> I don't want to disable Switch User and Lock button in the Leave Menu at
> system level.
> 
> Instead, I would like to do it at user level. That is, I would like to
> configure a special user's .kde/share/config file and when this special
> user logins, he will not see the Switch User and Lock button in the
> Leave Menu.
> 
> I tried to put below contents in .kde/share/config/kdeglobals of
> intended user.

You could also try ksmserverrc or plasmarc

Also consider asking at the KDE Enterprise mailinglist

https://mail.kde.org/mailman/listinfo/enterprise

It is used by sysadmins who manage KDE deployments and often discuss action 
restrictions.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


signature.asc
Description: This is a digitally signed message part.


Re: Put all KDE config files under one directory like ~/.config/kde/

2018-03-12 Thread Kevin Krammer
On Montag, 12. März 2018 06:33:42 CET stardiviner wrote:
> I found KDE put all components config files under ~/.config/.
> Because there are lot of configs of KDE, and lot of programs configs
> under it.
> When I want to do something (like reset KDE configs) I don't know which
> ones need to delete.
> Put all KDE related config files under ~/.config/kde/ will help user.

It seems that at some point there was a .config/kde.org "vendor" directory, but 
indeed most configs are at the top level nowadays.

I would suggest to file a wish item ticket on bugs.kde.org

Unfortunately changing file locations is a bit problematic, as moving the file 
means an older version won't find it anymore and copying means they easily get 
out of sync.

But it does sound like a good idea to have each vendor use a directory of its 
own.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring


signature.asc
Description: This is a digitally signed message part.


Re: Put all KDE config files under one directory like ~/.config/kde/

2018-03-12 Thread René J . V . Bertin
How long have you been using Linux and/or Unix systems?

Before the Freedesktop.org standard everyone put their config and other 
user-specific resource stuff in a place of their choosing, typically directly 
into $HOME or if you were lucky, in a dedicated subdirectory under $HOME (e.g.: 
~/.ssh).

To extrapolate your argument a bit: don't you think that /usr/bin is an even 
worse total mess? Everything ends up being installed there

Morale: storing settings files of an entire software family will always remain 
a mess. This may be why Gnome/GTk use a database (or at least provide a 
database-like central interface to the settings repository). And you only have 
to look at the MS Windows registry to know what an incredible mess such a thing 
can become.

The best way to figure out which settings file you're looking for is to look at 
the file date. And if you want them all in one place you should be able to do 
that with a simple change (maybe even a configure option) to one of the 
frameworks. Certain distributions did that so KDE4 stuff was under ~/.kde4 
instead of ~/.kde .

Doing this upstream would force the decision upon everyone, with all the 
resulting maintenance costs (each and every application will have to ensure 
their settings are migrated properly and even then some users may find that 
they lost their settings). That's not a decision the core devs will make 
lightly, or so I hope.

R.


Re: KDE - How to disable the Switch User and Lock in Leave Menu ?

2018-03-12 Thread Zaiwen Gong

Hi Kevin,

Thank you very much for the reply.

I tried several files (kdeglobals, ksmserverrc, plasma-desktoprc, 
plasma-desktop-appletsrc) with two formats, but none is working.


   [KDE Action Restrictions][$i]
   action/switch_user=false
   action/start_new_session=false


   [KDE Action Restrictions]
   lock_session=false
   switch_user=false

I will ask at the KDE Enterprise mailing list.

||

Thanks,

Zaiwen


On 03/12/18 05:05, Kevin Krammer wrote:

Hi,

On Freitag, 9. März 2018 21:55:52 CET Zaiwen Gong wrote:

Hi,

I am using KDE 4.10.

I would like to find out how to disable the Switch User and Lock in
Leave Menu.

I don't want to disable Switch User and Lock button in the Leave Menu at
system level.

Instead, I would like to do it at user level. That is, I would like to
configure a special user's .kde/share/config file and when this special
user logins, he will not see the Switch User and Lock button in the
Leave Menu.

I tried to put below contents in .kde/share/config/kdeglobals of
intended user.

You could also try ksmserverrc or plasmarc

Also consider asking at the KDE Enterprise mailinglist

https://mail.kde.org/mailman/listinfo/enterprise

It is used by sysadmins who manage KDE deployments and often discuss action
restrictions.

Cheers,
Kevin




Re: Put all KDE config files under one directory like ~/.config/kde/

2018-03-12 Thread stardiviner
I see. you mentioned problem indeed. I will consider find file based on 
modified timestamp.



On 03/12/2018 05:17 PM, Kevin Krammer wrote:

On Montag, 12. März 2018 06:33:42 CET stardiviner wrote:

I found KDE put all components config files under ~/.config/.
Because there are lot of configs of KDE, and lot of programs configs
under it.
When I want to do something (like reset KDE configs) I don't know which
ones need to delete.
Put all KDE related config files under ~/.config/kde/ will help user.

It seems that at some point there was a .config/kde.org "vendor" directory, but
indeed most configs are at the top level nowadays.

I would suggest to file a wish item ticket on bugs.kde.org

Unfortunately changing file locations is a bit problematic, as moving the file
means an older version won't find it anymore and copying means they easily get
out of sync.

But it does sound like a good idea to have each vendor use a directory of its
own.

Cheers,
Kevin