Nice that you are satisfied, but both settings should function IMHO. Each in their own way.
On 2015-04-26 20:56, hcvv wrote:
>
> robin_listas;2706993 Wrote:
>> On 2015-04-26 17:16, hcvv wrote:
>>
>>> So please check the camera.
>>
>> Yes, that’s what I’m saying, it is a camera issue.
> I do not see you anywhere saying “Check the camera for PTP/mass-storage
> setting” or similar. But I may misinterprete what you try to explain. Or
> maybe I missed some of your NNTP smileys :\
But somebody else said it 
And yes, of course I checked the camera for such a setting, didn’t find
anything. Or I didn’t recognize it (it is not my own camera).
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
As far as digital photography goes I am after Kodaks demise a simple run of the mill user and happy that things work.
From a technical point of view you are absolutely right.
I noted that with the PTP menu setting the camera does describe itself as a different product ( idVendor=07cf, idProduct=1033), I would have expected one product with different configuration options. Should I raise this problem with udev developers ?? or somewhere else.
Enno
No, that will be down to the device chipset itself. When you switched to PTP mode it took effect, and that is how the device identifies itself to the kernel, and ultimately how udev then handles it (ie not a problem at all).
I agree with that. The switch should result in a different identification. But my concern is that, while it identifies itself as a mass-storage device, no device fies are created (and of course anything following that like pop-ups, mounting on behalf of the desktop or a command will happen then).
I vaguely remember another thread here (could be in the German section) that has the same sort of problem. And that somebody there talked about it being seen (incorrectly) as a “system type of device”. What ever that means. Sorry, I know this is very vague.
Yes, I understand what you’re saying here, and I think that it is down to the uas driver, or the device interaction with it at least. There were bugs filed against this driver during it’s development, and even though it is now active in openSUSE 13.2 (it wasn’t in openSUSE 13.1), maybe there are still problems to be resolved. This is why I think a bug report should be submitted.
FWIW, here’s one bug I found concerning UAS
https://bugzilla.novell.com/show_bug.cgi?id=888069
Yes, I hope the OP fennema is willing to file a bug at https://en.opensuse.org/Submitting_Bug_Reports (same user/password as here).
My idea that describing what happens (or rather what does not happen) accompanied by the dmesg listing and the long USB listing (both from the posts above) should be enough.