Bug 394309 - Plasma freezing continuously
Summary: Plasma freezing continuously
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Friedrich W. H. Kossebau
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2018-05-16 07:38 UTC by Paolo
Modified: 2018-10-29 02:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paolo 2018-05-16 07:38:47 UTC
Application: plasmashell (5.12.5)

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

-- Information about the crash:
- What I was doing when the application crashed: when more instances are opened, plasma freezes. I kill all open apps with xkill: this temporarily solves the problem but after a while it comes back again

- Unusual behavior I noticed:

- Custom settings of the application: adapta icon theme - adapta kde theme. I haven't tried with default theme / icons, so far

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fe051e5b394 in  () at /lib64/libKF5Plasma.so.5
#7  0x00007fe051e6f847 in  () at /lib64/libKF5Plasma.so.5
#8  0x00007fe051e5f027 in Plasma::DataEngineConsumer::~DataEngineConsumer() () at /lib64/libKF5Plasma.so.5
#9  0x00007fe01e76b2ac in  () at /usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_weather.so
#10 0x00007fe01e76b2dd in  () at /usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_weather.so
#11 0x00007fe051e6eff2 in  () at /lib64/libKF5Plasma.so.5
#12 0x00007fe051e6f15d in  () at /lib64/libKF5Plasma.so.5
#13 0x00007fe04cd7f6ac in  () at /lib64/libc.so.6
#14 0x00007fe04cd7f7dc in  () at /lib64/libc.so.6
#15 0x00007fe034057c23 in QXcbConnection::processXcbEvents() () at /lib64/libQt5XcbQpa.so.5
#16 0x00007fe04dcc5986 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#17 0x00007fe04e630eb5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#18 0x00007fe04e63885a in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#19 0x00007fe04dc9c286 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#20 0x00007fe04dc9efab in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#21 0x00007fe04dcece57 in  () at /lib64/libQt5Core.so.5
#22 0x00007fe0456ef7cd in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#23 0x00007fe0456efb98 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#24 0x00007fe0456efc30 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#25 0x00007fe04dcecba3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#26 0x00007fe0340e3065 in  () at /lib64/libQt5XcbQpa.so.5
#27 0x00007fe04dc9b02b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#28 0x00007fe04dca34c6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#29 0x000055a1ea562ed8 in  ()
#30 0x00007fe04cd691bb in __libc_start_main () at /lib64/libc.so.6
#31 0x000055a1ea56326a in _start ()

Reported using DrKonqi
Comment 1 Rex Dieter 2018-05-16 14:54:37 UTC
to get a better backtrace, please do:
dnf debuginfo-install kf5-plasma
Comment 2 Friedrich W. H. Kossebau 2018-05-16 15:03:11 UTC
Thanks for the report. 2 things for now:

a) what do you mean with "when more instances are opened"? instances of what?

b) Sadly the backtrace you gave is missing some details, not sure why DrKonqi still allowed to send it like it is. So please help manually by doing this, for installing the debug infos for the plasma library, so the backtrace has more details:

dnf debuginfo-install kf5-plasma

Then trigger a crash again and update this bug report with the new backtrace as new comment.

On a first look it seems the backtrace is similar to the one of https://bugs.kde.org/show_bug.cgi?id=394154 so some I/O error results in a hard exit and the exit handlers are doing some bad shutdown. But to judge better, more info is needed.
Comment 3 Christoph Feck 2018-06-06 19:56:41 UTC
If you can still reproduce this crash, please add a backtrace with debug symbols.
Comment 4 Andrew Crouthamel 2018-09-28 03:17:58 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 set the bug status 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 5 Andrew Crouthamel 2018-10-29 02:19:03 UTC
Dear Bug Submitter,

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!