[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

wheezy to jessie upgrade: gdm system.d failure



The dist-upgrade with no apparent problems but gdm3 desktop failed to
open.  I ran /etc/init.d/gdm3 restart which failed with messages to
check systemctl status gdm.service and journalctl -xn. The outputs of
these commands are given below.

I ENCOUNTERED THIS SAME PROBLEM WITH THE INSTILLATION OF JESSIE ON A NEW
COMPUTER, POSTED THE DESCRIPTION TO THE DEBIAN USER LIST AND RECEIVE NO
HELP.

On the new computer quite by accident I discovered that if I created a
new user the gnome desktop would open for the new user.  By tranferring
files I was eventually able use the original user name and eliminate the
dummy user. I don't want to do that on this computer which has all my
files and setups though much of the information was backed up before
starting the upgrade. 

I belive the problem is with a setting in systemd and that an expert in
jessie and systemd should be able to resolve it from the error outputs
given below.

Tom


Script started on Mon 11 May 2015 02:46:00 PM EDT
dragon:~# systemctl status gdm.service
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; enabled)
   Active: failed (Result: start-limit) since Mon 2015-05-11 14:37:22 EDT; 9min ago
  Process: 2067 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=1/FAILURE)

May 11 14:37:21 dragon systemd[1]: Triggering OnFailure= dependencies of gdm.service.
May 11 14:37:21 dragon systemd[1]: Failed to enqueue OnFailure= job: Invalid argument
May 11 14:37:22 dragon systemd[1]: gdm.service holdoff time over, scheduling restart.
May 11 14:37:22 dragon systemd[1]: Stopping GNOME Display Manager...
May 11 14:37:22 dragon systemd[1]: Starting GNOME Display Manager...
May 11 14:37:22 dragon systemd[1]: gdm.service start request repeated too quickly, refusing to start.
May 11 14:37:22 dragon systemd[1]: Failed to start GNOME Display Manager.
May 11 14:37:22 dragon systemd[1]: Unit gdm.service entered failed state.
May 11 14:37:22 dragon systemd[1]: Triggering OnFailure= dependencies of gdm.service.
May 11 14:37:22 dragon systemd[1]: Failed to enqueue OnFailure= job: Invalid argument
dragon:~# exit

Script done on Mon 11 May 2015 02:46:27 PM EDT


Script started on Mon 11 May 2015 02:42:40 PM EDT
dragon:~# journalctl -xn

-- Logs begin at Mon 2015-05-11 14:31:09 EDT, end at Mon 2015-05-11 14:39:02 EDT. --
May 11 14:37:22 dragon systemd[1]: Starting GNOME Display Manager...
-- Subject: Unit gdm.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit gdm.service has begun starting up.
May 11 14:37:22 dragon systemd[1]: gdm.service start request repeated too quickly, refusing to start.
May 11 14:37:22 dragon systemd[1]: Failed to start GNOME Display Manager.
-- Subject: Unit gdm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit gdm.service has failed.
-- 
-- The result is failed.
May 11 14:37:22 dragon systemd[1]: Unit gdm.service entered failed state.
May 11 14:37:22 dragon systemd[1]: Triggering OnFailure= dependencies of gdm.service.
May 11 14:37:22 dragon systemd[1]: Failed to enqueue OnFailure= job: Invalid argument
May 11 14:39:01 dragon CRON[2075]: pam_env(cron:session): Unable to open env file: /etc/environment: No such file or dir
May 11 14:39:01 dragon CRON[2075]: pam_unix(cron:session): session opened for user root by (uid=0)
May 11 14:39:01 dragon CRON[2076]: (root) CMD (  [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
May 11 14:39:02 dragon CRON[2075]: pam_unix(cron:session): session closed for user root
lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)

lines 1-23/23 (END)
dragon:~# exit

Script done on Mon 11 May 2015 02:44:59 PM EDT


Reply to: