January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1179014] [rpm4.16] invalid use of barewords in kernel spec files
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179014 https://bugzilla.suse.com/show_bug.cgi?id=1179014#c24 --- Comment #24 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:0094-1: An update that solves 8 vulnerabilities and has 46 fixes is now available. Category: security (moderate) Bug References: 1040855,1044120,1044767,1055117,1065729,1094840,1109695,1112178,1114648,1115431,1138374,1152457,1164780,1171078,1172538,1172694,1174784,1178401,1178762,1179014,1179015,1179045,1179082,1179107,1179142,1179419,1179444,1179670,1179671,1179672,1179673,1179711,1179713,1179714,1179715,1179716,1179722,1179723,1179724,1179745,1179810,1179888,1179895,1179896,1179960,1179963,1180027,1180029,1180031,1180052,1180086,1180117,1180258,1180506 CVE References: CVE-2020-0444,CVE-2020-0465,CVE-2020-0466,CVE-2020-27068,CVE-2020-27777,CVE-2020-27825,CVE-2020-29660,CVE-2020-29661 JIRA References: Sources used: SUSE Linux Enterprise Real Time Extension 12-SP5 (src): kernel-rt-4.12.14-10.28.3, kernel-rt_debug-4.12.14-10.28.3, kernel-source-rt-4.12.14-10.28.3, kernel-syms-rt-4.12.14-10.28.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179014] [rpm4.16] invalid use of barewords in kernel spec files
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179014 https://bugzilla.suse.com/show_bug.cgi?id=1179014#c23 --- Comment #23 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:0097-1: An update that solves 15 vulnerabilities and has 83 fixes is now available. Category: security (moderate) Bug References: 1040855,1044120,1044767,1050242,1050536,1050545,1055117,1056653,1056657,1056787,1064802,1065729,1066129,1094840,1103990,1103992,1104389,1104393,1109695,1109837,1110096,1111666,1112178,1112374,1115431,1118657,1122971,1136460,1136461,1138374,1139944,1144912,1152457,1158775,1164780,1168952,1171078,1172145,1172538,1172694,1173834,1174784,1174852,1176558,1176559,1176956,1177666,1178270,1178401,1178590,1178634,1178762,1179014,1179015,1179045,1179082,1179107,1179141,1179142,1179204,1179403,1179406,1179418,1179419,1179421,1179429,1179444,1179520,1179578,1179601,1179663,1179670,1179671,1179672,1179673,1179711,1179713,1179714,1179715,1179716,1179722,1179723,1179724,1179745,1179810,1179888,1179895,1179896,1179960,1179963,1180027,1180029,1180031,1180052,1180086,1180117,1180258,1180506 CVE References: CVE-2018-20669,CVE-2019-20934,CVE-2020-0444,CVE-2020-0465,CVE-2020-0466,CVE-2020-11668,CVE-2020-15436,CVE-2020-27068,CVE-2020-27777,CVE-2020-27786,CVE-2020-27825,CVE-2020-29371,CVE-2020-29660,CVE-2020-29661,CVE-2020-4788 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP1 (src): kernel-azure-4.12.14-8.58.1, kernel-source-azure-4.12.14-8.58.1, kernel-syms-azure-4.12.14-8.58.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179014] [rpm4.16] invalid use of barewords in kernel spec files
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179014 https://bugzilla.suse.com/show_bug.cgi?id=1179014#c22 --- Comment #22 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:0098-1: An update that solves 14 vulnerabilities and has 86 fixes is now available. Category: security (moderate) Bug References: 1040855,1044120,1044767,1050242,1050536,1050545,1055117,1056653,1056657,1056787,1064802,1065729,1066129,1094840,1103990,1103992,1104389,1104393,1109695,1109837,1110096,1111666,1112178,1112374,1114648,1115431,1118657,1122971,1136460,1136461,1138374,1139944,1152457,1158775,1164780,1171078,1172538,1172694,1174784,1174852,1176558,1176559,1176956,1177666,1178270,1178401,1178590,1178634,1178762,1179014,1179015,1179045,1179082,1179107,1179141,1179142,1179204,1179403,1179406,1179418,1179419,1179421,1179429,1179444,1179520,1179578,1179601,1179616,1179663,1179666,1179670,1179671,1179672,1179673,1179711,1179713,1179714,1179715,1179716,1179722,1179723,1179724,1179745,1179810,1179888,1179895,1179896,1179960,1179963,1180027,1180028,1180029,1180030,1180031,1180032,1180052,1180086,1180117,1180258,1180506 CVE References: CVE-2018-20669,CVE-2019-20934,CVE-2020-0444,CVE-2020-0465,CVE-2020-0466,CVE-2020-15436,CVE-2020-27068,CVE-2020-27777,CVE-2020-27786,CVE-2020-27825,CVE-2020-29371,CVE-2020-29660,CVE-2020-29661,CVE-2020-4788 JIRA References: Sources used: SUSE Linux Enterprise Server 12-SP5 (src): kernel-azure-4.12.14-16.41.1, kernel-source-azure-4.12.14-16.41.1, kernel-syms-azure-4.12.14-16.41.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c32 --- Comment #32 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Bit Juggler from comment #30) > In comment #4 i confirmed that i had the same problem as discussed in this > bug report and that the proposed solution/workaround did help me to > successfully get back to a proper functioning system. Ah, so in that case I misunderstood that comment. > So if this was just some unwanted "me-too"-story i beg to accept my apology. No, I truly apologize you. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c31 filippos Filippos <filippos(a)filippides.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #31 from filippos Filippos <filippos(a)filippides.eu> --- Thank you, it now works well with the fix in kernel 5.10.5 Happy new year without covid-19 or other malicious viruses. Special thanks to Takashi for explaining the fix, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c30 --- Comment #30 from Bit Juggler <suse.junky(a)t-online.de> --- (In reply to Jiri Slaby from comment #29) > > BUT: it would be nice if people also did a quick search for existing reports > and read them before they create/append their me-too story. The same holds > for opensuse lists (look how many reports of this very issue occurred there). > In comment #4 i confirmed that i had the same problem as discussed in this bug report and that the proposed solution/workaround did help me to successfully get back to a proper functioning system. To give all details on what i did i described as well that i did not supply the option via grub kernel command line but (as mentioned in some other link given in comment #1) via a file /etc/modprobe.d (because to me both ways deemed valid what got confirmed in comment #25). So if this was just some unwanted "me-too"-story i beg to accept my apology. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180821] New: kmod ignores /usr/lib/modprobe.d/
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180821 Bug ID: 1180821 Summary: kmod ignores /usr/lib/modprobe.d/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- this seems to break our v4l2loopback-autoload package with ==> /usr/lib/modprobe.d/98-v4l2loopback.conf <== options v4l2loopback exclusive_caps=1 card_label="OBS Virtual Camera" ==> /usr/lib/modules-load.d/v4l2loopback.conf <== v4l2loopback -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c29 --- Comment #29 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #28) > (In reply to Bit Juggler from comment #27) > > Now and then i roam the forums and occasionally get asked to file a bug > > report. Replies like comment #5 or #22 are of no avail and really > > discouraging and have stopped me from doing so a long time ago. > > > > If openSUSE developers want to use bugzilla to improve their software then > > that sort of replies does not look very promising to me. > > On the other hand, only adding me-too comments (like your comment #4), > without actually trying what was already suggested (comment #3) only makes > our lives harder. I will elaborate as I didn't mean to offend anybody. It's nice people report bugs. Look at this one, the reporter reported this one and had a workaround in 2 hours. In the next days, Takashi submitted the fix and I submitted the kernel with the fix 3 days after the initial report! BUT: it would be nice if people also did a quick search for existing reports and read them before they create/append their me-too story. The same holds for opensuse lists (look how many reports of this very issue occurred there). These should be basic principles when reporting bugs. Search first, try the suggested fixes and only if it is not found or still doesn't work, append info about a new use case. The KDE bug reporter has a nice interface which does most of this... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c28 --- Comment #28 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Bit Juggler from comment #27) > Now and then i roam the forums and occasionally get asked to file a bug > report. Replies like comment #5 or #22 are of no avail and really > discouraging and have stopped me from doing so a long time ago. > > If openSUSE developers want to use bugzilla to improve their software then > that sort of replies does not look very promising to me. On the other hand, only adding me-too comments (like your comment #4), without actually trying what was already suggested (comment #3) only makes our lives harder. Not speaking about trying what was _not_ suggested and is obviously different from what was suggested. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c27 --- Comment #27 from Bit Juggler <suse.junky(a)t-online.de> --- (In reply to Takashi Iwai from comment #25) > Please don't play pingpong. > Thank you very much for your elaborate and helpful statement! Sorry! I do not want to cause any disturbance. Now and then i roam the forums and occasionally get asked to file a bug report. Replies like comment #5 or #22 are of no avail and really discouraging and have stopped me from doing so a long time ago. If openSUSE developers want to use bugzilla to improve their software then that sort of replies does not look very promising to me. -- You are receiving this mail because: You are the assignee for the bug.

1 0