June 2008 - openSUSE Bugs - openSUSE Mailing Lists

[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 403642] New: Kicker crashes sometimes when using the search function of suse menu
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=403642 Summary: Kicker crashes sometimes when using the search function of suse menu Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: F.Grannemann(a)02n.net QAContact: qa(a)suse.de Found By: --- Sometimes Kicker crashes when iam using the search function of the suse menu. It also crashes sometimes when i log out or shutdown the system. -- 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 391800] New: Plasma doesn't realize that screen resolution has changed
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=391800 Summary: Plasma doesn't realize that screen resolution has changed Product: openSUSE 11.0 Version: Beta 3 Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: friesoft(a)gmail.com QAContact: qa(a)suse.de Found By: --- When changing the screen resolution with nvidia-settings (in my case from 1280x1024 to 1680x1050) the screen resizes correctly but plasma doesn't realize it should resize too. It just stays the same size.. the panel resizes and moves to the bottom correctly but the desktop itself (wallpaper, clickable desktop area, icons) just stays the old size. Steps to reproduce: open nvidia-settings change your screen resolution click apply and you'll see the effects After a restart of the X-Server everything is fine again. -- 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 389769] New: KDE4 Kickoff CD eject does not work
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=389769 Summary: KDE4 Kickoff CD eject does not work 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: badshah400(a)gmail.com QAContact: qa(a)suse.de Found By: --- >From the KDE4 Kickoff/Computer menu right clicking on the inserted CD device and selecting eject does not do anything. One expects that this should eject the CD in the CD drive (selecting eject on the CD from the places sidebar in dolphin upon right click does eject the cd). Also the new device notifier in panel has no eject icon on pop-up menu (understandably a feature for KDE 4.1), so there is no way to eject devices from desktop in KDE4. -- 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 389715] New: KDE4: konsole does not create utmp entries
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=389715 Summary: KDE4: konsole does not create utmp entries Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: kukuk(a)novell.com QAContact: qa(a)suse.de Found By: --- konsole of KDE4 does not create utmp entries. As result, getlogin()/getlogin_r() functions don't work. How to test: Start konsole. Run "tty" and look, which tty is used. Run "who", the tty reported by "tty" is not in the list. -- 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 387441] New: virt-manager can't create routed guests
by bugzilla_noreply＠novell.com 17 Mar '09

17 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=387441 Summary: virt-manager can't create routed guests Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa(a)suse.de Found By: --- I need to use "routing" network mode for guests instead of "bridged" mode. So I changed the xend config to use vif-route scripts. But when I try to create/install a guest I can't get a network connection. The XML of the guest contains: <interface type='bridge' model='para'> <mac address='00:16:3e:2e:57:c9'/> <script path='/etc/xen/scripts/vif-bridge'/> </interface> and I can't define an IP address in virt-manager's network interface configuration while I understood from Xen documentation that vif-route needs an IP address specified in the vif configuration to set up the routing to the guest. -- 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 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