January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199319] can not build packages for Mageia 8 locally
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1199319 https://bugzilla.suse.com/show_bug.cgi?id=1199319#c4 hui <sturm-fr(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from hui <sturm-fr(a)web.de> --- All mentioned operating systems are EOL: Debian 11 Fedora 36 Mageia 8 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c21 Urvi Monty <software_suseidp(a)orcadian.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |software_suseidp(a)orcadian.n | |et Resolution|FIXED |--- --- Comment #21 from Urvi Monty <software_suseidp(a)orcadian.net> --- This appears to be broken again as of kernel-default-6.7.1-1.1.aarch64 The wsa883x module is not present at all. Audio is no longer working. ls /usr/lib/modules 6.6.11-1-default 6.7.1-1-default find /usr/lib/modules -name *wsa883* /usr/lib/modules/6.6.11-1-default/kernel/sound/soc/codecs/snd-soc-wsa883x.ko.zst -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217492] KVM vm client can no longer use a USB pass through device
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217492 https://bugzilla.suse.com/show_bug.cgi?id=1217492#c9 --- Comment #9 from Lin Ma <lma(a)suse.com> --- (In reply to P from comment #7) > Created attachment 872230 [details] > VM configuration using Conbee II as a USB device. Could you please help to capture the trace data and upload it? 1. Make sure the vm USB_Test is off. 2. On host, issues below commands as a priviledged user: lsusb -t virsh start USB_Test --paused virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_claim_interface on" virsh resume USB_Test lsusb -t Then upload the outputs of the two lsusb commands and the /var/log/libvirt/qemu/USB_Test.log TIA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211571] nmap non-OSI approved "Nmap Public Source License" NPSL
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1211571 https://bugzilla.suse.com/show_bug.cgi?id=1211571#c11 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #11 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- $ zypper search -t package -s --match-exact nmap Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------+---------+----------+--------+---------------------------- i+ | nmap | package | 7.94-2.1 | x86_64 | openSUSE-Tumbleweed-Non-Oss $ rpm -q --queryformat "%{LICENSE}\n" nmap SUSE-NonFree -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218808] bcachefs-tools: some systemd services use non-existing exec paths
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

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

1 0

[Bug 1217492] KVM vm client can no longer use a USB pass through device
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217492 https://bugzilla.suse.com/show_bug.cgi?id=1217492#c8 --- Comment #8 from P <opensuse(a)pohw.nl> --- There are some related posts which you might find interesting. The cross-section here is the relation with a Conbee II: search://"conbee" libusb did not claim interface 0 before use -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218288] New: liblxqt needed for brightness control, not installed by default
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218288 Bug ID: 1218288 Summary: liblxqt needed for brightness control, not installed by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: bog(a)khumba.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi there, I have a basic Tumbleweed install and selected LXQt in the installer. There is a display brightness control that can be added to the LXQt panel, however attempting to drag its slider results in the whole panel crashing (and restarting) with an error in .xsession-errors: > Cannot run program lxqt-backlight_backend: No such file or directory This program is part of the liblxqt binary package, great, so it should be installed by default, but I can't see why it's not. Information for package liblxqt1: (installed) --------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : liblxqt1 Version : 1.4.0-1.1 Recommends : [2] liblxqt-lang liblxqt >= 1.4.0 Provides : [4] liblxqt.so.1()(64bit) liblxqt liblxqt1 = 1.4.0-1.1 liblxqt1(x86-64) = 1.4.0-1.1 Information for package liblxqt: (not installed) -------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : liblxqt Version : 1.4.0-1.1 Provides : [3] liblxqt = 1.4.0-1.1 liblxqt(x86-64) = 1.4.0-1.1 liblxqt-qt5 = 1.4.0 I would expect the 'liblxqt >= 1.4.0' Recommends from liblxqt1 not to match the package's own unversioned 'liblxqt' Provides and instead pull in the proper liblxqt package, but that's not what's happening. What am I not understanding here? 'zypper inr' doesn't try to install liblxqt either. The workaround is to install liblxqt manually of course :). -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214420] New: [LXQt]compton-conf / picom
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214420 Bug ID: 1214420 Summary: [LXQt]compton-conf / picom Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: psi089(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Problem: After installation picom did not start because it lacked a config file. lxqt-config starts compton-conf which writes to .config/compton.conf but picom is used as compositor and expects to read from .config/picom.conf Further: on manual startup picom complains about deprecated config entries that got written by the currently used tool. What is the solution? For now I just softlinked picom.conf to compton.conf, but it looks like some clean fix is needed and to make it work out of the box. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1179897] Setting KBD_DISABLE_CAPS_LOCK="yes" gives error in boot sequence
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1179897 https://bugzilla.suse.com/show_bug.cgi?id=1179897#c1 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #1 from Stanislav Brabec <sbrabec(a)suse.com> --- This is a problem in the way how it works: Even the command: /usr/bin/dumpkeys | /usr/bin/loadkeys -q - fails with unable to load compose definitions because some of them are too large I am afraid that it is not fixable. As this is broken for years, and nobody else complies, I propose a radical solution: Remove KBD_DISABLE_CAPS_LOCK feature completely. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216604] [Build 20231025] graphicsMagick: config file references ghostscript fonts - but does not trigger installation
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216604 https://bugzilla.suse.com/show_bug.cgi?id=1216604#c5 --- Comment #5 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- (In reply to Petr Gajdos from comment #3) > Hello Stefan, > > in case ghostscript-fonts-std is not installed: > > $ gm convert -fill red -draw 'text 0,20 "TEST"' black.png output.png > gm convert: Unable to read font (/usr/share/ghostscript/fonts/n019003l.pfb). > $ > > It seems that, with current config, the font file above is required, even if > not in all usages, yes. I think "not in all usages" is putting more weight after it than actually true. The ghostscript font is required if and only if you want to impose a text stamp. For *all other* usages, format conversion, scaling, composing, etc, the fonts are *not* necessary. Thus my recommendation to just "recommend" the fonts, without a hard dependency. > Is there a way to do config such that we would get rid of ghostscript fonts > entirely? Will try to figure out, in case anyone see that immediately. Maybe its sufficient to add a matching config, but not sure. -- You are receiving this mail because: You are on the CC list for the bug.

1 0