Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G gnome-session
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-session
  • Issues
  • #79
Closed
Open
Issue created Jan 20, 2021 by Olivier Fourdan@ofourdan🛠

Demote `org.gnome.SettingsDaemon.XSettings` from required components

Now that gnome-shell/mutter has switched to Xwayland on demand by default (mutter!1673 (merged)), killing repeatedly gsd-xsettings should not cause a fail-whale:

gnome-session-binary: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
gnome-session: gnome-session-binary: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' respawning too quickly
gnome-session: gnome-session-binary: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
gsd-xsettings: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :3.

That means demoting org.gnome.SettingsDaemon.XSettings from required components so that failure to restart gsd-xsettings should not be a fatal error.

On my system, I can reproduce easily:

  1. Enable the experimental feature autoclose-xwayland in mutter
  2. Start a new GNOME Shell session
  3. Start xterm to spawn Xwayland
  4. Close xterm, wait for 10 seconds for mutter to kill Xwayland
  5. Start xterm to respawn Xwayland again
  6. Close xterm, wait for 10 seconds for mutter to kill Xwayland

→ the fail-whale dialog shows up

Note: I can reproduce at will on my system with the steps above, while @carlosg cannot, so maybe there's something wrong on my jhbuild installation, nevertheless gsd-xsettings should not be treated as required (or required) component anymore with Xwayland on demand.

Edited Jan 20, 2021 by Olivier Fourdan
Assignee
Assign to
Time tracking