You are not logged in.
While I can't say anything definitively, I do know that the Oxygen team's been migrating their stuff from SVN to Git lately; the whole KDE project will end up on Git in the coming weeks (maybe months; they're already behind schedule on this as it is). I don't know precisely how that might be responsible for this issue, but it does seem like a packaging error rather than an actual coding bug; just a thought.
Offline
No, it was done on purpose. See here:
http://quickgit.kde.org/?p=kde-workspac … 21b2fae0fa
They basically admit that it should be done by startkde, which does ignore anyone who doesn't run a full KDE session.
"Cared thou not, thou would have abstained." - Xyne
Offline
Hey folks, we figured this out. I updated the wiki:
https://wiki.archlinux.org/index.php/KD … leshooting
"into your ~/.profile" - maybe it's better to point to /etc/profile?
Offline
petelewis wrote:Hey folks, we figured this out. I updated the wiki:
https://wiki.archlinux.org/index.php/KD … leshooting"into your ~/.profile" - maybe it's better to point to /etc/profile?
Probably yes, if you have access :-)
"Cared thou not, thou would have abstained." - Xyne
Offline
No, it was done on purpose. See here:
http://quickgit.kde.org/?p=kde-workspac … 21b2fae0fa
They basically admit that it should be done by startkde, which does ignore anyone who doesn't run a full KDE session.
Huh. I can't claim to understand most of what's written on that page but, judging from the summary for the commit, they wanted tighter integration and changed how it worked to avoid crashes. Apparently, those crashes were experienced by people running two versions of KDE; does this mean testers? If so, why they felt the need to complicate everyone else's lives, I don't know.
At least there's a workaround for now.
Offline