[SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

erickwill · 2017-12-31 01:04:59

R00KIE wrote:

What I mean is: 'ln -snf /run/user/1000/gdm/Xauthority ~/.Xauthority'.
Edit:
Typo and add a few more options to ln.

I still get the same error..

Invalid MIT-MAGIC-COOKIE-1 keySegmentation fault (core dumped)

Last edited by erickwill (2017-12-31 01:09:14)

R00KIE · 2017-12-31 01:34:29

What if you do 'xauth -f /run/user/1000/gdm/Xauthority list'?

seth · 2017-12-31 08:16:44

It doesn't even work with "xhost +" but he can run other clients.

I'd say it's because of the second X server and the client trying to connect to that X11 server rather than the actual one.

loginctl session-status
echo $DISPLAY

Also skip gdm, try startx (https://wiki.archlinux.org/index.php/Xinit - you don't need an xserverrc, but pay attention to the xinitrc section), ensure you end up with only one X11 server and see whether that works.

In case we'll have to figure how to convice the client to use the proper server connection (if it already ignores the DISPLAY variable, a "-display" might work, but you'll likely have to ask upstream since it seems closed source)

erickwill · 2017-12-31 12:46:03

R00KIE wrote:

What if you do 'xauth -f /run/user/1000/gdm/Xauthority list'?

quarktech-01/unix:  MIT-MAGIC-COOKIE-1  530a023cc0e4567e58332ec7d0572818
#ffff#717561726b746563682d3031#:  MIT-MAGIC-COOKIE-1  530a023cc0e4567e58332ec7d0572818

erickwill · 2017-12-31 12:49:35

seth wrote:

It doesn't even work with "xhost +" but he can run other clients.
I'd say it's because of the second X server and the client trying to connect to that X11 server rather than the actual one.
loginctl session-status
echo $DISPLAY
Also skip gdm, try startx (https://wiki.archlinux.org/index.php/Xinit - you don't need an xserverrc, but pay attention to the xinitrc section), ensure you end up with only one X11 server and see whether that works.
In case we'll have to figure how to convice the client to use the proper server connection (if it already ignores the DISPLAY variable, a "-display" might work, but you'll likely have to ask upstream since it seems closed source)

$ loginctl session-status

c2 - erick (1000)
           Since: Sun 2017-12-31 04:41:39 PST; 5min ago
          Leader: 4640 (gdm-session-wor)
            Seat: seat0; vc2
             TTY: tty2
         Service: gdm-password; type x11; class user
           State: active
            Unit: session-c2.scope
                  ├─ 4640 gdm-session-worker [pam/gdm-password]
                  ├─ 4666 /usr/bin/gnome-keyring-daemon --daemonize --login
                  ├─ 4670 /usr/lib/gdm/gdm-x-session --run-script gnome-session
                  ├─ 4672 /usr/lib/xorg-server/Xorg vt2 -displayfd 3 -auth /run/
                  ├─ 4677 /usr/lib/gnome-session-binary
                  ├─ 4718 /usr/bin/gnome-shell
                  ├─ 4848 /usr/lib/gnome-settings-daemon/gsd-color
                  ├─ 4849 /usr/lib/gnome-settings-daemon/gsd-datetime
                  ├─ 4851 /usr/lib/gnome-settings-daemon/gsd-media-keys
                  ├─ 4852 /usr/lib/gnome-settings-daemon/gsd-mouse
                  ├─ 4853 /usr/lib/gnome-settings-daemon/gsd-power
                  ├─ 4860 /usr/lib/gnome-settings-daemon/gsd-print-notifications
                  ├─ 4864 /usr/lib/gnome-settings-daemon/gsd-rfkill
                  ├─ 4865 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
                  ├─ 4866 /usr/lib/gnome-settings-daemon/gsd-sharing
                  ├─ 4877 /usr/lib/gnome-settings-daemon/gsd-smartcard
                  ├─ 4881 /usr/lib/gnome-settings-daemon/gsd-sound
                  ├─ 4884 /usr/lib/gnome-settings-daemon/gsd-wacom
                  ├─ 4887 /usr/lib/gnome-settings-daemon/gsd-xsettings
                  ├─ 4894 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
                  ├─ 4895 /usr/lib/gnome-settings-daemon/gsd-clipboard
                  ├─ 4896 /usr/lib/gnome-settings-daemon/gsd-a11y-keyboard
                  ├─ 4899 /usr/lib/gnome-settings-daemon/gsd-housekeeping
                  ├─ 4901 /usr/lib/gnome-settings-daemon/gsd-keyboard
                  ├─ 4925 /usr/lib/gnome-settings-daemon/gsd-printer
                  ├─ 4948 /usr/lib/tracker-miners/tracker-miner-fs
                  ├─ 4952 /usr/lib/gsd-disk-utility-notify
                  ├─ 4971 nautilus-desktop
                  ├─ 4974 /usr/lib/tracker-miners/tracker-extract
                  ├─ 4975 /usr/lib/tracker-miners/tracker-miner-apps
                  ├─ 5159 /opt/google/chrome/chrome
                  ├─ 5165 cat
                  ├─ 5166 cat
                  ├─ 5642 /opt/google/chrome/chrome-sandbox /opt/google/chrome/c
                  ├─ 5643 /opt/google/chrome/chrome --type=zygote
                  ├─ 5645 /opt/google/chrome/chrome-sandbox /opt/google/chrome/n
                  ├─ 5646 /opt/google/chrome/nacl_helper
                  ├─ 5648 /opt/google/chrome/chrome --type=zygote
                  ├─ 5687 /opt/google/chrome/chrome --type=gpu-process --field-t
                  ├─ 5747 /opt/google/chrome/chrome --type=gpu-broker
                  ├─ 5772 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5843 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5846 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5849 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5852 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5855 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 5861 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6048 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6122 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6142 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6662 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6682 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6708 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6749 /opt/google/chrome/chrome --type=renderer --field-tria
                  ├─ 6760 /opt/google/chrome/chrome --type=renderer --field-tria
                  └─13856 /opt/google/chrome/chrome --type=renderer --field-tria
lines 42-64/64 (END)

$ echo $DISPLAY

:1

seth · 2017-12-31 12:53:56

Yeah, if it blindly (hardcoded) tries to connect the "standard" :0 server this is gonna fail.
Please try w/o gdm.

erickwill · 2017-12-31 14:35:13

seth wrote:

Yeah, if it blindly (hardcoded) tries to connect the "standard" :0 server this is gonna fail.
Please try w/o gdm.

Yep, you're right. It did the trick. Somehow GDM or correlated dependencies was preventing Equinox 3D to run.
Have you any idea on how to set properly GDM in order to have it enable and be able to run Equinox? (or Equinox is the culprit?)

Last edited by erickwill (2017-12-31 14:56:09)

seth · 2017-12-31 15:01:27

Equinox is the culprit.
It's supposed to read the DISPLAY variable - maybe it still accepts an "--display" parameter. You got to ask the author.
Afaik GDM is designed to run several X11 servers (at least one for itself), afaics a pretty exclusive feature (ie. other DMs likely won't get you this problem) but:

Equinox is the culprit.

Ask the author to fix that (or whether there's a way to impact which display it aproaches)

erickwill · 2017-12-31 16:39:55

seth wrote:

Equinox is the culprit.
It's supposed to read the DISPLAY variable - maybe it still accepts an "--display" parameter. You got to ask the author.
Afaik GDM is designed to run several X11 servers (at least one for itself), afaics a pretty exclusive feature (ie. other DMs likely won't get you this problem) but:
Equinox is the culprit.
Ask the author to fix that (or whether there's a way to impact which display it aproaches)

Thanks for your assistance.

gnagy · 2018-01-27 07:02:26

Hello,
An EQUINOX-3D user just pointed me to this forum.
This bug has been fixed. Please, grab the latest v0.9.8 preview version (v0.9.8.30):
http://www.equinox3d.com/download.html
It uses the DISPLAY variable now, for opening the X11 display (as it should ).
Sorry for the troubles.
Please, let me know if the issue was resolved, and feel free to contact me through the Web site, with any EQUINOX-3D related questions:
http://www.equinox3d.com/contact.html

The official (non-preview) 0.9.8 release is coming soon!
We just need to fix some issues with the FBX exporter, and finish the GLSL renderer...

Best,

Gabor Nagy
equinox3d.com
Founder / developer

Last edited by gnagy (2018-01-27 07:06:01)

Arch Linux

#26 2017-12-31 01:04:59

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#27 2017-12-31 01:34:29

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#28 2017-12-31 08:16:44

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#29 2017-12-31 12:46:03

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#30 2017-12-31 12:49:35

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#31 2017-12-31 12:53:56

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#32 2017-12-31 14:35:13

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#33 2017-12-31 15:01:27

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#34 2017-12-31 16:39:55

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

#35 2018-01-27 07:02:26

Re: [SOLVED] "Segmentation fault (core dumped)" on Equinox 3D

Board footer