SLED 12... Is it really as broken as it feels?

This is mostly a rant, but I’m hoping someone out there will see some of my rants and have an idea about how I’m doing something wrong/stupid and tell me the right way to do it. SLED 12 just seems broken. I really wish I would’ve stuck with SLED11 as I’ve never had any significant issues with it.

  1. The combination of VMWare Workstation and life (especially browsers) are incompatible. We have a few installed of VMWare Workstation 11 (started with 10, same problems) and things randomly freeze - badly. This is especially true if you have a browser open. Firefox is the worst, but Opera 28 does it as well. The same hardware running SLED11 and Workstation 10 had no such problems.
  2. The repositories are broken. Currently, there are 17 extensions for ant available in SLE-SDK12-Pool… but no package for ant itself. java-1_7_0-openjdk-devel seems to be missing. There have been a couple of other strange omissions from the repositories, but these are the two I can remember off hand.
  3. The audio subsystem seems broken. The default path reverts back to… whatever instead of remembering your changes. There’s also an issue with pidgin changing system volume. (which appears to be an upstream bug originally reported in 2013)

There are random other quirks that our users keep finding, most of them seem to be related to Gnome3, but it’s hard to tell.
In general, going from SLED9, 10 and 11 where you’d have a few minor annoyances here and there but overall a fully developed and stable platform to… this. If SLED12 were my first experience with SLED I would’ve never recommended anyone else use it… ever.
It just seems that there was no effort on SUSE’s (read: Attachmate’s) part to make sure they were delivering a polished product.

Can’t comment on that since I haven’t tried running VMWare Workstation on SLED 12 yet. I did have to downgrade from Workstation 11 to 10 on SLED 11 SP3 though due to a problem with VMs not letting go of mouse/keyboard focus though. Never saw the problem with 10, haven’t seen it since I downgraded to 10.

The SDK is accompaniment to both SLES and SLED and as a result contains packages that are installable on SLES but not SLED. The same is true on SLED 11 SP3. (I just tried installing all packages in the 11 SP3 SDK. I got through 50 packages zypper couldn’t install due to missing dependencies before I got bored of select ‘do not install’.) I guess there is a debate which could be had about how…helpful… it is to offer people a repo that contains packages they cannot install. ant is in the 11 SP3 SDK though and installable on SLED 11 SP3.

Url(s) for the bug?

Are you using the SLE-Classic mode of GNOME 3 that SUSE created for SLED 12? If so it might be interesting to see if the quirks occur under GNOME Classic or GNOME.

If you encounter reproducible issues, tell SUSE. If you can, raise Service Requests, if not use

I’m assuming that SUSE felt that ant and the jdk development packages
where more likely to be used at the server level rather than desktop
since the packages are both present on SLES 12, or just an oversight
(probably worth an SR or bug).

Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

I understand how the SDK works. If the base packages are in the SLES iso, I’ll gladly chase them down to get things working.

The bugs listed are specific Knotify/Kmix
Bug at KDE:
Bug at Redhat:

However, it seems that it’s really an issue with pulseaudio and they’re trying to work around it.

I was using SLE-Classic. I switched to GNOME Classic today but didn’t have VMWare Workstation open much, so over the next couple of days I’ll see if it resolves my freezing before changing anyone else.

Will do.

I’m assuming that SUSE felt that ant and the jdk development packages
where more likely to be used at the server level rather than desktop
since the packages are both present on SLES 12, or just an oversight
(probably worth an SR or bug).
Which seems silly to me, since I prefer to do development on my workstation before moving it to a server, but as I said above… if I can scavenge the packages from the SLES iso I can make due.

Most of the things we’ve run into are just annoyances that really add up to make the end product feel unfinished compared to the past few versions of SLED. I’ll continue hoping that SP1 (and maybe a change away from SLE-Classic) fixes most of them.

The state of vinagre/xfreerdp/tsclient is another thing that’s quite annoying.
You can install tsclient from the repos, but not rdesktop (required). Vinagre doesn’t really front-end XFreeRDP well without calling Vinagre from CLI (to approve certs and enter passwords).

After a few days of working, GNOME Classic seems to resolve the issues with VMWare Workstation completely.