I saw the error message from the headline of this bug report in /var/log/apport.log:
ERROR: apport (pid 27563) Mon Mar 28 11:45:22 2022: called for pid 1770, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: executable: /usr/bin/xfce4-power-manager (command line "xfce4-power-manager")
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: debug: session gdbus call:
ERROR: apport (pid 27563) Mon Mar 28 11:45:24 2022: wrote report /var/crash/_usr_bin_xfce4-power-manager.1000.crash
This occurred on a special installation on my "yellow" USB3 stick (instead of the built-in SSD) that I have made for maintenance purposes.
Do I need to worry about the error message?
Is it possible that this is why the boot process from the stick takes so long?
Trying to find the reason why the boot process takes 2:45 minutes with the screen being black for 1:30 minutes was the reason for me to look for error messages in `/var/log` and on this occasion I came across the error message.
Today, on my Xubuntu system
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
5.13.0-37-generic x86_64
I saw the error message from the headline of this bug report in /var/log/ apport. log:
ERROR: apport (pid 27563) Mon Mar 28 11:45:22 2022: called for pid 1770, signal 11, core limit 0, dump mode 1 xfce4-power- manager (command line "xfce4- power-manager" ) org.freedesktop .DBus.Error. ServiceUnknown: The name org.gnome. SessionManager was not provided by any .service files
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: executable: /usr/bin/
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: gdbus call error: Error: GDBus.Error:
ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: debug: session gdbus call: _usr_bin_ xfce4-power- manager. 1000.crash
ERROR: apport (pid 27563) Mon Mar 28 11:45:24 2022: wrote report /var/crash/
This occurred on a special installation on my "yellow" USB3 stick (instead of the built-in SSD) that I have made for maintenance purposes.
Do I need to worry about the error message?
Is it possible that this is why the boot process from the stick takes so long?
Trying to find the reason why the boot process takes 2:45 minutes with the screen being black for 1:30 minutes was the reason for me to look for error messages in `/var/log` and on this occasion I came across the error message.