updated yesterday to
Kernel: 4.1.6-3-desktop x86_64 (64 bit)
Desktop: KDE Plasma 5.4.0
Distro: openSUSE 20150903 (Tumbleweed)
using yast
booted ok to gui after removal of packages
< libKF5Baloo1-5.9.2-2.1.x86_64
< libKF5BalooXapian1-5.9.2-2.1.x86_64
< libKF5WaylandClient5-5.3.2-1.1.x86_64
< libKF5WaylandServer5-5.3.2-1.1.x86_64
yast gui worked ok after installing
> libmysql56client18-5.6.26-1.1.x86_64
So you selected the packages to update manually? You made a mistake then.
booted ok to gui after removal of packages
< libKF5Baloo1-5.9.2-2.1.x86_64
< libKF5BalooXapian1-5.9.2-2.1.x86_64
They should have been replaced by libKF5Baloo5.
< libKF5WaylandClient5-5.3.2-1.1.x86_64
< libKF5WaylandServer5-5.3.2-1.1.x86_64
Those should have been replaced by kwayland.
Running “zypper up” or “zypper dup” should have done the “right things” automatically…
yast gui worked ok after installing
> libmysql56client18-5.6.26-1.1.x86_64
I don’t see why YaST should depend at all on libmysqlclient…
yast made the update selection!
They should have been replaced by libKF5Baloo5.
after the original yast update both libKF5Baloo1-5.9.2-2.1.x86_64 and
libKF5Baloo5-5.13.0-1.1.x86_64 were installed
Those should have been replaced by kwayland.
Running “zypper up” or “zypper dup” should have done the “right things” automatically…
kwayland was installed by zypper up but missed by updating with yast No change was made for repos selection
I don’t see why YaST should depend at all on libmysqlclient…
before libmysqlclient18-10.0.20-1.1.x86_64 was installed yast gui could not be started
although yast ran ok from a terminal. No idea why unless it was a timing issue
Thanks for the feedback
Hm? Since when does YaST automatically select updates to install?
Only YaST->Online Update does this, but that doesn’t work at all on Tumbleweed, as there are no updates in the update repo.
after the original yast update both libKF5Baloo1-5.9.2-2.1.x86_64 and
libKF5Baloo5-5.13.0-1.1.x86_64 were installed
That shouldn’t really be possible. libKF5Baloo5 obsoletes libKF5Baloo1.
I think you should not even be able to force having both installed.
Unless you hit a bug.
kwayland was installed by zypper up but missed by updating with yast No change was made for repos selection
Well, that’s how it is in Tumbleweed.
Packages might get renamed or replaced by others.
Again, “zypper up” or “zypper dup” should do the correct thing.
If you use YaST, you have to do it manually (and know what you are doing), there is no “YaST->Update” or similar.
before libmysqlclient18-10.0.20-1.1.x86_64 was installed yast gui could not be started
although yast ran ok from a terminal. No idea why unless it was a timing issue
I have no idea either. Maybe libmysqlclient pulled in something else you were missing/didn’t update
This is just a comment for comparison.
I did
# zypper dup
to update to 20150903. As far as I know, everything is working. Previously, Plasma would crash during logout, but that seems to have been fixed in 20150903.
By yast “auto” update the following was meant,
-yast --Software Management —Package ----All Packages -----Update if newer versions available ------Accept
ps. not boot problems when iceWM selected
Hm, then this apparently doesn’t properly respect the package Obsoletes and doesn’t replace the old packages by the new ones (that are named differently) automatically. Might be worth a bug report I suppose.
Still, it shouldn’t allow to have both libKF5Baloo5 and libKF5Baloo1 installed.
Did you get any conflict resolution dialog?
ps. not boot problems when iceWM selected
Since the reason were wrong/obsolete KF5 packages installed, it’s not to be expected that IceWM would also have problems.
zypper is vary rarely used. Its always been assumed that zypper and yast work with the same repos for updating hence the effect should be the same.
There were no anomaly reports during installation. There were loss of error messages during initial booting, until the package changes as described above.
PS. another couple of points,
On 2015-09-06 17:56, wolfi323 wrote:
>
> keellambert;2727174 Wrote:
>> -yast --Software Management —Package ----All Packages -----Update if
>> newer versions available ------Accept
> Hm, then this apparently doesn’t properly respect the package Obsoletes
> and doesn’t replace the old packages by the new ones (that are named
> differently) automatically. Might be worth a bug report I suppose.
IMO, YaST is not designed to update Tumbleweed at all.
Maybe instead choose “update unconditionally” instead of “if newer”.
However, there is, or there was, a YaST module named “factory update”.
This one, if it is still correctly maintained, should (might) be able to
upgrade Tumbleweed.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Just because they use the same repos, doesn’t mean they do the same.
Even the effects of “zypper up” and “zypper dup” can be/are different.
There were no anomaly reports during installation. There were loss of error messages during initial booting, until the package changes as described above.
Hm. No idea then.
As mentioned, IMHO it should not be possible to have both libKF5Baloo1 and libKF5Baloo5 installed at the same time.
- synaptiks was auto deleted by yast, no problem as the touchpad is still disabled when the mouse is detected
Synaptiks is a KDE4 settings module, and something similar is now included in Plasma5 itself (plasma5-desktop).
- on a few occasions during booting the sound card detection takes >20secs to be setup, this only occurs randomly, usually its <2secs.
No idea.
Are you sure it is the soundcard detection itself?
systemd-analyze should tell.
I’d became quite fond of the Plasma “crash - restart - logout | shutdown” 
It’s still not particularly elegant… although the crash appears to have been fixed, I now get a black screen with only the mouse cursor until either, after a few seconds, the sddm login screen reappears or the machine shuts down.
This was certainly quite a “fun” update, as with the OP, I had used “-yast --Software Management —Package ----All Packages -----Update if newer versions available ------Accept”. After which KDE failed to start, after entering the user password the loading progress indicator would reach approx 80% then stall with no further activity.
Having little to lose I tried a “zypper up” which, after installing 3 more packages (didn’t note which), KDE was able to start. Unfortunately it also replaced “baloo-file” with “baloo5-file” and (again, again) lost metadata display within Dolphin for non indexed files.
Other “strange things” I’m now seeing:
Yast now shows a generic “gear” icon in the task manager.
After initial login I have to toggle compositing (ctrl-alt-F12) off and on to restore transparency to the panel.
(This one I really like…) The first time I press the shift key on the keyboard, it switches off NumLock; took me a little while to spot that one… wondered why my passwords weren’t being accepted.
Well, at least the digital clock and calendar should now have the options you asked for… 
Having little to lose I tried a “zypper up” which, after installing 3 more packages (didn’t note which), KDE was able to start. Unfortunately it also replaced “baloo-file” with “baloo5-file” and (again, again) lost metadata display within Dolphin for non indexed files.
KDE Applications 15.08.0 (including dolphin5 and baloo-widgets5) have been submitted to Factory/Tumbleweed 2 weeks ago, and should be in one of the next snapshots.
Other “strange things” I’m now seeing:
Yast now shows a generic “gear” icon in the task manager.
Maybe the icon is missing in the yast2-control-center package?
After initial login I have to toggle compositing (ctrl-alt-F12) off and on to restore transparency to the panel.
The panel should not be transparent at all (or only slightly) in the Breeze theme I think.
But try to delete the theme cache ~/.cache/plasma*.
(This one I really like…) The first time I press the shift key on the keyboard, it switches off NumLock; took me a little while to spot that one… wondered why my passwords weren’t being accepted.
Definitely unrelated to Plasma5.
But I see the same in 13.2/KDE4 if I play around with the keyboard layout settings, and also in IceWM when I run setxkbmap to change the layout.
Are you using the default system layout set in YaST, or did you override it in KDE’s settings?
PS: I never had Plasma5 crashing on logout here on 13.2…
It is still available, if you install Leap 42.1 Milestone 2 
It’s still not particularly elegant… although the crash appears to have been fixed, I now get a black screen with only the mouse cursor until either, after a few seconds, the sddm login screen reappears or the machine shuts down.
It seems that “sddm” has a long startup time. I usually switch to “lightdm”, though I am leaving “sddm” on one system.
I haven’t noticed your other issues.
And I’m still waiting for kwalletmanager5 (or whatever it is called) to show up. I had thought we would get that with this update, but it still isn’t there.
This was exactly my experience with the upgrade. I used Software Management, and after the reboot to activate the updated kernel KDE stalled at 80% and died. A quick switch to the console via CTRL+ALT+F1 followed by using zypper up and I had one package to remove and two to install. After completing that and rebooting again, KDE logged in as normal.
kdm is still an option too.
And I’m still waiting for kwalletmanager5 (or whatever it is called) to show up. I had thought we would get that with this update, but it still isn’t there.
Well, kwalletmanager5 is part of the KDE Applications 15.08.0 update (like dolphin5 and baloo-widgets5), but that’s still stuck in staging for some reason.
You can install it from KDE:Applications (the devel project for Factory/Tumbleweed) though if you want it now.
http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Factory_standard/
The same applies to dolphin5 and baloo-widgets5…
Yes…
Maybe the icon is missing in the yast2-control-center package?
Haven’t investigated, but I think there could be more to it than that… Gimp is also now showing the ‘Gear’ icon, as is ‘Digital Clock Settings’
The panel should not be transparent at all (or only slightly) in the Breeze theme I think.
But try to delete the theme cache ~/.cache/plasma*.
I’m not using Breeze, the desktop theme is ‘Air openSUSE’ with ‘Oxygen’ window decorations.
This is what I’m seeing:
At initial login the panel has a solid white background - http://paste.opensuse.org/c2e3ab06
After toggling compositing off I get a solid white background but with funky miniature icons - http://paste.opensuse.org/51a6096c
Toggle compositing again and I get the correct translucent background - http://paste.opensuse.org/fe6430e7
I’d tried deleting the cache files, that made no difference…
Definitely unrelated to Plasma5.
But I see the same in 13.2/KDE4 if I play around with the keyboard layout settings, and also in IceWM when I run setxkbmap to change the layout.
Are you using the default system layout set in YaST, or did you override it in KDE’s settings?
Unrelated to Plasma5 may be the case but this definitely started after this last snapshot update, don’t know which package may have caused it. I’ve not made any changes to the keyboard settings.
PS: I never had Plasma5 crashing on logout here on 13.2…
I was seeing it consistently… at logout or shutdown the crash reporter would briefly show (segfault) then Plasma would restart and logout or shutdown correctly…
Hm, I hope that’s not related to my patch that reads translated .desktop file strings from the package desktop-translations (to fix translations of menu entries).
It’s mainly a port of the already existing patch from KDE4, which somebody else wrote years ago.
For some reason, it changes the reading of the icon too, I did wonder about that, but thought it should be ok.
OTOH, those icons display fine here in 13.2 with the same patches (in both KDE4 and Plasma5).
I’ll have a look, but it will take some time as I don’t have a current Tumbleweed installation at the moment.
You might try to run “kbuildsycoca5 --noincremental” though, maybe that “fixes” it…
I’m not using Breeze, the desktop theme is ‘Air openSUSE’ with ‘Oxygen’ window decorations.
This is what I’m seeing:
At initial login the panel has a solid white background - [http://paste.opensuse.org/c2eI’m not using Breeze, the desktop theme is ‘Air openSUSE’ with ‘Oxygen’ window decorations.
This is what I’m seeing:
At initial login the panel has a solid white background - ](http://paste.opensuse.org/c2e3ab06)http://paste.opensuse.org/c2e3ab06
After toggling compositing off I get a solid white background but with funky miniature icons - http://paste.opensuse.org/51a6096c
Toggle compositing again and I get the correct translucent background - http://paste.opensuse.org/fe6430e7
3ab06
After toggling compositing off I get a solid white background but with funky miniature icons - http://paste.opensuse.org/51a6096c
Toggle compositing again and I get the correct translucent background - http://paste.opensuse.org/fe6430e7
Well, then maybe kwin might not turn on compositing correctly on startup, or Plasma doesn’t detect that it’s on correctly. (timing issue maybe? I.e. Plasma checking the state before Kwin actually started or turned compositing on?)
I did experience the same problem in KDE4 for a while (4.8 or 4.9 I think)…
You might want to file a bug report at KDE.
The small icons seem to be another bug.
I will try to reproduce both issues here (on 13.2).
But if it is a timing issue, I don’t expect that I can really.
Unrelated to Plasma5 may be the case but this definitely started after this last snapshot update, don’t know which package may have caused it. I’ve not made any changes to the keyboard settings.
There have been some changes to how the keyboard layouts are generated/installed. Maybe this is related?
More an issue with the X11 keyboard layout or something else in Xorg though.
You are using the US layout? Did you set it explicitly in KDE’s settings, maybe also an alternate layout?
Btw, there is a setting in KDE’s Keyboard settings (“Advanced” tab) that controls whether Shift turns off Caps Lock or not. Maybe that’s activated for some reason?
(actually those are Xorg setting, coming from xkeyboard-config)
I was seeing it consistently… at logout or shutdown the crash reporter would briefly show (segfault) then Plasma would restart and logout or shutdown correctly…
Well, as I said, I never saw this on 13.2.
I do run Tumbleweed in a VM from time to time, but don’t remember seeing it there either.
But something like that might have a variety of reasons, from problems/incompatibilities with a particular graphics driver to some broken/buggy plasmoid you use.
A back trace might give more hints to what’s causing it, or maybe not.
One quick additional note just to avoid a misunderstanding here:
The “Breeze” icon theme contains a replacement icon for GIMP. So it is “normal” that you don’t see the standard GIMP icon on a default Plasma5 desktop.
That’s not the case for YaST though.
What icon theme are you actually using? Breeze doesn’t show a “gear” for missing/broken icons, and not even for executable files…
And regarding “Digital Clock Settings”: do you mean the icon is missing in the right-click context menu of the plasmoid, or in the settings window itself?
Turning on/off Compositing does not change the icon size here btw.
No difference, but there was some interesting(?) terminal output:
paul@Orion-Tumble:~$ kbuildsycoca5 --noincremental
kbuildsycoca5 running...
Recreating ksycoca file ("/home/paul/.cache/ksycoca5", version 300)
Menu "suse-screensavers.menu" not found.
Menu "kde-settings.menu" not found.
"Directory" and "suse-yast.directory" requires combining!
Menu "custom.menu" not found.
Saving
Emitting notifyDatabaseChanged ("services", "servicetypes", "xdgdata-mime", "apps")
paul@Orion-Tumble:~$
You might want to file a bug report at KDE.
Yes, I’ll do that later today, against kwin?
…
You are using the US layout? Did you set it explicitly in KDE’s settings, maybe also an alternate layout?
Btw, there is a setting in KDE’s Keyboard settings (“Advanced” tab) that controls whether Shift turns off Caps Lock or not. Maybe that’s activated for some reason?
(actually those are Xorg setting, coming from xkeyboard-config)
en-GB - I don’t recall setting that anywhere apart from Country / Keyboard during the initial install of TW. Within KDE there is no alternate layout set. The only setting I’ve changed is to explicitly set the keyboard model. I did note that “Numlock On” is also set here, I don’t know if that is default or if I changed it.
Under the “Advanced” tab the only setting active is “Key sequence to kill the X server”.
This is rather odd in as much as it only happens on initial boot, if I log out/in the shift key does not change the NumLock state.
I have NumLock set to “On” in the BIOS, so the sequence is as follows:
Boot - NumLock On
Grub - NumLock remains On
Kernel Loading - NumLock Remains On
SSDM - NumLock remains On
KDE start - NumLock Off then Immediately On
NumLock remains ON until the first press of the Shift Key whereupon it switches OFF
Curiously, it then requires the NumLock key to be pressed twice to switch back ON.
Knowing it now has this odd behaviour I’ll live with it and hope that a future update ‘cures’ the problem.
Well, as I said, I never saw this on 13.2.
I do run Tumbleweed in a VM from time to time, but don’t remember seeing it there either.
But something like that might have a variety of reasons, from problems/incompatibilities with a particular graphics driver to some broken/buggy plasmoid you use.
A back trace might give more hints to what’s causing it, or maybe not.
Since the last update it no longer crashes at logout/shutdown… Further up the thread “nrickert” indicated that it happens still with “Leap 42.1 Milestone 2”.
With regard to Gimp, I apologise, must pay more attention. The Gimp icon appears for the main window, the “Gear” icons are appearing for the secondary (Gimp) windows, “Tool Options”, “Pointer”, etc. http://paste.opensuse.org/66b8ba8d
What icon theme are you actually using? Breeze doesn’t show a “gear” for missing/broken icons, and not even for executable files…
“Oxygen Ionised” http://kde-look.org/content/show.php/Oxygen+Ionized+(Oxygen+green)?content=149460 (which I have added quite a lot of custom icons of my own to).
And regarding “Digital Clock Settings”: do you mean the icon is missing in the right-click context menu of the plasmoid, or in the settings window itself?
Sorry, should have made that clear… The actual settings window.