Summary: | plasmashell segfaults on non-GLX 1.3 capable environments | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Orion Poplawski <orion> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bhush94, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.3.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Orion Poplawski
2015-04-29 17:50:33 UTC
That seg fault isn't about non GLX. That's either: 1) missing plasma-desktop 2) broken XDG_DATA_DIRS environment variable if you're self compiled. In the next release this problem will be "solved" with a dialog making it more obvious. You might still have an error on non GLX, but this isn't it. Can you check and report back for me? Yes, I was testing in a minimal environment - so I take it that we (Fedora) should have plasma-workspace depend on plasma-desktop? Currently it does not. Or does plasmashell need to get fixed so as to not segfault in this case? I installed plasma-desktop and it does appear to start up. I don't see the panel displayed though. output: QXcbConnection: Failed to get the primary output of the screen QXcbConnection: XCB error: 172 (Unknown), sequence: 162, resource id: 239, major code: 149 (Unknown), minor code: 20 kf5.kservice.sycoca: Trying to open ksycoca from "/home/orion/.cache/ksycoca5" populateAddPanelsMenu 1 WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported! This is an application bug! kscreen: Launcher finished with exit code 0 , status 1 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! I don't see any dialog indicating what the issue is. I do get a krunner crash dialog reporting a Qt abort trying to initialize GLX: Thread 1 (Thread 0x7fb6f7b2d940 (LWP 31720)): [KCrash Handler] #6 0x00007fb705e24eab in raise () from /lib64/libc.so.6 #7 0x00007fb705e0f5b9 in abort () from /lib64/libc.so.6 #8 0x00007fb706b73093 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1842 #9 QMessageLogger::fatal (this=this@entry=0x7fffd1cb7af0, msg=msg@entry=0x7fb70a99b7f0 "Could not initialize GLX") at global/qlogging.cpp:880 #10 0x00007fb70a995fe8 in QGLXContext::init (this=0x55f99b09d930, screen=0x55f99afe56f0, share=<optimized out>) at qglxintegration.cpp:375 #11 0x00007fb70a99648b in QXcbGlxIntegration::createPlatformOpenGLContext (this=<optimized out>, context=0x7fffd1cb7c60) at qxcbglxintegration.cpp:184 #12 0x00007fb6eb1f3ca9 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at qxcbintegration.cpp:281 #13 0x00007fb707124091 in QOpenGLContext::create (this=this@entry=0x7fffd1cb7c60) at ../../include/QtGui/5.11.1/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:105 #14 0x00007fb70a9996d7 in QGLXContext::queryDummyContext() () at qglxintegration.cpp:757 #15 0x00007fb70a999d0d in QGLXContext::supportsThreading () at qglxintegration.cpp:804 #16 0x00007fb70943eff5 in QSGRenderLoop::instance() () from /lib64/libQt5Quick.so.5 #17 0x00007fb7094b258a in QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) () from /lib64/libQt5Quick.so.5 #18 0x00007fb70a5482e2 in PlasmaQuick::Dialog::Dialog(QQuickItem*) () from /lib64/libKF5PlasmaQuick.so.5 #19 0x000055f99a164f7f in View::View(QWindow*) () #20 0x000055f99a16396d in main () Sep 25 15:58:55 bld-pc1.cora.nwra.com plasmashell[26162]: Could not initialize GLX Sep 25 15:58:56 bld-pc1.cora.nwra.com plasmashell[26469]: "Message recipient disconnected from message bus without replying" orion 31958 31668 1 16:14 ? 00:00:02 /usr/libexec/drkonqi -platform xcb -display :51 --appname plasmashell --apppath /usr/bin --signal 6 --pid 31722 --appversion 5.13.4 --programname Plasma --bugaddress submit@bugs.kde.org --startupid 0 --restarted plasma-desktop-5.13.4-1.fc28.x86_64 As a workaround run kcmshell5 qtquickettings select software as the backend you'll get something that works. This should be done automatically starting with Plasma 5.something. Please report back if this is still an issue with Plasma 5.18 or newer. |