June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 842108] New: curl (e.g. from inside zypper dup) suddeny switches to ipv6 on ipv4-only host and fails zypper progress
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=842108 https://bugzilla.novell.com/show_bug.cgi?id=842108#c0 Summary: curl (e.g. from inside zypper dup) suddeny switches to ipv6 on ipv4-only host and fails zypper progress Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: abittner(a)abittner.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 I remember quite vividly that I used to report similar bugs and these ipv6 madness many opensuse versions back 12.1 and others come to my mind e.g. <https://bugzilla.novell.com/show_bug.cgi?id=765638> so today trying a zypper dup from a 13.1/m4 to 13.1/b1 on an ipv4-only host (and ipv4-only network, with ipv4-only ISP) eventually fails sometimes during fetching one or another package. var/log/zypper.log shows the ipv6 curl errors that it cannot reach the ipv6 address. this is a real shame. is it possible to sort these ipv6 mad bugs out ever? or is there just no solution to this? ever since ipv6 came along to get more wider adoption with opensuse it has been a huge pain in many areas of the distro :(, when actually trying to NOT use it, or trying to stay away from it or being unable to use it due to ISP limitations and so on. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: routing tables linux-box:~ # ip route show table local broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1 local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1 broadcast 192.168.15.0 dev eth0 proto kernel scope link src 192.168.15.53 local 192.168.15.53 dev eth0 proto kernel scope host src 192.168.15.53 broadcast 192.168.15.255 dev eth0 proto kernel scope link src 192.168.15.53 linux-box:~ # ip route show default via 192.168.15.254 dev eth0 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev eth0 scope link 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.53 linux-box:~ # ifconfig eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:192.168.15.53 Bcast:192.168.15.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:912124 errors:0 dropped:611 overruns:0 frame:0 TX packets:510169 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1280623420 (1221.2 Mb) TX bytes:38352458 (36.5 Mb) zypper.log excerpt 2013-09-24 19:28:52 <1> linux-box(20933) [zypp:fetcher] Fetcher.cc(provideFromCache):350 start fetcher with 1 cache directories. 2013-09-24 19:28:52 <1> linux-box(20933) [zypp:fetcher] Fetcher.cc(provideToDest):547 Not found in cache, downloading 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaSetAccess.cc(provide):203 Going to try to provide file /suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm from media number 1 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaManager.cc(checkDesired):112 checkDesired(1): desired (cached) 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaManager.cc(checkDesired):112 checkDesired(1): desired (cached) 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1319 dest: /var/adm/mount/AP_0xPkRC8l/suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1320 temp: /var/adm/mount/AP_0xPkRC8l/suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm.new.zypp.FRo1Rg 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaCurl.cc(doGetFileCopyFile):1365 /suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm 2013-09-24 19:28:52 <1> linux-box(20933) [zypp++] MediaCurl.cc(doGetFileCopyFile):1375 URL: http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit… 2013-09-24 19:29:22 <3> linux-box(20933) [zypp] MediaCurl.cc(doGetFileCopyFile):1439 curl error: 7: Failed to connect to 2001:67c:2178:8::13: Network is unreachable, temp file size 0 bytes. 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaCurl.cc(evaluateCurlCode):1044 THROW: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaCurl.cc(evaluateCurlCode):1048 RETHROW: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaCurl.cc(doGetFileCopyFile):1451 RETHROW: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] PathInfo.cc(unlink):666 unlink /var/adm/mount/AP_0xPkRC8l/suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm.new.zypp.FRo1Rg 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaMultiCurl.cc(doGetFileCopy):1350 RETHROW: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaCurl.cc(getFileCopy):885 RETHROW: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 MediaSetAccess.cc(provide):216 CAUGHT: Download (curl) error for 'http://download.opensuse.org/distribution/13.1/repo/oss/suse/i586/libwebkit…': 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error code: Connection failed 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable 2013-09-24 19:29:22 <5> linux-box(20933) [zypp] Exception.cc(log):137 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaManager.cc(checkDesired):112 checkDesired(1): desired (cached) 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(getDetectedDevices):1370 No devices for this medium 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaSetAccess.cc(provide):228 Media couldn't provide file /suse/i586/libwebkitgtk-3_0-0-2.1.90.1-1.1.i586.rpm , releasing. 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaManager.cc(release):486 release(id=1) 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(release):723 Request to release attached media http<http://download.opensuse.org/distribution/13.1/repo/oss/>, use count=1 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(release):730 Releasing media http<http://download.opensuse.org/distribution/13.1/repo/oss/> 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaHandler.cc(disconnect):702 Disconnected: http://download.opensuse.org/distribution/13.1/repo/oss/ attached; localRoot "/var/adm/mount/AP_0xPkRC8l" 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(removeAttachPoint):179 MediaHandler - checking if to remove attach point 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/adm/mount/AP_0xPkRC8l 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaHandler.cc(removeAttachPoint):191 Deleted default attach point /var/adm/mount/AP_0xPkRC8l 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaHandler.cc(release):784 Released: http://download.opensuse.org/distribution/13.1/repo/oss/ not attached; localRoot "" 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaManager.cc(releaseAll):525 Releasing all attached media 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaManager.cc(releaseAll):543 Media id 1 not attached 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaManager.cc(releaseAll):553 Exit 2013-09-24 19:29:22 <1> linux-box(20933) [zypper++] media.cc(requestMedia):215 medium problem, url: http://download.opensuse.org/distribution/13.1/repo/oss/, error 3, label 'openSUSE-13.1-Oss', #1 2013-09-24 19:29:22 <1> linux-box(20933) [zypper] misc.cc(is_changeable_media):39 Checking if this is a changeable medium 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaAccess.cc(open):117 Trying scheme 'http' 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaCurl.cc(MediaCurl):450 MediaCurl::MediaCurl(http://download.opensuse.org/distribution/13.1/repo/os…, ) 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaMultiCurl.cc(MediaMultiCurl):1158 MediaMultiCurl::MediaMultiCurl(http://download.opensuse.org/distribution/13…, ) 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaAccess.cc(open):197 Opened: http(http://download.opensuse.org/distribution/13.1/repo/oss/ not attached; localRoot "") 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaManager.cc(open):277 Opened new media access using id 2 to http://download.opensuse.org/distribution/13.1/repo/oss/ 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaManager.cc(close):309 Close to access handler using id 2 requested 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(release):716 Request to release media - not attached; eject '' 2013-09-24 19:29:22 <1> linux-box(20933) [zypp] MediaAccess.cc(close):248 Close: http(http://download.opensuse.org/distribution/13.1/repo/oss/ not attached; localRoot "") (OK) 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(release):716 Request to release media - not attached; eject '' 2013-09-24 19:29:22 <1> linux-box(20933) [zypp++] MediaHandler.cc(removeAttachPoint):179 MediaHandler - checking if to remove attach point 2013-09-24 19:31:35 <1> linux-box(20933) [zypper] Zypper.cc(cleanup):4948 START 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/tmp/zypp.CQOl2t 2013-09-24 19:31:35 <1> linux-box(20933) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.CQOl2t{d 0700 0/0} 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] ZYppFactory.cc(_openLockFile):166 Open lockfile /var/run/zypp.pid 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] ZYppFactory.cc(~ZYppGlobalLock):115 Cleanned lock file. (20933) 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] ZYppFactory.cc(_closeLockFile):184 Close lockfile /var/run/zypp.pid 2013-09-24 19:31:35 <1> linux-box(20933) [zypper] Zypper.cc(~Zypper):85 Zypper instance destroyed. Bye! 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/tmp/TmpDir.I9k1Wj 2013-09-24 19:31:35 <1> linux-box(20933) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.I9k1Wj{d 0700 0/0} 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] RpmDb.cc(closeDatabase):734 Calling closeDatabase: RpmDb[V4(X--)V3(---): '(/)/var/lib/rpm'] 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] librpmDb.cc(blockAccess):328 Block access 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] RpmDb.cc(closeDatabase):765 closeDatabase: RpmDb[NO_INIT] 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] TargetImpl.cc(~TargetImpl):815 Targets closed 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] RpmDb.cc(~RpmDb):268 ~RpmDb() 2013-09-24 19:31:35 <1> linux-box(20933) [zypp] RpmDb.cc(~RpmDb):271 ~RpmDb() end -- 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 854263] New: apache update causes "403 forbidden" errors
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=854263 https://bugzilla.novell.com/show_bug.cgi?id=854263#c0 Summary: apache update causes "403 forbidden" errors Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEEDINFO Severity: Critical Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de InfoProvider: maintenance(a)opensuse.org Found By: Beta-Customer Blocker: --- There are separal reports on the opensuse-de mailinglist that apache will only deliver "403 forbidden" errors since the latest update. The log contains: [Fri Dec 06 17:53:22.804744 2013] [authz_core:error] [pid 3513] [client 127.0.0.1:58895] AH01630: client denied by server configuration: /srv/www/htdocs/index.html It reportedly works again after replacing "Order by ..." and "Allow from ... " / "Deny from ..." with "Require ...". I'd guess that... === openSUSE-2013-906 - Patch 1 (recommended) === apache2: Update apache2 to reflect changes introduced in Apache 2.4 This update fixes the following issue with apache2: - bnc#848146: Removed obsolete directive DefaultType - Changed Order Deny Allow directives to new Require{|Any|All|None} === .. "Changed Order Deny Allow directives..." is the change that broke it - it seems that "Require" has more weight than the old directives and overrules them. BTW: I've seen the same problem in factory, so I can help with testing if needed. @maintenance team: can you please remove this update until this bug is fixed to avoid breaking more systems? -- 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 32

[Bug 873975] New: home:scarabeus_iv/bumblebee: Bug
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=873975 https://bugzilla.novell.com/show_bug.cgi?id=873975#c0 Summary: home:scarabeus_iv/bumblebee: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: tchvatal(a)suse.com ReportedBy: zdenek(a)ille.cz QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=586661) --> (http://bugzilla.novell.com/attachment.cgi?id=586661) 10-bumblebee I have problem like system freeze with hibernation. Solved by stopping bumblebeed before hibernation "systemctl stop bumblebeed" -- 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 862988] New: wacom 0.20.0 needed to make CTH-480 work
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=862988 https://bugzilla.novell.com/show_bug.cgi?id=862988#c0 Summary: wacom 0.20.0 needed to make CTH-480 work Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: javier(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) QupZilla/1.7.0 Safari/537.21 wacom 0.20.0 is needed to make the CTH-480 (Intuos Pen & Touch, small) work on openSUSE 13.1. The patches included in this version have already been accepted upstream. Perhaps we could push an update. What do you think? Package: https://build.opensuse.org/package/show/home:javierllorente/wacom Discussion: http://linuxwacom-discuss.996327.n3.nabble.com/Status-of-support-for-CTH-48… 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 775279] New: Automount fails to bind to LDAP server using SASL + GSSAPI
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=775279 https://bugzilla.novell.com/show_bug.cgi?id=775279#c0 Summary: Automount fails to bind to LDAP server using SASL + GSSAPI Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: joschibrauchle(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=501834) --> (http://bugzilla.novell.com/attachment.cgi?id=501834) LDAP bind packet showing "mutual-authentication-required" bit set to 0 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.57 Safari/537.1 This is a followup on a discussion on the autofs mailing-list, see: http://www.spinics.net/lists/autofs/msg00174.html Problem: ------------------------------------------------------- Automount 5.0.7 fails to bind to LDAP server (OpenLDAP 2.4.26 server running on SLES11SP1) using SASL + GSSAPI. Error message: ------------------------------------------------------- automount -f -d: Starting automounter version 5.0.7, master map auto.master using kernel protocol version 5.02 lookup_nss_read_master: reading master files auto.master parse_init: parse(sun): init gathered global options: (null) spawn_mount: mtab link detected, passing -n to mount spawn_umount: mtab link detected, passing -n to mount lookup_read_master: lookup(file): read entry +auto.master lookup_nss_read_master: reading master files auto.master parse_init: parse(sun): init gathered global options: (null) lookup_nss_read_master: reading master ldap auto.master parse_server_string: lookup(ldap): Attempting to parse LDAP information from string "auto.master". parse_server_string: lookup(ldap): mapname auto.master parse_ldap_config: lookup(ldap): ldap authentication configured with the following options: parse_ldap_config: lookup(ldap): use_tls: 0, tls_required: 0, auth_required: 2, sasl_mech: GSSAPI parse_ldap_config: lookup(ldap): user: (null), secret: unspecified, client principal: host/<hostname>.<fqdn>@<REALM> credential cache: (null) parse_init: parse(sun): init gathered global options: (null) find_server: trying server uri ldap://<LDAPSERVER> do_bind: lookup(ldap): auth_required: 2, sasl_mech GSSAPI sasl_do_kinit: initializing kerberos ticket: client principal host/<hostname>.<fqdn>@<REALM> sasl_do_kinit: calling krb5_parse_name on client principal host/<hostname>.<fqdn>@<REALM> sasl_do_kinit: Using tgs name krbtgt/<REALM>@<REALM> sasl_do_kinit: Kerberos authentication was successful! sasl_bind_mech: Attempting sasl bind with mechanism GSSAPI getuser_func: called with context (nil), id 16385. The LDAP server indicated that the LDAP SASL bind was incomplete, but did not provide the required data to proceed. LDAP SASL bind with mechanism GSSAPI failed. sasl bind with mechanism GSSAPI failed do_bind: lookup(ldap): autofs_sasl_bind returned -1 lookup(ldap): couldn't connect to server ldap://<LDAPSERVER> do_reconnect: lookup(ldap): failed to find available server lookup(file): failed to read included master map auto.master no mounts in table Configuration: ------------------------------------------------------- /etc/autofs_ldap_auth.conf looks like this: <?xml version="1.0" ?> <autofs_ldap_sasl_conf authrequired="yes" authtype="GSSAPI" clientprinc="host/<hostname>.<fqdn>@<REALM>" /> /etc/sysconfig/autofs contains: LDAP_URI="ldap://<LDAPSERVER>" /etc/ldap.conf and /etc/openldap/ldap.conf are not configured, as the previous two conf files should suffice. /etc/krb5.conf is using a working (other kerberized tools work) kerberos config, /etc/krb5.keytab contains principal of the form "host/<hostname>.<fqdn>@<REALM>". LDAP with SASL bind and GSSAPI mech works in general: ------------------------------------------------------- "ldapsearch -H ldap://<LDAPSERVER> -Y GSSAPI" returns LDAP data! Wireshark trace comparison between automount (bind fails) and ldapsearch (bind OK): ------------------------------------------------------- ldapsearch: -------------- -> Client sends a bind request including a KRB-AP-REQ, with the "mutual-authentication-required" bit set to 1. <- Receives a bind response saying "SASLBindInProgress", containing the "serverSASLcreds" plus some more GSSAPI/Kerberos data. <-> Continues on and binds successfully... automount (see screenshot): -------------- -> Client sends a bind request including a KRB-AP-REQ, with the "mutual-authentication-required" bit set to 0! <- Receives a bind response saying "SASLBindInProgress" but which does NOT contain any "serverSASLcreds" and no further GSSAPI/Kerberos data. -> Sends an unbind request. I have also unsuccessfully tested automount version 5.0.5 as well as a special version by "Leonardo Chiquitto" from "http://download.opensuse.org/repositories/home:/leonardocf:/branches:/openS…", which reverts the "http://www.kernel.org/pub/linux/daemons/autofs/v5/patches-5.0.7/autofs-5.0.…". Hence it looks like the problem *may* not be the fault of automount, but rather *could* coming from some of its dependencies, like openldap, cyrus sasl, MIT kerberos... Reproducible: Always Steps to Reproduce: 1. Configure AutoFS to use LDAP, SASL and GSSAPI 2. Acquire Kerberos credentials 3. Start automount Actual Results: Bind fails Expected Results: Bind succeeds -- 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 28

[Bug 868588] New: cyrus-sasl broken for connecting to MS AD with "GSSAPI Error: A required input parameter could not be read (Unknown error)"
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=868588 https://bugzilla.novell.com/show_bug.cgi?id=868588#c0 Summary: cyrus-sasl broken for connecting to MS AD with "GSSAPI Error: A required input parameter could not be read (Unknown error)" Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: boris(a)steki.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 using squid with kerberos tickets is not possible because cyrus-sasl patch introduced while ago breaks its usage Already upstream documented here: https://bugzilla.cyrusimap.org/show_bug.cgi?id=3480 I have using cyrus-sasl with this patch and it definitely makes things work ---- without patch ---- support_ldap.cc(845): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Setting up connection to ldap server ldap.ADDOMAIN:636 support_ldap.cc(690): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Set SSL defaults support_ldap.cc(519): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Disable server certificate check for ldap server. support_ldap.cc(704): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while setting start_tls for ldap server: Operations error support_ldap.cc(845): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Setting up connection to ldap server ldap.ADDOMAIN:389 support_ldap.cc(690): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Set SSL defaults support_ldap.cc(519): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Disable server certificate check for ldap server. support_ldap.cc(704): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while setting start_tls for ldap server: Can't contact LDAP server support_ldap.cc(856): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI support_sasl.cc(268): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Can't contact LDAP server support_ldap.cc(860): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Can't contact LDAP server support_ldap.cc(845): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Setting up connection to ldap server ldap.ADDOMAIN:636 support_ldap.cc(690): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Set SSL defaults support_ldap.cc(519): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Disable server certificate check for ldap server. support_ldap.cc(704): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while setting start_tls for ldap server: Can't contact LDAP server support_ldap.cc(856): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI support_sasl.cc(268): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Can't contact LDAP server support_ldap.cc(860): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while binding to ldap server with SASL/GSSAPI: Can't contact LDAP server support_ldap.cc(845): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Setting up connection to ldap server ADDOMAIN:389 support_ldap.cc(690): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Set SSL defaults support_ldap.cc(519): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Disable server certificate check for ldap server. support_ldap.cc(704): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: Error while setting start_tls for ldap server: Can't contact LDAP server support_ldap.cc(856): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI support_sasl.cc(268): pid=10733 :2014/03/15 13:38:47| kerberos_ldap_group: ERROR: ldap_sasl_interactive_bind_s error: Can't contact LDAP server ---- end without patch ---- ---- with patch ---- support_ldap.cc(845): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Setting up connection to ldap server ldap.ADDOMAIN:636 support_ldap.cc(690): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Set SSL defaults support_ldap.cc(519): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Disable server certificate check for ldap server. support_ldap.cc(704): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: ERROR: Error while setting start_tls for ldap server: Operations error support_ldap.cc(856): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Bind to ldap server with SASL/GSSAPI support_ldap.cc(870): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Successfully initialised SSL protected connection to ldap server ldap.ADDOMAIN:636 support_ldap.cc(299): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Search ldap server with bind path "" and filter: (objectclass=*) support_ldap.cc(569): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Search ldap entries for attribute : schemaNamingContext support_ldap.cc(615): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: 1 ldap entry found with attribute : schemaNamingContext support_ldap.cc(308): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Search ldap server with bind path CN=Schema,CN=Configuration,dc=ldap,dc=ADDOMAIN and filter: (ldapdisplayname=samaccountname) support_ldap.cc(311): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Found 1 ldap entry support_ldap.cc(316): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Determined ldap server as an Active Directory server support_ldap.cc(978): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Search ldap server with bind path dc=ldap,dc=ADDOMAIN and filter : (samaccountname=luzer) support_ldap.cc(991): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Found 1 ldap entry support_ldap.cc(569): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: Search ldap entries for attribute : memberof support_ldap.cc(615): pid=11726 :2014/03/15 14:30:13| kerberos_ldap_group: DEBUG: 19 ldap entries found with attribute : memberof ---- with patch ---- Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: login with kerberos ticket of HTTP/ principal logins to ldap -- 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 876184] New: Enhancement: to disable scanner menu, when install/remove software is in use
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=876184 https://bugzilla.novell.com/show_bug.cgi?id=876184#c0 Summary: Enhancement: to disable scanner menu, when install/remove software is in use Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: 64bit OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: contracts(a)lobikfilip.eu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 Due to the fact, that during the first configuration of a scanner on OpenSUSE 13.1 in YaST2, it takes a very long time until the list of supported scanners appears, and I am almost sure that it is always required to install new packages to make the first installed scanner work, I suggest that that the "Scanner" menu in "Yast2" be disabled during the installation procedure, if the "install new software" procedure is on: - user clicks on "Scanner" in "Yast2" - "Yast2" checks whether software management features are processing - if "yes", then break and notify to open after install (or suggest to open after software management will be done) - else: keep it real Reproducible: Always Steps to Reproduce: 1. Install software 2. Open "Scanner" in "Yast2" for first time configuration 3. Add new scanner Actual Results: could not install hpaio could not install hplip Expected Results: don't open scanner, if it's being run for the first time & install software is in use -- 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 882599] New: Yast LDAP/KRB module and Kerberos Expert settings not honored by SSSD
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=882599 https://bugzilla.novell.com/show_bug.cgi?id=882599#c0 Summary: Yast LDAP/KRB module and Kerberos Expert settings not honored by SSSD Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: joschibrauchle(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 On openSUSE 13.1+, only SSSD is officially supported in combination with LDAP and Kerberos and replaced the old nss/pam/ldap/krb libs. Problem 1) Only Yast has never really caught up with this change. Most Kerberos **Expert** settings need to be set in the Kerberos Module, which is **disabled** by default when SSSD is used. In order to set expert settings, "Use Kerberos" must be enabled in Kerberos module, the settings must be changed and "Use Kerberos" must be disabled again Problem 2) All Kerberos **expert** settings configured in Yast are stored in /etc/krb5.conf like so: ----------------- [appdefaults] pam = { ticket_lifetime = 14d renew_lifetime = 31d forwardable = true proxiable = false minimum_uid = 10000 clockskew = 300 external = sshd use_shmem = sshd } ----------------- In combination with SSSD these settings are **ignored** as SSSD (using the Kerberos libraries) needs them to be set under "[libdefaults]"! Hence, for the short term, please fix Yast Kerberos modules to store expert settings as "[libdafaults]" and not "[appdefaults]". In the long term, please remove LDAP Client + Kerberos Module and provide a well thought out module to configure SSSD! Reproducible: Always Steps to Reproduce: 1. Set some Kerberos expert settings in Yast Actual Results: Expert settings are ignores by SSSD because they are saved as "[appdefaults]" for old Kerberos PAM module Expected Results: Expert settings should be saved as "[libdefaults]" such that SSSD recognizes them. PAM kerberos module is not supported by Yast anymore! -- 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 1

[Bug 803389] New: wpa_supplicant loaded twice preventng wifi from working
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=803389 https://bugzilla.novell.com/show_bug.cgi?id=803389#c0 Summary: wpa_supplicant loaded twice preventng wifi from working Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: thnielsen(a)novell.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- After poking around a lot in network configuration, i found that /var/log/messages was screaming at me connecting disconnecting etcetcetc This condition started after a recent zypper up (my wifi was working nice before upgrading) - versions below Disabling wifi in Networkmanager and killing the remaining wpa_supplicant reenable wifi makes things work. Here some facts: rpm -qf /usr/sbin/wpa_supplicant wpa_supplicant-1.1-1.1.x86_64 linux:/etc/NetworkManager # ps -aux |grep wpa root 3031 0.7 0.0 29652 1560 ? Ss 19:05 0:05 wpa_supplicant -iwlan0 -c/var/run/wpa_supplicant-wlan0.conf -Dnl80211,wext -P/var/run/wpa_supplicant/wlan0.pid -B root 5382 0.8 0.0 29776 3108 ? S 19:07 0:05 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log root 6334 0.0 0.0 7056 860 pts/1 S+ 19:17 0:00 grep --color=auto wpa linux:/etc/NetworkManager # rpm -qa |grep Net NetworkManager-vpnc-0.9.6.0-2.1.x86_64 NetworkManager-pptp-kde4-0.9.0.7-1.1.x86_64 perl-Net-DBus-1.0.0-4.7.x86_64 NetworkManager-vpnc-kde4-0.9.0.7-1.1.x86_64 perl-NetxAP-0.02-715.4.x86_64 NetworkManager-openvpn-0.9.6.0-1.2.x86_64 NetworkManager-openvpn-kde4-0.9.0.7-1.1.x86_64 NetworkManager-0.9.6.4-7.1.x86_64 NetworkManager-kde4-libs-0.9.0.7-1.1.x86_64 NetworkManager-pptp-0.9.6.0-1.2.x86_64 NetworkManager-kde4-libs-lang-0.9.0.7-1.1.noarch -- 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 876425] New: Iface files for BCM 5709 card are not generated with inbox drivers on SLES 12 Beta 5
by bugzilla_noreply＠novell.com 13 Jun '14

13 Jun '14

https://bugzilla.novell.com/show_bug.cgi?id=876425 https://bugzilla.novell.com/show_bug.cgi?id=876425#c0 Summary: Iface files for BCM 5709 card are not generated with inbox drivers on SLES 12 Beta 5 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SLES 12 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Siddharth.moghe(a)qlogic.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36 Iface files for BCM 5709 card are not generated with inbox drivers on SLES 12 Beta 5 Reproducible: Always Steps to Reproduce: 1. Install a BCM 5709 card with GA firmware 2. Execute iscsiadm -m iface to generate iface files 3. bnx2i.00:00:00:00:00:00:00 is what gets generated. 4. The system also has a 57810 and 57712 cards, for which iface files are generated Actual Results: bnx2i with all 0 mac is generated inplace of the iscsi iface file Expected Results: the proper iscsi file carrying the iscsi mac should be genereated -- 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