Nemesis 2022 rebooted!

Arch based Porteus community project

Moderator: M. Eerie

gnintilgyes
Black ninja
Black ninja
Posts: 73
Joined: 14 Sep 2022, 17:52
Distribution: Debian

Nemesis 2022 rebooted!

Post#31 by gnintilgyes » 22 Nov 2022, 22:46

My Nemesis installation got corrupted... had to erase the USB disk that it was on, and right now I don't have another candidate. I haven't officially given up on it, maybe I could just use it like I have with Porteus, with "static" XZM files and keeping totally offline. OTOH I desired to help with bug reports and the like.

If I recall correctly the "/config" was both with "/boot" and with "/porteus", ie. in two different partitions. But the "/etc/porteus.d" remained empty. Not that it matters a lot now because I have to try again later to install.

User avatar
M. Eerie
Moderator
Moderator
Posts: 620
Joined: 31 Aug 2017, 21:18
Distribution: Nemesis Xfce/MATE x64

Nemesis 2022 rebooted!

Post#32 by M. Eerie » 11 May 2023, 20:26

ncmprhnsbl wrote:
04 Nov 2022, 01:49
we have /etc/polkit-1/rules.d/49-rootpw_global.rules :
This is from some months ago...

Luckily, I have found this in /var/log/everything.log:

"
...
May 9 13:02:52 localhost polkitd[4424]: Loading rules from directory /etc/polkit-1/rules.d
May 9 13:02:52 localhost polkitd[4424]: Error opening rules directory: Error opening directory “/etc/polkit-1/rules.d”: Permission denied (g-file-error-quark, 2)
May 9 13:02:52 localhost polkitd[4424]: Loading rules from directory /usr/share/polkit-1/rules.d
...
"

Then, I looked for the permissions of the folder:

Code: Select all

nemesis:Desktop # ls -ldZ /etc/polkit-1/rules.d
drwxr-x--- 2 root root ? 43 Feb 20  2019 /etc/polkit-1/rules.d/                                         <-- root:root
nemesis:Desktop # ls -ldZ /usr/share/polkit-1/rules.d
drwxr-x--- 2 root polkitd ? 56 May  8 13:13 /usr/share/polkit-1/rules.d/                           <-- root:polkitd
nemesis:Desktop #
When I do a live system update, the administrative tasks are controlled by the user of the "wheel" group. That is, when an administrative action is required, the valid password is no longer root, but the one of the active user.

Shouldn't /usr/share/polkit-1 be the default location? Why is this happening? Are we mixing rules from different packages?

Does it happen to anyone else??


EDIT: There seems to be more people who have had the same thing happen, albeit on systems that launch their services with systemd instead of openrc.
> Does not compute_ 🖖

https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3924
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Nemesis 2022 rebooted!

Post#33 by ncmprhnsbl » 03 Jun 2023, 04:13

M. Eerie wrote:
11 May 2023, 20:26
Shouldn't /usr/share/polkit-1 be the default location?
/etc/polkit-1/rules.d/ should be fine, in fact the polkit package ships with it's 50-default.rules there (an artix thing apparently, the arch package has it in /usr/share)
now i see that build process is messing up the owner/permissions of /etc/polkit-1/rules.d/ which should be: user:polkitd group: polkitd 700 ...but it doesn't seem to a problem (been like this in slackware porteus for who knows how long, too)
i've now fixed this for the next release, but this probly isn't the cause of your anomaly ... the permission denied thing is very strange..

interestingly, slackware has a "dont-set-wheel-group-as-admin.diff.gz" patch for it's polkit package which sets "unix-user:root" instead of "unix-group:wheel" ..
weirdly, i havn't experienced any effect such as you have .. it's like something about your upgrade process is causing 50-default.rules to override 49-rootpw_global.rules ...
in any case, i'll hack 50-default.rules slackware style (and probly won't need 49-rootpw_global.rules) in the build from now on. (or even just delete 50-default.rules)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply