Summary: | KWin crashes on startup / login | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Stuart Campbell <stuart> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | markd.mcconnell, rdieter |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.2.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=343844 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Stuart Campbell
2015-03-23 13:06:19 UTC
Nested X server (xnest, xephyr, ...) or VNC? There're some bugreports on this, also see eg. https://bugreports.qt.io/browse/QTBUG-29978 None of the above, native local X session sitting in front of the machine. Does kwin_x11 restart automatically (and w/o crashing, oc.)? No, it just says that it kept crashing and do I want to use a different window manager. I fear that this is connected to the fact that I do not have xrandr enabled on my display - could that be the issue ? KDE 4 works with no problems though. That would be odd - the crashing xcb code looks for the first root window. You could try to re-enable the xrandr extension, but I assume this would be rather some forwarded error. I'm pretty sure it's related. QX11Info::connection passes by screen and QScreen is bound to an xrandr screen, so maybe we don't get a connection and thus we get the crash. A backtrace with full debug symbols could help as we would then know that xcb_connection_t* is null. I had seen similar looking crashes during kwin_wayland development the last weeks whenever I hit the code path before having set up the X connection. Git commit 289ec53350b50cf134a9867a9341419819b0578e by Martin Gräßlin. Committed on 24/03/2015 at 07:54. Pushed by graesslin into branch 'master'. Add basic information about the X server to supportInformation * Vendor name * Vendor release * Protocol version * All Extensions used by KWin (name, present and version) Need for this recognized due to a bug related to no xrandr present. M +14 -0 workspace.cpp http://commits.kde.org/kwin/289ec53350b50cf134a9867a9341419819b0578e If you are still able to reproduce please provide a backtrace with debug symbols. Overall what we see just doesn't make sense. It should not crash in that code. I rather think that you hit some instabilities due to a bad combination of packages or even ABI issues caused by using packages from an unstable repository. 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! |