January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1194210] The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194210 http://bugzilla.opensuse.org/show_bug.cgi?id=1194210#c7 --- Comment #7 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Maybe bug 1194193? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194210] The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194210 http://bugzilla.opensuse.org/show_bug.cgi?id=1194210#c6 --- Comment #6 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Again, why do you think you are unable to report a bug on one URL but not the other? Describe the steps you do, and what you observe until you think "hmm this is not working". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194210] The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194210 http://bugzilla.opensuse.org/show_bug.cgi?id=1194210#c5 --- Comment #5 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Both addresses are valid. Just try it with this bug: https://bugzilla.suse.com/show_bug.cgi?id=1194210 https://bugzilla.opensuse.org/show_bug.cgi?id=1194210 will both take you here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194210] The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194210 http://bugzilla.opensuse.org/show_bug.cgi?id=1194210#c3 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |79625490833(a)yandex.ru, | |Andreas.Stieger(a)gmx.de Flags| |needinfo?(79625490833@yande | |x.ru) --- Comment #3 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Nikolay Sabelnikov from comment #2) > I can't enter. Why? Describe the details. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194203] New fetchmail requires group "fetchmail" on openSUSE leap 15.2 (at least ...) that is not present
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194203 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194104] REQUEST: language restriction
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194104 https://bugzilla.suse.com/show_bug.cgi?id=1194104#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- For some packages, that may actually be the case; but that's a bug of the affected package(s), not of the installer. There is nothing that we can do about this from the side of the installer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192418] New: wicked fails to set nameservers
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192418 Bug ID: 1192418 Summary: wicked fails to set nameservers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: noreply.section+dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting from snapshot 20211105 and wicked 0.6.67, the network is not initialized correctly. In particular, resolv.conf is not populated with the nameservers from DHCP. Multiple of these errors show up in the log: wickedd-dhcp4: unexpected combination of interface flags 0x11003 wickedd-dhcp6: unexpected combination of interface flags 0x11003 wickedd-auto4: unexpected combination of interface flags 0x11003 Reverting to wicked 0.6.66 solves the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1186251] VUL-0: CVE-2021-20204: getdata: Use after free in _GD_Supports() in encoding.c
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1186251 https://bugzilla.suse.com/show_bug.cgi?id=1186251#c4 Christian Trippe <ctrippe(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Christian Trippe <ctrippe(a)opensuse.org> --- update was released -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189027] The ability to configure what the password should be, as well as its generation
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1189027 https://bugzilla.suse.com/show_bug.cgi?id=1189027#c5 --- Comment #5 from Nikolay Sabelnikov <79625490833(a)yandex.ru> --- (In reply to Ancor Gonzalez Sosa from comment #4) > Creating a user without password is a pretty specialized case. Of course > there might be use-cases for it, but I don't think it's something to be > offered as an option in a normal installation. We don't want to encourage > such an insecure setup. Admins needing that are surely knowledgeable enough > to configure it manually. > > If I read it correctly, you also suggest to integrate a passwords generator > into YaST (which is, by the way, a completely separated topic). That may > make more sense, it would also be usable to set the key for encrypted > devices. Something similar was suggested here [1]. It would need a good UI > design and it will bring some security and usability concerns, but is maybe > a possibility worth exploring. > > [1] https://bugzilla.suse.com/show_bug.cgi?id=1185291#c3 this topic closely echoes the recent open topic https://bugzilla.suse.com/show_bug.cgi?id=1194042 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194206] New: chronyd.service fails to start
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194206 Bug ID: 1194206 Summary: chronyd.service fails to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting recently, current TW chronyd.service fails to run. 2022-01-02T09:06:40.782714+01:00 awe chronyd[9914]: chronyd version 4.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG) 2022-01-02T09:06:40.783443+01:00 awe chronyd[9914]: Fatal error : Could not open /var/run/chrony/chronyd.pid : Read-only file system 2022-01-02T09:06:40.786347+01:00 awe chronyd[9912]: Could not open /var/run/chrony/chronyd.pid : Read-only file system 2022-01-02T09:06:40.786621+01:00 awe systemd[1]: chronyd.service: Control process exited, code=exited, status=1/FAILURE tw VERSION_ID "20211221" with package chrony-4.1-6.1.x86_64 was okay. tw VERSION_ID "20211228" with package chrony-4.2-1.1.x86_64 fails. -- You are receiving this mail because: You are on the CC list for the bug.

1 1