Hello Folks
I know there's many questions about 'no graphical environment on server', but I've install gnome and enabled it.
After booting the display hangs following: [ OK ] Started GNOME Display Manager And, perhaps a few following such as starting virtualisation demon, waiting for plymouth to quit
Following a server install I ran the following successfully: # yum groupinstall gnome --skip-broken # systemctl set-default graphical.target
This this is what systemctl says: ]# systemctl status -l gdm.service ● gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled) Active: failed (Result: start-limit) since Sun 2015-03-08 17:51:35 GMT; 1min 29s ago Process: 1613 ExecStart=/usr/sbin/gdm (code=exited, status=1/FAILURE) Main PID: 1613 (code=exited, status=1/FAILURE)
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service: main process exited, code=exited, status=1/FAILURE Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered failed state. Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed. Mar 08 17:51:35 frontserver.lan systemd[1]: start request repeated too quickly for gdm.service Mar 08 17:51:35 frontserver.lan systemd[1]: Failed to start GNOME Display Manager. Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered failed state. Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed.
Any pointers would be very much appreciated.
Many thanks. Morgan
It think you need to do: systemctl enable gdm
There might be some other services that need to be enabled. This is the enabled list for a recent installation of Fedora 21 Workstation:
Chris Murphy
On Mar 8, 2015 1:50 PM, "Morgan Read" mstuff@read.org.nz wrote:
Hello Folks
I know there's many questions about 'no graphical environment on server',
but I've install gnome and enabled it.
After booting the display hangs following: [ OK ] Started GNOME Display Manager And, perhaps a few following such as starting virtualisation demon,
waiting for plymouth to quit
Following a server install I ran the following successfully: # yum groupinstall gnome --skip-broken # systemctl set-default graphical.target
This this is what systemctl says: ]# systemctl status -l gdm.service ● gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled) Active: failed (Result: start-limit) since Sun 2015-03-08 17:51:35
GMT; 1min 29s ago
Process: 1613 ExecStart=/usr/sbin/gdm (code=exited, status=1/FAILURE) Main PID: 1613 (code=exited, status=1/FAILURE)
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service: main process
exited, code=exited, status=1/FAILURE
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed. Mar 08 17:51:35 frontserver.lan systemd[1]: start request repeated too
quickly for gdm.service
Mar 08 17:51:35 frontserver.lan systemd[1]: Failed to start GNOME Display
Manager.
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed.
Any pointers would be very much appreciated.
Many thanks. Morgan -- Morgan Read
Confused about DRM? Get all the info you need at: http://drm.info/ --
Hi Morgan,
I'm asking out of personal curiosity, so please don't take this as a criticism. If you wanted a GNOME desktop, why did you install Fedora Server instead of Fedora Workstation?
--Pete
One really great reason to install Fedora server is that logging, using rsyslog, works out of the box.
After learning this (this list, last week), I will be avoiding any desktop type installers, preferring the server image for workstation and laptop installs.
On Mon, Mar 9, 2015 at 9:34 AM, Pete Travis lists@petetravis.com wrote:
On Mar 8, 2015 1:50 PM, "Morgan Read" mstuff@read.org.nz wrote:
Hello Folks
I know there's many questions about 'no graphical environment on
server', but I've install gnome and enabled it.
After booting the display hangs following: [ OK ] Started GNOME Display Manager And, perhaps a few following such as starting virtualisation demon,
waiting for plymouth to quit
Following a server install I ran the following successfully: # yum groupinstall gnome --skip-broken # systemctl set-default graphical.target
This this is what systemctl says: ]# systemctl status -l gdm.service ● gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled) Active: failed (Result: start-limit) since Sun 2015-03-08 17:51:35
GMT; 1min 29s ago
Process: 1613 ExecStart=/usr/sbin/gdm (code=exited, status=1/FAILURE) Main PID: 1613 (code=exited, status=1/FAILURE)
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service: main process
exited, code=exited, status=1/FAILURE
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed. Mar 08 17:51:35 frontserver.lan systemd[1]: start request repeated too
quickly for gdm.service
Mar 08 17:51:35 frontserver.lan systemd[1]: Failed to start GNOME
Display Manager.
Mar 08 17:51:35 frontserver.lan systemd[1]: Unit gdm.service entered
failed state.
Mar 08 17:51:35 frontserver.lan systemd[1]: gdm.service failed.
Any pointers would be very much appreciated.
Many thanks. Morgan -- Morgan Read
Confused about DRM? Get all the info you need at: http://drm.info/ --
Hi Morgan,
I'm asking out of personal curiosity, so please don't take this as a criticism. If you wanted a GNOME desktop, why did you install Fedora Server instead of Fedora Workstation?
--Pete
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 09.03.2015 23:35, Morgan Read wrote: ...
[root@frontserver ~]# systemctl is-enabled cups.path abrt-ccpp.service abrt-oops.service abrt-vmcore.service abrt-xorg.service abrtd.service accounts-daemon.service atd.service auditd.service avahi-daemon.service bluetooth.service chronyd.service crond.service cups.service dbus-org.bluez.service dbus-org.fedoraproject.FirewallD1.service dbus-org.freedesktop.Avahi.service dbus-org.freedesktop.ModemManager1.service dbus-org.freedesktop.NetworkManager.service dbus-org.freedesktop.nm-dispatcher.service display-manager.service dmraid-activation.service firewalld.service gdm.servicegetty@.service iscsi.service libvirtd.service lvm2-monitor.service mcelog.service mdmonitor.service ModemManager.service multipathd.service netcf-transaction.service NetworkManager-dispatcher.service NetworkManager.service rngd.service rsyslog.service rtkit-daemon.service smartd.service spice-vdagentd.service sshd.service syst emd-reada head-collect.service systemd-readahead-drop.service systemd-readahead-replay.service vmtoolsd.service avahi-daemon.socket cups.socket dm-event.socket iscsid.socket iscsiuio.socket lvm2-lvmetad.socket rpcbind.socket default.target graphical.target nfs-client.target remote-fs.target dnf-makecache.timer enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled
$ systemctl list-unit-files | grep enabled ;)
Hi Pete - no criticism taken :)
I want to run a server because I want to serve things... ftp, mail, printer, media, backup, dhcp, samba, freeswitch, owncloud and much much more... Strange, but true
Still getting to the bottom of all this. I followed Chris Murphy's lead and this is what I now get from the list at http://ur1.ca/jvh4d
[root@frontserver ~]# systemctl is-enabled cups.path abrt-ccpp.service abrt-oops.service abrt-vmcore.service abrt-xorg.service abrtd.service accounts-daemon.service atd.service auditd.service avahi-daemon.service bluetooth.service chronyd.service crond.service cups.service dbus-org.bluez.service dbus-org.fedoraproject.FirewallD1.service dbus-org.freedesktop.Avahi.service dbus-org.freedesktop.ModemManager1.service dbus-org.freedesktop.NetworkManager.service dbus-org.freedesktop.nm-dispatcher.service display-manager.service dmraid-activation.service firewalld.service gdm.service getty@.service iscsi.service libvirtd.service lvm2-monitor.service mcelog.service mdmonitor.service ModemManager.service multipathd.service netcf-transaction.service NetworkManager-dispatcher.service NetworkManager.service rngd.service rsyslog.service rtkit-daemon.service smartd.service spice-vdagentd.service sshd.service systemd-reada head-collect.service systemd-readahead-drop.service systemd-readahead-replay.service vmtoolsd.service avahi-daemon.socket cups.socket dm-event.socket iscsid.socket iscsiuio.socket lvm2-lvmetad.socket rpcbind.socket default.target graphical.target nfs-client.target remote-fs.target dnf-makecache.timer enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled [root@frontserver ~]#
That was after installing ModemManager-glib-devel-1.4.0-1.fc21.i686 spice-vdagent-0.15.0-3.fc21.i686 dnf-0.6.4-1.fc21.noarch
And enabling those plus rpcbind.socket
But, still no boot into a graphical interface.
I've put the output /var/log/messages here: https://app.box.com/s/kb0becxjig2wmnl0b6468v83a85nd4wy Of interest perhaps are the following errors which seem to follow the point I'd expect gnome to kicking: Mar 9 21:45:17 frontserver rngd: Error writing /dev/tpm0 Mar 9 21:45:17 frontserver kernel: tpm_tis 00:04: tpm_transmit: tpm_send: error -16 Mar 9 21:45:18 frontserver kernel: [ 135.139069] tpm_tis 00:04: tpm_transmit: tpm_send: error -16
I'm beginning to wonder if bug report is needed...
thanks, M.
-
Chris Murphy -
Dan Irwin -
Morgan Read -
Pete Travis -
poma