13th November 2016, 4:45
(12th November 2016, 21:23)rocky7x Wrote: Hi kdemeoz,
Can you please check after you manage to boot via recovery, go to system settings -> workspace behavior -> compositor and check if you have opengl active or just Xrender? I ask because after googling a bit, when this happens and you are able to start the desktop only via recovery, there is a problem with graphics card or driver - it is not able to start compositing.. just check what you have after booting..
Hi rocky. Yes it was a good idea & one that also occurred to me soon after this strange bug commenced. I have checked several times since then [including just as i began this reply], & each time, Compositing is still on my OpenGL 3.1 setting [this is after doing the recovery fsck boot option btw; the only way now i can boot].
Here's something a little strange as well. My usual behaviour at day's/night's end, once i need zzzzzzzzzz, is to Suspend my Tower, not Shutdown, & then Resume it the following morning. Hence, in a way, some might argue that my anxiety over this recent problem is unwarranted, if i hardly ever have to do an actual boot [but for me, my anxiety is justified, as something must have changed / gone wrong, & that can't be a good thing]. Anyway, until a couple of days ago [that i can remember], after each morning's Resume, my previous night's plasmashell desktop with all active windows on all my VDs would correctly return & all compositing [eg, desktop effects] would be good & fine, BUT the Cairo-Dock [which uses OpenGL] icons would all be broken [they still worked correctly if i clicked them, but their icons/emblems were missing or pixelated]. To fix it each time i had to stop & start CD.
However for the past couple [that i can remember] of mornings' Resumes, everything is good... including CD. I can only definitely certainly recall the past couple of days that this new behaviour is true, but it is possible this new behaviour might actually have begun when the main bug arose of no normal boots possible, hence the recovery option needed. I cannot explain this, & it might be a mere coincidence unrelated to the recovery boot, but thought i'd mention it in case it gave anyone any fresh ideas.
Golly this is all so weird!