June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 609449] New: yast2 ca-mgm module have mangled capasswd option
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

http://bugzilla.novell.com/show_bug.cgi?id=609449 http://bugzilla.novell.com/show_bug.cgi?id=609449#c0 Summary: yast2 ca-mgm module have mangled capasswd option Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tthidney(a)seznam.cz QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4) KHTML/4.4.2 (like Gecko) SUSE I am trying to create certificate from cmdline using yast ca-mgm module. As I need to pass CA password I tried one from documentation: capasswd [string] CA password (Security: This should be given by an environment variable) however using capasswd="password" is ignored, obviously caPassword option is readed. So Window asking me to pass ca password appear (which is problem in batch) And of course passing caPasswd will fail: Unknown option for command 'createCertificate': caPasswd And at the end when I do not pass capasswd at all command complain about ca creation: Invalid password. Use of uninitialized value in sprintf at /usr/share/YaST2/modules/YaST/caUtils.pm line 1848 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl will try to tell you the name of the variable (if any) that was undefined. In some cases it cannot do this, so it also tells you what operation you used the undefined value in. Note, however, that perl optimizes your program and the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. Invalid value '' for parameter 'caPasswd'. Invalid value '' for parameter 'caPasswd'. Command look like: LANG=us yast2 ca_mgm createCertificate caname="CANAME" type="server" days="3" cn="testauto" keyPasswd="test" email="mymail" verbose 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 9

[Bug 827236] New: xdm init script stop command broken
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=827236 https://bugzilla.novell.com/show_bug.cgi?id=827236#c0 Summary: xdm init script stop command broken Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: lnussel(a)suse.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- the xdm init script has a problem in the "stop" route. It passes an empty DISPLAYMANAGER_BIN to killproc which leads to an error message and of course xdm not getting killed. -- 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 825150] New: Latest nfs-kernel-server update umounts /dev, /proc
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=825150 https://bugzilla.novell.com/show_bug.cgi?id=825150#c0 Summary: Latest nfs-kernel-server update umounts /dev, /proc Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de CC: nfbrown(a)suse.com, fcrozat(a)suse.com Found By: Beta-Customer Blocker: No 20:50 ares07:../Factory/icu # zypper up Loading repository data... Reading installed packages... The following packages are going to be upgraded: MPlayer libXext-devel libXext6 libXfixes-devel libXfixes3 libXrender-devel libXrender1 libXt-devel libXt6 libXv-devel libXv1 libxcb-composite0 libxcb-damage0 libxcb-devel libxcb-dpms0 libxcb-dri2-0 libxcb-glx0 libxcb-randr0 libxcb-record0 libxcb-render0 libxcb-res0 libxcb-screensaver0 libxcb-shape0 libxcb-shm0 libxcb-sync0 libxcb-xevie0 libxcb-xf86dri0 libxcb-xfixes0 libxcb-xinerama0 libxcb-xprint0 libxcb-xtest0 libxcb-xv0 libxcb-xvmc0 libxcb1 nfs-client nfs-kernel-server subversion subversion-perl ... (33/40) Installing: libxcb-dpms0-1.9-2.4.1 ...............................[done] (34/40) Installing: libxcb-damage0-1.9-2.4.1 .............................[done] (35/40) Installing: libxcb-composite0-1.9-2.4.1 ..........................[done] (36/40) Installing: nfs-kernel-server-1.2.7-2.6.1 ........................[done] Additional rpm output: redirecting to systemctl try-restart nfsserver Job for nfsserver.service failed. See 'systemctl status nfsserver.service' and 'journalctl -n' for details. (37/40) Installing: subversion-perl-1.7.10-2.8.1 .........................[done] Additional rpm output: warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? warning: Failed to read auxiliary vector, /proc not mounted? 21:00 ares07:/ # command mount -t proc proc /proc mount: wrong fs type, bad option, bad superblock on proc, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so 21:00 ares07:/ # dmesg | tail [2357722.754225] nfsd: last server has exited, flushing export cache [2357727.571685] warning: process `radvd' used the deprecated sysctl system call with 3.12.16.-2.1. I have no idea what ate /dev and made it impossible to mount /proc, but it smells like systemd's use of shared subtrees might play a role. -- 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 19

[Bug 804894] New: Disabling firewall in yast does not survive reboot
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=804894 https://bugzilla.novell.com/show_bug.cgi?id=804894#c0 Summary: Disabling firewall in yast does not survive reboot Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: roger(a)opq.se QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 If I both disable and stop the firewall in Yast, it still starts again after the system reboots. Bug 779455 addressed something related to this for 12.2, but there is something going on in 12.3 RC1 Reproducible: Always Steps to Reproduce: 1. Stop and Disable the firewall in Yast 2. Reboot 3. Actual Results: The firewall is started Expected Results: The firewall, having been disabled, should not be started. Stopping the firewall in Yast works. It just does not survive a reboot. Before the reboot, but after I have disabled the firewall, looking in yast again shows the correct/expected settings. They just don't happen after the reboot. -- 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 10

[Bug 811188] New: adding cups to allowed services in the firewall does not allow broadcasting
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=811188 https://bugzilla.novell.com/show_bug.cgi?id=811188#c0 Summary: adding cups to allowed services in the firewall does not allow broadcasting Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)suse.com ReportedBy: dpbasti(a)wp.pl QAContact: jsmeix(a)suse.com CC: lnussel(a)suse.com, ctrippe(a)opensuse.org Depends on: 498429 Found By: Customer Blocker: No The bug is still present, i have to disable firewall completely to have network printers from my LAN listen on my opensuse. i have tcp and udp blocking exception for port 631,9001, 160:162 , 9100 still nothing helps +++ This bug was initially created as a clone of Bug #498429 +++ User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.2 (like Gecko) SUSE I wanted to have my network in an external zone, but allow network printing via cups. So I enabled the cups service in the firewall module of yast, but still no remote printers were listed in the printer module of yast, although several are available in my network. I have to manually add '631' in the field for the external zone in the broadcast section of the firewall module or to modify to receive the printers via cups. Reproducible: Always Actual Results: No remote printers found after enabling the cups service in the firewall module. Expected Results: Remote printers are shown after enabling cups service in the firewall. -- 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 825263] New: YaST function type matching misconsiders the argument types
by bugzilla_noreply＠novell.com 04 Jul '13

04 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=825263 https://bugzilla.novell.com/show_bug.cgi?id=825263#c0 Summary: YaST function type matching misconsiders the argument types Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: jreidinger(a)suse.com ReportedBy: mvidner(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- >From a proposed changelog to the fix (https://github.com/yast/yast-core/commit/7fb894662dba29389bc553ee3ffdbac9b6… ) Fixed function type matching to be contravariant for arguments (return type has always been covariant, correctly). Interface expected to handle "any" argument will no longer accept implementations handling only a specific subtype. Conversely, interfaces expected to handle a "string" will also accept an implementation handling "any". Affects the "is" builtin; breaks *-bindings relying on the bug! TODO: fill in the actual symptoms and occurrences of the bug. -- 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 2

[Bug 788945] New: crowbar.pot have a strange string
by bugzilla_noreply＠novell.com 03 Jul '13

03 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=788945 https://bugzilla.novell.com/show_bug.cgi?id=788945#c0 Summary: crowbar.pot have a strange string Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)suse.com ReportedBy: guillaume.gardet(a)opensuse.org QAContact: ke(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 crowbar.pot (and all PO files) have a strange string: "Some range addresses are is not part of network '%1'." It does not look like well written English. Have a look on the file here: http://svn.opensuse.org/viewvc/opensuse-i18n/trunk/yast/50-pot/crowbar.pot?… Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 795246] New: vgaswitheroo does not really turn off NVD9 on linux 3.7
by bugzilla_noreply＠novell.com 03 Jul '13

03 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=795246 https://bugzilla.novell.com/show_bug.cgi?id=795246#c0 Summary: vgaswitheroo does not really turn off NVD9 on linux 3.7 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: srid(a)rkmail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.11 My laptop has an ugly optimus configuration with nvidia geforce 520M (aka nvd9) I usually switch useless nvidia card to save battery like this: echo OFF > /sys/kernel/debug/vgaswitheroo/switch But it looks that the trick does not work with linux 3.7. When the nvidia card is turned on, average power consumption is about 20W (according to powertop) But if I turn off the nvidia card, power consumption would drop to 7-8W. Or at least it used to be so on older kernels. After I turn off nvidia on 3.7, its state in /sys/kernel/debug/vgaswitheroo/switch becomes 'off', nit the computer is still hot and consumes much power. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 825162] New: projectM-data Package - Error in standard configuration File causes projectM not to start
by bugzilla_noreply＠novell.com 03 Jul '13

03 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=825162 https://bugzilla.novell.com/show_bug.cgi?id=825162#c0 Summary: projectM-data Package - Error in standard configuration File causes projectM not to start Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cherenz(a)aip.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 The projectM-data that is shipped with openSUSE contains an error in /usr/share/projectM/config.inp Instead of Title Font = /usr/share/fonts/truetype/DejaVuSans.ttf Title Font = /usr/share/fonts/truetype/DejaVuSansMono.ttf the last two lines shoule read: Title Font = /usr/share/fonts/truetype/DejaVuSans.ttf Menu Font = /usr/share/fonts/truetype/DejaVuSansMono.ttf This error would not allow projectM to start, if it is used as a configuration file. Since this config file is copied at the first start to ~/.projectM/config.inp new users will not be able to run projectM without modifying this line. Reproducible: Always Steps to Reproduce: 1. mv ~/.projectM ~./.projectM-bak (if you have a personal configuration) 2. projectM-pulseaudio Actual Results: projectM-pulseaudio does not start Expected Results: projectM-pulseaudio should start for users without an existing configuration file. Link to the repository in OBS: https://build.opensuse.org/package/show?project=openSUSE%3A12.3&package=pro… -- 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 826326] New: X.org does not start in Virtualbox with 13.1 M2
by bugzilla_noreply＠novell.com 03 Jul '13

03 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=826326 https://bugzilla.novell.com/show_bug.cgi?id=826326#c0 Summary: X.org does not start in Virtualbox with 13.1 M2 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: norbert.jurkeit(a)web.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Beta-Customer Blocker: --- Created an attachment (id=545252) --> (http://bugzilla.novell.com/attachment.cgi?id=545252) X server log file when running in openSUSE 13.1 M2 runs fine on my real hardware, but within Virtualbox the X server does not start, although systemd states that target Multi-User System has been reached. The included log file Xorg.0.log shows several errors. -- 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