https://bugs.kde.org/show_bug.cgi?id=473430
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #18 from Vince Dugar ---
(In reply to caulier.gilles from comment #16)
> If Exiv2 corrupt file and not ExifTool, well the bug is certainly located in
> Exiv2 library. Please report this problem to Exiv2 project for github:
>
>
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #17 from Vince Dugar ---
(In reply to caulier.gilles from comment #16)
> If Exiv2 corrupt file and not ExifTool, well the bug is certainly located in
> Exiv2 library. Please report this problem to Exiv2 project for github:
>
>
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #16 from caulier.gil...@gmail.com ---
If Exiv2 corrupt file and not ExifTool, well the bug is certainly located in
Exiv2 library. Please report this problem to Exiv2 project for github:
https://github.com/Exiv2/exiv2
Gilles Caulier
--
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #15 from Maik Qualmann ---
To do this automatically during the digiKam start scan, activate the option
"Reread metadata if file is changed" in the metadata settings. Not the album
monitoring option.
Maik
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #14 from Vince Dugar ---
Found it! Album > Reread Metadata from Files -- shows the changes make to the
file -- viewed in digiKam on the Windows machine. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #13 from Vince Dugar ---
Looking better now. After making the ExifTool changes below (running on my
chromebook), I can write tags to images without causing file corruption.
Thank you for the advice!
As a side note, I know the image file
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #12 from Maik Qualmann ---
The problem will surely be related to the virtual machine in Chrome OS.
Please activate writing with ExifTool with the digiKam-8.2.0 version in the
digiKam settings under Metadata. Please test whether the problem
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #11 from Vince Dugar ---
It still fails with 8.2.0 -- Image thumbnail becomes a JPG icon and fails
to load when I tried to apply a tag.
[image: image.png]
- Vince
On Wed, Aug 16, 2023 at 2:46 PM Vince Dugar wrote:
> I was leary of
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #10 from Vince Dugar ---
I was leary of appimage because of startup time and the fact that it wanted
me to download the support files for face recognition. But I tried it
again and it's running 8.2.0 on my chromebook. I had to run AppRun
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #9 from caulier.gil...@gmail.com ---
Why not AppImage. Nothing is installed on your system, all run in memory. Do do
it for you and we support this kind of bundle, not the linux standard package.
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #8 from Vince Dugar ---
PS -- Can you give me the 'apt install' syntax to install digiKam on Debian
from a repository? I'd rather not run an appimage.
Thanks,
Vince D
On Wed, Aug 16, 2023 at 10:36 AM Vince Dugar wrote:
> Thank you Maik,
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #7 from Vince Dugar ---
Thank you Maik,
So I just learned something -- that I can't rely on 'apt install' to get
the latest version of xyz! I'd think that would be administered...
I'll make another attempt to install (8.2.0) and see what
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #6 from Maik Qualmann ---
At the moment I just wanted to see the debug output in the terminal, which is
activated with the command before you start digiKam:
export QT_LOGGING_RULES="digikam*=true"
But I can see from your GDB backtrace
https://bugs.kde.org/show_bug.cgi?id=473430
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Tags-Keywords |Metadata-Engine
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #5 from Vince Dugar ---
vdugar@penguin:~$ version
Static hostname: penguin
Icon name: computer-container
Chassis: container
Machine ID: 0915979d79cf481ca6db3fcd03b9292c
Boot ID:
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #4 from Vince Dugar ---
Sorry, have to sign off for today. Will get back to you tomorrow as
needed.
- Vince
On Tue, Aug 15, 2023 at 4:49 PM Vince Dugar wrote:
> Hi Maik,
>
> I'm a retired engineer / programmer (C, Javascript) and rusty.
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #3 from Vince Dugar ---
Hi Maik,
I'm a retired engineer / programmer (C, Javascript) and rusty. But maybe
this is what you're looking for from my terminal...
Thread 45 "Thread (pooled)" hit Catchpoint 1 (exception thrown),
https://bugs.kde.org/show_bug.cgi?id=473430
--- Comment #2 from Maik Qualmann ---
I understand correctly that they are running the built-in virtual machine with
Debian 11 in current Chrome OS Book?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=473430
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
20 matches
Mail list logo
