April 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 331770] New: MPI-Selector: Make changes sooner effective
by bugzilla_noreply＠novell.com 18 Mar '09

18 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=331770 Summary: MPI-Selector: Make changes sooner effective Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: burnus(a)gmx.de QAContact: qa(a)suse.de CC: ken(a)novell.com Found By: --- Currently, one needs to log out in order that the changes are effective; opening a new xterm window is not enough. It would be great if the changes were effective a) if one opens a new xterm b) directly after one has run mpi-selector. -- 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 6

[Bug 326455] New: MPI-Selector / OpenMPI/MPICH etc: Set default when installing
by bugzilla_noreply＠novell.com 18 Mar '09

18 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=326455 Summary: MPI-Selector / OpenMPI/MPICH etc: Set default when installing Product: openSUSE 10.3 Version: Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: burnus(a)gmx.de QAContact: qa(a)suse.de Found By: --- Currently, if one installs OpenMPI, it is not in the path. The reason is that mpi-selector is used, which allows multiple MPI installations. Expected: (a) When an MPI-Package is installed, the post installation script checks whether already an MPI packages is registered (mpi-selector --query); if not, it registers itself. (b) If an MPI package is uninstalled, it removes itself; it would be great that then automatically the next MPI package (if enabled) would be selected. While one can argue about (b), I think (a) makes always sense - especially since on most systems there will be only one installed MPI. -- 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 4

[Bug 335046] New: kicker crashes randomly
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=335046 Summary: kicker crashes randomly Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: davidcanar(a)gmail.com QAContact: qa(a)suse.de Found By: Beta-Customer Kicker crashes randomly 3 - 5 times / week when I use the search functionality that comes with the new KDE SUSE Menu (beagle). My system is a laptop AMD 64bits dual core, 2 GB RAM, XGL, fglrx video driver. This is the backtrace I get when it crashes: System configuration startup check disabled. [?1034h(no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b08aef873e0 (LWP 3853)] [New Thread 0x41001950 (LWP 4128)] [New Thread 0x40800950 (LWP 4020)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00002b08a9f3bccb in read () from /lib64/libpthread.so.0 #0 0x00002b08a9f3bccb in read () from /lib64/libpthread.so.0 #1 0x00002b08ab0a3d1f in ?? () from /opt/kde3/lib64/libDCOP.so.4 #2 0x00002b08ab09da8b in _kde_IceRead () from /opt/kde3/lib64/libDCOP.so.4 #3 0x00002b08ab0a21f1 in KDE_IceProcessMessages () from /opt/kde3/lib64/libDCOP.so.4 #4 0x00002b08ab08ff6e in DCOPClient::callInternal () from /opt/kde3/lib64/libDCOP.so.4 #5 0x00002b08ab090248 in DCOPClient::callInternal () from /opt/kde3/lib64/libDCOP.so.4 #6 0x00002b08ab0946dd in DCOPClient::call () from /opt/kde3/lib64/libDCOP.so.4 #7 0x00002b08ab094713 in DCOPClient::call () from /opt/kde3/lib64/libDCOP.so.4 #8 0x00002b08ab0948d9 in DCOPClient::disconnectDCOPSignal () from /opt/kde3/lib64/libDCOP.so.4 #9 0x00002b08ab095181 in DCOPObject::~DCOPObject () from /opt/kde3/lib64/libDCOP.so.4 #10 0x00002b08a8ce92bb in KBookmarkManager::~KBookmarkManager () from /opt/kde3/lib64/libkio.so.4 #11 0x00002b08a9ab0a11 in QGList::clear () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00002b08a8d03d77 in QPtrList<KBookmarkManager>::~QPtrList () from /opt/kde3/lib64/libkio.so.4 #13 0x00002b08a8ce66e9 in ?? () from /opt/kde3/lib64/libkio.so.4 #14 0x00002b08aa7bc6f5 in __cxa_finalize () from /lib64/libc.so.6 #15 0x00002b08a8bc1b83 in ?? () from /opt/kde3/lib64/libkio.so.4 #16 0x00007fff024b85d0 in ?? () #17 0x00002b08a8d8ebb1 in _fini () from /opt/kde3/lib64/libkio.so.4 #18 0x0000000000000000 in ?? () Please let me know if you need more information from me. 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 9

[Bug 367669] New: opening czech man pages in konqueror use wrong codepage
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=367669 Summary: opening czech man pages in konqueror use wrong codepage Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: tcech(a)novell.com QAContact: qa(a)suse.de Found By: --- Opening "man:/usr/share/man/cs/man1/ssh.1.gz" use UTF-8 copepage by default for document, which is encoded in iso8859-2. It's probably because UTF-8 is default for all web pages. -- 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 6

[Bug 334206] New: Yast NTP configuration doesn't handle refclocks correctly
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=334206 Summary: Yast NTP configuration doesn't handle refclocks correctly Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin.burnicki(a)meinberg.de QAContact: jsrain(a)novell.com Found By: --- I've tried to configure a parse refclock using yast2 and found 2 points where yast doesn't work correctly. 1.) If I select "Generic Reference driver" then there is an "Options" field where I can add additional parameters. A correct configuration for the parse driver requires a "mode" parameter which specifies the type of refclock to use, e.g. "mode 2" has to be added to let the parse driver expect the Meinberg standard time string. Obviously the text entered in the "Options" field is appended to the server line, so if I enter "mode 2" here the result in ntp.conf is correct: server 127.127.8.0 mode 2 However, there is also a line generated in ntp.conf which can be used to set up additional configuration options for that device: fudge 127.127.8.0 This line is empty, though, i.e. it does not contain any parameters. Commonly uses parameters here would be the refid, a constant time bias, the trust time, .., so the line could look like this: fudge 127.127.8.0 time1 0.0 refid GPSi So there should be an additional field in the yast dialog where you could enter those fudge commands for that device, and the descriptive text should tell where the parameters of each field would be added in ntp.conf. 2.) If I mark the checkbox labelled "create symlink" and enter the device name to which the link should be created, this might work if I finish yast. However, if I run yast the next time the checkbox is not marked anymore and the device name for the symlink is grayed out. A quick look into /etc/sysconfig/ntp shows that the existing parameters are still NTP_PARSE_LINK="" NTP_PARSE_DEVICE="" so they are obviously not updated correctly when yast saves the configuration. By the way, the NTP package should finally be renamed from xntp-* to ntp-*. xntp is outdated for many years now, and if users refer to that package e.g. in the NTP newsgroup comp.protocols.time.ntp they are everytime told their package was outdated and they should upgrade, hust because it is still called xntp-* while it contains ntpd etc. rather than the old xntpd. AFAIK this should be handled fine by RPM which could have an entry saying the ntp-* package obsoletes the xntp-* package. Martin -- 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 7

[Bug 354392] New: software managment: use mirrors on the fly
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=354392 Summary: software managment: use mirrors on the fly Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- Recent hardware failure showed fragile points of yast without any doubt. Please, change the way the list of repos are organized. When user adds repo A, and yast gets the info from this repo, also mirror list should be downloaded. So when something happens to repo A, yast will be able to switch to its mirror on fly. -- 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 382344] New: default to /usr/local/lib64 for self-compiled stuff
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=382344 Summary: default to /usr/local/lib64 for self-compiled stuff Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de CC: coolo(a)novell.com, schwab(a)novell.com Blocks: 369696 Found By: --- It would be nice, if autoconf based configure script will default to libdir=/usr/local/lib64 for self compiles stuff (i. e. ./configure ; make ; make install). It would prevent bi-arch clashes in packages supporting /usr/local. It's trivial to do it: Add /usr/local/share/config.site with following contents: ---- #! /bin/sh if test "$libdir" = '${exec_prefix}/lib' ; then libdir='${exec_prefix}/lib64' fi ---- It is possible to enhance it and skip the change, if it was called inside "linux32" command. -- 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 6

[Bug 332186] New: network optimized upgrade of the system
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=332186 Summary: network optimized upgrade of the system Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- >From today experience of upgrading 10.2 to 10.3 from KDE CD I can only say it is too fragile to try it again. Too much time is wasted for displaying (when user is not looking at computer) network errors. Not mentioning it could be total network failure and then what user is supposed to do. Conclusions: user cannot work, a lot of time wasted, bad experience. It seems that only downloading full DVD would solve such problems. But not entirely. But what about such approach. One small CD installer as a kickstart disc -- user downloads it, and burns it. One install manager _program_ -- user downloads it and runs it. This IM would run in current system, user would select what kind of upgrade she/he wants, what packages to add extra, etc etc. Note that at this point system is fully running (something you cannot get with current installer) -- video card, network cards, etc. User clicks ok and downloading begins -- upgrade packages, updates, release notes, firmware, drivers, etc. NOW -- this is crucial. It is just another program in the system downloading stuff. User can still view www pages, write document in OOffice, simply put -- she/he can work! After downloading is finished, user burn DVD/CD(s) of downloaded software. And finally then she/he reboots, inserts kickstart disc, normal installer runs, but all packages are now copied from the burned disc! So there is no weak point in whole upgrade. What do you think? A bit elaborate process, but risk-free, and for upgrade (note, this not for INSTALL!) it could work like a charm. Very fast and safely. -- 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 8

[Bug 384170] New: Translating AppAmor is a pain
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=384170 Summary: Translating AppAmor is a pain Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: michael(a)michael-skiba.de QAContact: ke(a)novell.com Found By: Localization Translating AppAmor really is a pain, extremly long texts, unsorted lists in block text form, etc. it scared all our translators.. Couldn't it be made more comfortable? The biggest pain is MID:144: <ul><li> Allow configuration of the secure attention key</li> <li> Allow administration of the random device</li> <li> Allow examination and configuration of disk quotas</li> <li> Allow configuring the kernel's syslog (printk behaviour)</li> <li> Allow setting the domain name</li> <li> Allow setting the hostname</li> <li> Allow calling bdflush()</li> <li> Allow mount() and umount(), setting up new smb connection</li> <li> Allow some autofs root ioctls</li> <li> Allow nfsservctl</li> <li> Allow VM86_REQUEST_IRQ</li> <li> Allow to read/write pci config on alpha</li> <li> Allow irix_prctl on mips (setstacksize)</li> <li> Allow flushing all cache on m68k (sys_cacheflush)</li> <li> Allow removing semaphores</li> <li> Used instead of CAP_CHOWN to \"chown\" IPC message queues, semaphores and shared memory</li> <li> Allow locking/unlocking of shared memory segment</li> <li> Allow turning swap on/off</li> <li> Allow forged pids on socket credentials passing</li> <li> Allow setting read ahead and flushing buffers on block devices</li> <li> Allow setting geometry in floppy driver</li> <li> Allow turning DMA on/off in xd driver</li> <li> Allow administration of md devices (mostly the above, but some extra ioctls)</li> <li> Allow tuning the ide driver</li> <li> Allow access to the nvram device</li> <li> Allow administration of apm_bios, serial and bttv (TV) device</li> <li> Allow manufacturer commands in isdn CAPI support driver</li> <li> Allow reading non-standardized portions of pci configuration space</li> <li> Allow DDI debug ioctl on sbpcd driver</li> <li> Allow setting up serial ports</li> <li> Allow sending raw qic-117 commands</li> <li> Allow enabling/disabling tagged queuing on SCSI controllers and sending arbitrary SCSI commands</li> <li> Allow setting encryption key on loopback filesystem </li></ul> couldn't that be displayed as <li>foo</li> <li>bar</li> <li>and</li> <li>so</li> <li>on</li> Would be far easier to read (and as long as it doesn't have a special new-line tag it shouldn't change anything in the result for the end user). Also some very long texts could be splittet in several smaller texts, it's exhausting to even find the change, it would increase translation quality and translation efficency. -- 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 5

[Bug 381665] New: Cannot read EXT2 formatted floppy
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=381665 Summary: Cannot read EXT2 formatted floppy Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mario_bz(a)mgtech.com QAContact: qa(a)suse.de Found By: --- Just tried beta1 which now displays a floppy icon on the system screen. However, when I put an ext/ext2 formatted floppy into the drive and click the message below appears. When I try a standard DOS floppy it works fine. I use ext2 for my grub boot and it does work fine so there is no problem with the ext2 floppies. I also tried adding: /dev/fd0 /media/floppy auto noauto,user,sync 0 0 which I found in 10.3 fstab but not in 11.0, it prevented the message below but then other errors (missing /media/floppy) occurred and not data displayed. mount: wrong fs type, bad option, bad superblock on /dev/fd0, missing codepage on helper program or other error, error in some useful info found in syslog - try dmesg | tail. mario@linux:~> dmesg | tail sd 8:0:0:0: [sdc] Mode Sense: 11 00 00 00 sd 8:0:0:0: [sdc] Cache data unavailable sd 8:0:0:0: [sdc] Assuming drive cache: write through sdc: [mac] sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8 sd 8:0:0:0: [sdc] Attached SCSI disk sd 8:0:0:0: Attached scsi generic sg3 type 0 XFS mounting filesystem sdc7 Ending clean XFS mount for filesystem: sdc7 hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. hfs: write access to a jounaled filesystem is not supported, use the force option at your own risk, mounting read-only. mario@linux:~> -- 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 18