inkscape @0.92.3_5+quartz: renders black on Mojave

[hmeine (Hans Meine)]

After migration to Mojave (MacPorts reinstall), I was trying to install inkscape +quartz from scratch. I used the following command to check that I installed all dependencies which support +quartz also with that variant active:

# port installed rdepof:inkscape and variant:quartz
The following ports are currently installed:
  cairo @1.14.12_0+quartz+x11 (active)
  cairomm @1.12.2_0+quartz+x11 (active)
  glib2 @2.58.1_0+quartz (active)
  glib2 @2.58.1_0+x11
  glibmm @2.56.0_1+quartz (active)
  gtk2 @2.24.32_0+quartz (active)
  gtk2 @2.24.32_0+x11
  gtkmm @2.24.5_1+quartz (active)
  gtkspell2 @2.0.16_7+quartz (active)
  librsvg @2.42.2_2
  librsvg @2.42.2_2+quartz (active)
  pango @1.42.4_0+quartz+x11 (active)
  pangomm @2.40.1_0+quartz+x11 (active)

Problems:

1. When I start inkscape (which works for me, contrary to the report in #57604), I only get a black rendering (no visible document outline or graphical elements on it).
2. Furthermore, other necessary redraw or resize events do not seem to be invoked / handled; for instance, the main window contains the whole GUI cramped into a small upper left subpart of the full window, until it is resized.
3. I tried to open an existing file, and also had to manually trigger redraws of the file dialog by resizing, in order to get the file listing filled, for instance.

I then tried port install inkscape for the +x11 variant, but apparently that did not have a big effect; the dependencies (which I am partly also using for the Gimp) are still installed with +quartz, and the problems retain.

[rubendibattista (Ruben Di Battista)]

I also confirm the same behaviour. Inkscape (+quartz) starts ( I can see the original starting UI) but then keep the CPU at 100% and I cannot resize the window. Moreover I tried to download and run the App from the inkscape website that runs correctly on Mojave (and moreover is better looking graphically).

[rubendibattista (Ruben Di Battista)]

I tried to edit the Portfile to compile with cmake and I'm at least getting this warning that could be related:

2018-12-09 04:33:15.986 inkscape[20995:3162070] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.

[thede (Thede Loder)]

I performed a build using +quartz, and get the same results as hmeine. One of the errors reported on the console was failed connections to dbus. A manual install of dbus, plus manual activation of dbus via launchd for org.freedesktop.dbus-session made that error go away, but did not solve the UI window draw/refresh issue, and the CPU remains pegged at 100% on a core. Other tidbits: the application cannot be closed via a Quit from the main OSX menu. Selecting Quit from the file menu from the floating main window works.

[wmacevoy (Warren MacEvoy)]

Ditto (wish I found this before building!): black draw window with 100% cpu. Here are the launch errors:

2019-02-06 15:41:29.865 inkscape[83411:1244404] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead. 
dbus[83411]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Failed to get connection
** (inkscape:83411): CRITICAL **: 15:41:29.948: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (inkscape:83411): CRITICAL **: 15:41:29.948: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed

** (inkscape:83411): CRITICAL **: 15:41:29.949: dbus_g_connection_register_g_object: assertion 'connection != NULL' failed
dbus[83411]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Failed to get connection
** (inkscape:83411): CRITICAL **: 15:41:34.664: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (inkscape:83411): CRITICAL **: 15:41:34.664: dbus_g_connection_register_g_object: assertion 'connection != NULL' failed
dbus[83411]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Failed to get connection
** (inkscape:83411): CRITICAL **: 15:41:53.678: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (inkscape:83411): CRITICAL **: 15:41:53.678: dbus_g_connection_register_g_object: assertion 'connection != NULL' failed
dbus[83411]: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Failed to get connection
** (inkscape:83411): CRITICAL **: 15:42:10.083: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed

** (inkscape:83411): CRITICAL **: 15:42:10.083: dbus_g_connection_register_g_object: assertion 'connection != NULL' failed

Here are the package versions:

port installed rdepof:inkscape and variant:quartz
The following ports are currently installed:
  cairo @1.16.0_0+quartz+x11 (active)
  cairomm @1.12.2_0+quartz+x11 (active)
  glib2 @2.58.3_0+quartz (active)
  glibmm @2.58.0_0+quartz (active)
  gtk2 @2.24.32_0+quartz (active)
  gtkmm @2.24.5_2+quartz (active)
  gtkspell2 @2.0.16_7+quartz (active)
  pango @1.42.4_0+quartz+x11 (active)
  pangomm @2.42.0_0+quartz+x11 (active)

[steigerdominik]

I had behaviour similar to the one described above: Window rendering black, file open file trees not displaying (or only when resizing the window), opening files not possible. xquartz did not launch when starting inkscape. I did not experience 100% core load. Machine: Macbook Pro Retina Early 2013, macOS Mojave, OS never reinstalled from scratch.

I tried uninstalling and reinstalling xquartz, inkscape w/o xquartz and inkscape +quartz several times, to no avail.

Then I did the following:

I deleted x11 files per the following thread: ​https://gist.github.com/pwnsdx/d127873e24cef159d4d603accaf37ee4. I installed xquartz. I rerun sudo port install inkscape +quartz. I had xquartz open when running inkscape via terminal (macOS bash, not the xquartz terminal) the first time.

It started normally and works. Having xquartz closed, starting inkscape starts xquartz, and inkscape works normally.

I'm not sure what cured the problem, but suspect that the cleaner uninstall of x11/xquartz was responsible.

[hmeine (Hans Meine)]

Replying to steigerdominik:

It started normally and works. Having xquartz closed, starting inkscape starts xquartz, and inkscape works normally.

Not that that is giving you an X11 version of inkscape, which is indeed still working. The +quartz installation should not start xquartz, and that's the one that gives a black viewport.

You can try port installed rdepof:inkscape and variant:quartz and active and you'll see that although you activated +quartz on inkscape itself, its dependencies use x11, which we'd like not to for a native quartz build.

[sertal70]

I'm experiencing this issue too. I tried to follow ​steigerdominik instructions but without success, what else can I try to make Inkscape working again?

Thanks for helping!

[slavad (Viacheslav Dushin)]

I think it's a more general issue: #58280. I'm having the same problems not only with Inkscape but also with Dia

[hmeine (Hans Meine)]

Replying to sertal70:

I'm experiencing this issue too. I tried to follow ​steigerdominik instructions but without success, what else can I try to make Inkscape working again?

There's no know solution / cure / fix for the problem described here, but you can rebuild without the quartz variant. Use port installed rdepof:inkscape and active to see which packages need rebuilding.

[mascguy (Christopher Nielsen)]

I'll look into this as part of the Inkscape update (issue:61404).

[mascguy (Christopher Nielsen)]

Does this issue still occur with the new version (1.1.2)?

[hmeine (Hans Meine)]

It took me a while to answer this, because I now have a new M1 notebook, and when I first tried here, inkscape would just crash on startup. However, I now also checked on my previous notebook and can confirm that it works again, so that this issue can be considered resolved. I will next have to check if there's already a ticket for the crash.

[mascguy (Christopher Nielsen)]

Great, glad it's resolved!