From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 10:44:13 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D0C716A4B3 for ; Tue, 23 Sep 2003 10:44:13 -0700 (PDT) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD48C43FAF for ; Tue, 23 Sep 2003 10:44:10 -0700 (PDT) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (250-217.customer.cloud9.net [168.100.250.217])h8NHhYLP069721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 23 Sep 2003 13:44:09 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) h8NHiljA086414 for ; Tue, 23 Sep 2003 13:44:49 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: stable@FreeBSD.org Date: Tue, 23 Sep 2003 13:44:46 -0400 User-Agent: KMail/1.5.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309231344.46660@misha-mx.virtual-estates.net> X-Scanned-By: MIMEDefang 2.21 (www . roaringpenguin . com / mimedefang) Subject: hang/crash with KDE's ``kamera'' (usb) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2003 17:44:13 -0000 Hello! The machine runs: 4.9-PRERELEASE #0: Fri Sep 12 15:02:07 EDT 2003 It is a dual PII-Xeon. The camera is attached over USB: uhci0: port \ 0x14e0-0x14ff irq 16 at device 12.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 ugen0: Canon Inc. PowerShot S20, rev 1.00/0.01, addr 2 Accesing the camera with s10sh (from graphics/s10sh) works fine. However, trying to browse the contents using the camera://-style URL from Konqueror quickly causes the machine to stop responding. Sometimes you get to see the contents of toplevel directory of the flashmemory's filesystem, sometimes you don't. The whole machine needs to be rebooted... -mi