This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2044630 - housekeeping plugin GPU memory notifications not configurable
Summary: housekeeping plugin GPU memory notifications not configurable
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-settings-daemon
Version: 8.5
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-24 20:49 UTC by Paul Bransford
Modified: 2023-09-15 19:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-15 19:33:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
screenshot snip of problematic notification (12.10 KB, image/png)
2022-01-24 20:49 UTC, Paul Bransford 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4197 0 None Migrated None 2023-09-15 19:33:55 UTC
Red Hat Issue Tracker RHELPLAN-109437 0 None None None 2022-01-24 21:01:33 UTC

Description Paul Bransford 2022-01-24 20:49:13 UTC 
Created attachment 1853192 [details]
screenshot snip of problematic notification

Created attachment 1853192 [details]
screenshot snip of problematic notification

Description of problem:
Patch 0001-housekeeping-Add-a-GPU-memory-usage-notification.patch adds GPU memory utilization support to the housekeeping plugin built into gnome-settings-daemon.

However, unlike other housekeeping functionality, there are no gconf/dconf/gsettings keys to control this. On systems with relatively low amounts of GPU memory, this results in frequent useless warning messages that cannot be disabled or hidden.

In my case, the only indication of low GPU memory is the notification itself.

Version-Release number of selected component (if applicable):
3.32.0-16.el8 (though it is likely this affects all versions of this, as I have not been able to locate any followups on this patch since it's initial authorship)


How reproducible:
100%


Steps to Reproduce:
1. Utilize Gnome with an nvidia GPU with relatively little memory, using the proprietary driver (
2. Run several applications such as Slack, MS Teams, Discord
3. Observe repeated warning notifications (screenshot snippet attached) - sometimes several per minute.

Actual results:
Warning functionality is mandatory


Expected results:
Warning functionality is configurable/optional


Additional info:
Host has the following GPU and driver:
GPU (lspci): 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GL [Quadro K600] (rev a1)
Driver: kmod-nvidia-470.82.01-4.18.0-348.12.2-470.82.01-3.el8_5.x86_64 via https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64
Kernel: 4.18.0-348.12.2.el8_5.x86_64

Note that this is not kernel/driver version specific. This has been occuring for months over several versions of both.
Comment 1 Paul Bransford 2022-01-24 20:51:50 UTC 
Copy/paste error in the additional info. I meant to say:
    Kernel: 4.18.0-348.12.2.el8_5.x86_64

Instead I duplicated the repo URL. Sorry!
Comment 2 Paul Bransford 2022-01-24 20:56:55 UTC 
Additional: apparently in newer (or older?) versions of the daemon, there is/was an 'active' key under 'org.gnome.settings-daemon.plugins.<plugin>' that can be used to disable a plugin. This functionality appears absent now (or at least in the version packaged for RHEL8). This means this workaround doesn't apply, which is the only workaround for this issue I was able to locate broadly (was on an ubuntu forum).

    $ gsettings list-recursively org.gnome.settings-daemon.plugins.housekeeping
    org.gnome.settings-daemon.plugins.housekeeping min-notify-period 10
    org.gnome.settings-daemon.plugins.housekeeping free-size-gb-no-notify 1
    org.gnome.settings-daemon.plugins.housekeeping ignore-paths @as []
    org.gnome.settings-daemon.plugins.housekeeping free-percent-notify 0.050000000000000003
    org.gnome.settings-daemon.plugins.housekeeping free-percent-notify-again 0.01
    $ gsettings set org.gnome.settings-daemon.plugins.housekeeping active false
    No such key “active”
Comment 3 Benjamin Berg 2022-01-25 10:33:26 UTC 
You can disable the plugin by modifying the corresponding file in `/etc/xdg/autostart/` and adding `Hidden=true` to it. This also works per-user if you drop the file in to `.config/autostart/`.

This was originally added due to issue https://bugzilla.redhat.com/show_bug.cgi?id=1300852 as a workaround for gnome-shell leaking (GPU) memory. The idea was that this at least allowed user's to restart their session in order to free the memory again.

I believe that huge improvements were made on the memory leak issues on the GNOME Shell side since. As such, we might be able to just drop the patch from RHEL 8 again.
Comment 4 Florian Müllner 2022-01-26 18:42:09 UTC 
(In reply to Benjamin Berg from comment #3)

> I believe that huge improvements were made on the memory leak issues on the
> GNOME Shell side since.

The main issue was a gc problem in gjs, but I'm not sure how much it affected GPU memory instead of the normal heap.
Comment 8 RHEL Program Management 2023-09-15 19:32:56 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9 RHEL Program Management 2023-09-15 19:33:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.