March 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 214311] New: Package "sapinit" sets shared memory too low
by bugzilla_noreply＠novell.com 22 Jan '09

22 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=214311 Summary: Package "sapinit" sets shared memory too low Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SLES 10 Status: NEW Severity: Normal Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de The /etc/sysctl.conf.sap file (of package "sapinit") includes a shared memory setting kernel.shmall of about 5GB. As about 90% of SAP R/3's memory is located within shared memory segments, this setting prevents to use 8 GB or larger shared memory configurations. dev_disp of SAP says: Warning: tmpfs at /dev/shm is configured quite small with 3584 MB! Minimum value is 8192 MB. Recommended size is 75 % of RAM + swap -- 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 284339] New: Can't digitally sign OpenOffice documents on x86_64
by bugzilla_noreply＠novell.com 21 Jan '09

21 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=284339 Summary: Can't digitally sign OpenOffice documents on x86_64 Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OpenOffice.org AssignedTo: eward(a)novell.com ReportedBy: sbrys(a)novell.com QAContact: qa(a)suse.de Environment: - openSUSE Alpha5 on x86_64 platform Steps to duplicate: - open Firefox and go to Edit > Preferences > View Certificates - click Import and import the pfx file attached -- the password is "novell". You'll also need to enter an NSS password of your choice. - click Ok and Close - open a terminal window - type the following command: export MOZILLA_CERTIFICATE_FOLDER="/home/sbrys/.mozilla/firefox/1chxc07l.default" (replace with the path to your firefox profile) - still in the terminal window, run oowriter - in oowriter, create a document and save it - click File > Digital Signatures > Add - enter the NSS password you entered previously when you imported the pfx file - view the certificate -- everything should be valid - select the certificate and click Ok - result: nothing is added to the signatures list Notes: - I tested the procedure above on an openSUSE 10.3 Alpha4 on i386 and there it works fine. - The same problem exists when using the Belgian electronic identity card (eID) - I tested mail signing (Evolution and Thunderbird) and web site authentication (Firefox) using eID and that works fine. So it looks like the NSS part is working properly. -- 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 360344] New: xorg.conf overwritten by security updates
by bugzilla_noreply＠novell.com 21 Jan '09

21 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=360344 Summary: xorg.conf overwritten by security updates Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: SaX2 AssignedTo: ms(a)novell.com ReportedBy: com.opensuse(a)bucksch.org QAContact: qa(a)suse.de Found By: Customer Reproduction: 1. Install opensuse 10.3 2. Modify your xorg.conf, e.g. to use nvidia driver on a 2 monitor setup 3. <3 months pass> 4. Install security updates 5. Restart your machine Actual results: Glibberish on monitor 1 Reason: Something, probably a SaX update, has re-generated xorg.conf, dropping all your changes. You restart, try to re-install driver, check physical setup, until you realize that the "nv" driver is being used. Luckily, the proper xorg.conf is saved as xorg.conf.saxsave, but you lost quite some time on the investigation. Expected result: xorg.conf is left alone for security and reliability updates, only generated when it does not exist or upon explicit user (admin) confirmation. Workaround: Delete the comment at the header which says the stupid "Do not edit this file" (I have to!), and hope that SaX recognizes that the comment and leaves the file alone. This cannot be relied upon, though, that the user/admin knows that deleting a comment makes any difference (and in fact I am just hoping so). Also, the nvidia installer does not do that, IIRC. -- 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 25

[Bug 327454] New: Acer 4320: brightness special keys are not recognized
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=327454 Summary: Acer 4320: brightness special keys are not recognized Product: openSUSE 10.3 Version: RC 1 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- ( Is this a wish or a bug? -- I am not sure. ) It is typical for laptops that fn+arrow increase or decrease the brightness of the screen. In opensuse 10.3 it does not work, those keys are simply ignored (in console, while booting, they produces sequences like [[^M ) but when KDE starts, no reaction. For comparison I tested also Gparted-live and Slax Popcorn -- those keys work as expected. And what is odd here (in opensuse 10.3), that other special keys like volume up, standby, monitor switch work! And while I am talking about hardware -- many thanks for improved hardware detection, 10.3 is much better than 10.2. Thank you very much! -- 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 348987] New: kqemu module not loaded by default
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=348987 Summary: kqemu module not loaded by default Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: initialZero(a)gmail.com QAContact: qa(a)suse.de Found By: --- When one installs qemu amd kqemu. The kqemu module is not loaded by default. Can a group kqemu be created and the module loaded when kqemu is installed? Here are the warnings given by default. If modprobe kqemu is used the latter warning is not given. Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory -- 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 9

[Bug 357290] New: 'yast2 bootloader' module rewrites grub generic code when leaving with no changes, which may corrupt grub
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=357290 Summary: 'yast2 bootloader' module rewrites grub generic code when leaving with no changes, which may corrupt grub Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: root(a)proximasociale.cz QAContact: jsrain(a)novell.com Found By: --- i needed to reinstall my 'fallen into heresy' windows and then i'd needed to restore grub bootloader. I tried at first stance opensuse 10.3 install dvd, because i'd read somewhere, that it supports bootloader restoration. so, I'd found relevant section (install-methods->other->expert-tools->bootloader-restoration ..), but there i faced to some error, nothing was written to disk. I rebooted then into knopix live cd and :: mkdir /mnt/boot mount /dev/sda2 /mnt/boot ## i have separated boot partition grub-install --root-directory=/mnt /dev/sda ## 'chroot' is not neccessary << i'd rewrited generic grub code into mbr, using suse settings (original by yast created menu.lst is then used).. Everything was ok, but one thing changed. I lost default suse "boot-theme" and it was replaced with 'old-style' grub design. I'd launched 'yast2 bootloader' for check, how it things about my restored grub and if i could there rewrite grub again, which will result into 'original distributed suse grub' .. i found there, that this is the same module as on install dvd, so i'd leaved with no changes this module via 'finish' button. It rewrites then grub, which resulted into corrupted bootloader and restoring it with knoppix again.. solution:: order grub to do not rewrite bootloader code, if no changes are made. Best Regards ps. if u need logs, i forgot command for storing that (y2logs or something similar), so remind me 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.

1 12

[Bug 308068] New: Kickoff using Application Menu...
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=308068 Summary: Kickoff using Application Menu... Product: openSUSE 10.3 Version: Beta 2 Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: lunitik(a)gmail.com QAContact: qa(a)suse.de Found By: --- I find that using a mouse button on the desktop to bring up the Menu in that location is very useful... this doesn't happen using Kickoff however... KControl > Behavior > "Mouse Button Actions"... I usually set middle button for "Application menu"... I believe that this option should pull up the old Kmenu preferably, and give users that enjoy that feature the choice of using either, it's just a simpler interface... then we can use Kickoff when we browse down to the Panel... Either way, Kickoff should not open above it's location in the panel when I middle click at the opposite side of the screen, it is very inconvenient! It would be greatly appreciated if this could be fixed, thank you :) -- 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 3

[Bug 371657] New: attempt to access beyond end of device when using dmraid
by bugzilla_noreply＠novell.com 20 Jan '09

20 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=371657 Summary: attempt to access beyond end of device when using dmraid Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: deanjo(a)sasktel.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=202477) --> (https://bugzilla.novell.com/attachment.cgi?id=202477) boot.msg log OK this issue seems to be tied to dmraid. If a software raid 0 is set up on these drives, everything functions as it should. When using dmraid though you get spammed with hundreds of lines like this during boot. Oddly enough they seem to be tied to my larger drives Seagates 7200.11 500 Gig Sata 2 drives. I also have 2 Maxtor 250 Gig drives running dmraid on the same controller (sda and sdb) and they do not have the same issue. It looks like that it can't figure out the drive geometry for the Seagate raids. I'm posting my boot.msg as an attachment Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535936, limit=976773168 Mar 17 00:19:22 my kernel: printk: 30 messages suppressed. Mar 17 00:19:22 my kernel: Buffer I/O error on device sde1, logical block 1953535872 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535937, limit=976773168 Mar 17 00:19:22 my kernel: Buffer I/O error on device sde1, logical block 1953535873 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535938, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535939, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535940, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535941, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535942, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535943, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535936, limit=976773168 Mar 17 00:19:22 my kernel: attempt to access beyond end of device Mar 17 00:19:22 my kernel: sde: rw=0, want=1953535937, limit=976773168 -- 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 56

[Bug 281147] New: We should increase fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=281147 Summary: We should increase fs.inotify.max_user_watches to 65536 in /etc/sysctl.conf Product: openSUSE 10.3 Version: Alpha 4plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joeshaw(a)novell.com QAContact: qa(a)suse.de A common problem for users with large home directories is that Beagle tends to use up all of the inotify watches as it monitors file changes for indexing. We should set fs.inotify.max_user_watches in /etc/sysctl.conf to a pretty high value like 65536 -- the default is 8192 -- to help alleviate this problem for many users. Kernel memory is allocated as the watches are taken, so for those who would not use additional watches, there is no adverse effect. -- 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 275767] New: Konqueror doesn't always cleanup status bar
by bugzilla_noreply＠novell.com 19 Jan '09

19 Jan '09

https://bugzilla.novell.com/show_bug.cgi?id=275767 Summary: Konqueror doesn't always cleanup status bar Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de (using KDE from the buildservice, kdebase3-3.5.6-64.4, builddate 2007-04-23) I noticed that Konqueror doesn't always clean up the status bar. This happens when you move from a "normal" <a href=...> link to a JavaScript onClick link or a form label. To reproduce, - go to http://www.suse.de/~fs/opensuse/download/index_cols.html - scroll down to section "3. Choose a download method" - hover the word "BitTorrent" (near the option button, left of the "Help" link) -> status bar empty, OK - hover the "Help" link next to "BitTorrent" -> status bar shows the link target, OK - hover the word "BitTorrent" (near the option button, left of the "Help" link) -> status bar still shows the "Help" link target - _not_ OK Expected result: - the status bar should be empty after leaving the "Help" link This is just an optical problem in the status bar, clicking does the right thing. -- 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