Luigi Toscano <luigi.toscano@xxxxxxxxxx> wrote on 07.01.2016 11:20:12: > I can't reproduce the problem on a single monitor up-to-date F23, so plasma > 5.5.1 (but I'm not using the default Breeze-based set of themes), > using OpenGL 3.1/GLX for the compositor. > I would suggest to play with the configuration On my up-to-date F22, the choice of Compositor Settings does not make any difference (I tried OpenGL 3.1/GLX as well as OpenGL 2.0.). Besides, XRender is still the only rendering backend that works reasonably well with intel + nouveau. The konsole issue was clearly introduced when I upgraded to Plasma 5.5.0 and KDE frameworks 5.17 on 17. Dec. However, the updates-testing repo is already at Plasma 5.5.1 and KF5 5.18, and another thread (see subject "KDE 5.5.2- thanks") suggests that 5.5.2 (in repo kde-testing) is even more stable. I suspect that we are chasing some transient bugs here, which is not very productive ... Could someone using Plasma 5.5.1 or 5.5.2 or KF5 5.18 report whether the konsole hang exists for them? > at least try with the single monitor. Interestingly, LVDS only does not currently work for me, but that's another problem: When I boot my laptop with LVDS only (external monitor not connected to DP), Plasma comes up briefly at KDE login, but then it crashes, and there is no X at all. In /var/log/Xorg.0, I see [ 287.125] (EE) intel(0): sna_mode_check: invalid state found on pipe 0, disabling CRTC:21 so I suspect that X is confused when the intel and nouveau drivers are both loaded (which is the case), but there is no external monitor to drive. Who knows, for LVDS only, I might need to blacklist the nouveau driver ... (This is with kernel 4.2.8-200, I don't think this problem existed with kernel 4.1.3). Thanks, Fredy _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/kde@xxxxxxxxxxxxxxxxxxxxxxx
