December 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 332506] New: udev rule for logitech mice doesn't work (/etc/udev/rules .d/40-lomoco.rules)
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=332506 Summary: udev rule for logitech mice doesn't work (/etc/udev/rules.d/40-lomoco.rules) Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kra(a)ecolog.at QAContact: qa(a)suse.de Found By: Customer the udev rule for logitech mice which is stored in file /etc/udev/rules.d/40-lomoco.rules from rpm-package lomoco-1.0-15 doesn't work. 1. problem: it seems the conditions in 40-lomoco.rules for starting the program "lomoco" are set wrong. whatever you plug in into usb-port, it seems the script goes directly to the end-label ans skips every start of "lomoco". 2. problem: the call for program "lomoco" itself is wrong. instead the script "/lib/udev/lomoco.sh" should be called, which takes respect to the config-switches stored in config file /etc/sysconfig/logitech_mouse. -- 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 345575] New: Xen xm save does not work
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=345575#c1 Summary: Xen xm save does not work Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SLES 10 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: stephan.duehr(a)dass-it.de QAContact: qa(a)suse.de Found By: Third Party Developer/Partner We found this problem on SLES 10 SP1 when we wanted to do live migration. The Xen host runs on a Dell 1950 in 64-Bit mode: xen01:~ # uname -a Linux xen01 2.6.16.53-0.16-xen #1 SMP Tue Oct 2 16:57:49 UTC 2007 x86_64 x86_64 x86_64 GNU/Linux The latest versions of the Xen packages are installed: xen01:~ # rpm -qa|fgrep xen xen-doc-html-3.0.4_13138-0.57 xen-libs-3.0.4_13138-0.57 xen-doc-pdf-3.0.4_13138-0.57 kernel-xen-2.6.16.53-0.16 xen-3.0.4_13138-0.57 xen-tools-3.0.4_13138-0.57 xen-tools-ioemu-3.0.4_13138-0.57 The domU runs SLES 10 SP1 32-Bit paravirtualized. When trying live migration, the following error occurs: xm migrate 9 10.74.0.12 -l Error: /usr/lib64/xen/bin/xc_save 22 9 0 0 1 failed Calling xm save only yields almost the same error: xen01:/etc/xen/vm # xm save 9 sl10cl.chk Error: /usr/lib64/xen/bin/xc_save 22 9 0 0 0 failed for xm migrate /var/log/xen/xend.log says: [2007-11-22 09:20:34 xend 4920] DEBUG (balloon:146) Balloon: 1049524 KiB free; need 3072; done. [2007-11-22 09:20:34 xend 4920] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib64/xen/bin/xc_save 22 9 0 0 1 [2007-11-22 09:20:34 xend 4920] INFO (XendCheckpoint:247) ERROR Internal error: Domain is not in a valid Linux guest OS state [2007-11-22 09:20:34 xend 4920] INFO (XendCheckpoint:247) Save exit rc=1 [2007-11-22 09:20:34 xend.XendDomainInfo 4920] DEBUG (XendDomainInfo:768) Storing domain details: {'console/ring-ref': '417744', 'console/port': '2', 'name': 'migrating-sl10cl', 'console/limit': '1048576', 'vm': '/vm/e7bddc31-59b9-2dbb-c0ec-9f969ed72691', 'domid': '9', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '417745', 'store/port': '1'} [2007-11-22 09:20:34 xend 4920] ERROR (XendCheckpoint:111) Save failed on domain sl10cl (9). Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 97, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 235, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_save 22 9 0 0 1 failed [2007-11-22 09:20:34 xend.XendDomainInfo 4920] DEBUG (XendDomainInfo:768) Storing domain details: {'console/ring-ref': '417744', 'console/port': '2', 'name': 'sl10cl', 'console/limit': '1048576', 'vm': '/vm/e7bddc31-59b9-2dbb-c0ec-9f969ed72691', 'domid': '9', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '417745', 'store/port': '1'} And for xm save /var/log/xen/xend.log says: [2007-11-22 09:20:34 xend.XendDomainInfo 4920] DEBUG (XendDomainInfo:768) Storing domain details: {'console/ring-ref': '417744', 'console/port': '2', 'name': 'sl10cl', 'console/limit': '1048576', 'vm': '/vm/e7bddc31-59b9-2dbb-c0ec-9f969ed72691', 'domid': '9', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '417745', 'store/port': '1'} [2007-11-22 09:21:23 xend 4920] DEBUG (XendCheckpoint:80) [xc_save]: /usr/lib64/xen/bin/xc_save 22 9 0 0 0 [2007-11-22 09:21:23 xend.XendDomainInfo 4920] DEBUG (XendDomainInfo:768) Storing domain details: {'console/ring-ref': '417744', 'console/port': '2', 'name': 'migrating-sl10cl', 'console/limit': '1048576', 'vm': '/vm/e7bddc31-59b9-2dbb-c0ec-9f969ed72691', 'domid': '9', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '417745', 'store/port': '1'} [2007-11-22 09:21:23 xend 4920] INFO (XendCheckpoint:247) ERROR Internal error: Domain is not in a valid Linux guest OS state [2007-11-22 09:21:23 xend 4920] INFO (XendCheckpoint:247) Save exit rc=1 [2007-11-22 09:21:23 xend 4920] ERROR (XendCheckpoint:111) Save failed on domain sl10cl (9). Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 97, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 235, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_save 22 9 0 0 0 failed [2007-11-22 09:21:23 xend.XendDomainInfo 4920] DEBUG (XendDomainInfo:768) Storing domain details: {'console/ring-ref': '417744', 'console/port': '2', 'name': 'sl10cl', 'console/limit': '1048576', 'vm': '/vm/e7bddc31-59b9-2dbb-c0ec-9f969ed72691', 'domid': '9', 'cpu/0/availability': 'online', 'memory/target': '524288', 'store/ring-ref': '417745', 'store/port': '1'} The same error message "ERROR Internal error: Domain is not in a valid Linux guest OS state" always appears, no matter if xm migrate or xm save. Any idea what's the problem? Here the details of the VM: xen01:/etc/xen/vm # xm list -l sl10cl (domain (domid 9) (on_crash destroy) (memory 512) (uuid e7bddc31-59b9-2dbb-c0ec-9f969ed72691) (bootloader_args '--entry=xvda1:/boot/vmlinuz-xenpae,/boot/initrd-xenpae') (name sl10cl) (maxmem 512) (on_reboot restart) (on_poweroff destroy) (vcpus 1) (bootloader /usr/lib/xen/boot/domUloader.py) (shadow_memory 0) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1195719335.06) (cpu_time 15.890284846) (online_vcpus 1) (image (linux (kernel /var/lib/xen/tmp/kernel.FlKaLU) (ramdisk /var/lib/xen/tmp/ramdisk.Q7fGIf) (args ' ') ) ) (status 2) (memory_dynamic_min 512) (memory_dynamic_max 512) (state -b----) (store_mfn 417745) (console_mfn 417744) (device (vif (mac 00:16:3e:0b:3a:7f) (script vif-bridge) (uuid 2b6c32d0-fe6d-b3a4-5795-0c638d949df3) (backend 0) ) ) (device (vbd (uuid a4ee8ada-1b16-1413-cf88-64abd55652e7) (dev xvda:disk) (uname phy:/dev/disk/by-id/scsi-36090a018401ad6ea4874d4840daab3f0) (mode w) (type disk) (backend 0) ) ) (device (vkbd (backend 0))) (device (vfb (vncunused 1) (location localhost:5901) (type vnc) (xauthority /root/.Xauthority) (uuid a39439ce-86f3-3e87-3919-8a59efa8f60e) ) ) (device (console (protocol vt100) (location 2) (uuid efcf22b3-3f7d-1170-8506-78640d87b898) ) ) ) This is how our xend-config.sxp looks like: xen01:/etc/xen # grep -v ^# xend-config.sxp |grep -v ^$ (xen-api-server ((unix none))) (xend-http-server yes) (xend-unix-server yes) (xend-relocation-server yes) (xend-port 8000) (xend-relocation-port 8002) (xend-relocation-address '') (xend-relocation-hosts-allow '') (network-script 'network-bridge netdev=eth6') (vif-script vif-bridge) (dom0-min-mem 196) (dom0-cpus 0) (vncpasswd '') -- 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 2

[Bug 345661] New: TexLive does not contain fancyheadings.sty
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=345661 Summary: TexLive does not contain fancyheadings.sty Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jarl(a)softace.dk QAContact: qa(a)suse.de Found By: Customer ERROR: LaTeX Error: File `fancyheadings.sty' not found. kpsewhich fancyheadings.sty gives nothing. -- 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 2

[Bug 338395] New: No sound for new users
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=338395 Summary: No sound for new users Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: steffen.sobiech(a)gmx.de QAContact: qa(a)suse.de Found By: Other After creating a new user with YaST, this user has no sound in KDE. Steps to reproduce: 1. Fresh install of openSUSE 10.3 2. During setup, create the standard user (the sound will work for him) 3. In the running system, create a new user with YaST, leaving the defaults 4. Log into KDE with that new user 5. Try to play some sound e.g. with Amarok. The interesting thing is that the default user created during install is in the same groups as the newly created user: users, dialout, video. But the sound does not work for the newly created user. Permission problem nontheless? Even when I add the newly created user to the audio group, sound doesn't work. I tested this with 2 different computers, so it should not be a hardware issue. I don't know if this is a duplicate of another bug (I found none). -- 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 18

[Bug 344884] New: static executables are missing from module-init-tools
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344884 Summary: static executables are missing from module-init-tools Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: zoli(a)polarhome.com QAContact: qa(a)suse.de Found By: Customer In erlier releases there are the following static executables delivered: /sbin/insmod.static /sbin/lsmod.static /sbin/modinfo.static /sbin/modprobe.static /sbin/rmmod.static In 10.3 release Name : module-init-tools Relocations: (not relocatable) Version : 3.2.99.pre11 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 23 These static executables are missing. These static executables are extremely vital in deploying OpenSuSE based initrd's. >From other side there is not a big deal to deliver them for the rpm builder. Thank you in advance. Regards, Z -- 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 344289] New: yast2 scanner: when editing a detected scanner ( Canon Lide20 ) yast aborts
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344289 Summary: yast2 scanner: when editing a detected scanner ( Canon Lide20 ) yast aborts Product: openSUSE 11.0 Version: unspecified Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)yahoo.com QAContact: jsrain(a)novell.com Found By: Beta-Customer In openSuSE 10.3.1 when starting yast2 scanner and editing a detected device, yast aborts showing an xmessage stating: YaST got signal 11 at YCP file Wizard.ycp:1002 /sbin/yast2: line 431: 8414 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS -- 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 310425] New: PrintScreen problems in y2base
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=310425 Summary: PrintScreen problems in y2base Product: openSUSE 10.3 Version: Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: jsrain(a)novell.com Found By: --- trying to update from SUSE 10.1 to 10.3 (beta-3), old system is mounted in /mnt in y2base package selection I try to get a screen shot by pressing PrintScreen key. problem 1 : I saved the 1st screen shot as yast2-000.png into /root/yast2-/screen-shots/ as default. but I'd like to save shorts directly into /mnt/root/s103/ (directory exists already). the file selector shows some *.png in that directory, but when I press "save", the file selector box switches back to /root/yast2-/screen-shots/ and displays the 1st yast2-000.png -- no file has been saved :-( whatever I try -- it's not possible to save shots directly to /mnt/root/s103/ :-( problem 2: in package selection when checking for confilcts, the PrintScreen key is disabled (doesn't work) while the "Warning" window with pkg conflict information is shown. after closing that window (cancel) print screen works again. BUT it's not possible to get a sceen shot of those conflict window. yes I know I can save the text with "expert->save" but there is much more information on the screen (e.g. disk usage) on the screen... -- 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 344034] New: proxy authentication with online updates
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344034 Summary: proxy authentication with online updates Product: openSUSE 10.3 Version: Final Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: x10050614(a)stuttgart.de QAContact: jsrain(a)novell.com CC: x10050614(a)stuttgart.de Found By: --- Hi all, with yast we weren't able to install online updates on openSUSE 10.3. We've done the following: - yast -> Software -> Online Update Configuration -> Next (automatically checked "Configure Now (Recommended)") Finally we've got "Your configuration was successful. An update server has been added to your configuration." The update server is "http://download.opensuse.org/update/10.3/?alias=openSUSE-10.3-Updates". - yast online_update Here we get the final message "No active update source is available." In the network trace (text based wireshark) on openSUSE 10.3 we see: Hypertext Transfer Protocol GET http://download.opensuse.org/update/10.3/media.1/products HTTP/1.1\r\n Request Method: GET Request URI: http://download.opensuse.org/update/10.3/media.1/products Request Version: HTTP/1.1 Proxy-Authorization: Basic Og==\r\n Credentials: : User-Agent: Novell ZYPP Installer\r\n Host: download.opensuse.org\r\n Pragma: no-cache\r\n Accept: */*\r\n Proxy-Connection: Keep-Alive\r\n \r\n For a comparison here almost the same network packet on openSUSE 10.2: Hypertext Transfer Protocol GET http://ftp.gwdg.de/pub/suse/update/10.2/repodata/repomd.xml HTTP/1.1\r\n Request Method: GET Request URI: http://ftp.gwdg.de/pub/suse/update/10.2/repodata/repomd.xml Request Version: HTTP/1.1 Proxy-Authorization: Basic dTEwNHNlY3A6TmhvbGFlemx1Zw==\r\n Credentials: Benutzer:Geheim User-Agent: Novell ZYPP Installer\r\n Host: ftp.gwdg.de\r\n Pragma: no-cache\r\n Accept: */*\r\n Proxy-Connection: Keep-Alive\r\n \r\n We think the proxy authentification with online updates on openSUSE 10.3 doesn't work correctly. Could you please try to reproduce and correct the problem if necessary. Thank you very much. -- 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 2

[Bug 342348] New: Proxy config problemas [Yast2]
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=342348 Summary: Proxy config problemas [Yast2] Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alexio44(a)gmail.com QAContact: jsrain(a)novell.com Found By: Customer The Proxy configuration [alternative] is set up right all the configurations are good, and the test says OK BUT at the time that I accept the configuration at YAST nothing happens I have to go to a gnome-terminal and do rcnetwork restart to make the new proxy configuration ACTIVE -- 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 344812] New: zypper man page is incorrect
by bugzilla_noreply＠novell.com 04 Dec '07

04 Dec '07

https://bugzilla.novell.com/show_bug.cgi?id=344812 Summary: zypper man page is incorrect Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: dmacvicar(a)novell.com ReportedBy: leo(a)nwfactory.net QAContact: dmacvicar(a)novell.com Found By: Customer # zypper -V zypper 0.8.25 # zypper -h Options: --help, -h Help. --version, -V Output the version number. --quiet, -q Suppress normal output, print only error messages. --verbose, -v Increase verbosity. --terse, -t Terse output for machine consumption. --table-style, -s Table style (integer). --rug-compatible, -r Turn on rug compatibility. --non-interactive, -n Don't ask anything, use default answers automatically. --no-gpg-checks Ignore GPG check failures and continue. --root, -R <dir> Operate on a different root directory. Commands: help, ? Help shell, sh Accept multiple commands at once install, in Install packages or resolvables remove, rm Remove packages or resolvables search, se Search for packages matching a pattern repos, lr List all defined repositories. addrepo, ar Add a new repository removerepo, rr Remove specified repository renamerepo, nr Rename specified repository modifyrepo, mr Modify specified repository refresh, ref Refresh all repositories patch-check, pchk Check for patches patches, pch List patches list-updates, lu List updates xml-updates, xu List updates and patches in xml format update, up Update installed resolvables with newer versions. info, if Show full information for packages patch-info Show full information for patches source-install, si Install a source package If I read the man page -n, --name Select resolvables by their name (default). The explanation of the -n option in the help is the correct one (meaning non-interactive mode) -- 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