April 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 589994] New: gpg incurs problem at encryption, returns error code 2, breaks scripts
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589994 http://bugzilla.novell.com/show_bug.cgi?id=589994#c0 Summary: gpg incurs problem at encryption, returns error code 2, breaks scripts Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alext(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Just noticed on my updated 11.2 system. Probably introduced with a recent update to either gpg or gpg-agent. When symmetrically encrypting a file, gpg outputs the string "gpg: problem with the agent: Not implemented" and returns error code 2 after completion. The file does get successfully encrypted; however, since gpg returns error code 2, any scripts that use gpg will assume that the gpg failed (since the return code was not zero) and fail themselves. Transcript follows: [zuul:~]$ echo "hello there" > tstfile [zuul:~]$ cat tstfile | gpg --sign --symmetric > tstfile.gpg You need a passphrase to unlock the secret key for user: "Alex Tsariounov <XXX(a)XXX.XXX.net>" 1024-bit DSA key, ID EC21BF7F, created 2003-06-30 gpg: 3DES encryption will be used gpg: problem with the agent: Not implemented [zuul:~]$ echo $? 2 [zuul:~]$ cat tstfile.gpg | gpg gpg: 3DES encrypted data gpg: encrypted with 1 passphrase hello there gpg: Signature made Sat 20 Mar 2010 11:24:16 AM MDT using DSA key ID EC21BF7F gpg: Good signature from "Alex Tsariounov <XXX(a)XXX.XXX.net>" gpg: WARNING: message was not integrity protected [zuul:~]$ -- Configure bugmail: http://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 589541] New: nfs client not working
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589541 http://bugzilla.novell.com/show_bug.cgi?id=589541#c0 Summary: nfs client not working Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: till.eberlein(a)kabelbw.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 the nfs client in version 2.19.1-1.1 is not working. when pressing the "ok" button nothing happens, only the "abbrechen" button is working, but then no shares are saved. this happens with yast in gnome and text-based yast. the older available client version 2.18.0-2.2 is working properly. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 589433] New: Install grub into root (/) partition gives error
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589433 http://bugzilla.novell.com/show_bug.cgi?id=589433#c0 Summary: Install grub into root (/) partition gives error Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fisiu82(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=349250) --> (http://bugzilla.novell.com/attachment.cgi?id=349250) YaST2 screen from installation of grub User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 During install 11.3 M3 from KDE LiveCD on spare partition, installation of grub gave me an error. By default setup wanted to install grub into mbr (finally it works!) but I have fully working system on first partition with grub in mbr. So I decided to install grub into a root of new system (M3). Then I got this error. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 589431] New: preload kmp has broken supplements
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589431 http://bugzilla.novell.com/show_bug.cgi?id=589431#c0 Summary: preload kmp has broken supplements Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: coolo(a)novell.com ReportedBy: mls(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- $ rpm -q --supplements preload-kmp-desktop kernel-desktop packageand(kernel-desktop:preload) packageand(kernel-desktop:preload) Please remove "kernel-desktop". And one of "packageand(kernel-desktop:preload)" is enough. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 589293] New: DMZ Cursor theme needs to be removed from desktop-data-openSUSE
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589293 http://bugzilla.novell.com/show_bug.cgi?id=589293#c0 Summary: DMZ Cursor theme needs to be removed from desktop-data-openSUSE Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: awafaa(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 Currently desktop-data-openSUSE contains the DMZ Cursor theme. As part of the Moblin submissions to Factory I submitted icon-them-dmz-cursors. There was talk about splitting it out in the past, but no real push. Any chance this can be done now? Reproducible: Always -- Configure bugmail: http://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 589021] New: Better protect java stack
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=589021 http://bugzilla.novell.com/show_bug.cgi?id=589021#c0 Summary: Better protect java stack Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: pmladek(a)novell.com QAContact: qa(a)suse.de CC: mmeeks(a)novell.com Found By: Development Blocker: --- Could you please backport the fix from http://cr.openjdk.java.net/~aph/6929067-jdk7-webrev-4/ into our openJDK package? It should better protect the java stack and help with debugging problems, for example the bug #578802. -- Configure bugmail: http://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 588998] New: yast2-schema: no element "printer" in profile.rng
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588998 http://bugzilla.novell.com/show_bug.cgi?id=588998#c0 Summary: yast2-schema: no element "printer" in profile.rng Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de CC: mzugec(a)novell.com Found By: Development Blocker: --- I run as root "yast2 --gtk autoyast" and therein I do -> tools -> create reference profile (check only printer) -> create and then -> tools -> check validity of profile I get an error poput with the folowing xmllint error (I added only here \ to wrap the too long lines) -------------------------------------------------------------- /usr/bin/xmllint --noout --relaxng \ /usr/share/YaST2/schema/autoyast/rng/profile.rng \ /tmp/YaST2-15945-JC4X8S/printer.xml /tmp/YaST2-15945-JC4X8S/printer.xml:4: element printer: \ Relax-NG validity error : \ Element profile has extra content: printer /tmp/YaST2-15945-JC4X8S/printer.xml fails to validate -------------------------------------------------------------- I think xmllint is right because there is no element printer in /usr/share/YaST2/schema/autoyast/rng/profile.rng Adding -------------------------------------------------------- <optional> <ref name="printer"/> </optional> -------------------------------------------------------- to /usr/share/YaST2/schema/autoyast/rng/profile.rng does not help and I get another xmllint error: ------------------------------------------------------------------- /usr/bin/xmllint --noout --relaxng \ /usr/share/YaST2/schema/autoyast/rng/profile.rng \ /tmp/YaST2-15945-JC4X8S/printer.xml /usr/share/YaST2/schema/autoyast/rng/profile.rng:80: \ element ref: Relax-NG parser error : \ Reference printer has no matching definition Relax-NG schema /usr/share/YaST2/schema/autoyast/rng/profile.rng \ failed to compile ------------------------------------------------------------------- When this issue is fixed for openSUSE 11.3 please have in mind that the AutoYaST printer client in yast2-printer will change a lot for openSUSE 11.3, see bug #588679. -- Configure bugmail: http://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 588770] New: Installer complains that the "custom bootloader isn't available anymore".
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588770 http://bugzilla.novell.com/show_bug.cgi?id=588770#c0 Summary: Installer complains that the "custom bootloader isn't available anymore". Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: chobbs(a)siloamsprings.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/5.0.307.7 Safari/532.9 I'm installing Milestone 3 under VirtualBox. When the installer makes it to the Installation Settings screen, I opened the Booting screen, then Bootloader Options and changed the boot time from 8 seconds to 3. After saving the option, when the installer returns to the Installation Settings screen, a dialog pops up that reads "Custom bootloader isn't available anymore. Would you like to proceed with the default bootloader." I have not yet tried to reproduce this on actual hardware, so it may be a vbox thing. Reproducible: Always Steps to Reproduce: 1. Run the installer. 2. Change the boot time from 8 to 3 seconds in GRUB's options 3. Save the changes. Actual Results: A custom bootloader dialog pops up explaining that the custom bootloader is no longer available. Expected Results: The installer should return to the Installation Settings screen without error. -- Configure bugmail: http://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 588679] New: yast2-printer: AutoYaST client destroys information in cupsd.conf
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588679 http://bugzilla.novell.com/show_bug.cgi?id=588679#c0 Summary: yast2-printer: AutoYaST client destroys information in cupsd.conf Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEEDINFO Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: jsmeix(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de CC: ug(a)novell.com, mzugec(a)novell.com Found By: Development Blocker: --- When AutoYaST calls the "Write" function in printer_auto.ycp it results - a /etc/cups/cupsd.conf without any comments and without any indentation but with a strange unexpected re-ordering of the entries and - a /etc/cups/client.conf without any comments which is totally empty if there was no active entry in the /etc/cups/client.conf of the system wherefrom the AutoYaST control file was created. Because the comments provide useful and sometimes even very important information for the admin, the yast2-printer AutoYaST client destroys information. Because the ordering in /etc/cups/cupsd.conf in the cloned system is the well known upstream ordering, an unexpected strange re-ordering makes it very hard to understand the /etc/cups/cupsd.conf file afterwards. Therefore the bug severity is "major". Details: When AutoYaST calls the "Write" function in printer_auto.ycp it calls Printerlib::WriteClientSettings and Printerlib::WriteCupsSettings which call SCR::Write(.cups.client, ay) and SCR::Write(.cups.server, ay) where ay is a map as follows: ------------------------------------------------------------------------ $["cups_remote_server": $[], "server_settings": $["BrowseAllow":["all"], "BrowseOrder":["allow,deny"], "Browsing":["On"], "DefaultAuthType":["Basic"], "DefaultPolicy":["default"], "Listen":["localhost:631", "/var/run/cups/cups.sock"], "LogLevel":["info"], "SystemGroup":["sys root"], .. ------------------------------------------------------------------------ and the /etc/cups/cupsd.conf file is as follows: ------------------------------------------------------------------------ Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow none BrowseDeny all DefaultPolicy default DefaultAuthType Basic SystemGroup sys root .. LogLevel info ------------------------------------------------------------------------ I assume because a YCP map does not keep any ordering but the actual sequence of its entries is random, one gets also a random re-ordered cupds.conf file written. Uwe, for openSUSE 11.3 I will clean it up, compare https://bugzilla.novell.com/show_bug.cgi?id=582680#c35 Which YCP structure works for AutoYaST so that config files are written 100% identical on the target system? I.e. on one same system "Read"->"Export"->"Import"->"Write" must result 100% identical (i.e. unchanged) config files. I would prefer to have both cupsd.conf and client.conf as XML CDATA in the AutoYaST control file. Which YCP data must the "Export" function in printer_auto.ycp provide to AutoYaST so that the result are two XML CDATA sections, one for cupsd.conf and one for client.conf? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 20

[Bug 588325] New: AUDIT-0: lockdev
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=588325 http://bugzilla.novell.com/show_bug.cgi?id=588325#c0 Summary: AUDIT-0: lockdev Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: security-team(a)suse.de ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- lockdev is used to create lock files in /var/lock on behalf of users. To avoid having /var/lock world writeable the /usr/sbin/lockdev helper is setgid 'lock' and /var/lock writable only by group 'lock'. The lockdev package is currently staged for Factory in Base:System. Upstream git repo is here: git://git.debian.org/git/lockdev/lockdev -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4