[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-08-21 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #21 from Wolfram Kroiss --- Today I experienced this behavior again, directly after installing digikam 5.1.0. Earlier today I used the card reader to retrieve images. I ejected the medium properly afterwards. Later I started digikam and got

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-31 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 Wolfram Kroiss changed: What|Removed |Added Severity|normal |minor --- Comment #12 from Wolfram Kroiss ---

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #11 from Wolfram Kroiss --- NTFS. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #9 from Wolfram Kroiss --- What do you mean with "removable media D:\". This is the second partition of my hdd. I can't move data to C: because the first partition is just large enough to hold the OS and the applications. I have >200GB of im

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #7 from Wolfram Kroiss --- Yes. There is antivirus and also a backup job runs in the background. Probably you need to remove their debug messages. The complete log was made first. Then I closed digikam and restarted, creating the two other

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #5 from Wolfram Kroiss --- attached a few log files. BTW: My PC runs on Windows 10 64-bit. Digikam 5.0.0 was installed on 20/07/2016 (5.0.0-2) via http://download.kde.org/stable/digikam/ -- You are receiving this mail because: You are wat

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #4 from Wolfram Kroiss --- Created attachment 100372 --> https://bugs.kde.org/attachment.cgi?id=100372&action=edit log from start until the last series of popups is shown (after splash screen) -- You are receiving this mail because: You

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #3 from Wolfram Kroiss --- Created attachment 100371 --> https://bugs.kde.org/attachment.cgi?id=100371&action=edit log from start until the first popup is shown -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 --- Comment #2 from Wolfram Kroiss --- Created attachment 100370 --> https://bugs.kde.org/attachment.cgi?id=100370&action=edit complete log until album view is visible -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366234] New: Import from card readers starts automatically when digikam is started

2016-07-29 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366234 Bug ID: 366234 Summary: Import from card readers starts automatically when digikam is started Product: digikam Version: 5.0.0 Platform: Other OS: MS Windows

[digikam] [Bug 366034] Crash at edit metadata for jpgs made by a Casio EX-Z500

2016-07-24 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366034 --- Comment #3 from Wolfram Kroiss --- (In reply to caulier.gilles from comment #1) > It's probably due to crash inside Exiv2 shared library. Metadata Editor > read information in image trough this shared library. > > Please report this problem to Ex

[digikam] [Bug 366034] Crash at edit metadata for jpgs made by a Casio EX-Z500

2016-07-24 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366034 --- Comment #2 from Wolfram Kroiss --- No problems with manipulating these files using exiv2.exe (v0.25) though. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 366034] Crash at edit metadata for jpgs made by a Casio EX-Z500

2016-07-24 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366034 Wolfram Kroiss changed: What|Removed |Added CC||wolfram.kro...@gmail.com -- You are receiving

[digikam] [Bug 366034] New: Crash at edit metadata for jpgs made by a Casio EX-Z500

2016-07-24 Thread Wolfram Kroiss via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366034 Bug ID: 366034 Summary: Crash at edit metadata for jpgs made by a Casio EX-Z500 Product: digikam Version: 5.0.0 Platform: MS Windows OS: MS Windows Sta