Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xserver xserver
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 887
    • Issues 887
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 105
    • Merge requests 105
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • xorg
  • xserverxserver
  • Issues
  • #747
Closed
Open
Created May 23, 2019 by Bugzilla Migration User@bugzilla-migration

XQuartz installer shows questionable *install*-related log out message during *update* activity

Submitted by Andreas Mohr

Assigned to Jeremy Huddleston Sequoia

Link to original bug (#100145)

Description

Hello,

I just had an update prompt message shown on Mac OS X 10.10 (going from AFAIR 2.7.7, to 2.7.11).

Everything seems to have gone fine with an XQuartz update, but one thing irks me:

At the end of the update-based install activity, the message box "You will need to log out and back in to make XQuartz your default X server." was shown.

This, i would suspect, is rather out of place in my use case since we are talking about an update, not an initial install, where the reason for this activity (updating of DISPLAY variable assignment to related value) presumably does not exist any more, since the variable presumably already had the exact same(?) content (right??).

This message will cause:

  • lost productivity for users
  • potential data loss for users (open applications, failure to save)
  • nuclear power plant bills ;-)

So, possibly the installer scripting is missing a check conditional to sufficiently (yet still reliably!) determine whether the reason for requesting such a re-login does exist.

If it is decided that adding a conditional is not useful (each additional conditional will reduce processing reliability to some extent!), then at least the prompt message should be corrected to correctly describe the situation: decide to either actively detect an update use case, and give extra information in that case, or do not actively detect an update use case, and give a prompt message which is sufficiently detailed to successfully cover both use cases.

Anyway, at least in a software update use case, the message should be improved to mention that this action may not be needed.

Thanks!

Version: 2.7.11 (xserver-1.18.4)

See also

  • https://bugs.freedesktop.org/show_bug.cgi?id=96662
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking