I'm completely new to Inkscape and have just startet doing tutorials (I'm on Ubuntu 20.04.5 LTS).
The problem is I cannot save the projects.
When I hit save the first time, I don't get a warning, but the file that's saved does not have the Inkscape Icon and when I try to open it I get this message:
"Could not detect file format. Tried to open it as an SVG anyway but this also failed."
Second time I try to save the project I get this message:
"No Inkscape extension found to save document (/run/user/1000/doc/ 602bbfac/Test). This may have been caused by an unknown filename extension."
I've tried everything I could come up with, including changing the file association, testing with free .svg files etc.
The file, when saved, does not have the Inkscape Icon (see attached), but it is recognized as .svg (see attached) and it is set to open in Inkscape (after I changed it from Image Viewer) (see attached).
I have so far discovered that when saving (both save and save as) I have to type in .svg myself - and then I can open the file from within Inkscape via Open - so that's a workaround I guess. But, something seems to be broken since the icon still is wrong and .svg files do not open in Inkscape (the do not open at all).
Image below shows bottom of save as window in my system. Note that Inkscape SVG is selected. Then is red dot what you are seeing?
Double clicking on your svg file should open it.
Could you navigate to /home/user_name/.local/share/applications and then click on magnifier (Search Documents) then search ink and take screenshot of result?
a: yes, I see the "Inkscape SVG (*.svg)" (see attached) b: no - double-clicking the file in the folder does not work c: no, I don't see that red dot - I only see the .svg files that are already there (see attached) d: no luck with navigating to: /home/user_name/.local/share/applications (with changed user name of course) I just get "no results found"
Hey, OP has probably already found a solution to this, but just wanted to write this for anyone else having similar issues. I had this problem, still no clue why, but I noticed that even though my file said it was a .svg in file properties, it didn't actually have the svg extension in the filename - like, when you did 'ls' in terminal, the file came up as 'file' instead of 'file.svg'.
I went back into inkscape and hit save, it came up with the message seen in OP's and sent me to save as menu, and I just manually typed the .svg on the end of whatever filename I was using.
Weird issue, but now saving works for me, so I'm not complaining.
Anywho, hope this is helpful for someone.
(Using Inkscape 1.2.2 on Ubuntu 22.04, for reference.)
Just jumping in here to say that I've had the exact same issues (and then some).
The best I can describe my situation is that saving (or attempting to) seems to trigger some funky interactions with the filesystem. I'm almost inclined to suggest that simply leaving Inkscape open for long enough triggers the same kind of error state, but I haven't verified if I'm just thinking that because I've actually tried to save/saved then forgotten that I did that after leaving it open for a while, and then the problems come into play when I try to save later.
I've encountered the same issues as others have here and on the issue tracker - saving not including the ".svg" part, it automatically resetting to Home, unable to save etc. I have had these issues fairly consistently for about 6 months now. At first I thought this was because of me not including ".svg" on the end of the filename, as sometimes I found that if I did that it didn't get into the broken state and I could save and re-save. However, sometimes even doing that seemed to cause issues (again though, this could just be a case of me forgetting that I'd tried to save without the extension). I put the issues down to permissions on my machine (I run dual-boot on my second drive, and sometimes GDrive can lock files to Windows). Often times this rears its head as an inability to export - something that I've found I could get around by rebooting Inkscape (I used to think that I could export only to certain folders - specifically definitely Ubuntu-owned ones such as Desktop or Downloads, but I am no longer sure).
However, I have since encountered this error again, and fairly severely. I cannot remember if I tried to save without the extension or not, but Inkscape got into a state where it would not save the file (this was a first-save as well, so I was desperately trying to find a way to do it). I had had the file open for a number of hours, as I was using it to organise notes. It would not let me Save, Save As or Export, and if I opened other windows to try to copy into and save they also would not allow for saving - basically all interaction with the filesystem was dead. However, I did find that some svg files I had previously worked on could be opened, and changes saved to them. I tried copying one such file in the file browser and then copying the SVG data into it across Inkscape instances, however that didn't work. I did find, however, that I could edit the original svg file and copy the SVG data into and save that - the copy, however, remains unopenable.
Interestingly, the copied svg appears to be corrupted, with a premature end of data error. Maybe I opened it and forgot in my efforts?
I'm running Inkscape 1.2, installed via the software centre, and am on Ubuntu 22.04.3 LTS. I plan to uninstall Inkscape and then reinstall it from the website at version 1.3. I'll spend a few minutes trying to explore what cause the error.
TL;DR If you've got something you really want to save and are currently unable to, right-click on the Inkscape icon -> open a new window, then in that new window, open another SVG file, then delete it's contents and copy the contents of your previous work into it and then hit save. This will delete the previous contents, so you should definitely make a copy first - just ensure that things are normal when you do that before overwriting the contents.
As a follow-up, I spent some time trying to reliably recreate the error without much luck - it did recur after saving and resaving (as well as save-as'ing) a few times, but I couldn't get it to happen repeatedly. I've upgraded to 1.3 via adding the ppa and installing through apt and 1.3 (besides having some sweet new features) seems much more stable for me in this regard (that could be an apt vs snap thing though).
Beginners' Questions Problems saving project file
Inkscape.org
I'm completely new to Inkscape and have just startet doing tutorials (I'm on Ubuntu 20.04.5 LTS).
The problem is I cannot save the projects.
When I hit save the first time, I don't get a warning, but the file that's saved does not have the Inkscape Icon and when I try to open it I get this message:
"Could not detect file format. Tried to open it as an SVG anyway but this also failed."
Second time I try to save the project I get this message:
"No Inkscape extension found to save document (/run/user/1000/doc/
602bbfac/Test). This may have been caused by an unknown filename
extension."
Any ideas what to do?
Hi UM22.04 Inkscape 1.2.1
Just a really wild guess with limited information supplied. Sounds like you are working in a tutorial (that's good)
If you are doing tutorial, try clicking File / Save As and note location your choice and (you can change name if you want) and see if that works.
Or open Inkscape and draw a square or something and hit save.
Below is probably not the problem.
Also if navigate to a .svg file right click on it to see if it says open with Inkscape, if not you may choose open with other applications
Thanks @mendy
I've tried everything I could come up with, including changing the file association, testing with free .svg files etc.
The file, when saved, does not have the Inkscape Icon (see attached), but it is recognized as .svg (see attached) and it is set to open in Inkscape (after I changed it from Image Viewer) (see attached).
I have so far discovered that when saving (both save and save as) I have to type in .svg myself - and then I can open the file from within Inkscape via Open - so that's a workaround I guess. But, something seems to be broken since the icon still is wrong and .svg files do not open in Inkscape (the do not open at all).
Image below shows bottom of save as window in my system. Note that Inkscape SVG is selected. Then is red dot what you are seeing?
Double clicking on your svg file should open it.
Could you navigate to /home/user_name/.local/share/applications and then click on magnifier (Search Documents) then search ink and take screenshot of result?
How was Inkscape installed... PPA, appimage, or...?
@mendy
a: yes, I see the "Inkscape SVG (*.svg)" (see attached)
b: no - double-clicking the file in the folder does not work
c: no, I don't see that red dot - I only see the .svg files that are already there (see attached)
d: no luck with navigating to: /home/user_name/.local/share/applications (with changed user name of course) I just get "no results found"
@TylerDurden
With Ubuntu Software Center ⭐
It's version 1.2 1 as I can see...
Thank you for replying. B was just tied to a possible issue if C turned up something. It's not the problem. Will continue thinking about issue.
Another thought as suggested by TylerDurden in various posts seeming to correct all kinds of different issues.
Edit / Preferences / System / Reset Preferences then restart. Worth a try and is easy.
starting today I'm having the exact same issue as @56K, wondering if this was ever resolved?
@thx343, please share your system info and the installer you used.
also the same, version 1.2.2 in this case, on ubuntu using the software centre/snap store
Some issues in the Snap are open:https://gitlab.com/inkscape/inbox/-/issues/7807
More: https://gitlab.com/groups/inkscape/-/issues/?search=snap&sort=created_date&state=opened&label_name%5B%5D=OS%3A%3ALinux&first_page_size=20
Hey, OP has probably already found a solution to this, but just wanted to write this for anyone else having similar issues. I had this problem, still no clue why, but I noticed that even though my file said it was a .svg in file properties, it didn't actually have the svg extension in the filename - like, when you did 'ls' in terminal, the file came up as 'file' instead of 'file.svg'.
I went back into inkscape and hit save, it came up with the message seen in OP's and sent me to save as menu, and I just manually typed the .svg on the end of whatever filename I was using.
Weird issue, but now saving works for me, so I'm not complaining.
Anywho, hope this is helpful for someone.
(Using Inkscape 1.2.2 on Ubuntu 22.04, for reference.)
Just jumping in here to say that I've had the exact same issues (and then some).
The best I can describe my situation is that saving (or attempting to) seems to trigger some funky interactions with the filesystem. I'm almost inclined to suggest that simply leaving Inkscape open for long enough triggers the same kind of error state, but I haven't verified if I'm just thinking that because I've actually tried to save/saved then forgotten that I did that after leaving it open for a while, and then the problems come into play when I try to save later.
I've encountered the same issues as others have here and on the issue tracker - saving not including the ".svg" part, it automatically resetting to Home, unable to save etc. I have had these issues fairly consistently for about 6 months now. At first I thought this was because of me not including ".svg" on the end of the filename, as sometimes I found that if I did that it didn't get into the broken state and I could save and re-save. However, sometimes even doing that seemed to cause issues (again though, this could just be a case of me forgetting that I'd tried to save without the extension). I put the issues down to permissions on my machine (I run dual-boot on my second drive, and sometimes GDrive can lock files to Windows). Often times this rears its head as an inability to export - something that I've found I could get around by rebooting Inkscape (I used to think that I could export only to certain folders - specifically definitely Ubuntu-owned ones such as Desktop or Downloads, but I am no longer sure).
However, I have since encountered this error again, and fairly severely. I cannot remember if I tried to save without the extension or not, but Inkscape got into a state where it would not save the file (this was a first-save as well, so I was desperately trying to find a way to do it). I had had the file open for a number of hours, as I was using it to organise notes. It would not let me Save, Save As or Export, and if I opened other windows to try to copy into and save they also would not allow for saving - basically all interaction with the filesystem was dead. However, I did find that some svg files I had previously worked on could be opened, and changes saved to them. I tried copying one such file in the file browser and then copying the SVG data into it across Inkscape instances, however that didn't work. I did find, however, that I could edit the original svg file and copy the SVG data into and save that - the copy, however, remains unopenable.
Interestingly, the copied svg appears to be corrupted, with a premature end of data error. Maybe I opened it and forgot in my efforts?
I'm running Inkscape 1.2, installed via the software centre, and am on Ubuntu 22.04.3 LTS. I plan to uninstall Inkscape and then reinstall it from the website at version 1.3. I'll spend a few minutes trying to explore what cause the error.
TL;DR If you've got something you really want to save and are currently unable to, right-click on the Inkscape icon -> open a new window, then in that new window, open another SVG file, then delete it's contents and copy the contents of your previous work into it and then hit save. This will delete the previous contents, so you should definitely make a copy first - just ensure that things are normal when you do that before overwriting the contents.
As a follow-up, I spent some time trying to reliably recreate the error without much luck - it did recur after saving and resaving (as well as save-as'ing) a few times, but I couldn't get it to happen repeatedly. I've upgraded to 1.3 via adding the ppa and installing through apt and 1.3 (besides having some sweet new features) seems much more stable for me in this regard (that could be an apt vs snap thing though).