From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 48265@debbugs.gnu.org
Subject: bug#48265: mate-power-backlight-helper is referred to by store name instead of polkit action (IIUC)
Date: Thu, 06 May 2021 23:02:25 +0200 [thread overview]
Message-ID: <87a6p7d19a.fsf@gnu.org> (raw)
In-Reply-To: <28db052034ca1e3029bb3dc0aa9f87de2af6bdec.camel@telenet.be> (Maxime Devos's message of "Thu, 06 May 2021 22:24:43 +0200")
Hi!
Maxime Devos <maximedevos@telenet.be> skribis:
> FWIW, the following works as expected (no error message), using the store path in .policy:
> $ pkexec /gnu/store/zk4kb4437032swahywmgyzn55b5w5wj8-mate-power-manager-1.24.2/sbin/mate-power-backlight-helper --set-brightness=300
> Maybe MATE is trying the equivalent of "pkexec /wrong/store/path/mate-power-backlight-helper --etcetera" instead
> of referring to the action by name org.mate.power.backlight-helper.
>
> Note the store path is different. Now try something different
>
> $ which mate-power-backlight-helper
>> /run/current-system/profile/sbin/mate-power-backlight-helper
> $ ls -l /run/current-system/profile/sbin/mate-power-backlight-helper
>> /gnu/store/ffqhy4xdpzkg06rlq76zrbwn8v3rqgw9-mate-1.24.1/sbin/mate-power-backlight-helper
These are different versions (1.24.2 vs. 1.24.1). But that’s just two
store file names; where’s the third one?
Isn’t the problem that you reconfigured and so there’s now a mismatch
between the polkit rule in effect, which expects 1.24.1 (say), and the
version you’re running?
(FWIW brightness change works in GNOME.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-05-06 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 20:24 bug#48265: mate-power-backlight-helper is referred to by store name instead of polkit action (IIUC) Maxime Devos
2021-05-06 21:02 ` Ludovic Courtès [this message]
2021-05-06 21:18 ` Maxime Devos
2021-05-07 6:38 ` Maxime Devos
2021-05-07 6:48 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6p7d19a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48265@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).