This bug is not about afm-system-daemon but about trying to see what caused the problem, but you can't do that when afm-system-daemon is the one crashing at boot.
While installing homescreen wgt I got the following:
Then I decided to reboot the machine (not knowing what to do) which resulted in afm-system-daemon segfaulting. At this moment there's no "easy" way to see what caused as you can no longer login into the system.
Without booting with /bin/bash, mount manually partitions and figure out what caused it (if that is an option).
Environment
None
Attachments
1
Activity
Show:
Walt Miner
April 14, 2023 at 7:26 PM
App FW deprecated with Marlin release
jose bollo
May 18, 2020 at 2:18 PM
Off-line, it is possible to remove restart in the systemd service: Restart=no
Then getting a core file, a trace or other debugging output is possible.
The error reported by security-manager is strange and rare (I've not seen it before).
But it should not lead to a SEGV in afm-system-daemon. Even more after reboot. Knowing the reason is important.
Jan-Simon Moeller
May 18, 2020 at 12:39 PM
: This seems to happen on uninstall/install cycles.
Jan-Simon Moeller
May 10, 2020 at 11:06 PM
I've seen a similar issue when trying the test wgts.
Major
This bug is not about afm-system-daemon but about trying to see what caused the problem, but you can't do that when afm-system-daemon is the one crashing at boot.
While installing homescreen wgt I got the following:
Then I decided to reboot the machine (not knowing what to do) which resulted in afm-system-daemon segfaulting. At this moment there's no "easy" way to see what caused as you can no longer login into the system.
Without booting with /bin/bash, mount manually partitions and figure out what caused it (if that is an option).