November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1114008] SSH access fails after upgrade to openssh-7.8p1-1.1.x86_64
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1114008 Libor Pechacek <lpechacek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lpechacek(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112769] login.defs uid/gid values during autoyast install not respected
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1112769 http://bugzilla.suse.com/show_bug.cgi?id=1112769#c12 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers(a)suse.de Flags| |needinfo?(systemd-maintaine | |rs(a)suse.de) --- Comment #12 from Lukas Ocilka <locilka(a)suse.com> --- Systemd-Maintainers: Installer writes /etc/login.defs too late to be taken into account when users are created (in some cases). We can fix it, but it will probably not fix users created by the systemd package. Is there a way how we could influence it (and the user/customer)? When (the latest) can we write those settings and where? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112769] login.defs uid/gid values during autoyast install not respected
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1112769 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112769] login.defs uid/gid values during autoyast install not respected
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1112769 http://bugzilla.suse.com/show_bug.cgi?id=1112769#c11 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast-internal(a)suse.de |schubi(a)suse.com --- Comment #11 from Lukas Ocilka <locilka(a)suse.com> --- (In reply to Yan nix from comment #10) > Oh I see. In the meantime, I recompiled the shadow RPM package and set it so > it won't overwrite my /etc/login.defs from my DUD. The RPM postscripts that > call useradd/groupadd creates system user/group entries within my desired > uid/gid now. You could also try AutoYaST scripts. See https://susedoc.github.io/doc-sle/develop/SLES-autoyast/html/configuration.… for more information (you can, e.g., change /etc/login.defs after installing packages). I'd probably start with 4.30.3 Chroot Environment Scripts > However, I ran into an issue with systemd and specifically sysusers part of > it. After a lot of testing and reading, I find out to my chagrin that > systemd has taken some user/group creation and apparently is too special as > to ignore values from /etc/login.defs (at least uid/gid values). It looks > like its uid/gid values is set at compile time and there's no concept of > minimum, only a maximum. FWIW, the value for Leap 15 is 499 for both > systemuidmax and systemgidmax. Thanks, this is very useful. Could you, please, open another bugreport just systemd? It's a different package, different team, different bug. > I am just reporting back to point out that moving the security module to > first stage might only fix the ones that uses /etc/login.defs and will still > be broken for systemd created users. Hopefully as a reference too in case > someone runs into the same issue. See /usr/lib/sysusers.d/basic.conf and /usr/lib/sysusers.d/systemd.conf > I am still hoping there's a systemd runtime setting I haven't found yet as I > really don't want to get into recompiling systemd. Thanks Systemd users are created using %sysusers_create macro (e.g. at, https://build.opensuse.org/package/view_file/openSUSE:Factory/systemd/syste…) but that just calls `/usr/bin/systemd-sysusers` Try `man systemd-sysusers` And see https://github.com/systemd/systemd/blob/ad16158c10dfc3258831a9ff2f1a988214f… -> you can define IDs in those config files and the code is here https://github.com/systemd/systemd/blob/master/src/sysusers/sysusers.c#L158… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1110669] twisted.internet.gireactor (python3-Twisted) requires pygtkcompat
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=1110669 http://bugzilla.novell.com/show_bug.cgi?id=1110669#c2 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |mcepl(a)suse.com |ovo.novell.com | --- Comment #2 from Tomáš Chvátal <tchvatal(a)suse.com> --- Matej could you check this up and reassign to someone if needed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084943] NetworkManager with autoconnect enabled displays error messages
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1084943 http://bugzilla.suse.com/show_bug.cgi?id=1084943#c39 --- Comment #39 from Frank Kruger <fkrueger(a)mailbox.org> --- Let me recall that this issue does not show up after first login, only when I logout/login from/to the KDE session. So what is different here, as far as this race condition is concerned? Any idea from the KDE side? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084943] NetworkManager with autoconnect enabled displays error messages
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1084943 http://bugzilla.suse.com/show_bug.cgi?id=1084943#c38 --- Comment #38 from Frank Kruger <fkrueger(a)mailbox.org> --- (In reply to Jonathan Kang from comment #36) > The reason why an error message show up firstly is when NM asks for secrets, > sddm > session hasn't quitted yet. > ... > The possible improvement to this issue I can think of is to disable WPS > push-button method by default to reduce the duration of the first activation > process. > > Thought? Isn't disabling wps by default brute force? What about those people using it? Since the issue seems to be due to a race between NM (asking for secrets) and sddm (not finished yet), as you wrote, I doubt that wps is the main culprit. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1050305] Libreoffice extension 'Language Tool' fails after Tumbleweed update
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1050305 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:9277:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114267] with kernel-default 4.19.0-3.1, don't start X
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.novell.com/show_bug.cgi?id=1114267 http://bugzilla.novell.com/show_bug.cgi?id=1114267#c1 --- Comment #1 from Masaru Nomiya <nomiya(a)galaxy.dti.ne.jp> --- Sorry, it's my bad! Upgrading xorg-x11 is the cause. Thanks, -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041469] llvm4 spec issues
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1041469 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:8721:important | -- You are receiving this mail because: You are on the CC list for the bug.

1 0