Hi, I've been bitten by a very similar issue recently on a RedHat system. When trying to launch from commandline no message is shown and the command returns soon. I did an strace of the execution and found out that gedit creates a socket in a temporary directory (in my case was controlled by $TMPDIR) and sometimes it wouldn't be deleted when closing gedit. On the next execution, it would find the socket, try to connect there and close as the syscalls failed. If it happens again and no error appears on logs or stdout/stderr, try the strace. You won't see it on the last line but a bit before, in my case 10-20 lines before the end. HTH, Miguel El 22 abr. 2016 7:39 a. m., "Ralf Mardorf" <silver.bullet@xxxxxxxx> escribió: > On Thu, 21 Apr 2016 20:05:10 -0500, Marshall Neill wrote: > >Launch from the command line and see what shows up. > > > >Just a thought. > > That could help, after the issue appears when launching it by a file > manager or a launcher, but not necessarily helps. The output in > ~/.xsession-errors* could provide error messages from the original > event, when gedit first failed by e.g. launching it, when clicking a > file in a file manager. In ~/.xsession-errors* usually is the output, > that you get by running an app in a terminal. >
