22 Apr
2016
22 Apr
'16
5:38 a.m.
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.