Inkscape crashes when opening the 'fill and stroke' window

Bug #1486090 reported by jkokorian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned

Bug Description

When I press ctrl-shift-F or open the fill and stroke settings window from the menu, inkscape closes instantly.

I had a layers window open and 'broken-out' of inkscape on another monitor, so I figured that would be the problem. However, 'align-and-distribute' opened just fine, as well as the text properties window. No idea what's causing this...

OS: windows 7 enterprise
inkscape version: 0.91

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

Please add information about OS/platform and Inkscape version (see Inkscape menu 'Help > About Inkscape') to the bug description, thank you.

Changed in inkscape:
status: New → Incomplete
Revision history for this message
jkokorian (jkokorian) wrote :

Sorry, I edited the description

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

More questions:
1) Did you use the 32bit or 64bit installer for Inkscape 0.91?
2) Does it happen with a new document (based on the default template) too?
If the crash only happens with certain documents, please attach a test case to allow investigating on other systems.
4) Does it happen with default preferences? If so, please attach the current preferences file to allow further investigation.

Location of preferences file:
%APPDATA%\inkscape\preferences.xml

On Windows 7, %APPDATA% usually is
C:\Users\{username}\AppData\Roaming

To reset the preferences:
1) quit all running Inkscape processes
2) navigate in Explorer to %APPDATA%\inkscape
3) rename the file 'preferences.xml' (to allow inspection later on in case this is the trigger)
4) launch Inkscape (a new 'preferences.xml' file will be created with default settings)

Revision history for this message
jkokorian (jkokorian) wrote :

1) 64 bit
2) yes
4) I'm not sure if I'm using the default preferences. I've attached the file

Ah, resetting the preferences solved the problem. By diff'ing the old preferences with the fresh ones I could see that the old preferences file was actually __completely__ different that the fresh one. Probably because it was created with an old version and left in place when I upgraded to the new inkscape.

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

Crash reproduced with Inkscape 0.48.5, 0.91 r13725 and 0.91+devel r14326 on OS X 10.7.5 using the reporter's original preferences file.

tags: added: crash preferences styles
Changed in inkscape:
importance: Undecided → High
status: Incomplete → Confirmed
Revision history for this message
su_v (suv-lp) wrote :

Full backtrace from Inkscape 0.91+devel r14326 (debug build) attached.

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

Crash not reproduced after deleting line 543 from the corrupted preferences file:

$ diff -u 1486090-preferences.xml.old{,.edited}
--- 1486090-preferences.xml.old 2015-08-28 18:12:14.000000000 +0200
+++ 1486090-preferences.xml.old.edited 2015-08-28 18:22:06.000000000 +0200
@@ -540,7 +540,6 @@
       <dash
          id="dash-0110-0110"
          style="stroke-dasharray:0.1,0.1" />
- <da />
     </group>
   </group>
   <group
$

Revision history for this message
jazzynico (jazzynico) wrote :

~suv> Crash not reproduced after deleting line 543 from the corrupted preferences file

Inkscape should have correctly detected that the file is corrupted and reverted to the default preferences (see bug #911700 "Preferences.xml file recovery" ). Preferences check really needs to be improved.

Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
Jonathan Hofinger (jhofinger) wrote :

Replicated with 0.92.4, however, the issue seems fixed in 1.1-dev (2a5d477, 2020-01-18), Windows 10. Please reopen on http://inkscape.org/report if the problem occurs again. In this version, Inkscape simply ignores the bad XML tag, and it is still there after closing Inkscape.

Closed by: https://gitlab.com/jhofinger

Changed in inkscape:
status: Triaged → Invalid
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.