Bug 99783 - XQuartz under macOS Sierra repeatedly appears, disappears in Dock; app using it never starts
Summary: XQuartz under macOS Sierra repeatedly appears, disappears in Dock; app using ...
Status: RESOLVED MOVED
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 2.7.11 (xserver-1.18.4)
Hardware: Other Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-12 17:50 UTC by murray
Modified: 2019-05-23 18:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
attachment-21879-0.html (7.05 KB, text/html)
2017-02-13 21:05 UTC, murray
Details

Note You need to log in before you can comment on or make changes to this bug.
Description murray 2017-02-12 17:50:43 UTC
Under macOS Sierra (10.12.3), Xquartz 2.7.11 is not working with two apps that use it, namely, Rcmdr from within RStudio and the current Macports port of Inkscape (port inkscape @0.92.0_3+x11 together with inkscape-app @0.92_0).

For each, when I start the app, Rcmdr or Inkscape, the XQuartz icon repeatedly appears in the Dock and then quickly disappears; the app never actually opens.
Comment 1 Jeremy Huddleston Sequoia 2017-02-13 06:35:20 UTC
Is it crashing repeatedly or terminating successfully and respawning?

If a crash, attach the crash log.  If not, please debug why your system is misbehaving.  It's likely a bad ~/.xinitrc file.
Comment 2 Jeremy Huddleston Sequoia 2017-02-13 06:36:32 UTC
Or possibly a bad ~/.bashrc or ~/.profile or ~/.bash_profile, etc.  Create a fresh user account, login as the new user, and try.  If that works, then it's a problem with your current user configuration.  I suggest you ask for help on the mailing list as this is not the appropriate forum for support requests.
Comment 3 murray 2017-02-13 21:05:45 UTC
Created attachment 129564 [details]
attachment-21879-0.html

> On Feb 13, 2017, at 1:36 AM, bugzilla-daemon@freedesktop.org wrote:
> 
> 
> Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=99783#c2> on bug 99783 <https://bugs.freedesktop.org/show_bug.cgi?id=99783> from Jeremy Huddleston Sequoia <mailto:jeremyhu@freedesktop.org>
> Or possibly a bad ~/.bashrc or ~/.profile or ~/.bash_profile, etc.  Create a
> fresh user account, login as the new user, and try.  If that works, then it's a
> problem with your current user configuration.  I suggest you ask for help on
> the mailing list as this is not the appropriate forum for support requests.
> 
> You are receiving this mail because:
> You reported the bug.


XQuartz worked on a different account. On my usual account, I think I’ve tracked down the source of the trouble to file

    ~/.xinitrc.d/90-gnome.sh

which has contents:

    # make the freedesktop menu entries work
    export XDG_DATA_DIRS=/opt/local/share
    export XDG_DATA_HOME=/opt/local/share
    export XDG_CONFIG_DIRS=/opt/local/etc/xdg
 
    # enable sound
    export ESPEAKER=localhost

    # use Apple's window manager
    exec quartz-wm &
 
    # start GNOME
    exec gnome-session

(That file was installed as part of a macports gnome desktop port, I believe.)

This interferes with XQuartz??

——
Murray Eisenberg                                murray@math.umass.edu
Mathematics & Statistics Dept.       
Lederle Graduate Research Tower      phone 240 246-7240 (H)
University of Massachusetts                
710 North Pleasant Street                 
Amherst, MA 01003-9305
Comment 4 murray 2017-02-16 18:36:39 UTC
Remvoing (or renaming) file ~/.xinitrc.d/90-gnome.sh eliminates the XQuartz misbehavior I reported.
Comment 5 GitLab Migration User 2019-05-23 18:31:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/783.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.