Q4OS Forum

Luc11

Member

Registered: 2026-08-20

Posts: 11

DCOP crashes

Most items in the Control Center work fine. But some of them cause DCOP to crash. For example, the Login Manager. As soon as I click it, this error pops up:

There was an error setting up inter-process communications for TDE. The message returned by the system was:
Authentication Rejected, reason: None of the authentication protocols specified are supported and host-based authentication failed
Please check that the "dcopserver" is running!

This is absolutely reproducible with most or all of the "System" items in the Control Center.

I still can use the item I just clicked. For example, I can configure the Login Manager. But that will be the last thing I will be allowed to do. From that point on, no item at all in the Control Center works anymore. I can't even run applications from the menu anymore. I can't even use the minimal "Run" tool. Whenever I try, another error pops up:

TDELauncher could not be reached via DCOP

Everything turns back to normal if I log out and log in again. Well, not everything. Those Control Center items are still troublesome, of course.

Additional info:

1. May be related or not: every time I log in, this message pops up:

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

(I also have LXDE installed. Could be related?)

2. I installed regular Debian and stock Trinity from trinitydesktop.org (and LXDE) in another partition to compare it all with Q4OS. None of these problems happen.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 6,352

Website

Re: DCOP crashes

We are not able to reproduce on Q4OS-6 TDE live media.
Boot Q4OS-6 live media > main menu > control panel > system administration > click "login manager" > opens fine, no error.
Can you confirm?

We will investigate further and post here.

Luc11

Member

Registered: 2026-08-20

Posts: 11

Re: DCOP crashes

Hi.
I tested with the live media and the problem did not occur.
Then again, I tested on the installed system, this time logging in as a regular user, and the problem did not occur.
That is not good enough for me. I always log in as root. I've been running as root for more than 20 years.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 6,352

Website

Re: DCOP crashes

We strongly discourage users from logging into a GUI session directly as root. You should be able to perform all tasks as a regular user, using elevated commands as root when necessary. In any case, we will try logging in as root and investigate the issue.

Luc11

Member

Registered: 2026-08-20

Posts: 11

Re: DCOP crashes

"should be able to perform" is not good enough. I should be able to perform quickly and conveniently, without having to type "sudo" or a gosh darn password all the time, all the time, all the time. That is beyond foolish. This is a single user machine. There are no other users to be insulated from each other. "Protect the system" is nonsense. I don't care about the system, I'm not running a server with tenants. I can replace/reinstall the system if needed. I care about my personal data, and I have backups for those. I used Windows 9x as a single user for seven years and have been using Linux as a single user for 25 years. I began with Slackware. Slackware never blocked anything to root. That is respect for the user. This is my machine, I make the decisions here. Puppy Linux even defaults as root and they say Puppy is designed for single user setups, so sudo doesn't make sense. That is respect for the user's intelligence. The whole anti-root mentality reeks of superstition. Linux should be shaping users up to be thinkers, not obeyers.

q4osteam

Q4OS Team

Registered: 2015-12-06

Posts: 6,352

Website

Re: DCOP crashes

"should be able to perform" is not good enough ...

Right. Anything you cannot perform is a bug and needs to be fixed.

... without having to type "sudo" or a gosh darn password all the time, all the time, all the time. That is beyond foolish.

It's easy to configure passwordless sudo for the first user.

This is a single user machine. There are no other users to be insulated from each other. "Protect the system" is nonsense.

Q4OS is designed to run within a regular user's desktop session, not a root session. You should simply operate it under the first regular user - the same activity, but with better results.