I am running Inkscape 1.4 on Windows 10. I upgraded to 1.4 about a month ago, and it has worked without issue since then - until yesterday.
When trying to open any .svg file, I get the following error, "Unspecified fatal error encountered, aborting." I even get the error when just trying to open a new document.
I have uninstalled and re-installed Inkscape 1.4 using both the .msi and the .exe file, and the error persists.
@gwarren2525 I can't find the issue, but someone reported this on Gitlab, and the solution is to delete the Inkscape preferences by pasting this: %APPDATA%\Roaming\inkscape\ into the file explorer's URL bar, and deleting preferences.xml within, then restarting Inkscape. The problem seems to stem from an incorrect part of the software recording its data in the preferences.
UPDATE: It seems that the method above isn't working. If all fails try the Microsoft Store version, as that is known to work regardless of whether the original install starts or not.
Itinx - you have a link to that at gitlab? Maybe some keywords for it so I have search it. I would like to follow that. Might explain some of the bizarre issues I have been having with 1.4.
i got the same issue and found a solution for windows user, you can uninstall the inkscape and then reinstall it from microsoft store, but the current version that you can get in microsoft store is 1.3.2, its not updated to 1.4 version yet. If anyone found another solution for this problem please tell us in this section
I have windows 11 with Inkscape 1.4 and have had this issue on previous Inkscape versions. (not sure how long it dated back). But the error message "unspecified fatal error encountered, aborting" pops up when i am trying to modify a font. whenever I open svg file from a font created in font forge or other editors. trying to edit or add a font glyph or modifying will trigger error immediately. I tried creating a xml file totally basic and open it up in Inkscape also triggers the error. here is the xml text.
I have the same problem. Using 1.4 on Windows 11. All was working beautifully for weeks then all of a sudden it crashed with the "Unspecified fatal error encountered. Aborting." It happened in the middle of an inkscape session and now I can't open any .svg files. I have tried uninstalling and reinstalling, I have cleared my registry file of all inkscape and inkview references, checked my SSD drive for any errors, and rebooted multiple times, but nothing seems to let me open any of the files. I finally uninstalled 1.4 and reinstalled 1.3.2 instead and I seem to be up and running again (at least for now).
Same issue just happened today. Only happens on a couple files, but i have been working on the same files for the last couple days, even this morning. Came back to do some more work and all of a sudden started getting the error. I can still open other files. I'm on Using 1.4 on Windows 11. I have uninstalled, installed 1.3.2. Same issue. uninstalled and went back to 1.4. Any help is appreciated. I don't want to lose all this work. Thanks.
I'm experiencing the same issue. Inkscape 1.4 on Windows 10, 64bit.
Everything worked fine until a week or two ago. Then I was unable to start Inkscape.
I uninstalled Inkscape, deleted %APPDATA%\Roaming\inkscape\ and installed Inkscape 1.4 again. The very first run passed well and the program ran. Create a new blank document, close the program, then try to open it again, but hit 'Unspecified fatal error encountered, aborting.'. So there was no attempt to open any file.
All works fine in VirtualBox on clean Windows 10 with the latest updates KB5048652, KB4023057, KB5001716, and KB5020683. I had to finish in VirtualBox my SVG file started 3 weeks ago on my main machine where Inkscape failed to start.
EDIT: Confirming @ltlnx 2nd solution works - version from Microsoft Store run and open SVG files. Just it's old version 1.3.2 :(
Was working fine on 1.3.2 from the MS Store, but I'm Getting the error again. Tried uninstalling and reinstalling. Still get the error on certain files.
I'm getting the same issue. Created and edited .SVG yesterday & exported OK. File opened this morning to correct a couple of text errors (no change to fonts). Tried to export - FATAL ERROR message.
I have uninstalled and reinstalled but the programme will not open, even for a new document. Same error is recurring. I need this file for an ad. deadline. HELP PLEASE!
I'd try uninstalling Inkscape and renaming the user profile C:/Users/yourusername/AppData/Roaming/inkscape to C:/Users/yourusername/AppData/Roaming/inkscapeOLD. Then install Inkscape 1.3.2 (using the .msi installer) and see if it behaves properly.
If that does not work, I'd try installing the version 1.3.2 from the Microsoft Store.
Tyler - I came across a few older extensions (that I installed a few years ago) that were causing issues. Resetting the preference file didn't fix it. Uninstalling/Reinstalling didn't fix it. Your method seemed to fix an unrelated issue to this post.
I'm suggesting going beyond deleting the preferences.xml and clobbering the user profile, which would include extensions, symbols, etc... the whole lot.
Off topic - Installed the 1.5 dev version as you posted. Noticed the native (Windows) open/save is not available. I threw a fit about this during the 1.4 betas and the native was put back in. The GTK version of this is simply not ready for prime time and to be honest it is a piece of crap for 70% +- of Inkscape users. This actually hindered me in testing the betas. If the 1.5beta comes out with the same lack of native open/save I will (and many others) will have the same stupid issue.
I am running Inkscape 1.4 on Windows 10. I upgraded to 1.4 about a month ago, and it has worked without issue since then - until yesterday.
When trying to open any .svg file, I get the following error, "Unspecified fatal error encountered, aborting." I even get the error when just trying to open a new document.
I have uninstalled and re-installed Inkscape 1.4 using both the .msi and the .exe file, and the error persists.
@gwarren2525 I can't find the issue, but someone reported this on Gitlab, and the solution is to delete the Inkscape preferences by pasting this:
%APPDATA%\Roaming\inkscape\
into the file explorer's URL bar, and deleting preferences.xml within, then restarting Inkscape. The problem seems to stem from an incorrect part of the software recording its data in the preferences.UPDATE: It seems that the method above isn't working. If all fails try the Microsoft Store version, as that is known to work regardless of whether the original install starts or not.
UPDATE 2: Confirmed solution here: https://inkscape.org/forums/beyond/unspecified-fatal-error-encountered-aborting/#c77924
Itinx - you have a link to that at gitlab? Maybe some keywords for it so I have search it. I would like to follow that. Might explain some of the bizarre issues I have been having with 1.4.
I remember it having something to do with the preferences, in particular
/options/onimport
; but I can't find the issue. I'll ask around.Itinx - deleting preferences.xml didn't seem to fix it. I still get the same error.
I have the same issue
@gwarren2525 @chaki.cheri Can you upload your preferences.xml (or the whole inkscape folder) somewhere?
Has any progress been made to fix this? I still can't use 1.4 on one of my systems. None of the fixes above seem to work.
i got the same issue and found a solution for windows user, you can uninstall the inkscape and then reinstall it from microsoft store, but the current version that you can get in microsoft store is 1.3.2, its not updated to 1.4 version yet. If anyone found another solution for this problem please tell us in this section
I have windows 11 with Inkscape 1.4 and have had this issue on previous Inkscape versions. (not sure how long it dated back). But the error message "unspecified fatal error encountered, aborting" pops up when i am trying to modify a font. whenever I open svg file from a font created in font forge or other editors. trying to edit or add a font glyph or modifying will trigger error immediately. I tried creating a xml file totally basic and open it up in Inkscape also triggers the error. here is the xml text.
<svg xmlns="http://www.w3.org/2000/svg">
<defs>
<font id="testFont" horiz-adv-x="1000">
<font-face font-family="TestFont" units-per-em="1000" />
<missing-glyph horiz-adv-x="500" />
<glyph unicode="A" d="M100,0 L200,100 L100,200 L0,100 Z" horiz-adv-x="1000" />
</font>
</defs>
</svg>
I have the same problem. Using 1.4 on Windows 11. All was working beautifully for weeks then all of a sudden it crashed with the "Unspecified fatal error encountered. Aborting." It happened in the middle of an inkscape session and now I can't open any .svg files. I have tried uninstalling and reinstalling, I have cleared my registry file of all inkscape and inkview references, checked my SSD drive for any errors, and rebooted multiple times, but nothing seems to let me open any of the files. I finally uninstalled 1.4 and reinstalled 1.3.2 instead and I seem to be up and running again (at least for now).
Same issue just happened today. Only happens on a couple files, but i have been working on the same files for the last couple days, even this morning. Came back to do some more work and all of a sudden started getting the error. I can still open other files. I'm on Using 1.4 on Windows 11. I have uninstalled, installed 1.3.2. Same issue. uninstalled and went back to 1.4. Any help is appreciated. I don't want to lose all this work. Thanks.
I'm experiencing the same issue. Inkscape 1.4 on Windows 10, 64bit.
Everything worked fine until a week or two ago. Then I was unable to start Inkscape.
I uninstalled Inkscape, deleted %APPDATA%\Roaming\inkscape\ and installed Inkscape 1.4 again. The very first run passed well and the program ran. Create a new blank document, close the program, then try to open it again, but hit 'Unspecified fatal error encountered, aborting.'. So there was no attempt to open any file.
All works fine in VirtualBox on clean Windows 10 with the latest updates KB5048652, KB4023057, KB5001716, and KB5020683. I had to finish in VirtualBox my SVG file started 3 weeks ago on my main machine where Inkscape failed to start.
EDIT: Confirming @ltlnx 2nd solution works - version from Microsoft Store run and open SVG files. Just it's old version 1.3.2 :(
Was working fine on 1.3.2 from the MS Store, but I'm Getting the error again. Tried uninstalling and reinstalling. Still get the error on certain files.
I'm getting the same issue. Created and edited .SVG yesterday & exported OK. File opened this morning to correct a couple of text errors (no change to fonts). Tried to export - FATAL ERROR message.
I have uninstalled and reinstalled but the programme will not open, even for a new document. Same error is recurring. I need this file for an ad. deadline. HELP PLEASE!
I'd try uninstalling Inkscape and renaming the user profile C:/Users/yourusername/AppData/Roaming/inkscape to C:/Users/yourusername/AppData/Roaming/inkscapeOLD. Then install Inkscape 1.3.2 (using the .msi installer) and see if it behaves properly.
If that does not work, I'd try installing the version 1.3.2 from the Microsoft Store.
@metalpetalUK, if you would like to have your SVG file checked for integrity you can PM me for my email addy https://inkscape.org/~TylerDurden/
Tyler -
I came across a few older extensions (that I installed a few years ago) that were causing issues. Resetting the preference file didn't fix it. Uninstalling/Reinstalling didn't fix it. Your method seemed to fix an unrelated issue to this post.
I'm suggesting going beyond deleting the preferences.xml and clobbering the user profile, which would include extensions, symbols, etc... the whole lot.
OK, now there's a confirmed workaround. Bear with me:
The reason for this has yet to be known, but hey, it works!
@Itinx
Off topic -
Installed the 1.5 dev version as you posted. Noticed the native (Windows) open/save is not available. I threw a fit about this during the 1.4 betas and the native was put back in. The GTK version of this is simply not ready for prime time and to be honest it is a piece of crap for 70% +- of Inkscape users. This actually hindered me in testing the betas. If the 1.5beta comes out with the same lack of native open/save I will (and many others) will have the same stupid issue.