Inkscape crashes on launch

Bug #891089 reported by I Denker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
High
Unassigned

Bug Description

I'm on Mac OS 10.6.8. I used Inkscape a few times until the day I decided to learn it better.
When I launched the app, it came this time with a Turkish interface (my system and apps are in French as my system preferences, keyboard options, etc).
I changed the language in the Preferences pane.
At the next launch, I had the message : Internal error. The app has to close.
I've uninstalled. Redownloaded it several times from Inkscape site (Inkscape-0.48.2-1-SNOWLEOPARD.dmg file is avaliable).
And installed again.
The situation is allways the same : Turkish interface and the same an internal error (and so on) window.
I can't understand what it's about.
Thanks for your help.
Regards

Tags: crash osx
Revision history for this message
I Denker (m1-f-5l) wrote :
Revision history for this message
su_v (suv-lp) wrote :

> I can't understand what it's about.

About the crash:
Please attach the crash report created by the system:
Crash reports are saved in 'Home > Library > Logs > DiagnosticReports'. Choose the most recent one for 'inkscape-bin' (the reports have a date and time stamp in the name) and attach it here to the report.
Probably a duplicate of bug #623640.

About the Turkish menu language:
It has been reported by several users, and most confirmed that the menu language reverted to the default one after a reboot (or logging out and back in of the current user). The issue is tracked in bug #617079 - but based on what we know so far, it's actually the system reporting the incorrect language to Inkscape (possibly after installing new software?).

tags: added: crash osx
Changed in inkscape:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
I Denker (m1-f-5l) wrote :

Thanks for the answer.
Tried different things...
- Installed XQuartz 2.7. Honestly, I ignore the real importance of this feature. I only read that Apple dosn't update this app :)
- Inkscape launched normally -- still in turkish. (There is no reason for any app to get Turkish as system language. All my apps turn normally on this point. I checked again everywhere on my system preferences...)
- I hurried to change the Interface language in the Preferences pane.
- I cleaned up different caches with Onyx and Cocktail...
- Now : sometimes Inkscape launches normally (in french) and sometimes I get the previous situation (with a french interface in background).

I send 3 crash reports that I got during this experimentation.

Revision history for this message
I Denker (m1-f-5l) wrote :
Revision history for this message
su_v (suv-lp) wrote :
Download full text (3.2 KiB)

> Tried different things...
> - Installed XQuartz 2.7.
> (…)

It is not required (nor officially recommended by the Inkscape project) to install the development version of X11/Xquartz on Snow Leopard to be able to run Inkscape. The stable X11 version installed and updated by Apple is sufficient for Inkscape.

The menu language glitch does not trigger crashes [1]: those that you get (and attached the reports for [2]), are related to installed/loaded color profiles (duplicate of bug #623640):

> Thread 0 Crashed: Dispatch queue: com.apple.main-thread
> 0 libSystem.B.dylib 0x9409bdc8 _UTF8_mbsnrtowcs + 62
> 1 libSystem.B.dylib 0x940d3c90 mbsrtowcs_l + 100
> 2 libSystem.B.dylib 0x940d178a __collate_mbstowcs + 149
> 3 libSystem.B.dylib 0x940408ee strcoll_l + 121
> 4 libSystem.B.dylib 0x9404086f strcoll + 61
> 5 libglib-2.0.0.dylib 0x0211d31c g_utf8_collate + 124
> 6 inkscape-bin 0x0001a1e2 findThings() + 274
> 7 inkscape-bin 0x0001b5b3 Inkscape::colorprofile_get_system_profile_handle() + 611

A possible workaround to avoid the crashes:
1) install Inkscape 0.47, you can download the DMG from
   <http://sourceforge.net/projects/inkscape/files/inkscape/0.47/>
   Simply drop the application from the DMG into a temporary folder,
   no need to uninstall 0.48
2) launch Inkscape 0.47
3) open preferences dialog and select the 'Color-management' pane
4) check 'Display adjustment > [x] Retrieve profile from display'
5) quit Inkscape 0.47, launch Inkscape 0.48

Linking as duplicate to Bug #623640 “inkscape 0.48 crashes on startup in colorprofile_get_system_profile_handle()”.
Please add a comment here and revert the duplicate status if you don't agree and think these are different issues.

--
[1] Incorrect languages used for the menus is tracked in
    Bug #617079 “Turkish menu bar, I need English”
    <https://bugs.launchpad.net/inkscape/+bug/617079>

[2] the third report from the attached archive for the Xquartz crash should be reported upstream if reproducible - as far as I can tell it is not related to using Inkscape, but occurred when the screensaver was activated and/or the screen was locked:

> Thread 4 Crashed:
> 0 libSystem.B.dylib 0x00007fff85b6784f nanosleep$NOCANCEL + 0
> 1 libSystem.B.dylib 0x00007fff85bc43ce usleep$NOCANCEL + 57
> 2 libSystem.B.dylib 0x00007fff85be3a00 abort + 93
> 3 X11.bin 0x0000000100106efa System + 0
> 4 X11.bin 0x000000010000da4c DarwinSaveScreen + 0
> 5 X11.bin 0x000000010010b446 AbortServer + 34
> 6 X11.bin 0x000000010010adb6 FatalError + 279
> 7 X11.bin 0x0000000100105a0d LockServer + 798
> 8 X11.bin 0x00000001001055ab OsInit + 752
> 9 X11.bin 0x00000001000268be dix_main + 662
> 10 X11.bin 0x0000000100011327 server_thread + 38
> 11 libSystem.B.dylib 0x00007fff85b2dfd6 _pthread_start + 331
> 12 libSystem.B.dylib 0x00007fff85b2...

Read more...

Changed in inkscape:
status: Incomplete → New
Revision history for this message
I Denker (m1-f-5l) wrote :

I proceeded as above.
0.48 worked then once. And the same "Internal error" message came back at the second launch.
I tried something else: just deplaced 0.48 in a subfolder in my Apps folder.
Miracle! It launched OK... but not at every launch.
Today, I worked a little on 0.48, then I quitted.
Then I had the same "Internal error" message.
Quitted and launched again.
Launched normally.
This doesn't seem an exact duplicate of the bug #623640, i guess: color profile handling is de-activated on my 0.48.
Other point: it seems to me that quit and relaunch XQuartz 2.7.0 "helps" Inkscape.
(Should I uninstall this version XQuartz 2.7.0?)

Revision history for this message
su_v (suv-lp) wrote :

> This doesn't seem an exact duplicate of the bug #623640, i guess:
> color profile handling is de-activated on my 0.48.

Apparently not: from the attached bug reports:

inkscape-bin_2011-11-17-104048_iMac-de-Ibrahim-Denker.crash:
> 7 inkscape-bin 0x0001a623 Inkscape::colorprofile_get_proof_profile_handle() + 627
> 8 inkscape-bin 0x0001bc98 Inkscape::colorprofile_get_display_transform() + 1400

inkscape-bin_2011-11-17-104855_iMac-de-Ibrahim-Denker.crash:
> 7 inkscape-bin 0x0001b5b3 Inkscape::colorprofile_get_system_profile_handle() + 611
> 8 inkscape-bin 0x0001bc86 Inkscape::colorprofile_get_display_transform() + 1382

Did you at some point activate soft proofing in the same preferences pane (Color Management)? Please try to reset Inkscape's preferences completely:

1) quit any running Inkscape instance
2) in the Finder, use 'Cmd+Shift+G' to browse to the hidden
   folder '~/.config/inkscape' (the quotes are not part of the path name)
3) rename the file 'preferences.xml'
4) start Inkscape 0.47, set the preference as described earlier to retrieve
   the profile from display for display adjustment
   Note: do not activate or edit soft proofing, in the lower part of the
   color management preferences, see also the attached screenshot of the
   preferences pane in French
5) guit 0.47 and launch 0.48

It seems to me that some of your installed color profiles is broken, wrongly encoded or otherwise incompatible with Inkscape and/or lcms1.

> just deplaced 0.48 in a subfolder in my Apps folder.
> Miracle! It launched OK... but not at every launch.

In the other report (bug #623640), one user had described that the crash depends on which other applications had been launched before (re-)starting Inkscape (MS Word 2008 + Safari + Preview -> Inkscape crashes, comment #20). It seems to be a temporary but recurring issue, possibly initially triggered by certain color profiles installed by third-party applications (Adobe, MS, Printer drivers, etc.) - also indicated by another user reporting that repairing (corrupt) color profiles with ColourSync had helped to prevent these types of crashes.

> (Should I uninstall this version XQuartz 2.7.0?)

Xquartz is the development version of the stable X11 installed and updated by Apple. It's up to you to decide whether to use the stable version or a release from the development branch. Note that simply trashing the Xquartz application does _not_ uninstall Xquartz (it will possibly leave you with a broken X11 installation where neither Xquartz nor the default X11 will auto-launch on demand any more). Please read the documentation and FAQ on xquartz.macosforge.org if you decide to revert to Apple's X11 as default X server, or ask on one of the related mailing lists for advice (Apple's X11-users, or xquartz-dev).

Inkscape does not require a recent Xquartz release (Apple's X11 is sufficient). There is no indication in the backtraces of the provided crash reports that this crash is related in any way to the version of X11 installed on the local system.

Revision history for this message
I Denker (m1-f-5l) wrote : Re: [Bug 891089] Re: Inkscape crashes on launch
Download full text (4.6 KiB)

It works!
Thanks a lot!

[Je suis en déplacement.]

Le 17 nov. 2011 à 12:05, ~suv <email address hidden> a écrit :

> *** This bug is a duplicate of bug 623640 ***
> https://bugs.launchpad.net/bugs/623640
>
>> This doesn't seem an exact duplicate of the bug #623640, i guess:
>> color profile handling is de-activated on my 0.48.
>
> Apparently not: from the attached bug reports:
>
> inkscape-bin_2011-11-17-104048_iMac-de-Ibrahim-Denker.crash:
>> 7 inkscape-bin 0x0001a623 Inkscape::colorprofile_get_proof_profile_handle() + 627
>> 8 inkscape-bin 0x0001bc98 Inkscape::colorprofile_get_display_transform() + 1400
>
> inkscape-bin_2011-11-17-104855_iMac-de-Ibrahim-Denker.crash:
>> 7 inkscape-bin 0x0001b5b3 Inkscape::colorprofile_get_system_profile_handle() + 611
>> 8 inkscape-bin 0x0001bc86 Inkscape::colorprofile_get_display_transform() + 1382
>
> Did you at some point activate soft proofing in the same preferences
> pane (Color Management)? Please try to reset Inkscape's preferences
> completely:
>
> 1) quit any running Inkscape instance
> 2) in the Finder, use 'Cmd+Shift+G' to browse to the hidden
> folder '~/.config/inkscape' (the quotes are not part of the path name)
> 3) rename the file 'preferences.xml'
> 4) start Inkscape 0.47, set the preference as described earlier to retrieve
> the profile from display for display adjustment
> Note: do not activate or edit soft proofing, in the lower part of the
> color management preferences, see also the attached screenshot of the
> preferences pane in French
> 5) guit 0.47 and launch 0.48
>
> It seems to me that some of your installed color profiles is broken,
> wrongly encoded or otherwise incompatible with Inkscape and/or lcms1.
>
>> just deplaced 0.48 in a subfolder in my Apps folder.
>> Miracle! It launched OK... but not at every launch.
>
> In the other report (bug #623640), one user had described that the crash
> depends on which other applications had been launched before
> (re-)starting Inkscape (MS Word 2008 + Safari + Preview -> Inkscape
> crashes, comment #20). It seems to be a temporary but recurring issue,
> possibly initially triggered by certain color profiles installed by
> third-party applications (Adobe, MS, Printer drivers, etc.) - also
> indicated by another user reporting that repairing (corrupt) color
> profiles with ColourSync had helped to prevent these types of crashes.
>
>> (Should I uninstall this version XQuartz 2.7.0?)
>
> Xquartz is the development version of the stable X11 installed and
> updated by Apple. It's up to you to decide whether to use the stable
> version or a release from the development branch. Note that simply
> trashing the Xquartz application does _not_ uninstall Xquartz (it will
> possibly leave you with a broken X11 installation where neither Xquartz
> nor the default X11 will auto-launch on demand any more). Please read
> the documentation and FAQ on xquartz.macosforge.org if you decide to
> revert to Apple's X11 as default X server, or ask on one of the related
> mailing lists for advice (Apple's X11-users, or xquartz-dev).
>
> I...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.