| Summary: | plasma crash on thinkpad x40 at start | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | p92 |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bhush94, plasma-bugs |
| Priority: | NOR | Keywords: | drkonqi, triaged |
| Version: | 5.4.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | .xsession-errors when retried with startx | ||
|
Description
p92
2015-10-25 00:00:30 UTC
>#10 0xb5090d89 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
This is printing a message. Can you run plasmashell from a command line and tell me what it says?
Hello sorry for delay if I do under shell as user : # X& # export DISPLAY=0;0 # xclock& # plasmashell & plasma starts without problems and is usable. It is only with startx that plasmashell aborts (in loop since it seems startx wants to restart it each time). I don't really know how to start plasmashell by hand in this environnment. No message is displayed on X screen except the crash window. Created attachment 95304 [details]
.xsession-errors when retried with startx
I retried with startx and it seems there are somme interesting messages in .xsession-errors concerning plasmashell crash
networkmanager-qt: void NetworkManager::AccessPointPrivate::propertiesChanged(const QVariantMap&) Unhandled property "LastSeen"
QOpenGLShader: could not create shader
QSGSimpleMaterialShader does not implement 'uniform lowp float qt_Opacity' in its fragment shader
Application::crashHandler() called with signal 6; recent crashes: 1
Service "org.kde.StatusNotifierHost-19303" unregistered
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 19303
KCrash: Arguments: /usr/bin/plasmashell -s --crashes 1
KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit
kdeinit5: Got EXEC_NEW '/usr/lib/i386-linux-gnu/libexec/drkonqi' from wrapper.
kdeinit5: preparing to launch '/usr/lib/i386-linux-gnu/libexec/drkonqi'
found lsb_release
Using /proc to determine executable path
Executable is: "/usr/bin/plasmashell"
Executable exists: true
Enabling drkonqi crash catching
Invalid pixmap specified.
No frame loaded
No frame loaded
No frame loaded
No frame loaded
No frame loaded
No frame loaded
kscreen: launcherDataAvailable: "org.kde.KScreen.Backend.XRandR"
kscreen: Primary output changed from KScreen::Output(Id: 66 , Name: "LVDS1" ) ( "LVDS1" ) to KScreen::Output(Id: 66 , Name: "LVDS1" ) ( "LVDS1" )
QXcbConnection: XCB error: 3 (BadWindow), sequence: 41378, resource id: 88080390, major code: 18 (ChangeProperty), minor code: 0
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
unversioned plugin detected, may result in instability
Sending SIGSTOP to process
btw do you know where I could also report bugs on sddm-greeter ? 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! 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! |