On my ASUS K52F laptop I have the standard Leap42.2/KDE install, fully updated (Kernel 4.4.70-18.9-default). Occasionally it happened that after booting up all the windows come up without title bar and sometimes even the file - quit menu didn’t work. I either used Ctrl-Alt-Backspace and logged in again or, mostly I rebooted and then the computer came up alright and everything worked. Today I tried 5 times to reboot and always I had this situation that I had no title bars and only limited functions. I tried several things like booting into the previous kernel, all to no avail. I had a look at some of the log files but I could not see something obvious. What can cause this problem and how can it be fixed? Any assistance is very much appreciated. CHeers Uli
Have a look at the compositor render settings, you may have to switch them from openGL to Xrender or vice versa
Systemsettings - Display and Monitor - Compositor
Thank you, Knurpht, but it was hard to find this. When I go to System Settings -> Display and monitor I only find Screen Locker Settings and Screen Locker Type. In command line I typed systemsettings5 and there were the options: OpenGL2 (which was selected), OpenGL3.1 and XRender. What would you recommend for what reasons? The other thing is that normally (let’s say 95% of the time) displaying correctly and then suddenly misbehaving so if I change things and it works alright for some time that does not necessarily mean that the problem is solved. In which log file would I find something - I looked through messages and warn and didn’t find anything suspicious.
Any .xsession-errors evident? I wonder if restarting plasmashell from a terminal might yield clues…
Is kstart5 the replacement for startx which AFAIK is only for root? I have not used this command. But I will try next time. I don’t understand much of the link you supplied - sorry.
The file .xsession-error is empty but this are the last lines of .xsession-errors-:0 (I don’t know what this means either)
QXcbConnection: XCB error: 3 (BadWindow), sequence: 45903, resource id: 102760615, major code: 18 (Chang eProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 45904, resource id: 102760615, major code: 12 (Confi gureWindow), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 46183, resource id: 100663300, major code: 18 (Chang eProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 57942, resource id: 100663296, major code: 18 (Chang eProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 57946, resource id: 100663297, major code: 18 (Chang eProperty), minor code: 0 kf5.kio.core: KLocalSocket(0x18d7270) Jumbo packet of 33056 bytes ** (firefox:2484): WARNING **: Invalid borders specified for theme pixmap: /usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png, borders don't fit within the image uli@linux-tl1r:~>
No just use the commands as user within your KDE session.
I don’t understand much of the link you supplied - sorry.
Well, it was just a reading guide to help with general debugging. I don’t have issues with Plasma 5 that require any such debugging. (I was just offering general advice really.)
I’ll leave others to comment further about your xsession errors.
The window title bars (and compositing) are done by kwin though, not plasmashell.
To restart it:
The posted “error” comes from the breeze GTK2 theme though and is definitely unrelated.
The XCB errors could be anything, and don’t have to be a problem either.
Thank you, wolfi323, I will try this next time. Today computer was running OK again right from start. Cheers Uli