January 2007 - openSUSE Bugs - openSUSE Mailing Lists

[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 236712] New: /etc/bindresvprt.blacklist is incorrectly processed and effectively ignored
by bugzilla_noreply＠novell.com 04 Dec '08

04 Dec '08

https://bugzilla.novell.com/show_bug.cgi?id=236712 Summary: /etc/bindresvprt.blacklist is incorrectly processed and effectively ignored Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: brian(a)theharrises.plus.com QAContact: qa(a)suse.de The blacklist as supplied is effectively ignored due to the presence of a tab between the port number and associated comment. In my case, this resulted in cups not being able to function as its port 631 was stolen. The rogue line of code is in glibc-2.4/sunrpc/bindrsvprt.c, line 91: if (*tmp != '\0' || (port == ULONG_MAX && errno == ERANGE)) tmp is pointing to the first character after the port number. With the supplied blacklist, this is a tab character, resulting in the line being rejected. As far as I can see, this line serves no useful purpose and is an overkill for validation, and It should be removed. The circumvention is to delete the tabs after the port numbers in /etc/bindresvprt.blacklist. -- 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 3

[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 232446] New: Graphics problems with SUSE menu style on secondary screen
by bugzilla_noreply＠novell.com 22 Nov '08

22 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=232446 Summary: Graphics problems with SUSE menu style on secondary screen Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: jhansonxi(a)yahoo.com QAContact: qa(a)suse.de On the secondary screen of a multihead/multiscreen SUSE 10.2 setup (non-Xinerama) using KDE, the K Menu SUSE-style graphic is missing and there is also graphic problems with the search panel at the top. The KDE style menu does not have the problem. See screenshots. -- 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 14

[Bug 235050] New: digikam calls dcraw with unknown -2 option
by bugzilla_noreply＠novell.com 22 Nov '08

22 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=235050 Summary: digikam calls dcraw with unknown -2 option Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: meissner(a)novell.com QAContact: qa(a)suse.de CC: jjaeger(a)novell.com The 10.2 digikam and dcraw do not match. (i only get black view and "option -2 not known" on the console.) The 10.1 dcraw works with 10.2 digikam (has the -2 option). -- 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 17

[Bug 233625] New: kicker crashes on rotated display on startup
by bugzilla_noreply＠novell.com 22 Nov '08

22 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=233625 Summary: kicker crashes on rotated display on startup Product: openSUSE 10.2 Version: RC 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: dmueller(a)novell.com QAContact: qa(a)suse.de kicker crashes on rotated display on startup (reminder bugreport) -- 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 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