By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2179 - [CentOS 7] TDM won't start automatically
Summary: [CentOS 7] TDM won't start automatically
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.13.2 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2014-10-30 12:05 CDT by Kristopher
Modified: 2014-11-02 12:53 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2014-10-30 12:05:25 CDT 
On CentOS 7, enabling TDM as suggested on the wiki through the /etc/sysconfig/desktop file does *not* cause TDM to start on boot, nor does running the following command as root:

systemctl enable tdm

I have to start TDM manually by running the following command as root:

systemctl start tdm

Once started, TDM starts and behaves normally, aside from the broken "default" session type described in bug #2178 .
Comment 1 Francois Andriot 2014-11-02 08:08:33 CST 
Hello, I've updated the wiki to add instructions for CentOS 7.

See: 
https://wiki.trinitydesktop.org/RedHat_Trinity_Repository_Installation_Instructions
Comment 2 Kristopher 2014-11-02 08:52:37 CST 
I am reopening this bug because it is *not* fixed. The only thing added to the wiki which I hadn't tried in getting TDM to work was disabling the other display managers, however since I started with a bare-bones install (as in, nothing but a bash-powered command line) there are no other display managers installed. Despite this, I ran the "systemctl disable" commands from the wiki anyways, then disabled and re-enabled TDM, and rebooted: but to no avail. TDM will *not* start automatically. It will start only via a manual "systemctl start" command as suggested in the original post.
Comment 3 Francois Andriot 2014-11-02 09:23:25 CST 
I forgot to mention this in the other bug (2178):

Are you sure that your systemd is running "graphical" target by default ? (equivalent of the old "runlevel 5")

E.g. type: ls -l /etc/systemd/system/
You should see, among other:
  default.target -> /lib/systemd/system/graphical.target
and, if TDM was enabled:
  display-manager.service -> /usr/lib/systemd/system/tdm.service


If your "default.target" links to "multi-user.target", then this is equivalent of the old "runlevel 3", e.g. "no graphical interface at boot".

To enable graphical interface at boot:
 ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target


Please note that systemd configuration is not specific to TDE nor to Centos 7.
I'm not even sure that, if you install KDM or GDM, it will enable graphical boot automatically.
Comment 4 Kristopher 2014-11-02 12:53:53 CST 
(In reply to Francois Andriot from comment #3)
> I forgot to mention this in the other bug (2178):
> 
> Are you sure that your systemd is running "graphical" target by default ?
> (equivalent of the old "runlevel 5")
> 
> E.g. type: ls -l /etc/systemd/system/
> You should see, among other:
>   default.target -> /lib/systemd/system/graphical.target
> and, if TDM was enabled:
>   display-manager.service -> /usr/lib/systemd/system/tdm.service
> 
> 
> If your "default.target" links to "multi-user.target", then this is
> equivalent of the old "runlevel 3", e.g. "no graphical interface at boot".
> 
> To enable graphical interface at boot:
>  ln -sf /lib/systemd/system/graphical.target
> /etc/systemd/system/default.target
> 
> 
> Please note that systemd configuration is not specific to TDE nor to Centos
> 7.
> I'm not even sure that, if you install KDM or GDM, it will enable graphical
> boot automatically.

Aha! I had worked with systemd before, however I was completely unaware of the "targets" thing. Doing the symlink fixed it. Thanks.

I'd recommend mentioning it in the wiki for others who are also unaware of this.