Bug 457004 - plasma crashes when switching audio profile output from win7 volume mixer widget
Summary: plasma crashes when switching audio profile output from win7 volume mixer widget
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.24.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-07-22 04:54 UTC by julioalfredomachado
Modified: 2022-08-28 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
button which causes widget to crash (hdmi icon box) (212.06 KB, image/png)
2022-07-22 04:59 UTC, julioalfredomachado
Details
install debug symbols on kde crash handlers does not work for plasma-workspace (118.78 KB, image/png)
2022-07-24 06:27 UTC, julioalfredomachado
Details
missing debug packages on plasma-workspace crash on kde crash handler (27.11 KB, image/png)
2022-07-27 22:04 UTC, julioalfredomachado
Details

Note You need to log in before you can comment on or make changes to this bug.
Description julioalfredomachado 2022-07-22 04:54:35 UTC
Application: plasmashell (5.24.4)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-41-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
from the desktop panel (the system tray) I opened the widget "win7 volume mixer" clicking the icon, then I clicked the speakers icon (in my case HDMI) to check which audio profile is being used, if I do this again, next time it will crash, this happens everytime

- Custom settings of the application:
no real custom settings, only worth noting is that both the default audio volume icon/item and the win7 volume mixer are enabled at the same time (I have both icons active in my system tray, which is how I want it) and I'm also using version 26 (v26)

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f924442051b in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x00007f924443190f in QWidget::removeAction(QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x00007f9229dd0d98 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/libplasmacomponentsplugin.so
#7  0x00007f92443f8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x00007f9243701e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f9243737437 in QObjectPrivate::setParent_helper(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f9243737948 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f9229dcb82b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/libplasmacomponentsplugin.so
#12 0x00007f924372f1b3 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f92443f8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f9243701e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9243704f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f924375ba57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f9241addd1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f9241b326f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f9241adb3c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f924375b0a8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f924370074b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f9243708ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000560fd3d60dce in ?? ()
#24 0x00007f924301dd90 in __libc_start_call_main (main=main@entry=0x560fd3d5ff70, argc=argc@entry=1, argv=argv@entry=0x7ffefd8fc0b8) at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x00007f924301de40 in __libc_start_main_impl (main=0x560fd3d5ff70, argc=1, argv=0x7ffefd8fc0b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffefd8fc0a8) at ../csu/libc-start.c:392
#26 0x0000560fd3d60ef5 in ?? ()
[Inferior 1 (process 1180) detached]

Possible duplicates by query: bug 456990, bug 456947, bug 456940, bug 456743, bug 456720.

Reported using DrKonqi
Comment 1 julioalfredomachado 2022-07-22 04:59:12 UTC
Created attachment 150804 [details]
button which causes widget to crash (hdmi icon box)
Comment 2 Nate Graham 2022-07-22 18:00:48 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

> #6  0x00007f9229dd0d98 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/libplasmacomponentsplugin.so

Could you please install debug symbols for plasma-workspace, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks again!
Comment 3 julioalfredomachado 2022-07-24 06:26:28 UTC
(In reply to Nate Graham from comment #2)
> Thank you for the bug report! Unfortunately the backtrace is incomplete and
> missing debug symbols for the following lines that we need to figure out
> exactly what's going wrong:
> 
> > #6  0x00007f9229dd0d98 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/components/libplasmacomponentsplugin.so
> 
> Could you please install debug symbols for plasma-workspace, reproduce the
> crash, and attach a new symbolicated backtrace? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Thanks again!

sorry I'm a novice at this I tried first running the commands sudo apt install plasma-workspace-dbg and sudo apt install plasma-workspace-dbgsym but both fail to install, I also tried installing this sudo apt install kubuntu-debug-installer but it seems to not make a difference, I tried reproducing the crash and then on the kde crash handler I clicked the button install debug symbols, but it didn't work too (i'll add the screenshot), also o the page "how to create useful reports" you added, this link was down https://wiki.kubuntu.org/DebuggingProgramCrash, idk if I need it.

Finally somebody seems to be also dealing with this: https://askubuntu.com/questions/1143321/where-are-the-debug-symbols-for-plasmashell-kubuntu-19-04 and one of the answers recommend executing this command and some others sudo apt install plasma-workspace-dev like suggesting that this should work instead of -dbg or -dbgsym packages (I really don't understand much but it seems related to my problem of not findings debug symbols packages)

That's my experience so far, I hope it's useful or at least that you can guide me on what should I do next.
Comment 4 julioalfredomachado 2022-07-24 06:27:27 UTC
Created attachment 150862 [details]
install debug symbols on kde crash handlers does not work for plasma-workspace
Comment 5 Nate Graham 2022-07-25 14:06:12 UTC
I don't use Kubuntu so I'm not familiar with the process needed to make this work there, sorry. I would recommend seeking assistance on a Kubuntu-specific forum or chatroom.
Comment 6 Nate Graham 2022-07-25 14:06:51 UTC
I did find https://wiki.ubuntu.com/Debug%20Symbol%20Packages, so maybe that can help.
Comment 7 julioalfredomachado 2022-07-26 23:32:26 UTC
Reading on the forums it seems I'm supposed to first report issues on forum.kde.org before doing it on bugs.kde.org: https://forum.kde.org/viewtopic.php?f=289&t=122020 (I didn't know this)

So I will do that, I'll report back if I receive a solution or any other info.
Comment 8 Nate Graham 2022-07-27 14:30:00 UTC
You can post bug reports here first, it's fine. Especially for crashes.
Comment 9 julioalfredomachado 2022-07-27 22:04:03 UTC
(In reply to Nate Graham from comment #6)
> I did find https://wiki.ubuntu.com/Debug%20Symbol%20Packages, so maybe that
> can help.

I was able to install debug symbols using your link, it failed to fetch packages first with the message on the terminal:

W: GPG error: http://ddebs.ubuntu.com jammy-updates Release: The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) <ubuntu-archive@lists.ubuntu.com>

but then I tried again installing the optional sources at step 1 and apt update seems to work now:
Ign:6 http://ddebs.ubuntu.com jammy InRelease 
Ign:7 http://ddebs.ubuntu.com jammy-updates InRelease
Ign:8 http://ddebs.ubuntu.com jammy-proposed InRelease
Get:9 http://ddebs.ubuntu.com jammy Release [40.4 kB]
Hit:11 http://ddebs.ubuntu.com jammy-updates Release                                                         
Get:13 http://ddebs.ubuntu.com jammy-proposed Release [40.5 kB]   

It lets me install -dbgsym for plasma-workspace on the terminal:
Get:1 http://ddebs.ubuntu.com jammy/universe amd64 plasma-workspace-dbgsym amd64 4:5.24.4-0ubuntu1 [95.5 MB]

now on kde crash handler I'm able to install debug symbols with the button "install debug symbols" except for 2 components (I'll attach the image) but still, the kde crash handler says the crash information is not useful (probably because of the debug packages missing)
Comment 10 julioalfredomachado 2022-07-27 22:04:59 UTC
Created attachment 150956 [details]
missing debug packages on plasma-workspace crash on kde crash handler
Comment 11 Nate Graham 2022-07-27 22:16:48 UTC
It's frustrating to me as a bug triager that Ubuntu users have such a bad experience installing debug symbols.
Comment 12 julioalfredomachado 2022-07-27 22:21:21 UTC
(In reply to Nate Graham from comment #11)
> It's frustrating to me as a bug triager that Ubuntu users have such a bad
> experience installing debug symbols.

Indeed, I thought this bug reporting would go smooth.
Comment 14 Bug Janitor Service 2022-08-13 04:35:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 15 Bug Janitor Service 2022-08-28 04:35:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!