Bug 359890 - Desktop freezes, plasmashell hangs using up CPU when trying to do anything in plasma
Summary: Desktop freezes, plasmashell hangs using up CPU when trying to do anything in...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-28 16:42 UTC by wodencafe
Modified: 2021-01-02 04:34 UTC (History)
5 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 wodencafe 2016-02-28 16:42:00 UTC
I am able to correctly log into the Plasma desktop.

However, if I try to run / launch any applications or do anything, the entire desktop hangs, and when I switch to TTY, I can see plasmashell is hung. It never resumses, and when I Ctrl-Alt-F7 back to the desktop, it seg faults.

Reproducible: Always

Steps to Reproduce:
1. Log into the plasma desktop
2. Try to launch an application or do something
3. Everything hangs



Here is the Stack Trace from gdb:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#0  0x00007f6092aedda0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f60939fa55b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x3e393d0) at thread/qwaitcondition_unix.cpp:136
#2  0x00007f60939fa55b in QWaitCondition::wait(QMutex*, unsigned long) (this=<optimized out>, mutex=0x3e0d820, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x00007f6096c0883b in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x00007f6096c091d5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007f60946b6b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x26561e0, receiver=receiver@entry=0x26e7720, e=e@entry=0x7ffffd2fc4d0) at kernel/qapplication.cpp:3720
#6  0x00007f60946bc230 in QApplication::notify(QObject*, QEvent*) (this=0x7ffffd2fc890, receiver=0x26e7720, e=0x7ffffd2fc4d0) at kernel/qapplication.cpp:3503
#7  0x00007f6093bd8f1b in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffffd2fc890, receiver=0x26e7720, event=event@entry=0x7ffffd2fc4d0) at kernel/qcoreapplication.cpp:935
#8  0x00007f6093c2f09d in QTimerInfoList::activateTimers() (event=0x7ffffd2fc4d0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#9  0x00007f6093c2f09d in QTimerInfoList::activateTimers() (this=0x2648820) at kernel/qtimerinfo_unix.cpp:635
#10 0x00007f6093c2f5d9 in idleTimerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:177
#11 0x00007f6093c2f5d9 in idleTimerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:224
#12 0x00007f60900b3ff7 in g_main_context_dispatch (context=0x7f607c001710) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3154
#13 0x00007f60900b3ff7 in g_main_context_dispatch (context=context@entry=0x7f607c001710) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3769
#14 0x00007f60900b4250 in g_main_context_iterate (context=context@entry=0x7f607c001710, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3840
#15 0x00007f60900b42fc in g_main_context_iteration (context=0x7f607c001710, may_block=may_block@entry=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901
#16 0x00007f6093c3027f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x26486a0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#17 0x00007f6093bd675a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffffd2fc710, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#18 0x00007f6093bde2cc in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1188
#19 0x00007f6093ef300c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1510
#20 0x00007f60946b3025 in QApplication::exec() () at kernel/qapplication.cpp:2956
#21 0x00000000004322c3 in main(int, char**) (argc=2, argv=<optimized out>) at ../../shell/main.cpp:176
Comment 1 Marco Martin 2016-03-02 09:46:54 UTC
may be the usual sync KRun problem on launching malformed desktop files?
Comment 2 wodencafe 2016-03-02 13:12:42 UTC
I just wanted to add that I upgraded to the latest plasmashell 5.5.2 and still see this.

I also reset my .config, .cache, and .kde directories, which also did not help.

I don't see any kind of issue like this in GNOME or Unity, so I'm thinking it's something KDE-specific.

Is there any more information I can provide, or any other way I can help you guys in narrowing this problem now?
Comment 3 wodencafe 2016-03-02 13:13:35 UTC
I have also apt-get purged all of KDE and plasma and reinstalled them multiple times, which did not affect the issue.
Comment 4 Justin Zobel 2020-12-03 01:04:56 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" when you respond, thank you.
Comment 5 Bug Janitor Service 2020-12-18 04:34:57 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 6 Bug Janitor Service 2021-01-02 04:34:30 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!