Bug 365172 - creating new panel crashes with multi-monitor setup
Summary: creating new panel crashes with multi-monitor setup
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.7.0
Platform: Chakra Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-07-06 21:44 UTC by Alexander Ahjolinna
Modified: 2018-10-27 03:32 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Ahjolinna 2016-07-06 21:44:19 UTC
only thing I tried to add was a new (default) panel to my 2nd monitor and then my plasma crashed, except with the "empty" panel it doesn't crash...but "empty system tray" panel crashes it also

I'm using chakraOS with plasma5.7 & Qt 5.7...anyway: here is the gdb output (part of it): https://paste.kde.org/pslzxfajp

and "bt full" output : https://paste.kde.org/pf0cc9ylr


Reproducible: Always

Steps to Reproduce:
1. have multi-monitor setup
2. add task manager (default)
3.

Actual Results:  
plasmashell hard crashes at times


 inxi -xSCGI
System:    Host: chakra-pc Kernel: 4.6.3-1-ck x86_64 (64 bit gcc: 5.2.0) Desktop: KDE Plasma 5.7.0 (Qt 5.7.0)
           Distro: Chakra
CPU:       Quad core Intel Core i5-6600K (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28031
           clock speeds: max: 4400 MHz 1: 4399 MHz 2: 4400 MHz 3: 4399 MHz 4: 4399 MHz
Graphics:  Card: NVIDIA GM204 [GeForce GTX 970] bus-ID: 01:00.0
           Display Server: X.Org 1.17.4 driver: nvidia Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 970/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 367.27 Direct Rendering: Yes
Info:      Processes: 356 Uptime: 1 day Memory: 6982.7/15978.9MB Init: systemd Gcc sys: 5.2.0
           Client: Shell (bash 4.3.391) inxi: 2.3.0
Comment 1 Marco Martin 2016-07-08 10:09:07 UTC
pasting inline

note that it doesn't have enough debug symbols to be useful

(gdb) bt full

#0  0x00007ffff55ef6b7 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#1  0x00007ffff55ef796 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#2  0x00007ffff55cfb11 in ?? () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#3  0x00007ffff55d084a in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, bool) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#4  0x00007ffff55d122a in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#5  0x00007ffff55d14ff in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#6  0x00007ffff5674f17 in QV4::QmlContextWrapper::get(QV4::Managed const*, QV4::String*, bool*) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#7  0x00007ffff555a776 in QV4::ExecutionContext::getProperty(QV4::String*) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#8  0x00007ffff55e31c0 in QV4::Runtime::getActivationProperty(QV4::ExecutionEngine*, int) () from /usr/lib/libQt5Qml.so.5

No symbol table info available.

#9  0x00007fff2a2151f9 in ?? ()

No symbol table info available.

#10 0x0000000000000078 in ?? ()

No symbol table info available.

#11 0x175904452c5e3b00 in ?? ()

No symbol table info available.

#12 0x0000000000000008 in ?? ()

No symbol table info available.

#13 0x00000000008123a0 in ?? ()

No symbol table info available.

#14 0x00000000008123a0 in ?? ()

No symbol table info available.

---Type <return> to continue, or q <return> to quit---
Comment 2 Andrew Crouthamel 2018-09-26 22:21:29 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 3 Andrew Crouthamel 2018-10-27 03:32:50 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!