March 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 345421] New: AC3 SPDIF passthrough stopped working after alsa upgrade 1.0.13 --> 1.0. 14a on terratec aureon space 7.1 (ice1724)
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=345421 Summary: AC3 SPDIF passthrough stopped working after alsa upgrade 1.0.13 --> 1.0.14a on terratec aureon space 7.1 (ice1724) Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: contezero(a)technet.it QAContact: qa(a)suse.de Found By: --- I've a terratec aureon space 7.1 (ice1724). With alsa version 1.0.13 AC3 SPDIF passthrough works with all players (mplayer, xine, vlc), when I upgrade alsa to 1.0.14a it stop working. On mplayer it works but give the following error: [AO_ALSA] alsa-lib: conf.c:3949:(snd_config_expand) Unknown parameters AES0=6 [AO_ALSA] alsa-lib: pcm.c:2144:(snd_pcm_open_noupdate) Unknown PCM default:AES0=6 On VLC there aren't errors but AC3 sound doesn't work. On Xine AC3 sound doesn't work and give the following error: audio_alsa_out: snd_pcm_open() of iec958:AES0=0x6,AES1=0x82,AES2=0x0,AES3=0x2 failed: Invalid argument audio_alsa_out: >>> check if another program already uses PCM <<< .. ---------------------- (ERROR) ---------------------- The audio device is unavailable. Please verify if another program already uses it. ------------------ (END OF ERROR) ------------------- Normal stereo audio works with SPDIF, the problem is only with AC3. I have tested also with Opensuse 10.3 that ships with alsa 1.0.14 and the problem is the same. I've tried to upgrade to alsa 1.0.15 but it doesn't work. -- 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 26

[Bug 308867] New: Windows NTFS disks not mounted
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=308867 Summary: Windows NTFS disks not mounted Product: openSUSE 10.3 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: trofimich(a)gmail.com QAContact: qa(a)suse.de Found By: Beta-Customer Created an attachment (id=162825) --> (https://bugzilla.novell.com/attachment.cgi?id=162825) Screenshot I've installed OpenSuse 10.3 Beta 2 on disk with Windows partitions (all updates before september 8 unstalled too). I have 3 windows disks: two NTFS and one FAT32. FAT32 disk mounted without problems. Both NTFS disks shown as not mounted after SUSE loaded. I use KDE 3.5.7. When i select "Mount" from popup menu, i've got an error: "Error opening partition device: Access denied" If i enter in KDE under root, than mounting works (working with disks too slow, but this is other question). -- 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 29

[Bug 229853] New: cannot install with clgd5446 pci graphics card
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=229853 Summary: cannot install with clgd5446 pci graphics card Product: openSUSE 10.2 Version: Final Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: teheo(a)novell.com QAContact: jsrain(a)novell.com Okay, call me crazy but I still use Cirrus Logic GD 5446 PCI graphics card (1013:00b8). I can understand if suse 10.2 doesn't support this venerable thingie and x and graphical installation don't work, but complete installation failure is a bit extreme. What happens is... * During the first installation phase, YaST2 complains that the graphics card isn't powerful enough and reverts to text mode, which is all fine and dandy. * After reboot, when the 'continue' phase of YaST installation starts, YaST2 is against started but this time it doesn't revert to text mode. It renders the screen but fails to draw any text or response to input. Switching to other vt works. Switching to vt2 and killing it makes things continue but it ends up at login prompt where root login is prohibited (no password set yet) and no other user added. I don't think clgd5446 support is anywhere near critical, so rejecting this bug is fine too but please consider at least making phase#2 use detection result from phase#1 (ie. if phase#1 was done in console, do the same for phase#2). FYI, clgd5446 can happily do 1024x768x256 X windows. -- 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 30

[Bug 363599] New: Vertical noise on video display with SIS driver at high resolution/ color depth
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=363599 Summary: Vertical noise on video display with SIS driver at high resolution/color depth Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: ms(a)novell.com ReportedBy: ducalen(a)sympatico.ca QAContact: qa(a)suse.de Found By: Other Created an attachment (id=196248) --> (https://bugzilla.novell.com/attachment.cgi?id=196248) Output from lspci -vv I have an Intel D201GLY2 motherboard with sis graphics chipset. Using the sis video driver provided with openSUSE 10.3 results in vertical "noise" bars on my LCD display. The noise increases with higher resolution/color depths (i.e. 1680x1050@24bpp). To have a workable display there are 3 options; 1. Using the default sis driver, drop the resolution/depth to much lower levels than the native screen resoltion, in my case 1024x768@16bpp. 2. Use the vesa driver/resolutions, but my monitor's native resolution (1680x1050) is not supported. 3. Use the latest driver available from the intel site. The problem with this driver is that after the monitor wakes up from suspend, it switches to 1400x1050. Intel driver link: http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=… There's a thread on the ubuntu forum describing the same issue: http://ubuntuforums.org/showthread.php?t=463077 -- 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 33

[Bug 210988] New: kernel cash caused by xorg with two DH Matrox G550
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=210988 Summary: kernel cash caused by xorg with two DH Matrox G550 Product: openSUSE 10.2 Version: Alpha 5 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: lauffer(a)ph-freiburg.de QAContact: sndirsch(a)novell.com My "quad head setup" with two G550 DH (one AGP card, one PCI) worked fine for a long time. But since the xorg-x11-server-6.9.0-50.17 update SL-10.1 update the machine crashes during the start of X11. This bug is in OSS-10.2Alpha5, two. I see there no error logs from the kernel crash (console on ttyS) and no errors logged by the xserver (-verbose 9). The related part of the xorg.conf: <<snip>> [...] Section "Module" Load "type1" Load "dbe" Load "freetype" Load "glx" Load "v4l" Load "extmod" EndSection Section "Device" BoardName "G550" BusID "PCI:1:0:0" Driver "mga" Identifier "Device[0]" Option "hwcursor" "on" Option "MGASDRAM" "off" Chipset "mgag550" VideoRam 32768 Screen 0 VendorName "Matrox" EndSection Section "Device" BoardName "G550" BusID "PCI:1:0:0" Driver "mga" Identifier "Device[1]" Option "hwcursor" "on" Option "MGASDRAM" "off" Chipset "mgag550" VideoRam 32768 Screen 1 VendorName "Matrox" EndSection Section "Device" BoardName "G550" BusID "PCI:3:0:0" Driver "mga" Identifier "Device[2]" Option "hwcursor" "on" Option "MGASDRAM" "off" Chipset "mgag550" VideoRam 32768 Screen 0 VendorName "Matrox" EndSection Section "Device" BoardName "G550" BusID "PCI:3:0:0" Driver "mga" Identifier "Device[2]" Option "hwcursor" "on" Option "MGASDRAM" "off" Chipset "mgag550" VideoRam 32768 Screen 1 VendorName "Matrox" EndSection [...] <<snap>> How can I help? -- 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 52

[Bug 348719] New: X.org leaks a lot of memory (nv driver?)
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=348719 User jensseidel(a)users.sf.net added comment https://bugzilla.novell.com/show_bug.cgi?id=348719#c1 Summary: X.org leaks a lot of memory (nv driver?) Product: openSUSE 10.2 Version: Final Platform: 64bit OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: jensseidel(a)users.sf.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Hi, Xorg leaks a lot of memory. Top reports PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4070 root 15 0 7331m 2.9g 7872 R 2 42.7 122:49.30 Xorg and the value (currently 2.9 GB) increases. xrestop reports that no application is responsible: xrestop - Display: localhost:0 Monitoring 31 clients. XErrors: 0 Pixmaps: 51034K total, Other: 304K total, All: 51339K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 1c00000 2558 128 1 3267 1744 42625K 104K 42729K 5647 Novell Customer Center - Validate Email - Konqueror 1600000 71 123 1 101 162 4206K 9K 4215K 5633 KDE Desktop Details: $ uptime 1:09pm up 34 days 21:10, 13 users, load average: 3.24, 1.54, 1.24 $ rpm -q xorg-x11-server xorg-x11-driver-video xorg-x11-server-7.2-30.8 xorg-x11-driver-video-7.2-33 $ uname -a Linux imkf-pc073 2.6.18-xen #1 SMP Tue Oct 2 16:31:51 CEST 2007 x86_64 x86_64 x86_64 GNU/Linux (xen-3.0-x86_64 self compiled) $ /usr/sbin/hwinfo --gfx 27: PCI 100.0: 0300 VGA compatible controller (VGA) [Created at pci.286] UDI: /org/freedesktop/Hal/devices/pci_10de_391 Unique ID: VCu0.v2eJ1zq6Pz0 Parent ID: vSkL.cutpr6XtQiF SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: graphics card Model: "Giga-byte GeForce 7600 GT" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x0391 "GeForce 7600 GT" SubVendor: pci 0x1458 "Giga-byte Technology" SubDevice: pci 0x3417 Revision: 0xa1 Memory Range: 0xf4000000-0xf4ffffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (rw,prefetchable) Memory Range: 0xf5000000-0xf5ffffff (rw,non-prefetchable) I/O Ports: 0x7000-0x7fff (rw) Memory Range: 0xf6000000-0xf601ffff (ro,prefetchable,disabled) IRQ: 10 (no events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v000010DEd00000391sv00001458sd00003417bc03sc00i00" Driver Info #0: XFree86 v4 Server Module: nv Driver Info #1: XFree86 v4 Server Module: nvidia 3D Support: yes Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #10 (PCI bridge) Primary display adapter: #27 -- 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 334165] New: NetworkManager fails to connect at 28%
by bugzilla_noreply＠novell.com 19 Nov '08

19 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=334165 Summary: NetworkManager fails to connect at 28% Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Eric(a)Kincl.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=178677) --> (https://bugzilla.novell.com/attachment.cgi?id=178677) copy of /var/log/NetworkManager First of all, this is likely a duplicate bug report, but the *method* by which I am getting this error is different than all the others that have similar outcomes. (The others have never worked and are trying to connect to an encrypted network) Much like all the other errors of this type, NetworkManager tries to connect (in this case to a visible and un-encrypted network) and sits at 28% then fails. The difference is that it connected just fine an hour ago, then my computer froze (Having problems with compiz ;-) and now it won't connect. Windows (same machine) connects flawlessly, and Linux ifup method works just fine as well. NetworkManager log is 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 11

[Bug 224476] New: ERROR: Core::SplidDevPath: Cannot get device for (hd0,20)/boot/grub/stage1
by bugzilla_noreply＠novell.com 18 Nov '08

18 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=224476 Summary: ERROR: Core::SplidDevPath: Cannot get device for (hd0,20)/boot/grub/stage1 Product: openSUSE 10.2 Version: RC 1 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mrmazda(a)ij.net QAContact: qa(a)suse.de CC: aj(a)novell.com ERROR: Core::SplidDevPath: Cannot get device for (hd0,20)/boot/grub/stage1 ERROR: Core::SplidDevPath: Cannot get device for (hd0,20)/boot/grub/stage2 These messages happened at the conclusion of using rpm -ivh on the latest kernel yesterday, after the bootsplash messages from mkinitrd. The initial installation was ftp from the beta2 mirror state to hda21. Before upgrading with YaST2 to RC1, I had rearranged my partitioning, and factory was successfully moved to hda10. Afterwards, hda21 no longer existed. At the conclusion of the update to RC1, /etc/grub.conf remained as beta2 installation initially created it, with the obsolete target partition. Either the upgrade process or the kernel installer or both should check to be sure /etc/grub.conf is valid before using it. -- 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 39

[Bug 329280] New: rt2500 driver and AP
by bugzilla_noreply＠novell.com 18 Nov '08

18 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=329280 Summary: rt2500 driver and AP Product: openSUSE 10.3 Version: Beta 3 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: behlert(a)novell.com ReportedBy: snakedriverx(a)gmail.com QAContact: qa(a)suse.de Found By: Customer With the rt2500 driver properly set up in Yast, it requires: "iwlist scan" to detect the AP everytime, including after each boot which means that I have to login as root and issue the command each & every time I boot. BTW, it also refuses the command: "iwconfig wlan0 rate 54M" Hardware is a Sager 4750 x86-64 laptop with a builtin rt2500 with all the 10.3 updates as of this AM 27Sept2007. Thanks for thinking on this issue. -- 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 39

[Bug 243785] New: no WPA connection possible
by bugzilla_noreply＠novell.com 17 Nov '08

17 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=243785 Summary: no WPA connection possible Product: openSUSE 10.3 Version: Alpha 0plus Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dominique.leuenberger(a)tmf-group.com QAContact: qa(a)suse.de NIC: ipw2200 driver WPA encrypted WLAN, PSK ESSID: hidden I can not connect to the network when using Network Manager. I can connect perfectly to it when using the following commands: wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant.conf -B iwconfig eth0 essid <ssid> dhclient eth0 /etc/wpa_supplicant contains only the lines: network={ ssid=<ssid> psk=<PSK in encrypted form> } I consider this feature a higly required one. It's a show stopper if it can not be used in such an environment. Also a configuration via Yast (traditional, without NM) does not work for a connection. -- 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 9