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 2150212 - Many "Failed to start Application launched by gnome-session-binary" errors after fresh install RHEL 9 ISO on UEFI boot
Summary: Many "Failed to start Application launched by gnome-session-binary" errors af...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-desktop3
Version: 9.1
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-02 05:46 UTC by VIRENDRASINGH RAJPUT
Modified: 2023-04-18 15:19 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-17 14:42:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-desktop issues 160 0 None opened GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessI... 2022-12-14 17:35:21 UTC
Red Hat Issue Tracker RHELPLAN-141127 0 None None None 2022-12-02 05:54:38 UTC

Description VIRENDRASINGH RAJPUT 2022-12-02 05:46:07 UTC 
Description of problem:
After system boot with a fresh install, RHEL 9 ISO in UEFI boot "Logs" program lists several "Failed to start Application launched by gnome-session-binary" errors.

Version-Release number of selected component (if applicable):
gnome-shell-40.9-2.el9.x86_64         
gome-shell-40.10-3.el9.x86_64

How reproducible:
Everytime


Steps to Reproduce:
1.Downloaded fresh RHEL 9 ISO file from customer portal.

2. In Virt manager then Choose the installation medium or ISO. Choose memory Disk image, Then Check "Customize configuration before install" box and click Finish button.

3. You should now see the Virtual machine's hardware details. From the Overview section, choose "UEFI X86_64..." option from the Firmware drop-down box and then begin the installation.

4. Other steps are the same as the normal installation setup.

5. After successful installation and booting of the system see in "/var/log/message", the below error appears in logs:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-glib-xdg\x2duser\x2ddirs-3796.scope: Couldn't move process 3796 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-glib-xdg\x2duser\x2ddirs-3796.scope': No such process
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-glib-xdg\x2duser\x2ddirs-3796.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-glib-xdg\x2duser\x2ddirs-3796.scope: Failed with result 'resources'.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-gnome-xdg\x2duser\x2ddirs-3796.scope: Couldn't move process 3796 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-gnome-xdg\x2duser\x2ddirs-3796.scope': No such process
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-gnome-xdg\x2duser\x2ddirs-3796.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:02 192-168-112-197 systemd[3544]: app-gnome-xdg\x2duser\x2ddirs-3796.scope: Failed with result 'resources'.
Jul 15 13:42:02 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.freedesktop.portal.IBus.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Starting sandboxed app permission store...
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.CalendarServer.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started sandboxed app permission store.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.6-org.a11y.atspi.Registry.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.OnlineAccounts.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.Identity.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.Notifications.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-spice\x2dvdagent-4002.scope: Couldn't move process 4002 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-gnome-spice\x2dvdagent-4002.scope': No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-spice\x2dvdagent-4002.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-spice\x2dvdagent-4002.scope: Failed with result 'resources'.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-gnome\x2dshell\x2doverrides\x2dmigration-4062.scope: Couldn't move process 4062 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-glib-gnome\x2dshell\x2doverrides\x2dmigration-4062.scope': No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-gnome\x2dshell\x2doverrides\x2dmigration-4062.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-gnome\x2dshell\x2doverrides\x2dmigration-4062.scope: Failed with result 'resources'.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Couldn't move process 4070 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-glib-user\x2ddirs\x2dupdate\x2dgtk-4070.scope': No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed with result 'resources'.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-vmware\x2duser-4066.scope: Couldn't move process 4066 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-glib-vmware\x2duser-4066.scope': No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-vmware\x2duser-4066.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-glib-vmware\x2duser-4066.scope: Failed with result 'resources'.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Started Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Couldn't move process 4070 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope': No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed with result 'resources'.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Failed to start Application launched by gnome-session-binary.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.ScreenSaver.
Jul 15 13:42:03 192-168-112-197 systemd[3544]: Created slice Slice /app/dbus-:1.2-org.gnome.Shell.Screencast.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Actual results:
The above mentioned errors appears in messages logs after a fresh install of RHEL 9 ISO in UEFI boot.


Expected results:
The error messages should not appear in logs.

Additional info:

The customer also saw the below error messages but when I tried to reproduce it I can't see these messages in logs as this is only one-time occurrence of the below error logs and there is no functional impact on the customer side, can someone from the engineering team please confirm if we are good to ignore these messages?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Jul 15 13:42:19 192-168-112-197 nautilus[4467]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Jul 15 13:42:44 192-168-112-197 nautilus[5350]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

NOTE: There is already an upstream bug(https://bugzilla.redhat.com/show_bug.cgi?id=1973058) filed for this issue.
Comment 1 Tomas Popela 2022-12-02 08:10:09 UTC 
(In reply to VIRENDRASINGH RAJPUT from comment #0)
> Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Couldn't move process 4070 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope': > No such process
> Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed to add PIDs to scope's control group: No such process
> Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Failed with result 'resources'.

This has been reported as https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/160. Moving to gnome-desktop and adding also the uresourced maintainer (the issue should probably be moved to her).
Comment 2 Michael Catanzaro 2022-12-14 16:25:56 UTC 
I think this is a gnome-desktop bug, not a uresourced bug, although it is certainly related to uresourced. I posted some suggestions to resolve it in the upstream issue.
Comment 3 Ray Strode [halfline] 2022-12-14 16:57:00 UTC 
dtardon do you know off hand if there's a way to make systemd mum for this type of situation?
Comment 4 David Tardon 2022-12-16 08:42:38 UTC 
(In reply to Ray Strode [halfline] from comment #3)
> dtardon do you know off hand if there's a way to make systemd mum for this
> type of situation?

The only way I can think of is to set LogLevelMax= for the scope, as that is applied also for log messages about the unit in recent versions of systemd. The problem is that at least one of the messages is a warning, which means you'd have to set LogLevelMax=error to get rid of them. I'm pretty sure that's not desirable.
Comment 5 David Tardon 2022-12-16 08:59:04 UTC 
> > Jul 15 13:42:03 192-168-112-197 systemd[3544]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope: Couldn't move process 4070 to requested cgroup '/user.slice/user-0.slice/user/app.slice/app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4070.scope': > No such process

We've seen this before (bug 2009307), but it appeared to be a rare issue, so nobody has really looked into it. I suggest opening an upstream issue, though. It will likely get more traction there.
Comment 8 Ray Strode [halfline] 2023-04-17 14:42:04 UTC 
The warnings are benign.

As I understand it, gnome-session sometimes uses systemd to start services, and sometimes launches session services itself. In the case that it's launching a service itself, it still wants to integrate with systemd as much as possible, so systemd knows about the service and can provide resource management for it.

It does this integration work, by asking systemd to create "transient" service associated with the already running pid.

The problem is that not all services started by gnome-session at start up last very long. Some services are one-off things that start and stop very quickly.  gnome-session will still try to integrate those services with systemd and systemd will report an error to the log because they'll already be finished before it can do the integration work.

Systemd has no good way to turn off the error reporting in this benign case without turning off error reporting for more serious cases.

One way that was proposed upstream to fix this, is to make gnome-session freeze the started process with a SIGSTOP signal until systemd is finished setting up the transient service. That would avoid the error message, but suspending active processes while they're running in an uncontrolled fashion has the potential to cause problems, but it might work okay in practice. three other potential ideas:

1. Add some mechanism to systemd to make it quiet if the pid doesn't exist. StartTransientUnit already has a array of string-value pairs. We could add a new one to mute it for this particular failure case
2. We could create the transient unit at fork time instead of exec time, and defer the exec until it finishes
3. We could create the transient unit for services that are still running ~10 seconds after they're started (or something). This would avoid the any one shot services from getting integrated into systemd

But the messages are benign, and I'm not sure there's a big value from doing any of these types of changes. devnak unless we get business justification from customer or partner.
Comment 9 RHEL Program Management 2023-04-17 14:42:15 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.