···132132 plasma-workspace = with pkgs; super.plasma-workspace // {
133133 buildInputs = with xlibs;
134134 super.plasma-workspace.buildInputs ++ [ libSM libXcursor pam ];
135135+ postPatch = ''
136136+ substituteInPlace startkde/kstartupconfig/kstartupconfig.cpp \
137137+ --replace kdostartupconfig5 $out/bin/kdostartupconfig5
138138+ '';
135139 postInstall = ''
136140 # We use a custom startkde script
137141 rm $out/bin/startkde
+3-11
pkgs/desktops/plasma-5.2/startkde/startkde.in
···6363# * Then ksmserver is started which takes control of the rest of the startup sequence
64646565# We need to create config folder so we can write startupconfigkeys
6666-if [ ${XDG_CONFIG_HOME} ]; then
6767- configDir=$XDG_CONFIG_HOME;
6868-else
6969- # This is the default
7070- # http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
7171- configDir=${HOME}/.config;
7272-fi
7373-7474-mkdir -p $configDir
6666+configDir=$(@qt5@/bin/qtpaths --writable-path GenericConfigLocation)
6767+mkdir -p "$configDir"
75687669# This is basically setting defaults so we can use them with kstartupconfig5
7770cat @startupconfigkeys@ >$configDir/startupconfigkeys
···177170# For anything else (that doesn't set env vars, or that needs a window manager),
178171# better use the Autostart folder.
179172180180-# TODO: Use GenericConfigLocation once we depend on Qt 5.4
181181-scriptpath=`@qt5@/bin/qtpaths --paths ConfigLocation | tr ':' '\n' | @gnused@/bin/sed 's,$,/plasma-workspace,g'`
173173+scriptpath=$(@qt5@/bin/qtpaths --paths GenericConfigLocation | tr ':' '\n' | @gnused@/bin/sed 's,$,/plasma-workspace,g')
182174183175# Add /env/ to the directory to locate the scripts to be sourced
184176for prefix in `echo $scriptpath`; do