Bug 360290

Summary:	startplasmacompositor cause of qdbus cannot open socket /run/user/0/bus when starting from gdm or sddl or user tty session
Product:	[Plasma] plasmashell	Reporter:	Flav <hl037.prog>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	bshah, kde, mgraesslin, notmart, plasma-bugs-null, reuben_p
Priority:	NOR
Version First Reported In:	5.5.1
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Flav 2016-03-09 09:51:52 UTC

When starting startplasmacompositor from gdm, sddm or tty user session, startplasmacompositor fails with the message "startplasmacompositor: Could not start D-Bus. Can you call qdbus?"
When trying to run qdbus independently, it says : "failed to connect to socket /run/user/0/bus : permission denied".

Reproducible: Always

Steps to Reproduce:
1. Start gdm / sddm
2. Try to connect with a Plasma wayland session

or

1. log in a tty user session (not root) and try to start startplasmacompositor
1.bis start qdbus its error

Actual Results:  
startplasmacompositor outputs
 "startplasmacompositor: Could not start D-Bus. Can you call qdbus?"
qdbus outputs
"failed to connect to socket /run/user/0/bus : permission denied".

Expected Results:  
Should start normally

It's a problem with dbus, so the error is similar to 357744
but in my case, the qdbus executable is found correctly but gets error starting

Comment 1 Kai Uwe Broulik 2016-03-09 10:04:00 UTC

Run export $(dbus-launch) before that but I guess it should do that by itself if dbus is not yet running?

Comment 2 Flav 2016-03-09 20:42:50 UTC

No, it didn't. Nice shot, that work if I add this line to the startplasmacompositor (after other the exports)

Comment 3 Martin Flöser 2016-04-07 12:28:52 UTC

the wayland session file installed by plasma explicitly starts dbus.