November 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 205721] New: getgrgid_r always returns nonsense
by bugzilla_noreply＠novell.com 05 Dec '08

05 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=205721 Summary: getgrgid_r always returns nonsense Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmueller(a)novell.com QAContact: qa(a)suse.de getgrgid_r seems to fail. works on 10.1. -- 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 13

[Bug 213941] New: LSB: ttyname_r() returns an incorrect error value on a bad filedescriptor
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=213941 Summary: LSB: ttyname_r() returns an incorrect error value on a bad filedescriptor Product: openSUSE 10.2 Version: Alpha 5 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdluhos(a)novell.com QAContact: qa(a)suse.de Found by the LSB runtime test: When a ttyname_r() function is called on a filedescriptor that is already closed (and previously referred to a valid terminal device), the ENOTTY error is reported. This is incorrect, the EBADF error should be reported in this case. Please find the attached program that demonstrates this. -- 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 7

[Bug 215668] New: jing - false positive error (attribute "type" from ... not allowed at this point;...)
by bugzilla_noreply＠novell.com 27 Nov '08

27 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=215668 Summary: jing - false positive error (attribute "type" from ... not allowed at this point;...) Product: openSUSE 10.2 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: ke(a)novell.com ReportedBy: locilka(a)novell.com QAContact: qa(a)suse.de CC: mvidner(a)novell.com /usr/bin/jing -c /usr/share/YaST2/schema/autoyast/rnc/inetd-bug.rnc /root/7_auto.xml 2>&1 returns: /root/7_auto.xml:17: error: attribute "type" from namespace "http://www.suse.com/1.0/configns" not allowed at this point; ignored for every: <conf> <enabled config:type="boolean">false</enabled> <iid>1:/etc/xinetd.d/chargen</iid> <protocol>tcp</protocol> <script>chargen</script> <server></server> <service>chargen</service> </conf> (<service /> is the problematic tag - line 17) This could cause errors when validating AutoYaST xml profile -> Major I'll attach rnc and xml file... -- 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 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 205390] New: DHT is still disabled in Ktorrent
by bugzilla_noreply＠novell.com 07 Nov '08

07 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=205390 Summary: DHT is still disabled in Ktorrent Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hugo.costelha(a)gmail.com QAContact: kde-maintainers(a)suse.de Hi, The ktorrent v. >=2.0 packages still have DHT disabled, although it is no longer experimental. This can be found in the SUSE 10.2 or in the packages provided in KDE:/Backports for 10.1/. I think it is safe to remove the patch that disables DHT. -- 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 13

[Bug 214956] New: online update still fails with timeout V 2.13.43.2-0.2
by bugzilla_noreply＠novell.com 04 Nov '08

04 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=214956 Summary: online update still fails with timeout V 2.13.43.2-0.2 Product: SUSE Linux 10.1 Version: Final Platform: i386 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)tpg.com.au QAContact: jsrain(a)novell.com V 2.13.43.2-0.2 of on line update still fails with timeout - see screen shot. Please amend ZMD time out parameter. This may be dupe - Hard to tell with different versions and many fixes have been attempted -- 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 213233] New: On-line Update - fails in resole dependencies and unable to install new updates indicated by ZEN updates
by bugzilla_noreply＠novell.com 04 Nov '08

04 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=213233 Summary: On-line Update - fails in resole dependencies and unable to install new updates indicated by ZEN updates Product: SUSE Linux 10.1 Version: Final Platform: i386 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)tpg.com.au QAContact: jsrain(a)novell.com I Noticed and ZEN online update just released has caused a problem. The recent online distribution in 4 New updates updated YAST2 online update. YAST updates and displayed YAST will close and restart after that process ZMD still indicates the are updates, however there cannot be installed by On-line update. The following message from root indices problems with On-line update version couston@scott:~> su Password: scott:/home/couston # rpm -q libzypp zen-updater libzypp-1.3.2-0.9 zen-updater-7.1.0-51.30 scott:/home/couston # root email indicates Waking up ZMD...Done The following updates are required: Resolving Dependencies... ERROR: Dependency resolution failed: Unresolved dependencies: Updating patch:libzypp-logging-2158-0.noarch[System packages] to patch:libzypp-logging-2158-0.noarch[20061011-181226] Can't install patch:libzypp-logging-2158-0.noarch[20061011-115300], since patch:libzypp-logging-2158-0.noarch[20061011-181226] is already marked as needing to be installed Marking this resolution attempt as invalid. Current display indicates updates are available, however this new version of YAST online update goes black when ZMD indicates updates are required. We have to get On-line update finally fixed be have has the following versions as We need either to roll-back current version of YOU or correct it again. Please do not release v 10.2 until YOU is finally fixed and will not cause errors as without it this functioning correctly we can can fit nothing. This problem may well have been resolved or rolled-back as of today? New On-line Update - fails in resole dependencies and unable to install new updates indicated by ZEN updates -- 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 223408] New: Problem changing NIC during installation
by bugzilla_noreply＠novell.com 23 Oct '08

23 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=223408 Summary: Problem changing NIC during installation Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: holgi(a)novell.com QAContact: jsrain(a)novell.com Two network cards (NIC) environment: If you do configure the 'wrong' NIC during installation and do recognize that when YaST tries to (unseccessfull) enable a connection to the internet - returning to the NIC configuration (with back buttons) deleting the config of the 'wrong' NIC and configuring the 'right' NIC causes a problem: it is not possible to connect to the internet afterwards. I thing YaST do not delete the config or the 'wrong' NIC and still tries to use just that NIC to enable the 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 20

[Bug 218285] New: ALSA-related gnome-panel crash
by bugzilla_noreply＠novell.com 22 Oct '08

22 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=218285 Summary: ALSA-related gnome-panel crash Product: openSUSE 10.2 Version: Beta 1 plus Platform: x86 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: qa(a)suse.de While trying to fix an unrelated sound problem, I found out that the gnome-panel crashes in the following situations: - "/etc/init.d/rcalsasound restart" (this is done by YaST when configuring the soud card) - "alsaconf" Both of these crash my gnome-panel and it's 100% reproducible. No backtrace for now because gdb seems to have a problem with this. -- 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 10