Summary: | KInfoCenter Crash When Tried to view Energy Information | ||
---|---|---|---|
Product: | [Applications] kinfocenter | Reporter: | BlueAlchemy <BlueAlchemy17> |
Component: | general | Assignee: | David Hubner <hubn3rd> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, felipeariasf, sitter |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.5.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
BlueAlchemy
2016-09-25 18:44:30 UTC
Does "glxgears" OpenGL test work? You might need to ask in a forum of your distribution which package you need to install. Created attachment 108002 [details]
New crash information added by DrKonqi
kinfocenter (5.10.5) using Qt 5.9.1
- What I was doing when the application crashed:
Just opening "Energy Information" or "File Indexer Monitor" from Info Center
-- Backtrace (Reduced):
#6 0x00007fd2ba5e0428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007fd2ba5e202a in __GI_abort () at abort.c:89
#8 0x00007fd2bad8e001 in qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1690
#9 QMessageLogger::fatal (this=this@entry=0x7ffd95d1a000, msg=msg@entry=0x7fd2bd8d44d5 "Could not initialize GLX") at global/qlogging.cpp:796
#10 0x00007fd2bd8d206f in QGLXContext::init (this=0x131fdf0, screen=0xfcf620, share=<optimized out>) at qglxintegration.cpp:319
Is this still reproducible on newer Plasmas? 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! 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! |