https://bugs.kde.org/show_bug.cgi?id=500665

--- Comment #50 from postix <pos...@posteo.eu> ---
systemd-analyze --user log-level debug

I see in journalctl
> Failed to establish memory pressure event source, ignoring: Operation not 
> supported
> Failed to connect to /run/systemd/oom/io.systemd.ManagedOOM: File or folder 
> not found
Just don't know the cause yet, especially of the first line. 

This seems to be the reason that 
> ls 
> /sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service
shows no memory entries

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to