August 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 229500] New: K3bSetup not installed
by bugzilla_noreply＠novell.com 22 Nov '08

22 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=229500 Summary: K3bSetup not installed Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: mludvig(a)logix.net.nz QAContact: qa(a)suse.de When running k3b as a normal user I get: ===== cdrecord will be run without root privileges It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr. Solution: Use K3bSetup to solve this problem. ===== There is however no k3bsetup binary on my system. I have only found a bunch of MO files in /opt/kde3/share/locale/*/LC_MESSAGES/k3bsetup.mo but no corresponding binary. -- 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 11

[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 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 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 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

[Bug 292172] New: USB generic audio stick produces lots of noise
by bugzilla_noreply＠novell.com 16 Nov '08

16 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=292172 Summary: USB generic audio stick produces lots of noise Product: openSUSE 10.3 Version: Alpha 5 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: ktf(a)icer.nl QAContact: qa(a)suse.de Found By: Beta-Customer I've 2 "soundcards", a AC'97 build in and a generic USB audio device. The second one is the problem: it produces sound, but is is quite noisy. The driver works good op openSUSE 10.2, the problem is only present on openSUSE 10.3 (alpha 5) I think it is a driver or a soundlibrary problem (or something other low-level) because it is a problem in all my audio programs. I've tested it on amaroK, realplayer and mplayer. Also, the startup-sound and all other systemsound are noisy. -- 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

[Bug 244138] New: ZyppSearch::setupRegexp(): .*stdc++.* is not a valid regular expression: "Invalid preceding regular expression"
by bugzilla_noreply＠novell.com 15 Nov '08

15 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=244138 Summary: ZyppSearch::setupRegexp(): .*stdc++.* is not a valid regular expression: "Invalid preceding regular expression" Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: kkaempf(a)novell.com ReportedBy: maw(a)novell.com QAContact: kkaempf(a)novell.com mw@quill:~/builds/home:maw/simias/simias-1.2.5347.1> sudo zypper search stdc++ Restoring system sources... ZyppSearch::setupRegexp(): .*stdc++.* is not a valid regular expression: "Invalid preceding regular expression" This is a bug, please file a bug report against zypper. -- 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 5

[Bug 239194] New: cleanup /etc/modprobe.conf
by bugzilla_noreply＠novell.com 14 Nov '08

14 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=239194 Summary: cleanup /etc/modprobe.conf Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de CC: kasievers(a)novell.com It currently contains a load of aliases and options for modules that don't exist any longer. >From Kay's mail: alias 'bcm-new' for unknown module 'bcm' alias 'binfmt-0004' for unknown module 'binfmt_coff' alias 'binfmt-002c' for unknown module 'abi_ibcs' alias 'binfmt-332' for unknown module 'abi_ibcs' alias 'binfmt-518' for unknown module 'abi_ibcs' alias 'block-major-117' for unknown module 'evms' alias 'block-major-15' for unknown module 'cdu31a' alias 'block-major-23' for unknown module 'mcd' alias 'block-major-25' for unknown module 'sbpcd' alias 'block-major-26' for unknown module 'sbpcd' alias 'block-major-27' for unknown module 'sbpcd' alias 'block-major-28' for unknown module 'sbpcd' alias 'block-major-2' for unknown module 'floppy' alias 'block-major-32' for unknown module 'cm206' alias 'char-major-10-170' for unknown module 'thinkpad' alias 'char-major-107' for unknown module '3dfx' alias 'char-major-109' for unknown module 'lvm_mod' alias 'char-major-185' for unknown module 'intermezzo' alias 'char-major-195*' for unknown module 'nvidia' alias 'char-major-212' for unknown module '/bin/true' alias 'char-major-27' for unknown module 'ftape' alias 'char-major-30' for unknown module 'abi_ibcs' alias 'char-major-36' for unknown module 'netlink_dev' alias 'char-major-48' for unknown module 'riscom8' alias 'char-major-49' for unknown module 'riscom8' alias 'char-major-4' for unknown module 'serial' alias 'char-major-5' for unknown module 'serial' alias 'char-major-83' for unknown module 'vtx' alias 'cipcb0' for unknown module 'cipcb' alias 'cipcb1' for unknown module 'cipcb' alias 'InterMezzo' for unknown module 'intermezzo' alias 'iso9660' for unknown module 'isofs' alias 'md-personality-4' for unknown module 'raid5' alias 'net-pf-1' for unknown module 'unix' alias 'pci:v00001385d00003872sv*sd*bc*sc*i*' for unknown module 'prism2_pci' alias 'pcmcia:m000Bc7110f*fn*pfn*pa*pb*pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m0089c0002f*fn*pfn*pa*pb*pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m01FFc0008f*fn*pfn*pa*pb*pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m1668c0101f*fn*pfn*pa*pb*pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:mC001c0008f*fn*pfn*pa*pb*pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa0306467Fpb9762E8F1pcC9049A39pdC23ADC0E*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa0733CC81pb0C52F395pc00000000pd00000000*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa209F40ABpb46263178pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa2DECECE3pb82067C18pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa35DADC74pb01F7FEDBpcC9049A39pdC23ADC0E*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa393089DApbA71E69D5pc90471FA9pd57A66194*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa41240E5BpbAFC7C33Epc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa4AC44287pb235A6BEDpc4B74BAA0pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa4B801A17pbF222EC2Dpc630D52B2pdC23ADC0E*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa71B18589pbF144E3ACpc4B74BAA0pd00000000*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa74C5E40Dpb8304FF77pc4B74BAA0pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa78FC06EEpb45A50C1Epc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa78FC06EEpbDB9AA842pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*pa7E3B326Apb49893E92pc4B74BAA0pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paA37434E9pb9762E8F1pcA57ADB8Cpd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paA5F472C2pb9C05598DpcC9049A39pd57A66194*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paB67A610Epb655AA7B7pc264B451Apd00000000*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paC6536A5Epb3F35797Dpc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paC7B8DF9Dpb1700D087pc4B74BAA0pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paFDD73470pbE0B6F146pc*pd*' for unknown module 'prism2_cs' alias 'pcmcia:m*c*f*fn*pfn*paFEA54C90pb48F2BDD6pc4B74BAA0pd*' for unknown module 'prism2_cs' alias 'personality-13' for unknown module 'abi_solaris' alias 'personality-14' for unknown module 'abi_uw7' alias 'personality-1' for unknown module 'abi_ibcs' alias 'personality-2' for unknown module 'abi_ibcs' alias 'personality-3' for unknown module 'abi_sco' alias 'personality-4' for unknown module 'abi_wyse' alias 'personality-5' for unknown module 'abi_ibcs' alias 'personality-7' for unknown module 'abi_ibcs' alias 'tap0' for unknown module 'ethertap' alias 'tap10' for unknown module 'ethertap' alias 'tap11' for unknown module 'ethertap' alias 'tap12' for unknown module 'ethertap' alias 'tap13' for unknown module 'ethertap' alias 'tap14' for unknown module 'ethertap' alias 'tap15' for unknown module 'ethertap' alias 'tap1' for unknown module 'ethertap' alias 'tap2' for unknown module 'ethertap' alias 'tap3' for unknown module 'ethertap' alias 'tap4' for unknown module 'ethertap' alias 'tap5' for unknown module 'ethertap' alias 'tap6' for unknown module 'ethertap' alias 'tap7' for unknown module 'ethertap' alias 'tap8' for unknown module 'ethertap' alias 'tap9' for unknown module 'ethertap' alias 'tty-ldisc-2' for unknown module 'serio' blacklist 'ad1889' blacklist 'ali5455' blacklist 'aty128fb' blacklist 'clgenfb' blacklist 'cmpci' blacklist 'cs4281' blacklist 'e2220pc' blacklist 'e5520pc' blacklist 'emu10k1' blacklist 'encode_big5' blacklist 'encode_gb' blacklist 'encode_gbk' blacklist 'encode_jis' blacklist 'encode_kscm' blacklist 'es1370' blacklist 'esssolo1' blacklist 'evbug' blacklist 'fbcon_afb' blacklist 'fbcon_cfb2' blacklist 'fbcon_cfb4' blacklist 'fbcon_hga' blacklist 'fbcon_ilbm' blacklist 'fbcon_iplan2p2' blacklist 'fbcon_iplan2p4' blacklist 'fbcon_iplan2p8' blacklist 'fbcon_mac' blacklist 'fbcon_mfb' blacklist 'fbcon_vga' blacklist 'fbcon_vga_planes' blacklist 'fbgen' blacklist 'fcclassic' blacklist 'fcdsl' blacklist 'fcdsl2' blacklist 'fcdslslusb' blacklist 'fcdslslusb2' blacklist 'fcdslusb' blacklist 'fcdslusb2' blacklist 'fcdslusba' blacklist 'fcpci' blacklist 'fcusb' blacklist 'fcusb2' blacklist 'forte' blacklist 'fxusb' blacklist 'fxusb_CZ' blacklist 'hysdn' blacklist 'i2c_matroxfb' blacklist 'ich2rom' blacklist 'intelfbdrv' blacklist 'intelfbhw' blacklist 'maestro' blacklist 'maestro3' blacklist 'matroxfb_maven' blacklist 'matroxfb_proc' blacklist 'nm256_audio' blacklist 'opl3sa2 # Bug 219758' blacklist 'pm3fb' blacklist 'prism2_cs' blacklist 'prism2_pci' blacklist 'rme96xx' blacklist 'slamr' blacklist 'slusb' blacklist 'sonicvibes' blacklist 'tpam' blacklist 'uhci' blacklist 'unikey' blacklist 'vmware' blacklist 'ymfpci' options 'cipe_debug=0' for unknown module 'cipcb' options 'isapnp_reset=0' for unknown module 'isa_pnp' options 'NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660' for unknown module 'nvidia' options 'quiet=1' for unknown module 'vtx' -- 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 63

[Bug 257774] New: Enhancements to Yast's checkmedia
by bugzilla_noreply＠novell.com 13 Nov '08

13 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=257774 Summary: Enhancements to Yast's checkmedia Product: openSUSE 10.3 Version: Alpha 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: n5xwb(a)hal-pc.org QAContact: jsrain(a)novell.com Donn Washburn wrote: As a suggestion, it would be handy to have a "Eject media" button added to "Check Media" in the Yast2 app. Or have checkmedia do it after completion. This system is openSuSE10.3 Alpha0plus and .wodim-1.1.2-4 Second request is to have Yast2 again save to a HD and/or floppy. It saves time when something goes wrong. Besides it might kind of be used like kickstart or jumpstart. (sort of!) -- 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 6

[Bug 295059] New: AutoYaST converts kickstart file wrong and other problems
by bugzilla_noreply＠novell.com 13 Nov '08

13 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=295059 Summary: AutoYaST converts kickstart file wrong and other problems Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: caspert(a)math.aau.dk QAContact: qa(a)suse.de Found By: --- I imported this kickstart file: http://www.math.aau.dk/~caspert/junta/client-caspert.cfg (remark the include/ dir.) The output can be found here: http://www.math.aau.dk/~caspert/junta/imported-kickstart.xml Firstly, it's extremely hard to debug since xmllint produces nonsense error messages: Relax-NG validity error : Element profile has extra content: bootloader As far as I have discovered yet, <gid> cannot be in <profile><groups><group>. Moreover, <... /> is "bad", and <base> cannot (according to http://www.suse.com/~ug/autoyast.pdf) be in <software>. After a tremendous amount of time, I IRC'ed with some #suse (freenode) guys and they told me that I cannot trust xmllint to tell me about errors and that it doesn't b0rk about correct things. I have seen the light myself, and can conclude that I cannot trust the error messages of xmllint (try using the imported-kickstart.xml file and debug it) and that I cannot trust YaST2/AutoYaST to output correct xml files. I don't know if I can trust that kickstart files are imported correctly. Actually I cannot trust anything, so finding errors takes very long time. Now I'm faced with the error "Error while configuring partitions. Try again." The error is found in the perl code, and is produced since AutoinstStorage::Write() fails. As far as I can se, it's definition is found in line 632 in AutoinstStorage.ycp. "y2milestone("solutions: %1", sol);" (line 678) is reached according to y2log which can be found here: http://www.math.aau.dk/~caspert/junta/y2log Tracing the error takes me quite some time, so I'd appreciate if someone can 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.

1 1