[digikam] [Bug 371530] Database query fails when adding face rectangle resulting in full freeze

https://bugs.kde.org/show_bug.cgi?id=371530 --- Comment #1 from Simon --- Created attachment 101725 --> https://bugs.kde.org/attachment.cgi?id=101725&action=edit Relevant command line output. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 371530] New: Database query fails when adding face rectangle resulting in full freeze

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: Linux

[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x

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 receiving this mail beca

[digikam] [Bug 369345] In tagging apply to all versions fails

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 tags only applying to t

[digikam] [Bug 369345] In tagging apply to all versions fails

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.

[digikam] [Bug 369345] In tagging apply to all versions fails

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 mail because: You are

[digikam] [Bug 369345] New: In tagging apply to all versions fails

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: n

[kmail2] [Bug 364967] Kmail message list does not remember rightmost column width

https://bugs.kde.org/show_bug.cgi?id=364967 Kay Simon changed: What|Removed |Added CC||kayingosi...@gmail.com -- You are receiving this m

[gwenview] [Bug 362474] Copy To/Move To does not remember path any more

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 in QFileDialog. --

[gwenview] [Bug 362474] Copy To/Move To does not remember path any more

https://bugs.kde.org/show_bug.cgi?id=362474 Simon changed: What|Removed |Added CC||simon.th...@gmx.de --- Comment #6 from Simon --- If an

[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x

https://bugs.kde.org/show_bug.cgi?id=357944 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #7 from Simon --- This

[digikam] [Bug 366740] New: Remove dependency on libkexiv

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 Pr

[digikam] [Bug 366567] New: Allow choosing several duplicates

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: wishli

[digikam] [Bug 267131] SETUP : digiKam config and data cannot be moved, absolute paths embedded in database and digikamrc

https://bugs.kde.org/show_bug.cgi?id=267131 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #16 from Simon --- Yes

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored [patch]

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 break" without any notice i

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

https://bugs.kde.org/show_bug.cgi?id=364258 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #18 from Simon --- Cre

[digikam] [Bug 366219] Setting up internal mysql database fails [patch]

https://bugs.kde.org/show_bug.cgi?id=366219 --- Comment #9 from Simon --- Created attachment 100382 --> https://bugs.kde.org/attachment.cgi?id=100382&action=edit minor patch on top of maiks commits Thanks Maik for going over it and improve it. I have some minor points to add (additional.patch)

[digikam] [Bug 366219] Setting up internal mysql database fails

https://bugs.kde.org/show_bug.cgi?id=366219 --- Comment #2 from Simon --- Created attachment 100359 --> https://bugs.kde.org/attachment.cgi?id=100359&action=edit Patch of cpp file after refactor -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366219] Setting up internal mysql database fails

https://bugs.kde.org/show_bug.cgi?id=366219 --- Comment #1 from Simon --- Created attachment 100358 --> https://bugs.kde.org/attachment.cgi?id=100358&action=edit Patch of header file after refactor -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366219] New: Setting up internal mysql database fails

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: no

[digikam] [Bug 366202] New: Bootstrap script does not test for QT5 mysql library

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

[digikam] [Bug 297922] THUMBDB : different database locations for thumbnails

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 Digikam automatically rese

[digikam] [Bug 366124] [Patch] Corrected spelling in first run widgets

https://bugs.kde.org/show_bug.cgi?id=366124 --- Comment #1 from Simon --- Created attachment 100310 --> https://bugs.kde.org/attachment.cgi?id=100310&action=edit This patch corrects spelling/formatting in the first run widgets. -- You are receiving this mail because: You are watching all bug

[digikam] [Bug 366124] New: [Patch] Corrected spelling in first run widgets

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: m

[digikam] [Bug 366122] New: Next button not activatable via Alt+N in widget

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 Se

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

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 reads and writes metada

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

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 new items: digi

[digikam] [Bug 366092] New: Individual database names are always reset to Database Name

https://bugs.kde.org/show_bug.cgi?id=366092 Bug ID: 366092 Summary: Individual database names are always reset to Database Name Product: digikam Version: 5.0.0 Platform: Debian testing OS: Linux

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

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 pointing to the same

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

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 internally too. So any ope

[digikam] [Bug 364793] wrong icon useage

via KDE Bugzilla wrote: > 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

[digikam] [Bug 364793] wrong icon useage

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 monochrome pendants to the fo

[digikam] [Bug 364793] wrong icon useage

https://bugs.kde.org/show_bug.cgi?id=364793 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #4 from Simon --- I no

[zanshin] [Bug 365826] New: Some tasks from caldav calendar not shown

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

[plasmashell] [Bug 337079] sddm theme doesn't focus password field

https://bugs.kde.org/show_bug.cgi?id=337079 Simon changed: What|Removed |Added CC||simon.th...@gmx.de -- You are receiving this mail beca

[plasmashell] [Bug 364234] New: plasma crashes and then reloads

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: drkonqi

[kamoso] [Bug 356133] crash when starting - segmentation fault

https://bugs.kde.org/show_bug.cgi?id=356133 Simon changed: What|Removed |Added CC||s.sueu...@gmail.com --- Comment #16 from Simon --- On

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

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 (it already failed to

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

https://bugs.kde.org/show_bug.cgi?id=363638 --- Comment #12 from Simon --- Created attachment 99332 --> https://bugs.kde.org/attachment.cgi?id=99332&action=edit remove typos from FIndGphoto2.cmake and make it more verbose I finally resolved this. The actual problem is that the debian package h

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

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 'lensfun' -- Found le

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

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 script, so know the only

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

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 "e74ea61a3177d964474a04dc1460c1

[digikam] [Bug 363638] bootstrap does not detect libgphoto2

https://bugs.kde.org/show_bug.cgi?id=363638 Simon changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNC

[muon] [Bug 363695] Segmentation fault after startup of muon updater

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.

[muon] [Bug 363695] Segmentation fault after startup of muon updater

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.

[muon] [Bug 363695] Segmentation fault after startup of muon updater

https://bugs.kde.org/show_bug.cgi?id=363695 Laurent Simon changed: What|Removed |Added CC||k...@contact.stratic.fr -- You are receiving t

[muon] [Bug 363695] New: Segmentation fault after startup of muon updater

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 Se

[digikam] [Bug 363638] New: bootstrap does not detect libgphoto2

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: no

[digikam] [Bug 350098] Sort images on photograph specific metadata

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 mail because: You are

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

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 be automatically cach

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #12 from Simon --- Created attachment 98665 --> https://bugs.kde.org/attachment.cgi?id=98665&action=edit Command line output in the middle of writing metadat to files with scancontroller2.patch I applied the patch and added the command li

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #11 from Simon --- Created attachment 98664 --> https://bugs.kde.org/attachment.cgi?id=98664&action=edit Startup of digikam and start of writing metadata with scancontroller2.patch -- You are receiving this mail because: You are watching

[digikam] [Bug 362411] New: Selecting grouped files and renaming only acts on one file of every group

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: Lin

[digikam] [Bug 362407] New: Shortcut to either (un-)collapse grouping tree or change to "ignore grouping"

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 OS:

[digikam] [Bug 362406] New: On import renaming by date from file should use exif date and time not modification time as standard

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 unsta

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

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=3

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

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.

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

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.

[plasmashell] [Bug 336079] plasmashell desktop crash with kactivitymanager segfault message libQtCore

https://bugs.kde.org/show_bug.cgi?id=336079 Simon changed: What|Removed |Added CC||simon.t...@tngtech.com -- You are receiving this mail

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #7 from Simon --- Created attachment 98528 --> https://bugs.kde.org/attachment.cgi?id=98528&action=edit Command line output in the middle of writing metadat to files with scancontroller.patch -- You are receiving this mail because: You a

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #6 from Simon --- Created attachment 98527 --> https://bugs.kde.org/attachment.cgi?id=98527&action=edit Startup of digikam and start of writing metadata with scancontroller.patch -- You are receiving this mail because: You are watching

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

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 is excluded (marked by

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

https://bugs.kde.org/show_bug.cgi?id=362023 --- Comment #1 from Simon --- Created attachment 98490 --> https://bugs.kde.org/attachment.cgi?id=98490&action=edit Command line output of writing metadata to files. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 362023] New: Extremely slow metadata writing via maintenance

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 S

[digikam] [Bug 361848] New: When writing metadata to files is disabled, digikam still displays "Writing metadata to files"

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

[digikam] [Bug 361686] New: When returning from full screen to preview mode the same image should be selected/shown.

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

https://bugs.kde.org/show_bug.cgi?id=357479 Kay Simon changed: What|Removed |Added CC||kayingosi...@gmail.com -- You are receiving this m

[digikam] [Bug 359108] 5 beta 3: interface problem, icons not showing up

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 icons within digikam 4.1

[digikam] [Bug 359108] 5 beta 3: interface problem, icons not showing up

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 are very different from

[plasmashell] [Bug 359508] Plasma crash after opening Audio Volume Settings via Tray

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.

[frameworks-kconfigwidgets] [Bug 357467] plasmashell crash

https://bugs.kde.org/show_bug.cgi?id=357467 Simon changed: What|Removed |Added CC||simon.th...@gmx.de -- You are receiving this mail beca

[plasma-pa] [Bug 358339] Plasma crash after changing default audio output

https://bugs.kde.org/show_bug.cgi?id=358339 Simon changed: What|Removed |Added CC||simon.th...@gmx.de -- You are receiving this mail beca

[plasma4] [Bug 315557] system tray crashed

https://bugs.kde.org/show_bug.cgi?id=315557 Simon changed: What|Removed |Added CC||simon.th...@gmx.de -- You are receiving this mail beca

[plasmashell] [Bug 359508] Plasma crash after opening Audio Volume Settings via Tray

https://bugs.kde.org/show_bug.cgi?id=359508 Simon changed: What|Removed |Added CC||simon.th...@gmx.de --- Comment #1 from Simon --- Hi,

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

https://bugs.kde.org/show_bug.cgi?id=360528 Simon changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

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 problem disappears (and wo

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

https://bugs.kde.org/show_bug.cgi?id=360528 --- Comment #6 from Simon --- I did remove the build directory and then ran cmake -DCMAKE_INSTALL_PREFIX=/usr/ -DBUILD_TESTING=OFF -DCMAKE_BUILD_TYPE=debug -DENABLE_INTERNALMYSQL=ON -DENABLE_MYSQLSUPPORT=ON -DENABLE_AKONADICONTACTSUPPORT=OFF .. again,

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

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 for qt5, I only had a

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

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 changed: > > What|Re

[digikam] [Bug 360528] New: Digikam looks for digikamimageplugins in different directory than they were installed to

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

[digikam] [Bug 359897] Compilation failure - conflicting return type decodeRawImage()

https://bugs.kde.org/show_bug.cgi?id=359897 Simon changed: What|Removed |Added CC||freisi...@gmail.com -- You are receiving this mail bec

[krita] [Bug 357480] Krita Crash after Fullscreen switch

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 receiving this mail because

[krita] [Bug 357480] New: Krita Crash after Fullscreen switch

https://bugs.kde.org/show_bug.cgi?id=357480 Bug ID: 357480 Summary: Krita Crash after Fullscreen switch Product: krita Version: 2.9.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: cras