Bloodfire Comments - Answer Overflow

systemctl status sssd
● sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (running) since Wed 2025-01-15 13:20:11 EST; 10min ago

systemctl status sssd
● sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (running) since Wed 2025-01-15 13:20:11 EST; 10min ago

23 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

OSTREE_VERSION='41.20250115.0'
BUILD_ID="Testing (F41.20250115, #9665cbc)"
BOOTLOADER_NAME="Bazzite Testing (F41.20250115, #9665cbc)"

OSTREE_VERSION='41.20250115.0'
BUILD_ID="Testing (F41.20250115, #9665cbc)"
BOOTLOADER_NAME="Bazzite Testing (F41.20250115, #9665cbc)"

23 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

did not work but i see a new merge went into rechunk that address version detection fixes

23 replies

UBUniversal Blue

•Created by Tsubajashi (ツバジャシ) on 1/9/2025 in #🛟bazzite-help

cockpit default port

your screenshot shows that you used port 7070 instead of 9090 for 127.0.0.1 The IP used for the other section of the screenshot does not match a private IP, but rather a public IP. You need to use your private IP or apply port forwarding through your router (hella unsafe, do not recommend).

14 replies

UBUniversal Blue

•Created by Tsubajashi (ツバジャシ) on 1/9/2025 in #🛟bazzite-help

cockpit default port

I had to open up any ports I needed... including 7860, and 7860 > 1024 so... though tbf I have custom firewall rules, so probably not a fair comparison. I guess it depends on if they're using the FedoraWorkstation zone or not, if that's not the active zone then they have to open the port. Once again, easy way to tell using the first command I listed above...

14 replies

UBUniversal Blue

•Created by Tsubajashi (ツバジャシ) on 1/9/2025 in #🛟bazzite-help

cockpit default port

if it's not open:

firewall-cmd --add-port=9090/tcp --permanent

firewall-cmd --add-port=9090/tcp --permanent

14 replies

UBUniversal Blue

•Created by Tsubajashi (ツバジャシ) on 1/9/2025 in #🛟bazzite-help

cockpit default port

firewall-cmd --list-all

firewall-cmd --list-all

14 replies

UBUniversal Blue

•Created by Tsubajashi (ツバジャシ) on 1/9/2025 in #🛟bazzite-help

cockpit default port

Did you open the port in your firewall?

14 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

ok I'll rebase to testing after work unless new stable is released prior haha

23 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

as of 41.20250106.2 it was still bork bork by the way. Is the build bot not upstream change aware? Feels like a trigger is not in place if that's the issue.

23 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

Hello again @antheas thanks so much for your work last week on that PR 🙂

23 replies

UBUniversal Blue

•Created by Bloodfire on 1/9/2025 in #🛟bazzite-help

SSSD broken, unable to login since capabilities changes made to sssd-2.10.1

Hoping posting it in the discord will increase visibility, referencing appropriate bazzite github issues pages to make it easier 🙂

23 replies

Gaming

Programming