Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #166445 > unrolled thread

Debian 8 fresh install, lost MATE desktop (lightdm) after first reboot, cannot recover graphical login

Back to article view | Back to linux.debian.user

Contents

  Debian 8 fresh install, lost MATE desktop (lightdm) after first  reboot, cannot recover graphical login Tom Browder <tom.browder@gmail.com> - 2016-04-06 00:30 +0200
    Re: Debian 8 fresh install, lost MATE desktop (lightdm) after first  reboot, cannot recover graphical login arian <debian@semioptimal.net> - 2016-04-06 00:30 +0200
      Fwd: Debian 8 fresh install, lost MATE desktop (lightdm) after first  reboot, cannot recover graphical login Tom Browder <tom.browder@gmail.com> - 2016-04-07 12:20 +0200

#166445 — Debian 8 fresh install, lost MATE desktop (lightdm) after first reboot, cannot recover graphical login

Yesterday, after a week with my new Debian 8 desktop running Mate, I
did an "aptitude update" and somehow upgraded "fglrx-control" among
other things (I have no idea if that was the genesis of my problem,
but later I found some nvidia packages installed wile I have an Intel
graphics device).  I merrily continued to work until I had to shutdown
to go to my Linux group meeting.  There I booted up my laptop (he
first reboot after the intial install) and could not get a graphical
display!

I have fooled with it all day to no avail.  I discovered just now that
I can get an X program to display from a remote login into the laptop,
but nothing on the physical laptop.  I have tried reinstalling MATE as
well as xfce to no avail.

When booting I get a flash of a message saying:

  [FAILED] Failed to start Light Display Manager.
  See 'systemctl status lightdm.service' for details.

When I execute "systemctl status lightdm.service" I get:

# systemctl status lightdm.service
* lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: failed (Result: start-limit) since Tue 2016-04-05 14:31:51
CDT; 3min 19s ago
     Docs: man:lightdm(1)
  Process: 833 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 829 ExecStartPre=/bin/sh -c [ "$(cat
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ]
(code=exited, status=0/SUCCESS)
 Main PID: 833 (code=exited, status=1/FAILURE)

Apr 05 14:31:51 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 14:31:51 juvat2 systemd[1]: Unit lightdm.service entered failed state.
Apr 05 14:31:51 juvat2 systemd[1]: lightdm.service start request
repeated too quickly, refusing to start.
Apr 05 14:31:51 juvat2 systemd[1]: Failed to start Light Display Manager.
Apr 05 14:31:51 juvat2 systemd[1]: Unit lightdm.service entered failed state.

I will reinstall Debian 8 from scratch if necessary, but that would be
a real pain, so I would appreciate any hints.

Thanks.

Best regards,

-Tom

[toc] | [next] | [standalone]

#166446

[Multipart message — attachments visible in raw view] — view raw

> # systemctl status lightdm.service
> * lightdm.service - Light Display Manager
> [...]
please retrieve the actual logs from
# journalctl -u lightdm

[toc] | [prev] | [next] | [standalone]

#166496

[Multipart message — attachments visible in raw view] — view raw

I just realized I didn't post my reply to the list.

-Tom

---------- Forwarded message ----------
From: *Tom Browder* <tom.browder@gmail.com>
Date: Tuesday, April 5, 2016
Subject: Debian 8 fresh install, lost MATE desktop (lightdm) after first
reboot, cannot recover graphical login
To: arian <debian@semioptimal.net>


On Tue, Apr 5, 2016 at 5:26 PM, arian <debian@semioptimal.net <javascript:;>>
wrote:
> please retrieve the actual logs from
> # journalctl -u lightdm

Output of "journalctl -u lightdm" follows:

# journalctl -u lightdm
-- Logs begin at Tue 2016-04-05 16:50:35 CDT, end at Tue 2016-04-05
17:51:15 CDT. --
Apr 05 16:50:46 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 16:50:46 juvat2 systemd[1]: Unit lightdm.service entered failed
state.
Apr 05 16:50:47 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 16:50:47 juvat2 systemd[1]: Unit lightdm.service entered failed
state.
Apr 05 16:50:47 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 16:50:47 juvat2 systemd[1]: Unit lightdm.service entered failed
state.
Apr 05 16:50:48 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 16:50:48 juvat2 systemd[1]: Unit lightdm.service entered failed
state.
Apr 05 16:50:48 juvat2 systemd[1]: lightdm.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 16:50:48 juvat2 systemd[1]: Unit lightdm.service entered failed
state.
Apr 05 16:50:48 juvat2 systemd[1]: lightdm.service start request
repeated too quickly, refusing to start.
Apr 05 16:50:48 juvat2 systemd[1]: Failed to start Light Display Manager.
Apr 05 16:50:48 juvat2 systemd[1]: Unit lightdm.service entered failed state

Thanks, arian.

Best,

-Tom

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web