August 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213028] New: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213028 Bug ID: 1213028 Summary: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- On building mingw32-qt6-imageformat for MinGW it turned out that the mentioned package does not have pkgconfig support ~/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats> osc build openSUSE_Leap_15.5 -j12 Building mingw32-qt6-imageformats.spec for openSUSE_Leap_15.5/x86_64 Getting buildconfig from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildconfig-openSUSE_Leap_15.5-x86_64 Getting buildinfo from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildinfo-openSUSE_Leap_15.5-x86_64.xml buildinfo is broken... it says: unresolvable: nothing provides mingw32(pkg:libmng) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214073] New: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214073 Bug ID: 1214073 Summary: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868684 --> https://bugzilla.suse.com/attachment.cgi?id=868684&action=edit photo of screen when system frozen As the system frozen and I am in hurry, I could only take photo of screen. It says "ACPI: _SB_.PCIB. IXUE. IGPU: failed to evaluate _DSM" on the last line which was said to be a harmless effect of nvidia chipset. I am using nouveau drivers (built into kernel) and the system is macbook 5,1 I don't want to flood here with needless data, I can provide everything needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1213384] New: Jul-2023 update of windows 10/11 breaks trust relationship
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213384 Bug ID: 1213384 Summary: Jul-2023 update of windows 10/11 breaks trust relationship Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: nopower(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Target Milestone: --- Found By: --- Blocker: --- Reports of users getting errors like "The trust relationship between this workstation and the primary domain failed." have been reported upstream since applying updates KB5028166 / KB5028185. this at least affects samba domain controllers (AD & PDC I believe) it also apparently can affect rdp access. upstream bug https://bugzilla.samba.org/show_bug.cgi?id=15418 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1214133] New: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes
by bugzilla_noreply＠suse.com 25 Feb '24

25 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214133 Bug ID: 1214133 Summary: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes 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: hofmann(a)shiphrah.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868726 --> https://bugzilla.suse.com/attachment.cgi?id=868726&action=edit dmesg on TW 20230808 After update to Tumbleweed 20230808 bluetooth is disabled and can not be enabled again. dmesg | grep luetooth (on TW 20230806) [ 6.098671] Bluetooth: Core ver 2.22 [ 6.098681] Bluetooth: HCI device and connection manager initialized [ 6.098683] Bluetooth: HCI socket layer initialized [ 6.098684] Bluetooth: L2CAP socket layer initialized [ 6.098685] Bluetooth: SCO socket layer initialized [ 26.836464] Bluetooth: hci0: Device setup in 20228164 usecs [ 26.836469] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 27.115864] Bluetooth: hci0: AOSP extensions version v1.00 [ 27.115870] Bluetooth: hci0: AOSP quality report is supported dmesg | grep luetooth (on TW 20230808) [ 4.355787] Bluetooth: Core ver 2.22 [ 4.355794] Bluetooth: HCI device and connection manager initialized [ 4.355797] Bluetooth: HCI socket layer initialized [ 4.355798] Bluetooth: L2CAP socket layer initialized [ 4.355799] Bluetooth: SCO socket layer initialized [ 4.368031] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 4.368034] Bluetooth: hci0: Failed to load firmware file (-2) [ 4.368045] Bluetooth: hci0: Failed to set up firmware (-2) [ 4.368053] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 4.438485] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.438487] Bluetooth: BNEP filters: protocol multicast [ 4.438489] Bluetooth: BNEP socket layer initialized unfortunately I can not say if it was working in TW 20230807 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213353] New: bash crash during autocompletion: systemctmalloc_consolidate(): unaligned fastbin chunk detected
by bugzilla_noreply＠suse.com 23 Feb '24

23 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213353 Bug ID: 1213353 Summary: bash crash during autocompletion: systemctmalloc_consolidate(): unaligned fastbin chunk detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: werner(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868226 --> https://bugzilla.suse.com/attachment.cgi?id=868226&action=edit bash screendump and coredumpctl output with intact linebreaks I just had the following bash crash during autocompletion: Unfortunately I don't remember exactly what I did when bash crashed. The only hint that I can offer is that my prompt starts with $? if it's non-zero. The last propmt line indicates that $? was [INT] ====================================================================== cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl enable -- --after --defaults --firmware-setup --help --legend=no --no-ask-password --now --plain --recursive --show-types --timestamp --version --all --dry-run --force --host --lines --no-block --no-wall --preset-mode --reverse --signal --type --wait --before --fail --full --job-mode --machine --no-pager --no-warn --property --root --state --user --check-inhibitors --failed --global --kill-whom --message --no-reload --output --quiet --runtime --system --value cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl enable --no --no-ask-password --no-block --no-pager --no-reload --now --no-wall --no-warn cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl e [INT] cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctmalloc_consolidate(): unaligned fastbin chunk detected Achtung: Das Programm „/bin/bash“ ist abgestürzt. ====================================================================== ====================================================================== # coredumpctl dump bash PID: 13069 (bash) UID: 1000 (cb) GID: 100 (users) Signal: 6 (ABRT) Timestamp: Fri 2023-07-14 19:58:42 CEST (8min ago) Command Line: /bin/bash Executable: /usr/bin/bash Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-kde_autostart@autostart.service Unit: user(a)1000.service User Unit: app-kde_autostart(a)autostart.service Slice: user-1000.slice Owner UID: 1000 (cb) Boot ID: c4b7162d927340e9995cb85273857589 Machine ID: abf06ac46e2e487ea0edd474065e8b87 Hostname: tux.boltz Storage: /var/lib/systemd/coredump/core.bash.1000.c4b7162d927340e9995cb85273857589.13069.1689357522000000.zst (present) Size on Disk: 722.5K Message: Process 13069 (bash) of user 1000 dumped core. Stack trace of thread 13069: #0 0x00007fe721781a7c __pthread_kill_implementation (libc.so.6 + 0x8fa7c) #1 0x00007fe721730226 raise (libc.so.6 + 0x3e226) #2 0x00007fe721718921 abort (libc.so.6 + 0x26921) #3 0x00007fe721719611 __libc_message.cold (libc.so.6 + 0x27611) #4 0x00007fe72178c417 malloc_printerr (libc.so.6 + 0x9a417) #5 0x00007fe72178d03c malloc_consolidate (libc.so.6 + 0x9b03c) #6 0x00007fe72178f6b8 _int_malloc (libc.so.6 + 0x9d6b8) #7 0x00007fe721790aba __libc_malloc (libc.so.6 + 0x9eaba) #8 0x000055ff5a6938ee xmalloc (bash + 0x758ee) #9 0x000055ff5a69fd61 n/a (bash + 0x81d61) #10 0x000055ff5a6b98cf map_over_funcs (bash + 0x9b8cf) #11 0x000055ff5a6818f6 all_visible_functions (bash + 0x638f6) #12 0x000055ff5a68dc6a command_word_completion_function (bash + 0x6fc6a) #13 0x00007fe72190cddb rl_completion_matches (libreadline.so.8 + 0x1dddb) #14 0x000055ff5a68c7a0 bash_default_completion (bash + 0x6e7a0) #15 0x00007fe72190cef3 n/a (libreadline.so.8 + 0x1def3) #16 0x00007fe72191579c rl_complete_internal (libreadline.so.8 + 0x2679c) #17 0x00007fe72190d178 _rl_dispatch_subseq (libreadline.so.8 + 0x1e178) #18 0x00007fe72190dfa6 readline_internal_char (libreadline.so.8 + 0x1efa6) #19 0x00007fe721916f65 readline (libreadline.so.8 + 0x27f65) #20 0x000055ff5a65ce67 n/a (bash + 0x3ee67) #21 0x000055ff5a69904e n/a (bash + 0x7b04e) #22 0x000055ff5a697394 n/a (bash + 0x79394) #23 0x000055ff5a696be7 yyparse (bash + 0x78be7) #24 0x000055ff5a696821 parse_command (bash + 0x78821) #25 0x000055ff5a6a2c8e read_command (bash + 0x84c8e) #26 0x000055ff5a6a2919 reader_loop (bash + 0x84919) #27 0x000055ff5a6b5f04 main (bash + 0x97f04) #28 0x00007fe721719bb0 __libc_start_call_main (libc.so.6 + 0x27bb0) #29 0x00007fe721719c79 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c79) #30 0x000055ff5a6b4fe5 _start (bash + 0x96fe5) ELF object binary architecture: AMD x86-64 Refusing to dump core to tty (use shell redirection or specify --output). ====================================================================== I can provide the full coredump on request. Unfortunately it contains private data (for example filenames from the bash history), therefore I don't want to attach it to a public bugreport. However, I can send it by mail if needed. [Note to myself: the coredump is in ~/susebeta/2023-07-14-*.zst] The attached file contains the above bash screendump and coredumpctl output, just in case bugzilla inserts funny linebreaks. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1213757] New: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi
by bugzilla_noreply＠suse.com 20 Feb '24

20 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213757 Bug ID: 1213757 Summary: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868483 --> https://bugzilla.suse.com/attachment.cgi?id=868483&action=edit strace of hanging "ip a" The issue appears a few (~5) minutes after hostapd is started. Jul 28 12:47:40 openqa-piworker systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Jul 28 12:47:40 openqa-piworker hostapd[15307]: Configuration file: /etc/hostapd.conf Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered disabled state Jul 28 12:47:40 openqa-piworker kernel: device wlan0 entered promiscuous mode Jul 28 12:47:40 openqa-piworker hostapd[15307]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=0 pid=730 comm="/usr/sbin/wickedd --systemd --foreground ") Jul 28 12:47:41 openqa-piworker systemd[1]: Starting WPA Supplicant daemon... Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jul 28 12:47:41 openqa-piworker systemd[1]: Started WPA Supplicant daemon. Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: Could not connect to kernel driver Jul 28 12:47:45 openqa-piworker hostapd[15307]: Using interface wlan0 with hwaddr e4:5f:01:bb:63:41 and ssid "openQA-worker" Jul 28 12:47:45 openqa-piworker kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered forwarding state Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: AP-ENABLED openqa-piworker:~ # cat /etc/sysconfig/network/ifcfg-br0 IPADDR='192.168.7.1/24' BOOTPROTO='static' STARTMODE='auto' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_STP='off' BRIDGE_FORWARDDELAY='15' ZONE=dmz openqa-piworker:~ # cat /etc/hostapd.conf interface=wlan0 bridge=br0 ssid=openQA-worker wpa_passphrase=0foobar12345 driver=nl80211 country_code=DE hw_mode=g channel=7 # Bit field: bit0 = WPA, bit1 = WPA2, 3=both wpa=2 # Bit field: 1=wpa, 2=wep, 3=both auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK logger_stdout=-1 logger_stdout_level=2 openqa-piworker:~ # systemctl cat hostapd.service # /usr/lib/systemd/system/hostapd.service [Unit] Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator After=network.target [Service] ExecStart=/usr/sbin/hostapd /etc/hostapd.conf ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/hostapd.service.d/override.conf # Ensure that wlan0 is up before starting hostapd (otherwise hostapd will not add wlan0 to the bridge) [Unit] BindsTo=sys-subsystem-net-devices-wlan0.device After=sys-subsystem-net-devices-wlan0.device -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1214458] New: /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214458 Bug ID: 1214458 Summary: /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Doing a simple xzegrep - # xzegrep 'GET /release/[0-9A-F]+' vhost_access_log ...[snip] /usr/bin/xzegrep: line 219: /usr/bin/egrep: Permission denied See also https://progress.opensuse.org/issues/113108 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212954] New: amdgpu: Monitor displaying wrong resolution
by bugzilla_noreply＠suse.com 16 Feb '24

16 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1212954 Bug ID: 1212954 Summary: amdgpu: Monitor displaying wrong resolution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867944 --> https://bugzilla.suse.com/attachment.cgi?id=867944&action=edit IMG_20230703_164538751_HDR.jpg Having a 4K monitor (SAMSUNG LU28R55) attached to the docking station of my ThinkPad via HDMI I can easily 1:1 mirror the screen output of the laptop and the monitor with openSUSE Leap 15.4. Doing the same with openSUSE Leap 15.5 will result in monitor displaying a resolution 1980x2160 instead of the set 1980x1080. Using a 4x different screen (Philips) is working fine. Photo of monitor attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1214049] New: USB audio dies after idle
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214049 Bug ID: 1214049 Summary: USB audio dies after idle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868666 --> https://bugzilla.suse.com/attachment.cgi?id=868666&action=edit lsusb -v output After a recent kernel update within the past week or so I have been experiencing a problem where if audio is stopped for a while it will never restart when using a USB HID audio device. In the logs I see the following: usb_set_interface failed (-19) I have swapped the cable and that made no difference. Note that if audio is constantly active it will continue to work without issues. [33346.442012] usb 7-4: New USB device found, idVendor=1852, idProduct=7022, bcdDevice= 0.01 [33346.442023] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [33346.442027] usb 7-4: Product: DigiHug USB Audio [33346.442031] usb 7-4: Manufacturer: GFEC ASSP [33346.529561] input: GFEC ASSP DigiHug USB Audio as /devices/pci0000:40/0000:40:07.1/0000:45:00.3/usb7/7-4/7-4:1.0/0003:1852:7022.001B/input/input54 [33346.586066] hid-generic 0003:1852:7022.001B: input,hidraw11: USB HID v1.00 Device [GFEC ASSP DigiHug USB Audio] on usb-0000:45:00.3-4/input0 [33360.314128] usb 3-1.3.1: reset high-speed USB device number 36 using xhci_hcd Note that the audio recovers if I unplug and reconnect the audio device. It does not matter which application is generating the audio. The USB audio device is also plugged directly into a motherboard USB port and not a hub. Desktop is running KDE factory. Kernel is 5.14.21-150400.24.74-default #1 SMP PREEMPT_DYNAMIC I have a lot of USB devices connected. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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