Hi KDE team,
Workstation enabled earlyoom by default[1] in Fedora 32. A search of Bugzilla suggests it has been a pretty well-behaved change. How do we feel about submitting this as a self-contained change proposal for Fedora 33 KDE?
[1] https://fedoraproject.org/wiki/Changes/EnableEarlyoom
Just tried it and works like a charm. But I noticed that this earlyoom daemon get a dynamic user from systemd, and now SDDM shows "Dynamic User" in the login screen. Anyone knows how to avoid that? It's confusing.
On Wed, 27 May 2020 at 21:35, Ben Cotton bcotton@redhat.com wrote:
Hi KDE team,
Workstation enabled earlyoom by default[1] in Fedora 32. A search of Bugzilla suggests it has been a pretty well-behaved change. How do we feel about submitting this as a self-contained change proposal for Fedora 33 KDE?
[1] https://fedoraproject.org/wiki/Changes/EnableEarlyoom
-- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
The UID of the "Dynamic User" should be outside of the visible UID range of SDDM (default 1000-60000 inclusive) in order for it to not show up in SDDM.
-- Carson Black [ jan Pontaoski ]
Am Mi., 27. Mai 2020 um 16:48 Uhr schrieb Iñaki Ucar iucar@fedoraproject.org:
Just tried it and works like a charm. But I noticed that this earlyoom daemon get a dynamic user from systemd, and now SDDM shows "Dynamic User" in the login screen. Anyone knows how to avoid that? It's confusing.
On Wed, 27 May 2020 at 21:35, Ben Cotton bcotton@redhat.com wrote:
Hi KDE team,
Workstation enabled earlyoom by default[1] in Fedora 32. A search of Bugzilla suggests it has been a pretty well-behaved change. How do we feel about submitting this as a self-contained change proposal for Fedora 33 KDE?
[1] https://fedoraproject.org/wiki/Changes/EnableEarlyoom
-- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
-- Iñaki Úcar _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
Thanks, changed it. Max default was 65000 though.
On Wed, 27 May 2020 at 22:51, Carson Black uhhadd@gmail.com wrote:
The UID of the "Dynamic User" should be outside of the visible UID range of SDDM (default 1000-60000 inclusive) in order for it to not show up in SDDM.
-- Carson Black [ jan Pontaoski ]
Am Mi., 27. Mai 2020 um 16:48 Uhr schrieb Iñaki Ucar iucar@fedoraproject.org:
Just tried it and works like a charm. But I noticed that this earlyoom daemon get a dynamic user from systemd, and now SDDM shows "Dynamic User" in the login screen. Anyone knows how to avoid that? It's confusing.
On Wed, 27 May 2020 at 21:35, Ben Cotton bcotton@redhat.com wrote:
Hi KDE team,
Workstation enabled earlyoom by default[1] in Fedora 32. A search of Bugzilla suggests it has been a pretty well-behaved change. How do we feel about submitting this as a self-contained change proposal for Fedora 33 KDE?
[1] https://fedoraproject.org/wiki/Changes/EnableEarlyoom
-- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
-- Iñaki Úcar _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
On 2020-05-28 17:43, Iñaki Ucar wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Did someone change it? My system shows...
# Maximum user id for displayed users #MaximumUid=60000
And the man page states
MaximumUid= Maximum user id of the users to be listed in the user interface. Default value is 60000
On Thu, 28 May 2020 at 11:43, Iñaki Ucar iucar@fedoraproject.org wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Well, actually, the wrong default was in /etc/sddm.conf.d/kde_settings.conf, and
$ rpm -q --whatprovides /etc/sddm.conf.d/kde_settings.conf file /etc/sddm.conf.d/kde_settings.conf is not owned by any package
So I'm a little confused here. Where did this file come from? I don't remember changing that setting before, but maybe I did?
On 2020-05-28 17:51, Iñaki Ucar wrote:
On Thu, 28 May 2020 at 11:43, Iñaki Ucar iucar@fedoraproject.org wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Well, actually, the wrong default was in /etc/sddm.conf.d/kde_settings.conf, and
$ rpm -q --whatprovides /etc/sddm.conf.d/kde_settings.conf file /etc/sddm.conf.d/kde_settings.conf is not owned by any package
So I'm a little confused here. Where did this file come from? I don't remember changing that setting before, but maybe I did?
That directory, /etc/sddm.conf.d/ , doesn't exist on any of my systems.
On Thu, 2020-05-28 at 17:54 +0800, Ed Greshko wrote:
On 2020-05-28 17:51, Iñaki Ucar wrote:
On Thu, 28 May 2020 at 11:43, Iñaki Ucar iucar@fedoraproject.org wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Well, actually, the wrong default was in /etc/sddm.conf.d/kde_settings.conf, and
$ rpm -q --whatprovides /etc/sddm.conf.d/kde_settings.conf file /etc/sddm.conf.d/kde_settings.conf is not owned by any package
So I'm a little confused here. Where did this file come from? I don't remember changing that setting before, but maybe I did?
That directory, /etc/sddm.conf.d/ , doesn't exist on any of my systems.
Same here, though /etc/sddm and /etc/sddm.conf both exist.
poc
On 5/28/20 8:40 AM, Patrick O'Callaghan wrote:
On Thu, 2020-05-28 at 17:54 +0800, Ed Greshko wrote:
On 2020-05-28 17:51, Iñaki Ucar wrote:
On Thu, 28 May 2020 at 11:43, Iñaki Ucar iucar@fedoraproject.org wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote:
Thanks, changed it. Max default was 65000 though.
Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Well, actually, the wrong default was in /etc/sddm.conf.d/kde_settings.conf, and
$ rpm -q --whatprovides /etc/sddm.conf.d/kde_settings.conf file /etc/sddm.conf.d/kde_settings.conf is not owned by any package
So I'm a little confused here. Where did this file come from? I don't remember changing that setting before, but maybe I did?
That directory, /etc/sddm.conf.d/ , doesn't exist on any of my systems.
Same here, though /etc/sddm and /etc/sddm.conf both exist.
Gets created when you make a change in System Settings, SDDM module.
poc _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
On Thu, 28 May 2020 at 13:42, Patrick Boutilier boutilpj@ednet.ns.ca wrote:
On 5/28/20 8:40 AM, Patrick O'Callaghan wrote:
On Thu, 2020-05-28 at 17:54 +0800, Ed Greshko wrote:
On 2020-05-28 17:51, Iñaki Ucar wrote:
On Thu, 28 May 2020 at 11:43, Iñaki Ucar iucar@fedoraproject.org wrote:
On Thu, 28 May 2020 at 11:27, Kamil Paral kparal@redhat.com wrote:
On Wed, May 27, 2020 at 11:03 PM Iñaki Ucar iucar@fedoraproject.org wrote: > Thanks, changed it. Max default was 65000 though. Can you please file a bug against the earlyoom package? We need to fix this for everyone.
In the earlyoom or SDDM? Because the wrong default was in the SDDM options.
Well, actually, the wrong default was in /etc/sddm.conf.d/kde_settings.conf, and
$ rpm -q --whatprovides /etc/sddm.conf.d/kde_settings.conf file /etc/sddm.conf.d/kde_settings.conf is not owned by any package
So I'm a little confused here. Where did this file come from? I don't remember changing that setting before, but maybe I did?
That directory, /etc/sddm.conf.d/ , doesn't exist on any of my systems.
Same here, though /etc/sddm and /etc/sddm.conf both exist.
Gets created when you make a change in System Settings, SDDM module.
So most probably I changed something at some point, and it's just I don't remember.
Nobody yelled when I floated the idea a month ago, so I've drafted a change proposal: https://fedoraproject.org/wiki/Changes/KDEEarlyOOM
Does anything look horrendously bad (it shouldn't because it's like 80% what chrismurphy did for Workstation)? In particular, I'm wondering
1. if "kde-desktop" is the right comps group, or if it would be better in "critical-path-kde" or another group. In either case, it will affect anyone who uses KDE Plasma, not just the KDE Spin. Is there a better way to restrict it to just the spin itself and not people who install it from some other means? 2. Do we know offhand if any other spins/labs besides Fedora Jam that uses KDE?
On Tue, Jun 23, 2020 at 5:22 PM Ben Cotton bcotton@redhat.com wrote:
Nobody yelled when I floated the idea a month ago, so I've drafted a change proposal: https://fedoraproject.org/wiki/Changes/KDEEarlyOOM
Does anything look horrendously bad (it shouldn't because it's like 80% what chrismurphy did for Workstation)?
Looks good to me.
In particular, I'm wondering
- if "kde-desktop" is the right comps group, or if it would be better
in "critical-path-kde" or another group. In either case, it will affect anyone who uses KDE Plasma, not just the KDE Spin. Is there a better way to restrict it to just the spin itself and not people who install it from some other means?
Most labs are fine with inheriting from the parent variant group. They can deselect in their own kickstarts as needed.
- Do we know offhand if any other spins/labs besides Fedora Jam that uses KDE?
Yeah, I actually just looked this up for the Btrfs change. Astronomy is the other one. The former Scientific lab also used KDE, but the new Comp Neuro one uses GNOME.
-- 真実はいつも一つ！/ Always, there's only one truth!
+1
On Tue 23 Jun 2020 at 17:22, Ben Cotton bcotton@redhat.com wrote:
Nobody yelled when I floated the idea a month ago, so I've drafted a change proposal: https://fedoraproject.org/wiki/Changes/KDEEarlyOOM
Does anything look horrendously bad (it shouldn't because it's like 80% what chrismurphy did for Workstation)? In particular, I'm wondering
- if "kde-desktop" is the right comps group, or if it would be better
in "critical-path-kde" or another group. In either case, it will affect anyone who uses KDE Plasma, not just the KDE Spin. Is there a better way to restrict it to just the spin itself and not people who install it from some other means? 2. Do we know offhand if any other spins/labs besides Fedora Jam that uses KDE?
-- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
Nobody yelled when I floated the idea a month ago
I haven't yelled because I missed the mail, because Gmane's gateway to this list was not picking up any messages. (Problem reported to Gmane, I hope they will fix it.)
As I replied on the devel list, I object to this Change because I object to EarlyOOM altogether (and, while, to be honest, I can live with the GNOME Workstation getting such dubious "features", I do not want to see them on the spin that I actually care about).
Kevin Kofler
If both RAM and swap go below 10% free, earlyoom issues SIGTERM to the process with the largest oom_score. If both RAM and swap go below 5% free, earlyoom issues SIGKILL
Fedora's earlyoom package is provided with the changed default settings:
EARLYOOM_ARGS="-r 0 -m 4 -M 409600 --prefer '^Web Content$' --avoid '^(dnf|packagekitd|gnome-shell|gnome-session-c|gnome-session-b|lightdm|sddm|sddm-helper|gdm|gdm-wayland-ses|gdm-session-wor|gdm-x-session|Xorg|Xwayland|systemd|systemd-logind|dbus-daemon|dbus-broker|cinnamon|cinnamon-sessio|kwin_x11|kwin_wayland|plasmashell|ksmserver|plasma_session|startplasma-way|xfce4-session|mate-session|marco|lxqt-session|openbox)$'"
It means that:
1. SIGTERM threshold for MemAvailable is 4% (but not more than 400 MiB) and SIGKILL threshold for MemAvailable is 2% (but not more than 200 MiB) by default. The change was due to the fact that earlyoom tree was criticized for too aggressive thresholds by default, and this was taken into account. Please update description in the proposal.
2. Firefox's children processes "Web Content" gets +300 to its oom_score. It means that earlyoom will prefer to kill firefox tabs rather than entire browser. Similar behavior is already practiced in chromium and electron-based apps by default.
3. Processes, the killing of which can lead to the killing of the entire session (kwin_x11|kwin_wayland|plasmashell|ksmserver|plasma_session etc), receive reduced priority in choosing a victim. dnf also gets low prio. This is yet another advantage that you can mention in the proposal.
see https://pagure.io/fedora-workstation/issue/119#comment-638366
-
Alexey Avramov -
Ben Cotton -
Carson Black -
Ed Greshko -
Harold Dost -
Iñaki Ucar -
Kamil Paral -
Kevin Kofler -
Neal Gompa -
Patrick Boutilier -
Patrick O'Callaghan