KDE SC 4 to Plasma 5 Tutorial

Orbmiser · June 29, 2015, 9:31pm

Yep I was making the mistake of clicking on titlebar of application and that doesn’t work either. Had to track down and see that need to click inside the actual application.

And thanks AJ for the info on fsck disk errors and to ignore messages.

.

Platon91 · July 1, 2015, 5:14am

Thanks

Yeah figures ass much and will try and report the bug at KDE as well, just though in case there was some easy fix people had encountered, especially as it effects freefilesync as well which is not run under wine…

AJSlye · July 1, 2015, 6:53am

How did you install freefilesync?

Hopefully you used the AUR: https://aur.archlinux.org/packages/freefilesync/

yaourt -S freefilesync

holgerw · July 1, 2015, 1:20pm

Hello,

refering to this bug “kinit5 crash when trying to modify special window settings”

With current plasma 5.3.2 this error has gone, thanks to developers of plasma and kf5.

Kind regards,
Holger

Orbmiser · July 1, 2015, 4:40pm

Nope still getting the kdeinit5 when I try to use it on Netrunner rolling. As got the update a couple of days ago? That had 5.3.2?

holgerw · July 1, 2015, 5:16pm

Sorry, I should mention that I use unstable branch of manjaro.

Kind regards,
Holger

AJSlye · July 1, 2015, 5:41pm

Orbmiser:
Plasma 5.3.1 is in the stable branch not Plasma 5.3.2. Plasma 5.3.2 just hit Arch and Manjaro unstable on 2015-06-30, it will be a couple of weeks before we get it in the stable branch.

holgerw:
Yes, that was one of the fixes in Plasma 5.3.2, as well as quite a few others.

Orbmiser · July 1, 2015, 6:03pm

Thanks for the info AjSlye as always helpful for us that can’t keep track of the every changing plasma landscape.

.

brasher · July 13, 2015, 1:24am

AJSlye:

Yes, kcm-about-distro has been depreciated and removed from the Manjaro repository, kcm-about-distro was merged into Kinfocenter upstream by the KDE developers.

You can add our new repository for Netrunner Rolling Plasma 5 and update Kinfocenter.

Add these lines to you pacman.conf file between core and extra:
[netrunner]
SigLevel = Never
Server = http://arch.netrunner-os.com/blueshell5/$arch
then
sudo pacman -Syyu
Please note that this repository is currently in flux as I add, remove and update packages prior to the next ISO release. This shouldn’t effect anything but if you have any issues at all over the course of the next few weeks, please post them in a new thread here: http://forums.netrunner.com/forumdisplay.php?fid=62

Doing this and running an update yields:

:: libksysguard and kdebase-workspace are in conflict. Remove kdebase-workspace? [y/N]

If I answer no:
error: unresolvable package conflicts detected

error: failed to prepare transaction (conflicting dependencies)
:: libksysguard and kdebase-workspace are in conflict

If I answer yes:
error: failed to prepare transaction (could not satisfy dependencies)

:: homerun: requires kdebase-workspace
:: kcm-touchpad: requires kdebase-workspace
:: kdeartwork-colorschemes-oxygreen: requires kdebase-workspace
:: kdebase-plasma: requires kdebase-workspace
:: kdeplasma-addons-applets-icontasks: requires kdebase-workspace
:: kdeplasma-addons-applets-showdesktop: requires kdebase-workspace
:: kdeplasma-applets-plasma-nm: requires kdebase-workspace
:: kdeplasma-applets-veromix-git-blueshell: requires kdebase-workspace
:: netrunnerarch-default-settings: requires kdebase-workspace

How can I correct this?

AJSlye · July 13, 2015, 2:36am

This thread is way outdated and I haven’t had the time to look at it again.

Try, following the original post in this order and let me know how it goes:
1,3,4,5,6,7,2,8,9,10,11

flipper · August 12, 2015, 6:34pm

Is it already possible to add a new [blueshell] repo in /etc/pacman.conf to get access to netrunner-related packages, or is it still in testing?

AJSlye · August 12, 2015, 7:09pm

Yes and no.

The new ISO’s for the next rolling release are still only for testing and are now being built using manjaro tools, a new packaging scheme, and a minimum of diversions from upstream. I took a lot of time and effort separating release based artwork and settings, etc. into release dated packages so that each new snapshot release ISO’s packages won’t effect already installed systems. Any changes that do need pushed out to those systems can be done by updating there release dated packages, leaving out changes that might be upsetting to the end user, things like changing their backgrounds, font settings, installed or removed applications, etc.

In other words:
netrunner-default-settings-2015.06
netrunner-default-settings-2015.09
netrunner-system-settings-2015.06
netrunner-system-settings-2015.09
netrunner-wallpapers-2014.04
netrunner-wallpapers-2014.09
netrunner-wallpapers-2015.06
etc.

You would need to remove the old repository and all packages related to it, then Install the new repository and the correct packages for your desired point release. Also keep in mind that this repository is still changing, and there are some packages that I’m now maintaining myself that are scheduled to be release officially, from upstream as part of Plasma 5.4, user-manager and plasma-volume control just to name two, that will eventually be dropped from our repository once they are provided in Manjaro’s. There are also two other files needed that are only part of the overlay since they don’t change from release to release that I use to create the ISO, namely /etc/issues and /etc/os-release, I can provide these if you wish.

So, If you have the know how and are willing to possibly break your system, then I can provide a list of the packages needed via a private chat.

flipper · August 14, 2015, 7:47pm

Thank you for the clarification. I don’t want to rush things too much on my production system, I will wait for the official release to install on my desktop pc.

Clyde · August 25, 2015, 11:19pm

I’ve finally upgraded to Plasma 5, but “sudo pacman -Syyu” doesn’t work after. I get this message:

resolving dependencies…
looking for conflicting packages…
:: kdebase-workspace and kdeplasma-addons are in conflict. Remove kdeplasma-addons? [y/N]

I select the default of N because I think I want to keep kdeplasma-addons. However, I can’t upgrade otherwise. I did do the step to remove kdebase-workspace so I don’t know what happened. Any suggestions?

Clyde · August 25, 2015, 11:21pm

BTW, trying to remove kdebase-workspace again gives:

sudo pacman -R kdebase-workspace
error: target not found: kdebase-workspace

AJSlye · August 25, 2015, 11:59pm

That is a strange issue your having, kdebase-workspace would have been replaced by plasma-workspace when upgrading to plasma 5.

Clyde · August 26, 2015, 1:30am

I found the thread by fairoaks called “Having a hard time updating after fresh install” and follow those instructions. That seems to have fixed it. It appears that everything is working just fine now.

Thanks,
Clyde

Foxblood · March 30, 2016, 9:41pm

Hi, I’m unable to get past step 4.

pacman -Rdd $(LANG=C pacman -Qi kdebase-workspace | grep "Req" | sed -e 's/Required By : //g')

gives me

error: target not found: Required

error: target not found: By
error: target not found: :

Any help, please.

AJSlye · March 30, 2016, 10:00pm

That’s because kdebase-workspace no longer exist.
Manjaro/Arch dropped Plasma 4 (KDE 4) back in December.
https://www.archlinux.org/news/dropping-plasma-4/

This upgrade path no longer exists, Please follow the arch guide:
https://wiki.archlinux.org/index.php/KDE#Upgrading_from_Plasma_4_to_5

Please note: Instead of installing the meta package or the entire plasma group, you should be able to just update all the rest of the existing packages with pacman -Syyu, selecting Y to replace the old with the new packages.

If you run into any issue, I will be glad to help.

Foxblood · April 1, 2016, 10:10am

Hi, Thanks for the assist. Al went well, including a reboot. However, a second reboot failed. The reason seems to be plymouthd failed to start splash screen, no such file or directory. I’m in work, the error message may not be accurate. I’ll let you know and thanks again.