What will be the difference from Workstation at that point?

K

Kasher_CS•6/29/24, 3:05 PM

This isn't a problem with the partition in this case

Z

Zeglius•6/29/24, 3:06 PM

so, Bazzite is supposed to rely in setroubeshootd for SELinux? Because I noticed this

Z

Zeglius•6/29/24, 3:06 PM

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

○ setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs
     Loaded: loaded (/usr/lib/systemd/system/setroubleshootd.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/setroubleshoot_database.xml [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/setroubleshoot_database.xml to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/setroubleshoot_database.xml to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot create file /var/lib/setroubleshoot/email_alert_recipients [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chmod /var/lib/setroubleshoot/email_alert_recipients to 600 [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: cannot chown /var/lib/setroubleshoot/email_alert_recipients to setroubleshoot:setroubleshoot [No such file or directory]
jun 29 16:54:45 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora setroubleshoot[10540]: could not write /var/lib/setroubleshoot/setroubleshoot_database.xml: [Errno 2] No such file or directory: '/var/lib/setroubleshoot/setroubleshoot_database.xml'
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Deactivated successfully.
jun 29 16:54:59 fedora systemd[1]: setroubleshootd.service: Consumed 1.365s CPU time.

Z

Zeglius•6/29/24, 3:07 PM

seems the selinux troubleshooter is kneecapped by selinux itself

KKasher_CS This isn't a problem with the partition in this case

B

byeproduct•6/29/24, 3:12 PM

If its not a problem, is there anything else I can try?

ZZeglius seems the selinux troubleshooter is kneecapped by selinux itself 😂

M

M2•6/29/24, 3:13 PM

It doesn't create /var/lib/setroubleshoot so it freaks out

Z

Zeglius•6/29/24, 3:13 PM

Yeah can see that

Z

Zeglius•6/29/24, 3:17 PM

rather cant touch anything at /var/lib/setroubleshoot ( that after

 mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

 mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml

mkdir -p /var/lib/setroubleshoot/; touch /var/lib/setroubleshoot/setroubleshoot_database.xml)

A

antheas•6/29/24, 3:19 PM

xwayland is not x11

A

antheas•6/29/24, 3:19 PM

its not going away

A

antheas•6/29/24, 3:19 PM

its perfectly fine to use xwayland right now, apart from fractional scaling

A

antheas•6/29/24, 3:19 PM

which looks like garbage on x11 apps

Z

Zeglius•6/29/24, 3:21 PM

Hmm seems

sudo restorecon -rv /var/lib/setroubleshoot

sudo restorecon -rv /var/lib/setroubleshoot

sudo restorecon -rv /var/lib/setroubleshoot

sudo restorecon -rv /var/lib/setroubleshoot didnt fix it

Bbyeproduct If its not a problem, is there anything else I can try?

K

Kasher_CS•6/29/24, 3:23 PM

Check with your adapter is what I say, the partition manager should list your partitions fine

Aantheas its perfectly fine to use xwayland right now, apart from fractional scaling

H

halva•6/29/24, 3:24 PM

~~honestly probably "mandatory for non-qt/gtk things" than "fine"~~

H

halva•6/29/24, 3:24 PM

it's probably here to stay like multilib lmao

H

halva•6/29/24, 3:25 PM

wouldnt be surprised if a certain valve company will keep clinging to x11 for their client until it's physically impossible for it to function

ZZeglius Hmm seems `sudo restorecon -rv /var/lib/setroubleshoot` didnt fix it

A

antheas•6/29/24, 3:26 PM

did you rebase from kinoite?

Aantheas did you rebase from kinoite?

Z

Zeglius•6/29/24, 3:27 PM

yep

A

antheas•6/29/24, 3:27 PM

yea one of the bugs i found during rechunking bazzite is that

A

antheas•6/29/24, 3:27 PM

if you rebase you lose the setroubleshoot user

A

antheas•6/29/24, 3:27 PM

Appending the following passwd users to /usr/lib/passwd
clevis:x:992:964:Clevis Decryption Framework unprivileged user:/var/cache/clevis:/usr/sbin/nologin
setroubleshoot:x:976:963:SELinux troubleshoot server:/var/lib/setroubleshoot:/usr/sbin/nologin
wsdd:x:975:962:Web Services Dynamic Discovery host daemon:/:/sbin/nologin

Appending the following group entries to /usr/lib/group
adbusers:x:966:
plugdev:x:965:
clevis:x:964:
setroubleshoot:x:963:
wsdd:x:962:

Appending the following passwd users to /usr/lib/passwd
clevis:x:992:964:Clevis Decryption Framework unprivileged user:/var/cache/clevis:/usr/sbin/nologin
setroubleshoot:x:976:963:SELinux troubleshoot server:/var/lib/setroubleshoot:/usr/sbin/nologin
wsdd:x:975:962:Web Services Dynamic Discovery host daemon:/:/sbin/nologin

Appending the following group entries to /usr/lib/group
adbusers:x:966:
plugdev:x:965:
clevis:x:964:
setroubleshoot:x:963:
wsdd:x:962:

Appending the following passwd users to /usr/lib/passwd
clevis:x:992:964:Clevis Decryption Framework unprivileged user:/var/cache/clevis:/usr/sbin/nologin
setroubleshoot:x:976:963:SELinux troubleshoot server:/var/lib/setroubleshoot:/usr/sbin/nologin
wsdd:x:975:962:Web Services Dynamic Discovery host daemon:/:/sbin/nologin

Appending the following group entries to /usr/lib/group
adbusers:x:966:
plugdev:x:965:
clevis:x:964:
setroubleshoot:x:963:
wsdd:x:962:

Appending the following passwd users to /usr/lib/passwd
clevis:x:992:964:Clevis Decryption Framework unprivileged user:/var/cache/clevis:/usr/sbin/nologin
setroubleshoot:x:976:963:SELinux troubleshoot server:/var/lib/setroubleshoot:/usr/sbin/nologin
wsdd:x:975:962:Web Services Dynamic Discovery host daemon:/:/sbin/nologin

Appending the following group entries to /usr/lib/group
adbusers:x:966:
plugdev:x:965:
clevis:x:964:
setroubleshoot:x:963:
wsdd:x:962:

A

antheas•6/29/24, 3:27 PM

this is what should happen and didnt

Z

Zeglius•6/29/24, 3:28 PM

can be done manually i guess?

A

antheas•6/29/24, 3:28 PM

if you install bazzite with the ISO, these are added to the initial passwd and group files

A

antheas•6/29/24, 3:28 PM

if you rebase from kinoite no

V

VAtrick•6/29/24, 3:28 PM

Hello I got a little question here, are there any security concerns about bazzite os or is it as secure as fedora silverblue?

KKasher_CS Check with your adapter is what I say, the partition manager should list your pa...

B

byeproduct•6/29/24, 3:28 PM

Awesome. Shot. I'll try another adaptor. Thanks

A

antheas•6/29/24, 3:28 PM

add them to /etc/passwd /etc/group

A

antheas•6/29/24, 3:28 PM

since you cant write to the lib files

K

Kasher_CS•6/29/24, 3:29 PM

Why is my clevis IDs different

A

antheas•6/29/24, 3:29 PM

probably clevis recreated the user

A

antheas•6/29/24, 3:29 PM

with a different id

K

Kasher_CS•6/29/24, 3:30 PM

And setrobleshoot

A

antheas•6/29/24, 3:30 PM

add the missing ones

A

antheas•6/29/24, 3:30 PM

if there are any missing

K

Kasher_CS•6/29/24, 3:31 PM

Just the groups I think

Aantheas add them to /etc/passwd /etc/group

Z

Zeglius•6/29/24, 3:32 PM

Now that I checked, it seems i had those beforehand(?)

K

Kasher_CS•6/29/24, 3:32 PM

Yeah the groups are there too

K

Kasher_CS•6/29/24, 3:32 PM

Very strange

A

antheas•6/29/24, 3:33 PM

if they are they got autoadded

A

antheas•6/29/24, 3:33 PM

but its one of the potential issues i found

K

Kasher_CS•6/29/24, 3:36 PM

What's the permissions on /var/lib/setroubleshoot?

K

Kasher_CS•6/29/24, 3:37 PM

Actually I have this bluefin vm right here I can check

K

Kasher_CS•6/29/24, 3:37 PM

wait its not there

Z

Zeglius•6/29/24, 3:37 PM

Yeah

Z

Zeglius•6/29/24, 3:37 PM

literally, selinux doesnt even let create the directory

Z

Zeglius•6/29/24, 3:38 PM

I mean using sudo I can

Z

Zeglius•6/29/24, 3:38 PM

but not setroubleshootd

K

Kasher_CS•6/29/24, 3:38 PM

Doesn't run on the bluefin vm either?

What will be the difference from Workstation at that point?

Similar Threads

Similar Threads

Similar Threads