Re: how to log mozilla crash?
> i do it and this what is get: > -=-=- > [EMAIL PROTECTED]:~$ script -c "strace /usr/bin/mozilla-1.7.3" moz.log > Script started, file is moz.log > Script done, file is moz.log > [EMAIL PROTECTED]:~$ cat moz.log > Script started on Sat 09 Oct 2004 09:30:28 PM AST > > Script done on Sat 09 Oct 2004 09:30:28 PM AST > -=-=- > > it seems that there's something wrong! Yes, there is something wrong. Probably your path to mozilla is wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Firefox, Thunderbird etc.
Hi, Sorry if this has been asked before on the list. Does anyone know when is the firefox (or thunderbird) package going to be in the unstable/testing of Debian Sarge? I am on sarge (testing) and can see only Firefox version 0.9.3 Thanks, Sayantan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problem using Canon SD400 on Debian Sarge
Hello, I recently got a Canon SD400 camera. I have been trying to get it to work with my laptop which runs Debian Sarge but no luck yet :-( I am running kernel version 2.6.12-1-686. I have usb storage working fine. I can use USB hard disks and other kinds of memory sticks by mounting them onto /dev/sda1 ... Coming to the peculiar problem which I face with the camera ... As soon as I plug the camera in, for a brief period it is reported by `lsusb' (from usbutils package). But after a few seconds, the device dissappears from lsusb!! However, it is always to be found in /proc/bus/usb/devices. Any clue as to why this behavior? This camera works with SuSe (I think 10.someversion), but it should work on Debian too!! Thanks for all your help, Sayantan. = Debug information: 1. lsusb -v # For the very short period of time the camera is reported by lsusb Bus 001 Device 009: ID 04a9:310e 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 0x310e bcdDevice0.02 iManufacturer 1 iProduct2 iSerial 0 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 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 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 32 can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted 2. cat /proc/bus/usb/devices # Device info for the camera T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=310e Rev= 0.02 S: Manufacturer=Canon Inc. S: Product=Canon Digital Camera C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=32ms 3. tail -f /var/log/messages # When camera is inserted and turned on Oct 3 21:50:39 localhost kernel: usb 1-1: new full speed USB device using uhci_hcd and address 10 Oct 3 21:50:40 localhost usb.agent[7405]: libgphoto2: loaded successfully -- http://www.cse.ohio-state.edu/~surs
Re: problem using Canon SD400 on Debian Sarge
On 10/3/05, Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: > On Mon, 03 Oct 2005, Sayantan Sur wrote: > > As soon as I plug the camera in, for a brief period it is reported by > > `lsusb' (from usbutils package). But after a few seconds, the device > > dissappears from lsusb!! However, it is always to be found in > > /proc/bus/usb/devices. > > Try lsusb as root. If it shows up, it is just braindamage happening, with a > race condition on USB plugin just to make sure you know that whomever is > responsible for it really needs to get his act together. > > Track down whatever is screwing up with /proc/bus/usb permissions and you > will have the culprit. Thanks a lot! This worked. There is definitely brain damage happening ;-) Apparently, if I run lsusb as root, everything is just fine. However, as Tom else pointed out on the list, it is not accessible as a Mass Storage Device. Now, if I use gphoto2 as root, then everything is just hunky-dory. > > > Oct 3 21:50:40 localhost usb.agent[7405]: libgphoto2: loaded > > successfully > > Ah. This means hotplug is probably the one to blame for the race condition. > Looks like it. Can you tell me what should I do to accurately describe (collect info) the race condition to the developers of gphoto2/usb drivers? Thanks, Sayantan. > -- > "One disk to rule them all, One disk to find them. One disk to bring > them all and in the darkness grind them. In the Land of Redmond > where the shadows lie." -- The Silicon Valley Tarot > Henrique Holschuh > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- http://www.cse.ohio-state.edu/~surs
