August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1200944] New: Lua failure
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200944 Bug ID: 1200944 Summary: Lua failure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I launch VLC 3.1.4 from OSS repo I get an error about Lua, then I can't access to VLC web server with Lua interface. ******************************************************************************* localhost:~> vlc VLC media player 3.0.17.4 Vetinari (revision 3.0.13-8-g41878ff4f2) [00005625bf5d2b40] [http] lua interface error: Error loading script /usr/lib64/vlc/lua/intf/http.luac: lua/modules/common.lua:3: attempt to call a nil value (global 'module') [00007f96903d73c0] lua probe error: Error loading script /home/roubach/.local/share/vlc/lua/sd/tunein.lua: lua/modules/simplexml.lua:24: attempt to call a nil value (global 'module') [00005625bf4cd600] main libvlc: Lancement de vlc avec l'interface par d�faut. Utiliser ��cvlc�� pour d�marrer VLC sans interface. [00005625bf5ade90] qt interface error: cannot start Qt multiple times [00007f9648025ae0] qt generic error: cannot start Qt multiple times [00005625bf5ade90] skins2 interface error: cannot instantiate dialogs provider [00005625bf562ae0] main playlist: playlist is empty [00005625bf5ade90] [cli] lua interface error: Error loading script /usr/lib64/vlc/lua/intf/cli.luac: lua/modules/common.lua:3: attempt to call a nil value (global 'module') ******************************************************************************* -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1173574] New: fwupd Initialize default tcti. ErrorCode (0x000a000a)
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 Bug ID: 1173574 Summary: fwupd Initialize default tcti. ErrorCode (0x000a000a) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: emiliano.langella(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I noticed the following fwupd errors: # journalctl -u fwupd.service -b -- Logs begin at Thu 2020-04-23 11:28:04 CEST, end at Wed 2020-07-01 09:54:57 CEST. -- Jul 01 09:52:40 kitt systemd[1]: Starting Firmware update daemon... Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: 07:52:43:0646 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initialize> Jul 01 09:52:43 kitt systemd[1]: Started Firmware update daemon. # fwupdate -i failed: Error opening file /sys/firmware/efi/efivars/fwupd-34578c72-11dc-4378-bc7f-b643866f598c-0-0abba7dc-e516-4167-bbf5-4d9d1c739416: No such file or directory Laptop: Dell Precision 5520 Tumbleweed: 20200628 # fwupdmgr --version client version: 1.4.2 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.4.2 Let me know if you need any additional info. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1191975] New: Fwupd assertion fails, causing coredump
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191975 Bug ID: 1191975 Summary: Fwupd assertion fails, causing coredump Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rawat.arnav(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The error at the end makes no difference, the coredump still occurs when tpm2-0-tss and tpm2.0-abrmd are instaled. I don't know what could cause these asserts to fail. Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: 00:12:12:0517 GLib g_bytes_get_data: assertion 'bytes != NULL' failed Oct 22 19:12:12 linux fwupd[16013]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Oct 22 19:12:12 linux systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1192066] New: fwupd.service failes to start
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192066 Bug ID: 1192066 Summary: fwupd.service failes to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: patric.schramm(a)rub.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed fwup today but i cannot start the system via systemctl start. Error log from systemd: Okt 27 11:00:03 localhost.localdomain systemd[1]: Starting Firmware update daemon... �� Subject: A start job for unit fwupd.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit fwupd.service has begun execution. �� The job identifier is 4816. Okt 27 11:00:03 localhost.localdomain systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit fwupd.service has exited. �� The process' exit code is 'dumped' and its exit status is 11. Okt 27 11:00:03 localhost.localdomain systemd[1]: fwupd.service: Failed with result 'core-dump'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit fwupd.service has entered the 'failed' state with result 'core-dump'. Okt 27 11:00:03 localhost.localdomain systemd[1]: Failed to start Firmware update daemon. �� Subject: A start job for unit fwupd.service has failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit fwupd.service has finished with a failure. �� The job identifier is 4816 and the job result is failed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1200293] New: wget: Segmentation fault
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200293 Bug ID: 1200293 Summary: wget: Segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: robin.roevens(a)disroot.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- At least since last Tumbleweed update, wget fails to download anything and always fails with a segmentation fault: -- $ wget https://web.archive.org/web/2000/https://github.com/adobe-fonts/source-han-… Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal --2022-06-07 16:36:41-- https://web.archive.org/web/2000/https://github.com/adobe-fonts/source-han-… Resolving web.archive.org (web.archive.org) 207.241.237.3 Connecting to web.archive.org (web.archive.org)|207.241.237.3|:443... Segmentatiefout (geheugendump gemaakt) -- $ wget https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.5/zabbix_agent-6.0.5-… Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal --2022-06-07 16:38:51-- https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.5/zabbix_agent-6.0.5-… Resolving cdn.zabbix.com (cdn.zabbix.com) 172.67.69.4, 104.26.7.148, 104.26.6.148, ... Connecting to cdn.zabbix.com (cdn.zabbix.com)|172.67.69.4|:443... connected. Segmentatiefout (geheugendump gemaakt) -- I also noticed this message I never saw before: "Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal" -- not sure if it is related. Current Tumbleweed version: 20220605 wget version: Repository : openSUSE:Tumbleweed Name : wget Version : 1.21.3-1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 711.3 KiB Installed : Yes Status : up-to-date Source package : wget-1.21.3-1.2.src -- Not sure If I do this right, and if this is useful, but this is what I get with gdb: -- $ gdb --args wget https://aka.ms/vs/16/release/vc_redist.x64.exe GNU gdb (GDB; openSUSE Tumbleweed) 11.1 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from wget... Reading symbols from /usr/lib/debug/usr/bin/wget-1.21.3-1.2.x86_64.debug... (gdb) r Starting program: /usr/bin/wget https://aka.ms/vs/16/release/vc_redist.x64.exe [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [Detaching after vfork from child process 18815] [New Thread 0x7ffff4c69640 (LWP 18819)] Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal --2022-06-07 16:54:38-- https://aka.ms/vs/16/release/vc_redist.x64.exe Verbinding maken met 192.168.0.1:800... verbonden. Thread 2 "BMScavenger" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff4c69640 (LWP 18819)] 0x00007ffff788668c in __condvar_dec_grefs (cond=cond@entry=0x7ffff6bf8500, g=g@entry=1, private=private@entry=0) at pthread_cond_wait.c:152 152 if (atomic_fetch_add_release (cond->__data.__g_refs + g, -2) == 3) (gdb) bt #0 0x00007ffff788668c in __condvar_dec_grefs (cond=cond@entry=0x7ffff6bf8500, g=g@entry=1, private=private@entry=0) at pthread_cond_wait.c:152 #1 0x00007ffff7887164 in __pthread_cond_wait_common (abstime=<optimized out>, clockid=1, mutex=0x55555562e5c0, cond=0x7ffff6bf8500) at pthread_cond_wait.c:510 #2 ___pthread_cond_clockwait64 (abstime=<optimized out>, clockid=1, mutex=0x55555562e5c0, cond=0x7ffff6bf8500) at pthread_cond_wait.c:682 #3 ___pthread_cond_clockwait64 (cond=0x7ffff6bf8500, mutex=0x55555562e5c0, clockid=1, abstime=<optimized out>) at pthread_cond_wait.c:670 #4 0x00007ffff66294f7 in () #5 0x0000000000005656 in () #6 0x000000002076b0af in () #7 0x000055555562e5c0 in () #8 0x0000141a205c7cea in () #9 0x0000000000000001 in () #10 0x0000000000000064 in () #11 0x0000000000005656 in () #12 0x000000002076b0af in () #13 0x6e65766163534d42 in () #14 0x0000000000726567 in () #15 0x0000000000000000 in () -- I have no idea how and where to look for more detail about this problem and the gdb output does not make me any wiser. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1202162] New: MicroOS Desktop: Shutdown with Update results in Restart
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202162 Bug ID: 1202162 Summary: MicroOS Desktop: Shutdown with Update results in Restart Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time I select 'Shutdown' and the pop-up asks to install pending updates, the system performs a restart, not a shutdown.... -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1200461] New: Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200461 Bug ID: 1200461 Summary: Dracut locks computer, fails to generate initrd file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mfdemicco(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859545 --> http://bugzilla.opensuse.org/attachment.cgi?id=859545&action=edit Photo of screen at moment of freeze When I update to kernel 5.18.1-1 or 5.18.2.1, Dracut locks up my system requiring a power button reboot when creating the initrd file. I also tried installing the latest version of Tumbleweed to another partition, and the installation locked up the computer about 50% into the installation with no creation of the initrd file. The computer freezes at: Dracut: *** Including module: kernel-modules *** When I look in my /boot folder, everything for the kernel is created except for the initrd file I've done a search and can't find anyone that has the same problem. The system runs file with the older kernel 5.17.4-1. I have a legacy BIOS system. -- You are receiving this mail because: You are on the CC list for the bug.

1 39

[Bug 1194202] New: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header)
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194202 Bug ID: 1194202 Summary: binutils-mingw PE executables/dlls are not reproducible (Timestamp in header) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- PE images have a timestamp in the header: https://blog.beuc.net/posts/Practical_basics_of_reproducible_builds_2/ Debian has some patches to use SOURCE_DATE_EPOCH instead of the current time: https://salsa.debian.org/mingw-w64-team/binutils-mingw-w64/-/blob/master/de… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1202662] New: VUL-0: CVE-2020-35511: pngcheck: Buffer overflow in pngcheck 2.4.0 via a crafted png file
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202662 Bug ID: 1202662 Summary: VUL-0: CVE-2020-35511: pngcheck: Buffer overflow in pngcheck 2.4.0 via a crafted png file Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/340566/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pgajdos(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-35511 A global buffer overflow was discovered in pngcheck function in pngcheck-2.4.0(5 patches applied) via a crafted png file. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35511 https://www.cve.org/CVERecord?id=CVE-2020-35511 http://www.libpng.org/pub/png/apps/pngcheck.html -- You are receiving this mail because: You are on the CC list for the bug.

1 5