I found a better solution to Qt not finding KDE configs: add an environment variable named KDEHOME, and set it to ~/.kde4. This should be set before KDE startup.
For those who don’t know how to do that, have a shell script (named maybe “exports.sh”) with the following:
export KDEHOME=~/.kde4
Set it to executable (Dolphin can do it via File Properties). Add it to Autostarts under System Settings > Startup and Shutdown. Then set the script to execute on Pre-KDE startup.
Finally dived in. I went though the procedure for one of my systems. Everything went fine and smooth so thanks a lot for the very clear instructions. I do have a couple of questions.
Previously in the system settings there was a removable devices section were I could just tick the various devices/partitions that i would like kde to mount on login but I can’t find something similar in the new system settings? I can do this with fstab no problem just wondering if I missed something.
An other thing in the system settings, when I try to change the sddm, when i click on it it gets on of those yellow warning signs, any idea why? Also it seems very slow and can stop responding when I click on it. It does seem though that I can change the sddm theme and so on, so I don’t get why that sign is popping up.
Also a more general question. What does “netrunnerarch-systemsettings-settings netrunnerarch-default-settings netrunner-desktop” do? If I would uninstall it what would change/miss.
How to get transparent window borders back? On the PC where I have kde4 still it says I use something called FormaN for window theme, is that one available in kde5 yet? Any other way to mess around with the window apperance or other “Air” like themes, couldn’t find any in the settings?
The right click root actions open txt does not work? Is there some fix for this? I get asked for the psw but the file does not open. I can do “kdesu kate whatever.txt” fine and it works like that, but not the right click option.
It’s now recommended that you use device actions to mount devices and.or open specific apps once mounted.
"netrunnerarch-systemsettings-settings, netrunnerarch-default-settings and netrunner-desktop, have the various configuration files, etc. when they made the original ISO they used config files that pointed to netrunner specific directories to make system changes without overwriting files owned by installed packages. If you remove one of them the system may or may not boot up again, I just don’t remember which one it was.
The SDDM issue is also related to the redirecting links of system files to netrunner specific ones as explained above.
The last one may also be related to the above issue, however you may want to do a search for this on in Manjaro forums, I think I remember the issue discussed there as well.
Hi, I’m stuck on #1. I can’t seem to locate the pacman.conf file (via Find in Dolphin). Also, can you suggest a specific editor to use to edit the file? Thanks!
Then use the octopi repoeditor to move the blue shell repository:
In the octopi top menu Tools > Repository Editor click on the blue shell entry and use the move down button on the right save and exit. Now refresh the repositories again with the refresh button in octopi and continue on with the tutorial.
If you would rather edit the file manually any editor will do , it’s a plain text file, I recommend kate as root though.
warning: print-manager-15.04.1-1 is up to date – reinstalling
resolving dependencies…
looking for conflicting packages…
:: kmix and kdemultimedia-kmix are in conflict. Remove kdemultimedia-kmix? [y/N] y
Yes, The kcm-about-distro project was merged into systemsettings and kinfocenter by the upstream Plasma developers around version 5.3. I will make the correction now.
I guess I’ve been so busy working on the Next Plasma 5 based ISO that I forgot to update this tutorial. I’m taking my time and using the Manjaro tools this time around, so there is a bit of learning going on. I’m shooting for releasing around the same time as the official Manjaro 0.8.13 release.
Thanks a lot for your replies, will continue checking out the the issue could be with the right click.
There is another issue that has popped up. I don’t know if it is associated with the move to plasma5 but it is little else I have done recently to my system to be anything else.
I have all of the sudden gotten sound issues. For whatever reason pulseaudio does not recognize my sound card and uses a “dummy” card. I have gone into alsamixer and actively choose my card and unmute and then in VLC for example choose my card then I can get sound, so no problem with the card as such.
I have actually fixed the issue by adding
[code]load-module module-alsa-sink device=hw:0,0
set-default-sink 0[/code]
to [color=#222222][size=x-small][font=monospace]/etc/pulse/default.pa [/font][/size][/color]then no problem the sound works again.
Just don’t get why pulseaudio does not recognize it by itself. Wast thinking if it is some booting/ racing issue when the computer starts up. Also I think that before the move to plasma5 I had actually removed pulseaudio and managed by just alsa. Does pulseaudio come together with the move to plasma5?.
Cheers
blueshell/kdeplasma-applets-veromix-git 23.cac3925-1
A plasmoid mixer for the Pulseaudio sound server
blueshell/kdeplasma-applets-veromix-git-blueshell 4.53c5233-1
A plasmoid mixer for the Pulseaudio sound server
extra/libao 1.2.0-1 [installed]
Cross-platform audio output library and plugins
extra/libcanberra-pulse 0.30-5 [installed]
PulseAudio plugin for libcanberra
extra/libpulse 6.0-2 [installed]
A featureful, general-purpose sound server (client library)
extra/manjaro-pulse 2012.11-1 [installed]
Manjaro Pulseaudio support (Meta-PKG)
extra/pa-applet 1.0.2-1
PulseAudio system tray applet with volume bar
extra/paprefs 0.9.10-4
A simple GTK-based configuration dialog for PulseAudio
extra/pavucontrol 3.0-1 [installed]
A GTK volume control for PulseAudio
extra/pnmixer 0.5.1-2 (pnmixer)
PNMixer is a GTK volume mixer applet that runs in the system tray. It is lightweight, works with
both pulseaudio and alsa, supports mouse wheel volume adjustment, works with tint2, and can run
outside of gnome. PNMixer provides many configuration options including which icon theme to use
for display, middle click actions and more.PNMixer is a fork of OBMixer.
extra/pulseaudio 6.0-2 [installed]
A featureful, general-purpose sound server
extra/pulseaudio-alsa 2-3 [installed]
ALSA Configuration for PulseAudio
extra/pulseaudio-bluetooth 6.0-2
Bluetooth support for PulseAudio
extra/pulseaudio-equalizer 6.0-2
Equalizer for PulseAudio
extra/pulseaudio-gconf 6.0-2
GConf support for PulseAudio
extra/pulseaudio-jack 6.0-2
Jack support for PulseAudio
extra/pulseaudio-lirc 6.0-2
IR (lirc) support for PulseAudio
extra/pulseaudio-xen 6.0-2
Xen support for PulseAudio
extra/pulseaudio-zeroconf 6.0-2
Zeroconf support for PulseAudio
extra/xfce4-pulseaudio-plugin 0.2.3-1 (xfce4-goodies)
Pulseaudio plugin for Xfce4 panel
extra/xfce4-volumed-pulse 0.2.0-2
A volume keys control daemon for Xfce (using pulseaudio)
community/floyd 2.0.1-5
displays system load with pulse of keyboard LED
community/libcec 2.2.0-1
Pulse-Eight's libcec for the Pulse-Eight USB-CEC adapter
community/mate-media-pulseaudio 1.8.0-3 (mate-extra)
MATE Media Tools (pulseaudio)
community/mate-settings-daemon-pulseaudio 1.8.3-1 (mate)
The MATE Settings daemon (pulseaudio)
community/ponymix 4-1
CLI PulseAudio Volume Control
community/projectm-pulseaudio 2.1.0-10
ProjectM support for Pulseaudio
community/pulseaudio-ctl 1.61-1 [installed]
Control pulseaudio volume from the shell or mapped to keyboard shortcuts.
multilib/lib32-libcanberra-pulse 0.30-4 [installed]
PulseAudio plugin for libcanberra (32-bit)
multilib/lib32-libpulse 6.0-1 [installed]
A featureful, general-purpose sound server (32-bit client libraries)
Cheers
That happens when icons are set and doesn’t completely refresh, this issue has been present since KDE SC 4 came out and has never been fixed. Usually logging out and back in restores the icons that are missing.
I was thinking of removing pulseaudio, sound should work even without it, or not? As long as pulselib and alsa is there?
I don’t think that this problem was there in the beginning after moving to KDE5, I think it came after a few boots although I haven’t been doing anything to the sound.
I have now followed this migration procedure on my other desktop system as well and things seem to work fine, including the sound…
If you’re still using KDE SC 4 you will still be using KDE SC 4 no mater what the latest ISO has by default, if you used my tutorial to switch to Plasma 5, then you would still be using Plasma 5 and it would be just another update. Rolling release distributions like Arch and Manjaro don’t push the changes from one snaphot ISO release to another on it users, so there are no plans currently to switch users to plasma 5 automatically. If you wish to switch to Plasma 5 then yes, my tutorial will still be needed, otherwise the only other option would be a fresh install once a new Netrunner Rolling ISO is made available.