August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1049097] YaST2 - Network Settings report error after changing network manager from wicked to NetworkManager
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1049097 http://bugzilla.suse.com/show_bug.cgi?id=1049097#c5 Nick Singer <nsinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nsinger(a)suse.com) | --- Comment #5 from Nick Singer <nsinger(a)suse.com> --- http://openqa.glados.qa.suse.de/tests/336#downloads now contains several logs (everything with "yast2_network_setup" prefix is relevant here) including y2logs. In y2log, from line 6410 yast checks several network services (or this is just a retry counter) which all seem to be offline. Also the main network interface (called "sta0" in that VM) is down after changing to NetworkManager. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1039837] New: password policy configuration
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1039837 Bug ID: 1039837 Summary: password policy configuration Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: 64bit OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: pmm3012(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 725650 --> http://bugzilla.opensuse.org/attachment.cgi?id=725650&action=edit Image is taken when error come out at time when password policy edited and clicked OK I want to configure openldap password policy. so that Users can change their password Forcefully At First time login. I am using openldap2-2.4.44-14.1.x86_64 version. I had tried to configure with yast2 auth-server >> databases >> dc=domain-name**>>password policy configuration clicked on enable password policy >> edit policy >>Clicked OK >> Clicked OK got Error error while committing the change to config databases in details it prints Other (e.g., implementation specific) error: <olcAccess> handler exited with 1 Every thing Other than that Working properly. We are able to login via ldap authentication and able to self change password. but first login password change option not working in opensuse leap 42.2. password policy Works in SLES 12 SP2 properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1031170] Password Policy Configuration Exits with error on 42.2
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1031170 http://bugzilla.opensuse.org/show_bug.cgi?id=1031170#c7 --- Comment #7 from Howard Guo <hguo(a)suse.com> --- Please use the resolution from this bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1047217 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1051340] Missing file for Yast2-Rear
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1051340 http://bugzilla.suse.com/show_bug.cgi?id=1051340#c2 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Flags|needinfo?(cwh(a)suse.com) | --- Comment #2 from Ladislav Slezák <lslezak(a)suse.com> --- The files are there in Git (see https://github.com/yast/yast-rear/tree/master/src/lib/rear) It seems that the Makefile.am (https://github.com/yast/yast-rear/blob/master/src/Makefile.am) has not been updated so the files are missing in the built RPM. I'll fix that as a part of the bug squashing day ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1048911] Plymouth core dumps on every boot of Tumbleweed system
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=1048911 http://bugzilla.novell.com/show_bug.cgi?id=1048911#c13 --- Comment #13 from Stuart Rogers <stuart(a)stella-maris.org.uk> --- I now have an issue with continuing with this bug. Since I updated yesterday my TW system has been booting just fine with the plymouth screen displaying normally and no debug log being created. Also no dumps have been created on these boots. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1039034] no ODBC support in MariaDB Server
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1039034 http://bugzilla.suse.com/show_bug.cgi?id=1039034#c2 --- Comment #2 from Thomas Hänig <haenig(a)cosifan.de> --- Thanks a lot, this indeed fixes the issue for me. With this build I have been able to successfully connect from MySQL to a MS SQL Database. best regards Thomas -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1049097] YaST2 - Network Settings report error after changing network manager from wicked to NetworkManager
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1049097 http://bugzilla.suse.com/show_bug.cgi?id=1049097#c4 --- Comment #4 from Nick Singer <nsinger(a)suse.com> --- No, not yet. I'm about to collect the relevant yast logs but have to fix an issues with the test itself in before. Will update -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1049179] kernel: possible regression: "sleeping function called from invalid context" during shutdown
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.suse.com/show_bug.cgi?id=1049179 http://bugzilla.suse.com/show_bug.cgi?id=1049179#c4 --- Comment #4 from Neil Brown <nfbrown(a)suse.com> --- Weird. When mdmon exits, the kernel seems to think that it is in_atomic() and in_interrupt(), which it shouldn't be. I cannot think of any way that this could happen. You aren't using oprofile are you? That could make the 'exit' handling a little more complex, but I still doubt it would change the "preempt_count" variable, which stores the in_atomic and in_interrupt status. -- You are receiving this mail because: You are on the CC list for the bug.

1 0