September 2006 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 208505] New: gscmxx not working
by bugzilla_noreply＠novell.com 25 Jun '08

25 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=208505 Summary: gscmxx not working Product: openSUSE 10.2 Version: Alpha 4 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: felix(a)derklecks.de QAContact: qa(a)suse.de I just tried to run gscmxx but it does not work. It gives: felix@vaio-gr214mp:~> gscmxx Can't locate Gtk.pm in @INC (@INC contains: /usr/lib/perl5/5.8.8/i586-linux-thread-multi /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl . /usr/bin/../SCMxx /usr//lib/perl5/site_perl/5.8.8 /usr//lib/perl5/vendor_perl/5.8.8) at /usr/bin/gscmxx line 196. BEGIN failed--compilation aborted at /usr/bin/gscmxx line 196. For it seems like there is just a gtk2 package for perl and not a gtk1 one. So is gscmxx not working at all? -- 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 10

[Bug 207599] New: rug should provide a command --make-debug-log
by bugzilla_noreply＠novell.com 25 Jun '08

25 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=207599 Summary: rug should provide a command --make-debug-log Product: openSUSE 10.2 Version: Alpha 4 plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Zenworks AssignedTo: flucifredi(a)novell.com ReportedBy: mauro(a)novell.com QAContact: mauro(a)novell.com CC: jtariq(a)novell.com, aj(a)novell.com PROBLEM STATEMENT Anytime the user or testers need to report a bug with zypp/zmd, will be asked for the logs. Would be nice to have just one command to provide them, ready and in the format the developers really need. Something like: rug --make-debug-log my-debug-log.tgz should work just fine; or maybe something like: rug --make-debug-log will create a file like debug-$DATE-machineID.tgz -- 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 206969] New: Ignore button does not work, it cancels the the whole installation
by bugzilla_noreply＠novell.com 25 Jun '08

25 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=206969 Summary: Ignore button does not work, it cancels the the whole installation Product: openSUSE 10.2 Version: Alpha 4 Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: felix(a)derklecks.de QAContact: jsrain(a)novell.com I tried to install alpha4. The first CD was defect and therefore a package failed the integrity check. I got the message you see in the attached screenshot. (sorry but it is in german) It says: Could not find package in installation source .. [Cancel] - [Repeat] - [Ignore] Now pressing the Ignore button quits the whole installation and you have to start over again. It should just skip this one package! btw. "Could not find package in installation source" is misleading shouldn't it be something like "Package broken on media"? -- 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 206965] New: Shows Pattern Uninstalled if All Packages Are Installed
by bugzilla_noreply＠novell.com 25 Jun '08

25 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=206965 Summary: Shows Pattern Uninstalled if All Packages Are Installed Product: openSUSE 10.2 Version: Alpha 4 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: stbinner(a)suse.de QAContact: jsrain(a)novell.com The software management dialog doesn't show patterns checked/installed even if all its/the sole package contained within are/is installed and shown selected. Examples in a standard KDE installation are the "KDE Help System" and "KDE System" patterns. -- 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 7

[Bug 204742] New: Kickoff improvements / usability / consistency
by bugzilla_noreply＠novell.com 25 Jun '08

25 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=204742 Summary: Kickoff improvements / usability / consistency Product: openSUSE 10.2 Version: Alpha 4 Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: one_way(a)online.de QAContact: qa(a)suse.de I think the new "kickoff" menu is a quite interesting concept. But it takes same time to get used to it. A few points that somehow "don't feel right": 1. Sometimes just moving the mouse pointer over an item opens the next subitem, sometimes you have to click to achieve this. E.g.: Kickoff-menu is opened by just moving the mouse pointer over "Geeko". Instinctively clicking in addition to that often closes the menu again :(. Browsing through "all programs" (classic menu structure) requires the user to explicitely click on every submenu, hovering the pointer achieves nothing. Browsing the tabs at the bottom works with both hovering and clicking. The delay is a bit to slacky, however. 2. More configurability (I guess this is coming in future versions). I'd like e.g. the sequence of the buttoms at the bottom configurably (and the new "Geeko"-icon doesn't fit at all in my desktop look ;). 3. "Leave"-Tab: Somehow this part feels quite awkward, too many mouseclicks are necessary, the requester asking for confirmation does never appear in the same place (center of screen), but always somewhere else. And, IMHO, once you have clicked your (long) way through to the "shutdown" button (or so), you shouldn't need another reconfirmation. 4. Is Beagle really necessary?? -- 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 10

[Bug 208693] New: zen updater crashes on its suggestion to install additional packages
by bugzilla_noreply＠novell.com 20 Jun '08

20 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=208693 Summary: zen updater crashes on its suggestion to install additional packages Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: Elmar_Stellnberger(a)hotmail.com QAContact: qa(a)suse.de 19 Software Updates available System.NullReferenceException: Object reference not set to an instance of an object in <0x00866> Novell.Zenworks.Gui.ResolvableTransactionHelper:Transact () in <0x00039> Novell.Zenworks.Gui.ResolvableTransactionHelper:Run () in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void () zen updater crashes on its suggestion to install additional packages -- 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 4

[Bug 204729] New: opera does not need to be built for x86_64
by bugzilla_noreply＠novell.com 18 Jun '08

18 Jun '08

https://bugzilla.novell.com/show_bug.cgi?id=204729 Summary: opera does not need to be built for x86_64 Product: openSUSE 10.2 Version: Alpha 4 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.hanke(a)gmx-topmail.de QAContact: qa(a)suse.de opera is currently being built for both i586 and x86_64, but the x86_64 package has exactly the same content as the i586 package, i.e. i586 binaries. opera for x86_64 can be dropped for openSUSE 10.2, a package for i586 is sufficient just like it is the case with MozillaFirefox, acroread, RealPlayer and others. Doing so will save ~6MB in inst-source-extra and even more in the update tree because opera is updated often and there are patch RPMs and delta RPMs in addition to the full RPMs. -- 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 207637] New: kernel-debug is symlinked as /boot/vmlinuz when installed
by bugzilla_noreply＠novell.com 23 May '08

23 May '08

https://bugzilla.novell.com/show_bug.cgi?id=207637 Summary: kernel-debug is symlinked as /boot/vmlinuz when installed Product: openSUSE 10.2 Version: Alpha 4 plus Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rschiele(a)gmail.com QAContact: qa(a)suse.de CC: aj(a)novell.com kernel-debug is symlinked as /boot/vmlinuz when installed as all the default kernels. Although it could be argued that this seems to be the logical way doing it I'd like to argue why this kernel should get special handling like the xen kernels: 1. In the current situation not so experienced users might run into serious problems when they install kernel-debug by accident. 2. Even a lot of people installing kernel-debug most likely don't want to have this booted as default kernel. 3. People that really _need_ kernel-debug should be easily capable to boot it even if it is not symlinked as the default kernel. -- 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 2

[Bug 209339] New: KMail signature check problem
by bugzilla_noreply＠novell.com 22 May '08

22 May '08

https://bugzilla.novell.com/show_bug.cgi?id=209339 Summary: KMail signature check problem Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: kde-maintainers(a)suse.de KMail showed me the following error message when checking the signature of a mail with Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; The message in the main window was: Nicht genügend Informationen zur Überprüfung der Signatur vorhanden: [Details] Status: Keine Status-Informationen verfügbar. translated: not enough information to check the signature: [details] status: no status information available Clicking [Details], I see the following message: Fehler - Kleopatra Das Krypto-Modul lässt sich nicht initialisieren. Der Zertifikatsmanager wird jetzt beendet. translated: error - Kleopatra The crypto module can't be initialized. The certificate manager will be terminated now. I see two problems here: a) the failed signature check Unfortunately, I don't know why it happens. What I can tell is that I have seen it some days ago with another mail (dunno if it was the same sender). KMail prints on stdout/stderr: gpgmeplug checkMessageSignature status flags: 0 gpgmeplug checkMessageSignature found email: <lists(a)norrbring.se> gpgmeplug checkMessageSignature found email: <lists(a)norrbring.se> b) despite of the failed signature check, the mail gets a green border like mails with valid (but non-trusted) signatures. I consider this more critical than the failed signature check because it can make people believe the signature is valid. -> I would expect a yellow border because the signature can't be checked. I'm using KDE and KMail from 10.1 + online updates. -- 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 204647] New: Installation locks right after the installation begin in vmware.
by bugzilla_noreply＠novell.com 22 May '08

22 May '08

https://bugzilla.novell.com/show_bug.cgi?id=204647 Summary: Installation locks right after the installation begin in vmware. Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jharmon(a)novell.com QAContact: jsrain(a)novell.com I am using openSUSE 10.2 Alpha 4 and when I try to install it in vmware it will get to the end of the loading kernel section and lock up hard. I have tried the CD's, creating a DVD, as well as a network install and all of them lock up at the same point where is says loading linux kernel and as soon as the dialog disappears it lock hard. I am unable to get the yast files because of the lockup but I was able to switch over the the debug screen and catch the attached screen shot before it locked up. -- 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