Wow …
I just experienced a genuine microsoftish moments on my Leap 42.1 box, with your most recent update for KDE framework = plasma 5, right ?
I had a popup indicating I have some updates, I simply click on it to let them install … and after a reboot (considering there were tons of packages of plasma 5 replaced with a newer version, I thought this would be the necessary step, despite it was not mandatory), plasma 5 simply would not complete it’s start !! It just stayed at about 1/3 in the splash screen (mouse working of course, but it was the only thing working at this point). No errors on screen, nothing; just a lengthy, almost like frozen screen (it was not frozen, because mouse was moving all right) that never came to any end; as I wrote above, the splash screen bar was frozen at about 1/3 from it’s total length.
So … I wonder, didn’t you guys even tested it at all ?!?
Now, I finally succeeded to revert, after a painful search for the modified packages (luckily, option “Show history” from the menu “Extras” in Yast2 was a very good friend – I would make a few examples: kded, kpackage, kconf, baloo*, libKF5* (these are really a tone :-), kcore, kglobal and many, many others) to their previous version; the bad (new) version is something as 5.19.0; the current working version is 5.16.0.
And now I’m on the working-good plasma5 desktop.
But … update notification piece of software is coming again with this update(s) – as I see them now they are updates named “openSUSE-2016-264” for KDE applications stack and “openSUSE-2016-287” for kde frameworks.
Obviously I won’t give them permission to run again, at least at this point.
Can anyone explain what happened with all these new packages ?
at this moment (my local hour here is 8:30 GMT+2 ) updates were done successfully this time.
Granted, now I saw a new one available: 4723 – for libqt5-qtbase, besides those openSUSE-2016-287 and openSUSE-2016-264 from yesterday try.
Successfully means that now plasma5 works very well after this update
Yes I too had this problem and used a read-only rollback data-set and re-booted and then ran this command ‘snapper rollback’ & rebooted back to ‘safety’
My only concern is do I continue un-check fix ‘openSUSE-2016-287’ for future updates? - and how do I know when the fix for this is fixed?
It is fixed already, as the OP wrote directly before your reply.
The problem was that the necessary Qt5 update was released a few hours too late although it had been submitted earlier.
There is (and was) nothing wrong with the ‘openSUSE-2016-287’ update itself.
The OP said it correctly. My desktop is now a mess. The look/feel has changed radically (breeze desktop and opened windows appear ‘electric’ - if that means anything) and the panel at the bottom of the screen is much bigger than usual and the lower edge is off the screen and I cannot raise it. My 4 panel pager only shows the top 2 panels as a result of this (as does the digital clock, showing only the top 1/2 of time). The screen has expanded slightly and 25% of the icons at left side are off screen. I have adjusted it’s height & width as best I can but still missing the lower 1/2 of it. FWIW, display is using fglrx.
I did the online update referred to upthread, there is no change to my messed up system. I have libqt5* versions 5.5.1-10.1 and no update indicated.
I’ll wait a bit for suggestions but I can’t work with this mess. Later today I will probably be reverting to my last snapshot, which I presently have no idea how to do and will have to research it. Would like to know where to find the necessary info on that.
Hm?
The OP said that “plasma5 works very well after this update” after installing the libqt5-qtbase update.
The look/feel has changed radically… and the panel at the bottom of the screen is much bigger than usual and the lower edge is off the screen and I cannot raise it.
…
But that’s clearly a completely different problem, isn’t it?
Have you tried a fresh user account to rule out a problem with user settings or caches?
Would rather sound like a graphics driver problem to me though, not related to the KDE update.
(breeze desktop and opened windows appear ‘electric’ - if that means anything)
Not really, at least I don’t understand at all what you mean with that.
Oddly, if I take a screen shot the panel shows itself fully, as it should show.
Hm, that would sound that “just” the display is wrong.
Does it help if you disable compositing via Shift+Alt+F12 (and maybe re-enable it again afterwards via the same keyboard shortcut)?
If not, I would suggest as a first step to clear the caches, i.e. delete ~/.cache/ (at least the plasma* files in there).
Or delete ~/.local/share/kscreen/, this contains the monitor settings.
Logout and login afterwards for any effect.
If that doesn’t fix it: wiping out all user configuration by deleting ~/.config/ should help in any case then I suppose, but probably the kwin* or plasma* files in there (deleting the latter ones would of course revert your desktop setup to the defaults) would be enough too. But you should preferably do that while Plasma is not running, i.e. logout and choose “IceWM” at the login screen e.g.
Shift+Alt+F12 did not appear to make any difference, I was unable to determine if anything happened, except Firefox flashed when I pressed that key combo. When I pressed it again I saw no changes either.
Recalling that compositing is a selection is settings in System Settings -> Display & Monitor, I disabled compositing on startup and logged out.
Logging in displays the entire panel in the properly anchored to the lower edge of the screen. I re-adjusted the height & width and all is well now.
The problem I mentioned with the ‘electric’ appearance of open windows has also gone away.
I seem to recall having a similar problem here (on one of my computers).
I know what cause it. To a first approximation, the monitor was switched off during startup, so the software did not get the right information about the monitor parameters.
In more detail, the computer is connected to a KVM switch. I logged into Plasma 5, but toggled the KVM switch to the other system while Plasma 5 was coming up. And the result was the kind of mess you described.
And it stuck. Logout and login didn’t fix it.
I fixed it by deleting desktop settings files (roughly, files with names beginning “.”), and made a fresh start with Plasma 5. And, since then, I’ve been careful about when I toggle the KVM switch.
Well, as it seems to have worked on a fresh user account, you could try to turn it on again.
Although I don’t know whether it was actually enabled on the fresh user account or not, kwin might have turned off compositing automatically on first start if it recognized problems…
THANKS!
You’re welcome.
Great to hear that it’s “fixed” now.
Logged out and back to test user just to confirm status of compositing. In new test user compositing is Enabled.
Then logged out of new user and back to myself, and what is this??? Same problem of panel positioning and icons too far to left and partially off screen, and that ‘electric’ look (by which I mean very bright and washed out window backgrounds).
Checked compositing and it is disabled. I tried alt-shift-F12 and no change.
I’ll try rebooting and if no luck I’ll re-enable the compositing again and see what happens.
re: nrickert KVM comment. I don’t have a KVM but the ‘monitor’ is a digital TV used as a monitor. It has an HDMI connection to video card.
No change in my problem from a fresh boot. Compositor still off.
My monitor ‘optimal’ resolution is 1920x1080 @ 60hz. I’m starting to wonder about the fglrx driver. Several months ago I removed the fglrx driver but the result was so poor that I re-installed it after several weeks.
Using AMD Control Center (installed by fglrx) I changed the resolution to 1680x1050 and the problems all went away and other than a lower resolution, all is fine now.
I have not shut off my monitor in all of my different changes. Later today I’ll reset the resolution back to 1920x1080 and shut down the system and monitor and see what happens on the next boot.
Commenting on my last post, further info on my problem. I shutdown my system for a few hours, at that time I had compositing Disabled and AMD Catalyst selected for 1680x1050. When I started up my problem appeared. Checking Catalyst I found the resolution had reset itself to 1920x1080. I did not change it in System Settings so this is probably why the resolution did not ‘stick’.
I checked again the new user profile I created and it works fine at 1920x1080 and compositing Enabled.
If there are no other ideas about this I will need to consider deleting ~/.cache/ files and see if there is an improvement.
) updates were done successfully this time.