Hi,
I just installed Trinity R14.0.5 [1] in a recently installed Arch Linux based system and I'm not able to start the DM. I added 'exec starttde' line to .xinitrc and made the needed changes in my PATH variable, but, when I issue startx command, TDE won't open.
Instead, the following message is shown:
----------- There was an error setting up inter-process communications for TDE. The message returned by the system was:
Could not read network connection list. /home/username/.DCOPserver_hostname__0
Please check that the "dcopserver program is running! ----------
When I click 'OK', the TDE's splash screen appears, but the first icon keeps flash infinitely and the above mentioned message appears again underneath them. When I click on splash screen, it disappears and when I click in OK again, X exits to tty.
The following video shows exactly what occurs:
This is the output from starttde command:
$ starttde [starttde] Starting starttde. [starttde] This script is /opt/trinity/bin/starttde [starttde] TDE version is R14.0.5 [starttde] TDE base directory is /opt/trinity [starttde] TDEHOME is not set. [starttde] Set TDEHOME to /home/lucas/.trinity. [starttde] Setting TDEROOTHOME to /root/.trinity. [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share gpg-agent: a gpg-agent is already running - not starting a new one [starttde] TDEDIR: /opt/trinity [starttde] TDEDIRS: [starttde] Starting Trinity... [starttde] Trinity hardware control dbus daemon running. [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. [starttde] TDE_FULL_SESSION: true [starttde] TDE_SESSION_UID: 1000 [tdeinit] Launched DCOPServer, pid = 759 result = 0 [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. [starttde] tdeinit started successfully. [tdeinit wrapper] Warning: socket connection failed: : Connection refused [tdecore-tdeapplication] Found visual with alpha support [tdecore-tdeapplication] Found visual with alpha support [tdeinit] Launched DCOPServer, pid = 769 result = 0 [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. [KSMServer] Could not register with DCOPServer. Aborting. ERROR: Couldn't attach to DCOP server! [starttde] Shutting down Trinity... [tdeinit wrapper] Warning: socket connection failed: : Connection refused [tdeinit wrapper] Error: Can't contact tdeinit! [starttde] Running Trinity shutdown scripts... [starttde] Running /opt/trinity/shutdown/agent-shutdown.sh. [starttde] Trinity shutdown complete.
Deleting files from ~/.trinity and /tmp directories [2] doesn't solve the problem.
I have an old installation of Arch Linux in a virtual machine where Trinity works perfectly. So, I decided to play around with it and do some tests. That system was a little outdated. Thus I decided to do a pacman -Syu in order to update the system's packages. After updating, I no more could to start Trinity. It looks like that a new version from some package is breaking Trinity. Which one? I have no idea! But, I saved a list of the updated packages and also a list of packages' version before updating. Maybe some of you could try to find what package is causing the problem.
Trinity works fine with the following packages' version:
argon2-20171227-3 audit-2.8.5-2 btrfs-progs-5.1-1 bzip2-1.0.6-8 ca-certificates-mozilla-3.44-1 cmake-3.14.5-1 curl-7.65.1-2 dbus-1.12.14-1 dhcpcd-7.2.1-1 e2fsprogs-1.45.2-1 expat-2.2.6-1 ffmpeg-1:4.1.3-1 firefox-67.0.2-1 freetype2-2.10.0-2 gcc-8.3.0-1 gcc-libs-8.3.0-1 glib2-2.60.4-1 glibc-2.29-1 gnupg-2.2.16-1 gnutls-3.6.8-1 gpgme-1.13.0-1 grub-2:2.02-8 gtk-update-icon-cache-1:3.24.8+177+gae2ef1472c-1 gtk3-1:3.24.8+177+gae2ef1472c-1 guile-2.2.4-2 harfbuzz-2.5.1-1 iana-etc-20190531-1 iproute2-5.1.0-1 iptables-1:1.8.2-1 iso-codes-4.2-1 js60-60.7.0-1 kidletime-5.59.0-1 kwayland-5.59.0-1 kwindowsystem-5.59.0-1 lcms2-2.9-1 less-550-1 libarchive-3.3.3-1 libblockdev-2.21-1 libdrm-2.4.98-1 libice-1.0.9-2 libinput-1.13.2-1 libkscreen-5.16.0-1 libnftnl-1.1.1-1 libpciaccess-0.14-1 libqtxdg-3.3.1-3 libraw-0.19.2-1 libssh-0.8.7-1 libtool-2.4.6+42+gb88cebd5-3 libtorrent-rasterbar-1:1.1.12-1 libutil-linux-2.33.2-1 libuv-1.29.1-1 libva-2.4.1-1 libvpx-1.8.0-1 libwebp-1.0.2-1 libx11-1.6.7-1 libxi-1.7.9-2 libxt-1.1.5-2 libyaml-0.2.1-1 libzip-1.5.2-1 linux-5.1.9.arch1-1 linux-api-headers-5.0.7-1 linux-firmware-20190514.711d329-1 mesa-19.0.6-1 nano-4.2-1 nettle-3.4.1-1 nss-3.44-1 opera-60.0.3255.170-1 perl-5.30.0-2 polkit-0.116-1 proj-5.2.0-1 qt5-base-5.12.3-2 qt5-script-5.12.3-1 qt5-svg-5.12.3-1 qt5-x11extras-5.12.3-1 solid-5.59.0-1 sqlite-3.28.0-1 systemd-242.29-1 systemd-libs-242.29-1 systemd-sysvcompat-242.29-1 tzdata-2019a-1 udisks2-2.8.2-1 util-linux-2.33.2-1 wget-1.20.3-1 x265-3.0-1 xorg-fonts-encodings-1.0.4-5 xorg-server-1.20.5-1 xorg-server-common-1.20.5-1 xorg-server-devel-1.20.5-1 xorg-server-xdmx-1.20.5-1 xorg-server-xephyr-1.20.5-1 xorg-server-xnest-1.20.5-1 xorg-server-xvfb-1.20.5-1 xorg-server-xwayland-1.20.5-1 xorg-setxkbmap-1.3.1-2 xorg-xauth-1.0.10-2 xorg-xbacklight-1.2.2-1 xorg-xclock-1.0.8-1 xorg-xinput-1.6.2-2 xorg-xwininfo-1.1.4-1 xorgproto-2018.4-1 xscreensaver-5.42-1 xterm-346-1
But, if I upgrade that packages, Trinity won't start. These are the current packages' version:
argon2-20190702-1 audit-2.8.5-3 btrfs-progs-5.2-1 bzip2-1.0.8-2 ca-certificates-mozilla-3.45-1 cmake-3.15.0-1 curl-7.65.1-3 dbus-1.12.16-1 dhcpcd-7.2.2-1 e2fsprogs-1.45.3-1 expat-2.2.7-1 ffmpeg-1:4.1.4-1 firefox-68.0.1-2 freetype2-2.10.1-1 gcc-9.1.0-2 gcc-libs-9.1.0-2 glib2-2.60.5-1 glibc-2.29-3 gnupg-2.2.17-2 gnutls-3.6.8-3 gpgme-1.13.1-1 grub-2:2.04-1 gtk-update-icon-cache-1:3.24.10-1 gtk3-1:3.24.10-1 guile-2.2.6-1 harfbuzz-2.5.3-1 iana-etc-20190702-1 iproute2-5.2.0-1 iptables-1:1.8.3-1 iso-codes-4.3-1 js60-60.8.0-1 kidletime-5.60.0-1 kwayland-5.60.0-1 kwindowsystem-5.60.0-1 lcms2-2.9-2 less-551-1 libarchive-3.4.0-2 libblockdev-2.22-1 libdrm-2.4.99-1 libice-1.0.10-1 libinput-1.13.4-1 libkscreen-5.16.3-1 libnftnl-1.1.3-1 libpciaccess-0.16-1 libqtxdg-3.3.1-5libraw-0.19.3-1 libssh-0.9.0-1 libtool-2.4.6+42+gb88cebd5-4 libtorrent-rasterbar-1:1.1.13-1 libutil-linux-2.34-3 libuv-1.30.1-1 libva-2.5.0-1 libvpx-1.8.1-1 libwebp-1.0.3-1 libx11-1.6.8-1 libxi-1.7.10-1 libxt-1.2.0-1 libyaml-0.2.2-1 libzip-1.5.2-2 linux-5.2.1.arch1-1 linux-api-headers-5.1-1 linux-firmware-20190712.d52556e-1 mesa-19.1.2-1 qt5-base-5.13.0-7 qt5-script-5.13.0-1 qt5-svg-5.13.0-1 qt5-x11extras-5.13.0-1 solid-5.60.0-1 sqlite-3.29.0-1 systemd-242.32-3 systemd-libs-242.32-3 systemd-sysvcompat-242.32-3 tzdata-2019b-1 udisks2-2.8.3-1 util-linux-2.34-3 wget-1.20.3-2 x265-3.1.1-1 xorg-fonts-encodings-1.0.5-1 xorg-server-1.20.5-2 xorg-server-common-1.20.5-2 xorg-server-devel-1.20.5-2 xorg-server-xdmx-1.20.5-2 xorg-server-xephyr-1.20.5-2 xorg-server-xnest-1.20.5-2 xorg-server-xvfb-1.20.5-2 xorg-server-xwayland-1.20.5-2 xorg-setxkbmap-1.3.2-1 xorg-xauth-1.1-1 xorg-xbacklight-1.2.3-1 xorg-xclock-1.0.9-1 xorg-xinput-1.6.3-1 xorg-xwininfo-1.1.5-1 xorgproto-2019.1-1 xscreensaver-5.43-1 xterm-347-1
I don't know if this is a Trinity or Arch Linux issue, but the fact is that I'm unable to use TDE. If at least I knew what package is causing this I could temporarily keep outdated until this problem is solved.
Thanks for your attention.
NOTES:
[1] http://repo.nasutek.com/arch/contrib/trinity/x86_64/ [2] https://www.trinitydesktop.org/faq/install.php#greyscreen
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.
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@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@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
On 07/22/2019 10:52 AM, Lucas dos Santos wrote:
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.
Damn good work. Thank you for the effort. This has apparently hit suse/KDE3 as well on Tumbleweed. We'll spread your results and see if we can't get it solve. You should write a bug on trinity bugzilla so it can be tracked and worked.
Thanks again.
On Tue, 23 Jul 2019 at 02:30, David C. Rankin drankinatty@suddenlinkmail.com wrote:
On 07/22/2019 10:52 AM, Lucas dos Santos wrote:
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.
Damn good work. Thank you for the effort. This has apparently hit suse/KDE3 as well on Tumbleweed. We'll spread your results and see if we can't get it solve. You should write a bug on trinity bugzilla so it can be tracked and worked.
Thanks again.
-- David C. Rankin, J.D.,P.E.
Done: http://bugs.pearsoncomputing.net/show_bug.cgi?id=3027
Thanks for your attention!
-
David C. Rankin -
Lucas dos Santos