March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 486837] New: bad dependencies chain backup-manager - python-setuptools - python-devel
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=486837 Summary: bad dependencies chain backup-manager - python-setuptools - python-devel Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: behlert(a)novell.com QAContact: qa(a)suse.de Found By: Development backup-manager requires python-setuptools python-setup-tools requires python-devel. This is not good. Can we change either backup-manager or python-setuptools? I don't regard it as wise to install 22MB of python-devel for a run-time system. -- 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 7

[Bug 489735] New: pci passthrough of sata_sil24 device requires that firewire "must be co-assigned to the same guest"
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=489735 Summary: pci passthrough of sata_sil24 device requires that firewire "must be co-assigned to the same guest" 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: pgnet.trash(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 i'm running OS 11.1 Dom0, uname -ri 2.6.27.21-4-xen x86_64 i've a sata_sil24 PCS card, 04:07.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) which (now) works fine in Dom0. setup for passthrough to the DomU in xen .cfg, pci = [ '04:07.0' ] @ DomU launch reports, Error: pci: 0000:04:08.0 must be co-assigned to the same guest with 0000:04:07.0 checking @ Dom0 lspci, 04:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) firewire on this box is on the mobo -- completely discrete/separate from the PCI card. iiuc, passthrough of the sata_sil24 card should not require firewire to also be passed thru. 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 10

[Bug 483787] New: NTP Configuration (proposal): UI::ChangeWidget failed: UI::ChangeWidget( `id (`ntp_configure), `Enabled, true )
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=483787 User locilka(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=483787#c483211 Summary: NTP Configuration (proposal): UI::ChangeWidget failed: UI::ChangeWidget( `id (`ntp_configure), `Enabled, true ) Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: mvidner(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Originally reported as bug #483211 Created an attachment (id=277866) --> (https://bugzilla.novell.com/attachment.cgi?id=277866) --- cut --- 2009-03-07 14:25:39 <1> 192.168.150.47(3969) [Interpreter] clients/ntp-client_proposal.ycp:287 Called YaST client returned. 2009-03-07 14:25:39 <2> 192.168.150.47(3969) [ui] YWidget.cc(findWidget):611 THROW: No widget with ID `ntp_configure 2009-03-07 14:25:39 <2> 192.168.150.47(3969) [ui] YCP_UI.cc(ChangeWidget):685 CAUGHT: No widget with ID `ntp_configure 2009-03-07 14:25:39 <3> 192.168.150.47(3969) [libycp] timezone/dialogs.ycp:175 UI::ChangeWidget failed: UI::ChangeWidget( `id (`ntp_configure), `Enabled, true ) 2009-03-07 14:25:39 <1> 192.168.150.47(3969) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished --- cut --- -- 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 3

[Bug 490727] New: Absurdly verbose output in warning log when placing a blank dvd in burner
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490727 Summary: Absurdly verbose output in warning log when placing a blank dvd in burner Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1 Firefox/3.0.7 Tit: Absurdly verbose output in warning log when placing a blank dvd in burner system 11.0, PATA. When I put a blank DVD in my burner, I get and absurdly verbose output in /var/log/warn. This output can be correct in the kernel log, of course, but not with a warning level. The warn log should have a line or two to warn the admin of real problems: the admin then goes to the detailed log to see the details. Too much text in the warning log and it becomes useless. This are the log entries in /var/log/warn: Mar 31 13:47:11 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Mar 31 13:47:11 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Mar 31 13:47:11 nimrodel kernel: ide: failed opcode was: unknown Mar 31 13:47:11 nimrodel kernel: ATAPI device hdc: Mar 31 13:47:11 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Mar 31 13:47:11 nimrodel kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Mar 31 13:47:11 nimrodel kernel: The failed "Read 10" packet command was: Mar 31 13:47:11 nimrodel kernel: "28 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 " Mar 31 13:47:11 nimrodel kernel: end_request: I/O error, dev hdc, sector 0 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 0 Mar 31 13:47:11 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Mar 31 13:47:11 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Mar 31 13:47:11 nimrodel kernel: ide: failed opcode was: unknown Mar 31 13:47:11 nimrodel kernel: ATAPI device hdc: Mar 31 13:47:11 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Mar 31 13:47:11 nimrodel kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Mar 31 13:47:11 nimrodel kernel: The failed "Read 10" packet command was: Mar 31 13:47:11 nimrodel kernel: "28 00 00 00 00 02 00 00 06 00 00 00 00 00 00 00 " Mar 31 13:47:11 nimrodel kernel: end_request: I/O error, dev hdc, sector 8 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 1 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 2 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 3 Mar 31 13:47:11 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Mar 31 13:47:11 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Mar 31 13:47:11 nimrodel kernel: ide: failed opcode was: unknown Mar 31 13:47:11 nimrodel kernel: ATAPI device hdc: Mar 31 13:47:11 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Mar 31 13:47:11 nimrodel kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Mar 31 13:47:11 nimrodel kernel: The failed "Read 10" packet command was: Mar 31 13:47:11 nimrodel kernel: "28 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 " Mar 31 13:47:11 nimrodel kernel: end_request: I/O error, dev hdc, sector 0 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 0 Mar 31 13:47:11 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Mar 31 13:47:11 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Mar 31 13:47:11 nimrodel kernel: ide: failed opcode was: unknown Mar 31 13:47:11 nimrodel kernel: ATAPI device hdc: Mar 31 13:47:11 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Mar 31 13:47:11 nimrodel kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Mar 31 13:47:11 nimrodel kernel: The failed "Read 10" packet command was: Mar 31 13:47:11 nimrodel kernel: "28 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 " Mar 31 13:47:11 nimrodel kernel: end_request: I/O error, dev hdc, sector 0 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 0 Mar 31 13:47:11 nimrodel kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Mar 31 13:47:11 nimrodel kernel: hdc: command error: error=0x50 { LastFailedSense=0x05 } Mar 31 13:47:11 nimrodel kernel: ide: failed opcode was: unknown Mar 31 13:47:11 nimrodel kernel: ATAPI device hdc: Mar 31 13:47:11 nimrodel kernel: Error: Illegal request -- (Sense key=0x05) Mar 31 13:47:11 nimrodel kernel: Illegal mode for this track or incompatible medium -- (asc=0x64, ascq=0x00) Mar 31 13:47:11 nimrodel kernel: The failed "Read 10" packet command was: Mar 31 13:47:11 nimrodel kernel: "28 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 " Mar 31 13:47:11 nimrodel kernel: end_request: I/O error, dev hdc, sector 0 Mar 31 13:47:11 nimrodel kernel: Buffer I/O error on device hdc, logical block 0 Reproducible: Always -- 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 490688] New: rename mail server module from "Mail Transfer Agent" to "Mail Server"
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490688 Summary: rename mail server module from "Mail Transfer Agent" to "Mail Server" Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Almost all modules in the YaST control center category "Network Services" are labeled "XY server" or "XY client". One of the exceptions is the mail server module which appears in the control center as "Mail Transfer Agent". To improve consistency in YaST, please label it into "Mail Server". Thanks! -- 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 451011] New: "Create virtual machines" does not open and has no user visible error message
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=451011 Summary: "Create virtual machines" does not open and has no user visible error message Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hfiguiere(a)novell.com QAContact: jsrain(a)novell.com Found By: --- xend is not runing because I don't run a Xen kernel. If I click on "Create Virtual Machines" (because I just installed the tools), it does NOTHING. I get in the console (started yast from the command line): libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory Error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory Expected: A user visible message explaining it can connect to the hypervisor or something. -- 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 7

[Bug 457083] New: Virtual machine for WinXP doesn' t support National Language Keyboard layout
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=457083 Summary: Virtual machine for WinXP doesn't support National Language Keyboard layout Product: openSUSE 11.1 Version: RC 1 Platform: x86-64 OS/Version: Windows XP 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: --- With YaST2 I created a virtual machine for WindowsXP and succeeded to install Windows XP (Norwegian version) from CD-ROM installation source. A couple of issues during the early XP installation phases, as shown on the attached screenshots, were 1. Typing the <F8> key to accept the XP license agreement didn't work. Had to send F8 from the context menu instead 2. After copying the XP files, an error message told that the VM Console couldn't be opened, and the XP installation was quitted (disappeared). I had to manually start VM Manager from YaST to be able to continue the WinXP setup part of the installation Norwegian Language layout for the keyboard was selected during this setup. 3. The major issue that was discovered during the late XP setup, writing in the fields for user name and hostname, was the that the Norwegian keyboard language didn't work. When typing the special Norwegian keys for the characters 'æøå' or 'ÆØÅ', nothing was written, while typing '-' became '+' instead. After the installation, starting XP and WordPad, the same happened. (I think a related issue previous on Suse/SLE-10 prohibited to enter the right registering codes for Windows XP, as not all keys worked) -- 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 11

[Bug 490246] New: openSuSE-Branding-KDM-Package: kdm and kde4 starts with intermediate images (pixels from former session
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490246 Summary: openSuSE-Branding-KDM-Package: kdm and kde4 starts with intermediate images (pixels from former session Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: maand(a)gmx.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.1.19) Gecko/20081213 SUSE/2.0.0.19-0.1 Firefox/2.0.0.19 I installed KDE 4.2.1 on a openSuSE 11.1. If I use the package openSuSE-Branding-KDM instead of the upstream package I get intermediate images (pixels from a former session; mostly distorted), first while KDM launches and then a second and third while KDE 4.2.1 launches. If I replace the branding package with the upstream I get only one intermediate image (while KDE 4.2.1 launches). The first and the second intermediate images are gone. My system: Medion Akoya mini with Atom 270 and GM 945 (Intel graphic), openSuSE 11.1-i586, KDE 4.2.1 Reproducible: Always Steps to Reproduce: 1.Go to runlevel 5 2.While KDM starts look at the screen 3.While you log in look a second time at the screen 4.If you log out in KDE you get an intermediate image again. Actual Results: see above Expected Results: no intermediate images -- 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 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