September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189033] New: config: re-modularize CRYPTO_{GCM,GHASH,GF128MUL}
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189033 Bug ID: 1189033 Summary: config: re-modularize CRYPTO_{GCM,GHASH,GF128MUL} Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- These modules were set as built-in as a result of a Kconfig change that forced them rather than an explicit choice. In 4.14-rc3: BIG_KEYS [=y] && KEYS [=y] && TMPFS [=y] - BIG_KEYS=y selected CRYPTO_GCM=y - CRYPTO_GHASH=y selected by CRYPTO_GCM=y - CONFIG_CRYPTO_GF128MUL=y selected by CRYPTO_GHASH=y A rework in 5.8-rc1 removed that select so that CRYPTO_GCM can be a module. Once CRYPTO_GCM is a module again, the others can as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1189032] New: config: re-modularize ext4
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189032 Bug ID: 1189032 Summary: config: re-modularize ext4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jeffm(a)suse.com Reporter: jeffm(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As part of Greg KH and Kay Siever's "boot faster" project, many config options were set to =y to avoid the module loading/linking overhead at boot time. As system defaults change over time, those choices need to be revisited. commit bad9377ef98ec626bb46a3d791f5295017978341 Author: Greg Kroah-Hartman <gregkh(a)suse.de> Date: Fri Apr 24 09:23:34 2009 -0700 - Update config files. change to CONFIG_EXT2_FS=y and CONFIG_EXT3_FS=y --- Set EXT2/EXT3 to be builtins. commit 2601b15ce15ba8438bec61c7276cd01dbd2f4dc1 Author: Jan Kara <jack(a)suse.cz> Date: Sat Apr 16 00:31:11 2011 +0200 - Disable ext2, use ext4 instead as a driver - Update config files. -- Replaced the separate ext2 and ext3 drivers with the ext4 module. Since ext2/3 were built-in, ext4 was changed to be built-in. The default root file system for SLES and openSUSE has been btrfs for many years. There is little benefit in building ext4 into the kernel anymore. This report serves as an anchor for the following changes: CONFIG_EXT4_FS=y->m CONFIG_JBD2=y->m CONFIG_FS_MBCACHE=y->m CONFIG_FS_ENCRYPTION_ALGS=m->y CONFIG_CRC16=y->m It is likely that the crypto modules can be modularized too but that requires FS_ENCRYPTION be modular and that will be a separate report. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190235] umip: remember that you printed the warning and only print it once
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190235 https://bugzilla.suse.com/show_bug.cgi?id=1190235#c4 --- Comment #4 from Borislav Petkov <bpetkov(a)suse.com> --- Ok, I can't read. It says /* Bursts of 5 messages every two minutes */ static DEFINE_RATELIMIT_STATE(ratelimit, 2 * 60 * HZ, 5); so it is actually every *two* minutes. So it works as advertized (timestampss are every 2 minutes). So, the thing I'm thinking about is adding a "umip=quiet" which you supply at the kernel cmdline and no more output. How's that? [ 115.100225] umip: sidt[2578] ip:55a8f9ecf083 sp:7ffcd9824480: SIDT instruction cannot be used by applications. [ 115.101088] umip: sidt[2578] ip:55a8f9ecf083 sp:7ffcd9824480: For now, expensive software emulation returns the result. [ 117.020143] umip: sidt[2580] ip:560d91114083 sp:7fff5851a7e0: SIDT instruction cannot be used by applications. [ 117.021026] umip: sidt[2580] ip:560d91114083 sp:7fff5851a7e0: For now, expensive software emulation returns the result. [ 117.532120] umip: sidt[2582] ip:55791bacf083 sp:7ffcab72a7b0: SIDT instruction cannot be used by applications. [ 235.100938] umip_printk: 252529 callbacks suppressed [ 235.100940] umip: sidt[31772] ip:557e4bdd1083 sp:7ffd62327520: SIDT instruction cannot be used by applications. [ 235.102641] umip: sidt[31772] ip:557e4bdd1083 sp:7ffd62327520: For now, expensive software emulation returns the result. [ 235.104214] umip: sidt[31773] ip:55b4f9a39083 sp:7fffe26616b0: SIDT instruction cannot be used by applications. [ 235.105075] umip: sidt[31773] ip:55b4f9a39083 sp:7fffe26616b0: For now, expensive software emulation returns the result. [ 235.106700] umip: sidt[31774] ip:555eff064083 sp:7ffec0fa7890: SIDT instruction cannot be used by applications. [ 355.104933] umip_printk: 397903 callbacks suppressed [ 355.104935] umip: sidt[4081] ip:55a1e12ea083 sp:7ffd1c9e9db0: SIDT instruction cannot be used by applications. [ 355.106654] umip: sidt[4081] ip:55a1e12ea083 sp:7ffd1c9e9db0: For now, expensive software emulation returns the result. [ 355.108232] umip: sidt[4082] ip:5572e28ae083 sp:7ffd515477f0: SIDT instruction cannot be used by applications. [ 355.109120] umip: sidt[4082] ip:5572e28ae083 sp:7ffd515477f0: For now, expensive software emulation returns the result. [ 355.110728] umip: sidt[4083] ip:55bfbcb64083 sp:7ffd16a2d350: SIDT instruction cannot be used by applications. [ 475.108935] umip_printk: 397107 callbacks suppressed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190264] New: URL to user manual of Pinta shown in Discover is outdated
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190264 Bug ID: 1190264 Summary: URL to user manual of Pinta shown in Discover is outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bugs(a)caralluin.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Discover shows a link to the user manual of Pinta, which points to https://pinta-project.com/pintaproject/pinta/howto, but the documentation has been moved to https://www.pinta-project.com/howto. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189773] Keyboard / Mouse do not work when connected through MT VIKI Auto USB KVM Switch
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189773 https://bugzilla.suse.com/show_bug.cgi?id=1189773#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Thomas Vatter from comment #16) > (In reply to Takashi Iwai from comment #15) > > If you switch back again from the graphics desktop to the text mode (e.g. > > plug another or re-plug the keyboard directly to the USB d or re-plug the > > same one to the USB port directly (without KVM), does it start working? > > > > The dmesg shows that the device have been recognized, at least. > > No, it doesn't. Hm, then you need to clarify which dmesg lines belong to which timing. I interpreted the lines about logitech things as the hotplugged events with KVM, but maybe it wasn't. That is, please identify whether the USB hotplug events get triggered by re-plugging to KVM. e.g. run "dmesg -w" on a terminal, then unplug the keyboard, and re-plug over the KVM. Which events are logged at which timing? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189823] New: ALSA: confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.3.pcm.front.0:CARD=3
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189823 Bug ID: 1189823 Summary: ALSA: confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.3.pcm.front.0:CARD=3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with snapshot 20210823 I get ... pipewire[2661]: ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.3.pcm.front.0:CARD=3' pipewire[2661]: ALSA lib conf.c:5114:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory pipewire[2661]: ALSA lib conf.c:5602:(snd_config_expand) Evaluate error: No such file or directory pipewire[2661]: ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM front:3 pipewire[2661]: 'front:3': playback open failed: No such file or directory pipewire[2661]: adapter 0x561f28c4f400: can't get format: No such file or directory pipewire[2661]: usage: node.name=<string> pipewire-media-session[2662]: error id:87 seq:8252 res:-22 (Invalid argument): usage: node.name=<string> ... and my Plantronics headset does not work completely, i.e. mute and volume buttons don't work any more. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1189733] Screen flickers and network disconnects when on battery power on Samsung Chromebook3
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189733 https://bugzilla.suse.com/show_bug.cgi?id=1189733#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Could you get the output with drm.debug=0x1e boot option? This will give lots of debug messages from the graphics driver. But in anyway, please check the behavior with 5.14.x kernel. The situation might be changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190210] nvidia: PCI ID Supplements no longer available on Tumbleweed
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190210 http://bugzilla.opensuse.org/show_bug.cgi?id=1190210#c10 --- Comment #10 from Hans-Peter Jansen <hpj(a)urpla.net> --- Given, this issue boils down to a changed naming convention during the call of __kmp_supplements, where the kernel version is deliberately appended to the file argument (eg. something like _k5.14.1_1, see https://build.opensuse.org/package/view_file/X11:Drivers:Video/nvidia-gfxG0…) This is kind of a regression between rpm 4.14 and 4.16 as being hard to comprehend and deal with in the rare cases, a build would need to define such things itself. I'm assigning this to rpm now. Michal, could you come up with an explanation at least, why this was changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189596] iwlwifi: BUG: kernel NULL pointer dereference, address: 0000000000000000
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189596 https://bugzilla.suse.com/show_bug.cgi?id=1189596#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(vicente.bolea@gma | |il.com) | --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- The "official" package is in update repo, i.e. http://download.opensuse.org/update/leap/15.3/sle/x86_64/ It's in sle/* because Leap 15.3 is composed with multiple layers, and the kernel is derived from SLE15-Sp3. As you mentioned that the bug is no longer reproducible with the latest kernel, I close the entry for now. Feel free to reopen if it's reproduced again (hopefully reliably). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190245] New: AutoYast rules and classes match against range does not work
by bugzilla_noreply＠suse.com 07 Sep '21

07 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190245 Bug ID: 1190245 Summary: AutoYast rules and classes match against range does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: rainer.konig(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852337 --> https://bugzilla.suse.com/attachment.cgi?id=852337&action=edit YaST2 log from failed attempt Trying out AutoYast Rules & Classes as it is described here: https://documentation.suse.com/sles/15-SP3/html/SLES-all/rulesandclass.html The rules.xml file looks like this: <?xml version="1.0" encoding="UTF-8"?> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <disksize> <match>/dev/sda 19000</match> <match_type>greater</match_type> </disksize> <result> <profile>profile_a.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> <rule> <disksize> <match>/dev/vda 10000-19000</match> <match_type>range</match_type> </disksize> <result> <profile>profile_b.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> Trying to install on KVM with boot param "autoyast=http://myserver/rule-based_example/". AutoYast shows a dialog box that says "no profile found at this location". it Looking at my local apache log I see, that it receives the rules/rules.xml, but then switches to defaults: 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/rules/rules.xml HTTP/1.1" 200 732 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A80046 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A8004 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A800 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A80 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A8 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0A HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C0 HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/C HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/52540095067E HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/52540095067e HTTP/1.1" 404 984 "-" "-" 192.168.0.70 - - [07/Sep/2021:09:45:21 +0200] "GET /rule-based_example/default HTTP/1.1" 404 984 "-" "-" Looking at the YaST-Log (see attachment) I see that the range match seems to work, but then I see a shell syntax error that probably causes AutoYast to switch to the default rules (as seen in the Apache access.log). 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(block (2 levels) in Read):463 Rule: disksize 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(block (2 levels) in Read):464 Ruledef: $["match":"/dev/vda 10000-49000", "match_type":"range"] 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(block (2 levels) in Read):463 Rule: result 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(block (2 levels) in Read):464 Ruledef: $["continue":false, "profile":"profile_b.xml"] 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(SubVars):406 file: profile_b.xml 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(SubVars):415 var: 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(SubVars):425 val: profile_b.xml 2021-09-07 03:45:17 <3> install(4435) [bash] ShellCommand.cc(shellcommand):78 sh: -c: line 3: syntax error near unexpected token `)' 2021-09-07 03:45:17 <3> install(4435) [bash] ShellCommand.cc(shellcommand):78 sh: -c: line 3: `if ( ) ; then exit 0; else exit 1; fi' 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(verifyrules):400 Bash return: if ( ) ; then exit 0; else exit 1; fi ($["exit":2, "stderr":"sh: -c: line 3: syntax error near unexpected token `)'\nsh: -c: line 3: `if ( ) ; then exit 0; else exit 1; fi'\n", "stdout":""]) ($["disksize_device0":"/dev/vda", "disksize_size0":40960]) 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(Read):640 element2file=$[] 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(GetRules):815 Getting Rules: [] 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/AutoInstallRules.rb(GetRules):858 No files from rules found 2021-09-07 03:45:17 <1> install(4435) [Ruby] modules/ProfileLocation.rb(Process):251 Creating default Rules Changing the rules.xml to <disksize> <match>/dev/vda 10000</match> <match_type>greater</match_type> </disksize> makes the AutoYast installation work. So the conclusion is that matching against a size range is broken because of that syntax error in the shell skript that is invoked. -- You are receiving this mail because: You are on the CC list for the bug.

1 3