You are not logged in.
This is weird. There is a bug somewhere, but it is not with sxiv.
If I open an image with sxiv (or sxiv-git), it writes a file to home, with a filename like 1562468903.exiv2_temp
┌─[Shiv ~]
└─╼ file 1562468903.exiv2_temp
1562468903.exiv2_temp: empty
stat 1562468903.exiv2_temp
File: 1562468903.exiv2_temp
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fe02h/65026d Inode: 5769179 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 1000/ jason) Gid: ( 1000/ jason)
Access: 2019-07-07 15:08:23.961102476 +1200
Modify: 2019-07-07 15:08:23.961102476 +1200
Change: 2019-07-07 15:08:23.961102476 +1200
Birth: 2019-07-07 15:08:23.961102476 +1200If I open several images, one temp file is created for each one, polluting home.
Now the weird bit. sxiv does not depend on exiv2. If I remove exiv2 from my system, sxiv creates no temp files.
exiv2 is a dependency of Gimp. Opening, editing, or saving an image in Gimp creates no temp file.
So the bug appears to be with exiv2, but I'm not sure how to narrow it down further. Any pointers?
┌─[Shiv ~]
└─╼ pacman -Q sxiv exiv2 gimp
sxiv 25-1
exiv2 0.27.1-1
gimp 2.10.12-1Offline
Probably something in the image-info script?
grep -r exiv2 ~/.config/sxivLast edited by lolilolicon (2019-07-07 11:47:11)
This silver ladybug at line 28...
Offline
Thanks! I'm guessing that would make exiv2 at least an optdepends of sxiv...
Offline
It would seem you're keeping an image-info pre https://github.com/muennich/sxiv/commit … bfd938fca0 ?
Right now there seems no reference to exiv2 in the upstream scripts (nor the one provided by the repo package.
Offline
Yep: my bad ![]()
Offline