Bug 366466 - Plasma crashes at load time
Summary: Plasma crashes at load time
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-08-06 05:11 UTC by wh8rt57
Modified: 2018-06-08 18:32 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wh8rt57 2016-08-06 05:11:39 UTC
Application: plasma-desktop (4.11.22)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 3.16.7-35-desktop i686
Distribution: "openSUSE Tumbleweed (20160730) (i586)"

-- Information about the crash:
- What I was doing when the application crashed: logging on

Plasma crashes in both standard and failsafe mode.

Desktop screen black, but appears fleetingly in background when working on an application that somehow came up started - like this bugtracker window.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4e85780 (LWP 1713))]

Thread 3 (Thread 0xa04d2b40 (LWP 1715)):
#0  0xffffffff in __kernel_vsyscall ()
#1  0xffffffff in clock_gettime () at /lib/libc.so.6
#2  0xffffffff in  () at /usr/lib/libQtCore.so.4
#3  0xffffffff in  () at /usr/lib/libQtCore.so.4
#4  0xffffffff in  () at /usr/lib/libQtCore.so.4
#5  0xffffffff in  () at /usr/lib/libQtCore.so.4
#6  0xffffffff in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#7  0xffffffff in  () at /usr/lib/libglib-2.0.so.0
#8  0xffffffff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#9  0xffffffff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#10 0xffffffff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#11 0xffffffff in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#12 0xffffffff in QThread::exec() () at /usr/lib/libQtCore.so.4
#13 0xffffffff in  () at /usr/lib/libQtCore.so.4
#14 0xffffffff in  () at /usr/lib/libQtCore.so.4
#15 0xffffffff in start_thread () at /lib/libpthread.so.0
#16 0xffffffff in clone () at /lib/libc.so.6

Thread 2 (Thread 0xa2e28b40 (LWP 1714)):
#0  0xffffffff in __kernel_vsyscall ()
#1  0xffffffff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0xffffffff in  () at /usr/lib/libQtScript.so.4
#3  0xffffffff in  () at /usr/lib/libQtScript.so.4
#4  0xffffffff in start_thread () at /lib/libpthread.so.0
#5  0xffffffff in clone () at /lib/libc.so.6

Thread 1 (Thread 0xb4e85780 (LWP 1713)):
[KCrash Handler]
#7  0xffffffff in __kernel_vsyscall ()
#8  0xffffffff in raise () at /lib/libc.so.6
#9  0xffffffff in abort () at /lib/libc.so.6
#10 0xffffffff in  () at /lib/libc.so.6
#11 0xffffffff in __fortify_fail () at /lib/libc.so.6
#12 0xffffffff in  () at /lib/libc.so.6
#13 0xffffffff in _fini () at /usr/lib/libkunitconversion.so.4
#14 0xffffffff in KUnitConversion::UnitCategory::addIdMapValue(KSharedPtr<KUnitConversion::Unit>, int) () at /usr/lib/libkunitconversion.so.4
#15 0x0afec798 in  ()
#16 0x00000000 in  ()

Reported using DrKonqi
Comment 1 Nate Graham 2018-06-08 18:32:15 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham