Looking in journal and Xorg.0.log I see no clues. X starts, but startx just starts X and exits. Trinity-tdm is installed, but no other *dm, and I see no evidence of its configuration in systemctl list-unit-files or systemctl list-units. /var/log/tdm.log was last written over a year ago. Trinity tries to start using startx /opt/trinity/bin/starttde, but a popup comes twice, then X exits:
"There was an error setting up inter-process communications for TDE. The messag returned by the system was:
Could not read network connection list. /root/.DCOPserver_hp945_0
Please check that the "dcopserver" program is running!"
startx icewm works.
How does one do that, and why isn't there a TDM running?
On Thursday 26 of September 2019 04:14:33 Felix Miata wrote:
Looking in journal and Xorg.0.log I see no clues. X starts, but startx just starts X and exits. Trinity-tdm is installed, but no other *dm, and I see no evidence of its configuration in systemctl list-unit-files or systemctl list-units. /var/log/tdm.log was last written over a year ago. Trinity tries to start using startx /opt/trinity/bin/starttde, but a popup comes twice, then X exits:
"There was an error setting up inter-process communications for TDE. The messag returned by the system was:
Could not read network connection list. /root/.DCOPserver_hp945_0
Please check that the "dcopserver" program is running!"
startx icewm works.
How does one do that, and why isn't there a TDM running?
Hi Felix,
acording to the error message you receive, it looks like this problem:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=3027
...and here you can see the workaround that can be used before we make a change in the source code:
http://trinity-users.pearsoncomputing.net/?0::15847
Cheers
Felix Miata composed on 2019-09-25 22:14 (UTC-0400):
Looking in journal and Xorg.0.log I see no clues. X starts, but startx just starts X and exits. Trinity-tdm is installed, but no other *dm, and I see no evidence of its configuration in systemctl list-unit-files or systemctl list-units. /var/log/tdm.log was last written over a year ago. Trinity tries to start using startx /opt/trinity/bin/starttde, but a popup comes twice, then X exits:
"There was an error setting up inter-process communications for TDE. The messag returned by the system was:
Could not read network connection list. /root/.DCOPserver_hp945_0
Please check that the "dcopserver" program is running!"
startx icewm works.
How does one do that, and why isn't there a TDM running?
startx /opt/trinity/bin/starttde works, but why not TDM? MCC claims it setup TDM, but it's not happening. The only places dm shows up in the journal are within HDMI, administator, dma and loadmodules.
Le 17/10/2019 à 07:02, Felix Miata a écrit :
startx /opt/trinity/bin/starttde works, but why not TDM? MCC claims it setup TDM, but it's not happening. The only places dm shows up in the journal are within HDMI, administator, dma and loadmodules.
Hello, It looks like Mageia 7 now uses normal systemd configuration files to manage display manager, instead of mageia specific files in previous version.
So, you can try to create a file '/usr/lib/systemd/system/tdm.service' with following content:
[Unit] Description=Trinity Display Manager Documentation=man:tdm(1) Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service systemd-logind.service
[Service] ExecStart=/opt/trinity/bin/tdm Restart=always
[Install] Alias=display-manager.service
Then, you can reboot your computer and TDM should start automatically.
If this does the job for you, I will update the package.
François
Felix Miata composed on 2019-10-17 01:02 (UTC-0400):
Felix Miata composed on 2019-09-25 22:14 (UTC-0400):
Looking in journal and Xorg.0.log I see no clues. X starts, but startx just starts X and exits. Trinity-tdm is installed, but no other *dm, and I see no evidence of its configuration in systemctl list-unit-files or systemctl list-units. /var/log/tdm.log was last written over a year ago. Trinity tries to start using startx /opt/trinity/bin/starttde, but a popup comes twice, then X exits:
"There was an error setting up inter-process communications for TDE. The messag returned by the system was:
Could not read network connection list. /root/.DCOPserver_hp945_0
Please check that the "dcopserver" program is running!"
startx icewm works.
How does one do that, and why isn't there a TDM running?
startx /opt/trinity/bin/starttde works, but why not TDM? MCC claims it setup TDM, but it's not happening. The only places dm shows up in the journal are within HDMI, administator, dma and loadmodules.
Still no progress trying to figure out what is supposed to start TDM or control which dm is configured. :-( Is it supposed to be something in /etc/alternatives? /etc/systemd/system/graphical.target.wants? Why is there no display-manager.service? Reinstalling trinity-tdm doesn't help.
Le 26/10/2019 à 05:40, Felix Miata a écrit :
DMI, administator, dma and loadmodules. Still no progress trying to figure out what is supposed to start TDM or control which dm is configured. :-( Is it supposed to be something in /etc/alternatives? /etc/systemd/system/graphical.target.wants? Why is there no display-manager.service? Reinstalling trinity-tdm doesn't help.
Hello, It looks like Mageia 7 now uses normal systemd configuration files to manage display manager, instead of mageia specific files in previous version.
So, you can try to create a file '/usr/lib/systemd/system/tdm.service' with following content:
[Unit] Description=Trinity Display Manager Documentation=man:tdm(1) Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service systemd-logind.service
[Service] ExecStart=/opt/trinity/bin/tdm Restart=always
[Install] Alias=display-manager.service
Then, you can reboot your computer and TDM should start automatically if it was selected in Mageia Control Center.
If this does the job for you, please report and I will update the package.
François
Messages I try to send directly to François Andriot bounce. Messages composed by François Andriot and sent to the list never reach me. What follows has been constructed from: http://trinity-users.pearsoncomputing.net/?0::16189
François Andriot composed 26 Oct 2019 13:14:31 +0200:
Felix Miata composed on 2019-10-25 23:40 (UTC-0500):
Still no progress trying to figure out what is supposed to start TDM or control which dm is configured. :-( Is it supposed to be something in /etc/alternatives? /etc/systemd/system/graphical.target.wants? Why is there no display-manager.service? Reinstalling trinity-tdm doesn't help.
Hello, It looks like Mageia 7 now uses normal systemd configuration files to manage display manager, instead of mageia specific files in previous version.
So, you can try to create a file '/usr/lib/systemd/system/tdm.service' with following content:
[Unit] Description=Trinity Display Manager Documentation=man:tdm(1) Conflicts=getty@... After=systemd-user-sessions.service getty@... plymouth-quit.service systemd-logind.service
[Service] ExecStart=/opt/trinity/bin/tdm Restart=always
[Install] Alias=display-manager.service
I tried, but was unable to find how to manage display manager in MCC. However, I created /etc/systemd/system/tdm.service with that content, and then
systemctl enable tdm.service
worked. :)
Felix Miata composed on 2019-12-04 03:48 (UTC-0500):
I created /etc/systemd/system/tdm.service with that content, and then
systemctl enable tdm.service
worked. :)
While it works, something is wrong: # systemctl status tdm ● tdm.service - Trinity Display Manager Loaded: loaded (/etc/systemd/system/tdm.service; enabled; vendor preset: disabled) Active: inactive (dead) Docs: man:tdm(1)
Dec 04 21:08:09 gx62b systemd[1]: /etc/systemd/system/tdm.service:4: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:08:09 gx62b systemd[1]: /etc/systemd/system/tdm.service:5: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:08:09 gx62b systemd[1]: /etc/systemd/system/tdm.service:6: Missing '=', ignoring line. Dec 04 21:16:00 gx62b systemd[1]: /etc/systemd/system/tdm.service:4: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:16:00 gx62b systemd[1]: /etc/systemd/system/tdm.service:5: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:16:00 gx62b systemd[1]: /etc/systemd/system/tdm.service:6: Missing '=', ignoring line. Dec 04 21:16:02 gx62b systemd[1]: /etc/systemd/system/tdm.service:4: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:16:02 gx62b systemd[1]: /etc/systemd/system/tdm.service:5: Failed to add dependency on getty@..., ignoring: Unknown error -22 Dec 04 21:16:02 gx62b systemd[1]: /etc/systemd/system/tdm.service:6: Missing '=', ignoring line. Dec 04 21:54:58 gx62b systemd[1]: /etc/systemd/system/tdm.service:6: Missing '=', ignoring line. # /etc/systemd/system/tdm.service [Unit] Description=Trinity Display Manager Documentation=man:tdm(1) Conflicts=getty@... After=systemd-user-sessions.service getty@... plymouth-quit.service systemd-logind.service
[Service] ExecStart=/opt/trinity/bin/tdm Restart=always
[Install] Alias=display-manager.service
Apparently the archive thinks those lines with @ are email addresses, so redacted them.
-
Felix Miata -
François Andriot -
Slávek Banko