Hello,

I have a weird problem with the new 0.48.1 in OS X 10.6.6. (latest Quartz 2.6.0)

1. On my main account 0.48.1 starts/runs fine.
2. On my other account which is just for doing screen recordings (clean desktop and dock)
it crash at startup with this message:
But if i first start the previous 0.48.0, quit and then start 0.48.1 it works.
I've tried making a few new accounts and this problem happens on every account except for my main account.

Anyone have a clue what could cause this and what to do?
I really would like 0.48.1 to work OK on on any account.

Thanks

To further investigate the issue, more information is needed beyond the generic error message "Inkscape encountered an internal error and will close now.":

1. Console messages
   1. open 'Applications > Utilities > Console'
   2. select 'All messages' from 'LOG DATABASE QUERIES' in the log list on the left
   3. clear the display ('View > Clear Display' or ⌘K)
   4. launch Inkscape, wait for it to crash
   5. copy the messages from the Console window into a new TextEdit document and save it (please use 'Plain Text' format)
   6. attach the console log here or pastebin its contents and share the link here
2. Crash Report
   
   1. in the Finder, browse to 'Home > Library > Logs > DiagnosticReports'
   2. search for the latest crash report from Inskcape (the file name contains 'inkscape-bin', as well as a date and time stamp)
   3. attach the crash report or pastebin its contents and share the link here

Additional notes for trouble-shooting the issue:

Jmx wrote:On my main account 0.48.1 starts/runs fine.

In which folder do you have Inkscape installed? Do all users have equally permissions to run applications from that location?

Jmx wrote:But if i first start the previous 0.48.0, quit and then start 0.48.1 it works.

Does it depend on doing that within a certain time span, or just within the same login session (or X11 session)?

Jmx wrote:I've tried making a few new accounts and this problem happens on every account except for my main account.

Have you tried launching X11 first by itself (not 'auto-launched' by Inkscape) to exclude that it's an issue with your Xquartz installation? Do other X11 apps (e.g. Gimp on OS X) run with all accounts?

Thanks ~suv for taking the time to help!

I've attached both files.

~suv wrote:In which folder do you have Inkscape installed? Do all users have equally permissions to run applications from that location?

I have tried it in the default Application folder, Desktop and my usual Application/Grafik folder, same result.

~suv wrote:Does it depend on doing that within a certain time span, or just within the same login session (or X11 session)?

Doesn't matter how or when i start it, it crash upon startup, but after further testing it now mostly crash even after 0.48.0.

~suv wrote:Have you tried launching X11 first by itself (not 'auto-launched' by Inkscape) to exclude that it's an issue with your Xquartz installation? Do other X11 apps (e.g. Gimp on OS X) run with all accounts?

Yes i've started X11 first and then 0.48.1, still crash. Even started 0.48.0, quit it and left X11 running and then start 0.48.1 and i still get crash.
If i close everything and try again and again, i sometimes get it running, but as soon as i quit and try relaunch it crash.
Gimp runs fine in any account, so does Inkscape 0.48.0.
Strange that 0.48.1 runs fine all the time on my main account, but not on any other accounts.
It runs fine on my 10.6.6 Macbook though, but not on my Mac Pro

Jmx wrote:I've attached both files.

From your (duplicate) crash report:

It seems to be the same error as in

• Bug #623640 in Inkscape: “inkscape 0.48 crashes on startup in colorprofile_get_system_profile_handle()”

Please try this workaround [1]:
With each account where Inkscape 0.48.1 fails to launch:

1. start the last working version of Inkscape (0.47, or 0.48.0)
2. open 'File > Inkscape Preferences > Color Management'
3. check "[x] Retrieve profile from display"
4. quit Inkscape
5. launch Inkscape 0.48.1

As for the reasons why 0.48.0 apparently works for you, but 0.48.1 fails to properly handle the color profiles located on your system - I can only guess (in earlier user reports, 0.47 launched without error, but 0.48.0 always crashed):

• IIRC some internal routines to retrieve color profiles have been changed, and 0.48.1 possibly locates more installed profiles?
• the default (new) user accounts have a different setup (monitor configuration, installed software) - compared to your (older?) main account?
• login items and currently running applications: one user reported this observation: «I noticed that in my case the error only appeared when certain apps were running: I was running word 2008 while I launched inkscape. Everything went fine. Then I opened Safari and Preview. When I closed inkscape and tried to reopen it showed again the internal error message.»

You can try to further investigate by e.g. making a list of the profiles that Inkscape finds in each account and comparing them to those from your main account :

• profile search paths
  the tooltip of the drop-down with detected display profiles ('Inkscape preferences > Color management > Display adjustment > Display profile') lists all paths that Inkscape searches: you can browse them in the Finder and check the profiles located there
• available profiles
  for each account take notes of all profiles listed in
  1. 'Preferences > Color management > Display adjustement > Display profiles'
  2. 'Preferences > Color management > Color proofing > Device profile'
  3. 'Document Properties > Color Management > Available Color Profiles'
• identify the profile(s) that trigger the crash
  so far not many details are known about the actual cause, but several users have been able to narrow down the problem to a single profile (possibly installed by third-party apps like Adobe CS4) by validating the installed profiles, and by removing and adding back one-by-one the installed profiles

In case you can identify a single color profile (display, printer or other) which Inkscape 0.48.1 fails to properly handle, please consider attaching it to the bug report (together with some basic information about your system setup).

[1] the same can be done without launching Inkscape, by manually editing the preferences file - I can give you detailed instructions if needed.

@~suv

That solved my problem and now it starts/runs just fine.
Super thanks for taking the time to explain and help.

~suv wrote:Please try this workaround [1]:
With each account where Inkscape 0.48.1 fails to launch:

1. start the last working version of Inkscape (0.47, or 0.48.0)
2. open 'File > Inkscape Preferences > Color Management'
3. check "[x] Retrieve profile from display"
4. quit Inkscape
5. launch Inkscape 0.48.1

Hello,

I have exactly the same problem as mentioned above, but NO VERSION of Inkscape LAUNCHES anymore.
I always get the same message: "Inkscape encountered an internal error and will close now."

What else can be done, without launching it?

My system:
Mac OS X 10.6.8
Logs are attached

Thank you for helping me!
Lubaum

Lubaum wrote:I have exactly the same problem as mentioned above, but NO VERSION of Inkscape LAUNCHES anymore.
I always get the same message: "Inkscape encountered an internal error and will close now."

What else can be done, without launching it?

My system:
Mac OS X 10.6.8
Logs are attached

From the log file crash report: it appears that the crash occurs when preparing the list of installed fonts…

You could try to remove [1] fonts you have installed lately - maybe you can figure out if and which one triggers the crash?

[1] Disabling fonts in Font Book does not have an effect for Inkscape: you have to actually move the font(s) out of the 'Fonts' folder.

Lubaum wrote:My system:
Mac OS X 10.6.8
Logs are attached

From the console log: Oddly, a bug report was recently filed for Inkscape (built with MacPorts on OS X Lion), with the console warnings (unfortunately the user did not provide additional information so far, nor attach a crash report ot backtrace):
Bug #898704 in Inkscape: “MacPort Inkscape on Lion crash at startup” (Incomplete)

I can't tell though whether the two reports are related, nor did I find any earlier reports about Inkscape failing to launch on Mac OS X which had the same type of console warnings ('missing action'). For most users, Inkscape (0.48.2 and earlier versions) work ok on Mac OS X Snow Leopard.

List of fonts from the console log about which X11 complains:

Also, there are several error messages from Apple's own font system (com.apple.fontd), and there is a recent message warning about your disk getting (or being) full (possibly due to log files or other system files which the Finder usually hides from normal users) - this one occurred right after installing 'Sophos Anti-Virus':

Thanks a lot!

THIS...
You could try to remove [1] fonts you have installed lately - maybe you can figure out if and which one triggers the crash?
[1] Disabling fonts in Font Book does not have an effect for Inkscape: you have to actually move the font(s) out of the 'Fonts' folder.
...HELPED.

Indeed, I installed new fonts lately. It was boring at school, so I downloaded several hundred fonts manually... I guess it takes a while to figure out which one/-s is/are the mad one/-s...

Thank you again,
Lubaum

I'm having the same problem (won't open and get the same error message) but can't tell from the logs what I need to do.

Here's what I'm running on:
Mac OS X Version 10.6.7

Downloaded:
Inkscape-0.48.2-1-SNOWLEOPARD.dmg
XQuartz (removed X11 and then logged out)

It crashed a couple of times when just opening the application in the Applications menu...but then I opened an example file using Inkscape and it opened. Interface language was changed to English and then I closed it. I tried opening it the same way and got a "Inkscape encountered an internal error and will close now". The interface language is still English and I can see the example file but it won't let me do anything. It now crashes both ways (opening it directly or by opening a file). I've since deleted all XQuartz/X11 and Inkscape files and reinstalled both applications. Attached is the most recent console log.

Any suggestions?