gedit @3.14.2_0: opening/saving a file causes XQuartz 2.3.6 to crash.

[udbraumann]

When I try to open a simple file, gedit crashes:

$ gedit .bashrc

(gedit:81476): Gtk-WARNING **: drawing failure for widget `GtkSeparator': out of memory

(gedit:81476): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory

(gedit:81476): Gtk-WARNING **: drawing failure for widget `GtkHeaderBar': out of memory

(gedit:81476): Gtk-WARNING **: drawing failure for widget `GtkPaned': out of memory

(gedit:81476): Gtk-WARNING **: drawing failure for widget `GeditWindow': out of memory

(gedit:81476): Gdk-WARNING **: gedit: Fatal IO error 22 (Invalid argument) on X server /tmp/launch-XogDzn/org.x:0.

If I try to edit a file from scratch, as soon as I try to press Save I receive this

$ gedit

(gedit:82202): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(gedit:82202): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

(gedit:82202): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

** (gedit:82202): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-language not supported

** (gedit:82202): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkSeparator': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkHeaderBar': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkPaned': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GeditWindow': out of memory

(gedit:82202): Gdk-WARNING **: gedit: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-XogDzn/org.x:0.

I am using MacOSX 10.6.8. Some recommendations?

[dbevans (David B. Evans)]

I don't have a 10.6 system available to test but I don't see this problem when running on 10.9 or 10.10.

In my case, when opening a file from the command line, I see the following warning only and the file opens correctly

gedit Portfile

** (gedit:79874): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-language not supported

saving the file works correctly and the following additional warnings are emitted

** (gedit:79879): CRITICAL **: gedit_spell_checker_language_to_key: assertion 'lang != NULL' failed

** (gedit:79879): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported

Similar results when opening a file from the menu or editing a file from scratch.

The messages that I would consider significant are these (from your report)

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkSeparator': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkBox': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkHeaderBar': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GtkPaned': out of memory

(gedit:82202): Gtk-WARNING **: drawing failure for widget `GeditWindow': out of memory

(gedit:82202): Gdk-WARNING **: gedit: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-XogDzn/org.x:0.

Is it possible that you really are running out of memory? Can you try and shut down as many other apps that may be running as possible? What does Activity Monitor say about memory consumption? Is there a diagnostic report available in Console when the app crashes? Can you post it?

[dbevans (David B. Evans)]

Would appreciate it if others who have access to a 10.6 system could report whether they can reproduce this result and any other information that might be useful.

Thanks

[udbraumann]

Thanks, I have tried to reinstall gedit, i.e. this time I forced making a local build by issuing

$ sudo port uninstall gedit
$ sudo port -s install gedit

Unfortunately this did not solve the problems, gedit still crashes the way it crashed before. I attach a "Problem Report for X11" which is automatically displayed after crashing.

What I can promise is that no memory overrun occurs, more than 3GB RAM are presently unused.

[dbevans (David B. Evans)]

From the crash report, it appears that it is the X server that has crashed not the gedit app itself. That's what the fatal IO error message is about. Are you using the X11.app that comes with the OS, a downloaded version of X Quartz or MacPorts xorg-server?

[udbraumann]

Thanks, to be honest, I presently believe that X11 stops working due to problems inside gedit. That X11 I am using is

The X Window System
XQuartz 2.3.6 (xorg-server 1.4.2-apple56)
© 2003-2010 Apple Inc.
© 2003 XFree86 Project, Inc.
© 2003-2010 X.org Foundation, Inc.

I cannot remember if this was shipped with 10.6.8 or if I have installed it separately, but I definitely have neither installed nor use X11 from MacPorts.

[dbevans (David B. Evans)]

I agree that the X11 server probably dies because it can't deal with something that gedit is sending it.

The version you are running is a bit out of date. The version I'm running is

The X Window System
XQuartz 2.7.7 (xorg-server 1.15.2)
© 2003-2013 Apple Inc.
© 2003 XFree86 Project, Inc.
© 2003-2013 X.org Foundation, Inc.

which is the latest released version AFAIK.

Since this server is working correctly with gedit for me, you might think about upgrading to this version. It can be downloaded as a .dmg installer ​here and works on 10.6 up.

After installing you need to log out and then log in again to use the new version.

[dbevans (David B. Evans)]

BTW, the XQuartz site contains ​a historical list of released versions. According to this list, the version you are running is the one shipped with OS X 10.6.5.

[nerdling (Jeremy Lavergne)]

Cc Me!

[udbraumann]

Thank you for pointing me to the latest version of 2.7.7 of XQuartz. I have installed it, unexpectedly I had to wait about 7hours after trying to launch gedit since the first call of the new X11 has triggered a one-time exhaustive fc-cache run updating the font cache.

Guess what! Now gedit @3.14.2_0 works! Though this comes as a surprise to me: updating XQuartz from 2.3.6 to 2.7.7 was a very good idea.

[dbevans (David B. Evans)]

Frankly, I'm a little surprised as well, but glad it's working for you now. And an interesting result that may help others with similar problems. Let us know if you run across any further issues.