Cannot start the cinnamon session when restarting my computer

[Titanet]

What happened?

From my Journalctl log :

ov. 09 16:09:28 msi-x370 portmaster-start[905]: [pmstart] 2024/11/09 15:09:28 got terminated signal (ignoring), waiting for child to exit...
nov. 09 16:09:28 msi-x370 portmaster-start[905]:
nov. 09 16:09:28 msi-x370 portmaster-start[905]: 241109 16:09:28.388 5/run/main:085 ▶ WARN 049 main: program was interrupted, shutting down.
nov. 09 16:09:28 msi-x370 systemd[1]: Stopping Portmaster by Safing...
nov. 09 16:09:28 msi-x370 systemd[1]: avahi-daemon.service: Deactivated successfully.
nov. 09 16:09:28 msi-x370 NetworkManager[893]: [1731164968.4045] exiting (success)
nov. 09 16:09:28 msi-x370 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
nov. 09 16:09:28 msi-x370 systemd[1]: NetworkManager.service: Deactivated successfully.
nov. 09 16:09:28 msi-x370 network[3847]: Stopping network profile 'bridge'...
nov. 09 16:09:28 msi-x370 systemd[1]: Stopped Network Manager.
nov. 09 16:09:28 msi-x370 kernel: br0: port 1(eno1) entered disabled state
nov. 09 16:09:28 msi-x370 dbus-broker-launch[885]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
nov. 09 16:09:28 msi-x370 kernel: igb 0000:21:00.0 eno1: left allmulticast mode
nov. 09 16:09:28 msi-x370 kernel: igb 0000:21:00.0 eno1: left promiscuous mode
nov. 09 16:09:28 msi-x370 kernel: br0: port 1(eno1) entered disabled state
nov. 09 16:09:28 msi-x370 portmaster-start[905]: 241109 16:09:28.489 dules/stop:057 ▶ WARN 051 modules: starting shutdown...
nov. 09 16:09:28 msi-x370 systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-hostnamed.service/start is destructive (systemd-update-utmp.service has 'stop' job queued, but 'start' is included in transaction).
nov. 09 16:09:28 msi-x370 hostnamectl[3876]: Could not get property: Could not activate remote peer 'org.freedesktop.hostname1': activation request failed: a concurrent deactivation request is already in progress
nov. 09 16:09:28 msi-x370 portmaster-start[905]: 241109 16:09:28.749 ◀ EOF
nov. 09 16:09:28 msi-x370 portmaster-start[905]: [pmstart] 2024/11/09 15:09:28 core/portmaster-core exited without error
nov. 09 16:09:28 msi-x370 network[3847]: Stopped network profile 'bridge'
nov. 09 16:09:28 msi-x370 systemd[1]: [email protected]: Deactivated successfully.
nov. 09 16:09:28 msi-x370 systemd[1]: Stopped Bridge eno1.
nov. 09 16:09:28 msi-x370 systemd[1]: portmaster.service: Deactivated successfully.
nov. 09 16:09:28 msi-x370 systemd[1]: Stopped Portmaster by Safing.
nov. 09 16:09:28 msi-x370 systemd[1]: portmaster.service: Consumed 1.971s CPU time, 263.3M memory peak.

What did you expect to happen?

How did you reproduce it?

Additional information

I didn't have this problem the days before November 9.
I had to disable the service Portmaster to be able to start my cinnamon session.

Debug-Info: https://support.safing.io/privatebin/?1d9724b827422797#4ZAmXMNUbdx2nfitmdmg1sdN8RxWLpgptjMxxChgeoap

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[Nextnx]

You'll need to disable portmaster then reboot to login. Then after login start portmaster, now allow in global "::1" and "Localhost" as incoming and possible outgoing as well. Before "Localhost" was enough but something changed.

Black/hanging at login in cinnamon still happens from time to time, where you have to tty and reboot then all is fine again.

Also at startup after login sometimes filter rules guessing might be partial broken where you need restart core again else some sockets might be blocked and nothing shows in UI, all green. E.g. where browser might work and Discord can start and join channels but speak/RTC will not connect. Not sure if that is related to the systemd launch order or conflicts herein.

[dhaavi]

Hey @Titanet and @Nextnx, thanks for reporting and chiming in.

We've experienced this before, but I am currently not able to reproduce this.
Please try out if this works in Beta, here is how you can switch: https://wiki.safing.io/en/FAQ/SwitchReleaseChannel

[Titanet]

After following your advice and modifying the configuration in Incoming rules, the Cinnamon session launch works again, thank you.

[dhaavi]

Great! Thanks a lot for reporting back.