Bug 394435

Summary: Crash when opening apps from panel: in ~DataEngineManagerPrivate
Product: [Plasma] plasmashell Reporter: Paolo <paolo>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED WORKSFORME    
Severity: crash CC: justin.zobel, notmart, plasma-bugs-null
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.12.5   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Paolo 2018-05-19 08:10:24 UTC 
Application: plasmashell (5.12.5)

Qt Version: 5.10.1
Frameworks Version: 5.46.0
Operating System: Linux 4.17.0-0.rc5.git1.1.fc29.x86_64 x86_64
Distribution: "Fedora release 29 (Rawhide)"

-- Information about the crash:
- What I was doing when the application crashed:
I was watching a video on youtube, then tried to swap to another open application (deluge) without success. Closing running apps from window button (x button) works; swapping through open apps from main panel does not work
- Unusual behavior I noticed:
Xkill temporarily solves the freeze (it shuts all open windows)
- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Illegal instruction
[KCrash Handler]
#6  0x00007f3ab4c86fa0 in  () at /lib64/libKF5GlobalAccel.so.5
#7  0x00007f3ab5adfff2 in Plasma::DataEngineManagerPrivate::~DataEngineManagerPrivate() (this=0x564d8fb88ba0, __in_chrg=<optimized out>) at /usr/src/debug/kf5-plasma-5.46.0-1.fc29.x86_64/src/plasma/private/dataenginemanager.cpp:63
#8  0x00007f3ab5adfff2 in Plasma::DataEngineManager::~DataEngineManager() (this=0x7f3ab5d3b110 <Plasma::(anonymous namespace)::Q_QGS_privateDataEngineManagerSelf::innerFunction()::holder>, __in_chrg=<optimized out>) at /usr/src/debug/kf5-plasma-5.46.0-1.fc29.x86_64/src/plasma/private/dataenginemanager.cpp:103
#9  0x00007f3ab5ae015d in Plasma::DataEngineManagerSingleton::~DataEngineManagerSingleton() (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kf5-plasma-5.46.0-1.fc29.x86_64/src/plasma/private/dataenginemanager.cpp:82
#10 0x00007f3ab5ae015d in Plasma::(anonymous namespace)::Q_QGS_privateDataEngineManagerSelf::Holder::~Holder() (this=<optimized out>, __in_chrg=<optimized out>) at /usr/src/debug/kf5-plasma-5.46.0-1.fc29.x86_64/src/plasma/private/dataenginemanager.cpp:88
#11 0x00007f3ab09ee6ac in  () at /lib64/libc.so.6
#12 0x00007f3ab09ee7dc in  () at /lib64/libc.so.6
#13 0x00007f3a97cc2c23 in QXcbConnection::processXcbEvents() () at /lib64/libQt5XcbQpa.so.5
#14 0x00007f3ab1936986 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#15 0x00007f3ab22a1eb5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#16 0x00007f3ab22a985a in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#17 0x00007f3ab190d286 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#18 0x00007f3ab190ffab in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#19 0x00007f3ab195de57 in  () at /lib64/libQt5Core.so.5
#20 0x00007f3aa935b8ad in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#21 0x00007f3aa935bc78 in  () at /lib64/libglib-2.0.so.0
#22 0x00007f3aa935bd10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#23 0x00007f3ab195dba3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#24 0x00007f3a97d4e065 in  () at /lib64/libQt5XcbQpa.so.5
#25 0x00007f3ab190c02b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#26 0x00007f3ab19144c6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#27 0x0000564d8dadded8 in  ()
#28 0x00007f3ab09d81bb in __libc_start_main () at /lib64/libc.so.6
#29 0x0000564d8dade26a in _start ()

Reported using DrKonqi
Comment 1 Justin Zobel 2020-12-04 04:55:09 UTC 
Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 2 Bug Janitor Service 2020-12-19 04:35:18 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 3 Bug Janitor Service 2021-01-03 04:34:45 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!