Bug 1593215
Summary: | 'org.gnome.SettingsDaemon.DiskUtilityNotify.desktop' failed to register before timeout | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Tomas Hudziec <thudziec> |
Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.6 | CC: | jkoten, modehnal, rstrode, tpelka, vbenes |
Target Milestone: | beta | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gnome-session-3.28.1-5.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 10:26:43 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1607454 |
Description
Tomas Hudziec
2018-06-20 09:56:20 UTC
I have similar issue with gnome-session-quit command. 1. Connect via ssh to VM. 2. sudo service gdm stop 3. sudo service gdm start 4. Open terminal in VM and type: gnome-session-quit Actual result: ** (gnome-session-quit:4239): WARNING **: 14:11:16.205: Failed to call logout: GDBus.Error:org.gnome.SessionManager.NotInRunning: Logout interface is only available after the Running phase starts I am not able to quit the session. Expected result: No message, session will prompt the user to confirm or cancel session quitting. Additional info: I cannot quit the session for roughly 70 seconds. After that I am able to quit the session with the above command. After successful command query journalctl will print gnome-session-binary[9400]: Entering running state. I suspect this issue is for the same reason the icons are not showing on start. If not let me know and I will file a new bug. The easiest reporoducer is to create new user and login. The gnome initial setup shows up about 2m after login. In logs I see: gnome-session[21782]: gnome-session-binary[21782]: WARNING: Application 'org.gnome.SettingsDaemon.DiskUtilityNotify.desktop' failed to register before timeout tracker-store.desktop[23685]: (uint32 2,) gnome-session-binary[21782]: Entering running state And when I remove the 'org.gnome.SettingsDaemon.DiskUtilityNotify.desktop' from /etc/xdg/autostart everything is ok. Moving to gnome-disk-utility. gnome-disk-utility-3.28.2-1.el7 I have found following commit upstream https://gitlab.gnome.org/GNOME/gnome-disk-utility/commit/78034ca97df5621a52b8ad522859a7da58a7544b But the commit is already in, so the question is why the gnome-session is still waiting for the app to register? we had to add a hack to accommodate upgrades at one point: + const char *app_id;• +• + app_id = g_app_info_get_id (G_APP_INFO (app->priv->app_info));• +• + /* These hardcoded checks are to keep upgrades working */• + if (app_id != NULL && g_str_has_prefix (app_id, "org.gnome.Shell"))• + phase = GSM_MANAGER_PHASE_DISPLAY_SERVER;• + else if (app_id != NULL && g_str_has_prefix (app_id, "org.gnome.SettingsDaemon"))• + phase = GSM_MANAGER_PHASE_INITIALIZATION;• + else• + phase = GSM_MANAGER_PHASE_APPLICATION;• }• This is what's causing the problem. We might be able to change that g_str_has_prefix (app_id, "org.gnome.SettingsDaemon") to g_str_equal (app_id, "org.gnome.SettingDaemon.desktop") (i'll need to see when the settings-daemon modularity happened). otherwise, we'll probably just need to special case DiskUtilityNotify to be phase application specifically (or force it in desktop file). Working well now. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3140 |