September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1041112] KDE packagekit update dialog shows still updates available for a short time after applying updates
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1041112 https://bugzilla.suse.com/show_bug.cgi?id=1041112#c87 --- Comment #87 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: install_with_updates_kde@uefi-2G https://openqa.opensuse.org/tests/1927128 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188444] [RPi3] [Firmware Bug]: Bootloader left irq enabled: bank 1 irq 9
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1188444 https://bugzilla.suse.com/show_bug.cgi?id=1188444#c5 --- Comment #5 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi3 https://openqa.opensuse.org/tests/1926577 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188224] New: iio-sensor-proxy cannot rotate screen: orientation undefined in monitor-sensor
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188224 Bug ID: 1188224 Summary: iio-sensor-proxy cannot rotate screen: orientation undefined in monitor-sensor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: herzenschein(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- iio-sensor-proxy in running installation of openSUSE Tumbleweed is running, but it is unable to rotate the screen. I noticed that monitor-sensor --accel gives the following error: Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === Has accelerometer (orientation: undefined) Whereas KDE Neon Unstable for instance shows orientation: normal, changing its orientation once I rotate my 2-in-1. output of: lsmod | grep iio hid_sensor_iio_common 20480 7 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation hid_sensor_hub 24576 9 hid_sensor_gyro_3d,hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_incl_3d,hid_sensor_als,hid_sensor_accel_3d,hid_sensor_magn_3d,hid_sensor_rotation,hid_sensor_custom This occurs on both GNOME Wayland and Plasma Wayland (tested just before installing Next and Krypton), as well as the Wayland sessions in GNOME Next and Krypton. Because of this and the output of monitor-sensor, I suspect this is not DE related. Moreover, I have tested and confirmed that this works on Fedora Rawhide, KDE Neon Unstable, Kubuntu Impish and Arch, so the issue is openSUSE specific. The only different things I did on this install was use ext4 and leave the security thing set as Easy. Not sure how I'd tell the wayland version currently in use, but wayland-devel reports 1.19.0-1.4. xorg-x11-server is at version 1.20.11-3.1 if that matters. Complete output from KInfoCenter if that helps: Operating System: openSUSE Tumbleweed 20210709 (Krypton and GNOME Next now) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-1-default (64-bit) Graphics Platform: Wayland Processors: 4 �� Intel�� Core�� i7-5500U CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel�� HD Graphics 5500 I haven't managed to try previous kernels yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1190573] New: Incompatible libraries being leaked in modinfo.c (--enable-modules)
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190573 Bug ID: 1190573 Summary: Incompatible libraries being leaked in modinfo.c (--enable-modules) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: jose.ziviani(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Beginning at QEMU v6.1.0, --enable-modules create a file modinfo.c, with information about modules available for dynamic loading. Information such as dependencies and architecture can be found in that file. During the build phase, modinfo.c is generated based in the target architecture its being build. For example, if qemu-system-s390x doesn't support hw-display-virtio-vga, that module won't be listed as available in modinfo.c. The problem happens when building multiple targets at once (for instance --target-list=s390x-softmmu,x86_64-softmmu). Because we have only one modinfo.c, modules supported by x86_64-softmmu will be list in it - even if not supported by s390x (or other architectures). It will lead to errors messages like: $ qemu-system-s390x -nodefaults -display none -accel qtest -M none -device help Failed to open module: /home/jose/qemu/build/hw-display-virtio-vga.so: undefined symbol: vmstate_vga_common In order to solve this, we need to generate one modinfo per target, for instance modinfo-s390x.c, or improve the current modinfo arch filed information. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1186256] qemu-linux-user: hardcoded binfmt handler doesn't play well with containers
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186256 http://bugzilla.opensuse.org/show_bug.cgi?id=1186256#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1186256) was mentioned in https://build.opensuse.org/request/show/920365 Factory / qemu -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190636] New: Full fan speed (25k rpm) for no good reason right after logging in
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190636 Bug ID: 1190636 Summary: Full fan speed (25k rpm) for no good reason right after logging in Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrien.glauser(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852627 --> http://bugzilla.opensuse.org/attachment.cgi?id=852627&action=edit sensors data About 10 seconds after logging (Plasma Wayland) my fans are spinning at full speed (25'500 rpm), see the logs attached to this comment. I have never seen that on that machine on any other Linux distribution or operating system (NixOS and Windows 10, same machine, have no issue whatoever). I've rolling back and forth between the 3-4 most recent Tumbleweed snapshots, to no avail. I've created a test user to reproduce, and indeed the issue occurs on the other user's session too. Model: ASUS N552VX Operating System: openSUSE Tumbleweed 20210915 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 �� Intel�� Core�� i7-6700HQ CPU @ 2.60GHz Memory: 15.5��Gio of RAM Graphics Processor: Mesa Intel�� HD Graphics 530 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1189201] java-11-openjdk fails with glibc 2.34
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189201 https://bugzilla.suse.com/show_bug.cgi?id=1189201#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- # maintenance_jira_update_notice SUSE-RU-2021:3171-1: An update that has two recommended fixes can now be installed. Category: recommended (important) Bug References: 1189201,1190252 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Server for SAP 15-SP1 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Server for SAP 15 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Server 15-SP1-LTSS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Server 15-SP1-BCL (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Server 15-LTSS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Module for Packagehub Subpackages 15-SP3 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Module for Packagehub Subpackages 15-SP2 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise High Performance Computing 15-SP1-LTSS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise High Performance Computing 15-SP1-ESPOS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise High Performance Computing 15-LTSS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Linux Enterprise High Performance Computing 15-ESPOS (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE Enterprise Storage 6 (src): java-11-openjdk-11.0.12.0-3.62.1 SUSE CaaS Platform 4.0 (src): java-11-openjdk-11.0.12.0-3.62.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 on the CC list for the bug.

1 0

[Bug 1189201] java-11-openjdk fails with glibc 2.34
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189201 https://bugzilla.suse.com/show_bug.cgi?id=1189201#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- # maintenance_jira_update_notice openSUSE-RU-2021:3171-1: An update that has two recommended fixes can now be installed. Category: recommended (important) Bug References: 1189201,1190252 CVE References: JIRA References: Sources used: openSUSE Leap 15.3 (src): java-11-openjdk-11.0.12.0-3.62.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190677] New: exiftool requires perl-File-RandomAccess
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190677 Bug ID: 1190677 Summary: exiftool requires perl-File-RandomAccess 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: peter.kiral(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installing rapid-photo-downloader pulled exiftool as well. Running exiftool generated the error below. Installing perl-File-RandomAccess solved the issue. I suggest adding perl-File-RandomAccess as dependency to exiftool. Can't locate File/RandomAccess.pm in @INC (you may need to install the File::RandomAccess module) (@INC contains: /usr/bin/lib /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.32.1 /usr/lib/perl5/vendor_perl/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.32.1 /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi /usr/lib/perl5/5.32.1 /usr/lib/perl5/site_perl) at /usr/lib/perl5/vendor_perl/5.32.1/Image/ExifTool.pm line 21. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.32.1/Image/ExifTool.pm line 21. Compilation failed in require at /usr/bin/exiftool line 37. BEGIN failed--compilation aborted at /usr/bin/exiftool line 37. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190272] Most volumes gets unmounted after boot
by bugzilla_noreply＠suse.com 20 Sep '21

20 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190272 https://bugzilla.suse.com/show_bug.cgi?id=1190272#c3 --- Comment #3 from Linus Kardell <linus.kardell(a)gmail.com> --- Maybe. There is a "systemd[1]: Reloading" shortly before it starts unmounting stuff. Your link leads back to this issue, but if you're referring to: # systemctl disable btrfsmaintenance-refresh.service # systemctl enable btrfsmaintenance-refresh.path That doesn't see to do anything, as btrfsmaintenance-refresh.service is static and btrfsmaintenance-refresh.path was already enabled. And I did indeed still get the issue when I ran those commands before rebooting. -- You are receiving this mail because: You are on the CC list for the bug.

1 0