I have a Canon EOS SL1 camera (also known as an EOS 100D). With Fedora 20 and 21, when I connected the camera to a USB port, it was recognized and the KDE device notifier would ask whether I wanted to open it with the file manager or download photos with digikam. Digikam also recognized the camera when it was connected. The camera is supported by libghoto2 and uses the PTP protocol.
But with Fedora 22 and 23, the camera is not fully recognized and I can't download photos directly from the camera. (I can use a card reader, of course.) In /var/log/messages, I see the following:
Nov 11 11:17:01 g kernel: usb 4-1.4.1: new high-speed USB device number 9 using ehci-pci Nov 11 11:17:02 g kernel: usb 4-1.4.1: New USB device found, idVendor=04a9, idProduct=3270 Nov 11 11:17:02 g kernel: usb 4-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 11 11:17:02 g kernel: usb 4-1.4.1: Product: Canon Digital Camera Nov 11 11:17:02 g kernel: usb 4-1.4.1: Manufacturer: Canon Inc. Nov 11 11:17:02 g mtp-probe: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4.1" Nov 11 11:17:02 g mtp-probe: bus: 4, device: 9 was not an MTP device
The device notifier doesn't notice the camera (it says "no devices available) and digikam can't see it. I've tried other cables and usb ports (and even another computer). I use KDE, but this doesn't look like it's a KDE issue.
The only other camera with a usb connection thta I have at hand right now is an old Canon Powershot G9, which gets similar messages about not being an MTP device (but /var/log/messages shows a serial number for the camera). This also worked with earlier Fedoras.
I'm not sure what changed from F21 to F22. I was hoping that things would work again with F23. Any suggestions? I don't understand udev very well...
On 11 November 2015 at 17:19, George Avrunin avrunin@math.umass.edu wrote:
I have a Canon EOS SL1 camera (also known as an EOS 100D). With Fedora 20 and 21, when I connected the camera to a USB port, it was recognized and the KDE device notifier would ask whether I wanted to open it with the file manager or download photos with digikam. Digikam also recognized the camera when it was connected. The camera is supported by libghoto2 and uses the PTP protocol.
But with Fedora 22 and 23, the camera is not fully recognized and I can't download photos directly from the camera. (I can use a card reader, of course.) In /var/log/messages, I see the following:
Nov 11 11:17:01 g kernel: usb 4-1.4.1: new high-speed USB device number 9 using ehci-pci Nov 11 11:17:02 g kernel: usb 4-1.4.1: New USB device found, idVendor=04a9, idProduct=3270 Nov 11 11:17:02 g kernel: usb 4-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 11 11:17:02 g kernel: usb 4-1.4.1: Product: Canon Digital Camera Nov 11 11:17:02 g kernel: usb 4-1.4.1: Manufacturer: Canon Inc. Nov 11 11:17:02 g mtp-probe: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4.1" Nov 11 11:17:02 g mtp-probe: bus: 4, device: 9 was not an MTP device
The device notifier doesn't notice the camera (it says "no devices available) and digikam can't see it. I've tried other cables and usb ports (and even another computer). I use KDE, but this doesn't look like it's a KDE issue.
The only other camera with a usb connection thta I have at hand right now is an old Canon Powershot G9, which gets similar messages about not being an MTP device (but /var/log/messages shows a serial number for the camera). This also worked with earlier Fedoras.
I'm not sure what changed from F21 to F22. I was hoping that things would work again with F23. Any suggestions? I don't understand udev very well...
I've also got a Canon not showing up, putting camera:// into the dolphin address bar while it's connected works and I haven't got around to finding out why it's doing this.
On Wed, 11 Nov 2015 17:31:54 +0000, Ian Malone wrote:
I've also got a Canon not showing up, putting camera:// into the dolphin address bar while it's connected works and I haven't got around to finding out why it's doing this.
Thanks, Ian. Just "camera://"? I tried that just now; when I hit enter, I got a big red bar with "Invalid protocol".
But I don't use dolphin in general (or any graphical file manager), so I could well be doing something wrong.
On 11 November 2015 at 17:49, George Avrunin avrunin@math.umass.edu wrote:
On Wed, 11 Nov 2015 17:31:54 +0000, Ian Malone wrote:
I've also got a Canon not showing up, putting camera:// into the dolphin address bar while it's connected works and I haven't got around to finding out why it's doing this.
Thanks, Ian. Just "camera://"? I tried that just now; when I hit enter, I got a big red bar with "Invalid protocol".
But I don't use dolphin in general (or any graphical file manager), so I could well be doing something wrong.
Just tried it and looks like it should be "camera:/" but "camera://" would also get corrected t a single /.
This is what I see on F22 in /var/log/messages: Nov 11 21:42:13 atlas kernel: usb 4-6.3: new high-speed USB device number 4 using ehci-pci Nov 11 21:42:13 atlas kernel: usb 4-6.3: New USB device found, idVendor=04b0, idProduct=0221 Nov 11 21:42:13 atlas kernel: usb 4-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 11 21:42:13 atlas kernel: usb 4-6.3: Product: NIKON DSC COOLPIX P300-PTP Nov 11 21:42:13 atlas kernel: usb 4-6.3: Manufacturer: NIKON Nov 11 21:42:13 atlas kernel: usb 4-6.3: SerialNumber: 40033678 Nov 11 21:42:13 atlas mtp-probe: checking bus 4, device 4: "/sys/devices/pci0000:00/0000:00:13.2/usb4/4-6/4-6.3" Nov 11 21:42:13 atlas mtp-probe: bus: 4, device: 4 was not an MTP device
So something different going on. Maybe try https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1256591/comments/30 and also the kio client command from https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1256591/comments/61
Hi, i have a server auth by group in Active Directory, the dansguardian recive every connection in HTTP and HTTPS, and after analyze its sent request to squid. In log of dansguardian i saw the username OK, but in squid log i saw only the IP of listen dansguardian. First, there is a way to dansguardian pass username to squid ? Second, in sites https i have a problem, i recive access denied, but in dansguardian i have the exceptionlist configured, but in squid log, i recive error 407 denied, only if i explicity a freesitelist in squid its work fine. Someone know how to solve this ?
On Wed, 2015-11-11 at 19:22 -0200, Bruno de Oliveira Bastos wrote:
Don't hijack threads. If you want to start a new topic then compose a new message, don't just reply to an existing one on a different subject.
poc
George Avrunin writes:
Nov 11 11:17:02 g kernel: usb 4-1.4.1: Manufacturer: Canon Inc. Nov 11 11:17:02 g mtp-probe: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4.1" Nov 11 11:17:02 g mtp-probe: bus: 4, device: 9 was not an MTP device
The device notifier doesn't notice the camera (it says "no devices available) and digikam can't see it. I've tried other cables and usb ports (and even another computer). I use KDE, but this doesn't look like it's a KDE issue.
The only other camera with a usb connection thta I have at hand right now is an old Canon Powershot G9, which gets similar messages about not being an MTP device (but /var/log/messages shows a serial number for the camera). This also worked with earlier Fedoras.
I'm not sure what changed from F21 to F22. I was hoping that things would work again with F23. Any suggestions? I don't understand udev very well...
May or may not be related, but I had a similar issue with Gnome and my MP3 player after upgrading to F21, not F22. So, it is probably a slightly different, but likely a related issue.
Anyway, my MP3 player is a USB storage device, and after an upgrade to F21 something in Gnome-land apparently got the bright idea that it's now an MTP device. Hilarity ensued.
I happened to have a netbook that wasn't beefy enough for Gnome, and I had the XFCE spin running on it already. On a lark, I plugged in the MP3 player, and it came up like nothing has ever happened. Fully functional. I switched to XFCE on my main server, and suddenly it could talk to the MP3 player again.
I dutifully opened a bug, included syslog dumps, USB device IDs, etc… It was all for nothing, the ticket had no activity after I created it, and it's about to be closed together with all other unresolved F21 bugs. I don't really care much for it, since all my desktops and laptops are running XFCE now.
So, try switching to XFCE. You may need to create a new user account, though. Even after I had reconfigured my user account for XFCE, for some reason it still had a bunch of Gnome stuff refusing to go away.
On Wed, 11 Nov 2015 18:53:56 -0500, Sam Varshavchik wrote:
May or may not be related, but I had a similar issue with Gnome and my MP3 player after upgrading to F21, not F22. So, it is probably a slightly different, but likely a related issue.
Anyway, my MP3 player is a USB storage device, and after an upgrade to F21 something in Gnome-land apparently got the bright idea that it's now an MTP device. Hilarity ensued.
I happened to have a netbook that wasn't beefy enough for Gnome, and I had the XFCE spin running on it already. On a lark, I plugged in the MP3 player, and it came up like nothing has ever happened. Fully functional. I switched to XFCE on my main server, and suddenly it could talk to the MP3 player again.
I dutifully opened a bug, included syslog dumps, USB device IDs, etc… It was all for nothing, the ticket had no activity after I created it, and it's about to be closed together with all other unresolved F21 bugs. I don't really care much for it, since all my desktops and laptops are running XFCE now.
So, try switching to XFCE. You may need to create a new user account, though. Even after I had reconfigured my user account for XFCE, for some reason it still had a bunch of Gnome stuff refusing to go away.
Thanks. I tried both XFCE and Gnome, each with a scratch user. No change, neither desktop seems to notice a new device. Since the kernel isn't fully recognizing the camera (doesn't get the model number or the serial number) and mtp-probe rejects it, my guess is that the problem is before the desktop.
Running the kio client command, as suggested in the bug report pointed out by Ian Malone, yields "Canon%20EOS%20100D@usb:004,011", which does seem to be getting the model number (100D) correctly, but doesn't seem to make the camera accessible to dolphin or anything else. Running kdeinit4 from a konsole and then trying camera:/ in Dolphin just gives the same "invalid protocol" message. (But the bug Ian cited was for KDE 4, so I'm not sure it applies in F23.)
There's a check-ptp-camera script in /lib/udev (which comes from gphoto2). It's supposed to exit with code 0 if the device offers a PTP interface. When I run that and check the exit code, I'm getting 1. (I couldn't see who actually calls that in normal operation, but I figured I'd give it a try.)
I can get pictures off the camera using a card reader, so this isn't urgent for me, but it's annoying and it seems that other people are having some related problems. There's bug 1249283 on this (filed against the kamera component, but maybe it should be something else?).
An addendum:
konqueror (but not dolphin) supports the camera:/ protocol and can see the camera. And now (though this was definitely not true earlier, at least with F22--I'm not sure I even tried with F23), digikam can import from the camera. But the device notifier doesn't see any device, so it doesn't prompt to download pictures, and the messages in /var/log/messages about mtp-probe, etc., are the same.
I had fiddled around with commenting out a like in the libmtp udev ruleset, but I put it back to the original version, and then I rebooted. So I'm not sure why digikam can now import from the camera (though it simply calls it a "Canon Digital Camera", when I think it used to know the model).