July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 17 Jan '24

17 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213477] New: Update to gutenprint 5.3 broke cups config
by bugzilla_noreply＠suse.com 05 Jan '24

05 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1213477 Bug ID: 1213477 Summary: Update to gutenprint 5.3 broke cups config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: dheidler(a)suse.com QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- From cups log: E [19/Jul/2023:14:07:42 +0200] Samsung_Samsung_ML-2525W: Datei \"/usr/lib/cups/filter/rastertogutenprint.5.2\" nicht verfügbar: No such file or directory E [19/Jul/2023:14:07:42 +0200] [Job 49] Unable to start filter "rastertogutenprint.5.2" - No such file or directory. E [19/Jul/2023:14:07:42 +0200] [Job 49] Stopping job because the scheduler could not execute a filter. From cups config: <Printer Samsung_Samsung_ML-2525W> PrinterId 45 UUID urn:uuid:70334a01-d800-39ed-5a4e-5e4f45e9c01f Info Samsung Samsung ML-2525W Location MakeModel Samsung ML-2550 - CUPS+Gutenprint v5.2.15 DeviceURI socket://10.131.0.20 State Idle StateTime 1689768462 ConfigTime 1689767864 Type 8392724 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#000000 Attribute marker-levels 50 Attribute marker-names Toner S/N:CRUM-11000311613 Attribute marker-types toner Attribute marker-change-time 1683056782 </Printer> It seems that the config was not updated breaking the printing driver as the config was still pointing to gutenprint 5.2. This should be somehow prevented - eg by not including the version number in the config or updating the config automatically. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213152] New: noto sans display gets mismatched for regular noto sans and noto serif has not properly matched styles
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213152 Bug ID: 1213152 Summary: noto sans display gets mismatched for regular noto sans and noto serif has not properly matched styles Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868101 --> https://bugzilla.suse.com/attachment.cgi?id=868101&action=edit I think the family property should only be Noto Sans Display and Noto Serif Display for the display versions of the fonts Hello, I noticed that in mpv after changing my default preferences for system sans-serif font I get Noto Sans Display, even though I've set it to normal Noto Sans. When I go to the kde font viewer there is only the Noto Sans font family, but there is no Noto Sans Display. With Noto Serif there is Noto Serif Display, but there are only italic versions of the font. My guess is that the display versions of the fonts shouldn't be in the normal Noto Sans/Noto Serif families. They should be a different family named Noto Sans Display/Noto Serif Display. The Noto Serif Display is a different family in the kde font viewer, but comparing the output of fc-match -a "Noto Serif" and fc-match -a "Noto Sans" gives something interesting: the display versions of the fonts belong to the normal noto font families, so when I want it to match "Noto Sans" I get the one that is alphabetically the first one (will give output in attachment). The serif one gets matched with the regular one first as the names of the noto serif display and noto sans display fonts are without and with a hyphen between the display in the font file name (alphabetically first is "-", "D" is after). The terminal output shows what is going on with the families. Thanks for any help -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1213830] New: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213830 Bug ID: 1213830 Summary: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213217] New: ceph: fails to build against fmt 10.0
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213217 Bug ID: 1213217 Summary: ceph: fails to build against fmt 10.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ceph-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868147 --> https://bugzilla.suse.com/attachment.cgi?id=868147&action=edit ceph ftbs with fmt 10 fmt 10.0 has been submitted for inclusion into Factory. During the staging process we have observed ceph failing to build, I'm attaching the full log. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213177] New: Libreoffice FTBFS with GCC13 update (13.1.1+git7489)
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213177 Bug ID: 1213177 Summary: Libreoffice FTBFS with GCC13 update (13.1.1+git7489) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868120 --> https://bugzilla.suse.com/attachment.cgi?id=868120&action=edit Libreoffice x86_64 build log Libreoffice fails to build with an update of GCC13 to 13.1.1+git7489. Please see the attached log. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213492] New: python3-podman-compose.rpm bring 247 packages uneeded
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213492 Bug ID: 1213492 Summary: python3-podman-compose.rpm bring 247 packages uneeded Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, Today was installing python3-podman-compose, but when do the install the rpm bring 551.7 MB of packages a total of 247 packages. i thinks is anormal this behavior. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213351] New: python-lxml contains non-free file (RNG scheme for ISO Schematron)
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213351 Bug ID: 1213351 Summary: python-lxml contains non-free file (RNG scheme for ISO Schematron) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Red Hat lawyers concluded (https://gitlab.com/fedora/legal/fedora-license-data/-/issues/154) that the license included in https://github.com/lxml/lxml/blob/master/src/lxml/isoschematron/resources/r… is confusing, misworded, and most likely non-Free (distribute-only-for-gratis problem). They started to remove the schema file from their project (e.g., https://src.fedoraproject.org/rpms/python-lxml/c/9d95f5a04edc386313fa854541…). This issue has been reported upstream as https://bugs.launchpad.net/lxml/+bug/2024343 and they created patch which allows the test suite to pass even without RNG file in the question. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1212839] New: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212839 Bug ID: 1212839 Summary: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP test cve-2021-22555 setsockopt08.c fails with ENOENT [1], but it expects EINVAL on mostly all archs on Tumbleweed (all but s390x, i.e. aarch64, ppc64le, x86_64 and x86_64 compiled as 32bit). The test has been failing for very long time (our history goes to 6.3.2 20230517, but it's failing on my VM with 6.2.12-1-default 20230502). When test run more times (200x with -i200 [3]) it fails only on first time, the rest happily have EINVAL. And indeed, when verifying manually on VM, only first run fails dmesg on affected archs contains: [ 1514.789118][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.792200][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.795209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.798209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.801190][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.804092][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.807159][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.810210][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.813257][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.816227][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 But when running manually I see on first (failing): [ 208.455124] bpfilter: Loaded bpfilter_umh pid 1223 [ 208.456650] Started bpfilter (this is also in openQA jobs, but earlier, triggered by setsockopt03.c, which runs earlier). And x_tables run is reported on later (successful run): [ 221.292549] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 => Maybe there is a problem with loading x_tables on these 3 archs Interestingly x_tables is loaded on all archs, including s390x (which does not fail) and the same dmesg [4] FYI we stop and disable firewall in openQA install_ltp job (this qcow is then used for LTP tests) [5]: systemctl --no-pager disable firewalld Removed "/etc/systemd/system/multi-user.target.wants/firewalld.service". Removed "/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service". systemctl --no-pager stop firewalld [1] https://openqa.opensuse.org/tests/3390125#step/setsockopt08/7 [2] https://github.com/linux-test-project/ltp/blob/a564d3e1672e9cd7ac302d597ffa… [3] https://openqa.opensuse.org/tests/3391862#step/cve-2021-22555/7 [4] https://openqa.opensuse.org/tests/3380876/file/shutdown_ltp-dmesg.txt [5] https://openqa.opensuse.org/tests/3391842/file/serial_terminal.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1212970] New: [JeOS] systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit status 71.
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212970 Bug ID: 1212970 Summary: [JeOS] systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit status 71. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3403981/modules/jour nal_check/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: antonio.teixeira(a)suse.com, dmueller(a)suse.com, fvogt(a)suse.com Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 867964 --> https://bugzilla.suse.com/attachment.cgi?id=867964&action=edit main packages changes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD20G fails in [journal_check](https://openqa.opensuse.org/tests/3403981/modules/journal_ch… openQA found erros in journal on aarch64 JeOS images (only): localhost systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit status 71. localhost systemd-vconsole-setup[169]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version localhost systemd-vconsole-setup[165]: Setting fonts failed with a "system error", ignoring. The list of main changes would point to kbd update: https://build.opensuse.org/request/show/1096363 ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20230503](https://openqa.opensuse.org/tests/3264760) ## Expected result Last good: [20230502](https://openqa.opensuse.org/tests/3260397) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 1