https://bugs.kde.org/show_bug.cgi?id=400604
--- Comment #4 from Johannes Berg ---
> Any idea where to find the exiv2 bug tracker?
Never mind, I found a link on the homepage.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=238372
--- Comment #4 from Magnus Johansson ---
Dear Andrew,
I have now tried to test, but I believe the GUI has changed so much since May
2010 so this bug is probably not relevant any longer.
Thank you for providing us with and working on improving the alre
https://bugs.kde.org/show_bug.cgi?id=400604
Johannes Berg changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400604
Johannes Berg changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=400611
Bug ID: 400611
Summary: Blur context menu on file drop
Product: dolphin
Version: 18.08.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Pr
https://bugs.kde.org/show_bug.cgi?id=400612
Bug ID: 400612
Summary: Discover shouldn't have flatpak-backend and
snap-backend as hard dependency
Product: Discover
Version: unspecified
Platform: Other
OS: Linu
https://bugs.kde.org/show_bug.cgi?id=400579
--- Comment #4 from Philippe ROUBACH ---
(In reply to caulier.gilles from comment #2)
> In digiKam or Showfoto, did you see the GPS tags removed from Exif viewer in
> right sidebar ?
>
> Gilles Caulier
yes
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=400604
--- Comment #6 from caulier.gil...@gmail.com ---
Johannes,
Since Exiv2 is migrated to github, the use this bugzilla in priority :
https://github.com/Exiv2/exiv2/issues
I know that Exiv2 migrate step by step all older redmine issue to guthub and
it's n
https://bugs.kde.org/show_bug.cgi?id=400579
--- Comment #5 from Philippe ROUBACH ---
(In reply to Maik Qualmann from comment #3)
> I'll take a closer look. But I think it's correct, all this data comes from
> a GPS receiver. After the GPS correction, the information would no longer
> fit. Take th
https://bugs.kde.org/show_bug.cgi?id=384846
christian.rohm...@gmx.de changed:
What|Removed |Added
CC||christian.rohm...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=400604
--- Comment #7 from Johannes Berg ---
(In reply to caulier.gilles from comment #6)
> Johannes,
>
> Since Exiv2 is migrated to github, the use this bugzilla in priority :
>
> https://github.com/Exiv2/exiv2/issues
Oh. *sigh*, you'd think they'd link th
https://bugs.kde.org/show_bug.cgi?id=398999
Michał B. changed:
What|Removed |Added
CC||mic...@greenpath.pl
--- Comment #4 from Michał B.
https://bugs.kde.org/show_bug.cgi?id=327105
Romain D. changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=384995
Maksim changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED|REOP
https://bugs.kde.org/show_bug.cgi?id=208320
--- Comment #2 from Alvaro Aguilera ---
I moved to pidgin several years ago and haven't used kopete ever since. Feel
free to close the bug. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363941
Andreas Schärtl changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=395647
Nico Dorn changed:
What|Removed |Added
Ever confirmed|0 |1
CC||n
https://bugs.kde.org/show_bug.cgi?id=394053
Nico Dorn changed:
What|Removed |Added
CC||nicod...@posteo.de
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=195600
Zayed Al-Saidi changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=400613
Bug ID: 400613
Summary: kcm_printer_manager - Windows printer via SAMBA -
Browse button greyed out
Product: print-manager
Version: unspecified
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=400614
Bug ID: 400614
Summary: Crash wiggling over menu
Product: plasmashell
Version: 5.8.7
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=195430
--- Comment #4 from J.O. Aho ---
For me this issue can be closed, haven't been using Kopete and not sure I ever
got the msn connection to work or not.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=235359
Schiwi changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |RE
https://bugs.kde.org/show_bug.cgi?id=400615
Bug ID: 400615
Summary: Please add 'hybrid-sleep' and 'suspend-then-hibernate'
support into Plasma
Product: Powerdevil
Version: unspecified
Platform: Archlinux Packages
https://bugs.kde.org/show_bug.cgi?id=400592
--- Comment #5 from Claudio ---
Created attachment 116059
--> https://bugs.kde.org/attachment.cgi?id=116059&action=edit
smb-backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400592
--- Comment #6 from Claudio ---
Created attachment 116060
--> https://bugs.kde.org/attachment.cgi?id=116060&action=edit
webm-backtrace1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400592
--- Comment #8 from Claudio ---
Created attachment 116062
--> https://bugs.kde.org/attachment.cgi?id=116062&action=edit
webm-backtrace3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400592
--- Comment #7 from Claudio ---
Created attachment 116061
--> https://bugs.kde.org/attachment.cgi?id=116061&action=edit
webm-backtrace2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400592
--- Comment #9 from Claudio ---
Hi Kai
I deinstalled the kdegraphics-thumbnailers package, restartet KDE and still got
these crahes, so I attached the backtraces. The crash for the .wma file also
seems to come from ffmpegthumbnailer (Can attach them if
https://bugs.kde.org/show_bug.cgi?id=357430
Martin Ueding changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=223200
--- Comment #4 from Sébastien Wilmet ---
Aha, I didn't remember reporting this bug :-) Looking at the date, I was
implementing the same feature (extract warnings/errors/badboxes from the LaTeX
output) in LaTeXila (now renamed to GNOME LaTeX). The implem
https://bugs.kde.org/show_bug.cgi?id=400579
--- Comment #6 from Maik Qualmann ---
We call the MetaEngine::removeGPSInfo() function in MetaEngine::setGPSInfo()
before setting the new coordinates. This is the comment:
// In first, we need to clean up all existing GPS info.
The question is why. I
https://bugs.kde.org/show_bug.cgi?id=156800
Markus Elfring changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=400579
--- Comment #7 from Maik Qualmann ---
Maybe I'm getting a little too far. But GPS information can be an important
part of preserving evidence. And only fully coherent GPS data makes sense.
Maik
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=195248
Markus Elfring changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=400608
Elvis Angelaccio changed:
What|Removed |Added
Version|18.08.2 |5.51.0
Component|general
https://bugs.kde.org/show_bug.cgi?id=212378
Marcos Dione changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=98864
--- Comment #2 from h...@gmx.at ---
no change -- the dialog has some options, but no options is about symlinks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=98864
h...@gmx.at changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=400615
mthw0 changed:
What|Removed |Added
CC||jari...@hotmail.com
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=400579
--- Comment #8 from caulier.gil...@gmail.com ---
// In first, we need to clean up all existing GPS info.
==> This comment come from me. Certainly to prevent garbage in GPS data and
re-write all from scratch. Remember that not all camera record a complet
https://bugs.kde.org/show_bug.cgi?id=400594
Elvis Angelaccio changed:
What|Removed |Added
Assignee|dolphin-bugs-n...@kde.org |baloo-bugs-n...@kde.org
Product|d
https://bugs.kde.org/show_bug.cgi?id=400604
--- Comment #8 from caulier.gil...@gmail.com ---
Let's Exiv2 team manage your entry (:=)))... Robin know well the right place to
post an issue and if tit need to be moved.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=219294
Stephan Karacson changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=400554
--- Comment #1 from b...@beuc.net ---
One work-around is to name the subgroups with the full (redundant) hierarchy
name (e.g. "face > neutral" becomes "face > face_neutral").
My suggestions may matching a specific workflow, so take it with a grain of
sa
https://bugs.kde.org/show_bug.cgi?id=13
--- Comment #3 from Andrew Svet ---
(In reply to Andrew Crouthamel from comment #2)
> Dear Bug Submitter,
>
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the st
https://bugs.kde.org/show_bug.cgi?id=400611
--- Comment #1 from RaitaroH ---
I managed to find it in another place. Unlock panels, then right click on the
`Places` text.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=146595
rpnpif changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=384846
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=317611
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=152478
--- Comment #4 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=195641
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=108873
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=292845
--- Comment #6 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=195426
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=278347
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=104204
--- Comment #7 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=228413
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=317688
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=272461
--- Comment #5 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=303443
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=322530
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=394544
--- Comment #4 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=150730
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=313816
--- Comment #8 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=386294
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=38
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=120945
--- Comment #11 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue M
https://bugs.kde.org/show_bug.cgi?id=363913
--- Comment #8 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=389274
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=133137
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=254932
--- Comment #4 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=194811
--- Comment #10 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue M
https://bugs.kde.org/show_bug.cgi?id=304772
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=400035
RaitaroH changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=152038
--- Comment #7 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=266865
--- Comment #5 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=287813
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=346128
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=321113
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=149430
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=272451
--- Comment #7 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=146866
--- Comment #10 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue M
https://bugs.kde.org/show_bug.cgi?id=262323
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=227345
--- Comment #8 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=144256
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=138072
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=357163
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=297290
--- Comment #12 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue M
https://bugs.kde.org/show_bug.cgi?id=274854
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=221704
--- Comment #5 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=306362
--- Comment #6 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=92050
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Man
https://bugs.kde.org/show_bug.cgi?id=278343
--- Comment #3 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=199848
--- Comment #19 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue M
https://bugs.kde.org/show_bug.cgi?id=104487
--- Comment #5 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=287811
--- Comment #1 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=351366
--- Comment #5 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=309725
--- Comment #2 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
https://bugs.kde.org/show_bug.cgi?id=228444
--- Comment #4 from caulier.gil...@gmail.com ---
WARNING : with digiKam 6.0.0 and later, we will not support kipi interface
anymore. All tools are now located in digiKam core as well for a plan to
provide a more power-full integration with Batch Queue Ma
1 - 100 of 305 matches
Mail list logo
