February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 842360] New: dhcpd does not listen for dhcp requests
by bugzilla_noreply＠novell.com 16 Jun '16

16 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=842360 https://bugzilla.novell.com/show_bug.cgi?id=842360#c0 Summary: dhcpd does not listen for dhcp requests Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 When running the dhcp server that is included with opensuse 12.3,l it simply "doe not work at all". on closer inspection it turns out that the dhcpd does not listen on port 67... and so it can't serve dhcp requests. Reproducible: Always Steps to Reproduce: 1. start dhcpd 2. run dhcpcd-test from another computer 3. observe it failing w/o getting an answer 4. check with netstat -ulpn|grep dhcp that the dhcp server listens on two random udp ports but *not* on port 67 Actual Results: running a dhcp server with openSUSE 12.3 does not work at all. Expected Results: it "should just work". -- 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 30

[Bug 843734] New: security: Bug
by bugzilla_noreply＠novell.com 13 Jun '16

13 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=843734 https://bugzilla.novell.com/show_bug.cgi?id=843734#c0 Summary: security: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86 OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: lnussel(a)suse.com ReportedBy: lutchy.horace(a)outlook.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: meissner(a)suse.com Found By: --- Blocker: --- In /etc/sysconfig/sshguard, option PORTS separated by comma. Processed in /etc/init.d/sshguard by iptables_start() function. Iptables doesn't accept multiple ports with just '/usr/sbin/iptables -A INPUT -p tcp --dport $PORTS'. It must be specified in the format of '/usr/sbin/iptables -A INPUT -p tcp -m multiport --dport $PORTS' otherwise it will fail with: iptables v1.4.16.3: invalid port/service `22,443' specified Try `iptables -h' or 'iptables --help' for more information. Best Regards -- 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 3

[Bug 786024] New: vsftpd broken - OOPS: priv_sock_get_cmd
by bugzilla_noreply＠novell.com 11 Jun '16

11 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=786024 https://bugzilla.novell.com/show_bug.cgi?id=786024#c0 Summary: vsftpd broken - OOPS: priv_sock_get_cmd Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: mvyskocil(a)suse.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- vsftpd is running, but... # ncftp -u demo localhost NcFTP 3.2.4 (May 16, 2010) by Mike Gleason (http://www.NcFTP.com/contact/) Server hungup immediately after connect. OOPS: priv_sock_get_cmd Workaround: add seccomp_sandbox=NO to vsftpd.conf See also https://bbs.archlinux.org/viewtopic.php?id=147074 - the page says this is fixed in vsftpd 3.0.2, so updating vsftpd to this version should be enough. I did not test if this bug is only in Factory (I'm using factory-tested from 2012-10-03) or also in 12.2. -- 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 75

[Bug 831629] New: python3-base test test_faulthandler fails on ppc64
by bugzilla_noreply＠novell.com 09 Jun '16

09 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c0 Summary: python3-base test test_faulthandler fails on ppc64 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: PowerPC-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dvaleev(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- [ 456s] test_unregister (test.test_faulthandler.FaultHandlerTests) ... test test_faulthandler failed [ 456s] ok [ 456s] [ 456s] ====================================================================== [ 456s] FAIL: test_register_chain (test.test_faulthandler.FaultHandlerTests) [ 456s] ---------------------------------------------------------------------- [ 456s] Traceback (most recent call last): [ 456s] File "/home/abuild/rpmbuild/BUILD/Python-3.3.2/Lib/test/test_faulthandler.py", line 588, in test_register_chain [ 456s] self.check_register(chain=True) [ 456s] File "/home/abuild/rpmbuild/BUILD/Python-3.3.2/Lib/test/test_faulthandler.py", line 572, in check_register [ 456s] self.assertEqual(exitcode, 0) [ 456s] AssertionError: -11 != 0 [ 456s] [ 456s] ---------------------------------------------------------------------- -- 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 837290] New: xl2tpd: kernel oops (system hangs) when start VPN connection
by bugzilla_noreply＠novell.com 08 Jun '16

08 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=837290 https://bugzilla.novell.com/show_bug.cgi?id=837290#c0 Summary: xl2tpd: kernel oops (system hangs) when start VPN connection Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alerom-666(a)yandex.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=554749) --> (http://bugzilla.novell.com/attachment.cgi?id=554749) ctrl+alt+f10 terminal screenshot User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 When I start connection with xl2tpd -D -c /etc/xl2tpd/xl2tpd.conf i've: xl2tpd[18159]: setsockopt recvref[22]: Protocol not available xl2tpd[18159]: Using l2tp kernel support. xl2tpd[18159]: xl2tpd version xl2tpd-1.3.0 started on linux-t9pv PID:18159 xl2tpd[18159]: Written by Mark Spencer, Copyright (C) 1998, Adtran, Inc. xl2tpd[18159]: Forked by Scott Balmos and David Stipp, (C) 2001 xl2tpd[18159]: Inherited by Jeff McAdams, (C) 2002 xl2tpd[18159]: Forked again by Xelerance (www.xelerance.com) (C) 2006 xl2tpd[18159]: Listening on IP address 0.0.0.0, port 1701 xl2tpd[18159]: get_call: allocating new tunnel for host 78.107.1.49, port 1701. xl2tpd[18159]: Connecting to host tp.internet.beeline.ru, port 1701 xl2tpd[18159]: control_finish: message type is (null)(0). Tunnel is 0, call is 0. xl2tpd[18159]: control_finish: sending SCCRQ xl2tpd[18159]: network_thread: recv packet from 78.107.1.49, size = 110, tunnel = 25911, call = 0 ref=0 refhim=0 xl2tpd[18159]: handle_avps: handling avp's for tunnel 25911, call 0 xl2tpd[18159]: message_type_avp: message type 2 (Start-Control-Connection-Reply) xl2tpd[18159]: protocol_version_avp: peer is using version 1, revision 0. xl2tpd[18159]: firmware_rev_avp: peer reports firmware version 4384 (0x1120) xl2tpd[18159]: hostname_avp: peer reports hostname 'bras304' xl2tpd[18159]: vendor_avp: peer reports vendor 'Cisco Systems, Inc.' xl2tpd[18159]: receive_window_size_avp: peer wants RWS of 32000. Will use flow control. xl2tpd[18159]: assigned_tunnel_avp: using peer's tunnel 43115 xl2tpd[18159]: framing_caps_avp: supported peer frames: xl2tpd[18159]: bearer_caps_avp: supported peer bearers: xl2tpd[18159]: control_finish: message type is Start-Control-Connection-Reply(2). Tunnel is 43115, call is 0. xl2tpd[18159]: control_finish: sending SCCCN xl2tpd[18159]: Connection established to 78.107.1.49, 1701. Local: 25911, Remote: 43115 (ref=0/0). xl2tpd[18159]: Calling on tunnel 25911 xl2tpd[18159]: control_finish: message type is (null)(0). Tunnel is 43115, call is 0. xl2tpd[18159]: control_finish: sending ICRQ xl2tpd[18159]: network_thread: recv packet from 78.107.1.49, size = 12, tunnel = 25911, call = 0 ref=0 refhim=0 xl2tpd[18159]: network_thread: recv packet from 78.107.1.49, size = 28, tunnel = 25911, call = 51794 ref=0 refhim=0 xl2tpd[18159]: handle_avps: handling avp's for tunnel 25911, call 51794 xl2tpd[18159]: message_type_avp: message type 11 (Incoming-Call-Reply) xl2tpd[18159]: assigned_call_avp: using peer's call 7161 xl2tpd[18159]: control_finish: message type is Incoming-Call-Reply(11). Tunnel is 43115, call is 7161. xl2tpd[18159]: control_finish: Sending ICCN xl2tpd[18159]: Call established with 78.107.1.49, Local: 51794, Remote: 7161, Serial: 1 (ref=0/0) xl2tpd[18159]: network_thread: recv packet from 78.107.1.49, size = 12, tunnel = 25911, call = 0 ref=0 refhim=0 xl2tpd[18159]: network_thread: select timeout xl2tpd[18159]: network_thread: select timeout xl2tpd[18159]: network_thread: select timeout xl2tpd[18159]: network_thread: select timeout xl2tpd[18159]: network_thread: select timeout xl2tpd[18159]: network_thread: select timeout And at this time - the system hangs. Screenshot is attached. xl2tp developers said that it fixed in kernel https://github.com/xelerance/xl2tpd/issues/28 A latest system updates is installed Reproducible: Always Steps to Reproduce: 1.start xl2tpd 2. 3. Actual Results: System hangs Expected Results: VPN is up and running -- 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 853313] New: GroupWise client crashes, because Java uses too small stack alignment
by bugzilla_noreply＠novell.com 06 Jun '16

06 Jun '16

https://bugzilla.novell.com/show_bug.cgi?id=853313 https://bugzilla.novell.com/show_bug.cgi?id=853313#c0 Summary: GroupWise client crashes, because Java uses too small stack alignment Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: schwab(a)suse.com ReportedBy: vojtech(a)suse.com QAContact: qa-bugs(a)suse.de CC: matz(a)suse.com Found By: Beta-Customer Blocker: No The GroupWise client crashes on openSUSE 13.1 because it uses Java and Java's JIT generates code with too small stack alignment compared to what the (new) 32-bit ABI dictates. Vectorized string operations in glibc depend on the full alignment and the application segfaults. It'd be good for backwards compatibility with (arguably broken) old applications to be able to set an environment variable to use non-vectorized string operations even on modern CPUs. -- 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 11

[Bug 859673] New: WINS name lookup unreliable
by bugzilla_noreply＠novell.com 31 May '16

31 May '16

https://bugzilla.novell.com/show_bug.cgi?id=859673 https://bugzilla.novell.com/show_bug.cgi?id=859673#c0 Summary: WINS name lookup unreliable Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: bart(a)bartvanassche.be QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Since a long time I'm using openSUSE and WINS name lookup for name resolution. This worked fine in every previous openSUSE version I have been running but seems to be unreliable in openSUSE 13.1. Reproducible: Always Steps to Reproduce: 1. Disable the firewall # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination # iptables -L -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination 2. Enable bridging # cat /etc/sysconfig/network/ifcfg-br0 BOOTPROTO='dhcp' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='enp8s0' BRIDGE_STP='on' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' # cat /etc/sysconfig/network/ifcfg-enp8s0 BOOTPROTO='none' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='RTL8111/8168B PCI Express Gigabit Ethernet controller' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='manual' USERCONTROL='no' 3. Install the samba-client RPM # rpm -qf /usr/lib64/libnss_wins.so.2 samba-client-4.1.3-3.12.1.x86_64 4. Enable WINS name lookup # grep wins /etc/nsswitch.conf hosts: files wins mdns_minimal [NOTFOUND=return] dns 5. Test WINS name lookup $ nmblookup ubuntu-vm 192.168.1.124 ubuntu-vm<00> $ host ubuntu-vm Host ubuntu-vm not found: 2(SERVFAIL) $ ping ubuntu-vm ping: unknown host ubuntu-vm Actual Results: Name lookup via WINS not working. Expected Results: Name lookup via WINS working. -- 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 659905] New: Error in GRUB installation & configuration
by bugzilla_noreply＠novell.com 20 May '16

20 May '16

https://bugzilla.novell.com/show_bug.cgi?id=659905 https://bugzilla.novell.com/show_bug.cgi?id=659905#c0 Summary: Error in GRUB installation & configuration Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 4 of 6 Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: lassaad(a)pochta.ru QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-1.2 Firefox/3.6.12 In the Bootloader installation procedure I get an error, so I can't instal GRUB, I've tried many installation option like install on MBR, on sda, on /root but it doesn't work. so I quit installation and when I try to install GRUB manually I get the same error. There are some screenshots of my installation: This is my partitions setup http://yfrog.com/0rdiskpartitionsp My installation setting http://yfrog.com/5einstallationsettingsp GRUB installation ERROR http://yfrog.com/1gerrorgrubp Reproducible: Always Steps to Reproduce: 1.start live USB installation (my CD-ROM is broken) 2.set my "/" on sda5 (ext4) 3.wait until the GRUB error appear in the end of installation Actual Results: when I restart, no GRUB, I get error " no operating system... " and in the /boot directory, there is no vmlinuz or initrd files. only mbr.backup and grub folder. Expected Results: setup the GRUB, and end the installation. -- 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 822774] New: perl-Bootloader doesn't rotate it's log
by bugzilla_noreply＠novell.com 20 May '16

20 May '16

https://bugzilla.novell.com/show_bug.cgi?id=822774 https://bugzilla.novell.com/show_bug.cgi?id=822774#c0 Summary: perl-Bootloader doesn't rotate it's log Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: snwint(a)suse.com ReportedBy: lazy.kent(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- perl-Bootloader doesn't rotate it's log. In my system /var/pbl.log size is 9.8 MB since 2013-01-05. It should provide a pbl file in /etc/logrotate.d/. -- 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 15

[Bug 828693] New: Zarafa-spooler does not work when started by systemd
by bugzilla_noreply＠novell.com 03 May '16

03 May '16

https://bugzilla.novell.com/show_bug.cgi?id=828693 https://bugzilla.novell.com/show_bug.cgi?id=828693#c0 Summary: Zarafa-spooler does not work when started by systemd Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ian.hodge(a)verrinus-consulting.ltd.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=547291) --> (http://bugzilla.novell.com/attachment.cgi?id=547291) Output of strace User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET4.0C; .NET4.0E) When systemd is used to start zarafa-spooler the process starts but does not pickup and deliver any message from zarafa-server. If the spooler is started on the command line it works correctly. If systemd is replaced by sysvinit as the boot mechanism, the spooler also works correctly. This is true on openSUSE 12.1, 12.2 and 12.3 with zarafa 7.0.x and zarafa 7.1.x from the opensuse repository. I'm assuming this is a problem to do with the very limited execution environment systemd passes on to process it starts and that there is something special that the zarafa-spooler needs that isn't being provided by systemd. Note that all zarafa processes are still using /etc/init.d scripts rather than unit files. As it stands my mailserver does not survive a reboot as it needs manual intervention to get it to deliver mail. Reproducible: Always Steps to Reproduce: 1. # systemctl start zarafa-spooler.service 2. send an email from within zarafa 3. Actual Results: The mail will sit in outbox forever and not be delivered. Expected Results: Zarafa-spooler will pick up the mail and deliver it to the local MTA (postfix) for delivery. If the spooler is stopped and started on the command line ie. # systemctl stop zarafa-spooler.service # /usr/sbin/zarafa-spooler The mail is immediately picked up from the outbox and delivered. -- 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 12