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

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|5.1.0                       |5.3.0

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

Nicolas Brisset <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #38 from Nicolas Brisset <[hidden email]> ---
I also see this bug (5.2.0 installed, Windows 7 64 bits AND Windows 10 64 bits
on a different PC). I also use a card reader to transfer the pictures, I
suspect this has something to do with the issue.

Now, the interesting thing in my case is that I live close to Salon de Provence
=> @Gilles C.: if you still live in the area, we could maybe organize a live
debug session on the PC with the problem, since it seems you can't reproduce
it. I also have a couple of other problems we could look at... I'd be really
happy to help improve digikam, it's such a great program!

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #39 from Maik Qualmann <[hidden email]> ---
I have now access to a Windows7 computer where I can reproduce the problem. I
will create a special debug version in the next days and look.

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

Anthony Cartmell <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #40 from Anthony Cartmell <[hidden email]> ---
I also get this problem, and Digikam also wants to access the floppy disk in
drive A: here!

The problem occurs whether or not I ask to scan for changes on startup.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

--- Comment #41 from Maik Qualmann <[hidden email]> ---
I have created a special debug version. I can not reproduce the problem on my
test computer. I think the problem was fixed in the Solid framework now.

Please try the latest Windows build (digiKam-5.4.0) from Gilles Google drive
for testing:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Maik

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

--- Comment #42 from [hidden email] ---
Just for info, last KF5 5.29.0 is now used to build digiKam bundles. In this
KF5 release, Solid changelog report : "winutils_p.h: Restore compatibility with
WinXP SDK".

This can be the solution of the problem.

So please check if new Windows installer work fine now, as Maik said.
Thanks in advance for your feedback.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

--- Comment #43 from Anthony Cartmell <[hidden email]> ---
It's a lot better, but not quite fully fixed.

I only get one error popup now, saying that drive A: is not ready. It no longer
pops up lots of errors for the card reader drives.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

--- Comment #44 from Twilight Sparkle <[hidden email]> ---
I just tried the new build.  It fixed the bug completly for me.

@ Anthony Cartmell
Do you have a floppy drive?  I don't and I'm no logger getting any error
messages.  (I was just wondering since A is traditionally the drive name for
floppies.)

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

--- Comment #45 from Anthony Cartmell <[hidden email]> ---
Aha, somehow the A: drive was present on my Windows 7 machine, even though it
doesn't have a floppy drive. A restart via the BIOS settings to disable the
legacy floppy drive fixed this problem.

So I can report that the beta release of 5.4 works perfectly here, Windows 7
64-bit. Thanks to everyone involved!

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.4.0
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #46 from [hidden email] ---
Thanks to all for your feedbacks and tests under Windows.
It's very appreciate, as we are not Windows users (as developers). Remmeber
that whole digiKam (including all dependencies are cross-compiled under Linux).

This take age (around 4 hours to build 32 and 64 bits version from scratch).
The tests are don in a VM with Windows 7. Results can be different with a real
install on computer.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

Wolfram Kroiss <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED

--- Comment #47 from Wolfram Kroiss <[hidden email]> ---
Dear Gilles and Maik (and all others who contributed),

during the last few weeks of using digikam 5.4.0 I didn't experience the
problem at all. Therefore I set the status to VERIFIED. Hope this is ok for
everyone following this thread.

Thank you very much!

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=366234

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|VERIFIED                    |RESOLVED

--
You are receiving this mail because:
You are the assignee for the bug.