[Bug 1191405] New: [Snapshots 20210929 and 20211001] [KDE Plasma Wayland] Telegram-desktop does not start due to Pipewire library undefined symbol
http://bugzilla.opensuse.org/show_bug.cgi?id=1191405 Bug ID: 1191405 Summary: [Snapshots 20210929 and 20211001] [KDE Plasma Wayland] Telegram-desktop does not start due to Pipewire library undefined symbol Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: mrcuve0@posteo.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0 Build Identifier: telegram Desktop 3.1.1-1.1 (updated from 20210927 to 20210929 and later) does not start when launched from gui. When launched from command line, it returns such error and exits: ``` telegram-desktop: symbol lookup error: /usr/lib64/pipewire-0.3/jack/libjack.so.0: undefined symbol: PW_LOG_TOPIC_DEFAULT ``` Reverting all changes related to Pipewire to the original snapshot (20210927) solves the issue. Reproducible: Always Steps to Reproduce: 1. Update from 20210927 to 20210929 or 20211001 2. Start Telegram Desktop from CLI Actual Results: Telegram Desktop does not start and returns the aforementioned error. Expected Results: Telegram should start with no issues -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191405 http://bugzilla.opensuse.org/show_bug.cgi?id=1191405#c1 --- Comment #1 from Mrcuve0 <mrcuve0@posteo.net> --- Created attachment 852972 --> http://bugzilla.opensuse.org/attachment.cgi?id=852972&action=edit List of packages upgraded from 20210927 to 20211001 The error is solved when rolling back all the files related to Pipewire -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191405 http://bugzilla.opensuse.org/show_bug.cgi?id=1191405#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com Assignee|tiwai@suse.com |alarrosa@suse.com --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Seems to be a regression in the latest pipewire update. Reassigned to PW package maintainer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191405 http://bugzilla.opensuse.org/show_bug.cgi?id=1191405#c3 --- Comment #3 from Mrcuve0 <mrcuve0@posteo.net> --- Created attachment 853010 --> http://bugzilla.opensuse.org/attachment.cgi?id=853010&action=edit Pipewire SW as of 20211005 snapshot The bug is solved w/ snapshot 20211005, see latest attachment reporting the new pipewire versions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1191405 http://bugzilla.opensuse.org/show_bug.cgi?id=1191405#c4 Mrcuve0 <mrcuve0@posteo.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mrcuve0 <mrcuve0@posteo.net> --- The issue is solved, noob here: shall I mark "resolved + upstream" or a more generic "resolved + fixed"? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com