You are not logged in.

#1 2017-02-24 01:02:46

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

[Resolved] Light Display Manager is hanging up the boot on my laptop

I'm installing Bunsen labs on an HP Probook 6540b laptop. I have posted on Linuxquestions.org and now I am cross posting here because the problem could possibly be a Bunsenlabs distribution problem. I'm really not sure. It looks like the problem could be with the Light Display Manager (LDM) configuration. Unfortunately, I know nothing about LDM and could use some help/advise on fixing the problem. In my following posts on this thread, I would post what has shown up on Linuxquestions.org so far.

One problem I have right now is that I don't see how to make an attachment here. I will work on that.

Jim Anderson

Last edited by jjanderson5 (2017-02-24 05:54:25)

Offline

#2 2017-02-24 01:06:49

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

This is my original post on linuxquestions.org

Hi,

I'm trying to fully install Bunsenlabs Hydrogen (a Debian derivative) on an HP Probook 6540b laptop. I have had to restart from the beginning a few times now. The procedure that I have gone through is:

- load the o/s from CDROM
- configure the laptop for the network
- apt-get update
- apt-get upgrade
- load distro s/w with apt-get
- load some extra software from tarballs, e.g. firefox, jdk

The first time, I loaded everything and on reboot, the laptop got hung up during boot. So, I started loading the software in chunks and reboot as I go along. On my 3rd iteration, I made it pretty far, but eventually, the system hung up on boot again.

I am thinking it is now time to try to figure out why it is hanging. The message that I am getting is:

[OK] Created slice user-108.slice.
[OK] Starting User Manager for UID 108...
[OK] Started User Manager for UID 108.

and then my cursor blinks forever.


I'm not sure of the best place to look for information, but I have attached a few logs. Are there other logs which may be more useful to look at?

The good news is that I can boot into the 'emergency mode' as root and get a good look at the system. I went to /var/log and I'm attaching the 'short_syslog.txt' file and the output of 'dmesg > dmesg.txt'. The file short_syslog.txt is the last 1000 lines of the 'syslog' file. I had to reduce the size to attach the file.

If you look at last 2 or 3 hundred lines of the 'short_syslog.txt', it looks like something has gone wrong, but I'm not sure what clues to take out of that information.

Jim Anderson

Offline

#3 2017-02-24 01:09:32

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

This is the first reply I got at linuxquestions.org.

Offline

#4 2017-02-24 01:11:10

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

This was my 2nd post to linuxquestions.org

@smallpond

I think you have isolated the right problem, i.e. something is fishy with the Light Display Manager. I took a look at the link you pointed to, but I was not able to make too much sense out of it.

I'm going to go to the Bunsenlabs forum and see if anyone know about configuring the LDM. When I look in /etc/lightdm directory is see that the lightdm.conf file is a symbolic link to the lightdm.conf.bunsen file. Hopefully, someone there knows something about configuring the LDM.

For now, I'm going to keep this open here at and hope someone who knows something about LDM can help me. I'm going to change the title of the thread too, I think.

Offline

#5 2017-02-24 03:09:45

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

Below is the last 300 lines of the syslog file.

It is interesting to do a search in this text for 'lightdm' and 'Light Display'.

Also note the warnings about 'org/freedesktop'...  I'm not sure why this would appear, but just recently I was subscribing to freedesktop.org and some it should up during the log process. In my mind, there is now way these reference should be showing up in a syslog. It looks suspicious.

Feb 23 10:33:54 valo NetworkManager[603]: <info> (33465056) ... get_connections.
Feb 23 10:33:54 valo NetworkManager[603]: <info> (33465056) ... get_connections (managed=false): return empty list.
Feb 23 10:33:54 valo NetworkManager[603]: <info> new connection /etc/NetworkManager/system-connections/Wired connection 1
Feb 23 10:33:54 valo NetworkManager[603]: <info> get unmanaged devices count: 0
Feb 23 10:33:54 valo NetworkManager[603]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb 23 10:33:54 valo NetworkManager[603]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb 23 10:33:54 valo NetworkManager[603]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:45:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Feb 23 10:33:54 valo NetworkManager[603]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/platform/hp-wmi/rfkill/rfkill1) (platform driver hp-wmi)
Feb 23 10:33:54 valo NetworkManager[603]: <info> WiFi hardware radio set enabled
Feb 23 10:33:54 valo NetworkManager[603]: <info> WWAN hardware radio set enabled
Feb 23 10:33:54 valo NetworkManager[603]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
Feb 23 10:33:54 valo NetworkManager[603]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
Feb 23 10:33:54 valo NetworkManager[603]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so
Feb 23 10:33:54 valo NetworkManager[603]: <info> Loaded device plugin: /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so
Feb 23 10:33:54 valo NetworkManager[603]: <info> WiFi enabled by radio killswitch; enabled by state file
Feb 23 10:33:54 valo NetworkManager[603]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb 23 10:33:54 valo NetworkManager[603]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb 23 10:33:54 valo NetworkManager[603]: <info> Networking is enabled by state file
Feb 23 10:33:54 valo NetworkManager[603]: <info> (lo): link connected
Feb 23 10:33:54 valo NetworkManager[603]: <info> (lo): carrier is ON
Feb 23 10:33:54 valo NetworkManager[603]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Feb 23 10:33:54 valo NetworkManager[603]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Feb 23 10:33:54 valo NetworkManager[603]: <info> (eth0): carrier is OFF
Feb 23 10:33:54 valo NetworkManager[603]: <info> (eth0): new Ethernet device (driver: 'sky2' ifindex: 2)
Feb 23 10:33:54 valo NetworkManager[603]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb 23 10:33:54 valo NetworkManager[603]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 23 10:33:54 valo systemd[1]: Started Network Manager.
Feb 23 10:33:54 valo NetworkManager[603]: <info> (eth0): preparing device
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): using nl80211 for WiFi device control
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/2
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 23 10:33:54 valo kernel: [   18.335186] sky2 0000:46:00.0 eth0: enabling interface
Feb 23 10:33:54 valo kernel: [   18.335301] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 23 10:33:54 valo kernel: [   18.336660] iwlwifi 0000:45:00.0: L1 Disabled - LTR Disabled
Feb 23 10:33:54 valo kernel: [   18.344194] iwlwifi 0000:45:00.0: Radio type=0x0-0x0-0x3
Feb 23 10:33:54 valo kernel: [   18.379742] iwlwifi 0000:45:00.0: L1 Disabled - LTR Disabled
Feb 23 10:33:54 valo kernel: [   18.387335] iwlwifi 0000:45:00.0: Radio type=0x0-0x0-0x3
Feb 23 10:33:54 valo kernel: [   18.426830] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): preparing device
Feb 23 10:33:54 valo NetworkManager[603]: <info> (wlan0): supplicant interface state: starting -> init
Feb 23 10:33:54 valo NetworkManager[603]: <info> ModemManager available in the bus
Feb 23 10:33:56 valo ModemManager[602]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:45:00.0': not supported by any plugin
Feb 23 10:33:56 valo ModemManager[602]: <warn>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:46:00.0': not supported by any plugin
Feb 23 10:33:56 valo lightdm[956]: ** (process:1036): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:33:56 valo systemd[1]: Starting user-108.slice.
Feb 23 10:33:56 valo systemd[1]: Created slice user-108.slice.
Feb 23 10:33:56 valo systemd[1]: Starting User Manager for UID 108...
Feb 23 10:33:56 valo systemd[1]: Starting Session c2 of user lightdm.
Feb 23 10:33:56 valo systemd[1]: Started Session c2 of user lightdm.
Feb 23 10:33:56 valo systemd[1039]: Starting Paths.
Feb 23 10:33:56 valo systemd[1039]: Reached target Paths.
Feb 23 10:33:56 valo systemd[1039]: Starting Timers.
Feb 23 10:33:56 valo systemd[1039]: Reached target Timers.
Feb 23 10:33:56 valo systemd[1039]: Starting Sockets.
Feb 23 10:33:56 valo systemd[1039]: Reached target Sockets.
Feb 23 10:33:56 valo systemd[1039]: Starting Basic System.
Feb 23 10:33:56 valo systemd[1039]: Reached target Basic System.
Feb 23 10:33:56 valo systemd[1039]: Starting Default.
Feb 23 10:33:56 valo systemd[1039]: Reached target Default.
Feb 23 10:33:56 valo systemd[1039]: Startup finished in 6ms.
Feb 23 10:33:56 valo systemd[1]: Started User Manager for UID 108.
Feb 23 10:33:56 valo kernel: [   20.353800] sky2 0000:46:00.0 eth0: Link is up at 100 Mbps, full duplex, flow control both
Feb 23 10:33:56 valo kernel: [   20.353856] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): link connected
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Feb 23 10:33:56 valo NetworkManager[603]: <info> Auto-activating connection 'home'.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) starting connection 'home'
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> NetworkManager state is now CONNECTING
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Feb 23 10:33:56 valo NetworkManager[603]: <warn> Could not send ARP for local address 192.168.0.236: Failed to execute child process "/usr/bin/arping" (No such file or directory)
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 23 10:33:56 valo NetworkManager[603]: <info> NetworkManager state is now CONNECTED_LOCAL
Feb 23 10:33:56 valo NetworkManager[603]: <info> NetworkManager state is now CONNECTED_GLOBAL
Feb 23 10:33:56 valo NetworkManager[603]: <info> Policy set 'home' (eth0) as default for IPv4 routing and DNS.
Feb 23 10:33:56 valo NetworkManager[603]: <info> Activation (eth0) successful, device activated.
Feb 23 10:33:56 valo NetworkManager[603]: <warn> (2) failed to call dispatcher scripts: (dbus-glib-error-quark:2) The name org.freedesktop.nm_dispatcher was not provided by any .service files
Feb 23 10:33:56 valo systemd[1]: Starting Session c3 of user rabbitmq.
Feb 23 10:33:56 valo systemd[1]: Started Session c3 of user rabbitmq.
Feb 23 10:33:58 valo NetworkManager[603]: <warn> Could not send ARP for local address 192.168.0.236: Failed to execute child process "/usr/bin/arping" (No such file or directory)
Feb 23 10:33:58 valo kernel: [   22.200005] lightdm-gtk-gre[1046]: segfault at 0 ip 00007f2c954bd69e sp 00007fffa56b28f0 error 4 in lightdm-gtk-greeter[7f2c954b3000+13000]
Feb 23 10:33:58 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:33:58 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:33:59 valo NetworkManager[603]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Feb 23 10:33:59 valo NetworkManager[603]: <info> Activation (eth0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Feb 23 10:33:59 valo NetworkManager[603]: <info> dhclient started with pid 1199
Feb 23 10:33:59 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:33:59 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:33:59 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:33:59 valo systemd[1]: Started Light Display Manager.
Feb 23 10:33:59 valo lightdm[1204]: ** (lightdm:1204): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:33:59 valo NetworkManager[603]: <info> (eth0): DHCPv6 state changed nbi -> preinit6
Feb 23 10:33:59 valo dhclient: XMT: Solicit on eth0, interval 1010ms.
Feb 23 10:33:59 valo lightdm[1204]: ** (process:1218): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:33:59 valo systemd[1]: Starting Session c4 of user lightdm.
Feb 23 10:33:59 valo systemd[1]: Started Session c4 of user lightdm.
Feb 23 10:33:59 valo kernel: [   23.618947] lightdm-gtk-gre[1221]: segfault at 0 ip 00007f030c86e69e sp 00007fff836745a0 error 4 in lightdm-gtk-greeter[7f030c864000+13000]
Feb 23 10:34:00 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:00 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:00 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:00 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:00 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:00 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:00 valo lightdm[1232]: ** (lightdm:1232): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:00 valo dhclient: XMT: Solicit on eth0, interval 2070ms.
Feb 23 10:34:00 valo lightdm[1232]: ** (process:1246): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:00 valo systemd[1]: Starting Session c5 of user lightdm.
Feb 23 10:34:00 valo systemd[1]: Started Session c5 of user lightdm.
Feb 23 10:34:00 valo kernel: [   24.682464] lightdm-gtk-gre[1249]: segfault at 0 ip 00007f81b9dea69e sp 00007fffa6611aa0 error 4 in lightdm-gtk-greeter[7f81b9de0000+13000]
Feb 23 10:34:01 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:01 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:01 valo ntpd[734]: Listen normally on 4 eth0 192.168.0.236 UDP 123
Feb 23 10:34:01 valo ntpd[734]: Listen normally on 5 eth0 fe80::725a:b6ff:feac:a841 UDP 123
Feb 23 10:34:01 valo ntpd[734]: peers refreshed
Feb 23 10:34:01 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:01 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:01 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:01 valo rabbitmq-server[609]: Starting message broker: rabbitmq-server.
Feb 23 10:34:01 valo systemd[1]: Started LSB: Enable AMQP service provided by RabbitMQ broker.
Feb 23 10:34:01 valo systemd[1]: Starting Multi-User System.
Feb 23 10:34:01 valo systemd[1]: Reached target Multi-User System.
Feb 23 10:34:01 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:01 valo systemd[1]: Starting Graphical Interface.
Feb 23 10:34:01 valo systemd[1]: Reached target Graphical Interface.
Feb 23 10:34:01 valo systemd[1]: Starting Update UTMP about System Runlevel Changes...
Feb 23 10:34:01 valo lightdm[1266]: ** (lightdm:1266): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:01 valo systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 23 10:34:01 valo systemd[1]: Startup finished in 4.298s (kernel) + 20.838s (userspace) = 25.137s.
Feb 23 10:34:01 valo lightdm[1266]: ** (process:1284): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:01 valo systemd[1]: Starting Session c6 of user lightdm.
Feb 23 10:34:01 valo systemd[1]: Started Session c6 of user lightdm.
Feb 23 10:34:02 valo kernel: [   25.724302] lightdm-gtk-gre[1287]: segfault at 0 ip 00007fd58304669e sp 00007ffe0b38f0e0 error 4 in lightdm-gtk-greeter[7fd58303c000+13000]
Feb 23 10:34:02 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:02 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:02 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
Feb 23 10:34:02 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
Feb 23 10:34:02 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
Feb 23 10:34:02 valo NetworkManager[603]: <warn> (3) failed to call dispatcher scripts: (dbus-glib-error-quark:2) The name org.freedesktop.nm_dispatcher was not provided by any .service files
Feb 23 10:34:02 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:02 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:02 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:02 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:02 valo lightdm[1299]: ** (lightdm:1299): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:02 valo dhclient: XMT: Solicit on eth0, interval 4130ms.
Feb 23 10:34:02 valo lightdm[1299]: ** (process:1312): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:02 valo systemd[1]: Starting Session c7 of user lightdm.
Feb 23 10:34:02 valo systemd[1]: Started Session c7 of user lightdm.
Feb 23 10:34:03 valo kernel: [   26.771205] lightdm-gtk-gre[1316]: segfault at 0 ip 00007fb1b7eeb69e sp 00007ffd45b8b960 error 4 in lightdm-gtk-greeter[7fb1b7ee1000+13000]
Feb 23 10:34:03 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:03 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:03 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:03 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:03 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:03 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:03 valo lightdm[1328]: ** (lightdm:1328): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:03 valo lightdm[1328]: ** (process:1341): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:03 valo systemd[1]: Starting Session c8 of user lightdm.
Feb 23 10:34:03 valo systemd[1]: Started Session c8 of user lightdm.
Feb 23 10:34:04 valo kernel: [   27.769775] lightdm-gtk-gre[1344]: segfault at 0 ip 00007f4d87d6369e sp 00007fff375e59e0 error 4 in lightdm-gtk-greeter[7f4d87d59000+13000]
Feb 23 10:34:04 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:04 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:04 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:04 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:04 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:04 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:04 valo lightdm[1356]: ** (lightdm:1356): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:04 valo lightdm[1356]: ** (process:1370): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:04 valo systemd[1]: Starting Session c9 of user lightdm.
Feb 23 10:34:04 valo systemd[1]: Started Session c9 of user lightdm.
Feb 23 10:34:05 valo kernel: [   28.808787] lightdm-gtk-gre[1373]: segfault at 0 ip 00007f867948369e sp 00007ffddab816c0 error 4 in lightdm-gtk-greeter[7f8679479000+13000]
Feb 23 10:34:05 valo ntpd[734]: Listen normally on 6 eth0 fd00:1cab:c076:b142:725a:b6ff:feac:a841 UDP 123
Feb 23 10:34:05 valo ntpd[734]: Listen normally on 7 eth0 fd00:1cab:c076:b142:8c17:620e:1d44:e8a0 UDP 123
Feb 23 10:34:05 valo ntpd[734]: peers refreshed
Feb 23 10:34:05 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:05 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:05 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:05 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:05 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:05 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:05 valo lightdm[1386]: ** (lightdm:1386): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:05 valo lightdm[1386]: ** (process:1399): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:05 valo systemd[1]: Starting Session c10 of user lightdm.
Feb 23 10:34:05 valo systemd[1]: Started Session c10 of user lightdm.
Feb 23 10:34:06 valo kernel: [   29.767471] lightdm-gtk-gre[1402]: segfault at 0 ip 00007f189974c69e sp 00007ffdec6ad170 error 4 in lightdm-gtk-greeter[7f1899742000+13000]
Feb 23 10:34:06 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:06 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:06 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:06 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:06 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:06 valo systemd[1]: Started Light Display Manager.
Feb 23 10:34:06 valo lightdm[1415]: ** (lightdm:1415): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:06 valo dhclient: XMT: Solicit on eth0, interval 8470ms.
Feb 23 10:34:06 valo lightdm[1415]: ** (process:1428): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 23 10:34:06 valo systemd[1]: Starting Session c11 of user lightdm.
Feb 23 10:34:06 valo systemd[1]: Started Session c11 of user lightdm.
Feb 23 10:34:07 valo kernel: [   30.802440] lightdm-gtk-gre[1431]: segfault at 0 ip 00007fb13c05969e sp 00007fff8630e5b0 error 4 in lightdm-gtk-greeter[7fb13c04f000+13000]
Feb 23 10:34:07 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:34:07 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:07 valo systemd[1]: lightdm.service holdoff time over, scheduling restart.
Feb 23 10:34:07 valo systemd[1]: Stopping Light Display Manager...
Feb 23 10:34:07 valo systemd[1]: Starting Light Display Manager...
Feb 23 10:34:07 valo systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
Feb 23 10:34:07 valo systemd[1]: Failed to start Light Display Manager.
Feb 23 10:34:07 valo systemd[1]: Unit lightdm.service entered failed state.
Feb 23 10:34:08 valo ntpd_intres[760]: DNS 0.debian.pool.ntp.org -> 108.61.73.244
Feb 23 10:34:10 valo systemd[1]: Stopping User Manager for UID 108...
Feb 23 10:34:10 valo systemd[1039]: Stopping Default.
Feb 23 10:34:10 valo systemd[1039]: Stopped target Default.
Feb 23 10:34:10 valo systemd[1039]: Stopping Basic System.
Feb 23 10:34:10 valo systemd[1039]: Stopped target Basic System.
Feb 23 10:34:10 valo systemd[1039]: Stopping Paths.
Feb 23 10:34:10 valo systemd[1039]: Stopped target Paths.
Feb 23 10:34:10 valo systemd[1039]: Stopping Timers.
Feb 23 10:34:10 valo systemd[1039]: Stopped target Timers.
Feb 23 10:34:10 valo systemd[1039]: Stopping Sockets.
Feb 23 10:34:10 valo systemd[1039]: Stopped target Sockets.
Feb 23 10:34:10 valo systemd[1039]: Starting Shutdown.
Feb 23 10:34:10 valo systemd[1039]: Reached target Shutdown.
Feb 23 10:34:10 valo systemd[1039]: Starting Exit the Session...
Feb 23 10:34:10 valo systemd[1039]: Received SIGRTMIN+24 from PID 1443 (kill).
Feb 23 10:34:10 valo systemd[1]: Stopped User Manager for UID 108.
Feb 23 10:34:10 valo systemd[1]: Stopping user-108.slice.
Feb 23 10:34:10 valo systemd[1]: Removed slice user-108.slice.
Feb 23 10:34:13 valo ntpd_intres[760]: DNS 1.debian.pool.ntp.org -> 204.9.54.119
Feb 23 10:34:13 valo ntpd_intres[760]: DNS 2.debian.pool.ntp.org -> 208.75.88.4
Feb 23 10:34:13 valo ntpd_intres[760]: DNS 3.debian.pool.ntp.org -> 216.218.254.202
Feb 23 10:34:15 valo dhclient: XMT: Solicit on eth0, interval 17140ms.
Feb 23 10:34:20 valo systemd[1]: Time has been changed
Feb 23 10:34:20 valo systemd[971]: Time has been changed
Feb 23 10:34:32 valo dhclient: XMT: Solicit on eth0, interval 34610ms.
Feb 23 10:34:44 valo NetworkManager[603]: <warn> (eth0): DHCPv6 request timed out.
Feb 23 10:34:44 valo NetworkManager[603]: <info> (eth0): canceled DHCP transaction, DHCP client pid 1199
Feb 23 10:34:44 valo NetworkManager[603]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Feb 23 10:34:44 valo NetworkManager[603]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Feb 23 10:34:44 valo NetworkManager[603]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Feb 23 10:34:45 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) scheduled...
Feb 23 10:34:45 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) started...
Feb 23 10:34:45 valo NetworkManager[603]: <info> Activation (eth0) Stage 5 of 5 (IPv6 Commit) complete.
Feb 23 10:48:52 valo systemd[1]: Starting Cleanup of Temporary Directories...
Feb 23 10:48:52 valo systemd[1]: Started Cleanup of Temporary Directories.
Feb 23 11:09:18 valo systemd[1]: Started Synchronise Hardware Clock to System Clock.
Feb 23 11:09:18 valo systemd[1]: Stopping Session c1 of user rabbitmq.
Feb 23 11:09:18 valo systemd[1]: Stopping Sound Card.
Feb 23 11:09:18 valo systemd[1]: Stopped target Sound Card.
Feb 23 11:09:18 valo systemd[1]: Stopping system-systemd\x2dfsck.slice.
Feb 23 11:09:18 valo systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Feb 23 11:09:18 valo systemd[1]: Stopping Remote File Systems (Pre).
Feb 23 11:09:18 valo systemd[1]: Stopped target Remote File Systems (Pre).
Feb 23 11:09:18 valo systemd[1]: Stopping User Manager for UID 112...
Feb 23 11:09:18 valo systemd[1]: Stopping Graphical Interface.
Feb 23 11:09:18 valo systemd[1]: Stopped target Graphical Interface.
Feb 23 11:09:18 valo systemd[1]: Stopping Multi-User System.
Feb 23 11:09:18 valo systemd[1]: Stopped target Multi-User System.
Feb 23 11:09:18 valo systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
Feb 23 11:09:18 valo systemd[1]: Stopping Regular background program processing daemon...
Feb 23 11:09:18 valo systemd[971]: Stopping Default.
Feb 23 11:09:18 valo systemd[971]: Stopped target Default.
Feb 23 11:09:18 valo systemd[971]: Stopping Basic System.
Feb 23 11:09:18 valo systemd[971]: Stopped target Basic System.
Feb 23 11:09:18 valo systemd[1]: Stopping Initialize hardware monitoring sensors...
Feb 23 11:09:18 valo systemd[971]: Stopping Paths.
Feb 23 11:09:18 valo systemd[1]: Stopped Initialize hardware monitoring sensors.
Feb 23 11:09:18 valo systemd[971]: Stopped target Paths.
Feb 23 11:09:18 valo systemd[1]: Stopping OpenBSD Secure Shell server...
Feb 23 11:09:18 valo systemd[971]: Stopping Timers.
Feb 23 11:09:18 valo kernel: [ 2142.388192] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 23 11:09:18 valo systemd[1]: Stopping Modem Manager...
Feb 23 11:09:18 valo systemd[971]: Stopped target Timers.
Feb 23 11:09:18 valo systemd[1]: Stopping Network Manager...
Feb 23 11:09:18 valo systemd[971]: Stopping Sockets.
Feb 23 11:09:18 valo systemd[1]: Stopping Deferred execution scheduler...
Feb 23 11:09:18 valo systemd[971]: Stopped target Sockets.
Feb 23 11:09:18 valo systemd[1]: Stopping Login Prompts.
Feb 23 11:09:18 valo systemd[971]: Starting Shutdown.
Feb 23 11:09:18 valo systemd[1]: Stopped target Login Prompts.
Feb 23 11:09:18 valo systemd[971]: Reached target Shutdown.
Feb 23 11:09:18 valo systemd[1]: Stopping Getty on tty1...
Feb 23 11:09:18 valo systemd[971]: Starting Exit the Session...
Feb 23 11:09:18 valo systemd[1]: Stopping LSB: set CPUFreq kernel parameters...
Feb 23 11:09:18 valo systemd[971]: Received SIGRTMIN+24 from PID 1892 (kill).
Feb 23 11:09:18 valo systemd[1]: Stopping LSB: disk temperature monitoring daemon...
Feb 23 11:09:18 valo systemd[1]: Stopping LSB: Enable AMQP service provided by RabbitMQ broker...
Feb 23 11:09:18 valo rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="742" x-info="http://www.rsyslog.com"] exiting on signal 15.

Last edited by damo (2017-02-24 07:21:40)

Offline

#6 2017-02-24 03:46:56

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

Well, I made a bit of progress. I went to https://wiki.ubuntu.com/LightDM and found the section "Help, I can't see my Desktop!". The first item there was to hit Alt-Ctrl-F1 to break out of the graphics mode of the display manager. I did that and sure enough, I went into text mode and was able to log in.

This tells me that my problem is definitely lies within the Light Display Manager. My guess is that there is a configuration problem, but I'm not sure what that is yet. Suggestions are welcome!!

Jim

Offline

#7 2017-02-24 04:19:00

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

I'm adding more information, that was take from the '/var/log/lightdm' directory

The file 'x-1.log' contains context information, not debug information.

X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux valo 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u1 (2017-02-22) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=b5f1e8a1-3eb8-4085-ad82-b5e1464a3830 ro initrd=/install/initrd.gz quiet
Build Date: 11 February 2015  12:32:02AM
xorg-server 2:1.16.4-1 ([url]http://www.debian.org/support[/url]) 
Current version of pixman: 0.32.6
	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Thu Feb 23 00:59:42 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) AIGLX: Suspending AIGLX clients for VT switch
(EE) Server terminated successfully (0). Closing log file.

The file 'x-1-greeter.log' shows that the Light Display Manager is failing.

(lightdm-gtk-greeter:2835): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(lightdm-gtk-greeter:2835): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(lightdm-gtk-greeter:2835): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

** (lightdm-gtk-greeter:2835): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files

The file 'lightdm.log' also shows that the Light Display Manager is failing. Unfortunately, I'm still not sure why.

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1440
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Registered seat module surfaceflinger
[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Seat: Starting
[+0.01s] DEBUG: Seat: Creating greeter session
[+0.01s] DEBUG: Seat: Creating display server of type x
[+0.01s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.02s] DEBUG: Launching process 1444: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.02s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.02s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.02s] DEBUG: User jja added
[+0.33s] DEBUG: Got signal 10 from process 1444
[+0.33s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+0.33s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+0.33s] DEBUG: Seat: Display server ready, starting session authentication
[+0.34s] DEBUG: Session pid=1454: Started with service 'lightdm-greeter', username 'lightdm'
[+0.36s] DEBUG: Session pid=1454: Authentication complete with return value 0: Success
[+0.36s] DEBUG: Seat: Session authenticated, running command
[+0.36s] DEBUG: Session pid=1454: Running command /usr/sbin/lightdm-gtk-greeter
[+0.36s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+0.36s] DEBUG: Session pid=1454: Logging to /var/log/lightdm/x-0-greeter.log
[+0.37s] DEBUG: Activating VT 7
[+0.37s] DEBUG: Activating login1 session c12
[+0.44s] DEBUG: Session pid=1454: Greeter connected version=1.10.3
[+0.55s] DEBUG: Session pid=1454: Greeter closed communication channel
[+0.55s] DEBUG: Session pid=1454: Exited with return value 11
[+0.55s] DEBUG: Seat: Session stopped
[+0.55s] DEBUG: Seat: Stopping; failed to start a greeter
[+0.55s] DEBUG: Seat: Stopping
[+0.55s] DEBUG: Seat: Stopping display server
[+0.55s] DEBUG: Sending signal 15 to process 1444
[+0.72s] DEBUG: Process 1444 exited with return value 0
[+0.72s] DEBUG: DisplayServer x-0: X server stopped
[+0.72s] DEBUG: Releasing VT 7
[+0.72s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+0.72s] DEBUG: Seat: Display server stopped
[+0.72s] DEBUG: Seat: Stopped
[+0.72s] DEBUG: Required seat has stopped
[+0.72s] DEBUG: Stopping display manager
[+0.72s] DEBUG: Display manager stopped
[+0.72s] DEBUG: Stopping daemon
[+0.73s] DEBUG: Exiting with return value 1

Last edited by damo (2017-02-24 07:22:38)

Offline

#8 2017-02-24 05:53:43

jjanderson5
Member
Registered: 2016-05-10
Posts: 94

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

Well, I did not solve the Light Display Manager problem, but I do have a work around. I found the following web page: [link]http://www.makeuseof.com/tag/choose-swi … -managers/[/link] and decide to install and use a different display manager.

I rebooted my laptop and when it hung, I hit Alt-Ctrl-F1, which stop LDM and dropped me into text mode. I logged in.


Using 'apt-cache search display', I found 'xdm'. So I ran 'apt-get install xdm' and it not only installed it but it pop-ed up a window that let me set xdm as the default DM. I rebooted and it worked.

So that laptop is working now.

The bad new is that I have another laptop with the identical problem with LDM. On this laptop, hitting Alt-Ctrl-F1 does not break the display manager and put me into text mode. I will have to address that problem on a different day.

Jim A.

Offline

#9 2017-02-24 07:35:50

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

jjanderson5 wrote:
Feb 23 10:34:00 valo kernel: [   24.682464] lightdm-gtk-gre[1249]: segfault at 0 ip 00007f81b9dea69e sp 00007fffa6611aa0 error 4 in lightdm-gtk-greeter[7f81b9de0000+13000]
Feb 23 10:34:01 valo systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE

That should not happen hmm

I think that perhaps your installation is corrupted, have you tried a memory test & a SMART check?


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#10 2017-02-24 07:38:25

damo
....moderator....
Registered: 2015-08-20
Posts: 6,351

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

Did Bunsenlabs run OK from a Live session, before you "installed" it?

- load the o/s from CDROM
- configure the laptop for the network
- apt-get update
- apt-get upgrade
- load distro s/w with apt-get
- load some extra software from tarballs, e.g. firefox, jdk

The above steps should have happened either automatically or during the bl-welcome script. apt-get should not have been needed to install the distro software - it is included in the iso (firefox as well). Java is an install option in the welcome script.

It seems that whatever you during the install process may have messed up the lightdm configuration. The welcome script can be run any time with the command 'bl-welcome' ( - and note the warning about installing from non-Debian Stable sources!)

NB Please use [ code ] tags when posting terminal output - it makes it much easier to read and scroll through wink I have edited your posts with the appropriate tags. As you have noticed, this forum doesn't allow attachments.


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#11 2017-02-24 10:56:34

hhh
Meep!
Registered: 2015-09-17
Posts: 10,618
Website

Re: [Resolved] Light Display Manager is hanging up the boot on my laptop

@Jim, thanks for registering and welcome!

As damo said, the first step is to transfer one of our DVD/USB ISO images and run a Live session. Instructions for that are here...
https://www.bunsenlabs.org/installation … ey-install

If it boots, you'll see the BunsenLabs desktop and can test your Internet connection, mouse, keyboard, etc...

If all is well, reboot and install using these instructions...
https://forums.bunsenlabs.org/viewtopic.php?id=518

Post back and let us know how it went. Make note of any error messages you see. Thanks!

Offline

Board footer

Powered by FluxBB