Sublime Forum

Subl command does nothing on Centos 7

#1

I’ve installed sublime using yum and now have /usr/bin/subl but it does nothing when I run it. It exits with status 0.

0 Likes
#2

It shows no output? What build are you using, stable or dev? Do you have libgtk2 installed? Has this worked previously?

0 Likes
#4

I’m using the stable version. This is a brand new CentOS 7 installation. I’m not sure about the library. How would I check?

The behavior is immediate termination with a exit status of 0.

0 Likes
#5

I’m afraid I’m not in a position to debug this any further.

0 Likes
#6

what display environment does CentOS 7 use? someone recently had a problem with X11 on Ubuntu because their DISPLAY env var was set incorrectly, maybe something similar is happening here? Do other GUI apps launch from the command line?

0 Likes
#7

I thought this is unlikely because the process just exits.

However, there might be a different process already running and thus the new instance just signals the running instance to open a new file/folder. You may want to check for existing processes and terminate those or run subl -w to make the process in the terminal wait for the file to be closed.

0 Likes
#8

subl -w hangs for a bit then closes with status 0

0 Likes
#9

I have both gtk-2.0 and gtk-3.0 in /usr/lib64

0 Likes
#10

DISPLAY is :0

0 Likes
#11

Is there a switch with a debug mode that could show messages?

0 Likes
#12

Additional information. subl launches a process running /opt/sublime_text/sublime_text. The process hangs around until killed.

0 Likes
#13

More information here. I am getting these error messages:

(sublime_text:43854): GLib-GObject-WARNING **: 13:08:55.046: cannot register existing type 'GTask'

(sublime_text:43854): GLib-GObject-WARNING **: 13:08:55.046: cannot register existing type 'GAsyncResult'

(sublime_text:43854): GLib-GObject-CRITICAL **: 13:08:55.046: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(sublime_text:43854): GLib-CRITICAL **: 13:08:55.046: g_once_init_leave: assertion 'result != 0' failed
0 Likes
#14

Here is a complete list of the errors: https://pastebin.com/6hkDUu9A

0 Likes