So in your settings you define a library location (if you didn’t, it should default to ~/Pictures).
“Copy Photos” will copy the photos from the folder you chose to import from into the library location, putting them into the folder structure (usually Year/Month/Day).
“Import in Place” will not copy the image files but put their current paths into the database that backs Shotwell.
Dropping images from a folder into Shotwell corresponds to “Copy Photos”
You can also just copy the files into your chosen library location, Shotwell should pick them up as well (should work without a restart, but might need one)
Yes I overrode that to make it a sub folder in Pictures called Photo Library, reason being I want other images in Pictures folder that I don’t want in Shotwell. Temp work stuff etc, I only want Shotwell to have our family photos in.
Copy Vs Import - Aaah, gotcha, that makes sense thanks.
I didn’t actually know that was possible, I did mean to drop from say my camera card or phone, into the Photo Library folder in Files app (i.e. my Shotwell library folder, but via Files app rather than via Shotwell GUI)
Bingo, that solves the anove problems, not much of a workaround for me as I like moving files around so I know what’s happening, I prefer that to import functions generally.
Just two questions to harass you about left …
Could you comment on which installation method you think is best (Flathub, Fedora Flatpak, Fedora RPM) please?
I have only one gripe/complaint about Shotwell, you can’t use the space bar to preview/open an image. Files can do this, Apple Photos always did this, Files can do it for any file actually even PDFs, so it’s a common action by Linux users (in Gnome at least). Is there any way to make the space bar open files instead of ‘Enter’?
Thanks so much for your help. (Shotwell looks awesome and such a refreshing change from Apple Photos (which they spy on and analyse, going by my background processes, and web searches)
I would pick either the flathub flatpak or the RPM. The Fedora Flatpak imho combines the worst of the too.
Between the other two, it depends. The unsandboxed rpm has potentially fewer issues accessing cameras and sometimes the document portal seems to interfere a bit with the imports in the flatpak.
On the other hand, the flatpak currently has more supported image formats and is potentially updated directly after upstream release (though Fedora is quite quick there as well)
So. It depends on what you want, really.
In theory, space should select and enter should open. the first is definitely broken, the second worked last time I tried.
Thanks, but is there a way to make space open an image? Is there a setting somewhere for this or maybe another way to make it happen in Gnome settings?
Hi again. Well I ran the import today direct from an external backup drive (my entire photo library from Mac). It was running well for a few hours before I left the desk, about half way through. I have just returned to machine and noticed Shotwell is not running, and I see a notification that it crashed. Bit worried and unsure what to do now. I managed to access the crash report but trying to copy it to paste it here or into a doc to send you is troublesome, impossible in fact as can’t select all off the error log.
Do you have any advice on how to get you the error log? I tried clicking on Report and it popped up a window asking for Bugzilla API key and all sorts of complicated stuff I don’t understand!
Also do you have any advice on what I should do next, re-run the import and it will hopefully skip those already imported? I won’t proceed or do anything for now, grateful for your thoughts when you have a sec.
There are some known but hard to point out race conditions in long-running imports that cause shotwell to abort.
First step would be to look at the ~/.cache/shotwell/shotwell.log for the last few lines in there
Seocnd, doing a coredumpctl dump shotwell should give a rough first set of information we can go on from further and see if it’s one of the existing issues.
Depending on the issue, you can just re-run Shotwell until you’re done, or need to identify the image, but one of those two will tell
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:02 [CRT] Directory Canon with 6656 entries considered invalid; not read.
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:02 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:02 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:04 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:04 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:04 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:04 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:05 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:05 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:06 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:06 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:07 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:07 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:08 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:08 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:10 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:10 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:10 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:10 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:10 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:10 [WRN] Invalid JPEG preview image.
L 14480 2024-07-04 15:52:10 [WRN] Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored.
L 14480 2024-07-04 15:52:10 [WRN] Invalid JPEG preview image.
Huh. that is new. a memory corruption on import :-/ What are you importing, jpegs? 40k you said? I will try to setup a reproducer. Sorry about that :-/
Memory corruption? Sounds scary!! (I recently bought this machine and ran a full memtest86 on all RAM, it tested good, in case that’s relevant.
I took an export of Photos App library on Mac, using the ‘export unmodified originals’, and I chose jpegs yes, that’s not to say there aren’t some other types in there from 20 years of imports, and some video files from digi cameras and phones too, but should be 95% jpegs
Should I go ahead and try again to import it all, or hang fire? (waiting is fine, no urgency)
No you can go ahead, It might just be that shotwell will crash again during the process. It should be able to pick up where it left off. The memory corruption is something that happens inside Shotwell, nothing from your system.
I ran the import again, looked like it was going ok but I came back to computer a couple of hours ago and it’s still ‘importing’ the exact same image as it was then right now, so I am guessing it has hung. What’s the best way to kill it and run again? I am assuming I should do that?
thanks
Thanks, I went to bed last night and left it as it was, just come back and it says import complete, so I guess it wasn’t hung (or it recovered). It says 27,775 duplicate photos not imported, which is entirely possible between the number of dupes apple seems to have created in my library (even when choosing the defunct and misleading ‘export unmodified originals’!), and given that I have done a few attempts.
Not sure how to compare to what I had on Photos, bit nervous they are not all there but not much I can do to verify without spending hours and hours checking each one!
Looks good. For fun I am gonna run it again, ‘just in case’
Thanks for all your help here, and I will be curious to hear what you think happened above, not vital though now that i seem to have it done
hahah. Happy to be of service
My import has just finished, reported tens of thousands of duplicates and only ONE photo imported. Looks like I should have my photo library in Shotwell now!
More troubles. Wonder if this is intended or a bug due to my OS (Fedora Workstation).
I have photos in Shotwell. I want to grab say 5 or 10, to put in a folder somewhere or send to someone like in Signal or email etc.
i can’t see any way to select some photos and right click copy, is it not possible to ‘copy’ from Shotwell library?
I tried the ‘send to’ option (found in right click menu), but it first refused due to long subject, so i tried just one, and it opened a blank email in Thunderbird and weirdly didn’t attach an image but a local file link in the subject line?!
What’s the ‘done thing’ for wanting to send someone (or move/copy somewhere else) some photos from Shotwell please? being a new user I’m assuming/hoping it’s ‘user error’!
The way this was supposed to work is with the old “Send To” from Nautilus which no longer exists and drag and drop - Drag and Drop only works somewhat reliably in X11 and even there it is super hacky and picky about the target applications.
This will only be fixed for 33, sorry. You would have to manually export the files to a temporary folder and use those through the file manager.