Version: 3.5.2 (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages OS: Linux When a user which is not in the camera group (or at least which is lacking permissions to the camera) adds a camera and clicks on "Test", nothing happens. Since I suppose suggesting to verify camera group membership would be too system-specific, I would expect kamera to at least say something about missing permissions. At the very least, it should show some error message which could be Googled. Note that clicking on a camera doesn't clearly make it selected, and this will certainly be confusing when combined with this bug. E.g., if clicking "Test" has no effect, the user will wonder whether testing is buggy, or if the camera selection is buggy. The other functions which don't work are Configure (fails with "Camera configuration failed." Details: "Wrong parameters") and Information ("No camera summary information is available."). The error message for Information is not bad, but overall none of the failures give the user a clue about lacking permissions. ...and another thing I realized while writing this: the same thing happens if a camera is turned off. The user has to add the camera manually, and then the same problems happen, not hinting that the camera is misconnected or turned off (possibly due to automatic poweroff if figuring out the lacking permissions took some time). So instead of doing nothing, Test should hint about checking the connection, that the camera is turned on, and that permissions aren't lacking.
KDE 4.10.5 (under Gentoo LInux) and this seems to still be the case, although I have no idea what permissions I'm missing. This does seem to work as root, although "configure" crashes the dialog. Is there any other testing I can do?
I realize I should have provided a bit more information - gphoto2 sees the camera, and also camera:/ in knoqueror works. My problem is that f-spot does not see the camera. This happened several years ago, at which time the solution was to click "Cancel" in the popup that showed when I plugged in the camera. I don't remember when that popup disappeared. I just installed kamera, and I get a notifier popup again, but no options - just the possibility to open the camera in the file manager, which works fine.
f-spot is no KDE application.
I know that, and sorry not to be clear. I just mentioned the f-spot problem in case it helped point in some particular direction, I wasn't expecting any specific help for that. I think the issue with the camera configuration problems in system settings is the focus here. I'll have to test again, and I'll post a concise summary of the KDE specific problems that remain.
This problem still seems to exist with kamera 4.14.3 and systemsettings 4.11.19. Even as root, the other actions (information, configure) fail with some sort of I/O error - but that seems related to bug 315268, and I can't really tell if they are related or just both about cameras. However, I don't actually see any group related to the camera, and since the camera doesn't seem to have a device node, I don't know exactly what permissions I may be lacking. The group plugdev is mentioned in the udev rule for the camera, but I am in that group, so I seem to be missing something else.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
I am unable to reproduce on Linux 5.0.0, using kcm_kamera from KDE Apps 18.12 (Ubuntu 19.04's 4:18.12.3-0ubuntu1), even with a user which is only in its own group. I do not know enough about udev, hal and systemd to tell how device permissions are managed nowadays, but it may be that this is no longer reproducible under Linux. This might still affect under non-Linux systems though.