[Xfce-bugs] [Bug 11784] New: A new property - LockCommand

[b***@xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=11784

Bug ID: 11784
Summary: A new property - LockCommand
Classification: Xfce
Product: Xfce4-session
Version: 4.12.0
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: Medium
Component: General
Assignee: xfce-***@xfce.org
Reporter: ***@gmail.com
QA Contact: ***@cornell.edu
CC: ***@xfce.org, ***@xfce.org

Created attachment 6156
--> https://bugzilla.xfce.org/attachment.cgi?id=6156&action=edit
Create a new property "/general/LockCommand" on channel "xfce4-session"

$ xflock4
Property "/general/LockCommand" does not exist on channel "xfce4-session".

[b***@xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=11784

Eric Koegel <***@xfce.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |***@xfce.org
Resolution|--- |FIXED

--- Comment #1 from Eric Koegel <***@xfce.org> ---
Thanks, pushed to master in:
commit 570093ffafa8a6226ce9dd0ee29e9e64539d4bc9
Author: Eric Koegel <***@gmail.com>
Date: Sun Apr 5 18:24:49 2015 +0300

Create a new property on channel (Bug #11784)

This prevents the warning: "Property "/general/LockCommand" does
not exist on channel "xfce4-session"." Bug report and patch
provided by poma.
http://git.xfce.org/xfce/xfce4-session/commit/?id=570093ffafa8a6226ce9dd0ee29e9e64539d4bc9

In the future, if you want you can submit the patches in git format. That way
you get full credit for your work!

[b***@xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=11784

edwardo <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #2 from edwardo <***@gmail.com> ---
I tried to add <property name="LockCommand" type="string" value=""/> to both

/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml

without success (I still get "/general/LockCommand does not exist")

Is it expected ? i.e. does the fix affect the build -- hence I have to wait for
updated package builds for my distro (Fedora 22 beta) --, or am I just
modifying the wrong files ?

[b***@xfce.org]

https://bugzilla.xfce.org/show_bug.cgi?id=11784

--- Comment #3 from Eric Koegel <***@xfce.org> ---
running from the command line:
xfconf-query -c xfce4-session -p /general/LockCommand -s ""

should also prevent the popup while still allowing the defaults.