Your message dated Mon, 12 May 2008 18:03:03 +0200 with message-id <200805121803.20484.Sune@vuorela.dk> and subject line Re: Bug#480866: kamera does not mount my USB camera has caused the Debian Bug report #480866, regarding kamera does not mount my USB camera to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 480866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480866 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: kamera does not mount my USB camera
- From: Pelayo Gonzalez <pelayogmp@orange.es>
- Date: Mon, 12 May 2008 12:28:45 +0200
- Message-id: <[🔎] 20080512102845.30202.50334.reportbug@palas.pedraz.fam>
Package: kamera Version: 4:3.5.9-1+b1 Severity: normal With kamera installed KDE is not able to mount my camera (Olympus C-370 ZOOM). dmesg shows this last line when it is connected: usb 2-2: usbfs: process 28910 (kio_kamera) did not claim interface 0 before use Bellow is included the full dmesg output from console and from KDE. I was able to uninstall kamera (making an equivs) and now KDE is able to mount it, however two icons are shown in the Desktop, one working for USB mass storage, and the other not working for the camera. lsusb output: ------------- $ lsusb | grep Olympus Bus 002 Device 005: ID 07b4:0109 Olympus Optical Co., Ltd C-370Z/D-535Z/X-450 $ lsusb -v -d 07b4:0109 Bus 002 Device 005: ID 07b4:0109 Olympus Optical Co., Ltd C-370Z/D-535Z/X-450 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x07b4 Olympus Optical Co., Ltd idProduct 0x0109 C-370Z/D-535Z/X-450 bcdDevice 0.00 iManufacturer 3 OLYMPUS iProduct 4 X450/D535Z/C370Z iSerial 5 712591784 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 5 SFF-8070i bInterfaceProtocol 80 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0000 (Bus Powered) Dmesg output from console: -------------------------- usb 2-2: new full speed USB device using uhci_hcd and address 5 usb 2-2: configuration #1 chosen from 1 choice scsi5 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning usb-storage: device scan complete scsi 5:0:0:0: Direct-Access OLYMPUS X450/D535Z/C370Z 1.00 PQ: 0 ANSI: 0 CCS sd 5:0:0:0: [sdb] 256000 512-byte hardware sectors (131 MB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 00 06 00 00 sd 5:0:0:0: [sdb] Assuming drive cache: write through sd 5:0:0:0: [sdb] 256000 512-byte hardware sectors (131 MB) sd 5:0:0:0: [sdb] Write Protect is off sd 5:0:0:0: [sdb] Mode Sense: 00 06 00 00 sd 5:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 5:0:0:0: [sdb] Attached SCSI removable disk Dmesg output from KDE: ---------------------- usb 2-2: new full speed USB device using uhci_hcd and address 2 usb 2-2: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning usb 2-2: usbfs: process 28910 (kio_kamera) did not claim interface 0 before use usb 2-2: usbfs: process 28910 (kio_kamera) did not claim interface 0 before use -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kamera depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-4 core libraries and binaries for al ii libc6 2.7-11 GNU C Library: Shared libraries ii libgcc1 1:4.3.0-4 GCC support library ii libgphoto2-2 2.4.0-9 gphoto2 digital camera library ii libgphoto2-port0 2.4.0-9 gphoto2 digital camera port librar ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.0-4 The GNU Standard C++ Library v3 kamera recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 480866-done@bugs.debian.org
- Subject: Re: Bug#480866: kamera does not mount my USB camera
- From: Sune Vuorela <Sune@vuorela.dk>
- Date: Mon, 12 May 2008 18:03:03 +0200
- Message-id: <200805121803.20484.Sune@vuorela.dk>
- In-reply-to: <[🔎] 1210605839.4592.7.camel@palas.pedraz.fam>
- References: <[🔎] 20080512102845.30202.50334.reportbug@palas.pedraz.fam> <handler.480866.B.121059797416564.ack@bugs.debian.org> <[🔎] 1210605839.4592.7.camel@palas.pedraz.fam>
On Monday 12 May 2008, Pelayo Gonzalez wrote: > Further search reveals that this is related to libgphoto-2-2 bug 459017 > as symptoms are the same. > > Please feel free to close this bug if this is the case. As kamera is just a fancy frontend to gphoto, this is almost certainly the same bug. /Sune -- Genius, I cannot uninstall the analogic icon, how does it work? From ICQ or from the control panel inside ICQ 97 you either should overclock a DirectX application, or should never insert the proxy of a prompt in order to cancel a mousepad over the controller to a 94X OpenGL space bar on the connection.Attachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---