Public bug reported:
I was surprised last week to find that my computer had logged me out
when I had left it alone for some 15 minutes. I did not bother to
research at the time and did not see any reason as the problem did not
manifest again .
Then today, it happens again. The circumstances are similar: I leave the
system long enough for the screen to power off and come back to find
myself kicked out of my session. Yes, kicked out, not simply locked out.
I need to log in again and find that all running apps and open files
have all been closed.
My journal would appear to show that gnome-shell got stopped as a
consequence of systemd-oomd killing several applications (see the
included journalctl snippet - mind that the output is in reverse order
(journalctl -r)).
Should not oomd terminate single applications instead of complete user
sessions?
And I do have some doubts about the statistics listed in the journal.
One of the killed apps is reported as consuming over 22GB or RAM (out
of 32). I have been using that app for many years and cannot remember
having see it use more than a few GB.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-oomd 255.4-1ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 30 04:00:27 2024
InstallationDate: Installed on 2022-03-27 (855 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Description changed:
I was surprised last week to find that my computer had logged me out
when I came back to it after about fifteen minutes. I did not bother to
research at the time and did not see any reason as the problem did not
manifest again .
Today, however, it has happened again. The circumstances are similar: I
leave the system long enough for the screen to power off and come back
to find myself kicked out of my session. Yes, kicked out, not simply
locked out. I have to log in again and find that running applications
have been terminated and open files closed.
My journal would appear to show that gnome-shell got stopped as a
- conseuqence of systemd-oom killing several applications (see journalctl
+ consequence of systemd-oomd killing several applications (see journalctl
snip, mind that the output is in reverse order (journalctl -r)).
But I thought the point of oomd was to terminate single applications,
not the whole user session?
I also have my doubts about the statistics listed in the journal. One
app is reported as consuming over 22GB or RAM (out of 32). I have been
using that app for years and have not once seen it use more than a few
GB.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-oomd 255.4-1ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 30 04:00:27 2024
InstallationDate: Installed on 2022-03-27 (855 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
I was surprised last week to find that my computer had logged me out
- when I came back to it after about fifteen minutes. I did not bother to
+ when I had left it alone for some 15 minutes. I did not bother to
research at the time and did not see any reason as the problem did not
manifest again .
- Today, however, it has happened again. The circumstances are similar: I
- leave the system long enough for the screen to power off and come back
- to find myself kicked out of my session. Yes, kicked out, not simply
- locked out. I have to log in again and find that running applications
- have been terminated and open files closed.
+ Then today, it happens again. The circumstances are similar: I leave the
+ system long enough for the screen to power off and come back to find
+ myself kicked out of my session. Yes, kicked out, not simply locked out.
+ I need to log in again and find that all running apps and open files
+ have all been closed.
My journal would appear to show that gnome-shell got stopped as a
- consequence of systemd-oomd killing several applications (see journalctl
- snip, mind that the output is in reverse order (journalctl -r)).
+ consequence of systemd-oomd killing several applications (see the
+ included journalctl snippet - mind that the output is in reverse order
+ (journalctl -r)).
- But I thought the point of oomd was to terminate single applications,
- not the whole user session?
+ Should not oomd terminate single applications instead of complete user
+ sessions?
- I also have my doubts about the statistics listed in the journal. One
- app is reported as consuming over 22GB or RAM (out of 32). I have been
- using that app for years and have not once seen it use more than a few
- GB.
+ And I do have some doubts about the statistics listed in the journal.
+ One of the killed apps is reported as consuming over 22GB or RAM (out
+ of 32). I have been using that app for many years and cannot remember
+ having see it use more than a few GB.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: systemd-oomd 255.4-1ubuntu8.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 30 04:00:27 2024
InstallationDate: Installed on 2022-03-27 (855 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075104
Title:
user session is randomly terminated by systemd-oom when the system is
left alone for a while
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2075104/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
