You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When configured & built with --prefix=/usr/local, polkitd from polkit-126 errors out with an assertion on startup (I reverted to polkit-125 for the time being, that's why I started it using LD_LIBRARY_PATH to make sure it's linking against its matching libs):
[root@disclosure:~/usrlocal/stow]# LD_LIBRARY_PATH=/usr/local/stow/polkit-126-@FDO/lib64 /usr/local/stow/polkit-126-@FDO/lib/polkit-1/polkitd
Successfully changed to user polkitd
20:49:19.783: Loading rules from directory /usr/local/etc/polkit-1/rules.d
20:49:19.784: Loading rules from directory /run/polkit-1/rules.d
20:49:19.784: Loading rules from directory /usr/local/share/polkit-1/rules.d
20:49:19.784: Loading rules from directory /usr/local/share/polkit-1/rules.d
**
ERROR:../src/polkitbackend/polkitbackendcommon.c:475:polkit_backend_common_rules_file_name_cmp: assertion failed: (ret != 0)
Bail out! ERROR:../src/polkitbackend/polkitbackendcommon.c:475:polkit_backend_common_rules_file_name_cmp: assertion failed: (ret != 0)
Aborted
If I interpret the corresponding code correctly, then this probably originates from
when trying to figure out which entry takes precedence, which is impossible when comparing two exactly identical entries.
Up to and including polkit-125, I used to build with meson setup --prefix=/usr/local -D js_engine=mozjs, and there were no duplicate path entries generated in
Additional context
As I said before, I built against mozjs in previous versions, which didn't exhibit this behavior, as it didn't create duplicate entries in rules_dirs.
There's no output in the logs except for the startup notification ("Jan 15 20:49:19 disclosure polkitd[20392]: Started polkitd version 126").
If you need any additional information, plesae let me know. Thanks for listening! 🙂
Thomas
The text was updated successfully, but these errors were encountered:
bob-beck
pushed a commit
to openbsd/ports
that referenced
this issue
Jan 17, 2025
Describe the bug
When configured & built with
--prefix=/usr/local
,polkitd
frompolkit-126
errors out with an assertion on startup (I reverted topolkit-125
for the time being, that's why I started it usingLD_LIBRARY_PATH
to make sure it's linking against its matching libs):If I interpret the corresponding code correctly, then this probably originates from
polkit/src/polkitbackend/polkitbackendduktapeauthority.c
Line 259 in 939c1a9
/usr/local/share/polkit-1/rules.d
gets added to the list ofrules_dirs
, leading to a duplicate path entry inpolkit/src/polkitbackend/polkitbackendduktapeauthority.c
Line 260 in 939c1a9
--prefix=/usr/local
, which ultimatelyassert()
s inpolkit/src/polkitbackend/polkitbackendcommon.c
Line 475 in 939c1a9
Up to and including
polkit-125
, I used to build withmeson setup --prefix=/usr/local -D js_engine=mozjs
, and there were no duplicate path entries generated inpolkit/src/polkitbackend/polkitbackendjsauthority.cpp
Lines 402 to 407 in 112752c
To Reproduce
Steps to reproduce the behavior:
polkit-126
withmeson setup --prefix=/usr/local
, then build as usual/usr/local
withninja install
polkitd
to be activated viad-bus
, or .../usr/local/lib/polkit-1/polkitd
Expected behavior
I expected
polkitd
to startup properly as usual, when built with-D js_engine=mozjs
in earlier versions. 🤷♂️ 😉Screenshots
N/A, see terminal output above.
Desktop (please complete the following information):
Additional context
As I said before, I built against
mozjs
in previous versions, which didn't exhibit this behavior, as it didn't create duplicate entries inrules_dirs
.There's no output in the logs except for the startup notification (
"Jan 15 20:49:19 disclosure polkitd[20392]: Started polkitd version 126"
).If you need any additional information, plesae let me know. Thanks for listening! 🙂
Thomas
The text was updated successfully, but these errors were encountered: