Summary: | KDE plasma, sddm crash on start after hanging while playing audio | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Eyal Rozenberg <eyalroz1> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bhush94, eyalroz1, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.4.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
.xsession-errors from a session with crashes |
Description
Eyal Rozenberg
2015-11-06 22:48:55 UTC
Created attachment 95363 [details]
New crash information added by DrKonqi
plasmashell (5.4.2) using Qt 5.5.1
This is another one of the numerous crashes I got when logging in again after rebooting.
-- Backtrace (Reduced):
#6 0x00007fbd7b87b107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007fbd7b87c4e8 in __GI_abort () at abort.c:89
#8 0x00007fbd7bffd1e1 in qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1578
#9 QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:781
#10 0x00007fbd7f279991 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
Can I see ~.xsession-errors please Created attachment 95397 [details]
.xsession-errors from a session with crashes
So, here's an .xsession-errors I generated just now; obviously it's not the same session as the crash reports I uploaded a before. If it's critical for the reports and the .xsession-errors to be from the same session, let me know.
Also note that this session was started using LXDE. If I try to use sddm - the machine hangs.
Finally I'll note that the machine has an NVIDIA GTX 650 Ti - although the display does not use it - and a few days ago I installed CUDA 7.5 and the display drivers which come with it. I was thinking perhaps that could be part of the cause.
> was thinking perhaps that could be part of the cause.
It is, the error was in us using OpenGL.
I just wanted to get the exact error message from this log for our error handling.
Git commit e20c4c6b7a2910bef752a19a414488e257a49419 by David Edmundson. Committed on 09/11/2015 at 22:30. Pushed by davidedmundson into branch 'master'. Catch other openGL error gracefully Related: bug 355054 REVIEW: 125997 M +6 -3 shell/main.cpp http://commits.kde.org/plasma-workspace/e20c4c6b7a2910bef752a19a414488e257a49419 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! |