Bug#608341: [libgphoto2-2] please add support for Canon IXUS 130 (lsusb -v attached)

2011-01-03 Thread Andreas Metzler
On 2011-01-02 Bastian Venthur vent...@debian.org wrote:
 Thanks for your patch, it works. There are two things:

 1. With your patch I'm able to access the camera as Canon IXUS 130 in
 KDE's filemanager, w/o your patch I'm only able to access it with
 gphoto2 (Why?). W/o your patch the camera is also correctly recognized
 in KDE's filemanager but I cannot access the images due to some unknown
 device-like error.

 2. The *real* problem was actually that KDE's filemanager and gphoto2
 were not able to access the device, there was an error message like:

   ('Could not lock the device'): Camera is already in use.

 I didn't really pay attention to this message since it never happened
 with my last camera, and I knew I did not mount the camera. Anyways,
 after reading a few bugreports someone pointed to this message and said
 he solved the problem by killing all gvfs processes. I looked and
 noticed that I had rhythmbox open and the camera was already shown there
 as a media device (although it was not listed as mounted device via
 mount). Closing rhythmbox allowed me to access the camera w/o the
 above error message.

 Do you think it is a bug in libgphoto or rhytmbox or something else?

Hello,

I am largely udev-agnostic, and totally do not know how KDE changes
things. However I think that the following should be true:

A With 2.4.10.1-3 you should be able to access the camera as root with
  gphoto but should not be able to do so as normal user.

B The patch should fix the issue for normal users.

C On a sidenote: Devices accessed through gphot generally will not be
  listed by mount, unless you are using gphotofs or similar tricks.

I realize that A contradicts your observations (w/o your patch I'm
only able to access it with gphoto2). Could you verify it by
downgrading to 2.4.10.1-3, rebooting, and checking whether gphoto
works (as non-root)? Any custom udev rules you added for the camera
should be removed before eboot.

thanks, cu andreas




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#608341: [libgphoto2-2] please add support for Canon IXUS 130 (lsusb -v attached)

2011-01-02 Thread Andreas Metzler
On 2010-12-30 Bastian Venthur vent...@debian.org wrote:
 Package: libgphoto2-2
 Version: 2.4.10.1-3
 Severity: normal

 --- Please enter the report below this line. ---
 Bus 002 Device 006: ID 04a9:31f3 Canon, Inc.
 Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass0 (Defined at Interface level)
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize064
   idVendor   0x04a9 Canon, Inc.
   idProduct  0x31f3
   bcdDevice0.02
   iManufacturer   1 Canon Inc.
   iProduct2 Canon Digital Camera
   iSerial 3 7C718E77E58D4946966AB145DDC48D09
   bNumConfigurations  1
[...]
You later wrote in your blog:
 Today I bought me a Canon IXUS 130 and was quite disappointed to see
 that it couldn’t properly connect to my Debian/Sid machine via USB.
 Apparenty the camera is not recognized as a USB Mass Storage Device
 but utilizes PTP. I upgraded to libgphoto2 (2.4.10.1-3) from
 experimental and added a proper udev rule with vendor- and product-id
 but it did not help. Is there anything more I can try?


Hello,

for supported devices there is *no* *need* to touch the udev rules.
Things should just work.

However, afaict from reading camlibs/ptp2/library.c the IXUS 130 is
not listed.

Does the attached patch fix the issue for you?

cu andreas
--- libgphoto2-2.4.10.1.orig/camlibs/ptp2/library.c
+++ libgphoto2-2.4.10.1/camlibs/ptp2/library.c
@@ -1069,6 +1069,7 @@ static struct {
 	/* http://sourceforge.net/tracker/index.php?func=detailaid=2918540group_id=8874atid=358874 */
 	{Canon:IXY 220 IS,			0x04a9, 0x31e6, PTPBUG_DELETE_SENDS_EVENT},
 	{Canon:Digital IXUS 120 IS,		0x04a9, 0x31e6, PTPBUG_DELETE_SENDS_EVENT},
+	{Canon:Digital IXUS 130 IS,		0x04a9, 0x31f3, PTPBUG_DELETE_SENDS_EVENT},
 	{Canon:PowerShot SD940 IS,		0x04a9, 0x31e6, PTPBUG_DELETE_SENDS_EVENT},
 
 	/* IRC reporter */


Bug#608341: [libgphoto2-2] please add support for Canon IXUS 130 (lsusb -v attached)

2011-01-02 Thread Bastian Venthur
Hi Andreas,

Thanks for your patch, it works. There are two things:

1. With your patch I'm able to access the camera as Canon IXUS 130 in
KDE's filemanager, w/o your patch I'm only able to access it with
gphoto2 (Why?). W/o your patch the camera is also correctly recognized
in KDE's filemanager but I cannot access the images due to some unknown
device-like error.

2. The *real* problem was actually that KDE's filemanager and gphoto2
were not able to access the device, there was an error message like:

  ('Could not lock the device'): Camera is already in use.

I didn't really pay attention to this message since it never happened
with my last camera, and I knew I did not mount the camera. Anyways,
after reading a few bugreports someone pointed to this message and said
he solved the problem by killing all gvfs processes. I looked and
noticed that I had rhythmbox open and the camera was already shown there
as a media device (although it was not listed as mounted device via
mount). Closing rhythmbox allowed me to access the camera w/o the
above error message.

Do you think it is a bug in libgphoto or rhytmbox or something else?


Cheers,

Bastian

Am 02.01.2011 11:07, schrieb Andreas Metzler:
 On 2010-12-30 Bastian Venthur vent...@debian.org wrote:
 Package: libgphoto2-2
 Version: 2.4.10.1-3
 Severity: normal
 
 --- Please enter the report below this line. ---
 Bus 002 Device 006: ID 04a9:31f3 Canon, Inc.
 Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass0 (Defined at Interface level)
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize064
   idVendor   0x04a9 Canon, Inc.
   idProduct  0x31f3
   bcdDevice0.02
   iManufacturer   1 Canon Inc.
   iProduct2 Canon Digital Camera
   iSerial 3 7C718E77E58D4946966AB145DDC48D09
   bNumConfigurations  1
 [...]
 You later wrote in your blog:
 Today I bought me a Canon IXUS 130 and was quite disappointed to see
 that it couldn’t properly connect to my Debian/Sid machine via USB.
 Apparenty the camera is not recognized as a USB Mass Storage Device
 but utilizes PTP. I upgraded to libgphoto2 (2.4.10.1-3) from
 experimental and added a proper udev rule with vendor- and product-id
 but it did not help. Is there anything more I can try?
 
 
 Hello,
 
 for supported devices there is *no* *need* to touch the udev rules.
 Things should just work.
 
 However, afaict from reading camlibs/ptp2/library.c the IXUS 130 is
 not listed.
 
 Does the attached patch fix the issue for you?
 
 cu andreas

-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#608341: [libgphoto2-2] please add support for Canon IXUS 130 (lsusb -v attached)

2010-12-29 Thread Bastian Venthur
Package: libgphoto2-2
Version: 2.4.10.1-3
Severity: normal

--- Please enter the report below this line. ---
Bus 002 Device 006: ID 04a9:31f3 Canon, Inc.
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x04a9 Canon, Inc.
  idProduct  0x31f3
  bcdDevice0.02
  iManufacturer   1 Canon Inc.
  iProduct2 Canon Digital Camera
  iSerial 3 7C718E77E58D4946966AB145DDC48D09
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xc0
  Self Powered
MaxPower2mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass 6 Imaging
  bInterfaceSubClass  1 Still Image Capture
  bInterfaceProtocol  1 Picture Transfer Protocol (PIMA 15470)
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   9
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x0001
  Self Powered


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.37-rc5-686

Debian Release: 6.0
  500 unstableftp.de.debian.org
  500 unstabledebian-multimedia.org
  500 stable  dl.google.com
  101 experimentalftp.de.debian.org

--- Package information. ---
Depends  (Version) | Installed
==-+-==
libc6 (= 2.7) | 2.11.2-7
libexif12  | 0.6.19-1
libgphoto2-port0 (= 2.4.10.1) | 2.4.10.1-3
libjpeg62 (= 6b1) | 6b1-1
libltdl7   (= 2.2.6b) | 2.2.6b-2
adduser| 3.112+nmu2


Recommends  (Version) | Installed
=-+-===
udev   (= 0.136) | 164-3


Suggests  (Version) | Installed
===-+-===
gphoto2  (= 2.1.1) |





-- 
Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org