Registered Member
|
When I connect my camera (I have two different ones) to the computer, there is no notification. The camera is neither in Places nor in the Device Notifier. It is visible in System Settings and accessible via <URL: camera:/ >but I have to add this place by hand. Is it just me or is it a problem in KDE?
Also, the Add New Device Shortcut dialog box allows me to select a camera for the target device but then it looks for the camera device to be mounted among the file systems |
Administrator
|
With each camera connected to the computer, please try running the following command to see if it is being recognised by the device backend, which is likely UDisks / UDisks2.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I have the same problem with my Canon PowerShot SX120 IS. If i turn on the camera, the device notifier does'nt show the actions of Digikam, Gwenview or Dolphin. The kio-slave (camera:/) works well, and download the Fotos manually with Digikam works also. The camera is recognized by gphoto2 but not by solid-hardware:
A
Do i need a specific ptp-udev-rule for this camera? Join a mtp-device (mediaplayer) will show up the device notifier. I've tried to figure out how the interaction of udev, udisks, solid, devicenotifier and deviceactions works, but i miss the point. I am using an daily updatet arch-linux. |
Administrator
|
Please find your camera in the output of "solid-hardware list" and then provide the output of "solid-hardware details <udi of camera>"
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for your reply
I turn on the Camera, but the camera isn't listed in the output from "solid-hardware list". But there are two failures:
Don't know if this belongs to my issue. Edit: The output from "udiskctl dump" doesn't show the camera to. |
Registered Member
|
Hmmm...
I've made a udev-rule with the gphoto-helper skript "/usr/lib64/libgphoto2/print-camera-list":
It makes a rules-file with all devices gphoto be aware of (snippet with the rule for my camera):
I played with this rule and verfy it with the hwdb-file under /lib/udev/hwdb.d/20-gphoto.conf. So i changed it to:
Now the device notifier appears with approriate Options (download Fotos with Gwenview/Digikam/open with filemanger)... but it shows two Cameras solid-hardware listen shows two actions too:
So i rebuild the udev hwdb, to be sure the hwdb.bin contains all the rules from /lib/udev/hwdb.d/. But without my udev-rule the device-notifier do not came up and solid do not recognize the new attached camera. Any ideas, of whats going wrong here? |
Administrator
|
This explains a bit - KDE/Solid is reliant upon UDev, UDisks, etc. to provide correct/detailed information on devices attached to the system.
It is likely that your UDev rule is too wide in scope, which is why you're seeing it twice. To help track down this, please ensure the adjustments are in place, then run the following and provide it's output:
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
With my udev-rule i got this:
The Command "solid-hardware details udi=" works only for the first udi:
With the second udi, no output returns and i have to use "CTRL+c" to get a command line back. Hope this will help. |
Registered Member
|
Something mysterious: Seems that "solid-hardware details [udi]" works not correct, because it shows nothing, but "solid-hardware list details did.
vs:
I am shure the camera did not turn off, while examining the commands. For safety i test this two times. As you could see, my last comment in my previous post was not right. Maybe i did it wrong this early, early morning Anyway, i've done it. My udev-rule is enhanced with
The additional condition was found in the output "udevadm info --query=all --attribute-walk --name='[busname of device]'". Maybe there are other conditions to minimize the scope so that the device isn't shown twice in the devicemanager. Hints therefore are welcome. Thanks bcooksley for care about my problem Why does solid not recognize the ptp-device, while mtp-devices are recognized? It's because there is no udev-rule for ptp-devices? |
Administrator
|
Not a problem. In my experience, PTP devices are usually detected - it is likely your distribution is missing the necessary rules, either for PTP devices in general or just your camera (which might behave unusually).
In regards to the solid-hardware command, try the following:
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I could not say, if ptp-devices are generally not recognized. I am using arch-linux, maybe i ask in an arch-related forum. Your last command works as expected. I edited my udev rule, because i found a little mistake: The key name "ATTRS" matches against the upwards device, while "ATTR" (without the S) matches against the device directly. So i changed "ATTRS" with "ATTR", delete the serialnumber and the devicemanager shows only one camera
|
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar