Bug 19154 - Cannot log into Plasma as root (qdbus problem?)
Summary: Cannot log into Plasma as root (qdbus problem?)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 17523
  Show dependency tree / graph
 
Reported: 2016-08-08 17:05 CEST by David Walser
Modified: 2017-06-26 00:46 CEST (History)
2 users (show)

See Also:
Source RPM: plasma-workspace
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2016-08-08 17:05:00 CEST 
Trying to log in to Plasma as root gives a dialog that says:
"Could not start D-Bus. Can you call qdbus?"

with a button that says "okay"

Clicking it results in nothing else happening; just stuck with a red screen.
David Walser 2016-08-08 17:05:15 CEST

Blocks: (none) => 17523

Comment 1 Nicolas Lécureuil 2016-08-10 22:42:41 CEST 
Please report this upstream but i don't think this is a bug.
Comment 2 David Walser 2016-08-10 23:58:46 CEST 
It's certainly a bug, as this used to work, and it should work (even if it's not recommended for general use), and it really sounds like a possible packaging problem to me.
Comment 3 David Walser 2016-08-17 13:53:27 CEST 
Note that Lewis got the same exact error logging into Plasma from GDM:
https://ml.mageia.org/l/arc/qa-discuss/2016-08/msg00107.html

I assume that was even as a regular user.

CC: (none) => lewyssmith

Samuel Verschelde 2016-08-25 16:24:13 CEST

Assignee: mageia => kde

David Walser 2016-12-24 02:51:01 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=20010

Comment 4 Nicolas Lécureuil 2017-03-14 17:27:12 CET 
is it still valid with plasma 5.8.6 ?

CC: (none) => mageia

Comment 5 Nicolas Lécureuil 2017-04-01 19:58:48 CEST 
just tested, this is now fixed in cauldron.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 6 David Walser 2017-06-26 00:46:44 CEST 
I can confirm that this is fixed.  Thanks.
Note You need to log in before you can comment on or make changes to this bug.