Yes, I had that problem with konsole5. I also had it with konqueror in 13.2.
There’s something broken in font setup.
Go into the settings. See what font is used. Change it to something else and save the change. Then change it back and save the change.
Somehow some applications are not using the font that they say they are using, when they get that font from system defaults. If you explicitly set that font in your own user settings, then they do use it.
Well, how would you know how the default font would look like if you don’t have it installed?
konsole still has a cursor jumping ahead of the text in Plasma 5. zypper al konsole.
That’s exactly what happens if you don’t have the default Oxygen fonts installed. For some reason it uses a proportional font then which causes this problem and treats it as non-proportional.
Again, either install them (kde-oxygen-fonts), or set a different, non-proportional font in the settings.
I am only aware of this problem with the KDE4 based Konqueror. (you reported it as bug, didn’t you?)
For KF5 based applications it’s more likely that the system default font (Oxygen) is not installed I think. If you change the font settings, you set an existing font though, so it works afterwards.
I have seen that konsole5 problem when I first installed/used it over a year ago. Installing the Oxygen fonts fixed it immediately, without changing any font settings. The mentioned Konqueror4 problem seems to be different…
It’s been about five weeks since I have been using openSUSE. Basically, I wanted a posix environment that did not use cygwin.dll.
As I said, I rolled back everything and removed all KF5 libs. But now I installed konversation by unlocking KF5 and seeing which libs it needed. Then I zipper locked libKF5* again.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+------------------------+--------------------------------------------------------------------+--------
i | libKF5Archive5 | Qt 5 addon providing access to numerous types of archives | package
i | libKF5Attica5 | Open Collaboration Service client library - development files | package
i | libKF5Auth5 | Framework which lets applications perform actions as a privilege-> | package
i | libKF5Bookmarks5 | Lets you access and manipulate bookmarks stored using XBEL format | package
i | libKF5Codecs5 | Provides a collection of methods to manipulate strings using var-> | package
i | libKF5Completion5 | Provides widgets with advanced completion support | package
i | libKF5ConfigCore5 | Provides access to the configuration files themselves | package
i | libKF5ConfigGui5 | Provides a way to hook widgets to the configuration | package
i | libKF5ConfigWidgets5 | Widgets for configuration dialogs | package
i | libKF5CoreAddons5 | Utilities for core application functionality and accessing the OS | package
i | libKF5Crash5 | Gracefull handling of application crashes | package
i | libKF5DBusAddons5 | Convenience classes for QtDBus | package
i | libKF5DNSSD5 | Network service discovery using Zeroconf | package
i | libKF5Emoticons5 | Convert text emoticons to graphical emoticons | package
i | libKF5GlobalAccel5 | Global desktop keyboard shortcuts | package
i | libKF5GuiAddons5 | Utilities for graphical user interfaces | package
i | libKF5I18n5 | KDE Gettext-based UI text internationalization | package
i | libKF5IconThemes5 | Icon GUI utilities | package
i | libKF5IdleTime5 | Reporting of idle time of user and system | package
i | libKF5ItemViews5 | Set of item views extending the Qt model-view framework | package
i | libKF5JS5 | KDE Javascript engine | package
i | libKF5JobWidgets5 | Widgets for showing progress of asynchronous jobs | package
i | libKF5KDELibs4Support5 | Code and utilities to ease the transition to KDE Frameworks 5 | package
i | libKF5KHtml5 | HTML rendering engine | package
i | libKF5Notifications5 | KDE Desktop notifications | package
i | libKF5NotifyConfig5 | Configuration dialog for desktop notifications | package
i | libKF5Parts5 | Plugin framework for user interface components | package
i | libKF5Pty5 | Interfacing with pseudo terminal devices | package
i | libKF5Solid5 | KDE Desktop hardware abstraction | package
i | libKF5SonnetCore5 | KDE spell checking library | package
i | libKF5SonnetUi5 | KDE spell checking library | package
i | libKF5TextWidgets5 | KDE Text editing widgets | package
i | libKF5Wallet5 | Safe desktop-wide storage for passwords | package
i | libKF5WebKit5 | Integration of the HTML rendering engine WebKit | package
i | libKF5WidgetsAddons5 | Large set of desktop widgets | package
i | libKF5WindowSystem5 | KDE Access to window manager | package
i | libKF5XmlGui5 | Framework for managing menu and toolbar actions | package
i | libKF5XmlRpcClient5 | Library containing simple XML-RPC Client support | package
stephen@linux-lo2y:~>
After that several programs could be install all starting with the letter ‘k’, which I then locked except for kmix, which works better as plasma 5 than as a KDE4 version.
Sorry, try again.
root's password:
# | Name | Type | Repository
---+-------------------------------------+---------+-----------
1 | breeze | package | (any)
2 | patterns-openSUSE-kde_* | package | (any)
3 | patterns-openSUSE-sw_management_kde | package | (any)
4 | libKF5* | package | (any)
5 | kde4-print-manager | package | (any)
6 | ksshaskpass | package | (any)
7 | kcalc | package | (any)
8 | kcharselect | package | (any)
9 | kompare | package | (any)
10 | konsole-part | package | (any)
11 | kruler | package | (any)
12 | konsole | package | (any)
13 | libkpathsea6 | package | (any)
14 | libspandsp2 | package | (any)
15 | gcc | package | (any)
16 | MozillaFirefox | package | (any)
stephen@linux-lo2y:~>
Any way, it seem like a lot of libs for one application. But it is a gui internet client with spell check. My long term goal is to gradually update to Plasma 5.3 by August or migrate to 13.3 when it comes out. Whcih may be the same thing if 13.3 adopts Plasma 5. My goal was to see how far I can stretch things before they break and whether zypper can continue to keep me safe. And to learn more about zypper and to learn more about my new operating system. I retrospect, I don’t think I’ve done anything too extreme. For instance:
Wolfi: You suggested that I install 13.2 and just add packages from Tumbleweed as I wanted them. Well I installed Tumbleweed and use repos 13.2-update and 13.2-oss for versions that are not updated in Tumbleweed anymore as Tumbleweed drops support for KDE4. As long as one is mixing repositories, does it really matter which way one does it?
No, not really.
KF5 is split up in many small libraries, so that you can only install what you need. Unlike KDE4 where everything is in one (or actually two) “big” libraries/packages, libkde4 and libkdecore4.
This has been done to encourage non-KDE developers to use KF5 libraries.
And if you would use Plasma5 or other KF5 based applications (Kate/Kwrite, Konsole), you would have all that installed already anyway… 
Wolfi: You suggested that I install 13.2 and just add packages from Tumbleweed as I wanted them.
No, I didn’t.
I suggested to install 13.2 and then adding additional 13.2 repos for updating certain stuff.
Well I installed Tumbleweed and use repos 13.2-update and 13.2-oss for versions that are not updated in Tumbleweed anymore as Tumbleweed drops support for KDE4. As long as one is mixing repositories, does it really matter which way one does it?
Of course it does matter. If you add 13.2 repos to 13.2, stuff should work. If you add 13.2 repos to Tumbleweed, your system will probably break at one point. And having a mixture of Tumbleweed and 13.2 will not make it easier to find the reason for certain problems you might encounter.
Btw, I also provide all KDE4 applications that are ported to KF5 already in my repo, like Konversation konsole, and kwrite/kate, built for Tumbleweed.
I noticed that you did that and that is very good, still in practice we all want to pick between KDE4 and KF5 versions of our applications, but still use only one version for each application. At least that is true for me. But I suppose you did it for people who need a foot in each version. I just want a single release that isn’t an official release for a couple of months until the new versions are more mature.
At one point you pointed out that there is a lot I will never use. That is very true, I just want a console, a writepad, a browser, and multimedia capability to speak generically. My future project is to learn complex programs like kile, kate, and kdenlive; and advanced uses of sed, flex, and bison. Well, I should learn rpm. I shouldn’t know zypper so well and still not know anything about rpm.
Well, if you want the KF5 version of an installation, install the one included in Tumbleweed. If you want to stay with the KDE4 version, you can take it from my repo.
That said, I don’t really see a point in keeping the old, obsolete, unmaintained KDE4 versions for applications that have been released as KF5 version already. The KF5 versions are the official successors, and the only ones still maintained. And they are not rewritten from scratch or anything like that, they are ports of the KDE4 versions, sometimes even with new features already.
And also KF5 itself is basically just a port of kdelibs4 to Qt5 (although some parts have been moved to Qt itself where it made sense). And it’s available for about a year already, and Qt5 had its first release in 2012…
Still, it might make sense to keep certain KDE4 applications if you want to continue to use KDE4’s desktop. The KF5 versions install the files to different locations, so you won’t see e.g. ServiceMenus and device actions in KDE4.
At least that is true for me. But I suppose you did it for people who need a foot in each version.
Actually I started with my repo before 13.2 has been released. At first, it was mainly intended to be able to try out Plasma5, without having to switch completely to it (at that point it wasn’t really ready for general use either). I also started to add development snapshots of KF5 applications, but I switched them to the stable release as they became available (which are in Tumbleweed anyway).
Quite a few are not released yet as KF5 versions though. So my repo still makes sense to be able to try them as well.
I just want a single release that isn’t an official release for a couple of months until the new versions are more mature.
The “new” versions are mature. They are stable (upstream) releases after all.
Well, I should learn rpm. I shouldn’t know zypper so well and still not know anything about rpm.
Not really necessary I suppose.
In the end zypper just runs rpm to do the work…
This is why I don’t appreciate it when Tumbleweed is called the bleeding edge. Everything gets tested in Factory prior to Tumbleweed and there is probably more testing than that. The release philosophy is still pretty conservative compared to other rolling releases, or so I thought. I never tried apt-get, but I don’t want to. Now I think rpm based distros are the way to go.
Well, it does contain the latest stable releases of all (or most) software included.
So maybe not really “bleeding edge” (that was more fitting for the old Factory), but not far from it either.
Everything gets tested in Factory prior to Tumbleweed and there is probably more testing than that.
Well, not everything gets tested…
openqa only tests things somebody wrote a test for.
Most importantly it tests that the system boots after installation or upgrade and gets to a graphical desktop.
Tests are being added all the time I suppose (or at least they can be added), but you can never catch every possible problem.
There is no other testing done in Tumbleweed AFAIK. Of course, upstreams should test their stuff too anyway before they make a release…
The release philosophy is still pretty conservative compared to other rolling releases, or so I thought.
Depends on what you mean with “conservative”.
Normally only stable upstream releases go in, no pre-release/beta versions or even release candidates (depends also on the particular package though, in some cases pre-release versions might make sense or are the only way). And there is automated testing before it gets released. But see above.
But as you apparently don’t want to update your system and lock out certain new packages, it seems to be not “conservative” enough for you, no? 
I never tried apt-get, but I don’t want to. Now I think rpm based distros are the way to go.
I always preferred rpm myself…
But if you compare rpm with apt-get, you are comparing apples with oranges. apt-get is the equivalent to zypper, the Debian pendant to rpm would be dpkg.