openSUSE Bugs December 2006

bugs@lists.opensuse.org

1 participants
3533 discussions

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

04 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 230698] New: user space programs fail compiling when including <asm/bitops.h>
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=230698 Summary: user space programs fail compiling when including <asm/bitops.h> Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: SuSE Other Status: NEW Severity: Blocker Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: rnissl(a)gmx.de QAContact: qa(a)suse.de See the following excerpt of /usr/include/asm/bitops.h: static inline int fls(int x) { int r; __asm__("bsrl %1,%0\n\t" "jnz 1f\n\t" "movl $-1,%0\n" "1:" : "=r" (r) : "rm" (x)); return r+1; } #include <asm-generic/bitops/hweight.h> #endif /* __KERNEL__ */ #include <asm-generic/bitops/fls64.h> #ifdef __KERNEL__ #include <asm-generic/bitops/ext2-non-atomic.h> The file fls64.h gets included always and relies on a method fls() which is only defined in the case __KERNEL__. I'd suggest removing the #endif and #ifdef line of the above excerpt. -- 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 227403] New: Can't get rid of resapplet
by bugzilla_noreply＠novell.com 29 Nov '08

29 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=227403 Summary: Can't get rid of resapplet Product: openSUSE 10.2 Version: RC 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jmichael(a)novell.com QAContact: qa(a)suse.de No matter how many times I select "Remove from Panel" for resapplet and save my gnome session, it comes back every time I have to relogin. -- 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 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 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 226161] New: Cleaning up ftp.suse.com
by bugzilla_noreply＠novell.com 12 Nov '08

12 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=226161 Summary: Cleaning up ftp.suse.com Product: openSUSE.org Version: unspecified Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Action Items AssignedTo: draht(a)novell.com ReportedBy: rschiele(a)gmail.com QAContact: adrian(a)novell.com Now that 9.2 is out of support it might be the right time to do some cleanup on ftp.suse.com again to gain some space for 10.2. In my opinion the following directories are obsolete: out of support: /pub/suse/i386/9.2 /pub/suse/i386/update/9.2 /pub/suse/i386/live-cd-9.2 /pub/suse/x86_64/live-cd-9.2 really out of support: /pub/suse/i386/live-cd-9.1 /pub/suse/i386/live-eval-9.0 /pub/suse/x86_64/supplementary/9.0-PatchCD /pub/suse/i386/supplementary/9.1 /pub/suse/x86_64/supplementary/9.1 now in the build service (Why should we confuse people by keeping an out-of-date version on ftp.suse.com?): /pub/suse/i386/supplementary/GNOME /pub/suse/x86_64/supplementary/GNOME /pub/suse/i386/supplementary/X/Xorg -- 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

← Newer
1
2
3
4
5
6
7
8
...
354
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs December 2006