https://bugs.kde.org/show_bug.cgi?id=371530
--- Comment #1 from Simon ---
Created attachment 101725
--> https://bugs.kde.org/attachment.cgi?id=101725=edit
Relevant command line output.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371530
Bug ID: 371530
Summary: Database query fails when adding face rectangle
resulting in full freeze
Product: digikam
Version: 5.2.0
Platform: Debian testing
OS:
https://bugs.kde.org/show_bug.cgi?id=357944
--- Comment #10 from Simon ---
Hi Antonio
Thanks for working on this.
I do not see how this addresses the issue of encoded paths ("%2F" instead of
"/") in the database, are you sure this is fixed with your changes?
--
You are
https://bugs.kde.org/show_bug.cgi?id=369345
--- Comment #4 from Simon ---
Hi Maik,
Thanks for fixing this.
So there is currently no way to tag, flag, ... grouped images?
This is kind of a big deal, as grouping camera jpgs and raw images is an
essential feature for me, but
https://bugs.kde.org/show_bug.cgi?id=369345
--- Comment #1 from Simon ---
I can still reproduce this with the current master (afebcb2).
Can anyone else reproduce this error?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369345
Simon changed:
What|Removed |Added
Version|5.1.0 |5.2.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=369345
Bug ID: 369345
Summary: In tagging apply to all versions fails
Product: digikam
Version: 5.1.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=364967
Kay Simon changed:
What|Removed |Added
CC||kayingosi...@gmail.com
--
https://bugs.kde.org/show_bug.cgi?id=362474
--- Comment #7 from Simon ---
The issue was introduced when porting to QFileDialog:
https://github.com/KDE/gwenview/commit/6cd4688f7b17ede3e2c01e9b97207e0c1400325a
Re-using the pseudo URL "kfiledialog:///" apparently not
supported
https://bugs.kde.org/show_bug.cgi?id=362474
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=357944
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=366740
Bug ID: 366740
Summary: Remove dependency on libkexiv
Product: digikam
Version: 5.1.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=366567
Bug ID: 366567
Summary: Allow choosing several duplicates
Product: digikam
Version: 5.1.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=267131
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=364258
--- Comment #20 from Simon ---
Hi Gilles,
Do you plan to include this or something similar before the 5.1.0 release?
This is a major reason why digikam 5 is still in the experimental
repository on debian. The "compatibility
https://bugs.kde.org/show_bug.cgi?id=364258
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=366219
--- Comment #9 from Simon ---
Created attachment 100382
--> https://bugs.kde.org/attachment.cgi?id=100382=edit
minor patch on top of maiks commits
Thanks Maik for going over it and improve it. I have some minor points to add
https://bugs.kde.org/show_bug.cgi?id=366219
--- Comment #2 from Simon ---
Created attachment 100359
--> https://bugs.kde.org/attachment.cgi?id=100359=edit
Patch of cpp file after refactor
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366219
--- Comment #1 from Simon ---
Created attachment 100358
--> https://bugs.kde.org/attachment.cgi?id=100358=edit
Patch of header file after refactor
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366219
Bug ID: 366219
Summary: Setting up internal mysql database fails
Product: digikam
Version: 5.0.0
Platform: Other
OS: unspecified
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=366202
Bug ID: 366202
Summary: Bootstrap script does not test for QT5 mysql library
Product: digikam
Version: 5.1.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=297922
--- Comment #7 from Simon ---
The workaround mentioned in Comment 3 to set this manually in the config file
does not work in current digiKam version (5.1.0 devel). See duplicate bug:
https://bugs.kde.org/show_bug.cgi?id=366092
https://bugs.kde.org/show_bug.cgi?id=366124
--- Comment #1 from Simon ---
Created attachment 100310
--> https://bugs.kde.org/attachment.cgi?id=100310=edit
This patch corrects spelling/formatting in the first run widgets.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=366124
Bug ID: 366124
Summary: [Patch] Corrected spelling in first run widgets
Product: digikam
Version: 5.1.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=366122
Bug ID: 366122
Summary: Next button not activatable via Alt+N in widget
Product: digikam
Version: 5.1.0
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=366036
--- Comment #13 from Simon ---
The only "rescan metadata" option I find is "read metadata from file",
but I do not currently write any metadata to file with digiKam, I store
tags only internally.
So the behavior is that digiKam
https://bugs.kde.org/show_bug.cgi?id=366036
--- Comment #11 from Simon ---
So I just opened digikam for the first time after compiling it with
Maik's commit. It looks like digikam now detects the symlinks as
duplicates. This output was printed repeatedly while scanning for
https://bugs.kde.org/show_bug.cgi?id=366036
--- Comment #9 from Simon ---
Maik: So what is the behaviour after your commit: Does digikam handle
symlinked images like unique images (so unique database entry, e.g.
tags) or just as pointers to the real image (so all symlinks
https://bugs.kde.org/show_bug.cgi?id=366036
--- Comment #3 from Simon ---
Regarding the behaviour: Digikam does treat symlinks like "real files",
e.g. every symlink has its own set of tags in the database. In my
opinion it would make more sense to treat them as links
igiKam
On 20/07/16 11:12, Simon via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=364793
>
> --- Comment #6 from Simon <freisi...@gmail.com> ---
> Hi Andreas,
> There are other icons that stand out as not monochrome, however less
> present and much less intrusive. St
https://bugs.kde.org/show_bug.cgi?id=364793
--- Comment #6 from Simon ---
Hi Andreas,
There are other icons that stand out as not monochrome, however less
present and much less intrusive. Still making them monochrome too would
only be consistent. Are there already
https://bugs.kde.org/show_bug.cgi?id=364793
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=365826
Bug ID: 365826
Summary: Some tasks from caldav calendar not shown
Product: zanshin
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=337079
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=364234
Bug ID: 364234
Summary: plasma crashes and then reloads
Product: plasmashell
Version: 5.6.4
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Keywords:
https://bugs.kde.org/show_bug.cgi?id=356133
Simon changed:
What|Removed |Added
CC||s.sueu...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=363638
--- Comment #14 from Simon ---
Just for my own education, so only answer if you have time:
I have seen that you removed the return() calls in the else parts. My
reason to use them was, that any further evaluation becomes useless
https://bugs.kde.org/show_bug.cgi?id=363638
--- Comment #12 from Simon ---
Created attachment 99332
--> https://bugs.kde.org/attachment.cgi?id=99332=edit
remove typos from FIndGphoto2.cmake and make it more verbose
I finally resolved this. The actual problem is that the
https://bugs.kde.org/show_bug.cgi?id=363638
--- Comment #10 from Simon ---
Now there is this additional part about libgphoto:
-- Found Lqr-1:
/usr/include/lqr-1;/usr/include/glib-2.0;/usr/lib/x86_64-linux-gnu/glib-2.0/include
-- libgphoto2 found:
-- Checking for module
https://bugs.kde.org/show_bug.cgi?id=363638
--- Comment #7 from Simon ---
I always remove the build dir before rerunning the boostrap script and I
know have made sure to run it on an entirely clean git clone. I removed
the translation checkout from my custom bootstrap
https://bugs.kde.org/show_bug.cgi?id=363638
--- Comment #5 from Simon ---
I do not see anything related to libusb and still the same for
libgphoto. I am running the boostrap script on softwarecomp commit
"d30542149650693a58b355aab944fea4e7be6e09" and core commit
https://bugs.kde.org/show_bug.cgi?id=363638
Simon changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=363695
--- Comment #2 from Laurent Simon ---
Reported on Kubuntu Trusty (14.04) but the problem is identical on Kubuntu
Willy (15.10)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363695
--- Comment #1 from Laurent Simon ---
Possible duplicate of: bug 363679
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363695
Laurent Simon changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=363695
Bug ID: 363695
Summary: Segmentation fault after startup of muon updater
Product: muon
Version: 2.2.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363638
Bug ID: 363638
Summary: bootstrap does not detect libgphoto2
Product: digikam
Version: 5.0.0
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=350098
Simon changed:
What|Removed |Added
Version|4.11.0 |5.0.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #14 from Simon ---
Indeed, my setup is far from optimal for disk io. I have both the
database and the images on a ntfs pratition of a hard disk on my laptop
(at least not system hd). I thought that the database would
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #12 from Simon ---
Created attachment 98665
--> https://bugs.kde.org/attachment.cgi?id=98665=edit
Command line output in the middle of writing metadat to files with
scancontroller2.patch
I applied the patch and added
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #11 from Simon ---
Created attachment 98664
--> https://bugs.kde.org/attachment.cgi?id=98664=edit
Startup of digikam and start of writing metadata with scancontroller2.patch
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=362411
Bug ID: 362411
Summary: Selecting grouped files and renaming only acts on one
file of every group
Product: digikam
Version: 5.0.0
Platform: Debian unstable
OS:
https://bugs.kde.org/show_bug.cgi?id=362407
Bug ID: 362407
Summary: Shortcut to either (un-)collapse grouping tree or
change to "ignore grouping"
Product: digikam
Version: 5.0.0
Platform: Debian unstable
https://bugs.kde.org/show_bug.cgi?id=362406
Bug ID: 362406
Summary: On import renaming by date from file should use exif
date and time not modification time as standard
Product: digikam
Version: 5.0.0
Platform: Debian
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #10 from Simon ---
Do I apply this patch on top of the current HEAD or on top of your
previous patch? I guess the first, but just to be sure.
On 27/04/16 21:14, Maik Qualmann via KDE Bugzilla wrote:
>
https://bugs.kde.org/show_bug.cgi?id=357479
--- Comment #15 from Kay Simon ---
Still on 16.04
KDE Frameworks 5.21.0
Qt 5.6.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #8 from Simon ---
And the scan is now going clearly slower than before the patch. I am now
running it almost two days and its at 3% only.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=336079
Simon changed:
What|Removed |Added
CC||simon.t...@tngtech.com
--
You
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #7 from Simon ---
Created attachment 98528
--> https://bugs.kde.org/attachment.cgi?id=98528=edit
Command line output in the middle of writing metadat to files with
scancontroller.patch
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #6 from Simon ---
Created attachment 98527
--> https://bugs.kde.org/attachment.cgi?id=98527=edit
Startup of digikam and start of writing metadata with scancontroller.patch
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #5 from Simon ---
Thanks for looking into this. I applied your patch. The results seems to be the
same (maybe somewhat less frequent rescans). I attached the initial part of the
log after startup, where redundant stuff
https://bugs.kde.org/show_bug.cgi?id=362023
--- Comment #1 from Simon ---
Created attachment 98490
--> https://bugs.kde.org/attachment.cgi?id=98490=edit
Command line output of writing metadata to files.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=362023
Bug ID: 362023
Summary: Extremely slow metadata writing via maintenance
Product: digikam
Version: 5.0.0
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361848
Bug ID: 361848
Summary: When writing metadata to files is disabled, digikam
still displays "Writing metadata to files"
Product: digikam
Version: 5.0.0
Platform: Debian unstable
https://bugs.kde.org/show_bug.cgi?id=361686
Bug ID: 361686
Summary: When returning from full screen to preview mode the
same image should be selected/shown.
Product: digikam
Version: 5.0.0
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=357479
Kay Simon changed:
What|Removed |Added
CC||kayingosi...@gmail.com
--
https://bugs.kde.org/show_bug.cgi?id=359108
--- Comment #14 from Simon ---
Strangely with digikam 4.14 from debian repo I get all icons and they do
not look like breeze. And I use tango icon theme, but changing it to
something different (e.g. gnome) does not change the
https://bugs.kde.org/show_bug.cgi?id=359108
--- Comment #12 from Simon ---
I have the same problem. While it is now possible with gilles commit to
choose Breeze icons, they are not complete (e.g. Light Table and Editor
Window icons in settings are missing) and the icons
https://bugs.kde.org/show_bug.cgi?id=359508
--- Comment #2 from Simon ---
Another duplicate
https://bugs.kde.org/show_bug.cgi?id=358339
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357467
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=358339
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=315557
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=359508
Simon changed:
What|Removed |Added
CC||simon.th...@gmx.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=360528
Simon changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=360528
--- Comment #8 from Simon ---
This is embarrassing, sorry for wasting your time and thanks for your
patience:
I used git://anongit.kde.org/digikam instead of using the
software-compilation repo. Using the software-repo this
https://bugs.kde.org/show_bug.cgi?id=360528
--- Comment #4 from Simon ---
That gave the same result. You are right about the Qt installation. I
only installed the packages that were necessary for cmake to run without
errors. Therefore I was missing the qtpaths binary file
https://bugs.kde.org/show_bug.cgi?id=360528
--- Comment #2 from Simon ---
This results in
qtpaths: could not find a Qt installation of ''
On 14/03/16 19:48, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360528
>
> Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=360528
Bug ID: 360528
Summary: Digikam looks for digikamimageplugins in different
directory than they were installed to
Product: digikam
Version: 5.0.0
Platform: Debian testing
https://bugs.kde.org/show_bug.cgi?id=359897
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=357480
--- Comment #2 from simon ---
thank you for the response.
I tried but couldn't reproduce the bug either. It also didn't reappear during
normal usage of the program. I keep my eyes open and report if it reappears.
--
You are
80 matches
Mail list logo