October 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 257664] New: Wireless networking with intel wlan broken since latest kernel update
by bugzilla_noreply＠novell.com 20 Mar '09

20 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=257664 Summary: Wireless networking with intel wlan broken since latest kernel update Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)eregion.de QAContact: qa(a)suse.de since the lastest kernel update, wpa-encrypted networking with an intel ipw3945 collapses randomly, with the following in dmesg, and "no carrier" in the status of the interface: TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e TKIP: ICV error detected: STA=00:0f:b5:37:17:4e N/A: Michael MIC verification failed for MSDU from 00:0f:b5:37:17:4e keyidx=0 eth1: MSDU decryption/MIC verification failed (SA=00:0f:b5:37:17:4e keyidx=0) -- 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 34

[Bug 331060] New: updater should show the current version for upgrades, not just the candidate version
by bugzilla_noreply＠novell.com 20 Mar '09

20 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=331060 Summary: updater should show the current version for upgrades, not just the candidate version Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: tgoettlicher(a)novell.com ReportedBy: logixoul(a)gmail.com QAContact: kkaempf(a)novell.com Found By: --- The qt updater applet shows only the candidate version for any given upgrade. It should also show the currently installed version. -- 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 285482] New: 'verify installed package dependencies' functionality in YaST
by bugzilla_noreply＠novell.com 19 Mar '09

19 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=285482 Summary: 'verify installed package dependencies' functionality in YaST Product: openSUSE 10.3 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ke(a)novell.com QAContact: jsrain(a)novell.com CC: gs(a)novell.com, sh(a)novell.com Found By: Documentation Fate 301178. Does not work as annnounced for me. Default installation (with GNOME). rpm -e --nodeps sax2 tcl Start yast -> software management -> Extra -> Verify System => Yast says dependencies are fine. File -> Quit. Surprisingly, YaST installs "sax2". Quit yast, whole procedure again. ... Quit and yast installs tcl. [I did not test with yast-ncurses.] -- 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 14

[Bug 334690] New: libcurl comes with too few certs
by bugzilla_noreply＠novell.com 19 Mar '09

19 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=334690 Summary: libcurl comes with too few certs Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tom.horsley(a)att.net QAContact: qa(a)suse.de Found By: --- The /usr/share/curl/curl-ca-bundle.crt file that ships with openSUSE (rpm curl-ca-bundle-7.16.4-16) has a vastly limited subset of certs compared to firefox (for example). Since zypper uses libcurl for https access, this means that repos accessible only via https are likely not accessible without resorting to fiddling with the certs file. For example, the equivalent file on a fedora 7 box is found at /etc/pki/tls/certs/ca-bundle.crt and is 441017 bytes. The /usr/share/curl/curl-ca-bundle.crt file is only 238102 bytes. Copying the fedora 7 certs to my opensuse box did indeed allow me to access an https repo, but that is way too obscure for most folks to figure out. It seems reasonable to expect all the tools that talk https to have access to the same set of certs when they all come on the same linux distribution. -- 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 13

[Bug 297035] New: kino help opens non-existing html file
by bugzilla_noreply＠novell.com 18 Mar '09

18 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=297035 Summary: kino help opens non-existing html file Product: openSUSE 10.3 Version: Alpha 7 Platform: PowerPC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bk(a)novell.com ReportedBy: olh(a)novell.com QAContact: sndirsch(a)novell.com Found By: --- in german locale, the help -> content menu opens /usr/share/kino/help/en/en.html instead of /usr/share/kino/help/en/index.html french locale may have the same issue. -- 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 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 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 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