Camera not detected by system

English Hardware
1

Hello all, I am in need of help. I am running a Tumbleweed 20241211 Kde session on Lenovo IdeaPad 5 Pro 16ARH7. I have a Canon R10 camera and I wanted to try tethered shooting with Darktable , but I found out, that my camera is not recognized/detected by my system at all.

Can you please try to point me at direction of what to check? (settings, missing packages, etc.,…)

lsusb lists only the usual: integrated webcam, soundcard and connected phone, and fdisk -l lists only my system + home partitions. Gphoto2 and Kio Kamera packages are installed.

Thanks

2

Did you already check this:
https://docs.darktable.org/usermanual/4.8/en/tethering/overview/

https://docs.darktable.org/usermanual/4.8/en/tethering/troubleshooting/

3

Hi, yes, I have tried those commands, but with "*** Error: No camera found. *** " results.

4

According to the EOS R10 manual, there are some settings inside the camera menu regarding USB connections. Did you check them?

Only stabbing in the dark as i don’t own such a camera.

5

yes, that was the first thing I did. I have checked and set the camera to remote control (with no success)

6

Try to install:

https://software.opensuse.org/package/kamera

https://software.opensuse.org/package/kio_kamera

7

Please don’t link to s.o.o without checking first. It is known to regularly break users systems.

  1. kamera is no rpm but a src rpm. So not a package to install.
  2. kio_kamera is available in the official openSUSE Tumbleweed repositories
8

thanks, but kio kamera is already installed (mentioned that in my original post)

9

Camera is connected per USB with the Computer?

If yes, disconnect, open an terminal and as User:
journalctl -f

Now connect the Camera and post all new entries from the Terminal here in Code-Tags:
Code-Tags

10

Well, here is the output - the command did not recognized any activity after connecting and turning on the camera. I am beginning to think, that I may have a camera, with faulty usb port.

I have tried to connect it in a Kubuntu live session and also on another pc with an old Mint 19 with the same result. Tomorrow I can try my luck on a Windows PC.

miro@telekom:~> journalctl -f
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
dec 17 16:36:58 telekom.ip drkonqi-coredump-processor[2331]: "/usr/bin/plasmashell" 2374 "/var/lib/systemd/coredump/core.plasmashell.1000.8bac4eadf1d848a78fdf4f84b75640e9.2374.1729697496000000.zst"
dec 17 16:36:58 telekom.ip drkonqi-coredump-processor[2331]: "/usr/bin/plasmashell" 12514 "/var/lib/systemd/coredump/core.plasmashell.1000.8bac4eadf1d848a78fdf4f84b75640e9.12514.1729697761000000.zst"
dec 17 16:36:58 telekom.ip drkonqi-coredump-processor[2331]: "/usr/bin/kdenlive" 3211 "/var/lib/systemd/coredump/core.kdenlive.1000.8f8b882b67214e5cab412b675916afc8.3211.1731946396000000.zst"
dec 17 16:36:58 telekom.ip drkonqi-coredump-processor[2331]: "/home/miro/.local/share/Steam/ubuntu12_64/steamwebhelper" 6228 "/var/lib/systemd/coredump/core.steamwebhelper.1000.4e2faeaf9fda4d30a3501fff5254123c.6228.1732388526000000.zst"
dec 17 16:36:58 telekom.ip drkonqi-coredump-processor[2331]: "/app/XnView/XnView" 14710 "/var/lib/systemd/coredump/core.XnView.1000.85271050b29348dfa97d5fd2d1bb21ff.14710.1733669980000000.zst"
dec 17 16:36:58 telekom.ip systemd[1951]: Started Launch DrKonqi for a systemd-coredump crash (PID 2331/UID 1000).
dec 17 16:36:59 telekom.ip drkonqi-coredump-launcher[3183]: Unable to find file for pid 14710 expected at "kcrash-metadata/XnView.85271050b29348dfa97d5fd2d1bb21ff.14710.ini"
dec 17 16:37:07 telekom.ip plasmashell[2299]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
dec 17 16:37:07 telekom.ip systemd[1951]: Started Konsole - Terminál.
dec 17 16:37:08 telekom.ip systemd[1951]: Started app-org.kde.konsole-3191.scope.
11

My fault, execute it as root.
Did you see more?

12

well, here is the output when executed as root:

miro@telekom:~> sudo journalctl -f
[sudo] heslo pre používateľa root: 
dec 18 16:42:38 telekom.ip plasmashell[2332]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
dec 18 16:42:38 telekom.ip systemd[1983]: Started Konsole - Terminál.
dec 18 16:42:39 telekom.ip systemd[1983]: Started app-org.kde.konsole-5106.scope.
dec 18 16:42:47 telekom.ip sudo[5176]: pam_kwallet5(sudo:auth): pam_kwallet5: pam_sm_authenticate
dec 18 16:42:47 telekom.ip sudo[5176]: pam_kwallet5(sudo:auth): pam_kwallet5: Refusing to do anything for the root user
dec 18 16:42:50 telekom.ip sudo[5176]:     miro : TTY=pts/1 ; PWD=/home/miro ; USER=root ; COMMAND=/usr/bin/journalctl -f
dec 18 16:42:50 telekom.ip sudo[5176]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
dec 18 16:42:50 telekom.ip sudo[5176]: pam_unix(sudo:session): session opened for user root(uid=0) by miro(uid=1000)
dec 18 16:42:50 telekom.ip sudo[5176]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
dec 18 16:42:50 telekom.ip sudo[5176]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
dec 18 16:42:53 telekom.ip systemd[1]: snapperd.service: Deactivated successfully.

obviously the same result…

Today I have tried to connect the camera to a windows pc. It was immediately recognized and mounted by the system, but I was unable to unmount it so Darktable could lock it for itself. The usual “safely eject device” icon did not appeared and disabling the camera in the device manager disabled it completely. (am I getting rusty at using windows…?)

But at least I know, that there is nothing wrong with the camera.

Is there any command to check, if the gphoto2, or any other dependencies are installed and working correctly?

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.