9 Aug
2016
9 Aug
'16
11:41 a.m.
On booting a new installed xenial with trinity tdm I get the error message:
"A start job is running for Hold until boot process finishes up(time/no limit)"
which prevents starting the console logins.
Using sddm or lightdm works together with systemd.
I have looked into the systemd configuration of them both and changed the file
/lib/systemd/system/tdm.service according to the sddm configuration to
[Unit]
Description=Trinity Display Manager
Documentation=man:tdm-trinity(1)
Conflicts=getty(a)tty7.service
After=getty(a)tty7.service
# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service plymouth-quit-wait.se
OnFailure=plymouth-quit.service
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(basename $(cat /etc/X11/default-display-manager
2>
ExecStart=/opt/trinity/bin/tdm
Restart=always
RestartSec=1s
With this file the plymouth/systemd handshake seams to work.
Maybe this helps someone else.
Stef
9 Aug
9 Aug
2:01 p.m.
New subject: [trinity-users] Problem on ubuntu 16.04 with systemd and tdm-trinity and a proposed solution
On Tue, 9 Aug 2016, update wrote:
On booting a new installed xenial with trinity tdm I
get the error message:
"A start job is running for Hold until boot process finishes up(time/no limit)"
which prevents starting the console logins.
Using sddm or lightdm works together with systemd.
I have looked into the systemd configuration of them both and changed the file
/lib/systemd/system/tdm.service according to the sddm configuration to
[Unit]
Description=Trinity Display Manager
Documentation=man:tdm-trinity(1)
Conflicts=getty(a)tty7.service
After=getty(a)tty7.service
# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service plymouth-quit-wait.se
OnFailure=plymouth-quit.service
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(basename $(cat /etc/X11/default-display-manager
2>
ExecStart=/opt/trinity/bin/tdm
Restart=always
RestartSec=1s
With this file the plymouth/systemd handshake seams to work.
Maybe this helps someone else.
Maybe... I hope so...
I had the same boot "freeze" here on xenial:
"A start job is running for Hold until boot process finishes up(time/no limit)"
I did not connect it with trinity tdm. Googling show me folks with the
same issue -- but different causes/fixes -- none of which worked in my case.
Perhaps my problem is/was what you explain above.
What I did was remove systemd and go back to upstart.
If time permits and my frustration level stays low, I may try your fix, Stef.
I am still trying to beat several (other) problems into submission after
upgrading to Ub 16.04.
Thanks for your report!
Jonesy
--
Marvin L Jones | Marvin | W3DHJ(.net) | linux
Pueblo, Colorado | @ | Jonesy | FreeBSD __
38.238N 104.547W | jonz.net | DM78rf | OS/2 SK
2:04 p.m.
New subject: [trinity-users] Problem on ubuntu 16.04 with systemd and tdm-trinity and a proposed solution
On Tuesday 09 of August 2016 13:41:59 update wrote:
On booting a new installed xenial with trinity tdm I
get the error
message: "A start job is running for Hold until boot process finishes
up(time/no limit)" which prevents starting the console logins. Using
sddm or lightdm works together with systemd.
I have looked into the systemd configuration of them both and changed
the file /lib/systemd/system/tdm.service according to the sddm
configuration to
[Unit]
Description=Trinity Display Manager
Documentation=man:tdm-trinity(1)
Conflicts=getty(a)tty7.service
After=getty(a)tty7.service
# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service
plymouth-quit-wait.se OnFailure=plymouth-quit.service
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(basename $(cat
/etc/X11/default-display-manager 2> ExecStart=/opt/trinity/bin/tdm
Restart=always
RestartSec=1s
With this file the plymouth/systemd handshake seams to work.
Maybe this helps someone else.
Stef
Do you have installed Ubuntu Xenial 16.04.1 == binutils 2.26.1?
--
Slávek
5:22 p.m.
New subject: [trinity-users] Problem on ubuntu 16.04 with systemd and tdm-trinity and a proposed solution
On Tuesday, 9. August 2016, Slávek Banko wrote:
On Tuesday 09 of August 2016 13:41:59 update wrote:
Yes I have 16.04.1 and binutuils is Version: 2.26.1-1ubuntu1~16.04.1 .
Stef
On booting a new installed xenial with trinity
tdm I get the error
message: "A start job is running for Hold until boot process finishes
up(time/no limit)" which prevents starting the console logins. Using
sddm or lightdm works together with systemd.
I have looked into the systemd configuration of them both and changed
the file /lib/systemd/system/tdm.service according to the sddm
configuration to
[Unit]
Description=Trinity Display Manager
Documentation=man:tdm-trinity(1)
Conflicts=getty(a)tty7.service
After=getty(a)tty7.service
# Ordering
Conflicts=plymouth-quit-wait.service
After=systemd-user-sessions.service plymouth-start.service
plymouth-quit-wait.se OnFailure=plymouth-quit.service
[Service]
# temporary safety check until all DMs are converted to correct
# display-manager.service symlink handling
ExecStartPre=/bin/sh -c '[ "$(basename $(cat
/etc/X11/default-display-manager 2> ExecStart=/opt/trinity/bin/tdm
Restart=always
RestartSec=1s
With this file the plymouth/systemd handshake seams to work.
Maybe this helps someone else.
Stef
Do you have installed Ubuntu Xenial 16.04.1 == binutils 2.26.1?
2820
days inactive
2820
days old
3 comments
3 participants
participants (3)
-
Jonesy -
Slávek Banko -
update