There is now a pre-packaged version of Inkscape running native on my MacPro under OS X 10.6.2. That's the good news. The bad news is that there's some more work needed to make it useable. On start up I get the following console messages:
3/23/10 8:51:51 AM defaults[41485] The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist 3/23/10 8:51:51 AM defaults[41487] The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) does not exist 3/23/10 8:51:51 AM defaults[41496] The domain/default pair of (.GlobalPreferences, AppleCollationOrder) does not exist 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Warning: AppleCollationOrder setting not found, using AppleLocale. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Setting Language: .UTF-8 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (process:41460): Gtk-WARNING **: Locale not supported by C library. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Using the fallback 'C' locale. 3/23/10 8:51:54 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Could not find the icon 'object-visible'. The 'hicolor' theme 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] was not found either, perhaps you need to install it. 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] You can get a copy from: 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] http://icon-theme.freedesktop.org/releases
These don't seem to impede the start up process but are mentioned in case they affect something else later.
Based on a quick 'tour', the basic functionality of the drawing tools etc seems to be in place. Of course, the two problems discussed in previous threads are still with us - the lack of radio buttons and the non appearance of aqua drop down menu items that have secondary menus associated with them. Another fairly critical item - saving the current document to file - causes a crash at the point where the 'save' button on the file dialog box is activated. This creates a series of console messages:
3/23/10 8:54:15 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Unable to find default local directory monitor type 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Unable to find default local directory monitor type 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Emergency save activated! 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Emergency save completed. Inkscape will close now. 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] If you can reproduce this crash, please file a bug at www.inkscape.org 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] with a detailed description of the steps leading to the crash, so we can fix it. 3/23/10 8:54:45 AM ReportCrash[41535] Saved crash report for inkscape-bin[41460] version ??? (???) to /Users/stu/Library/Logs/DiagnosticReports/inkscape-bin_2010-03-23-085445_SEsMacPro.crash 3/23/10 8:54:46 AM system_profiler[41538] could not convert interface name
If these three items can be fixed, the application would be very useable. Any ideas would be much appreciated.
If anyone would like a copy - let me know and we'll figure out how to transfer it -
Stu
Am 23.03.2010 um 14:25 schrieb Stuart Edwards:
There is now a pre-packaged version of Inkscape running native on my MacPro under OS X 10.6.2. That's the good news. The bad news is that there's some more work needed to make it useable. On start up I get the following console messages:
Just to compare - these do not occur on my Tiger PPC build:
3/23/10 8:51:51 AM defaults[41485] The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist 3/23/10 8:51:51 AM defaults[41487] The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) does not exist 3/23/10 8:51:51 AM defaults[41496] The domain/default pair of (.GlobalPreferences, AppleCollationOrder) does not exist
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Warning: AppleCollationOrder setting not found, using AppleLocale.
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (process:41460): Gtk-WARNING **: Locale not supported by C library. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Using the fallback 'C' locale.
These do occur on my Tiger PPC build as well:
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/ stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory
3/23/10 8:51:54 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Could not find the icon 'object-visible'. The 'hicolor' theme 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] was not found either, perhaps you need to install it. 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] You can get a copy from: 3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] http://icon-theme.freedesktop.org/releases
3/23/10 8:54:15 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Unable to find default local directory monitor type 3/23/10 8:54:35 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): Gtk-WARNING **: Unable to find default local directory monitor type
So probabely we should focus onto the firstly mentioned ones first to handle the "cannot-save-file" bug.
Yours, Wolf
On 23/3/10 19:08, Wolf Drechsel wrote:
So probabely we should focus onto the firstly mentioned ones first to handle the "cannot-save-file" bug.
Most of those messages can be seen with different installs of the GTK+/X11 version as well and are warnings only. Some have been explained earlier in inkscape-devel or in various bug report comments.
The ones related to the "Aqua" version only are
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory
and
3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
Relevant for the "cannot-save-file" bug would be the crash report from Stu:
3/23/10 8:54:45 AM ReportCrash[41535] Saved crash report for inkscape-bin[41460] version ??? (???) to /Users/stu/Library/Logs/DiagnosticReports/inkscape-bin_2010-03-23-085445_SEsMacPro.crash
Is there already a bug report about this? IMHO this is a critical issue which makes the application unusable in its current state (beyond testing).
@Stu - related questions: 1) can you load existing SVG files with 'File > Open…'? 2) if so, can you load several different SVG files within one instance of Inkscape (by using 'File > Open…') at the same time?
~suv
On Mar 23, 2010, at 2:29 PM, ~suv wrote:
On 23/3/10 19:08, Wolf Drechsel wrote:
So probabely we should focus onto the firstly mentioned ones first to handle the "cannot-save-file" bug.
Most of those messages can be seen with different installs of the GTK+/X11 version as well and are warnings only. Some have been explained earlier in inkscape-devel or in various bug report comments.
The ones related to the "Aqua" version only are
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory
and
3/23/10 8:51:58 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (inkscape-bin:41460): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
Relevant for the "cannot-save-file" bug would be the crash report from Stu:
3/23/10 8:54:45 AM ReportCrash[41535] Saved crash report for inkscape-bin[41460] version ??? (???) to /Users/stu/Library/Logs/DiagnosticReports/inkscape-bin_2010-03-23-085445_SEsMacPro.crash
See attached
Is there already a bug report about this?
no - I was waiting to see if there was an easy fix -
IMHO this is a critical issue which makes the application unusable in its current state (beyond testing).
no doubt
@Stu - related questions:
- can you load existing SVG files with 'File > Open…'?
The image renders on the new page - and then the error message - 'Inkscape encountered ........ ' appears. When 'close' is pressed a crash occurs (see attached )
- if so, can you load several different SVG files within one instance
of Inkscape (by using 'File > Open…') at the same time?
~suv
Also, the gtk-engines2 change doesn't seem to bring my radio buttons back.
Stu
On 23/3/10 20:16, Stuart Edwards wrote:
On Mar 23, 2010, at 2:29 PM, ~suv wrote:
IMHO this is a critical issue which makes the application unusable in its current state (beyond testing).
no doubt
@Stu - related questions:
- can you load existing SVG files with
'File > Open…'?
The image renders on the new page - and then the error message - 'Inkscape encountered ........ ' appears. When 'close' is pressed a crash occurs (see attached )
- if so, can you load several different SVG files within one
instance of Inkscape (by using 'File > Open…') at the same time?
this means: current Inkscape "Aqua" builds with GTK+/Quartz on (Snow) Leopard [1]
- cannot load SVG documents - cannot save SVG documents
at all, correct?
~suv
[1] IIRC I had seen the same issue with a very preliminary, experimental GTK+/Quartz Inkscape build for Mac OS X 10.5 Leopard based on the early prerelease version 0.47pre0 (crash when opening or saving SVG files) http://article.gmane.org/gmane.comp.graphics.inkscape.user/12507
On Mar 23, 2010, at 5:09 PM, ~suv wrote:
On 23/3/10 20:16, Stuart Edwards wrote:
On Mar 23, 2010, at 2:29 PM, ~suv wrote:
IMHO this is a critical issue which makes the application unusable in its current state (beyond testing).
no doubt
@Stu - related questions:
- can you load existing SVG files with
'File > Open…'?
The image renders on the new page - and then the error message - 'Inkscape encountered ........ ' appears. When 'close' is pressed a crash occurs (see attached )
- if so, can you load several different SVG files within one
instance of Inkscape (by using 'File > Open…') at the same time?
this means: current Inkscape "Aqua" builds with GTK+/Quartz on (Snow) Leopard [1]
- cannot load SVG documents
- cannot save SVG documents
at all, correct?
~suv
[1] IIRC I had seen the same issue with a very preliminary, experimental GTK+/Quartz Inkscape build for Mac OS X 10.5 Leopard based on the early prerelease version 0.47pre0 (crash when opening or saving SVG files) http://article.gmane.org/gmane.comp.graphics.inkscape.user/12507
Quite correct. I can print (causes a crash right afterwards) and export a png (doesn't crash) - but no svg file input / output
Stu
On Mar 23, 2010, at 5:09 PM, ~suv wrote:
On 23/3/10 20:16, Stuart Edwards wrote:
On Mar 23, 2010, at 2:29 PM, ~suv wrote:
IMHO this is a critical issue which makes the application unusable in its current state (beyond testing).
no doubt
@Stu - related questions:
- can you load existing SVG files with
'File > Open…'?
The image renders on the new page - and then the error message - 'Inkscape encountered ........ ' appears. When 'close' is pressed a crash occurs (see attached )
- if so, can you load several different SVG files within one
instance of Inkscape (by using 'File > Open…') at the same time?
this means: current Inkscape "Aqua" builds with GTK+/Quartz on (Snow) Leopard [1]
- cannot load SVG documents
- cannot save SVG documents
at all, correct?
~suv
[1] IIRC I had seen the same issue with a very preliminary, experimental GTK+/Quartz Inkscape build for Mac OS X 10.5 Leopard based on the early prerelease version 0.47pre0 (crash when opening or saving SVG files) http://article.gmane.org/gmane.comp.graphics.inkscape.user/12507
Quite correct. I can print (causes a crash right afterwards) and export a png (doesn't crash) - but no svg file input / output
Stu
Slight correction - 'save' does function, but causes an immediate crash as it executes - but the file is saved
Stu
On Mar 23, 2010, at 6:25 AM, Stuart Edwards wrote:
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Warning: AppleCollationOrder setting not found, using AppleLocale. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Setting Language: .UTF-8 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (process:41460): Gtk-WARNING **: Locale not supported by C library. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Using the fallback 'C' locale.
I think this one might be related to needing a few magic directories added. I found this with fixing Java apps for OS X. One tricky point was that one a particular box had a locale unblocked for an app, it stayed unblocked in that box.
On 24/3/10 05:16, Jon Cruz wrote:
On Mar 23, 2010, at 6:25 AM, Stuart Edwards wrote:
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Warning: AppleCollationOrder setting not found, using AppleLocale. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Setting Language: .UTF-8
The message 'Setting Language: .UTF-8' comes from the launcher script 'Contents/Resources/bin/inkscape' which tries to look up a language string it has read from the system preferences in the file '/usr/share/locale/locale.alias' but fails because that alias table doesn't include a lot of entries on some (?) systems. '/usr/X11/share/X11/locale/locale.alias' (at least on Leopard) could be a better choice as lookup table imho.
see also: Bug #476678 “Mac OS X: Fails to get locale in Japanese”: https://bugs.launchpad.net/inkscape/+bug/476678 comment #2
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory
The packaging and launcher script needs to take into account that some files are not needed when building / running without X11 (e.g. the X font backend for pango)
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (process:41460): Gtk-WARNING **: Locale not supported by C library. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Using the fallback 'C' locale.
This seems an GTK+ issue I never really found an explanation for (using google ;), but the message is reported for other GTK+/X11 applications too, on different (linux) systems and with differing locale settings, not limited to Inkscape application bundles for Mac OS X.
I think this one might be related to needing a few magic directories added. I found this with fixing Java apps for OS X. One tricky point was that one a particular box had a locale unblocked for an app, it stayed unblocked in that box.
AFAICT adding empty *.lprj folders to 'Contents/Resources' does not solve the 'empty' $LANG string that is wrongly set it the launcher script but may override it on some systems? I no longer see the GTK+ message "Gtk-WARNING **: Locale not supported by C library." when using a modified version of the launcher script which correctly sets $LANG after reading the menu language setting from the system preferences.
~suv
participants (4)
-
Jon Cruz -
Stuart Edwards -
Wolf Drechsel -
~suv