March 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 337425] New: No error feedback if using wrong kernel
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=337425 Summary: No error feedback if using wrong kernel Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: jim.pye(a)pyenet.co.nz QAContact: qa(a)suse.de Found By: --- It would be good to have some visual feedback that you are trying to launch the xen Virtual Machine Manager on the wrong kernel. Using KDE and launching the xen VMM from the main menu. If I have booted the machine on the Normal Linux kernel the VMM will not launch. However there is no error message or any indication of what is wrong. Some error dialog at this point would be good indicating the VMM has detected an incorrectly configured kernel. Jim -- 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 364740] New: firewire problem sbp2: probe of 00d04b2b0404ffdc-0 failed with error -16
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=364740 Summary: firewire problem sbp2: probe of 00d04b2b0404ffdc-0 failed with error -16 Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nospam2(a)vajira.co.uk QAContact: qa(a)suse.de Found By: Customer When I first installed 10.3 my firewire devices worked correctly, but now they are no longer recognized as devices. My log gives: Feb 26 00:50:59 padma kernel: ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... Feb 26 00:51:00 padma kernel: ieee1394: Error parsing configrom for node 0-00:1023 Feb 26 00:51:00 padma kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023 Feb 26 00:51:07 padma kernel: ieee1394: Node resumed: ID:BUS[0-00:1023] GUID[00d04b2b0404ffdc] Feb 26 00:51:07 padma kernel: scsi11 : SBP-2 IEEE-1394 Feb 26 00:51:28 padma kernel: ieee1394: sbp2: Error logging into SBP-2 device - timed out Feb 26 00:51:28 padma kernel: sbp2: probe of 00d04b2b0404ffdc-0 failed with error -16 I updated my kernel to Linux 2.6.22.17-0.1-default when it became available on the repository & that is the only change I can think of that could cause a problem. If I boot with windows all works perfectly. -- 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 369051] New: Maintenance Package update fails due to wrong disksize warning
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=369051 Summary: Maintenance Package update fails due to wrong disksize warning Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chuller(a)novell.com QAContact: qa(a)suse.de Found By: --- Description: I installed a OpenSUSE 10.3 and tried to install maintenance updates after the Installation. However, the install process stopped with this error message: ------------------------------------snip------------------------------------------ Subprocess failed. Error: RPM failed: Free diskspace below /boot: 11539728 blocks error: unpacking of archive failed on file /boot/vmlinux-2.6.22.17-0.1-default.gz;46f2c8a3: cpio: read failed - Bad file descriptor ------------------------------------snip------------------------------------------ However, a df in the system showed this situation: ------------------------------------snip------------------------------------------ e221:~ # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 10325748 4037660 5763568 42% / udev 502112 108 502004 1% /dev /dev/sda6 34073212 544 34072668 1% /data ------------------------------------snip------------------------------------------ I'm not sure which package would need more than 5GB for its installation ;) Logs and hwinfo are attached -- 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 12

[Bug 355755] New: iconv from glibc generates nonstandard UCS-2 encoding.
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=355755 Summary: iconv from glibc generates nonstandard UCS-2 encoding. Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)novell.com QAContact: qa(a)suse.de Found By: --- echo Hello World > test.txt iconv -t UCS-2 test.txt > test.ucs2 xxd test.ucs2 0000000: 4800 6500 6c00 6c00 6f00 2000 5700 6f00 H.e.l.l.o. .W.o. 0000010: 7200 6c00 6400 0a00 r.l.d... This hexdump shows little-endian ucs-2, but misses a BOM. The BOM is defined in rfc2781 and explained as follows in http://en.wikipedia.org/wiki/UTF-16: The UTF-16 (and UCS-2) encoding scheme allows either endian representation to be used, but mandates that the byte order should be explicitly indicated by prepending a Byte Order Mark before the first serialized character. This BOM is the encoded version of the Zero-Width No-Break Space (ZWNBSP) character, codepoint U+FEFF, chosen because it should never legitimately appear at the beginning of any character data. This results in the byte sequence FE FF (in hexadecimal) for big-endian architectures, or FF FE for little-endian. The BOM at the beginning of a UTF-16 or UCS-2 encoded data is considered to be a signature separate from the text itself; it is for the benefit of the decoder. [...] The BOM is not optional in the UCS-2 scheme. -- 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 363987] New: No Sound with SiS SI7012
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=363987 Summary: No Sound with SiS SI7012 Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: andreowitsch(a)googlemail.com QAContact: qa(a)suse.de Found By: Customer SiS SI7012 soundcard is wrongly configured by default. this disables any sound output. which means: there is no sound at all. although programs will tell you that they actually do play sound ;) This happened on my Asus A9T laptop, according to google search it always happens with that soundcard. reproduce it that way: this occurs with any version of the linux kernel with any linux distribution. however it does not happen on other systems like freebsd. Steps: 1) installing any distribution (for example opensuse) 2) playing any soundfile for example the linux action show in ogg format 3) hearing no sound :) how to-Fix: I) open console II) su to root III) run alsamixer go right with the arrow keys and 1) <Master_S> (Master Surround): unmute (press m), increase volume (up-arrow key) 2) <PCM>: unmute (press m), increase volume (up-arrow key) 3) <Channel> (Channel Mode): set to 4 or 6 (up-arrow key) 4)<Exchange> (Exchange Front/Surround) unmute (press m) 5)exit press (Esc) 6) hear sound again :) -- 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 13

[Bug 358357] New: [XEN] XEN appears to not boot with VGA message
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=358357 Summary: [XEN] XEN appears to not boot with VGA message Product: openSUSE 11.0 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: sshaw(a)decriptor.com QAContact: jdouglas(a)novell.com Found By: --- I don't remember the settings for miniterm so no output, sorry. It locks the keyboard and displays: Xen is relinquishing VGA console This was an after install, install of XEN. (sorry don't have the dvd, so I added factory) Everything is from factory. -- 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 13

[Bug 367737] New: Realtek AC97 sound: Mono only
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=367737 Summary: Realtek AC97 sound: Mono only Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: bo1(a)hjemmehosbo.dk QAContact: qa(a)suse.de Found By: Other I have a main board of the brand MSI and type G31M-F and with Realtek AC97 surround sound. I have a set of stereo speakers attached (have not tried surround sound). However, I only hear the sound in mono. -- 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 247363] New: dante-server - Ports for SuSEfirewall added via packages
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=247363 Summary: dante-server - Ports for SuSEfirewall added via packages Product: openSUSE 10.3 Version: Alpha 1 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: mge(a)novell.com ReportedBy: locilka(a)novell.com QAContact: qa(a)suse.de There is a new feature: FATE #300687: Ports for SuSEfirewall2 added via packages implemented in SuSEfirewall2 and YaST2-Firewall. This functionality offers to define needed ports for particular package. The definition is then transparently used in Firewall. Please, add such definition into the package mentioned in $subject by following steps in this article: http://en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Packages 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, or are watching someone who is.

1 4

[Bug 340980] New: NoSource: tag in spec files
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=340980 Summary: NoSource: tag in spec files Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: adrian(a)novell.com QAContact: qa(a)suse.de CC: aj(a)novell.com, coolo(a)novell.com, mls(a)novell.com, ro(a)novell.com Found By: --- As discussed before on the research ml: We have currently a policy to disallow "NoSource:" tags in packages for openSUSE distribution. The kernel flavour spec files do contain them currently, what results in nosrc.rpms. Possible solutions: 1. Remove NoSource tag and ship full src.rpms for all flavours 2. Remove NoSource tag and do not ship src.rpms for the kernel flavours, because all sources are already in the kernel-source src.rpm. This would however violate the policy to ship all src.rpms for all $arch.rpms 3. Do a different packaging of the kernel, where the sources come from a central package and do not get package in a all src.rpms. 4. Do stop shipping src.rpms completely, but offering the download via a different mechanism. Please comment what options are thinkable or not acceptable for you. -- 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 331620] New: YaST won't start when logged in as user
by bugzilla_noreply＠novell.com 24 Oct '08

24 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=331620 Summary: YaST won't start when logged in as user Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nonlisted(a)gmail.com QAContact: jsrain(a)novell.com Found By: Other YaST2 just won't show up on my desktop when logged in as normal user. After giving root-password, nothing happens. When doing "su" in terminal then launching Yast with "yast2" it starts, however nothing happends when clicking on stuff in YaST. When launching from terminal I get this (don't know if it's of any help though): (y2controlcenter-gnome:7906): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:7906): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed (y2controlcenter-gnome:7906): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed (y2controlcenter-gnome:7906): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed -- 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 16