February 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 466267] New: Mouse pointer issues in Xen Virtual Machine Console
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=466267 Summary: Mouse pointer issues in Xen Virtual Machine Console Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: terje(a)nordland-teknikk.no QAContact: qa(a)suse.de Found By: --- After installing fullvirtualized Xen guests, both WindowsXP vm, rhel5 (CentOS5.2) vm and openSUSE 10.3 vm on various openSUSE/SLE platforms, there has been mouse pointer issues - during gui installation in the TightVNC window (had to continue with keybard) - and after login to the gui desktop in the Virtual Machine Console (VMC) CTRL+ALT helps to lock the mouse to the vm desktop. But the mouse pointer doesn't move smoothly (jumps) and can be prohibited or difficult to locate on and access menus on the desktop top or bottom bar. Works like a faulty bad roller mouse. Scrolling with the mouse wheel in configuration menus, has caused the windowsxp vmc to freeze for a while. This mouse issue cause that fullvirtualized Xen vm desktop guest are practical unuseable from the Virtual Machine Console (VMC). And as external connection to Windowsxp vm using rdesktop and i.e 'ssh -X' or 'NX' to the Linux vm desktops don't have this mouse pointer issues, it looks to be a specific related to TightVNC and VMC. 1. What about making these Xen Windows GPL PV drivers available also for openSUSE, maybe these can help on this mouse issue beside better performance? http://wiki.xensource.com/xenwiki/XenWindowsGplPv 2. Maybe this Xen Mouse Howto document has som preconfiguration/tuning tip? http://os-drive.com/files/docbook/xen-mouse.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 467988] New: Filesystem unmount problems during shutdown with Xen kernel
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=467988 Summary: Filesystem unmount problems during shutdown with Xen kernel Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081213 SUSE/2.0.0.19-0.1 Firefox/2.0.0.19 I've installed openSUSE 11.1 with en support. Some filesystem info: carrier4:~ # cat /etc/fstab /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part2 / ext3 defaults 1 1 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part1 /boot ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part8 /home ext3 defaults 1 2 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part3 /tmp ext3 defaults 1 2 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part5 /usr ext3 defaults 1 2 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part6 /var ext3 defaults 1 2 /dev/disk/by-id/scsi-SSun_CARRIER4_81E4E3A0-part7 /var/log ext3 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 carrier4:~ # mount /dev/sda2 on / type ext3 (rw) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda1 on /boot type ext3 (rw,acl,user_xattr) /dev/sda8 on /home type ext3 (rw) /dev/sda3 on /tmp type ext3 (rw) /dev/sda5 on /usr type ext3 (rw) /dev/sda6 on /var type ext3 (rw) /dev/sda7 on /var/log type ext3 (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) Now, when I shut down the system using the Xen kernel, then during the filesystem unmounting phase I got some error messages (see the attached image). I"ve installed both 32 and 64 bit versions with exactly same filesystem layout and both versions give very similar error messages during this phase when running on Xen kernels. This symptom does not happen with the default/pae kernels. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 11.1 with Xen support. 2. Shut it down in a way that you be able to see the output of init scripts Actual Results: You will see error messages during local filesystem unmounts. Expected Results: This shouldn't habbe since it may even cause filesystem corruption. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 474773] New: xen with pygrub uses cached grub menu.lst ,kernel and initrd images
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=474773 Summary: xen with pygrub uses cached grub menu.lst ,kernel and initrd images Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i386 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: kristjan.eentsalu(a)err.ee QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 Hello I have problem with two machines(one with 2 GB and another 12 GB memory)... Sometimes when I start/restart PV guests with pygrub it loads old grub config and/or old kernel and initrd images. It seems to be the same bug as described in here: https://bugzilla.redhat.com/show_bug.cgi?id=466681 my domU conf: bootloader = '/usr/bin/pygrub' memory = 512 name = "kessu" vif = [ 'bridge=br0' ] disk = [ 'phy:/dev/mapper/kessu,xvda,w' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'destroy' Kernel version: 2.6.27.7-9-xen xen versions: xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 xen-3.3.1_18494_03-1.8 Kristjan Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 476453] New: XEN vm destroys filesystem and PostgreSQL DBs on power fail
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=476453 Summary: XEN vm destroys filesystem and PostgreSQL DBs on power fail Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: novell-web(a)zmi.at QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 * Linux host with XEN, XFS filesystem with "nobarrier", RAID controller with battery backed cache as suggested by the XEN FAQ at http://xfs.org/index.php/XFS_FAQ * XEN vm with XFS filesystem with "nobarrier" with postgresql database. * my daughter with 3.5 years switching off the power supply of the server (behind the UPS of course) After restart, the XEN vm postgresql db was destroyed, obviously because some files (at least pg_clog/0891) were missing. This should never ever happen. Is there a way to run a XEN vm secured from this sort of error? I reported this to the XFS devs, and got the reply that also on ext3 that can happen, so it doesn't seem XFS related. Still, I need a secure way to run a XEN VM, as we want to use it on production servers... Reproducible: Always Steps to Reproduce: See the "Details" section first three steps. Expected Results: A normal crashed filesystem which recovers and doesn't destroy postgresql. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 341350] New: severe limitations in xen-tools python scripts
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=341350 Summary: severe limitations in xen-tools python scripts Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: duwe(a)novell.com QAContact: qa(a)suse.de Found By: Development qemu-dm appears to be accepting the same type of arguments as qemu does; however the automatically generated command line is impossible to contain 1st) multiple "-usbdevice" switches -- one is already used up by the "tablet" option. 2nd) a "-parallel" switch This may not be serious for a server virtualisation, but it surely hurts on the desktop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 343180] New: XEN keymap problem.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343180 Summary: XEN keymap problem. Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: Other I installed Vindows Vista on Xen by vm-install ran from YaST with the following settings (/etc/xen/vm/windowsvista): ############################################### name="windowsvista" ostype="windowsvista" uuid="cf93a3e0-c33f-50c4-dd3f-b68691418a40" memory=1024 vcpus=1 on_crash="destroy" on_poweroff="destroy" on_reboot="restart" localtime=1 builder="hvm" extid=0 device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" boot="c" disk=[ 'file:/mnt/xen/vista.bin,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r', ] vif=[ 'mac=00:16:3e:1a:4d:7d,model=rtl8139,type=ioemu', ] stdvga=0 vnc=1 vncunused=1 apic=0 acpi=1 pae=1 usb=1 usbdevice='tablet' serial="pty" ############################################### I tried to manage this qemu-dm assisted fully virtualized host either via VNC or SDL (changing the config file above), but I realized that the host's keyboard map was incomplete and incorrect. Let's see a sort example from the file /var/log/xen qemu-dm.29632.log: ############################################### Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 501 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 Warning: no scancode found for keysym 507 ############################################### I figured out that the problem could by corrected by make qemu-dm use some of the keymaps under /usr/share/xen/qemu/keymaps by passing a -key CODE parameter to it. Or am I wrong? I also figured out that I can make xend to pass this parameter to qemu-dm by adding a keymap='CODE' line to the /etc/xen/vm/VM file. So I added the line keymap='hu' to the vm config file, and qemu-vm's command line really changed: milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ /usr/lib/xen/bin/qemu-dm -d 2 -vcpus 1 -boot c -localtime -serial pty -acpi -usb -usbdevice tablet -k hu -domain-name windowsvista -net nic,vlan=1,macaddr=00:16:3e:1a:4d:7d,model=rtl8139 -net tap,vlan=1 -vncunused -vnclisten 127.0.0.1 milleniumfalcon:/var/log/xen # cat /proc/8046/cmdline | sed y/'\x0'/' '/ The keyboard got a bit better but there are still missing keys, "ű" for example. I tried other keymaps with similar results. What may be wrong with these keymaps? Are they defectivein a way? I have no idea. Thist bug report is primarily about the possible errors int these keymap files, but I have other related quetions too: It wold be good to make it possible to change the keymap setting in vm-install if it is necessary at all. Furthermore I do not know where virt-manager gets the information about VMs from. Once I moved every file from /etc/xen/vm to the root directory, restarted virt-manager and in spite of the lack of VM description files it still remebered my guest VM. I also do not know, what keeps the files /etc/xen/vm/VM and /etc/xen/vm/VM.xml in synchron. So, if i add a keymap to the file /etc/xen/vm/VM then that VM will use that keymap if I start if by the xm command. But what happens if i start that VM from virt-manager? Do I also need to add the keymap to the file /etc/xen/vm/VM.xml? Or to a third file? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 449785] New: Installing of GRUB fails when using live installer from a USB stick
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=449785 Summary: Installing of GRUB fails when using live installer from a USB stick Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: juhliarik(a)novell.com ReportedBy: awafaa(a)opensuse.org QAContact: jsrain(a)novell.com Found By: --- When trying to install openSUSE 11.0 via USB stick the installation of GRUB fails each time. The error I get is: GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> setup --stage2=/boot/grub/stage2 (hd0) (hd0,0) Error 22: No such partition grub> quit YaST correctly recognises the partitions, but refuses to install the boot loader leaving the system useless. If I select Boot Loader Installation -> button Boot Loader Installation Detaials all i get from that is there are no options to set for current boot loader. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 462707] New: No support for Poulsbo Graphics Chipset
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=462707 User ultimatedevr(a)yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462707#c17 Summary: No support for Poulsbo Graphics Chipset Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: ultimatedevr(a)yahoo.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Other I'm using a Kohjinsha SC3 and am currently running openSUSE 11.1 on it; everything works properly except for the graphics driver; there is no psb driver for X.Org under openSUSE, so I must use vesa, which does not allow me to change the resolution to anything above 800x600 (However it works perfectly with the psb driver on the Ubuntu LiveCD). I have tried to compile the psb driver from source, however I get this error (this is for the kernel module psb from the moblin site (psb-kmd), not the ubuntu source package:) make -C /lib/modules/2.6.25.18-0.2-default/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules make[1]: Entering directory `/usr/src/linux-2.6.25.18-0.2' CC [M] /home/ultimatedevr/Desktop/psb-kmd/drm_drv.o /home/ultimatedevr/Desktop/psb-kmd/drm_drv.c: In function ‘drm_core_init’: /home/ultimatedevr/Desktop/psb-kmd/drm_drv.c:478: error: implicit declaration of function ‘drm_init_pat’ make[2]: *** [/home/ultimatedevr/Desktop/psb-kmd/drm_drv.o] Error 1 make[1]: *** [_module_/home/ultimatedevr/Desktop/psb-kmd] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.25.18-0.2' make: *** [modules] Error 2 Also, here's a couple of links for the psb driver from moblin and ubuntu http://git.moblin.org/apt/pool/main/p/psb-kmd/ https://launchpad.net/~ubuntu-mobile/+archive?field.name_filter=xserver-xor… Output of hwinfo --gfx 17: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.310] UDI: /org/freedesktop/Hal/devices/pci_8086_8108 Unique ID: _Znp.+YhPLQ1xMP7 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel VGA compatible controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x8108 SubVendor: pci 0x1170 "Inventec Corporation" SubDevice: pci 0x0032 Revision: 0x06 Memory Range: 0xdff80000-0xdfffffff (rw,non-prefetchable) I/O Ports: 0xe880-0xe887 (rw) Memory Range: 0xd0000000-0xd7ffffff (rw,non-prefetchable) Memory Range: 0xdff60000-0xdff7ffff (rw,non-prefetchable) IRQ: 10 (no events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00008108sv00001170sd00000032bc03sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Primary display adapter: #17 Output of lspci 00:00.0 Host bridge: Intel Corporation System Controller Hub (SCH Poulsbo) (rev 06) 00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 06) 00:1b.0 Audio device: Intel Corporation System Controller Hub (SCH Poulsbo) HD Audio Controller (rev 06) 00:1c.0 PCI bridge: Intel Corporation System Controller Hub (SCH Poulsbo) PCI Express Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation System Controller Hub (SCH Poulsbo) PCI Express Port 2 (rev 06) 00:1d.0 USB Controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #1 (rev 06) 00:1d.1 USB Controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #2 (rev 06) 00:1d.2 USB Controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB UHCI #3 (rev 06) 00:1d.7 USB Controller: Intel Corporation System Controller Hub (SCH Poulsbo) USB EHCI #1 (rev 06) 00:1f.0 ISA bridge: Intel Corporation System Controller Hub (SCH Poulsbo) LPC Bridge (rev 06) 00:1f.1 IDE interface: Intel Corporation System Controller Hub (SCH Poulsbo) IDE Controller (rev 06) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 450944] New: Boot installed system of "repair tool box" doesn't work
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=450944 Summary: Boot installed system of "repair tool box" doesn't work Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: psikodad(a)gmx.de QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=257312) --> (https://bugzilla.novell.com/attachment.cgi?id=257312) yast logs The feature "Boot installed system" of the Repair functions of the DVD doesn't work. 1. Install e.g. KDE3.5 from the RC-1 DVD 32-bit. 2. reboot 3. choose "repair installed system" at the boot menu (of the DVD) 4. click on "expert tools" 5. choose boot installed system error message: "No Linux root partition found" however, "creating a new boot loader" works. Please make it possible to boot from a linux partition. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 28

[Bug 478502] New: No USB mount: usb-storage: waiting for device to settle before scanning
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=478502 User chudikm(a)post.sk added comment https://bugzilla.novell.com/show_bug.cgi?id=478502#c1 Summary: No USB mount: usb-storage: waiting for device to settle before scanning Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chudikm(a)post.sk QAContact: qa(a)suse.de Found By: --- Created an attachment (id=274507) --> (https://bugzilla.novell.com/attachment.cgi?id=274507) dmesg.txt User-Agent: Mozilla/5.0 (X11; U; Linux i686; nb-NO; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 I have Panasonic DMC-FZ7 camera. When I try to connected it to computer via USB and I choose PC mode(on camera), suse is unable to mount/connect it as USB drive Here is what I get from /var/log/messages/ ============================================ Feb 22 14:51:43 linux kernel: hub 7-0:1.0: unable to enumerate USB device on port 2 Feb 22 14:51:44 linux kernel: usb 4-2: new full speed USB device using uhci_hcd and address 3 Feb 22 14:51:44 linux kernel: usb 4-2: configuration #1 chosen from 1 choice Feb 22 14:51:44 linux kernel: scsi5 : SCSI emulation for USB Mass Storage devices Feb 22 14:51:44 linux kernel: usb 4-2: New USB device found, idVendor=04da, idProduct=2372 Feb 22 14:51:44 linux kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 22 14:51:44 linux kernel: usb 4-2: Product: DMC-FZ7 Feb 22 14:51:44 linux kernel: usb 4-2: Manufacturer: Panasonic Feb 22 14:51:44 linux kernel: usb-storage: device found at 3 Feb 22 14:51:44 linux kernel: usb-storage: waiting for device to settle before scanning ============================================ I believe it is some problem with HAL daemon. When I stop it, I can mount USB storage as /dev/sdb1 device ================================================== Feb 22 14:58:32 linux powersaved[3255]: WARNING (filter_function:206) Hal service stopped. Battery information no longer available Feb 22 14:58:44 linux kernel: usb 4-2: new full speed USB device using uhci_hcd and address 4 Feb 22 14:58:44 linux kernel: usb 4-2: configuration #1 chosen from 1 choice Feb 22 14:58:45 linux kernel: scsi6 : SCSI emulation for USB Mass Storage devices Feb 22 14:58:45 linux kernel: usb 4-2: New USB device found, idVendor=04da, idProduct=2372 Feb 22 14:58:45 linux kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 22 14:58:45 linux kernel: usb 4-2: Product: DMC-FZ7 Feb 22 14:58:45 linux kernel: usb 4-2: Manufacturer: Panasonic Feb 22 14:58:45 linux kernel: usb-storage: device found at 4 Feb 22 14:58:45 linux kernel: usb-storage: waiting for device to settle before scanning Feb 22 14:58:46 linux kernel: scsi 6:0:0:0: Direct-Access MATSHITA DMC-FZ7 0100 PQ: 0 ANSI: 2 Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] 3948544 512-byte hardware sectors (2022 MB) Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Write Protect is off Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] 3948544 512-byte hardware sectors (2022 MB) Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Write Protect is off Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through Feb 22 14:58:46 linux kernel: sdb: sdb1 Feb 22 14:58:46 linux kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Feb 22 14:58:46 linux kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Feb 22 14:58:46 linux kernel: usb-storage: device scan complete ================================================================ I found people have similar problems here: http://mail.kde.org/pipermail/digikam-users/2007-October/004313.html http://ubuntuforums.org/showthread.php?t=295423 I am attaching dmesg. thanks. Reproducible: Always Steps to Reproduce: 1.connect camera 2.unplug camera 3.stop hal daemon 4.connect camera one more time Expected Results: aftre step 1. camera should be connected without need of stopping hal daemon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6