I wanted to try plasma5 but didn’t want to give up kde4 so I added wolfi’s repo http://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Frameworks5/openSUSE_13.2
and installed plasma5-desktop
and I think I ended up with a mixed system
when I log-in to plasma5 the main panel is from kde4, kmix, klipper are both kde4 apps.
If I run a console from dolphin5 konsole 2.14.2 from kde 4.14 starts up.
I know this is a silly question but how do you setup plasma5?
ps.
I know there is a working kde3 desktop that installs in /opt/kde3/ will there be something similar in Leap ie. having kde4 sc installed in /opt/kde4 ?
You probably installed plasma5-session from KDE:Frameworks5 or openSUSE:13.2, but not from my repo. The official one run /usr/bin/startkde, which is still the KDE4 version in your case (mine is /opt/kf5/bin/startkde).
Do a full switch to my repo, and it should work:
sudo zypper in --from 9
(or click on “Switch all system packages to the versions from this Repository” in YaST->Software Management->View->Repositories after you selected my repo)
ps.
I know there is a working kde3 desktop that installs in /opt/kde3/ will there be something similar in Leap ie. having kde4 sc installed in /opt/kde4 ?
No. AFAIK there will still be KDE3 though.
I could create KDE4 packages that install to /opt/, but I don’t have any intention to do the same heavy and complicated work again that I did with Plasma 5 already.
I will build my repo for Leap 42.1 too though. So you should still be able to install my Plasma5 packages and keep KDE4 (the desktop and all applications, the latter are included in my repo if they have been switched to KF5 already).
You probably installed plasma5-session from KDE:Frameworks5 or openSUSE:13.2, but not from my repo. The official one run /usr/bin/startkde, which is still the KDE4 version in your case (mine is /opt/kf5/bin/startkde).
Do a full switch to my repo, and it should work:
Code:
sudo zypper in --from 9
yes I had plasma5-session-5.3.2-10.1.noarch
did a zypper dup -from 9
43 packages to change vendor, I’ll see if that fixes things.
I could create KDE4 packages that install to /opt/, but I don’t have any intention to do the same heavy and complicated work again that I did with Plasma 5 already.
I will build my repo for Leap 42.1 too though. So you should still be able to install my Plasma5 packages and keep KDE4 (the desktop and all applications, the latter are included in my repo if they have been switched to KF5 already).
good to know.
So there will be a kde4 sc in Leap?
I’ report after dup finishes and I reboot
Nope it seams I broke something
after zypper dup to your repo I get the plasma5 start-up screen (I was getting kde4 start-up in plasma5) but after that nothing just a mouse cursor, no panel no desktop no icons. I can’t even get a start menu with alt+F2, I had to kill X with ctrl+alt+backspace.
I removed all kde and plasma config files, I even created a new user.
The new user is the same I get the start-up screen but nothing after that just a black screen and a mouse cursor?
Any ideas?
could systemsettings5-5.4.0-58.1 from obs://build.opensuse.org/KDE be the cause of this?
trying to run /usr/bin/systemsettings5 from a terminal I get this error
user1@dhcp-xx-xxx-xx-xx:~> /usr/bin/systemsettings5
iconTheme "oxygen"
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.41'
detected kglobalaccel restarting, re-registering all shortcut keys
file:///usr/share/kwin/kcm_kwindecoration/main.qml:32:9: Type Buttons unavailable
Buttons {
^
file:///usr/share/kwin/kcm_kwindecoration/Buttons.qml:25:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/usr/lib64/libKF5PlasmaQuick.so.5: undefined symbol: _ZN12KQuickAddons21QuickViewSharedEngine16staticMetaObjectE)
import org.kde.plasma.core 2.0 as PlasmaCore;
^
kcm_icons: Theme list: ("Adwaita", "breeze", "breeze-dark", "hicolor", "oxygen", "crystalsvg") <<
Removing cache at "/home/user1/.cache/icon-cache.kcache"
checking permissions of "/usr/share/color-schemes/Breeze.colors"
checking permissions of "/usr/share/color-schemes/openSUSE.colors"
checking permissions of "/usr/share/color-schemes/Breeze.colors"
checking permissions of "/usr/share/color-schemes/openSUSE.colors"
QFile::copy: Empty or null file name
Error loading plugin "kcm_lookandfeel" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///opt/kf5/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml"
"Error loading QML file.
25: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/usr/lib64/libKF5PlasmaQuick.so.5: undefined symbol: _ZN12KQuickAddons21QuickViewSharedEngine16staticMetaObjectE)
"
log_kcm_desktoptheme: Save!
log_kcm_desktoptheme: theme changed to "default"
log_kcm_desktoptheme: m-defaultTheme "default"
log_kcm_desktoptheme: saved.
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
settingsFile: "/home/user1/.config/plasmarc"
Error loading plugin "kcm_splashscreen" "The shared library was not found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///opt/kf5/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml"
"Error loading QML file.
25: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/usr/lib64/libKF5PlasmaQuick.so.5: undefined symbol: _ZN12KQuickAddons21QuickViewSharedEngine16staticMetaObjectE)
"
KCrash: Application 'systemsettings5' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
[1]+ Stopped /usr/bin/systemsettings5
I think I’m missing some packages.
A few days ago I did notice a lot of new 32bit packages, I thought an update installed them so I removed them, does plasma5 depend on i586 rpm’s?
I did notice libKF5KCMUtils5 was an older package 5.11 from the update repo, I’ll switch to 5.13 from the KDE OBS repo?
After updating libKF5KCMUtils5 in plasma5 I get an error that resources are missing and to contact somebody.
I guess I broke something, I already did a dup with the update and then with Wolfi’s repo.
What do you guys suggest?
I don’t want to do a dup with the main oss repo as that will downgrade my kernel and every application I’ve got installed, and with Leap only 2 months away I don’t want to re-install.
ps. kde4 and lxqt are working fine only plasma5 is having issues.
There definitely will be no KDE4 SC in Leap. Such a thing doesn’t exist any more, the last release of KDE4 SC was last November (4.14.3).
In the current KDE Applications 15.08 more than half of all packages are already ported to KF5.
I think kdebase4-workspace (which contains the desktop) will be included in Leap though, because it also contains KDM (SDDM is not really a full replacement yet).
No idea about the support packages though, like plasma-addons and so on.
I will add them to my repo though as they get removed.
Hm.
Maybe try a full switch to the KDE:Qt5 repo as well. But I think the dependencies are strict enough that it shouldn’t be necessary.
Can you reach the Alt+F2 dialog?
You could start a Konsole and then run “plasmashell” there to get an error message.
Also try a fresh user account, and/or recovery mode. It might be a graphics driver or user settings problem (the latter is unlikely though I’d say, as you didn’t ever start it successfully yet, or did you?).
What graphics driver are you using, btw?
is there a start-kde for plasma5 that I can run in a terminal from window maker or open box and see any errors?
Yes, startkde, as mentioned. With my packages its path is /opt/kf5/bin/startkde.
But you should better use /opt/kf5/bin/startkf5 instead, this sets up the environment so that things are found (and actually preferred) in /opt/kf5/, before it runs startkde.
Hm.
Maybe try a full switch to the KDE:Qt5 repo as well. But I think the dependencies are strict enough that it shouldn’t be necessary.
I’ll try it
Can you reach the Alt+F2 dialog?
No, I even made a new user and I did see welcome to opensuse window but nothing else, there is no menu no panel, I have to end plasma with ctrl+alt+2xbackspace
You could start a Konsole and then run “plasmashell” there to get an error message.
I’ll try that
There are known problems with certain intel driver versions that cause Plasma/Kwin to crash due to a bug in the driver. Switching to UXA acceleration should help
I only have an nvidia card my cpu is an old dual core without the bundled intel gpu so I don’t think I’m using any intel video drivers I have the latest G3 (or G2 not sure) nvidia.
But you should better use /opt/kf5/bin/startkf5 instead, this sets up the environment so that things are found (and actually preferred) in /opt/kf5/, before it runs startkde.
Tanks for that, I’ll run it in windowmaker and see what happens.
doing a bit complex dup from KDE:Frameworks5, KDE:Qt5, home:wolfi323:branches:KDE:Frameworks5 and packman did the trick.
atm I am writing this from plasma5 session running inside of windowmaker
tanks wolfi323
ps. your ffmpeg libraries from home:wolfi323:branches:KDE:Frameworks5 are crippled right because I switched to packman’s, as there are no patented codecs in OBS right?
One final question the kickoff button uses the kde logo it’s not a geeko, and there is only the classic view. Is that right or do I need to configure a few more things, here’s a screenshot http://paste.opensuse.org/images/53518904.png
Hm, as you already dupped to KF5 and my repo, a dup to KDE:Qt5 should have sufficed I think.
But well, at least it works now, right?
ps. your ffmpeg libraries from home:wolfi323:branches:KDE:Frameworks5 are crippled right because I switched to packman’s, as there are no patented codecs in OBS right?
Yes.
I only have them in there to build some stuff with full multimedia ability or even at all:
kfilemetadata (for Baloo and Dolphin’s file information display)
mlt (used by kdenlive)
k3b
ffmpegthumbs
I maybe should not publish it, but then people not having ffmpeg installed from Packman could not install those packages (and Plasma5, because kfilemetadata5 is a vital component).
I could split out the ffmpeg requiring parts into separate subpackages though (e.g. kfilemetadata5-ffmpeg), but I haven’t found the time yet.
That’s not Kickoff, that’s “Kicker” which is new in Plasma5.
You can right-click on it and choose “Alternatives” to switch between all available application launchers (Kicker, Kickoff, and Kicker Dashboard, the new fullscreen launcher in 5.4). Similar like in KDE4, but in Plasma5 this “Alternatives” feature is more general, and available for all types of applets, like the clock and the task manager too.
And you can configure the button icon in its settings, also reachable in the right-click context menu.
and there is only the classic view
What do you mean with “classic view”?
Kicker is intended to be a bit like the old “classic style”, yes, if that’s what you mean. It has some additional features though.
If you prefer Kickoff (KDE4’s default), just switch to it.
Tanks for the info I saw 3 alternatives, I’ll stick with the new for now, what about it’s logo is it supposed to be the kde logo or do I have an upstream branding installed instead of opensuse’s?
Yes, the KDE logo is used even for the openSUSE branding.
Btw, the only real branding package is plasma5-workspace-branding-xxx at the moment, so you can check yourself.
But if you saw the SuSEgreeter on first start and have the openSUSE wallpaper, you do have the openSUSE branding installed.
Another distinguishing feature is that openSUSE’s default have two virtual desktops instead of just one.
PS: You can of course still add as many application launchers (or other widgets) to your panels and desktop as you want.
So you could add the other two too, to try all of them for a while…
