Bug 2185384

Summary: xdg-desktop-portal-gnome queries cups permanently producing too much load
Product: [Fedora] Fedora Reporter: Albert Flügel <af>
Component: xdg-desktop-portal-gnomeAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: amigadave, gnome-sig, jadahl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 14:36:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
captured selected system calls of xdg-desktop-portal-gnome for aronud 10 seconds showing the queries to cupsd and responses none

Description Albert Flügel 2023-04-08 18:47:43 UTC
Created attachment 1956391 [details]
captured selected system calls of xdg-desktop-portal-gnome for aronud 10 seconds showing the queries to cupsd and responses

Description of problem:
After the system is running a while (unclear, i would say, a few hours) xdg-desktop-portal-gnome starts to permanently query cups, about 27 times per second. Thus both xdg-desktop-portal-gnome and cupsd have a CPU utilization of 6-8%. No print job is active, nothing in any queue.

Version-Release number of selected component (if applicable):
xdg-desktop-portal-gnome-43.1-1.fc37.x86_64


How reproducible:


Steps to Reproduce:
1. Start up the system.
2. Wait for a while

Actual results:
as described above.

Expected results:
anyone and anything may query cups, but not 27 times per second for no obvious reason.

Additional info:
Find attached selected system calls captured with strace including timestamps for around 10 seconds
top shows:
top - 20:45:16 up 1 day,  8:33,  3 users,  load average: 0.42, 0.76, 0.82
Tasks: 232 total,   3 running, 229 sleeping,   0 stopped,   0 zombie
%Cpu(s):  5.5 us,  6.2 sy,  0.0 ni, 88.2 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st
MiB Mem :   5550.4 total,    785.1 free,   2007.4 used,   2758.0 buff/cache
MiB Swap:   9646.0 total,   9644.9 free,      1.1 used.   2925.2 avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND   
 3227 user1     20   0 1471804 145428  72136 S   8.3   2.6  15:45.45 xdg-deskt+
  977 root      20   0  248408  12224   8776 R   7.3   0.2  13:25.87 cupsd     

I can't accept such useless waste of CPU resources.

Comment 1 Aoife Moloney 2024-05-07 16:05:04 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2024-05-21 14:36:42 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.