September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1198549] Update TLP to the latest version 1.5.0
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1198549 https://bugzilla.suse.com/show_bug.cgi?id=1198549#c16 Frank Kr�ger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #16 from Frank Kr�ger <fkrueger(a)mailbox.org> --- (In reply to Maxime Cornet from comment #15) > On micro OS, uninstalling power-profile-daemon also uninstalls > patterns-microos-desktop-gnome. Is there a reason for this? Also can I > safely uninstall both if I want tlp. > By the way, I understand the rationale for the conflict, but both packages > can easily coexist on a system, as one can easily mask either the > power-profile-daemon and rfkill or the tlp systemd units. patterns-microos.spec requires power-profiles-daemon, cc'ing Fabian Vogt. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198549] Update TLP to the latest version 1.5.0
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1198549 https://bugzilla.suse.com/show_bug.cgi?id=1198549#c15 Maxime Cornet <max(a)ime.im> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |max(a)ime.im --- Comment #15 from Maxime Cornet <max(a)ime.im> --- On micro OS, uninstalling power-profile-daemon also uninstalls patterns-microos-desktop-gnome. Is there a reason for this? Also can I safely uninstall both if I want tlp. By the way, I understand the rationale for the conflict, but both packages can easily coexist on a system, as one can easily mask either the power-profile-daemon and rfkill or the tlp systemd units. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203312] New: KDE plasma session crashes when disabling monitor under wayland
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203312 Bug ID: 1203312 Summary: KDE plasma session crashes when disabling monitor under wayland Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: post+opensuse-bugzilla(a)guelker.eu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: Dear all, I have a laptop with a FHD display and an external 4k monitor. When I disable the internal laptop display and then switch workspaces, the KDE Plasma desktop session crashes so that all I see is a black screen. I am using Wayland (to have proper 4k handling). I suppose the problem is not related to the external monitor being 4k, but mine is 4k so I thought I ought to specify this. My laptop is configured to sit to the right of my external monitor, in case this is of any importance. Thanks for consideration. -quintus Reproducible: Always Steps to Reproduce: 1. Start a Wayland session with KDE Plasma. 2. Connect a 4k monitor to a laptop with a FHD screen, 3. In KDE's screen settings, disable the laptop display, 4. Switch workspace, 5. Crash. Actual Results: The KDE Plasma session crashes, i.e. I get a black screen. Expected Results: The KDE Plasma session should not crash. It is possible to "recover" from the problem by switching to a virtual console and executing $ killall plasma_session Then I can log in again, but as soon as I switch the workspace, the crash will happen again. At least however I can use this trick to get to the monitor settings and re-enable the laptop display. System information: Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.18-default (64-bit) Graphics Platform: Wayland Processors: 8 �� Intel�� Core�� i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel�� UHD Graphics 620 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203310] New: mariadb y2038 problem
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203310 Bug ID: 1203310 Summary: mariadb y2038 problem Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: pmonrealgonzalez(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: danilo.spinella(a)suse.com Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our perl-DBD-MariaDB package failed tests with > 2038-01-20 0:00:08 0 [ERROR] This server doesn't support dates later than 2038 To reproduce: osc co openSUSE:Factory/perl-DBD-MariaDB && cd $_ osc build --noservice --trust-all-projects --vm-type=kvm \ --alternative-project=home:bmwiedemann:reproducible \ --build-opt=--vm-custom-opt="-rtc base=2038-01-20T00:00:00" \ openSUSE_Tumbleweed x86_64 Background: As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future. The usual offset is +16 years, because that is how long I expect some software will be used in some places. This showed up failing tests in our package build. See https://reproducible-builds.org/ for why this matters. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1203311] New: python-softlayer / xmlrpc y2038 problem
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203311 Bug ID: 1203311 Summary: python-softlayer / xmlrpc y2038 problem Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mcepl(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our python-softlayer package failed tests in 2038 with self = <xmlrpc.client.Marshaller object at 0x7fa5770e91f0>, value = 2167459529 write = <built-in method append of list object at 0x7fa577194740> def dump_long(self, value, write): if value > MAXINT or value < MININT: > raise OverflowError("int exceeds XML-RPC limits") E OverflowError: int exceeds XML-RPC limits /usr/lib64/python3.8/xmlrpc/client.py:539: OverflowError =========================== short test summary info ============================ FAILED tests/CLI/modules/cdn_tests.py::CdnTests::test_detail_account - Overfl... FAILED tests/managers/cdn_tests.py::CDNTests::test_detail_usage_metric - Over... =========== 2 failed, 1831 passed, 6 skipped, 5 deselected in 38.01s =========== To Reproduce: osc co openSUSE:Factory/python-softlayer && cd $_ osc build --noservice --trust-all-projects --vm-type=kvm \ --alternative-project=home:bmwiedemann:reproducible \ --build-opt=--vm-custom-opt="-rtc base=2038-01-20T00:00:00" \ openSUSE_Tumbleweed x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203308] New: Astroprojection cursor after opening the steam client.
by bugzilla_noreply＠suse.com 11 Sep '22

11 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203308 Bug ID: 1203308 Summary: Astroprojection cursor after opening the steam client. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 861413 --> http://bugzilla.opensuse.org/attachment.cgi?id=861413&action=edit steam 2> steam-client.err.log Steps to reproduce. Start a wayland session on gnome. Open steam on the steam deck or steam controller. The cursor becomes invisible and can interact with UI elements. $gnome-shell --version GNOME Shell 42.4 $ lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220908 Codename: n/a I found other people who also have the same issue. https://www.reddit.com/r/gnome/comments/u3basx/using_steams_controller_desk… https://github.com/ValveSoftware/steam-for-linux/issues/6615 https://github.com/ValveSoftware/steam-for-linux/issues/4738 https://github.com/ValveSoftware/steam-for-linux/issues/8604 https://github.com/ValveSoftware/steam-for-linux/issues/4738 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1196784] expat: [>=2.4.5] Fix to CVE-2022-25236 breaks biboumi, ClairMeta, jxmlease, libwbxml, openleadr-python, rnv, xmltodict
by bugzilla_noreply＠suse.com 10 Sep '22

10 Sep '22

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

1 0

[Bug 1202788] New: scanf gives wrong results in Polish locale
by bugzilla_noreply＠suse.com 10 Sep '22

10 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202788 Bug ID: 1202788 Summary: scanf gives wrong results in Polish locale Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: giecrilj(a)stegny.2a.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following assertion fails: #include <assert.h> #include <locale.h> #include <stdio.h> #include <stdlib.h> int main () { #define NBSP "\342\200\257" auto float d; assert (! setlocale (LC_ALL, "pl_PL.UTF-8") || sscanf ("1" NBSP "0" NBSP NBSP "2", "%'f", &d) != 01 || d != 22); return EXIT_SUCCESS ; } -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1173319] Move /etc/logrotate.d/* to /usr/etc/logrotate.d
by bugzilla_noreply＠suse.com 10 Sep '22

10 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173319 http://bugzilla.opensuse.org/show_bug.cgi?id=1173319#c12 Gene Snider <genes1122(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |genes1122(a)gmail.com --- Comment #12 from Gene Snider <genes1122(a)gmail.com> --- This was implemented in logrotate-3.20.1-2.2, but now using /etc/logrotate.d/zypp-history.lr is broken. The file in /etc/logrotate.d is preserved across updates, but I get this journal error message since that update: > journalctl -p err -u logrotate.service Sep 06 00:00:02 Mobile-PC systemd[1]: Failed to start Rotate log files. -- Boot ac535881d63e4741a64e81cbb73e153a -- Sep 07 04:45:13 Mobile-PC systemd[1]: Failed to start Rotate log files. -- Boot 35f3b6fda0984c4cb85d380f76bf607e -- Sep 08 02:48:29 Mobile-PC systemd[1]: Failed to start Rotate log files. -- Boot acb8ef636b604f88bdc345ec5436fd8c -- Sep 09 07:50:22 Mobile-PC systemd[1]: Failed to start Rotate log files. -- Boot 0e96e0a1f82a47668f52ac8b4f4c9625 -- Sep 10 07:25:37 Mobile-PC systemd[1]: Failed to start Rotate log files. and > journalctl -b ac535881d63e4741a64e81cbb73e153a -u logrotate.serviceSep 07 04:45:13 Mobile-PC systemd[1]: Starting Rotate log files... Sep 07 04:45:13 Mobile-PC sh[1185]: error: zypp-history.lr:1 duplicate log entry for /var/log/zypp/hist> Sep 07 04:45:13 Mobile-PC sh[1185]: error: found error in file zypp-history.lr, skipping Sep 07 04:45:13 Mobile-PC systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAI> Sep 07 04:45:13 Mobile-PC systemd[1]: logrotate.service: Failed with result 'exit-code'. Sep 07 04:45:13 Mobile-PC systemd[1]: Failed to start Rotate log files. So this update introduced a problem when the administrator uses files in /etc/logrotate.d to over-ride package config files. Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203231] New: qpdf tests fail with GNU grep 3.8
by bugzilla_noreply＠suse.com 10 Sep '22

10 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203231 Bug ID: 1203231 Summary: qpdf tests fail with GNU grep 3.8 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: dmueller(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: schwab(a)suse.de Blocks: 1203092 Found By: --- Blocker: --- GNU grep from 3.8 emitting warnings when invoking egrep/fgrep https://build.opensuse.org/request/show/1001674 > egrep and fgrep commands, deprecated since 2007, now warn that > they are obsolescent and should be replaced by grep -E / -F From https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [ 266s] Running ../qtest/qpdf.test [ 266s] qpdf test 603 (check non-static ID version) FAILED [ 266s] cwd: /home/abuild/rpmbuild/BUILD/qpdf-10.6.3/qpdf/qtest/qpdf [ 266s] command: sh ./diff-ignore-ID-version a.pdf b.pdf [ 266s] at qpdf.test line 1725. [ 266s] --> BEGIN EXPECTED OUTPUT <-- [ 266s] okay [ 266s] --> END EXPECTED OUTPUT <-- [ 266s] --> BEGIN ACTUAL OUTPUT <-- [ 266s] egrep: warning: egrep is obsolescent; using grep -E [ 266s] egrep: warning: egrep is obsolescent; using grep -E [ 266s] egrep: warning: egrep is obsolescent; using grep -E [ 266s] okay [ 266s] --> END ACTUAL OUTPUT <-- [ 266s] --> DIFF EXPECTED ACTUAL <-- [ 266s] --- /tmp/testtemp.13811/expected 2022-09-08 02:09:09.120000000 +0000 [ 266s] +++ /tmp/testtemp.13811/actual 2022-09-08 02:09:09.120000000 +0000 [ 266s] @@ -1 +1,4 @@ [ 266s] +egrep: warning: egrep is obsolescent; using grep -E [ 266s] +egrep: warning: egrep is obsolescent; using grep -E [ 266s] +egrep: warning: egrep is obsolescent; using grep -E [ 266s] okay [ 266s] --> END DIFFERENCES <-- [ 266s] qpdf test 1851 (check against base) FAILED -- You are receiving this mail because: You are on the CC list for the bug.

1 3