Lightdm doesn't run after upgrade {closed}

Questions specific to the KDE DE go here
JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Lightdm doesn't run after upgrade {closed}

Postby JSladek » 11 Sep 2017 15:45

I have been have a terrible time trying to get this upgrade accomplished. After far too many tries, I finally got the deb9 files installed only by uninstalling all of the Nvidia files. I had to do that because whenever I got to the point where the deb9 install would start, the install always tried to install a version of the Nvidia driver that I knew would not work with my card.

I have tried to build on a fresh version of 9, but I have some old applications that will not install for various reasons.

So much for my tale of woe.

In short - ligthdm will not run on startup. The machine gets to tty1 and that's it. inxi data follows:

Code: Select all

jim@jim ~ $  inxi -Fzx
System:    Host: jim Kernel: 4.9.0-3-amd64 x86_64 (64 bit gcc: 6.3.0) 
           Console: (tty1) Distro: SolydXK
Machine:   Device: desktop
	   System: O.E.M product: O.E.M
           Mobo: FOXCONN model: G41AP/G41AP-S v: 1.0
           Bios: American Megatrends v: 080015 date: 04/18/2011
CPU:       Dual core Intel Core2 Duo E8400 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 11998 
           Clock Speeds: 1: 2003 MHz 2: 2003 MHz
Graphics:  Card: NVIDIA G98 [GeForce 8400 GS Rev. 2] bus-ID: 01:00.0
           Display Server: X.Org 1.19.2 driver: N/A
           tty size: 80x25 Advanced Data: N/A for root out of X
Audio:     Advanced Linux Sound Architecture k4.9.0-3-amd64
Network:   Card: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
           driver: 8139too v: 0.9.28 port: e800 bus-ID: 04:04.0
           IF: eth1 state: unknown speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 370.1GB (10.0% used)
           ID-1: /dev/sda model: WDC_WD2500AAJS size: 250.1GB temp: 41C
           ID-2: /dev/sdb model: SSD2SC120G1CS175 size: 120.0GB temp: 42C
Partition: ID-1: / size: 31G used: 6.4G (22%) fs: ext4 dev: /dev/sdb1 
           ID-2: /home size: 56G used: 5.2G (10%) fs: ext4 dev: /dev/sdb2 
           ID-3: /var size: 15G used: 3.5G (25%) fs: ext4 dev: /dev/sda11 
           ID-4: swap-1 size: 3.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 123 Uptime: 1 min Memory: 123.9/7987.4MB 
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (sudo) inxi: 2.3.5
In console, I checked the status of lightdm with "systemctl status lightdm.service" and received the following report:

Code: Select all

● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2017-09-10 23:01:01 UTC; 5min ago
     Docs: man:lightdm(1)
  Process: 989 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 987 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 989 (code=exited, status=1/FAILURE)

Sep 10 23:01:01 jim systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 10 23:01:01 jim systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep 10 23:01:01 jim systemd[1]: Stopped Light Display Manager.
Sep 10 23:01:01 jim systemd[1]: lightdm.service: Start request repeated too quickly.
Sep 10 23:01:01 jim systemd[1]: Failed to start Light Display Manager.
Sep 10 23:01:01 jim systemd[1]: lightdm.service: Unit entered failed state.
Sep 10 23:01:01 jim systemd[1]: lightdm.service: Failed with result 'exit-code'.
"/usr/sbin/lightdm" is in /etc/X11/default-display-manager and lightdm-gtk-greeter is in /usr/sbin. Lightdm does not start manually in tty1.

Okay - where do I go from here ........

User avatar
ilu
Posts: 2072
Joined: 09 Oct 2013 12:45

Re: Lightdm doesn't run after upgrade

Postby ilu » 11 Sep 2017 21:15

I'm trying to understand your situation:
You tried to upgrade to SolydK9 and this finally worked - but the SolydK9 boot hangs at emergency login because of lightdm? or: You tried to upgrade to SolydK9 but since you have old applications that don't work under 9, you are now back to 8 where lightdm won't start anymore?

I probably won't be able to help myself but I think the output of "ps -aux" could give more information for somebody more knowledgeable than me.

JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Re: Lightdm doesn't run after upgrade

Postby JSladek » 11 Sep 2017 21:38

You had it right in the first instance. The SolydK9 bootup hangs because lightdm is failing to run. Output from ps -aux follows:

Code: Select all

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  2.4  0.0 139436  7348 ?        Ss   22:00   0:04 /lib/systemd/systemd nosplash
root         2  0.0  0.0      0     0 ?        S    22:00   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    22:00   0:00 [ksoftirqd/0]
root         4  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/0:0]
root         5  0.0  0.0      0     0 ?        S<   22:00   0:00 [kworker/0:0H]
root         6  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/u8:0]
root         7  0.0  0.0      0     0 ?        S    22:00   0:00 [rcu_sched]
root         8  0.0  0.0      0     0 ?        S    22:00   0:00 [rcu_bh]
root         9  0.0  0.0      0     0 ?        S    22:00   0:00 [migration/0]
root        10  0.0  0.0      0     0 ?        S<   22:00   0:00 [lru-add-drain]
root        11  0.0  0.0      0     0 ?        S    22:00   0:00 [watchdog/0]
root        12  0.0  0.0      0     0 ?        S    22:00   0:00 [cpuhp/0]
root        13  0.0  0.0      0     0 ?        S    22:00   0:00 [cpuhp/1]
root        14  0.0  0.0      0     0 ?        S    22:00   0:00 [watchdog/1]
root        15  0.0  0.0      0     0 ?        S    22:00   0:00 [migration/1]
root        16  0.0  0.0      0     0 ?        S    22:00   0:00 [ksoftirqd/1]
root        17  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/1:0]
root        18  0.0  0.0      0     0 ?        S<   22:00   0:00 [kworker/1:0H]
root        19  0.0  0.0      0     0 ?        S    22:00   0:00 [kdevtmpfs]
root        20  0.0  0.0      0     0 ?        S<   22:00   0:00 [netns]
root        21  0.0  0.0      0     0 ?        S    22:00   0:00 [khungtaskd]
root        22  0.0  0.0      0     0 ?        S    22:00   0:00 [oom_reaper]
root        23  0.0  0.0      0     0 ?        S<   22:00   0:00 [writeback]
root        24  0.0  0.0      0     0 ?        S    22:00   0:00 [kcompactd0]
root        25  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/1:1]
root        26  0.0  0.0      0     0 ?        SN   22:00   0:00 [ksmd]
root        27  0.0  0.0      0     0 ?        SN   22:00   0:00 [khugepaged]
root        28  0.0  0.0      0     0 ?        S<   22:00   0:00 [crypto]
root        29  0.0  0.0      0     0 ?        S<   22:00   0:00 [kintegrityd]
root        30  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root        31  0.0  0.0      0     0 ?        S<   22:00   0:00 [kblockd]
root        32  0.0  0.0      0     0 ?        S<   22:00   0:00 [devfreq_wq]
root        33  0.0  0.0      0     0 ?        S<   22:00   0:00 [watchdogd]
root        34  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/0:1]
root        35  0.0  0.0      0     0 ?        S    22:00   0:00 [kswapd0]
root        36  0.0  0.0      0     0 ?        S<   22:00   0:00 [vmstat]
root        48  0.0  0.0      0     0 ?        S<   22:00   0:00 [kthrotld]
root        49  0.0  0.0      0     0 ?        S<   22:00   0:00 [ipv6_addrconf]
root        50  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/0:2]
root        88  0.0  0.0      0     0 ?        S<   22:00   0:00 [ata_sff]
root        89  0.0  0.0      0     0 ?        S<   22:00   0:00 [firewire]
root        98  0.0  0.0      0     0 ?        S<   22:00   0:00 [firewire_ohci]
root        99  0.0  0.0      0     0 ?        S<   22:00   0:00 [acpi_thermal_pm]
root       100  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/1:2]
root       101  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/u8:1]
root       104  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/1:3]
root       108  0.0  0.0      0     0 ?        S    22:00   0:00 [scsi_eh_0]
root       109  0.0  0.0      0     0 ?        S<   22:00   0:00 [scsi_tmf_0]
root       110  0.0  0.0      0     0 ?        S    22:00   0:00 [scsi_eh_1]
root       111  0.0  0.0      0     0 ?        S<   22:00   0:00 [scsi_tmf_1]
root       112  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/u8:2]
root       113  0.0  0.0      0     0 ?        S    22:00   0:00 [scsi_eh_2]
root       114  0.0  0.0      0     0 ?        S<   22:00   0:00 [scsi_tmf_2]
root       115  0.0  0.0      0     0 ?        S    22:00   0:00 [scsi_eh_3]
root       116  0.0  0.0      0     0 ?        S<   22:00   0:00 [scsi_tmf_3]
root       117  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/u8:3]
root       118  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/u8:4]
root       119  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/1:4]
root       120  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       121  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       122  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       123  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       125  0.0  0.0      0     0 ?        S<   22:00   0:00 [kworker/0:1H]
root       126  0.0  0.0      0     0 ?        S<   22:00   0:00 [kworker/1:1H]
root       134  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/0:3]
root       165  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       209  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sdb1-8]
root       210  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
root       241  0.0  0.0  46092  5180 ?        Ss   22:00   0:00 /lib/systemd/systemd-journald
root       251  0.0  0.0      0     0 ?        S    22:00   0:00 [kauditd]
root       266  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       268  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       269  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       270  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       271  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       272  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       273  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       274  0.0  0.0      0     0 ?        S<   22:00   0:00 [bioset]
root       283  0.1  0.0  46772  4416 ?        Ss   22:00   0:00 /lib/systemd/systemd-udevd
root       300  0.0  0.0      0     0 ?        S    22:00   0:00 [kworker/0:4]
root       414  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sdb2-8]
root       415  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
root       437  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sdb3-8]
root       443  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
root       465  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sda7-8]
root       466  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
root       468  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sda11-8]
root       469  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
root       476  0.0  0.0      0     0 ?        S    22:00   0:00 [jbd2/sda8-8]
root       477  0.0  0.0      0     0 ?        S<   22:00   0:00 [ext4-rsv-conver]
systemd+   503  0.0  0.0 131404  4160 ?        Ssl  22:00   0:00 /lib/systemd/systemd-timesyncd
root       585  0.0  0.0  29664  2884 ?        Ss   22:00   0:00 /usr/sbin/cron -f
root       588  0.0  0.0   4216  1144 ?        Ss   22:00   0:00 /usr/sbin/acpid
daemon     589  0.0  0.0  27964  2252 ?        Ss   22:00   0:00 /usr/sbin/atd -f
avahi      590  0.0  0.0  47280  3868 ?        Ss   22:00   0:00 avahi-daemon: running [jim.local]
root       591  0.0  0.0 283600  6640 ?        Ssl  22:00   0:00 /usr/lib/accountsservice/accounts-daemon
root       593  0.0  0.0  46504  4860 ?        Ss   22:00   0:00 /lib/systemd/systemd-logind
root       598  0.0  0.1 171520  8588 ?        Ssl  22:00   0:00 /usr/sbin/cupsd -l
avahi      603  0.0  0.0  47016   364 ?        S    22:00   0:00 avahi-daemon: chroot helper
rtkit      606  0.0  0.0 185748  3000 ?        SNsl 22:00   0:00 /usr/lib/rtkit/rtkit-daemon
root       607  0.0  0.0  35808  1916 ?        Ss   22:00   0:00 /usr/sbin/irqbalance --foreground
root       609  0.0  0.1 422568  8916 ?        Ssl  22:00   0:00 /usr/sbin/ModemManager
message+   610  0.0  0.0  45588  4200 ?        Ss   22:00   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root       620  0.0  0.1 258600  9028 ?        Ssl  22:00   0:00 /usr/sbin/cups-browsed
root       621  0.0  0.0 250116  3156 ?        Ssl  22:00   0:00 /usr/sbin/rsyslogd -n
root       623  0.0  0.2 481636 17448 ?        Ssl  22:00   0:00 /usr/sbin/NetworkManager --no-daemon
root       644  0.0  0.0      0     0 ?        S<   22:00   0:00 [iprt-VBoxWQueue]
root       647  0.0  0.0 286132  6332 ?        Ssl  22:00   0:00 /usr/lib/policykit-1/polkitd --no-debug
root       724  0.0  0.0  69944  5664 ?        Ss   22:00   0:00 /usr/sbin/sshd -D
root       736  0.0  0.0  90760  4184 tty1     Ss   22:00   0:00 /bin/login --
root       783  0.0  0.0  20348  4356 ?        S    22:00   0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-eth1.pid -lf /var/lib/NetworkManager/dhclient-f817e25b-6c18-36b9-98ae-73baf5fc0cd8-eth1.lease -cf /var/lib/NetworkManager/dhclient-eth1.conf eth1
colord    1156  0.0  0.1 313424 13424 ?        Ssl  22:00   0:00 /usr/lib/colord/colord
root      1170  0.0  0.1  46564  8312 ?        Ss   22:00   0:00 /usr/bin/apt-get update
root      1172  0.0  0.0   4192    88 ?        Ss   22:00   0:00 /usr/sbin/minissdpd -i 0.0.0.0
_apt      1181  0.0  0.0  46340  5884 ?        S    22:00   0:00 /usr/lib/apt/methods/http
_apt      1182  0.0  0.0  46340  5688 ?        S    22:00   0:00 /usr/lib/apt/methods/http
_apt      1183  1.1  0.0  46340  5828 ?        S    22:00   0:01 /usr/lib/apt/methods/http
_apt      1184  0.0  0.0  46340  5740 ?        S    22:00   0:00 /usr/lib/apt/methods/http
_apt      1186  0.0  0.0  41976  5576 ?        S    22:00   0:00 /usr/lib/apt/methods/gpgv
_apt      1330  3.1  0.1  50420 14268 ?        S    22:00   0:04 /usr/lib/apt/methods/store
jim       1479  0.0  0.0  65124  6676 ?        Ss   22:00   0:00 /lib/systemd/systemd --user
jim       1481  0.0  0.0 176156  2220 ?        S    22:00   0:00 (sd-pam)
root      1485  0.0  0.0 1062632 6488 ?        Ssl  22:00   0:00 /usr/sbin/console-kit-daemon --no-daemon
jim       1558  0.0  0.0  21080  4940 tty1     S    22:00   0:00 -bash
root      1652  0.0  0.0  72108  4160 tty1     S+   22:03   0:00 sudo ps -aux
root      1653  0.0  0.0  38304  3368 tty1     R+   22:03   0:00 ps -aux

kurotsugi
Posts: 2121
Joined: 09 Jan 2014 00:17

Re: Lightdm doesn't run after upgrade

Postby kurotsugi » 12 Sep 2017 00:21

I can't replicate the issue but we can always start with reinstalling lightdm. if that didn't work, gdm could be used as alternative.

JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Re: Lightdm doesn't run after upgrade

Postby JSladek » 13 Sep 2017 20:17

I am sorry to say that neither reinstall of lightdm nor installation of gdm resolved the problem. I have tried to do the upgrade for 8-9 far too many times and have now accepted the fact that it will probably never work. I have, of necessity, installed a new version of SolydK9 and work on the problem of applications that are no longer in the repository after I get up and running.

The problem, I don't believe, is with Solydxk - I could never get around the fact that the deb upgrade mechanism kept insisting on installing a version of Nvidia driver that will not work with my card. If I refused the installation of the driver, it would abort any further upgrade of the system. The only way I was able to get to the point I was at was to remove the current Nvidia drivers and support software - planning on then to install the available legacy driver in deb9. Of course, I was never able to get to that point.

I think that my transition to SolydK-8 a couple of years ago went smoothly because I was running whatever the equivalent was to the current EE version. Thus, when I did the upgrade to deb8, many files were already a more current version.

It seems now that going to EE version is the wiser move. This begs the question - since I already have a copy of SolydK-9 that I have been "toying with", can it be changed to EE by just changing to the testing repositories or is there more to it?

Thanks for your time on this issue and I am considering this issue "closed".

kurotsugi
Posts: 2121
Joined: 09 Jan 2014 00:17

Re: Lightdm doesn't run after upgrade {closed}

Postby kurotsugi » 15 Sep 2017 00:23

you can change the repo to testing then do

Code: Select all

sudo apt-get update
sudo aptitude -s dist-upgrade
it will simulate the upgrade process. if nothing broken you can continue with the real upgrade command (delete -s option from the command.

btw, before using the EE I'd suggest to try the live media. that way you'll know whether if things works or not.

JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Re: Lightdm doesn't run after upgrade {closed}

Postby JSladek » 15 Sep 2017 01:07

Thanks for the info. It'll be a while before I attempt it - I have to take a break from this for a while.

User avatar
grizzler
Posts: 2044
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Lightdm doesn't run after upgrade

Postby grizzler » 15 Sep 2017 11:24

JSladek wrote:This begs the question - since I already have a copy of SolydK-9 that I have been "toying with", can it be changed to EE by just changing to the testing repositories or is there more to it?
If you actually make that switch, you should also install solydkee-info. This is an empty package that acts as a flag for the system and system-adjustments packages. Without it, the sources.list file may get overwritten.
Frank

SolydX EE 64 - tracking Debian Testing

JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Re: Lightdm doesn't run after upgrade {closed}

Postby JSladek » 15 Sep 2017 14:15

Thanks, grizzler. Sorry, this is getting way off topic and I should be posting in testing. Last concern - I presume that it would not be a good idea to go right from my SolydK-8 stable to testing and that I should upgrade to -9 stable first or build from new.

User avatar
grizzler
Posts: 2044
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Lightdm doesn't run after upgrade {closed}

Postby grizzler » 15 Sep 2017 14:57

It's theoretically possible to go from SolydK-8 to SolydK-EE. At least it was when I ran the tests on my solydfixes script (which is in need of an upgrade, so don't try this now...). But that was several months ago and things are getting messy again (kdesudo has just been removed from testing...), so I wouldn't advise it.
Frank

SolydX EE 64 - tracking Debian Testing

JSladek
Posts: 133
Joined: 19 Jun 2014 23:15
Location: Suffolk VA

Re: Lightdm doesn't run after upgrade {closed}

Postby JSladek » 15 Sep 2017 15:57

Thanks. I'll go "Plan B" and put together -9 stable since my success rate at upgrading my 8-9 has been about zero and then go to EE after I get the system back to the way I like it.


Return to “KDE specific (SolydK)”

Who is online

Users browsing this forum: No registered users and 1 guest