22 Jul
2019
22 Jul
'19
3:52 p.m.
I did some more tests and finally found the culprit: it was libice package!
Instead upgrading the system at once, I upgraded package after
package, one after one, until I find out which one was causing the
problem. When I upgraded libice-1.0.9-2 to libice-1.0.10-1 I couldn't
start Trinity. Once I downgraded it back to 1.0.9-2 Trinity worked
normally again.
For now I will keep the old version of libice in my system.
On Mon, 22 Jul 2019 at 04:21, David C. Rankin
<drankinatty(a)suddenlinkmail.com> wrote:
On 07/21/2019 06:19 PM, Lucas dos Santos wrote:
[tdeinit] Launched DCOPServer, pid = 744 result =
0
/usr/bin/iceauth: creating new authority file /run/user/1000/ICEauthority
[dcopserver] ICE Connection rejected!
DCOPClient::attachInternal. Attach failed Authentication Rejected,
reason : None of the authentication protocols specified are supported
and host-based authentication failed
[dcopserver] ICE Connection rejected!
DCOPClient::attachInternal. Attach failed Authentication Rejected,
reason : None of the authentication protocols specified are supported
and host-based authentication failed
[dcopserver] DCOPServer self-test failed.
[tdeinit] DCOPServer could not be started, aborting.
That is the critical error. dcop could not setup ICEauthority (Xauthority)
allowing you to communicate with the xserver. The reason appears to be either
dcopserver wasn't started, or there has been a change to the protocol that
allows establishing a session (I don't know which), but this is the second
time I've seen a similar post in the past week or so.
--
David C. Rankin, J.D.,P.E.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting