I upgrade to 4.12 but i don’t see much difference. I was looking for a solution to downgrade but no luck. Is there a way to remove 4.12 withou braking my system. I really like it as is.
I used this thread to do the upgrade :
http://www.muktware.com/2013/12/install-kde-4-12-software-compilation-opensuse-13-1/17881
Now I get this when doing any update :
The following 59 package updates will NOT be installed:
any help would be appreciated
Thanks
What other repos do you have?
zypper lr -d
The easiest way would be to disable/remove the repo and run “sudo zypper dup”. If you use KDE:Extra as well, don’t forget to switch that back to the standard openSUSE_13.1 flavor before that.
But with many additional repos this could lead to problems.
Now I get this when doing any update :
The following 59 package updates will NOT be installed:
That just tells you that those packages would exist in another repo with a higher version or build number.
zypper doesn’t switch packages to another repo by default, and normally you wouldn’t want it to.
There is the output from terminal:
1 | Google-Chrome | Google-Chrome | Yes | No | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | KDE412 | KDE412 | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Release:/412/openSUSE_13.1/ |
3 | KDE412E | KDE412E | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_412_openSUSE_13.1/ |
4 | download.opensuse.org-Education | openSUSE BuildService - Education | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Education/openSUSE_13.1/ |
5 | download.opensuse.org-mozilla | openSUSE BuildService - Mozilla | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_13.1/ |
6 | ftp.gwdg.de-suse | Packman Repository | Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.1/ |
7 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.1/repo/oss/ |
8 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1/ |
9 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1-non-oss/ |
10 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
11 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
12 | repo-source | openSUSE-13.1-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.1/repo/oss/ |
13 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
14 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/
Disable repo 2 and 3
Then open a terminal and do
su -
zypper dup
reboot and then do this:
https://dl.dropboxusercontent.com/u/10573557/Switcher%20Pics/13.1_Packman_Switch_KDE.png
if you don’t see much difference why switch back?
Is there some problem that you didn’t have in KDE 4.11?
Visually KDE 4.12 is identical to 4.11 but there are probably some improvements that may not be immediately obvious.
The packages that will not be installed is normal if you have followed my guide on switching to a vendor such as Packman.
Restore from the backup you made before doing the upgrade.
The method outlined by wolfie323 and caf4926 should be sufficient. (I’ve done the same previously when needing to switch between KDE versions for bug reporting purposes.)
Disabling repo 3 shouldn’t be necessary, but as I mentioned already you should change the URL to the standard openSUSE_13.1 flavor before you run the “zypper dup”.
Either edit the corresponding file in /etc/zypp/repos.d/ with a text editor, or change it in YaST->Software Repositories.
The URL should be:
[noparse]http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_13.1/[/noparse]
Thank you everyone for the great help. wolfi323 thank you, it works.
Actually, there were two issues that made me downgrade my daughter’s ultrabook to 4.11.
One was the kwrite black background issue, quite annoying. The other I can’t remember right now, but it was more serious.
Hm. KWrite has a white background here on 4.12.
Have you looked into KWrite’s color settings? Maybe you were using the GTK+ theme? (I have heard of similar issues with the KMenu’s search field being black when using this)
I also have no other issues on 4.12 that were not present already on 4.11. And some that bothered me in 4.11 got even fixed in 4.12. 
Hi wolfi, sorry for the late reply (work, work, work…)
Kwrite color settings: yes. If I go into Config>Fonts and Colors, the text area background is correctly set to white, but the screen is all black because both text and bkg are black (duh), CTRL-A shows the text in white, as everything is selected.
If I click the “Use default KDE color sheme” button the bkg changes to white, as it should be, but if I quit and reopen kwrite, or just open another kwrite window, it’s back to black.
KDE widget style is set to oxygen, GTK2 theme is set to oxygen-gtk in system-settings.
It’s annoying, but no big deal, as I don’t use kw very often.
I also saw a post, I think in the KDE4.12 thread in Tech News, suggesting saving a new color theme, or something to that effect. I tried, very superficially, but it didn’t work. I didn’t have time to look further, however…
I can understand that.
Kwrite color settings: yes. If I go into Config>Fonts and Colors, the text area background is correctly set to white, but the screen is all black because both text and bkg are black (duh), CTRL-A shows the text in white, as everything is selected.
If I click the “Use default KDE color sheme” button the bkg changes to white, as it should be, but if I quit and reopen kwrite, or just open another kwrite window, it’s back to black.
Hm. I have never seen something like this, and I use KWrite every day.
It does sound similar to this though:
https://bugzilla.novell.com/show_bug.cgi?id=859218
Do you maybe have some non-standard colour settings? (“Configure Desktop”->“Application Appearance”->“Colors”)
One thing to try would be to create a new user and see whether the problem happens there as well.
I guess it won’t, otherwise the issue would be more wide-spread I think.
Probably some user’s setting/configuration file causes this.
KDE widget style is set to oxygen, GTK2 theme is set to oxygen-gtk in system-settings.
The GTK2 theme doesn’t matter for KDE applications like KWrite.
If you would set KDE’s widget style to Gtk+, it would use the GTK2 theme, but I cannot reproduce it with this either.
This thought just crossed my mind because the K-Menu’s search field has a black (well, not fully black, but the theme’s background colour, which is a very dark grey with the default openSUSE theme) background with the Gtk+ style as I mentioned, rendering it nearly unreadable.
Hi Wolfi, thank you for your efforts on this.
Needing kwrite more frequently this week, the color issue has been bothering me, so I went to yast to install kate. Although I had removed the deprecated KDE 4.12 repo, I hadn’t included the KDE:/Current one, so yast could only find kate 4.10.
Curiously, yast only wanted to downgrade libktexteditor and kwrite itself, with no other dependency errors. So I went ahead, and now, guess what, kwrite has the standard white background back :).
The installed packages are:
libktexteditor-4.10.5-1.101.9.x86_64.rpm
kwrite-4.10.5-1.101.9.x86_64.rpm
kate-4.10.5-1.101.9.x86_64.rpm
I’ll leave it for some time to see if there any other problems arise, but for now I’m happy with it.
Best regards,
Bruno