https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #204 from Maik Qualmann ---
Git commit fddc652e601b24b345f147d3a09b936d4e1b9b3a by Maik Qualmann.
Committed on 01/03/2024 at 21:44.
Pushed by mqualmann into branch 'master'.
add the first two desktop files for Windows
M +6-0core
https://bugs.kde.org/show_bug.cgi?id=482139
--- Comment #5 from Maik Qualmann ---
Ok, this tool is the mirroring for me.
The image is either mirrored on the horizontal or vertical center axis.
I have no difference in the mirroring between BQM and Editor. At the speed,
keep in mind that you have
https://bugs.kde.org/show_bug.cgi?id=482139
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=482132
--- Comment #9 from Maik Qualmann ---
Can you also please test the pre-release version of digiKam-8.3.0,
there is no database change in this version, download from here:
https://files.kde.org/digikam/
Maik
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=482132
--- Comment #8 from Maik Qualmann ---
Wayland would be an option under Linux and Neon means that an Snap package from
digiKam with Sandbox is probably used. But - that does not explain the behavior
under Windows10. I have now added a very large album
https://bugs.kde.org/show_bug.cgi?id=482132
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #202 from Maik Qualmann ---
We currently include anything that has an image (or video) mime type in its
*.desktop file. I see that as more of an advantage at the moment.
I still have a "pure" Ubuntu 22.04 as a VM, a
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #199 from Maik Qualmann ---
One difference that I have here is that, for example, the VLC player is also
linked to image mime. It is not listed as an image viewer in the KF5 service
menu. In fact it has an image mime entry in its list
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #197 from Maik Qualmann ---
The difference is the "Open with..." menu. Programs are listed for you and can
call up the selected image?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #193 from Maik Qualmann ---
Yes, I thought KIO was not active in the AppImage. I don't want to remove
KService for a native digiKam yet.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #189 from Maik Qualmann ---
Git commit 088dc6a74f566d420781ef5e4de24a704a7d4c7e by Maik Qualmann.
Committed on 27/02/2024 at 20:14.
Pushed by mqualmann into branch 'master'.
use new service menu also for Windows
M +52 -36 core/app
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #188 from Maik Qualmann ---
Git commit 562ba609b8407bf8e1fe84868f1b09a7270acf70 by Maik Qualmann.
Committed on 27/02/2024 at 17:58.
Pushed by mqualmann into branch 'master'.
If we compile with KIO then we still use KService
With KIO we
https://bugs.kde.org/show_bug.cgi?id=481888
--- Comment #1 from Maik Qualmann ---
I suspect that your network collection within digiKam is currently "offline".
Can you open images as a preview, or does a message appear as a tooltip?
Do you still use your network collection with anoth
https://bugs.kde.org/show_bug.cgi?id=481888
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #186 from Maik Qualmann ---
Git commit 554f19e0ec52e4d95d707a4442def2aebaaae6b2 by Maik Qualmann.
Committed on 27/02/2024 at 07:36.
Pushed by mqualmann into branch 'master'.
remove KService++
M +0-2core/app/main/main.cpp
M +0
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #185 from Maik Qualmann ---
Git commit 2ca6e26979eddbf703107c197a39cb7f2195ed32 by Maik Qualmann.
Committed on 27/02/2024 at 07:26.
Pushed by mqualmann into branch 'master'.
remove KService++
M +3-1core/libs/threadimageio/engine
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #183 from Maik Qualmann ---
What is "Negative" in Gnome? The currently current AppImage (from February
24th, 2024) does not yet contain the last test change.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #181 from Maik Qualmann ---
Git commit 3c4f76c0c237a21064374813d3e9c509f274f7b2 by Maik Qualmann.
Committed on 26/02/2024 at 21:40.
Pushed by mqualmann into branch 'master'.
just a first hack for an open with service menu without KService
https://bugs.kde.org/show_bug.cgi?id=481858
Maik Qualmann changed:
What|Removed |Added
Component|Setup-Misc |Geolocation-Workflow
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=481858
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=481830
--- Comment #8 from Maik Qualmann ---
If my research is correct, Neon is based on Ubuntu-22.04. Since there is no
native digiKam for Ubuntu, I think you are using a Snap package with sandbox
function.
For me it is inexplicable how distributions can
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #179 from Maik Qualmann ---
Gilles,
I think we will remove KService from digiKam. I'm starting this evening to
write a parser for *.desktop files. It would have the advantage that we could
also create *.desktop files for Windows. What do
https://bugs.kde.org/show_bug.cgi?id=481830
--- Comment #7 from Maik Qualmann ---
If there are other folders in your share, but you do not see them within a
digiKam file requester, digiKam's rights are restricted.
The whole thing can be tested quickly if you use our AppImage from here (make
https://bugs.kde.org/show_bug.cgi?id=481830
--- Comment #5 from Maik Qualmann ---
The collection is recognized as unavailable. Since no file UUID is found yet, I
suspect that no file or directory is recognized. The requirement in digiKam for
a network collection to be added is that at least one
https://bugs.kde.org/show_bug.cgi?id=481830
--- Comment #3 from Maik Qualmann ---
Please activate the debug output with the following command:
export QT_LOGGING_RULES="digikam*=true"
The messages are not relevant to the problem, we need the log from the
beginning here.
Mai
https://bugs.kde.org/show_bug.cgi?id=481830
--- Comment #1 from Maik Qualmann ---
I use an SMB4k network collection myself for testing purposes and it works
without any problems. Create a debug log (terminal) from the start of digiKam
as described here:
https://www.digikam.org/contribute/
Maik
https://bugs.kde.org/show_bug.cgi?id=481830
Maik Qualmann changed:
What|Removed |Added
Severity|grave |normal
CC
https://bugs.kde.org/show_bug.cgi?id=481762
--- Comment #11 from Maik Qualmann ---
Ok, then Adobe seems to have created duplicate elements under the same
namespace URI:
Google:
http://ns.google.com/photos/1.0/container/ -> Container
http://ns.google.com/photos/1.0/container/item/ ->
https://bugs.kde.org/show_bug.cgi?id=481762
--- Comment #9 from Maik Qualmann ---
The xmp from the original image has already been processed by Adobe Photoshop
CS6.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481735
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||8.3.0
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=480345
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=481787
Maik Qualmann changed:
What|Removed |Added
Summary|Plugin stops working|Google Photo plugin stops
https://bugs.kde.org/show_bug.cgi?id=472494
Maik Qualmann changed:
What|Removed |Added
CC||rt2sba...@mozmail.com
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=481787
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC
https://bugs.kde.org/show_bug.cgi?id=481766
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=481762
--- Comment #5 from Maik Qualmann ---
Do you still have an original image to compare whether Google created duplicate
namespace URIs across Pixel Phone generations? Or whether your sample image was
created incorrectly by Photoshop.
Maik
--
You
https://bugs.kde.org/show_bug.cgi?id=481762
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=481762
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed
https://bugs.kde.org/show_bug.cgi?id=481755
Maik Qualmann changed:
What|Removed |Added
Summary|exiftool not used as|Use ExifTool as a full
https://bugs.kde.org/show_bug.cgi?id=481755
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Severity
https://bugs.kde.org/show_bug.cgi?id=480134
Maik Qualmann changed:
What|Removed |Added
CC||kaiz...@gmail.com
--- Comment #178 from Maik
https://bugs.kde.org/show_bug.cgi?id=481753
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=480345
Maik Qualmann changed:
What|Removed |Added
CC||korti...@gmail.com
--- Comment #18 from Maik
https://bugs.kde.org/show_bug.cgi?id=481735
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #176 from Maik Qualmann ---
Rename/remove freedesktop.org.xml
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #20 from Maik Qualmann ---
Git commit 27aa2d0c26e25268253c98aa9ad6ebbea39d3d78 by Maik Qualmann.
Committed on 22/02/2024 at 19:49.
Pushed by mqualmann into branch 'master'.
For WAL mode we need another error code
SQLite no longer
https://bugs.kde.org/show_bug.cgi?id=479473
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #17 from Maik Qualmann ---
A note, you should also activate WAL mode in the digiKam settings under
Database.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479900
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=481630
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||8.3.0
Resolution
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #15 from Maik Qualmann ---
I can reproduce the lost transactions problem here with a SQLite database under
stress. The problem may be related to Qt6. I see another SQLite error code that
we need to catch, the SQLITE_LOCKED_SHAREDCACHE (262
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #13 from Maik Qualmann ---
Gilles, ignore my Comment 12.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #12 from Maik Qualmann ---
Gilles,
the problem is related to compiling with MSVC, we need to set
"SQLITE_DEFAULT_LOCKING_MODE=1" (Exclusive) as the compile option for SQLite.
The default is "Normal".
We have to see
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #11 from Maik Qualmann ---
The locked database issue is definitely the cause of tags disappearing or not
being saved. It is normal for a SQLite database to be locked during a write
operation, in this case we simply wait until
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #39 from Maik Qualmann ---
I can extract the MP4 video from the JPG image from my Galaxy S8 using the
following EXifTool command:
exiftool -b -Samsung:EmbeddedVideoFile image.jpg > image.mp4
It would be interesting to see if anything
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #8 from Maik Qualmann ---
You don't have debug mode enabled, but warnings still appear. The problem is
clear:
Cannot save metadata with Exiv2 backend: (Error # 38 : "Size of XMP JPEG
segment is larger than 65535 bytes"
This a
https://bugs.kde.org/show_bug.cgi?id=481630
--- Comment #4 from Maik Qualmann ---
There are actually no changes in the relevant code parts compared to 8.2.0 that
could cause this problem. Can you narrow it down to specific images or a
specific camera/image format? Maybe a debug log from
https://bugs.kde.org/show_bug.cgi?id=481630
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
https://bugs.kde.org/show_bug.cgi?id=481011
--- Comment #10 from Maik Qualmann ---
After yesterday's update of openSUSE to KF-6.0.0-git and Qt-6.6.2, this problem
no longer occurs.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481484
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||8.3.0
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481484
Maik Qualmann changed:
What|Removed |Added
OS|Other |Microsoft Windows
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=481484
Maik Qualmann changed:
What|Removed |Added
Component|Preview-Image |Plugin-DImg-HEIF
CC
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #170 from Maik Qualmann ---
Ok, the AppImage now works here with openSUSE, which is probably clear because
of the file from openSUSE. I looked for which entry in the file was causing the
problem for me, this entry is it:
Loop
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #167 from Maik Qualmann ---
It's definitely the freedesktop.org.xml, the DIFF to my system from openSUSE is
no longer as big as before, but still significant. I can change my
freedesktop.org.xml (remove types), the loop doesn't occur
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #161 from Maik Qualmann ---
What's interesting is that when I swap the files with those from my openSUSE
system, there is no loop either.
This means that the contents of the files lead to the loop.
Maik
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #160 from Maik Qualmann ---
Two files in the AppImage cause the loop, both files must not exist:
APPIMAGE_BASE/usr/share/mime/packages/freedesktop.org.xml
APPIMAGE_BASE/usr/share/mime/mime.cache
If I remember correctly
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #158 from Maik Qualmann ---
Ok, I'm a little further along. I unzipped the AppImage. It's something inside
the "share" folder. If I rename this, it works without looping and the KService
menu is correct. I'll narrow it down fur
https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #154 from Maik Qualmann ---
There is no thumbnail database update between 8.2.0 and 8.3.0. Your database
has probably been destroyed by the crashes (loops) and forced exits. Or there
are too many file handlers still open for the thumbnail
https://bugs.kde.org/show_bug.cgi?id=472494
--- Comment #26 from Maik Qualmann ---
Git commit 09858c9d57f92818695d8b238805811432414d34 by Maik Qualmann.
Committed on 17/02/2024 at 12:03.
Pushed by mqualmann into branch 'master'.
update Google Photo icon to the current one from 2020
M +1-1
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #16 from Maik Qualmann ---
In principle, the problem with the file path is not that common, only with file
paths whose characters are outside the current Windows code page. This should
only occur very rarely for most Windows users. We could
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #14 from Maik Qualmann ---
The problem would only be when writing metadata if ExifTool is not activated,
as we do not automatically switch to ExifTool when writing.
Maik
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #13 from Maik Qualmann ---
Yes, in case of a file read error due to file path encoding (Exiv2 Error #10),
we automatically read with ExifTool and decode the container with Exiv2 so that
all metadata is present.
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #11 from Maik Qualmann ---
We also have the problem with the file path encoding with the VCPKG build.
Which I don't understand since this build was supposed to use Windows' Utf8
API.
But it's not a problem because in this case we
https://bugs.kde.org/show_bug.cgi?id=481345
--- Comment #12 from Maik Qualmann ---
The file is still in the Windows bundle. Can you please delete the following
file as a test and try to reproduce it again:
C:\Program Files\digiKam\plugins\imageformats\qjp2.dll
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=481366
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=481366
Maik Qualmann changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481345
Maik Qualmann changed:
What|Removed |Added
Summary|I updated from version 7.6 |Crash in libJasper
https://bugs.kde.org/show_bug.cgi?id=481345
--- Comment #4 from Maik Qualmann ---
No, don't rebuild the database, the problem is clear. The libjasper library
(JPEG200) is initialized twice. We will fix it.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481366
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=481358
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=481358
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Summary
https://bugs.kde.org/show_bug.cgi?id=481345
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #2 from Maik
https://bugs.kde.org/show_bug.cgi?id=472494
--- Comment #24 from Maik Qualmann ---
With a Google Photo API key, it is not possible for a user to have a personal
one. See my Comment 10.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472494
--- Comment #18 from Maik Qualmann ---
Our API key has been deactivated again, I have to write another objection.
Since I don't know which Google policies we are violating, it will be difficult
to do anything about it.
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #13 from Maik Qualmann ---
It would also be displayed for A and B in the left sidebar if you have
activated the recursive tag view under Menu->View.
But be aware that with "A|B|C" only the tag C is actually assigned to the
https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #11 from Maik Qualmann ---
Another try:
"A|B|C" : only C is a tag of the image, A and B are not.
"A, A|B, A|B|C" : A and B and C are a tag of the image.
If you were to search for A or B in the first variant, the imag
https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #8 from Maik Qualmann ---
"A|B|C" :
[ ]A
[ ]B
[x]C
"A, A|B, A|B|C" :
[x]A
[x]B
[x]C
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #5 from Maik Qualmann ---
Yes, but only "Baker Street" has a "check", not "England" or "London", that's
the difference. Check "England" and "London" and you have the same metadata
https://bugs.kde.org/show_bug.cgi?id=481289
--- Comment #3 from Maik Qualmann ---
If you only have "Place|England|London|Baker street" in the metadata, only
"Baker street" will appear under the image, not "England" or "London" and these
will not have a
https://bugs.kde.org/show_bug.cgi?id=481289
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=481112
--- Comment #17 from Maik Qualmann ---
If you want to define a different format, it should definitely be compatible
with ExifTool. I don't know how your users otherwise apply the metadata to the
scanned images, but we have no problems with the JSON
https://bugs.kde.org/show_bug.cgi?id=481257
--- Comment #4 from Maik Qualmann ---
Git commit 3303c40502df47ce6122c783b693cb09985c332f by Maik Qualmann.
Committed on 13/02/2024 at 07:42.
Pushed by mqualmann into branch 'master'.
simplify metadata tab updating
M +14 -24 core/libs/properties
https://bugs.kde.org/show_bug.cgi?id=481257
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=481268
Maik Qualmann changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=481273
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Resolution
https://bugs.kde.org/show_bug.cgi?id=481268
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=481259
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed
https://bugs.kde.org/show_bug.cgi?id=481255
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481253
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed
https://bugs.kde.org/show_bug.cgi?id=481268
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #5 from Maik
301 - 400 of 12712 matches
Mail list logo
