[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

--- Comment #19 from Twilight Sparkle <[hidden email]> ---
(In reply to caulier.gilles from comment #16)
> The end of the trace is very very strange... Typically we see only these
> message (and limited ones) at end of digiKam session, not at startup...
>
> Gilles Caulier

That's because I closed digikam before saving the trace.  I've redone the trace
and left digikam running.

--
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|5.0.0                       |5.1.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

Ergin <[hidden email]> changed:

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

--- Comment #20 from Ergin <[hidden email]> ---
I am experiencing the same issue but in my case I get the popup 4 times for the
4 card reader drives I have and the messages appear at least twice; very
annoying.
//*Ergin

--
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 #21 from Wolfram Kroiss <[hidden email]> ---
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 the message boxes twice
for each of the four card drives.

A strange thing happened after retrieving the images from the memory card: All
files have been properly copied. But after copying the memory card disappeared
from "My Computer", i.e. the drive e: didn't show any medium inserted. After
removing the card and re-inserting the drive behaved as usual. Probably the two
events are not related at all. But I don't want to waste any piece of
information that helps to reproduce this bug.

--
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 #22 from [hidden email] ---
This is really strange because KDE::Solid interface used under Linux to
discovered in live the removable media do not work under Windows as i know.

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

Don <[hidden email]> changed:

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

--- Comment #23 from Don <[hidden email]> ---
My install of digiKam on Windows 10 (64-bit) exhibits the same problem.  When
starting digiKam, there is a warning for each card slot that nothing is
installed.  Selecting continue for each error eventually lets digiKam start.
This has happened each time after the first that digiKam is started.  A couple
of times, it seemed like digiKam was beginning to cycle through the card slots
a second time.

Don

--
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 #24 from [hidden email] ---
Can you take a screenshot of the problem ?

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 #25 from Don <[hidden email]> ---
Created attachment 100747
  --> https://bugs.kde.org/attachment.cgi?id=100747&action=edit
Screen Shot of Startup Showing No Disk Error

Four "drives" on memory card reader (F:, G:, H:, and I:).  For this screen
shot, the No Disk dialog came up 5 times for each drive letter (FGHI-FGHI-FGHI
....) then digiKam started.

--
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 #26 from Twilight Sparkle <[hidden email]> ---
Created attachment 100813
  --> https://bugs.kde.org/attachment.cgi?id=100813&action=edit
Screenshot of one of the messages

Here is a screenshot of the problem on my system.

--
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 #27 from Maik Qualmann <[hidden email]> ---
Git commit 6010949f407ba9de35e06a216a4225442442d4d5 by Maik Qualmann.
Committed on 28/08/2016 at 08:28.
Pushed by mqualmann into branch 'master'.

try to fix the card reader access problem under windows

M  +65   -45   app/main/digikamapp.cpp

http://commits.kde.org/digikam/6010949f407ba9de35e06a216a4225442442d4d5

--
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 #28 from [hidden email] ---
Maik,

This want mean that KDE::Solid interface start to work under Windows ? If yes,
this is a great news.

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

Maik Qualmann <[hidden email]> changed:

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

--- Comment #29 from Maik Qualmann <[hidden email]> ---
I have on work 2 computers with built-in card reader. None of these computer
this problem is to reproduce here. However, the computer still running with
older Windows versions. When I plug in there a USB flash drive, automatically
appears in the digiKam menu - but in the card reader menu. But works. This
commit prevents access to card reader volumes to get label or size,  if not a
volume exists.

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 #30 from Twilight Sparkle <[hidden email]> ---
Created attachment 100836
  --> https://bugs.kde.org/attachment.cgi?id=100836&action=edit
Screenshot of card readers and their names.

Don't know if this helps... but here is a screenshot giving some details about
the card reader in my computer.   If you need more details on the device ask
and I'll send it.

--
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 #31 from [hidden email] ---
Beta Windows 64bits installer for digiKam 5.2.0 for testing is here :

https://drive.google.com/open?id=0BzeiVr-byqt5a19HZEcyeXZrTHM

It include last patch from comment #27

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

Twilight Sparkle <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #100813|0                           |1
        is obsolete|                            |

--- Comment #32 from Twilight Sparkle <[hidden email]> ---
Created attachment 100862
  --> https://bugs.kde.org/attachment.cgi?id=100862&action=edit
With the patched 5.2 version

(In reply to caulier.gilles from comment #31)
> Beta Windows 64bits installer for digiKam 5.2.0 for testing is here :
>
> https://drive.google.com/open?id=0BzeiVr-byqt5a19HZEcyeXZrTHM
>
> It include last patch from comment #27
>
> Gilles Caulier

Problem persists.  Attached is a screenshot showing the debugview and the error
message at the same time.

--
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 #33 from Twilight Sparkle <[hidden email]> ---
Created attachment 100863
  --> https://bugs.kde.org/attachment.cgi?id=100863&action=edit
5.2 patch debugview log

--
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 #34 from Maik Qualmann <[hidden email]> ---
Git commit 9bcc19c2701202599e11bfe53cfed8f18b30509d by Maik Qualmann.
Committed on 31/08/2016 at 18:52.
Pushed by mqualmann into branch 'master'.

revert commit #6010949f407ba9de35e06a216a4225442442d4d5

M  +45   -65   app/main/digikamapp.cpp

http://commits.kde.org/digikam/9bcc19c2701202599e11bfe53cfed8f18b30509d

--
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 #35 from Twilight Sparkle <[hidden email]> ---
Maybe add some more messages that the debugview can grab to help pin down the
problem?

--
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 #36 from Twilight Sparkle <[hidden email]> ---
Found an interesting behavior that might help pinpoint the bug.
When I go to import and select the device that has a memory card in it... I get
the same error message as when starting, except only repeated once.

--
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 #37 from Twilight Sparkle <[hidden email]> ---
Bug present 5.3

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