September 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215465] New: [Build 20230917] groff / "man -P cat docker build | grep … => troff:<standard input>:80: warning: cannot select font 'C'
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215465 Bug ID: 1215465 Summary: [Build 20230917] groff / "man -P cat docker build | grep … => troff:<standard input>:80: warning: cannot select font 'C' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3584565/modules/dock er/steps/212 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation The test code runs: man -P cat docker build | grep 'docker-build - Build'; echo 4Kdp0-$?- this then returns troff:<standard input>:80: warning: cannot select font 'C' … troff:<standard input>:511: warning: cannot select font 'C' troff:<standard input>:513: warning: cannot select font 'C' troff:<standard input>:518: warning: cannot select font 'C' troff:<standard input>:518: warning: cannot select font 'C' 4Kdp0-1- i.e error spewn out and the grep fails (the actual search string not found) openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_docker@64bit fails in [docker](https://openqa.opensuse.org/tests/3584565/modules/docker/steps/212) ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20230917](https://openqa.opensuse.org/tests/3583658) ## Expected result Last good: [20230915](https://openqa.opensuse.org/tests/3580146) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213931] New: Sushi quick previewer for GNOME Files/Nautilus not working on fresh Leap 15.5 install
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213931 Bug ID: 1213931 Summary: Sushi quick previewer for GNOME Files/Nautilus not working on fresh Leap 15.5 install Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: bjurg.orsku(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi all, I've just installed Leap 15.5 on a new VM and I'm not getting file previews when I press the space bar but the following messages appear with "journalctl -f" : Aug 03 14:21:37 lp155 dbus-daemon[1636]: [session uid=1000 pid=1636] Activating service name='org.gnome.NautilusPreviewer' requested by ':1.90' (uid=1000 pid=4251 comm="/usr/bin/nautilus --gapplication-service ") Aug 03 14:21:37 lp155 org.gnome.Nauti[4290]: JS ERROR: SyntaxError: expected property name, got '{' @ resource:///org/gnome/NautilusPreviewer/js/viewers/html.js:63 Aug 03 14:21:37 lp155 org.gnome.Nauti[4290]: Script /usr/lib/org.gnome.NautilusPreviewer threw an exception Aug 03 14:21:37 lp155 dbus-daemon[1636]: [session uid=1000 pid=1636] Activated service 'org.gnome.NautilusPreviewer' failed: Process org.gnome.NautilusPreviewer exited with status 1 Information for package sushi: ------------------------------ Repository : Main Repository Name : sushi Version : 43.0-bp155.1.6 Arch : x86_64 Vendor : openSUSE Installed Size : 296.1 KiB Installed : Yes Status : up-to-date Information for package gjs: ---------------------------- Repository : Main Repository Name : gjs Version : 1.70.2-150400.3.3.1 Arch : x86_64 Vendor : SUSE LLC <https://www.suse.com/> Installed Size : 146.2 KiB Installed : Yes Status : up-to-date Maybe related to https://gitlab.gnome.org/GNOME/sushi/-/issues/81 ? Thanks for your help. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215480] New: [gdb/symtab] build-id debuginfo link doesn't work when debugging from outside container
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215480 Bug ID: 1215480 Summary: [gdb/symtab] build-id debuginfo link doesn't work when debugging from outside container Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [ This might be a dup of PR1197415. ] Consider this upstream PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=30866 ): "[gdb/symtab] symbolic links to debuginfo not followed when debugging from outside container". It exercises 4 scenarios for finding debug info: 2 from inside the container, two from outside. For the former both work, for the latter the build-id case works but the .gnu_debuglink case doesn't (which is the subject of the upstream PR). The latter cases are with gdb build from current source, and the results reproduce with the gdb-12-branch. However, when using system gdb (12.1 based), also the build-id case doesn't work: ... Looking for separate debug info (build-id) for target:/lib64-symlink/libc.so.6 Trying /usr/lib/debug/.build-id/76/7aa1e4d4fc7c106971b202b6b00e92f47411dc.debug... Trying target:/usr/lib/debug/.build-id/76/7aa1e4d4fc7c106971b202b6b00e92f47411dc.debug... Looking for separate debug info (debug link) for target:/lib64-symlink/libc.so.6 Trying target:/lib64-symlink/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/lib64-symlink/.debug/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/usr/lib/debug//lib64-symlink/libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:/usr/lib/debug/lib64-symlink//libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Trying target:target:/usr/lib/debug/lib64-symlink//libc-2.31.so-2.31-150300.52.2.x86_64.debug... no, unable to open. Missing separate debuginfo for target:/lib64-symlink/libc.so.6 ... This looks like a problem with one of the fedora patches. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215817] New: tcsh completion for 'ln' is incorrect
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215817 Bug ID: 1215817 Summary: tcsh completion for 'ln' is incorrect 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: hendersj(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When entering 'ln -s' and hitting tab to get a list of directories, I'm prompted for a <link_name> instead of getting completion from the filesystem. A comparison with the upstream project shows that their pattern in /etc/profile.d/complete.tcsh works, whereas what we have doesn't. I originally reported this issue upstream as I missed the differences between upstream's version of the file and ours. Using their file didn't work as-is (not sure why), but replacing our entry for 'ln' with theirs did. The upstream reported bug confirmed that it's an issue in our setup. That bug is at https://github.com/tcsh-org/tcsh/issues/80 This has been a longstanding issue, and I know it also exists in Leap (all versions, including 15.6 alpha). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215226] New: Yast2 "Active Directory Domain Controller" module fails on start-up
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215226 Bug ID: 1215226 Summary: Yast2 "Active Directory Domain Controller" module fails on start-up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: alanhants(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 869431 --> https://bugzilla.suse.com/attachment.cgi?id=869431&action=edit Screen shot showing the error message. In Yast2, when the "Active Directory Domain Controller" module is started, it promptly fails with a Ruby error. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213854] New: zypper still using /etc/bash_completion.d/
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1213854 Bug ID: 1213854 Summary: zypper still using /etc/bash_completion.d/ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- zypper is still using /etc/bash_completion.d/ This directory is for admin made changes, distribution packages should install in /usr/share/bash-completion/completions/ This is for Factory, ALP and SLE15 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214658] New: I No Longer Can Monitor Computer Speaker Output
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214658 Bug ID: 1214658 Summary: I No Longer Can Monitor Computer Speaker Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869045 --> https://bugzilla.suse.com/attachment.cgi?id=869045&action=edit Where monitoring output would normally be selected I used to stream audio to my computer's speakers, with the audio device configured as "Analog Stereo Duplex", and monitor the output and record it in Audacity. The process is described at https://manual.audacityteam.org/man/tutorial_recording_computer_playback_on…. This process still does work on this computer when I boot into and use Leap 15.5. But sometime between July 31 and August 6, it stopped working under Tumbleweed. I can no longer select "Monitor of Built-In Audio Analog Stereo" in pavucontrol-qt (see SelectingMonitor.png). The option is listed, but clicking it does not change the recording source. Under TW, I can record the speaker output by changing the audio playback device to "Analog Stereo Output". Also, I can no longer monitor output from the HDMI audio device, either, under TW. Selecting it does not "stick." I do not know what other information (e.g. logs, etc.) would be helpful, but am happy to provide anything that is asked for. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215837] New: [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost
by bugzilla_noreply＠suse.com 09 Oct '23

09 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215837 Bug ID: 1215837 Summary: [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: varun.ojha(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869843 --> https://bugzilla.suse.com/attachment.cgi?id=869843&action=edit Support Config KVM ## Description [Virtualization: KVM] systemd[1]: "Started Process Core Dump" in journals on localhost In the logs, there's a recurring issue with NetworkManager, which is triggering a "Started Process Core Dump" error in the system journals on the localhost. This issue is causing the NetworkManager service to fail with a core dump. The issue seems to be affecting the stability of the network management service on the system. NetworkManager Version: 1.44.0-1.1 Architecture: x86_64 Operating System: openSUSE-20230927-0 ## Information blackbauhinia:~ # zypper info NetworkManager Loading repository data... Reading installed packages... Information for package NetworkManager: --------------------------------------- Repository : openSUSE-20230927-0 Name : NetworkManager Version : 1.44.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 5.9 MiB Installed : Yes Status : up-to-date Source package : NetworkManager-1.44.0-1.1.src Upstream URL : https://networkmanager.dev/ Summary : Standard Linux network configuration tool suite Description : NetworkManager attempts to keep an active network connection available at all times. The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is intended to replace default routes, obtain IP addresses from a DHCP server, and change name servers whenever it sees fit. blackbauhinia:~ # coredumpctl --all TIME PID UID GID SIG COREFILE EXE SIZE Fri 2023-09-29 09:40:48 EDT 1787 0 0 SIGABRT present /usr/sbin/NetworkManager 522.1K blackbauhinia:~ # ## Reproduce steps The exact steps to reproduce the issue are not provided in the bug report. However, the issue has been observed in the logs of the system. Possible steps 1. Install openSUSE Tumbleweed with Latest build 2. After Autoyast installation, file: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data… 3. During virt_autotest/login_console, after KVM modules are loaded and NetworkManager is seen with Core dump in journalctl Can be seen here: https://openqa.opensuse.org/tests/3609023#step/login_console/17 https://openqa.opensuse.org/tests/3608243#step/login_console/34 https://openqa.opensuse.org/tests/3603405#step/login_console/19 Expected result: The NetworkManager service should run without errors and manage network connections as expected. Real result: The NetworkManager service is encountering a critical error and failing with a core dump. ## Reproducibility seen multiple times, frequently: Not 100% Was seen in build 20230927 ## Last good build was 20230922, 20230925 Now Seen at recent builds, 20230927 20230926 ## Environment(optional) Linux blackbauhinia 6.5.4-1-default #1 SMP PREEMPT_DYNAMIC Wed Sep 20 05:07:04 UTC 2023 (fdd7e9e) x86_64 x86_64 x86_64 GNU/Linux Linux Kernel Version: 6.5.4-1-default Hostname: blackbauhinia ## Testsuite description(optional, apply for complex scenarios) Test suit: virt-guest-installation-kvm@64bit-ipmi & virt-guest-installation-xen@64bit-ipmi ## Error https://openqa.opensuse.org/tests/3597532#step/login_console/19 Sep 25 00:03:57 blackbauhinia systemd[1]: Started Process Core Dump (PID 2366/UID 0). Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager-wait-online.service: Main process exited, code=exited, status=> Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager-wait-online.service: Failed with result 'exit-code'. Sep 25 00:03:57 blackbauhinia systemd[1]: Failed to start Network Manager Wait Online. Sep 25 00:03:57 blackbauhinia systemd[1]: Reached target Network is Online. Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Login and scanning of iSCSI devices... Sep 25 00:03:57 blackbauhinia iscsiadm[2369]: iscsiadm: No records found Sep 25 00:03:57 blackbauhinia iscsiadm[2371]: iscsiadm: No records found Sep 25 00:03:57 blackbauhinia iscsiadm[2373]: iscsiadm: Could not get list of targets from firmware. (err 21) Sep 25 00:03:57 blackbauhinia systemd-coredump[2367]: [🡕] Process 1781 (NetworkManager) of user 0 dumped core. Stack trace of thread 1781: #0 0x00007f42f2691e0c __pthread_kill_implementation (libc.so.6 +> #1 0x00007f42f263f0e6 raise (libc.so.6 + 0x3f0e6) #2 0x00007f42f26268d7 abort (libc.so.6 + 0x268d7) #3 0x00007f42f2e58b1d g_mutex_clear (libglib-2.0.so.0 + 0xb7b1d) #4 0x00007f42f30094a2 n/a (libgio-2.0.so.0 + 0xbe4a2) #5 0x00007f42f3005b4c n/a (libgio-2.0.so.0 + 0xbab4c) #6 0x00007f42f2f05970 g_object_unref (libgobject-2.0.so.0 + 0x1c> #7 0x00007f42f2dfaf89 n/a (libglib-2.0.so.0 + 0x59f89) #8 0x00007f42f2dfcb46 n/a (libglib-2.0.so.0 + 0x5bb46) #9 0x00007f42f2dfcf6f n/a (libglib-2.0.so.0 + 0x5bf6f) #10 0x00007f42f2dfeb18 n/a (libglib-2.0.so.0 + 0x5db18) #11 0x00007f42f2dff3ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3e> #12 0x00005643adfd6493 n/a (NetworkManager + 0x3f493) #13 0x00007f42f26281b0 __libc_start_call_main (libc.so.6 + 0x281b> #14 0x00007f42f2628279 __libc_start_main@@GLIBC_2.34 (libc.so.6 +> #15 0x00005643adfd6915 n/a (NetworkManager + 0x3f915) Stack trace of thread 1791: #0 0x00007f42f2709d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f42f2dfeabf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f42f2dff1cc g_main_context_iteration (libglib-2.0.so.0> #3 0x00007f42f2dff211 n/a (libglib-2.0.so.0 + 0x5e211) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1792: #0 0x00007f42f271616d syscall (libc.so.6 + 0x11616d) #1 0x00007f42f2e58cb0 g_cond_wait (libglib-2.0.so.0 + 0xb7cb0) #2 0x00007f42f2dc902b n/a (libglib-2.0.so.0 + 0x2802b) #3 0x00007f42f2e2ba92 n/a (libglib-2.0.so.0 + 0x8aa92) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1793: #0 0x00007f42f2709d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f42f2dfeabf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f42f2dff3ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3e> #3 0x00007f42f30708e6 n/a (libgio-2.0.so.0 + 0x1258e6) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 2365: #0 0x00007f42f271616d syscall (libc.so.6 + 0x11616d) #1 0x00007f42f2e58e5c g_cond_wait_until (libglib-2.0.so.0 + 0xb7> #2 0x00007f42f2dc9003 n/a (libglib-2.0.so.0 + 0x28003) #3 0x00007f42f2e2be0a n/a (libglib-2.0.so.0 + 0x8ae0a) #4 0x00007f42f2e2b44e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f42f268ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f42f271847c __clone3 (libc.so.6 + 0x11847c) ELF object binary architecture: AMD x86-64 Sep 25 00:03:57 blackbauhinia systemd[1]: Finished Login and scanning of iSCSI devices. Sep 25 00:03:57 blackbauhinia systemd[1]: systemd-coredump(a)0-2366-0.service: Deactivated successfully. Sep 25 00:03:57 blackbauhinia systemd[1]: Reached target Remote File Systems. Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Autoyast2 Init Scripts... Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Virtualization qemu daemon... Sep 25 00:03:57 blackbauhinia systemd[1]: Starting Virtualization storage daemon... Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 25 00:03:57 blackbauhinia systemd[1]: NetworkManager.service: Failed with result 'core-dump'. ## Logs/ crash # /bin/coredumpctl info 1787 PID: 1787 (NetworkManager) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Fri 2023-09-29 09:40:48 EDT (53min ago) Command Line: /usr/sbin/NetworkManager --no-daemon Executable: /usr/sbin/NetworkManager Control Group: /system.slice/NetworkManager.service Unit: NetworkManager.service Slice: system.slice Boot ID: 752a88f1ac2b4381b0fc7591961e743a Machine ID: 629cb90a95bb451e9026683e7cb65723 Hostname: blackbauhinia Storage: /var/lib/systemd/coredump/core.NetworkManager.0.752a88f1ac2b4381b0fc7591961e743a.1787.1695994848000000.zst (present) Size on Disk: 522.1K Message: Process 1787 (NetworkManager) of user 0 dumped core. Stack trace of thread 1787: #0 0x00007f4ed8491e0c __pthread_kill_implementation (libc.so.6 + 0x91e0c) #1 0x00007f4ed843f0e6 raise (libc.so.6 + 0x3f0e6) #2 0x00007f4ed84268d7 abort (libc.so.6 + 0x268d7) #3 0x00007f4ed8bcdb1d g_mutex_clear (libglib-2.0.so.0 + 0xb7b1d) #4 0x00007f4ed8d7e4a2 n/a (libgio-2.0.so.0 + 0xbe4a2) #5 0x00007f4ed8d7ab4c n/a (libgio-2.0.so.0 + 0xbab4c) #6 0x00007f4ed8c7a970 g_object_unref (libgobject-2.0.so.0 + 0x1c970) #7 0x00007f4ed8b6ff89 n/a (libglib-2.0.so.0 + 0x59f89) #8 0x00007f4ed8b71b46 n/a (libglib-2.0.so.0 + 0x5bb46) #9 0x00007f4ed8b71f6f n/a (libglib-2.0.so.0 + 0x5bf6f) #10 0x00007f4ed8b73b18 n/a (libglib-2.0.so.0 + 0x5db18) #11 0x00007f4ed8b743ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3ef) #12 0x00005652d1963493 n/a (NetworkManager + 0x3f493) #13 0x00007f4ed84281b0 __libc_start_call_main (libc.so.6 + 0x281b0) #14 0x00007f4ed8428279 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x28279) #15 0x00005652d1963915 n/a (NetworkManager + 0x3f915) Stack trace of thread 1796: #0 0x00007f4ed8509d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f4ed8b73abf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f4ed8b741cc g_main_context_iteration (libglib-2.0.so.0 + 0x5e1cc) #3 0x00007f4ed8b74211 n/a (libglib-2.0.so.0 + 0x5e211) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1797: #0 0x00007f4ed851616d syscall (libc.so.6 + 0x11616d) #1 0x00007f4ed8bcdcb0 g_cond_wait (libglib-2.0.so.0 + 0xb7cb0) #2 0x00007f4ed8b3e02b n/a (libglib-2.0.so.0 + 0x2802b) #3 0x00007f4ed8ba0a92 n/a (libglib-2.0.so.0 + 0x8aa92) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 2369: #0 0x00007f4ed851616d syscall (libc.so.6 + 0x11616d) #1 0x00007f4ed8bcde5c g_cond_wait_until (libglib-2.0.so.0 + 0xb7e5c) #2 0x00007f4ed8b3e003 n/a (libglib-2.0.so.0 + 0x28003) #3 0x00007f4ed8ba0e0a n/a (libglib-2.0.so.0 + 0x8ae0a) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) Stack trace of thread 1798: #0 0x00007f4ed8509d2f __poll (libc.so.6 + 0x109d2f) #1 0x00007f4ed8b73abf n/a (libglib-2.0.so.0 + 0x5dabf) #2 0x00007f4ed8b743ef g_main_loop_run (libglib-2.0.so.0 + 0x5e3ef) #3 0x00007f4ed8de58e6 n/a (libgio-2.0.so.0 + 0x1258e6) #4 0x00007f4ed8ba044e n/a (libglib-2.0.so.0 + 0x8a44e) #5 0x00007f4ed848ff64 start_thread (libc.so.6 + 0x8ff64) #6 0x00007f4ed851847c __clone3 (libc.so.6 + 0x11847c) ELF object binary architecture: AMD x86-64 The stack trace of the core dump is also provided in the logs. ## Workaround No Please note that resolving this issue may require further investigation, debugging, and potentially collaboration with the NetworkManager development team. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215227] New: Clementine/Strawberry crash on startup due to updated protobuf version
by bugzilla_noreply＠suse.com 08 Oct '23

08 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215227 Bug ID: 1215227 Summary: Clementine/Strawberry crash on startup due to updated protobuf version 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: zrenfire(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > strawberry: symbol lookup error: strawberry: undefined symbol: _ZN6google8protobuf8internal17AssignDescriptorsEPFPKNS1_15DescriptorTableEvEPN4absl12lts_202301259once_flagERKNS0_8MetadataE Also affects another user who's also tried Clementine. https://old.reddit.com/r/openSUSE/comments/16fr3wr/lookup_error/ I noticed that libprotobuf recently updated. > Sep 11 13:47:17 Client-57 plasmashell[1531]: plasma-pk-updates: Got update package: "libprotobuf-lite23_4_0;23.4-6.3;x86_64;repo-oss" , summary: "Protocol Buffers - Google's data interchange format" , type: "enhancement" > Sep 11 13:47:17 Client-57 plasmashell[1531]: plasma-pk-updates: Got update package: "libprotobuf23_4_0;23.4-6.3;x86_64;repo-oss" , summary: "Protocol Buffers - Google's data interchange format" , type: "enhancement" And I noticed that both players have not updated in two months. https://build.opensuse.org/package/show/openSUSE:Factory/clementine https://build.opensuse.org/package/show/openSUSE:Factory/strawberry I assume all these packages need is a rebuild. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1214046] New: Please Add "Thunderbird" or Other Additional Language to Component Description For Firefox
by bugzilla_noreply＠suse.com 08 Oct '23

08 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1214046 Bug ID: 1214046 Summary: Please Add "Thunderbird" or Other Additional Language to Component Description For Firefox Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: bill_wayson(a)yahoo.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868665 --> https://bugzilla.suse.com/attachment.cgi?id=868665&action=edit Current description for the Firefox component Currently, if I create a bug report openSUSE -> openSUSE Distribution, and then select the component Firefox, the Component Description box says "Firefox Web Browser" (see the attached screenshot). Apparently, Firefox is also the component to choose when reporting bugs in Thunderbird (e.g. bug 1213962). So, at the least, the description should also include "Thunderbird." At most, this may be the component to choose for any Mozilla product (so, maybe it should be called "Mozilla"?). -- You are receiving this mail because: You are on the CC list for the bug.

1 1