Xfce Forum

mattb

Member

Registered: 2023-02-21

Posts: 1

xfce4 per channel locking

Either this does not work or it is not intuitive how to make it work.

Am testing with XFCE in RHEL 9 from the EPEL repository (4.16).

Creating this file : /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-screensaver.xml

<?xml version="1.0" encoding="UTF-8"?>

<channel name="xfce4-screensaver" version="1.0" locked="*">
  <property name="saver" type="empty">
    <property name="mode" type="empty"/>
    <property name="fullscreen-inhibit" type="empty"/>
    <property name="enabled" type="bool" value="true"/>
  </property>
  <property name="lock" type="empty">
    <property name="saver-activation" type="empty">
      <property name="delay" type="empty"/>
    </property>
    <property name="enabled" type="empty"/>
  </property>
</channel>

.. results in a configuration that still permits the user to alter the given properties.  Is this broken in my version?

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 11,485

Re: xfce4 per channel locking

Hello and welcome.

I don't believe xfce4-screenaver supports kiosk mode, so the above config file won't work. And putting it in that location also won't work as be default, it will not be copied to a user's $XDG_CONFIG_DIR location on first use.

I'm unfamiliar with the specifics of RHEL, but in Arch, I can place a pre-configured version of the file in the correct path in /etc/skel and it will get copied to a new user's $XDG_CONFIG_DIR location. You can use this to set a default set of settings. These, however, can be overwritten by the user, so if you want to prevent that, you will need to hide the xfce4-screensaver-configure executable. Advanced users will still be able to make changes if they understand xfconf and adjust the xml file directly while not logged on to Xfce.

---

Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---