Linux machine (Fedora) restarted immediately after suspend

My Dell Laptop restarted immediately after suspend when using Fedora 28  (Linux). To debug this, I used the following commands :

  1. systemd-inhibit –list        – This shows the programs that can inhibit suspending the system.
  2. systemctl suspend                – Request a suspend. Similar to closing the laptop lid.
  3. systemctl suspend -i           – Override inhibit and suspend, preventing programs that are inhibiting suspend from being able to inhibit.

I found that I could kill off processes listed by (1) and see which one was causing problems. In my case the xfce4-power-manager was the culprett

 

NetworkManager and nm-applet not working properly with xfce4 window manager

Symptom

When running xfce4, I found that in the notifications area, the nm-applet (the applet that shows the network status) would sometimes take a while to arrive, and sometimes it would hang and not allow me to view or change network.

When I started xfce4-notifyd-config I noticed that the xfce4-notifyd daemon was not running.

Solution

It turned out that I had some kde utilities installed, and one of these, the org.kde.plasma.Notifications.service, was conflicting with the org.xfce.xfce4-notifyd.Notifications.service. Both notification services failed.

To solve the problem, simply remove /usr/share/dbus-1/services/org.kde.plasma.Notifications.service (ensuring first that /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service exists).

Now log out and log in again and you should find that the nm-applet works and that when you start xfce4-notifyd-config, you don’t get the message that the daemon has not started.

I could not log in as myself but could log in as root on Fedora 28. Dropbox failed to start.

The symptom is that at the login screen I was unable to login as myself, but I could log in as other users or as root.

The problem turned out to be that the root partition (“/”) was full. To solve the problem I logged in as root and went to /var/log/journal/257adc6a3c2544e98cae7eeea8f97e6e and removed the files in the journal.

After rebooting the machine I was again able to login as myself. I noticed that Dropbox, which had been complaining that it was not able to start, is now able to start again.