Summary: | After manually killing kwin_x11, "kwin_x11 --replace" crashed first (then worked okay) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Frans Oilinki <moilinki> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 5.3.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Frans Oilinki
2015-11-25 04:20:15 UTC
(In reply to Frans Oilinki from comment #0) > -- Information about the crash: it's a crash-on-exit, see bug #353624 The reason for the exit is "some" error in the xcb connection, you should have some "The X11 connection broke" output in the kwin logs (from the Qt event handler) > I killed existing corrupted corrupted in which way? > kwin_x11 with SIGHUP. SIGTERM failed? > working okay (except for the configuration of window title bar > configuration). mind to elaborate? different bug? > P.S. I am wondering what is the correct method to reclaim my KDE session > that is unusable because of apparent kwin corruption. kwin_x11 --replace & "anywm --replace &" can replace "anywm --replace &" (as long as they're compliant to the spec, iirc it even works with icewm and fvwm nowadays ;-) > configuration is not fully applied (window bar font sizes much bigger than > my configuration) Sounds more like a DPI issue? > could not change that with system settings since it just > crashed :-) backtrace? > By corrupted kwin_x11 above, I mean that keyboard or mouse events show > portions of window contents in seemingly random places. Clicking anything or > switching windows/desktops by keyboard hot keys is impossible. Sounds like compositor, try SHIFT+Alt+F12 if you encounter such and attach the output of "qdbus org.kde.KWin /KWin supportInformation" for wild guesses on why that may happen ;-) ---- Crash is dupe, exit reason might differ. *** This bug has been marked as a duplicate of bug 353624 *** |