Author Topic: Light DM issues  (Read 23491 times)

statmonkey

  • Posts: 330
    • View Profile
Light DM issues
« on: September 19, 2014, 02:35:40 AM »
I hadn't rebooted for a while ... oh lets say a couple of months :) and when I did lightdm seems to be failing google gives me some bug reports but no answers.  I can start x with no issues logging in and running startx but I see the same issues in my logs and running lightdm in test mode repeats the same error:

Quote
*** Error in `lightdm': double free or corruption (fasttop): 0x00007f6f371e8ab0

Has anyone else seen this or does anyone have a hint to a solution?

Thanks

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #1 on: September 19, 2014, 06:21:36 PM »
Aye.. Suffered through a power outage last night and when I turned the machine back on I am getting the same exact thing. I noticed an update to LightDM yesterday and I am sure this is the issue.  For the record, please explain how you are restarting X so that others may learn from this
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

orbea

  • Posts: 12
    • View Profile
Re: Light DM issues
« Reply #2 on: September 19, 2014, 08:25:16 PM »
Me too, I think it has something to do with systemd....
It booted fine yesterday before I updated, I'm pretty sure I saw both lightdm and systemd update...

Code: [Select]
$ systemctl status lightdm.service
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: failed (Result: start-limit) since Fri 2014-09-19 12:19:55 PDT; 14min ago
     Docs: man:lightdm(1)
  Process: 727 ExecStart=/usr/sbin/lightdm (code=killed, signal=ABRT)
  Process: 724 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 727 (code=killed, signal=ABRT)

Edit: As a workaround I installed xinit and added "exec startfluxbox" to my ~/.xinitrc.  It didn't autoload my .Xresources though...

PackRat

  • Posts: 1986
    • View Profile
Re: Light DM issues
« Reply #3 on: September 19, 2014, 10:24:40 PM »
Yes, both systemd and lightdm have had recent upgrade(s). I haven't had any issues with lightdm though.

@orbea add xrdb to your .xinitrc file. Something like -

Code: [Select]
xrdb -l ~/.Xresources &
that's pretty basic, and the default for xrdb, I think. Man page has a lot of other options.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

statmonkey

  • Posts: 330
    • View Profile
Re: Light DM issues
« Reply #4 on: September 19, 2014, 11:27:11 PM »
Aye.. Suffered through a power outage last night and when I turned the machine back on I am getting the same exact thing. I noticed an update to LightDM yesterday and I am sure this is the issue.  For the record, please explain how you are restarting X so that others may learn from this

Not really much to it.  When the system quit complaining about lightdm it gave me a login prompt.  Logged in as my user and ran startx.  Of course that caused other issues so it's not ideal.

I have done a little research and noticed that things for lightdm are completely different.  For example lightdm-set-defaults is completely gone and things have been moved around.  Of course I would suspect that lightdm which is horribly documented and is pretty much made for F_ubuntu is probably looking for some upstart conditions.  I am speculating here but ... grrr. Will look further.

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #5 on: September 19, 2014, 11:57:45 PM »
I appear to be completely lost... I am not able to even start startx

I booted to this partition which is the last Build partition before 3.16 (something I always do is change to the latest kernel on a totally new build partition)

Did a search and found no startx on this partition or on the new one (3.16) either

What am I missing?  (It has been a very very long trying day)

If this is the first bomb of systemd shutting out something as critical as the DM, then it sets a bit of panic down my spine...
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

orbea

  • Posts: 12
    • View Profile
Re: Light DM issues
« Reply #6 on: September 20, 2014, 12:18:51 AM »
Did you install the xinit package?  I was surprised when I noticed vsido didn'thave xinit by default which has startx.

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #7 on: September 20, 2014, 01:16:23 AM »
No and xinit is not necessary (nor is starx) to successfully boot to X..  and is not a part of VSIDO by design

I recall using startx in the past from another package though... it also seems to me that smxi also depends on startx .. I will research more and find it in the hallows of my fading memories
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #8 on: September 20, 2014, 01:34:18 AM »
To anyone interested these are all the packages updated since the release of the last ISO to now

Quote
The following NEW packages will be installed:
  libavdevice56 libavfilter5 libpostproc53 libswresample1 libswscale3
  libsystemd0
The following packages have been kept back:
  live-config-sysvinit
The following packages will be upgraded:
  acpi-fakekey acpi-support acpi-support-base apt apt-utils autotools-dev
  binutils bleachbit bluetooth bluez cmake cmake-data cpp-4.8 cpp-4.9 cups-bsd
  cups-client cups-common curl d-feet dbus dbus-x11 extlinux ffmpeg filezilla
  filezilla-common fonts-opensymbol g++-4.9 gcc-4.8 gcc-4.8-base gcc-4.9
  gcc-4.9-base gimp gimp-data gmusicbrowser grub-common grub-pc grub-pc-bin
  grub2 grub2-common gstreamer0.10-alsa gstreamer0.10-gconf
  gstreamer0.10-plugins-base gstreamer0.10-plugins-good
  gstreamer0.10-pulseaudio gstreamer0.10-x gstreamer1.0-plugins-base
  icedtea-7-jre-jamvm isolinux iucode-tool klibc-utils kmod lame
  libapt-inst1.5 libapt-pkg4.12 libasan0 libasan1 libatomic1 libav-tools
  libavcodec56 libavformat56 libavresample2 libavutil54
  libboost-date-time1.55.0 libboost-iostreams1.55.0 libboost-system1.55.0
  libc-bin libc-dev-bin libc6 libc6-dev libchromaprint-tools libchromaprint0
  libcilkrts5 libcups2 libcupsimage2 libcurl3 libcurl3-gnutls libdbus-1-3
  libemail-valid-perl libfm-data libfm-extra4 libfm-gtk-data libfm-gtk4
  libfm-modules libfm4 libfreetype6 libfreetype6-dev libgcc-4.8-dev
  libgcc-4.9-dev libgcc1 libgegl-0.2-0 libgfortran3 libgimp2.0 libgomp1
  libgpg-error0 libgstreamer-plugins-base0.10-0 libgstreamer-plugins-base1.0-0
  libgstreamer1.0-0 libgudev-1.0-0 libhyphen0 libio-socket-ip-perl libitm1
  libjs-sphinxdoc libklibc libkmod2 liblangtag-common liblangtag1
  liblightdm-gobject-1-0 liblircclient0 liblsan0 libltdl-dev libltdl7
  libmodule-build-perl libmp3lame0 libmpeg2-4 libncurses5 libncursesw5
  liborcus-0.8-0 libp11-kit0 libpam-systemd libparse-debianchangelog-perl
  libparted-fs-resize0 libparted2 libpython3.4 libpython3.4-minimal
  libpython3.4-stdlib libqtwebkit4 libquadmath0
  libreoffice-avmedia-backend-gstreamer libreoffice-base-core libreoffice-calc
  libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress
  libreoffice-java-common libreoffice-math libreoffice-style-galaxy
  libreoffice-writer librsvg2-2 librsvg2-common libsoup-gnome2.4-1
  libsoup2.4-1 libstdc++-4.9-dev libstdc++6 libsystemd-daemon0
  libsystemd-id128-0 libsystemd-journal0 libsystemd-login0 libtasn1-6
  libtinfo5 libtool-bin libtsan0 libubsan0 libudev1 libwayland-client0
  libwayland-cursor0 libwayland-server0 libwebrtc-audio-processing-0
  libxkbcommon0 libyaml-perl lightdm lintian linux-compiler-gcc-4.8-x86
  linux-libc-dev live-config live-config-doc live-tools locales lxmenu-data
  memtest86+ module-init-tools mtools multiarch-support ncurses-base
  ncurses-bin ncurses-term netcat-traditional openjdk-7-jdk openjdk-7-jre
  openjdk-7-jre-headless p11-kit p11-kit-modules parted python-debian
  python-lxml python-qt4 python-sip python-six python3-debian python3-six
  python3-uno python3.4 python3.4-minimal roxterm roxterm-common roxterm-gtk3
  smtube sudo syslinux syslinux-common systemd systemd-sysv task-english
  task-laptop tasksel tasksel-data udev uno-libs3 ure whois wpasupplicant
  xdg-user-dirs xserver-common xserver-xorg-core xserver-xorg-input-synaptics
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

orbea

  • Posts: 12
    • View Profile
Re: Light DM issues
« Reply #9 on: September 20, 2014, 01:47:17 AM »
No and xinit is not necessary (nor is starx) to successfully boot to X..  and is not a part of VSIDO by design

I recall using startx in the past from another package though... it also seems to me that smxi also depends on startx .. I will research more and find it in the hallows of my fading memories

Out of curiosity, what other ways are there to boot to X without xinit or a display manager?  I looked at packages.debian.org, but the only package I can find with startx is xinit, I'm wondering what you are recalling now too. :)

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #10 on: September 20, 2014, 01:49:00 AM »
LightDM is that DM and with it broken then so goes the boot

Still racking my brain but am more concerned with the fix to lightDM or systemd
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

statmonkey

  • Posts: 330
    • View Profile
Re: Light DM issues
« Reply #11 on: September 20, 2014, 02:28:40 AM »
I can't imagine that startx would be removed.  That is curious.  Just checked again and I have no issues using startx.  Still no idea what they have done to lightdm and why it is failing but clearly it's structure has changed.

Just an update.  If I run startx - get into an xsession and then run my lightdm default.sh as a user it runs with no errors and it seems I am in a lightdm session.  Soooooooooo I would speculate that during boot lightdm is calling for a file that isn't there and defaulting to failure.  More as it unfolds.

VastOne

  •      v-ger
  • Posts: 3964
    • View Profile
    • VSIDO Community
Re: Light DM issues
« Reply #12 on: September 20, 2014, 02:59:25 AM »
Xinit is not installed and therefor startx is also not a part of VSIDO... I have used startx in the past most likely trying to resolve nVidia issues.  Having gone to lightDM and pure nouveau as my drivers I do not miss xinit or startx

For clarity, I am on the build server partition now that had been my main build all through kernel 3.14 and 3.15.  It does not have xinit and startx either and until today it has not been used or useful

Log file of lightdm now on failed boot

/var/log/lightdm/lightdm.conf

Code: [Select]
[+0.03s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=818
[+0.03s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.03s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.03s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.12s] DEBUG: Registered seat module xlocal
[+0.12s] DEBUG: Registered seat module xremote
[+0.12s] DEBUG: Registered seat module unity
[+0.12s] DEBUG: Registered seat module surfaceflinger
[+0.84s] DEBUG: Adding default seat
[+0.84s] DEBUG: Seat: Starting
[+0.84s] DEBUG: Seat: Creating greeter session
[+0.94s] DEBUG: Seat: Creating display server of type x
[+0.94s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.94s] DEBUG: Using VT 7
[+0.94s] DEBUG: Seat: Starting local X display on VT 7
[+0.94s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.94s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.94s] DEBUG: DisplayServer x-0: Launching X Server
[+0.94s] DEBUG: Launching process 910: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.94s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.94s] WARNING: Could not enumerate user data directory /var/lib/lightdm-data: No such file or directory
[+0.94s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.94s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+2.96s] DEBUG: Got signal 10 from process 910
[+2.96s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+2.96s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+2.97s] DEBUG: Seat: Display server ready, starting session authentication
[+2.97s] DEBUG: Session pid=1173: Started with service 'lightdm-greeter', username 'lightdm'
[+3.13s] DEBUG: Session pid=1173: Authentication complete with return value 0: Success
[+3.13s] DEBUG: Seat: Session authenticated, running command
[+3.13s] DEBUG: Session pid=1173: Running command /usr/sbin/lightdm-gtk-greeter
[+3.13s] 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
[+3.13s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+3.13s] DEBUG: User vastone added
[+3.14s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+3.14s] WARNING: Could not create user data directory /var/lib/lightdm-data/lightdm: Error creating directory: No such file or directory
[+3.14s] DEBUG: Session pid=1173: Logging to /var/log/lightdm/x-0-greeter.log
[+3.40s] DEBUG: Activating VT 7
[+3.40s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c1
[+4.10s] DEBUG: Session pid=1173: Greeter connected version=1.10.1
[+5.53s] DEBUG: Session pid=1173: Greeter start authentication for vastone
[+5.53s] DEBUG: Session pid=1320: Started with service 'lightdm', username 'vastone'
[+5.57s] DEBUG: Session pid=1320: Got 1 message(s) from PAM
[+5.57s] DEBUG: Session pid=1173: Prompt greeter with 1 message(s)
[+9.61s] DEBUG: Session pid=1173: Continue authentication
[+9.64s] DEBUG: Session pid=1320: Authentication complete with return value 0: Success
[+9.64s] DEBUG: Session pid=1173: Authenticate result for user vastone: Success
[+9.64s] DEBUG: Session pid=1173: User vastone authorized
[+9.65s] DEBUG: Session pid=1173: Greeter sets language en_US.utf8
[+9.68s] DEBUG: Session pid=1173: Greeter requests session fluxbox
[+9.68s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+9.68s] DEBUG: Session pid=1173: Sending SIGTERM
[+9.70s] DEBUG: Session pid=1173: Greeter closed communication channel
[+9.70s] DEBUG: Session pid=1173: Exited with return value 0
[+9.70s] DEBUG: Seat: Session stopped
[+9.70s] DEBUG: Seat: Greeter stopped, running session
[+9.70s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+9.70s] DEBUG: Session pid=1320: Running command /etc/X11/Xsession /usr/bin/startfluxbox
[+9.70s] DEBUG: Creating shared data directory /var/lib/lightdm-data/vastone
[+9.70s] WARNING: Could not create user data directory /var/lib/lightdm-data/vastone: Error creating directory: No such file or directory
[+9.70s] DEBUG: Session pid=1320: Logging to .xsession-errors
[+9.92s] DEBUG: Activating VT 7
[+9.92s] DEBUG: Activating login1 session /org/freedesktop/login1/session/_31
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69555.78s] DEBUG: /etc/passwd changed, reloading user list
[+69555.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.78s] DEBUG: /etc/passwd changed, reloading user list
[+69556.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.78s] DEBUG: /etc/passwd changed, reloading user list
[+69556.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.78s] DEBUG: /etc/passwd changed, reloading user list
[+69556.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.78s] DEBUG: /etc/passwd changed, reloading user list
[+69556.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.78s] DEBUG: /etc/passwd changed, reloading user list
[+69556.78s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.79s] DEBUG: /etc/passwd changed, reloading user list
[+69556.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.79s] DEBUG: /etc/passwd changed, reloading user list
[+69556.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.79s] DEBUG: /etc/passwd changed, reloading user list
[+69556.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69556.79s] DEBUG: /etc/passwd changed, reloading user list
[+69556.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.79s] DEBUG: /etc/passwd changed, reloading user list
[+69557.79s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.80s] DEBUG: /etc/passwd changed, reloading user list
[+69557.80s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.80s] DEBUG: /etc/passwd changed, reloading user list
[+69557.80s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.80s] DEBUG: /etc/passwd changed, reloading user list
[+69557.80s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69557.80s] DEBUG: /etc/passwd changed, reloading user list
[+69557.80s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69558.81s] DEBUG: /etc/passwd changed, reloading user list
[+69558.81s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+69558.81s] DEBUG: /etc/passwd changed, reloading user list
[+69558.81s] DEBUG: Loading user config from /etc/lightdm/users.conf

Log file on a good working boot of lightdm (this machine I am on)

/var/log/lightdm/lightdm.conf
Code: [Select]
[+0.03s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=909
[+0.03s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.03s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.03s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.06s] DEBUG: Registered seat module xlocal
[+0.06s] DEBUG: Registered seat module xremote
[+0.06s] DEBUG: Registered seat module unity
[+0.06s] DEBUG: Registered seat module surfaceflinger
[+0.75s] DEBUG: Adding default seat
[+0.75s] DEBUG: Seat: Starting
[+0.75s] DEBUG: Seat: Creating greeter session
[+0.79s] DEBUG: Seat: Creating display server of type x
[+0.79s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
[+0.79s] DEBUG: Using VT 7
[+0.79s] DEBUG: Seat: Starting local X display on VT 7
[+0.79s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.79s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.79s] DEBUG: DisplayServer x-0: Launching X Server
[+0.79s] DEBUG: Launching process 1165: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.79s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.79s] WARNING: Could not enumerate user data directory /var/lib/lightdm-data: No such file or directory
[+0.79s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.79s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+2.37s] DEBUG: Got signal 10 from process 1165
[+2.37s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+2.37s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+2.37s] DEBUG: Seat: Display server ready, starting session authentication
[+2.37s] DEBUG: Session pid=1171: Started with service 'lightdm-greeter', username 'lightdm'
[+2.60s] DEBUG: Session pid=1171: Authentication complete with return value 0: Success
[+2.60s] DEBUG: Seat: Session authenticated, running command
[+2.60s] DEBUG: Session pid=1171: Running command /usr/sbin/lightdm-gtk-greeter
[+2.60s] 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
[+2.60s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+2.60s] DEBUG: User vastone added
[+2.63s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+2.63s] WARNING: Could not create user data directory /var/lib/lightdm-data/lightdm: Error creating directory: No such file or directory
[+2.63s] DEBUG: Session pid=1171: Logging to /var/log/lightdm/x-0-greeter.log
[+3.33s] DEBUG: Activating VT 7
[+3.33s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c1
[+4.75s] DEBUG: Session pid=1171: Greeter connected version=1.10.1
[+6.01s] DEBUG: Session pid=1171: Greeter start authentication for vastone
[+6.01s] DEBUG: Session pid=1280: Started with service 'lightdm', username 'vastone'
[+6.06s] DEBUG: Session pid=1280: Got 1 message(s) from PAM
[+6.06s] DEBUG: Session pid=1171: Prompt greeter with 1 message(s)
[+9.68s] DEBUG: Session pid=1171: Continue authentication
[+9.71s] DEBUG: Session pid=1280: Authentication complete with return value 0: Success
[+9.71s] DEBUG: Session pid=1171: Authenticate result for user vastone: Success
[+9.71s] DEBUG: Session pid=1171: User vastone authorized
[+9.72s] DEBUG: Session pid=1171: Greeter sets language en_US.utf8
[+9.78s] DEBUG: Session pid=1171: Greeter requests session fluxbox
[+9.78s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+9.78s] DEBUG: Session pid=1171: Sending SIGTERM
[+9.80s] DEBUG: Session pid=1171: Greeter closed communication channel
[+9.80s] DEBUG: Session pid=1171: Exited with return value 0
[+9.80s] DEBUG: Seat: Session stopped
[+9.80s] DEBUG: Seat: Greeter stopped, running session
[+9.80s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+9.80s] DEBUG: Session pid=1280: Running command /etc/X11/Xsession /usr/bin/startfluxbox
[+9.80s] DEBUG: Creating shared data directory /var/lib/lightdm-data/vastone
[+9.80s] WARNING: Could not create user data directory /var/lib/lightdm-data/vastone: Error creating directory: No such file or directory
[+9.80s] DEBUG: Session pid=1280: Logging to .xsession-errors
[+10.08s] DEBUG: Activating VT 7
[+10.08s] DEBUG: Activating login1 session /org/freedesktop/login1/session/_31
[+1694.25s] DEBUG: Process 1165 terminated with signal 6
[+1694.25s] DEBUG: DisplayServer x-0: X server stopped
[+1694.25s] DEBUG: Releasing VT 7
[+1694.25s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+1694.25s] DEBUG: Seat: Display server stopped
[+1694.25s] DEBUG: Seat: Stopping session
[+1694.25s] DEBUG: Session pid=1280: Sending SIGTERM
[+1694.25s] DEBUG: Seat: Active display server stopped, starting greeter
[+1694.25s] DEBUG: Seat: Creating greeter session
[+1694.25s] DEBUG: Seat: Creating display server of type x
[+1694.25s] DEBUG: Using VT 7
[+1694.25s] DEBUG: Seat: Starting local X display on VT 7
[+1694.25s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+1694.25s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+1694.25s] DEBUG: DisplayServer x-0: Launching X Server
[+1694.25s] DEBUG: Launching process 4482: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+1694.25s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+1694.30s] DEBUG: Session pid=1280: Exited with return value 15
[+1694.30s] DEBUG: Seat: Session stopped
[+1694.30s] DEBUG: Seat: Stopping display server, no sessions require it
[+1694.58s] DEBUG: Got signal 10 from process 4482
[+1694.58s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+1694.58s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+1694.59s] DEBUG: Seat: Display server ready, starting session authentication
[+1694.59s] DEBUG: Session pid=4494: Started with service 'lightdm-greeter', username 'lightdm'
[+1694.60s] DEBUG: Session pid=4494: Authentication complete with return value 0: Success
[+1694.60s] DEBUG: Seat: Session authenticated, running command
[+1694.60s] DEBUG: Session pid=4494: Running command /usr/sbin/lightdm-gtk-greeter
[+1694.60s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1694.60s] WARNING: Could not create user data directory /var/lib/lightdm-data/lightdm: Error creating directory: No such file or directory
[+1694.60s] DEBUG: Session pid=4494: Logging to /var/log/lightdm/x-0-greeter.log
[+1694.62s] DEBUG: Activating VT 7
[+1694.62s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c2
[+1694.70s] DEBUG: Session pid=4494: Greeter connected version=1.10.1
[+1695.03s] DEBUG: Session pid=4494: Greeter start authentication for vastone
[+1695.03s] DEBUG: Session pid=4523: Started with service 'lightdm', username 'vastone'
[+1695.04s] DEBUG: Session pid=4523: Got 1 message(s) from PAM
[+1695.04s] DEBUG: Session pid=4494: Prompt greeter with 1 message(s)
[+4905.37s] DEBUG: Session pid=4494: Continue authentication
[+4905.39s] DEBUG: Session pid=4523: Authentication complete with return value 0: Success
[+4905.39s] DEBUG: Session pid=4494: Authenticate result for user vastone: Success
[+4905.39s] DEBUG: Session pid=4494: User vastone authorized
[+4905.41s] DEBUG: Session pid=4494: Greeter sets language en_US.utf8
[+4905.45s] DEBUG: Session pid=4494: Greeter requests session fluxbox
[+4905.45s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session
[+4905.45s] DEBUG: Session pid=4494: Sending SIGTERM
[+4905.47s] DEBUG: Session pid=4494: Greeter closed communication channel
[+4905.47s] DEBUG: Session pid=4494: Exited with return value 0
[+4905.47s] DEBUG: Seat: Session stopped
[+4905.47s] DEBUG: Seat: Greeter stopped, running session
[+4905.47s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session1
[+4905.48s] DEBUG: Session pid=4523: Running command /etc/X11/Xsession /usr/bin/startfluxbox
[+4905.48s] DEBUG: Creating shared data directory /var/lib/lightdm-data/vastone
[+4905.48s] WARNING: Could not create user data directory /var/lib/lightdm-data/vastone: Error creating directory: No such file or directory
[+4905.48s] DEBUG: Session pid=4523: Logging to .xsession-errors
[+4905.50s] DEBUG: Activating VT 7
[+4905.50s] DEBUG: Activating login1 session /org/freedesktop/login1/session/_33

I am working now on changing the lightdm-gtk-greeter.conf around to see if that makes a difference
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

statmonkey

  • Posts: 330
    • View Profile
Re: Light DM issues
« Reply #13 on: September 20, 2014, 03:13:56 AM »
Not sure if it's related but my system is really lagging. In fact unusable typing this on my phone. I noticed in the service.lightdm file a comment about only using this structure until the dms catch up and that it is starting lightdm directly and ignoring all configuration files. That explains a lot. I also saw my logs filled with errors. I am pretty anal about keeping it clean so something has changed more than lightdm on my system at least.

I switched to xdm and got to a login screen with no issues.  System is still laggy for example can't use terminal at all.  I am not sure what is going on this may just be a sid issue but I have not seen any warnings on upgrade and don't see anything on googling. Hmm. Strange times.

jedi

  • DEFCON 1
  • Posts: 1556
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: Light DM issues
« Reply #14 on: September 20, 2014, 07:51:47 AM »
OK, since 15 minutes ago, (last post, which was right after a dist-upgrade), I've lost 'spacefm'  :'( from the menu or the terminal.  Due to IG's decision to go on hiatus, this is a bummer.  I really love spacefm!  Not the end of the world however.
I also am not having any of the issues you guys are having.  One thing of note;  I'm using the Liquorix Kernel 3.16-2.dmz.1-liquorix-amd64.
My lightDM screen definitely looks different, but works great.  No java related issues either.  (or icedtea)  The errors from terminal with spacefm are making me think GTK related...
I'll keep looking...
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous