Double-checking the .xinitrc content to start Plasma 5.4

[lostpaperclips]

I am a long time KDE 4 user that is finally making the jump to plasma. I typically start my computer at run-level 3 & then start X myself due to some poor life decisions (i.e. I bought an ATI video card).

I was curious if I should adjust the content of my .xinitrc file:

Code: Select all

exec ck-launch-session startkde

I was poking around and saw on some forum a recommendation for

Code: Select all

kstart plasmashell

For me, the latter didn't work quite right.

Can anyone confirm or deny if I am using the correct contents for .xinitrc?

[eccerr0r]

Disclaimer: I don't use KDE so I have no clue about what each kde command does.

What's it dong wrong is the first question?

I would imagine you would need to use something like:

Code: Select all

exec ck-launch-session kstart plasmashell

(if kstart plasmashell is the correct way to start a kde session normall)

as you still need to launch a consolekit session. But since I don't know how kde works, if you forget to launch a consolekit session, it should still load up but anything that requires root access will probably break (like dealing with disks, network, etc.)

I have an ATI card and it can be used with graphical logins that have built-in consolekit support, it should work fine. Just gdm with systemd = death.

[lostpaperclips]

Thanks for the suggestion, though that didn't quite work for me either as then I was missing a window manager.

I found on http://www.linuxfromscratch.org/blfs/vi ... rting.html a suggestion to try

Code: Select all

exec dbus-launch --exit-with-session startkde

That appears to work well so far. The system seemed to load faster and for the first time I had a progress bar during the initial loading.

[davidbrooke]

This what I use in both KDE4 and KDE5:

Code: Select all

exec ck-launch-session dbus-launch --sh-syntax --exit-with-session startkde