August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 906379] New: autofs - "Local domain name not set" during booting
by bugzilla_noreply＠novell.com 01 May '17

01 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906379 Bug ID: 906379 Summary: autofs - "Local domain name not set" during booting Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: renda.krell(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.65 Safari/537.36 Build Identifier: I use autofs for mounting some NFS and CIFS shares. In OpenSUSE 13.1 I haven't seen any error with the same configuration. In OpenSUSE 13.2 incl. Tumbleweed/Factory, 'systemctl status' returns: --- autofs.service - Automounts filesystems on demand Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled) Active: active (running) since Thu 2014-11-20 08:54:52 CET; 1h 47min ago Docs: man:automount(8) man:autofs(5) Process: 1709 ExecStart=/usr/sbin/automount ${AUTOFS_OPTIONS} -p /var/run/automount.pid (code=exited, status=0/SUCCESS) Main PID: 1712 (automount) CGroup: /system.slice/autofs.service └─1712 /usr/sbin/automount -p /var/run/automount.pid Nov 20 08:54:52 rkrell automount[1712]: lookup_init:139: lookup(yp): map auto.master: Local domain name not set --- In fact, the domain name is not set: rkrell:~ # hostname rkrell rkrell:~ # domainname (none) but the network is set up correctly using NetworkManager and a local LAN connection. Reproducible: Always Steps to Reproduce: 1. Boot the system 2. 3. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 909695] New: segmentation fault after pack & ioctl & unpack
by bugzilla_noreply＠novell.com 28 Apr '17

28 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=909695 Bug ID: 909695 Summary: segmentation fault after pack & ioctl & unpack Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: bkutil(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This snippet (requires sudo due to ioctl call) produces a segmentation fault on the 13.2 ruby [1], affecting current ruby2.0 and ruby2.1 packages. The bug is currently tracked upstream [2], but not yet fixed, however, a patch is known to work as a fix when backported [3]. require 'socket' SIOCETHTOOL = 0x8946 i = ["lo", "\n"].pack("a16p") s = Socket.new(Socket::AF_INET, Socket::SOCK_DGRAM, 0) s.ioctl(SIOCETHTOOL, i) i.unpack("a16p")[1] [1] ruby 2.1.3p242 (2014-09-19 revision 47630) [x86_64-linux-gnu] [2] https://bugs.ruby-lang.org/issues/10568 [3] https://github.com/ruby/ruby/commit/4b146b25333c52ca4503dfc3c4215b583e8e9963 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 926766] New: rpm: BuildArch resets %patches and %sources
by bugzilla_noreply＠novell.com 26 Apr '17

26 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=926766 Bug ID: 926766 Summary: rpm: BuildArch resets %patches and %sources Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mls(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- %patches and %sources are lua scripts that should print the patches and sources. That works fine as long as Source and Patch lines are before BuildArch. Anything that comes after BuildArch is ignored. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 695322] New: home:dannori: Bug
by bugzilla_noreply＠novell.com 23 Apr '17

23 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=695322 https://bugzilla.novell.com/show_bug.cgi?id=695322#c0 Summary: home:dannori: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dannoritzer(a)web.de ReportedBy: melchiaros(a)aol.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: No Hi, I try to install ghdl from your repo. Yast shows me that ghdl-grt needs libada >= 3.1. A look at my system shows that I´ve installed libada46 from devel:/gcc. So all what ghdl need should be there?! Please make a correction when it is necessary. Greetings -- 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 903989] New: lynis permissions needs small changes.
by bugzilla_noreply＠novell.com 19 Apr '17

19 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903989 Bug ID: 903989 Summary: lynis permissions needs small changes. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: roeland(a)linux-it.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed lynis-1.6.2-1.2.noarch to assess the syate of my 13.2 setup. It appears that the rpm content does not have correct permissions on some files. if I exec the first time: taplop:~ # lynis -h [!] Change file permissions of /usr/share/lynis/include/consts to 640. Command: chmod 640 /usr/share/lynis/include/consts [!] Change file permissions of /usr/share/lynis/include/functions to 640. Command: chmod 640 /usr/share/lynis/include/functions [X] Security check failed: See action above to correct this issue. Please change ownership and permissions of the related files and start Lynis again. taplop:~ # chmod 640 /usr/share/lynis/include/consts taplop:~ # chmod 640 /usr/share/lynis/include/functions taplop:~ # lynis -h Fatal error: permissions of file /usr/share/lynis/include/parameters are not strict enough. Access to 'other' should be denied or read-only. taplop:~ # ls -l /usr/share/lynis/include/parameters -rwxr-xr-x 1 root root 5187 Oct 6 17:43 /usr/share/lynis/include/parameters taplop:~ # chmod o-x /usr/share/lynis/include/parameters taplop:~ # ls -l /usr/share/lynis/include/parameters -rwxr-xr-- 1 root root 5187 Oct 6 17:43 /usr/share/lynis/include/parameters after this correction it works: taplop:~ # lynis -h [ Lynis 1.6.2 ] ################################################################################ Lynis comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the terms of the GNU General Public License. See the LICENSE file for details about using this software. Copyright 2007-2014 - Michael Boelen, http://cisofy.com Enterprise support and plugins available via CISOfy - http://cisofy.com ################################################################################ [+] Initializing program ------------------------------------ Scan options: --auditor "<name>" : Auditor name --check-all (-c) : Check system --no-log : Don't create a log file --pentest : Non-privileged scan (useful for pentest) --profile <profile> : Scan the system with the given profile file --quick (-Q) : Quick mode, don't wait for user input --tests "<tests>" : Run only tests defined by <tests> --tests-category "<category>" : Run only tests defined by <category> Layout options: --no-colors : Don't use colors in output --quiet (-q) : No output, except warnings --reverse-colors : Optimize color display for light backgrounds Misc options: --check-update : Check for updates --debug : Debug logging to screen --view-manpage (--man) : View man page --version (-V) : Display version number and quit Enterprise options: --plugin-dir "<path"> : Define path of available plugins --upload : Upload data to central node See man page and documentation for all available options. Exiting.. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 914698] New: Regression - plymoth no longer prompts for password for encrypted partition
by bugzilla_noreply＠novell.com 19 Apr '17

19 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=914698 Bug ID: 914698 Summary: Regression - plymoth no longer prompts for password for encrypted partition Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: robert.munteanu(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- (Initially posted at https://forums.opensuse.org/showthread.php/504578-Booting-from-encrypted-pa… ) Running 13.2 x86_64 with all updates applied, nvidia proprietary driver. I have disk encryption set up with the YAST parititioner ( I assume LUKS is used ). After updating to kernel 3.16.7 I noticed that I could not boot with it - never got asked to enter my passphrase. So I stuck to using 3.16.6 and after some other updates not even 3.16.6 would work. Sorry for being fuzzy, I don't remember exactly when it happened. The workaround I found was to remove the 'splash=slient quiet' options from the linux line in grub and got the the point where the passphrase was asked for. However, the prompt was different than the one I used to get. The old one was green text and centered in the screen, the current one has the same colour as the text and for each character I input the previous line gets echoed with an additional '*' character appended. I have tried the following to change the plymouth theme # plymouth-set-default-theme text # grub2-mkconfig -o /boot/grub2/grub.cfg However, I get the same behaviour as before. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 884398] New: libvirt-created iptables rules lost on DHCP lease renewal
by bugzilla_noreply＠novell.com 17 Apr '17

17 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=884398 https://bugzilla.novell.com/show_bug.cgi?id=884398#c0 Summary: libvirt-created iptables rules lost on DHCP lease renewal Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: lnussel(a)suse.com ReportedBy: vuntz(a)suse.com QAContact: qa-bugs(a)suse.de CC: mt(a)suse.com Found By: --- Blocker: --- libvirt is adding some rules to the firewall for the networks configured for the VMs (to allow some NAT). However, when using dhcpcd (ie, default network configuration on a workstation), every time the lease is renewed, /etc/sysconfig/network/if-up.d/SuSEfirewall2 is run and is resetting the firewall rules to what is configured, which doesn't include the libvirt rules. That means that the libvirt rules are lost every now and then. A similar issue was debugged in bug 573246 and the fix was http://bugzillafiles.novell.org/attachment.cgi?id=378796. Is this fix acceptable for SuSEfirewall too? -- 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 935164] New: dracut 037-17.12.1 fails to create initrd
by bugzilla_noreply＠novell.com 16 Apr '17

16 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=935164 Bug ID: 935164 Summary: dracut 037-17.12.1 fails to create initrd Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: piny(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build Identifier: patch openSUSE-2015-427 installs dracut 037-17.12.1 patch installation produces error message as Output of dracut-037-17.12.1.x86_64.rpm %posttrans script > see attachment <<dracut-037-17.12.1_initrd_log>> 037-17.9.1 Reproducible: Always Steps to Reproduce: 1.upgrade dracut to dracut-037-17.12.1 2.mkinitrd 3. error message acc. <<dracut-037-17.12.1_initrd_log>> Actual Results: system renders probably unbootable (did not dare to reboot) therefore selected severity level "critical" Expected Results: error free mkinitrd-output downgrade to dracut-037-17.9.1 allows for error free mkinitrd (see <<dracut-037-17.9.1_initrd_log>>) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 858703] New: "Invalid arguments for the Label widget" in yast2 firewall module
by bugzilla_noreply＠novell.com 13 Apr '17

13 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=858703 https://bugzilla.novell.com/show_bug.cgi?id=858703#c0 Summary: "Invalid arguments for the Label widget" in yast2 firewall module Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: aspiers(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- [first reported in bug 851769 comment #13] With yast2-firewall-3.0.1-2.1.4.noarch, if I launch "yast2 firewall", click "Interfaces", select "crowbar-br0" which is an openvswitch bridge I configured for use as a GRE tunnel, and click Change then I get an error dialog: UI Syntax Error Invalid arguments for the Label widget Check the log file! And y2log contains: 2014-01-13 13:21:02 <3> indian.linksys.moosehall(30549) [Ruby] modules/NetworkInterfaces.rb:1468 No such device: crowbar-br0 2014-01-13 13:21:02 <1> indian.linksys.moosehall(30549) [Ruby] yast/ops.rb:62 Index 0 is out of array size 2014-01-13 13:21:09 <1> indian.linksys.moosehall(30549) [Ruby] yast/ops.rb:62 Index 0 is out of array size 2014-01-13 13:21:09 <3> indian.linksys.moosehall(30549) [libycp] firewall/uifunctions.rb:303 Invalid arguments for the Label widget: `Label (nil) 2014-01-13 13:21:09 <2> indian.linksys.moosehall(30549) [ui] YCPDialogParser.cc(parseLabel):1213 THROW: Invalid arguments for the Label widget 2014-01-13 13:21:09 <2> indian.linksys.moosehall(30549) [ui] YCP_UI.cc(OpenDialog):585 CAUGHT: Invalid arguments for the Label widget 2014-01-13 13:21:09 <3> indian.linksys.moosehall(30549) [libycp] firewall/uifunctions.rb:303 UI::OpenDialog() failed 2014-01-13 13:21:09 <1> indian.linksys.moosehall(30549) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Close" at 0x7f53583df860 from function key F10 A valid workaround appears to be to manually edit FW_DEV_EXT in /etc/sysconfig/SuSEfirewall2. -- 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 841046] New: SuSEfirewall2: support IPv6 in FW_TRUSTED_NETS
by bugzilla_noreply＠novell.com 13 Apr '17

13 Apr '17

https://bugzilla.novell.com/show_bug.cgi?id=841046 https://bugzilla.novell.com/show_bug.cgi?id=841046#c0 Summary: SuSEfirewall2: support IPv6 in FW_TRUSTED_NETS Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: lnussel(a)suse.com ReportedBy: ro(a)suse.com QAContact: qa-bugs(a)suse.de CC: mt(a)suse.com Found By: Development Blocker: --- little patch for ipv6 support: mirrorbrain:/sbin # diff -u SuSEfirewall2 SuSEfirewall2.rudi --- SuSEfirewall2 2013-09-18 12:15:17.000000000 +0200 +++ SuSEfirewall2.rudi 2013-09-18 12:15:10.000000000 +0200 @@ -1482,6 +1482,12 @@ net="$1" proto="$2" port="$3" + iptables="$IPTABLES $IP6TABLES" + case "$net" in + *:*) iptables="$IP6TABLES" ;; + [0-9]*.*.*.*) iptables="$IPTABLES" ;; + esac + if [ -n "$4" ]; then error "Too many arguments in FW_TRUSTED_NETS -> $nets" elif [ -z "$net" ]; then @@ -1491,9 +1497,9 @@ elif check_proto_port "$proto" "$port" "" 'FW_TRUSTED_NETS'; then for chain in $input_zones; do # trusted networks can be on any interface ... chain=input_$chain - $LAC $IPTABLES -A $chain ${LOG}"-`rulelog $chain`-ACC-TRUST " -m state --state NEW -s $net $proto $port - $LAA $IPTABLES -A $chain ${LOG}"-`rulelog $chain`-ACC-TRUST " -s $net $proto $port - $IPTABLES -A $chain -j "$ACCEPT" -m state --state NEW,ESTABLISHED,RELATED -s $net $proto $port + $LAC $iptables -A $chain ${LOG}"-`rulelog $chain`-ACC-TRUST " -m state --state NEW -s $net $proto $port + $LAA $iptables -A $chain ${LOG}"-`rulelog $chain`-ACC-TRUST " -s $net $proto $port + $iptables -A $chain -j "$ACCEPT" -m state --state NEW,ESTABLISHED,RELATED -s $net $proto $port done fi done -- 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