November 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 1215631] New: Intuos4 tablet mouse clicks non-functional with GNOME 45
by bugzilla_noreply＠suse.com 05 Jan '24

05 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215631 Bug ID: 1215631 Summary: Intuos4 tablet mouse clicks non-functional with GNOME 45 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: hendersj(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Attempted to update my Tumbleweed installation to GNOME 45, and had the entire desktop crash multiple times. After getting extensions disabled and rebooting a few times, the desktop mostly stabilized, but attempting to use my mouse on my Intuos4 tablet was an exercise in futility. For the most part, mouse clicks were not recognized at all. I connected a bluetooth mouse, and that was recognized. On GNOME 44, the Wacom mouse works mostly fine (scroll wheel doesn't work in certain applications, but it's usable). Launching the wacom settings applet in gnome-settings caused the desktop to crash with the "Oh No, something went wrong" error message. I was able to roll back to GNOME 44, but would like to know what information would be useful to get this issue resolved so I can do a dup on the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214909] New: Konqi never closes after sending the bug report
by bugzilla_noreply＠suse.com 04 Jan '24

04 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214909 Bug ID: 1214909 Summary: Konqi never closes after sending the bug report Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- the crash application reporter "konqi" does correctly send the desired report but the windows stays eternally on "sending" with running "wheel" for ongoing progress, however when closed by hand, the report is found correctly already on kdebugs. So the program apparently works as expected but does not sense that the report has been successfully received by the bugzilla of KDE. Reproducible 100% of cases, since about 6 months. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216428] New: New Install - No NICs
by bugzilla_noreply＠suse.com 03 Jan '24

03 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216428 Bug ID: 1216428 Summary: New Install - No NICs Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Base Assignee: sfalken(a)cloverleaf-linux.org Reporter: colony.three(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just installed openSUSE-MicroOS-DVD-x86_64-Snapshot20231012-Media.iso with KDE and it booted just fine. But in NetworkMangler there were no interfaces set up. I configured one for IPV4 manual, but it -still- did not show up in the interfaces window. I rebooted, still no NIC. This is a showstopper. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216830] New: rpamd: crashes on start on aarch64
by bugzilla_noreply＠suse.com 03 Jan '24

03 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216830 Bug ID: 1216830 Summary: rpamd: crashes on start on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: asn(a)cryptomilk.org, wolfgang(a)rosenauer.org Target Milestone: --- Found By: --- Blocker: --- this basically runs `rspamd -f` with default config. It's using latest Tumbleweed container image and running on Leap Micro on aarch64 with `zypper in rspamd`. Works fine on x86_64. # podman run -it --rm localhost/rspamd:latest 2023-11-02 15:21:52 #1(main) <957c11>; main; main: rspamd 3.7.3 is loading configuration, build id: release (main) lua; lua_cfg_transform.lua:173: group excessb64 has no symbols*** stack smashing detected ***: terminated Stack trace (most recent call last): #24 Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in #23 Object "/usr/bin/rspamd", at 0xaaaacffad76f, in #22 Object "/lib64/libc.so.6", at 0xffffb06cb61f, in __libc_start_main #21 Object "/lib64/libc.so.6", at 0xffffb06cb54b, in #20 Object "/usr/bin/rspamd", at 0xaaaacffacb2b, in #19 Object "/usr/bin/rspamd", at 0xaaaacffc103b, in #18 Object "/lib64/librspamd-server.so", at 0xffffb0e3c5bf, in rspamd_config_read #17 Object "/lib64/librspamd-server.so", at 0xffffb0e35107, in rspamd_rcl_maybe_apply_lua_transform #16 Object "/lib64/liblua5.4.so.5", at 0xffffb0c9431f, in lua_pcallk #15 Object "/lib64/liblua5.4.so.5", at 0xffffb0cb2697, in #14 Object "/lib64/liblua5.4.so.5", at 0xffffb0c8e107, in #13 Object "/lib64/liblua5.4.so.5", at 0xffffb0c941f3, in #12 Object "/lib64/liblua5.4.so.5", at 0xffffb0ca0d1b, in #11 Object "/lib64/liblua5.4.so.5", at 0xffffb0c93713, in #10 Object "/lib64/librspamd-server.so", at 0xffffb0fe0863, in #9 Object "/lib64/librspamd-server.so", at 0xffffb0f23553, in #8 Object "/lib64/librspamd-server.so", at 0xffffb0e8c74b, in rspamd_common_log_function #7 Object "/lib64/librspamd-server.so", at 0xffffb0e8c553, in rspamd_common_logv #6 Object "/lib64/librspamd-server.so", at 0xffffb0e8f93b, in rspamd_log_console_log #5 Object "/lib64/libc.so.6", at 0xffffb07a77b7, in __stack_chk_fail #4 Object "/lib64/libc.so.6", at 0xffffb07a676f, in __fortify_fail #3 Object "/lib64/libc.so.6", at 0xffffb071e84b, in #2 Object "/lib64/libc.so.6", at 0xffffb06cae07, in abort #1 Object "/lib64/libc.so.6", at 0xffffb06dfbff, in raise #0 Object "/lib64/libc.so.6", at 0xffffb072b430, in Aborted (Signal sent by tkill() 1 498) watf? exit could be related to this, https://github.com/rspamd/rspamd/issues/3849 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215842] New: EOG could use AVIF and WEBP support urgently
by bugzilla_noreply＠suse.com 01 Jan '24

01 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215842 Bug ID: 1215842 Summary: EOG could use AVIF and WEBP support urgently Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Gnome's Image Viewer EOG could use AVIF and WEBP image support a lot, I encounter these formats so often online but when I download the image I can't even look at it. I think some future version of EOG at least can do WEBP, maybe this can be backported? It really isn't that practical that a generic image viewer can't open half the images that actually circulate on the web, so I hope there's a chance this can be looked into. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214394] New: Bluetooth toggle being grayed out on lock screen leaves me stranded regularly
by bugzilla_noreply＠suse.com 01 Jan '24

01 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214394 Bug ID: 1214394 Summary: Bluetooth toggle being grayed out on lock screen leaves me stranded regularly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Bluetooth is sadly quite unreliable on Linux, I've never found it to be otherwise, so sometimes I just need to turn it off and turn it back on to make my bluetooth keyboard reconnect. For that I use the wired mouse. But now switching from something else to OpenSUSE, suddenly the bluetooth toggle on the lock screen is grayed out. Since you apparently want me to login to use it, but that would require me to toggle bluetooth, that leaves me stuck. I think the obvious fix would be to not gray out such toggles on the lock screen. I'm picking severity major since it leaves me unable to lock back in multiple days per week which is really stopping me in my tracks and there isn't really a workaround that I've found. (Other than finding a wired keyboard, so with the input devices I previously used that worked fine for me I simply can't proceed.) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214135] New: Installed opensuse-repos -- Now, zypper dup Tries To Add Repo That Exists
by bugzilla_noreply＠suse.com 26 Dec '23

26 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1214135 Bug ID: 1214135 Summary: Installed opensuse-repos -- Now, zypper dup Tries To Add Repo That Exists Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868728 --> https://bugzilla.suse.com/attachment.cgi?id=868728&action=edit zypper.log Yesterday, I installed the openSUSE-repos-Tumbleweed-20230804.41e41a9-1.1.x86_64 package. Today, zypper dist-upgrade results in the following output (also attached as file_: rocky:~ # /usr/bin/zypper dist-upgrade Refreshing service 'openSUSE'. Adding repository 'repo-oss' ..........................................................................[error] Unexpected exception. [openSUSE:repo-oss|http://cdn.opensuse.org/tumbleweed//repo/oss] Repository already exists. Please file a bug report about this. See http://en.opensuse.org/Zypper/Troubleshooting for instructions. rocky:~ # I get this same result with every run of zypper dup. Per the request, I file this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1217615] New: VUL-0: libavif,chromium,ungoogled-chromium: use-after-free in colorProperties
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217615 Bug ID: 1217615 Summary: VUL-0: libavif,chromium,ungoogled-chromium: use-after-free in colorProperties Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: asn(a)cryptomilk.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: gmbr3(a)opensuse.org, m.szczepaniak.000(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- A use-after free issue was reported in libavif (bundled in Chromium). CVE-2023-6351 was assigned to this issue. Apparent fix: https://github.com/AOMediaCodec/libavif/commit/456f78a3b2d3eacb8ca4193b7912… SUSE:SLE-15-SP4:Update/libavif has 0.9.3 Chromium builds with the bundled libavif and needs a fix. References: https://crbug.com/1501770 https://github.com/AOMediaCodec/libavif/pull/1757 https://chromereleases.googleblog.com/2023/11/stable-channel-update-for-des… https://github.com/AOMediaCodec/libavif/releases/tag/v1.0.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[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