https://bugs.kde.org/show_bug.cgi?id=458029
--- Comment #12 from Such A Shame ---
This bug could be duplicate but it's not fixed. You corrupt peoples minds with
this kind of behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=458029
Such A Shame changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=492163
--- Comment #6 from Such A Shame ---
So it appears that as expected choosing "Read metadata from file" removes all
such tags from database too and thus looses data, whereas "Write metadata to
file" saves the correct updated d
https://bugs.kde.org/show_bug.cgi?id=458029
--- Comment #9 from Such A Shame ---
Files attached to https://bugs.kde.org/show_bug.cgi?id=492163 as I haven't
tested but only suspecting they cause this bug too.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492163
--- Comment #5 from Such A Shame ---
Created attachment 172943
--> https://bugs.kde.org/attachment.cgi?id=172943&action=edit
Sidecar from OLD location
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492163
--- Comment #4 from Such A Shame ---
Created attachment 172942
--> https://bugs.kde.org/attachment.cgi?id=172942&action=edit
Sidecar from NEW location
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492163
--- Comment #3 from Such A Shame ---
Created attachment 172941
--> https://bugs.kde.org/attachment.cgi?id=172941&action=edit
Screenshot of preview from NEW directory
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #9 from Such A Shame ---
This is not directly *convert* issue as running *ffmpeg* doesn't work either.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491778
--- Comment #11 from Such A Shame ---
Could you do this?
1. File location is always saved to database.
2. Everytime file properties are updated, digikam checks where the file
currently is, and does all needed to maintain database/sidecar integrity
https://bugs.kde.org/show_bug.cgi?id=491778
--- Comment #10 from Such A Shame ---
... referring to https://bugs.kde.org/show_bug.cgi?id=492163
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491778
--- Comment #9 from Such A Shame ---
"The problem is that the sidebar doesn't recognize drag and drop. It won't be
easy to find a solution here."
Can system check the situation while updating database instead? It should be
aware of
https://bugs.kde.org/show_bug.cgi?id=458029
Such A Shame changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=491778
Such A Shame changed:
What|Removed |Added
CC||myaccount...@protonmail.com
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=204487
--- Comment #22 from Such A Shame ---
Ability to move files directly to new location considerably saves time when
handling many pictures as writing occurs during move process and doesn't have
to be waited to finish while handling next bunch of pic
https://bugs.kde.org/show_bug.cgi?id=492163
--- Comment #1 from Such A Shame ---
Also should be noticed that xmp-files at OLD location are not perfect ones.
While they have updated tags, they seems to lag exif and other data which now
appear to be saved only at NEW location.
--
You are
https://bugs.kde.org/show_bug.cgi?id=458029
--- Comment #6 from Such A Shame ---
See https://bugs.kde.org/show_bug.cgi?id=492163 for possible cause.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492163
Bug ID: 492163
Summary: Creation of orphan sidecars
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: Other
OS: Linux
Status: REPORTED
S
https://bugs.kde.org/show_bug.cgi?id=458029
--- Comment #4 from Such A Shame ---
So it's normal behavior if I've several times removed those tags from all
images they were attached, and according to UI they disappeared from all those
images, still time after time they keep coming back
https://bugs.kde.org/show_bug.cgi?id=484858
--- Comment #3 from Such A Shame ---
I have digiKam-8.4.0-Qt6-x86-64.appimage which still opens several instances.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #27 from Such A Shame ---
Thanks, this was fixed already. "Funnily" 8.4.0 again occasionally started to
do similar blinking but immediately normalizes and doesn't freeze the view.
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=458029
Such A Shame changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=491809
Such A Shame changed:
What|Removed |Added
Platform|Other |Appimage
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=491809
Bug ID: 491809
Summary: Sort view bug/behavior at Geolocation editor
Classification: Applications
Product: digikam
Version: 8.4.0
Platform: Other
OS: Linux
Status: REP
https://bugs.kde.org/show_bug.cgi?id=484373
--- Comment #10 from Such A Shame ---
Sorry I was talking about two separate things. I just wanted to mention that
video files are now renamed with correct time like photos. I possibly shouldn't
have mixed it here. This is separate thing.
The pr
https://bugs.kde.org/show_bug.cgi?id=484373
--- Comment #8 from Such A Shame ---
It seems that 8.4.0 fixes other time issues too, like correct time based file
renaming for video files which has long been several hours wrong.
However the original problem is still partially there. Now it seems
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #8 from Such A Shame ---
Creating fresh profile didn't help. Otherwise this was new installation.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #7 from Such A Shame ---
Thanks for your help. I'll see through my profile which I saved from previous
installation. Possibly I could create another fresh profile for testing.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #5 from Such A Shame ---
... if I keep the copy line process virtually finishes as new file is created
like expected (but without needed changes), if i leave it out no new file
appears. I'm unsure how all this combines with what is sel
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #4 from Such A Shame ---
Either doesn't fix the problem. If I leave copy line out I will get many more
error messages:
Failed to process item...
User Script: Error code returned 1.
Failed to process item
Failed to create file...
https://bugs.kde.org/show_bug.cgi?id=490524
--- Comment #2 from Such A Shame ---
Is this enough?
Digikam::BatchTool::CustomTool :: wurl= QUrl("file:///media/photo")
Digikam::BatchTool::setOutputUrlFromInputUrl: path:
"/media/photo/BatchTool-dhVhqB-ca42a842.digikamtempfi
https://bugs.kde.org/show_bug.cgi?id=490524
Bug ID: 490524
Summary: BQM custom scripts stopped working after upgrading OS
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Appimage
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=484858
Bug ID: 484858
Summary: Multiple instances of Gimp opened
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=484373
--- Comment #5 from Such A Shame ---
Ok, I may have misinterpreted origin of the bug in the end here. My original
notice was that there seems to be "Z" timezone sent to iNaturalist now after
upgrade. And this may be the cause for +2 h
https://bugs.kde.org/show_bug.cgi?id=484373
--- Comment #3 from Such A Shame ---
It's actually image file creation date which gets +2 h time (shown at "File
Properties", while "digiKam properties" shows correct time). At least iNat
plugin seems to send this wrong time to
https://bugs.kde.org/show_bug.cgi?id=484373
--- Comment #1 from Such A Shame ---
Appeared after upgrading 8.2.0 -> 8.3.0 appimage, but didn't verify by
reverting back.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484373
Bug ID: 484373
Summary: Wrong time/timezone data
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Other
OS: Linux
Status: REPORTED
Seve
https://bugs.kde.org/show_bug.cgi?id=484234
--- Comment #1 from Such A Shame ---
For example mp4 videos no problems with this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484234
Bug ID: 484234
Summary: MP3 slider stopped working
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Other
OS: Linux
Status: REPORTED
Se
https://bugs.kde.org/show_bug.cgi?id=478991
--- Comment #7 from Such A Shame ---
Thx for explanation. Will try to simplify my scripts. (Still hoping for feature
to run these scripts directly by left clicking images. You have abundance of
technical features included which is great, but at some
https://bugs.kde.org/show_bug.cgi?id=478991
--- Comment #4 from Such A Shame ---
Ok, I have workflow where I first run custom shell script then use built in
"Assign Labels" feature to mark it with colour label, which creates the
problem. Running custom script only works fine. So the
https://bugs.kde.org/show_bug.cgi?id=478991
--- Comment #3 from Such A Shame ---
Sry, I sent wrong script. I'll check one thing from the correct one before
sending it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478991
--- Comment #2 from Such A Shame ---
Example script which worked perfectly before is as simple as:
cp $INPUT $OUTPUT
convert -geometry 2048x2048 -sharpen 2 -quality 85 -strip $INPUT $OUTPUT
I can't grasp the nuances you suggest from document
https://bugs.kde.org/show_bug.cgi?id=478991
Bug ID: 478991
Summary: BQM removes tags and ratings
Classification: Applications
Product: digikam
Version: 8.2.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #20 from Such A Shame ---
Problems started again immediately today with 8.1.0, no USB drive attached.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #19 from Such A Shame ---
I'm inclined to say this appears to affect 8.1.0 but not 8.0.0.
There was long while without any problems (using 8.1.0 only) but now I got
8.1.0 doing this very quickly and constantly (three times) after res
https://bugs.kde.org/show_bug.cgi?id=393382
--- Comment #20 from Such A Shame ---
Can't make scripts work without constantly getting "Failed to process item..."
& "Failed to create file..." however occasionally file is there after
refreshing. Applies for both images
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #18 from Such A Shame ---
So far 8.0.0 has been running fine, will continue testing.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #16 from Such A Shame ---
No, I switched to xfce because of earlier bug and stayed with it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #14 from Such A Shame ---
Can't find 8.0.0 here https://download.kde.org/Attic/digikam/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468593
--- Comment #8 from Such A Shame ---
See if this is related https://bugs.kde.org/show_bug.cgi?id=472918 and bug is
not properly fixed or it was deeper than this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #13 from Such A Shame ---
Well... now I had it while just browsing pictures at external drive. Didn't yet
open the plugin. It may be that it started with 8.1.0 but it does have some
relation to external drive to make occurences re
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #12 from Such A Shame ---
I can do just one upload at time and then restart digikam...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #11 from Such A Shame ---
What you said earlier is based in wrong assumption as I've hidden data from
these logs. These lines appear (correctly) multiple times because they're
different locations. They look repeating because I&
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #10 from Such A Shame ---
No, it just happened without external drive connected. I have no log for this
occurrence.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #9 from Such A Shame ---
Yes, in fact it may be that these problems have occurred only when I have had
external drive connected. However these problems seem to occur only in digikam
and they have started recently, and I still believe they
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #7 from Such A Shame ---
Created attachment 160730
--> https://bugs.kde.org/attachment.cgi?id=160730&action=edit
crash
And one complete crash...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #6 from Such A Shame ---
+ please remove the log files / outputs after you have analyzed them
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #5 from Such A Shame ---
Created attachment 160728
--> https://bugs.kde.org/attachment.cgi?id=160728&action=edit
full log #2
One shorter complete log attached. Digikam was already once crashed already and
after restart did it ve
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #4 from Such A Shame ---
Here's end of the log file. There's two mentions of errors and - if related -
there was earlier four times lines
Digikam::PreviewLoadingTask::execute: Preview quality: 2
above, which were now changed t
https://bugs.kde.org/show_bug.cgi?id=472918
--- Comment #2 from Such A Shame ---
Occurs also in Thumbnails mode trying to double click image to preview.
Thumbnails become locked, scrollbar moves but doesn't scroll images and there's
line at bottom half to show border of expected prev
https://bugs.kde.org/show_bug.cgi?id=472918
Such A Shame changed:
What|Removed |Added
Version|8.2.0 |8.1.0
--- Comment #1 from Such A Shame ---
sry
https://bugs.kde.org/show_bug.cgi?id=472918
Bug ID: 472918
Summary: Preview mode becomes unresponsive
Classification: Applications
Product: digikam
Version: 8.2.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=471492
--- Comment #13 from Such A Shame ---
Converted file was actually found from directory as
BatchTool-smFwpk-f6181d32.digikamtempfile.MTS.m4a
but for some reason doesn't appear at digikam. If I manually rename it, it will
show after refreshing.
https://bugs.kde.org/show_bug.cgi?id=471492
Such A Shame changed:
What|Removed |Added
Version|8.0.0 |8.2.0
--- Comment #12 from Such A Shame ---
Is
https://bugs.kde.org/show_bug.cgi?id=471492
--- Comment #11 from Such A Shame ---
I was able to find source code locations
digikam / core / app / items / utils / contextmenuhelper.h/cpp
digikam / core / dplugins / bqm
First supposedly has enough examples to create proper context menu item
https://bugs.kde.org/show_bug.cgi?id=471492
--- Comment #10 from Such A Shame ---
For repeated tasks there's just too much unnecessary clicking when you have to
use separate window, including selecting background window, switching control
panel tabs and emptying the queue. (You can't
66 matches
Mail list logo
