VSIDO Community

VSIDO Support => General Support => Topic started by: statmonkey on September 19, 2014, 02:35:40 AM

Title: Light DM issues
Post by: statmonkey 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
Title: Re: Light DM issues
Post by: VastOne 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
Title: Re: Light DM issues
Post by: orbea 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...
Title: Re: Light DM issues
Post by: PackRat 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.
Title: Re: Light DM issues
Post by: statmonkey 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.
Title: Re: Light DM issues
Post by: VastOne 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...
Title: Re: Light DM issues
Post by: orbea 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.
Title: Re: Light DM issues
Post by: VastOne 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
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 01:34:18 AM
To anyone interested these are all the packages updated since the release of the last ISO (http://vsido.org/blog/?p=206) 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
Title: Re: Light DM issues
Post by: orbea 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 (https://packages.debian.org/search?suite=sid&section=all&arch=any&searchon=all&keywords=startx), I'm wondering what you are recalling now too. :)
Title: Re: Light DM issues
Post by: VastOne 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
Title: Re: Light DM issues
Post by: statmonkey 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.
Title: Re: Light DM issues
Post by: VastOne 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
Title: Re: Light DM issues
Post by: statmonkey 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.
Title: Re: Light DM issues
Post by: jedi 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...
Title: Re: Light DM issues
Post by: jedi on September 20, 2014, 08:14:22 AM
Another reboot, no problems...
The error from terminal on trying to start spacefm;
Code: [Select]
Attempt to unlock mutex that was not lockedMaybe SID is just in a bad mood and breaking some of his toys.  Perhaps he'll calm down in a couple of days...
Title: Re: Light DM issues
Post by: statmonkey on September 20, 2014, 02:02:54 PM
Thanks for weighing in Jedi.  Can I ask if when you did your lightdm upgrade did you keep your old config files or did you install the maintainer's version?

There must be something different between our builds. 

Really hoping this is just Sid playing naughty.  I really have a ton of stuff to do today.  Not sure I could accept loss of spacefm and this keyboard lag, doubling of keypress, lack of ability to use terminal in x is really painful.
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 02:18:17 PM
I am in a bad way, I seem to have lost all access to my home directory which is it on its own partition, no matter what partition I try to log into I have no access to home.  The login attempt just flashes back to the login name again. I have tried to change ownership of my own home directory to no avail, because this isn't exactly what it looks like when you don't have permissions to your home directory.

I'm now in the process of installing on a different partition all over again.  If I was on a Windows machine seeing these same things I would swear  I was dealing with a virus. Will keep you updated on what's going on.
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 02:21:57 PM
I should add that none of this was going on until I started mucking around with this LightDM and systemd issue that's been plaguing us
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 02:53:29 PM
Further info on just what I did... I downloaded the deb for the old version of LightDM 1.10.1-3 and installed it on the broken partition ... it was as statmonkey said, puking on several systemd messages that lightdm was no good and then getting to a login prompt at tty1

I dpkg -i the old lightdm version and was happy when I rebooted and found the issue resolved.. or so it seemed... I had a login screen but it did not show my login name which is (was?) the default in the VSIDO version of the lightdm conf file setup... blah blah blah and yada yada yada... get on with it!

Tried to login there with my creds and it just flashes right back to the login screen... ok, I can deal with that.. Reboot back to the partition of the old build (which shares the same /home vastone home directory) and am getting the exact same results... it will not login, it just spits me back out to the login screen and any login I use with that /home directory does the same thing

I am now on a new build partition that I disabled using that specific /home partition and instead using it's own partition as the new /home.  It boots and logs in fine... but as soon as I change fstab to reflect the old /home/vastone partition it does the same exact thing on the login again.  I have checked all uuid's and nothing has changed in fstab

I am testing now copying the old home to the new home on that I am on now and doing a chown on it.. will update again when I reboot
Title: Re: Light DM issues
Post by: statmonkey on September 20, 2014, 02:55:29 PM
Fixed lightdm sort of from this tip:

Quote


Joined: 2010-08-26
Posts: 736

Status: Offline
   
It seems you've picked the 'wrong' choice when lightdm asked via debconf about how it should deal with "/etc/lightdm/lightdm.conf" during the dist-upgrade. The 'correct' answer would have been 'Y'es, to allow replacing the current version of /etc/lightdm/lightdm.conf with the new template from the maintainer.

By uninstalling lightdm and purging it.  I then reinstalled and rebooted.  Lightdm now works but not the way I had it configured.  I will have to research what it is now doing.  This is a pretty crappily documented app so ...... may take me a while.

Spacefm is sadly not working as reported by Jedi.  I will move to that next.  I am convinced that in order to work with systemd these and a lot of other apps are going to continue to be repackaged to make use of it Or they will be just broken and left to die.  See the paragraph in my rant about this.  I am guessing those of us who have customized things like lightdm are going to suffer some breakage because of it.  I have a long list of crap on my machine that is not working correctly as well and will report back on what I find that works.  Looks like a long day.

Sorry to hear your issues VO.  Mine are weirder still since I have characters diasappearing, keyboard skip and partitions that won't mount as well.  If you have downgraded lightdm then upgrading and making the proper Y selection to choose the maintainers version should fix it.  Then you will probably have to customize it all over again from the /etc/lightdm/lightdm.conf file to get back to what you actually want.

Guess I will just keep adding to this.  Apparently something has decided that my drives are uefi and the system keeps trying to load them that way.  This is causing the drives not to be found and not sure if this is from systemd, grub or where yet, it might be related to the spaceFM issues.  Additionally I am running into keyboard issues, mpd problems and numerous other issues.  It looks like a reinstall is in my future.  But my frustration is mounting.
Title: Re: Light DM issues
Post by: jedi on September 20, 2014, 06:27:05 PM
Yes, I chose the maintainers version.  With lightDM and Grub, I usually do.  (choose the maintainers version)  I like to see if something is going to break!  I am also deeply disappointed with the issue of spacefm.  I switched last night back to pcmanfm, but it ain't then same!
I have no other issues, and, as amof have gone through all of my installed apps to make sure of this.  So far for me, only spacefm is being naughty.
By using the Liquorix Kernel, have I avoided the issues you all are having?

For orbea's benefit, when doing a dist-upgrade, live-config-sysvinit has been being held back for quite a while now.  (several weeks at least?)

@statmonkey, doing a dist-upgrade right now shows an update to "keyboard-configuration".  Not sure if that'll help with your issues...
Title: Re: Light DM issues
Post by: jedi on September 20, 2014, 06:28:30 PM
I am going to reboot again and verify I'm not having troubles...
Title: Re: Light DM issues
Post by: jedi on September 20, 2014, 07:30:14 PM
Having rebooted, and then also powered off, I can safely say that on my system I'm not seeing the issues you all are.  Spacefm continues to not work, and also the Disk-Manager tool.  As I can edit the fstab directly, the Disk-Manager utility is not worrisome to me.  Spacefm however, I am most upset about as I use it a lot and truly like it's interface and function.

Sorry for the in and out, I've been sick for the past 2 weeks with a lung infection.  I am sleeping a lot but will check back in every few hours...
Title: Re: Light DM issues
Post by: statmonkey on September 20, 2014, 07:55:28 PM
Jedi, sorry you are not feeling well but what a trooper still trying to help :)  I will do an up again and see if the keyboard things go away.  I would guess most of this will settle in the next day or two.  I really do a lot of custom stuff to my system so it will be a painful return to normalcy for me.  Oh well. Get better soon and thanks for the info.
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 08:04:31 PM
Had to go on a long bike ride in the poring rain (https://plus.google.com/111544088375719961586/posts/97BsX9V529F) to ease my brain

There are several issues and I want to address them and try to use this thread (or another one) as a catch all for them

This bug seems to validated everything about the "Attempt to unlock mutex that was not locked' that is  killing both spacefm and disk-manager (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758619).
It may be possible to regress to the previous pygtk version and resolve it... I am not sure. I do believe that disk-manager is still maintained and it should be fixed.  I do not think IG will fix it for spaceFM but he may surprise us.  Right now I am using Thunar instead and like Jedi said, it just ain't the same...

With the rain pounding my head and wind freezing my gonads, I was able to think a bit...

My issue with a separate /home partition is most troubling.  All I did on that partition was do a dpkg -i install of the old version of lightdm.  Why would that freeze out that partition to all  VSIDO installs that share it? The drive is being mounted via fstab and I can access it from tty1 as me and delete/add files to it so it is not a permission issue.  I copied over that entire partition to a new install as /home/vastone (on a shared partition with /) and cannot boot to it there either. So it appears to be a config setting specific to that /home in .config somewhere

So to be clear I am on a new install of VSIDO, with home on the same partition as / and updated to today ... I chose the package maintainer version (the first time I have done that since creating VSIDO) and I have a vanilla login screen but can access it. Both spacefm and disk-manager are broken

Nice going jedi being sick and coming here to infect us all... I blame you!

Not sure what else I can add... once I access the log files for lightdm on that failed VSIDO build I will post the results but neither lightdm or systemd are giving me much info that I can relate to
Title: Re: Light DM issues
Post by: orbea on September 20, 2014, 09:49:23 PM
I just want to add that I'm getting "Attempt to unlock mutex that was not locked" for disk-manager too, but spacefm still seems to be working as expected...
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 11:07:56 PM
^ That is interesting... and definitely adds to this mystery

One thing I have noticed too in all these changes is that even though I do not have any power management enabled I come back to my computer and it is at a dark screen that leads to a login screen  .. my up time shows everything as normal, but every single app I had open prior to this is closed and gone
Title: Re: Light DM issues
Post by: statmonkey on September 20, 2014, 11:11:36 PM
Confirming this.  A bit confused about why spaceFM is still working for some.  Curious
Title: Re: Light DM issues
Post by: VastOne on September 20, 2014, 11:18:39 PM
One thing I am seeing regarding my separate /home partition is that it appears that that directory is not mounting in the login process and a 'new' home directory is being copied over from /etc/skel to the local directory

Of course /etc/fstab still has home labeled and mounted from the original separate /home partition and that is where the confusion begins
Title: Re: Light DM issues
Post by: jedi on September 20, 2014, 11:31:07 PM
on the spacefm issue, upon a reboot, when i try to open it, it will flash on the screen for a second then disappear.  That it is working for orbea is very confusing to me.

@orbea, are you on the latest version of the VSIDO ISO's?  Are you using Debian's Kernel?  As I mentioned in an earlier post, I'm using the Liquorix Kernel myself.  Also, what version of spacefm are you using?  Thanks...
Title: Re: Light DM issues
Post by: orbea on September 20, 2014, 11:50:36 PM
I installed recently with the Aug 21 iso, I haven't changed the kernel or spacefm from the defaults, the only thing I can think that I'm doing differently is running spacefm in daemon mode, maybe I just need to reboot to break it...
Title: Re: Light DM issues
Post by: statmonkey on September 21, 2014, 01:02:27 AM
Have you looked at your /etc/lightdm/lightdm.conf to see what is really being called?  I doubt anything.  I would also look at what systemd is calling on boot. 

I monkeyed with this til very late last night and had some similar issues with drives/boot.  Unfortunately by the time I got it figured out I was so tired and so confused that I can't really remember what I found out or how I did it.  I do know that I think it is unacceptable to make structural changes to things like login/dev calls etc. and not offer any documentation or warnings other than the "maintainer" version question.  I rarely or never accept maintainer versions and this is the first time I ever remember that a program just inexplicably changed what it called, how it called it and where it called it from without warning.  Lightdm was calling the greeter and lightdm.conf from the /usr folder structure which in turn could be used to call things from your structure as you saw fit.  I can't seem to plug anything into the /etc/lightdm/lightdm.conf to get the same results nor is the file documented as to what changed or why nor is there any info online about it from what I can find.  Frustrating to put it mildly.  I know this is the way it is, go with the flow, take your medicine like a man and all that rot.
Title: Re: Light DM issues
Post by: PackRat on September 21, 2014, 01:26:39 AM
@vastone - regarding your /home partition not mounting at boot, any other time I've seen that issue, it has always been related to a problem with gvfs and/or udev (the two work together don't they?).

Edit - another update of lightdm today (21 Sept). I have yet to experience any issues with lightdm. However, inxi is no longer working - appears some directories and some binaries have been replaced:

(http://en.zimagez.com/miniature/september14113158351366x768.jpg) (http://en.zimagez.com/zimage/september14113158351366x768.php)

@vastone - curious that /dev/disk/by-label is a missing directory. All my partitions are mounting though.

Edit #2

Mirage is also giving the error -

Code: [Select]
Attempt to unlock mutex that was not locked
ristretto works though.
Title: Re: Light DM issues
Post by: orbea on September 21, 2014, 04:29:47 PM
maybe I just need to reboot to break it...

Yep...  :'(
Title: Re: Light DM issues
Post by: statmonkey on September 21, 2014, 05:17:57 PM
I think PackRat as per usual is right on with this.  I am facing a re-install at the least but am not comfortable with where things are, it makes little sense to me to reinstall and duplicate the issues I have (plus more) with a new system.  I am in hopes I can struggle along until things settle down.  Among my issues the biggest is that my 4 disk external drive is crashing my system on any attempt to use it.  Hard resets are courting disaster and I am looking at two or three a day.  Adding to that my system is doggy on both boot up and operation along with many of my environment settings/customizations being broken.  Reading this I was reminded of something I saw over in the Aptosid forums some time ago, to wit:
Quote
In most cases the migration from sysvinit-core to systemd-sysv is supposed to be smooth and transparent, basically with the only visible effect being there less verbose startup messages (by default). Systemd is stricter when it comes to invalid fstab entries (like long forgotten swap partitions, but also other (syntax) errors are punished by systemd; sysvinit often managing to boot regardless of those is the real error here). Likewise systemd doesn't like dependency loops in system dæmons, this affects a handful of (broken) services (e.g. setserial), which declare conflicting service dependencies and might affect booting.
I could be suffering from all or none of these.  Unfortunately a less verbose messaging system means exactly that, it's less verbose which in turn means you are often depending on in app documentation, etc. to decipher where the problems are.  I feel a little like I brought a knife to a gun fight.

Anyway, the whole udev/gvfs handling has changed and the stricter fstab handling as well means that I am at a bit of a loss. I really need to understand exactly how the system is initializing drives at this point. 

[orbea] sorry you have joined us in losing spaceFM (which for me at least meant handling external drives with ease).  I am seeing a lot of things that are broken but can't look into them at present my priority has to be getting my external drive/sandbox/testing/backup environment back. 

My apologies if this seems like random blathering.  I have gone from light-hearted teasing on this to actually becoming concerned.  I am not seeing a lot on the web on this so I am guessing this must be about my customizations and personal needs, so I guess there is that :)
Title: Re: Light DM issues
Post by: VastOne on September 21, 2014, 07:22:06 PM
This is all over the place (Attempt to unlock mutex that was not locked) all these links just in the last month

http://forums.linuxmint.com/viewtopic.php?f=47&t=178152 (http://forums.linuxmint.com/viewtopic.php?f=47&t=178152)

https://code.google.com/p/gtkdialog/issues/detail?id=77 (https://code.google.com/p/gtkdialog/issues/detail?id=77)

https://bugzilla.redhat.com/show_bug.cgi?id=1138146 (https://bugzilla.redhat.com/show_bug.cgi?id=1138146)

http://ubuntuforums.org/showthread.php?t=2244969 (http://ubuntuforums.org/showthread.php?t=2244969)

http://murga-linux.com/puppy/viewtopic.php?t=95556&sid=e3a5e91a505b42d2feef7c31005f67a7 (http://murga-linux.com/puppy/viewtopic.php?t=95556&sid=e3a5e91a505b42d2feef7c31005f67a7)

I feel for you statmonkey and know you are in a bad way... We have lived on this edge for quite some time with little or no issues and now they arrive in bunches

I still cannot access my old home partition on a boot with it as defined as my home in fstab

The only time I have ever seen this was when I did not have the correct access rights to the data.  The fix was always chown -R vastone:vastone /home/vastone as root .... the behavior is exactly the same as this issue, the fix does not work

Title: Re: Light DM issues
Post by: VastOne on September 21, 2014, 07:59:54 PM
For anyone using pcmanfm or thunar and get a not authorized to perform operation when trying to mount a device

edit / create

Code: [Select]
/etc/polkit-1/localauthority/50-local.d/50-filesystem-mount-system-internal.pkla
with this
Code: [Select]
[Mount a system-internal device]
Identity=*
Action=org.freedesktop.udisks2.*
ResultActive=yes

It will resolve all mounting problems as long as udisks2 and gvfs are installed (both are by default in VSIDO)

Not as secure or as elegant as spaceFM but a fix for now
Title: Re: Light DM issues
Post by: VastOne on September 21, 2014, 08:12:22 PM
The tiniest and simplest things can bring down a giant...

The reason I was not able to boot into my /home/vastone directory had NOTHING to do with the directory .. it was the new lightdm login session that does not use a default config anymore... I did not have fluxbox selected in the settings on the top right menu items and it was trying to launch a default session that was not there

I do not know what to be pissed more about, the fact I missed something so FECKING basic or that lightdm is too FECKING stupid to understand fluxbox is the DM

Damn it all
Title: Re: Light DM issues
Post by: statmonkey on September 21, 2014, 08:28:35 PM
Really glad you got it sorted and many thanks for the policy kit hint.  The situation on the apps that don't work now is a different story and the idea that such a radical change in how an app functions comes through with no documentation/warning is still a biggie for me.  This is not what I have come to expect from Debian as I ranted earlier.
Title: Re: Light DM issues
Post by: ozitraveller on September 22, 2014, 12:19:34 AM
I stupidly accepted the maintainers config to be installed too. And then had to use startx to start the de.

I added back all the settings I used in lightdm.conf and rebooted to discover I couldn't login. :( :( I used systemrescuecd to edit lightdm.conf and comments out the lines I had just changed, and rebooted. Login now worked!

My original : lightdm.conf
Code: [Select]
[SeatDefaults]
#xserver-command=X
#xserver-layout=
#xserver-config=
xserver-allow-tcp=false <--- now commented out
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
greeter-session=lightdm-greeter <--- now commented out
greeter-hide-users=false  <--- this still works, displays users dropdown
#greeter-allow-guest=true
#greeter-show-manual-login=false
user-session=xfce  <--- now commented  out
#allow-guest=true
#guest-session=UNIMPLEMENTED
session-wrapper=/etc/X11/Xsession  <--- now commented out
#display-setup-script=
#greeter-setup-script=
session-setup-script=/usr/share/star/star-user-setup  <--- now commented out
#session-cleanup-script=
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-session=UNIMPLEMENTED
#exit-on-failure=false

Anything that is associated with session causes a lock out.

Only uncommented setting line
Code: [Select]
greeter-hide-users=false

I don't have any problems mounting or unmounting.

https://tracker.debian.org/pkg/lightdm (https://tracker.debian.org/pkg/lightdm)
Title: Re: Light DM issues
Post by: statmonkey on September 22, 2014, 12:29:19 AM
So my testing of this has shown me that any customization that I was doing in the lightdm.conf causes it to fail.  I was using lightdm to call and configure my arandr, etc. and attempts to do this in the new setup fail.  I haven't tested calling it as a separate script yet but do know that if I wait until the system settles after login and then run my old default.sh (the script I was calling within lightdm before) it does actually successfully set up my environment.  I am sure that there is some work around just wish there would have been some warning/documentation that would have provided some guidance here.  I am finding several things that are still borked but not ready to comment until I uncover more of the root of the issues.
Title: Re: Light DM issues
Post by: jedi on September 22, 2014, 01:06:50 AM
I have found I can logout, but am unable to 'reboot' or 'shutdown'.  This is ridiculous!  VastOne, glad you got your /home back...

If I try to 'reboot' or 'shutdown', I am sent to a blank screen where it just hangs.  I let it set that way for quite a few minutes to no avail.  I end up having to do a hard reset to do either.  This can only lead to disaster at some point...

Same results from the menu or tty.

Also what happened to "uptime"?  "The following applications are missing from your system: uptime" this comes from running "inxi --recommends".  It says to add it to my system I need to install the proper distribution package for my system: Debian: procps
procps is already the newest version

And yet, Conky displays the uptime just fine...

Like I said, ridiculous...
Title: Re: Light DM issues
Post by: VastOne on September 22, 2014, 01:42:37 AM
^ That seems to be related to you or just your system?

I cannot reproduce any of these behaviors

Title: Re: Light DM issues
Post by: jedi on September 22, 2014, 03:14:52 AM
Yes, like statmonkey, over the years I've "customized" too many things to remember.  The beauty of VSIDO, there is NO NEED to remember!  I reinstall, copy /home back and voilà!  So, yes, it is just my system...
Title: Re: Light DM issues
Post by: statmonkey on September 22, 2014, 03:52:12 AM
Jedi, I am finding that the only way to get through this is to hunt and peck each one, picking them off one at a time and hoping like heck that I remember what I did and when. LOL.  Anyway, on the reboot and shutdown that sounds like a policy kit issue as  I think that has changed recently.  Sorry you are having issues if there is something specific that I can help with post it or PM me anytime.   
Title: Re: Light DM issues
Post by: jedi on September 23, 2014, 12:25:22 AM
Shutdown, reboot issues fixed.  Removed Samba.  Presto, back to normal.  As to the topic of this thread, I say;
sudo apt-get purge lightdm lightdm-gtk-greeter liblightdm-gobject-1-0

Good riddance to bad rubbish!

Just kidding, lightdm has been pretty faithful for the most part for over 2 years now.  The above might be taken as a hint though about a future version of VSIDO...
Title: Re: Light DM issues
Post by: lwfitz on September 23, 2014, 02:15:01 AM
Poof...... and like a ghost I appear......

Has anyone found a fix for this (maybe I missed it?) I ran a new install after finally selling my macbook and when I updated without reading any warning posts I then needed to reinstall..... Feel free to laugh  ???


Edit:

I was able to get updated and boot with no errors by first uninstalling lightdm with

Code: [Select]
sudo apt-get remove lightdm
then

Code: [Select]
sudo apt-get update
then

Quote
get lightdm

When apt asked if I wanted to use the developers version of lightdm.comf I said yes.

Then I ran

Code: [Select]
sudo apt-get update
sudo apt-get dist-upgrade

I rebooted and all was good in the world again. I think someone else mentioned it already but it seemed to be a change in the lightdm config (stating the obvious I know).


Title: Re: Light DM issues
Post by: jedi on September 23, 2014, 03:43:12 AM
@lwfitz, your avatar is way more vomitous than mine!  This is the same lwfitz right?  The one who used to talk to us on IRC?  Maybe you'll "poof" in there too!
Title: Re: Light DM issues
Post by: lwfitz on September 23, 2014, 03:51:07 AM
Hahaha of course it is you dork! I'll be in there tonight so prepare yourself!
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 03:35:43 AM
I was able to get around the

Quote
Attempt to unlock mutex that was not locked

error in spacefm by removing spacefm and installing spacefm-gtk3
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 03:41:42 AM
^ Thanks lwstangerfitz

Was not even aware that there was a version such as this
Title: Re: Light DM issues
Post by: statmonkey on September 24, 2014, 03:50:32 AM
Me either, great tip. Thanks lwfitz
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 03:51:37 AM
 :D Theres definitely nobody stranger than me

I wasnt either, I found it in synaptic and gave it a try. I found some posts that mentioned removing libglib 2.0-0 or commenting it out in
the program thats erroring but I cant find it anywhere in disk-manager.
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 04:02:46 AM
Bonus points for anyone who can get the gtk3 themes working correctly ... I used to be able to change them but it no longer seems to work
Title: Re: Light DM issues
Post by: PackRat on September 24, 2014, 03:56:25 PM
Quote
Also what happened to "uptime"?  "The following applications are missing from your system: uptime" this comes from running "inxi --recommends".  It says to add it to my system I need to install the proper distribution package for my system: Debian: procps
procps is already the newest version

And yet, Conky displays the uptime just fine...

Like I said, ridiculous...

Conky must be using some other way to calculate the system uptime; there is a /proc/uptime file, but the numbers in the file appear to need conversion to a common time format - the first number appears to be seconds. Maybe the second number is a cumulative uptime if you have multiple boot/start during the day.

For anyone looking for a real hack of a solution to replace the uptime binary - and get inxi working again - I came up with this:

Code: [Select]
#!/bin/sh
# replacement (ok hack) uptime script for vsido/debian sid  -- DO NOT USE ON ANY OTHER DISTRO
# save file as uptime to some location on your path and make it executable
# gives uptime in minutes only

vsidoup=`top -n1 -d0.1 | grep "up" | awk '{print $5}'`

echo $vsidoup

exit 0

it's a real hack, but inxi is working again, and there doesn't appear to be any bad effects - I'm going with the assumption that debian sid/vsido has deprecated the uptime binary in favor of some other process. Obviously, this would hose any distro that uses the original uptime - debian stable, #!, etc ...
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 08:36:24 PM
Ok so a fresh install of VSIDO later and this is what I have come up with. I believe the culprit is

Code: [Select]
libglib2.0-0
so before updating I ran

Code: [Select]
sudo apt-mark hold libglib2.0-0 libglib2.0-data libglibmm-2.4-1c2a
that in turn stopped all this from updating

Code: [Select]
gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gtk-3.0 glib-networking
  glib-networking-common glib-networking-services gnome-themes-standard
  gnome-themes-standard-data libglib2.0-0 libglib2.0-data libglibmm-2.4-1c2a
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgtkmm-3.0-1 libsoup2.4-1

and also uninstalled pithos, xfce4-screenshooter and something else that I cant remember.

At this point I ran

Code: [Select]
sudo apt-get update && sudo apt-get dist-upgrade

and when asked about the lightdm version to keep I said "Y" to install the maintainers config.
Once all the updates installed I rebooted and spacefm and disk-manager opened just fine.

I then ran

Code: [Select]
sudo apt-get install pithos xfce4-screenshooter
Both installed fine and everything seems to be running properly except chromium but thats a seperate issue I believe.

So now that things are working as they should we can focus on exactly which one of those dependencies are causing this mess
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 09:04:05 PM
So if you unhold those packages that you held what then happens? this is great work Luke hopefully it'll lead us down to solving this even better

@packrat conky does use its own separate languages and calls and uptime is definitely one of them
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 09:20:54 PM
If I unhold

Code: [Select]
libglib2.0-0 libglib2.0-data libglibmm-2.4-1c2a
then

Code: [Select]
gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gtk-3.0 glib-networking
  glib-networking-common glib-networking-services gnome-themes-standard
  gnome-themes-standard-data libglib2.0-0 libglib2.0-data libglibmm-2.4-1c2a
  libgtk-3-0 libgtk-3-bin libgtk-3-common libgtkmm-3.0-1 libsoup2.4-1

will install and break everything again.

What I dont know is if it was truly libglib2.0-0 or if it was one of the other dependencies that got held back.


Edit:

I just released the hold on  libglib2.0-data libglibmm-2.4-1c2a and ran those updates with no problem.
Title: Re: Light DM issues
Post by: statmonkey on September 24, 2014, 09:23:08 PM
FWIW http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1260439.html (http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1260439.html)

States that it is libglib2.0-0. causing the issue

While I am at it this is about the fourth thread like this I have read today when trying to resolve errors that are showing up in my syslog and others http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/20551 (http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/20551) not to sound like a mensch but that answer/response and the similar ones just piss me off, totally unprofessional and slipshod work.
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 09:26:10 PM
^ Exactly what I thought. Thanks for the confirmation Statmonkey! So my guess is that if we give it a couple days this will be fixed
Title: Re: Light DM issues
Post by: statmonkey on September 24, 2014, 09:35:42 PM
Ha!  would not have found it wo your tip.  Easier to resolve once you have an idea.  The get back to a known beginning move was a good one.  You took one for the team there as I have been too nervy to do a re-install given the current state of affairs. Kudos lwfitz
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 10:26:12 PM
I would like this cleaned up and put in another thread and marked as solved if at all possible

Has every package that was held now unheld?  Is it all simply a matter of timing?

Let me know please.. thanks!
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 10:48:20 PM
Im always willing to take one for the team as long as it moves us forward  8)

@ VastOne

No, I still have

Code: [Select]
libglib2.0-0
being held withich in turn holds the following back

Code: [Select]
gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gtk-3.0 glib-networking
  glib-networking-common glib-networking-services gnome-themes-standard
  gnome-themes-standard-data libglib2.0-0 libglibmm-2.4-1c2a libgtk-3-0
  libgtk-3-bin libgtk-3-common libgtkmm-3.0-1 libsoup2.4-1

So all those packages I cant upgrade without bricking my system again. Should I wait to mark it solved until I can actually update successfully?
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 10:50:25 PM
Until all packages can be unheld and those can be updated it is not solved.  I misunderstood, I thought you had unheld them all

Thanks
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 10:51:05 PM
Since I am on a new install I am going to unhold and update to confirm. If I blow it up I can just reinstall tonight
Title: Re: Light DM issues
Post by: statmonkey on September 24, 2014, 10:52:21 PM
Well it is kind of solved.  If you held the packages before upgrading (as I understand it) then it would keep you from downloading broken packages.  If, like I think most of us did, you unknowingly upgraded the glib packages then it will remain broken until they are fixed.  So it's solved in that we think that those packages being fixed will resolve it manner but if you did the upgrade already you will either have to not use spaceFM, etc. or you will have to reinstall and upgrade holding that package at the least.  lwfitz can correct me if this is wrong, or anyone else for that matter but that is my take on it.

For me it's solved in that I rebuilt lightdm and am manually run my config on reboot. I have also removed spacefm and some others and will reinstall when I see this fixed.  Personally though I have everything on hold until I see things like calibre not being removed and I am not being forced to add apache2, etc.  8)

oops everybody answered at the same time  :D
Title: Re: Light DM issues
Post by: VastOne on September 24, 2014, 11:02:09 PM
^ Yes and I agree completely..

My version of solved is the bigger picture.. In terms of the next ISO build and there is no way I can go forward with so many held packages or a gtk3 version of spacefm

If this does resolve in the next few days then we may be able to stay with SpaceFM for a while longer but even that is iffy IMO.

I am also concerned that every solution I have seen for the mutex issue has been a patch to that specific application and that there may never be a solution for apps that are no longer maintained
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 11:24:17 PM
Ok I just went one step further and removed the hold on everything, essentially breaking my system again. I then manually downloaded the old version of  libglib2.0-0 which is being used by jessie (ver. 2.40.0-5). I then installed that version with dpkg and everything was back working. I can reproduce this simply by upgrading libglib2.0.0-0.

I will keep an eye on this and remove the hold and downgrade/dist-upgrade libglib2.0.0-0 until its fixed then post in here.

Title: Re: Light DM issues
Post by: statmonkey on September 24, 2014, 11:42:20 PM
[removed due to a sanity check by the author] :-[

Please erase my raving wild arse rant from your memories.  My apologies. 
Title: Re: Light DM issues
Post by: lwfitz on September 24, 2014, 11:57:05 PM
I was on the phone when I was typing and was a bit wordy, what I was getting at is that I can confirm that the next version of libglib2.0.0-0 works properly. Just stating the obvious I guess ;)
Title: Re: Light DM issues
Post by: VastOne on September 25, 2014, 12:02:03 AM
^ I think you mean the previous version of libglib2.0-0... that would be in Testing/jessie being used by jessie (ver. 2.40.0-5) realm ...

The broken version we are at in SID is libglib2.0-0 ver. 2.42.0-1 0

So it would need to be a regression install of libglib2.0-0 .. just to clarify


Title: Re: Light DM issues
Post by: VastOne on September 25, 2014, 12:04:41 AM
I am also shocked that none of this has made it to listbugs... hmmm unless of course listbugs is broken too!
Title: Re: Light DM issues
Post by: lwfitz on September 25, 2014, 12:05:48 AM
Oh shoot, your absolutely correct sorry about the misunderstanding. Doing too many things at once.

Fixed my post.
Title: Re: Light DM issues
Post by: statmonkey on September 25, 2014, 01:50:56 AM
For anyone using pcmanfm or thunar and get a not authorized to perform operation when trying to mount a device

edit / create

Code: [Select]
/etc/polkit-1/localauthority/50-local.d/50-filesystem-mount-system-internal.pkla
with this
Code: [Select]
[Mount a system-internal device]
Identity=*
Action=org.freedesktop.udisks2.*
ResultActive=yes

It will resolve all mounting problems as long as udisks2 and gvfs are installed (both are by default in VSIDO)

Not as secure or as elegant as spaceFM but a fix for now


I wanted to bump this back to the top.  It probably needs to be in a thread of it's own but this indeed fixed the problems I was having with all my external drives.  This was pretty major for me because just turning on my external 4 bay was completely locking up my system.  A belated and bow and thank you to the Very Vast One.
Title: Re: Light DM issues
Post by: VastOne on September 25, 2014, 02:02:30 AM
^ Thank you statman!

I am sure I got that from the Arch Wiki or forum.. those guys are the legends
Title: Re: Light DM issues
Post by: statmonkey on September 25, 2014, 02:24:36 AM
It looks like some things are sorted.  I just ran and update and it seemed to not demand the removal of calibre and it's got all the pythonqt and glib stuff in it.  It also is still demanding that I install apache2 but at this point I will give that up and see what removing it post upgrade does.  I'll be testing this tonight I suppose the bash bug/exploit forced them to push something out right away.
Title: Re: Light DM issues
Post by: jedi on September 25, 2014, 03:28:35 AM
Yes, some things are solved!  Calibre is still there and working after a successful update and dist-upgrade!  Still getting the "mutex" error on things like Mirage and Disk-Manager.  So to my eyes, while some things have been ironed out, probably should wait on marking this as solved?   ::)
I've switched around several Gtk themes, and get the same errors when trying to run those particular apps.

So it appears that the piecemeal effort of patching apps, one at a time, (as they fail) is still about the only way some of this is going to be worked out.  Why can't I kick the poop out of somebody?   :'(

I guess I can't complain to bad.  I got to read an Elmore Leonard novel today (Raylan) that was most enjoyable!  (thanks statmonkey)  8)
Title: Re: Light DM issues
Post by: statmonkey on September 25, 2014, 03:36:53 AM
Jedi you are welcome to (virtually anyway) kick the shit out of me anytime you want. 

Man you sprinted thru that you will probably have that whole library read in about a month.  Don't worry I have another 1,000 or books to add to it when I get the time. 
Title: Re: Light DM issues
Post by: ozitraveller on September 25, 2014, 03:43:00 AM
I have a number of boxes/vm's with sid running and apart from the issue with lightDM I seem to be stable, so far. The only place I had spacefm installed I had removed a couple of weeks ago and replaced with pcmanfm.

But I thought this sounded familiar, and had problems similar to this some time back.
http://crunchbang.org/forums/viewtopic.php?id=34355&p=1 (http://crunchbang.org/forums/viewtopic.php?id=34355&p=1)
Title: Re: Light DM issues
Post by: jedi on September 25, 2014, 06:43:57 AM
OK, some changes made to Gtk.  Will post more tomorrow...  Of note, the themes have to match for you to not get the 'ugly' windows.  There are only a few themes to choose from in this regard.  (in my defense this was all done at the point of exhaustion so try at your own risk...)
What I've done is switched to a theme that is the same with Gtk2 and Gtk3.  It is called OMG for anyone interested.  A nice eye pleasing dark theme...

A couple of scrots;
(http://en.zimagez.com/miniature/092514b.jpg) (http://en.zimagez.com/zimage/092514b.php)

(http://en.zimagez.com/miniature/092514c.png) (http://en.zimagez.com/zimage/092514c.php)
Title: Re: Light DM issues
Post by: statmonkey on September 25, 2014, 05:28:19 PM
I have a number of boxes/vm's with sid running and apart from the issue with lightDM I seem to be stable, so far. The only place I had spacefm installed I had removed a couple of weeks ago and replaced with pcmanfm.

But I thought this sounded familiar, and had problems similar to this some time back.
http://crunchbang.org/forums/viewtopic.php?id=34355&p=1 (http://crunchbang.org/forums/viewtopic.php?id=34355&p=1)

I love that thread.  Resisting ....... urge ............ to ................. rant. Especially

Quote
but why does it change over night and kill setups?  sad
Don't answer that . . . just thinking out loud.

I am thinking that your degree of problems is going to be directly related to what customizations you have made and where you have made them.  The first set of changes that happened then were more for permission type changes and now it is more for locational stuff and bells and whistles.  I missed most of that first run, this one hits me hard.

For me I will probably see more than most because I have written a fair amount of scripts/packages that work very low level and use certain sanity checks to make sure things are where I think they should be.  When they aren't then that is one problem, but when the actual beginning point is not where I think it should be then that is a different problem.  The second issue causes the sanity check itself to be completely ignored or worse infinite loops and heavy processing time to find that beginning point or resolve to something.  This explains why my box is just grinding away at times with no messages or notification and the box seems like it is locked up.  It would seem to be one of those rare cases where proper coding is actually a detriment.  It also explains what originally happened with LightDM, things were moved and left no forwarding address, the system didn't report it because it's the kind of exception that you just don't expect.  You expect to be starting from a known point.

I believe that I see a pattern here in the changes being made and I think they are towards greater consistency on the protocol of where things go and the order in which they are processed.  I do wish that there had been something put out somewhere (maybe there is but I haven't seen it) that says this is what we are doing and why and how you should expect things to be placed/perform going forward.

I also think that will happen and it will all catch up.  Or if it doesn't I will just start from scratch and rebuild it.  The great thing about VSIDO is that despite the customizations I have done and will probably have to rewrite or forgo I can be from 0-60 in an hour or so.  Again, VastOne thank you.
Title: Re: Light DM issues
Post by: VastOne on September 26, 2014, 01:31:36 AM
^ My pleasure sir!

I have a pretty good idea who said that over there and it leads me to a conclusion as well... people learn in their own ways. Some fast, some slow and some might not ever 'get it'

Then you have those who will be antagonistic till the day they die... those are also the ones who usually do not know the meaning of forgiveness and most often than not the same ones are banned from every reasonable forum out there. Just an observation ...

Jedi... nice OMG theme ... Here is the link to get it (http://gnome-look.org/content/show.php/OMG_Suite?content=149294)
Title: Re: Light DM issues
Post by: lwfitz on September 26, 2014, 01:53:27 AM
Quote
Then you have those who will be antagonistic till the day they die...

Yes! You mentioned me   :P
Title: Re: Light DM issues
Post by: statmonkey on September 26, 2014, 02:29:55 AM
Quote
some might not ever 'get it'

Then you have those who will be antagonistic till the day they die...

Aha! But he mentioned me twice.  Still torn on whether to reinstall or not.  System is locking up more frequently or more accurately slowing to a crawl and without out real error messages pretty impossible to debug.  I also really need to understand what services systemd really needs for drives.  I see an awful lot of things I would think would be started automagically that are "not-found".
Title: Re: Light DM issues
Post by: VastOne on September 26, 2014, 02:33:16 AM
^ statman!

REO Speedwagon - Ridin' The Storm Out (Original Studio Version) (http://www.youtube.com/watch?v=HTBv4kAdk_w#)
Title: Re: Light DM issues
Post by: statmonkey on September 26, 2014, 03:43:42 PM
Thank you for not foisting the REO with Kevin Cronin in it but the one of a kind REO where Gary Rickrath was still in one piece and Murphy sang lead.  When they were making statements instead of making $$$.  Now go to your room and listen to Golden Country five times in a row.
Title: Re: Light DM issues
Post by: superwow on September 27, 2014, 01:16:50 AM
All,

I have seen this thread growing the past few days. It relates to lightdm. I too had problems about a month ago with lightdm http://vsido.org/index.php?topic=823.0 (http://vsido.org/index.php?topic=823.0) but eventually solved them with your help.

But is this rash of recent borkage, apps like gpodder (ok now), calibre (ok for today), spacefm, lyx, mplayer (off and on), mirage, all breaking related to lightdm issues? or libgt issues?

I gave Sector11's post a read through (http://crunchbang.org/forums/viewtopic.php?id=34355&p=1 (http://crunchbang.org/forums/viewtopic.php?id=34355&p=1)) and that seems all somehow related to my own former issues, though more complex.

I guess what I want to know is
1) are these problems indicative of underlying troubles in the Debian or apt organizations?
2) I have suspected there is a bug in dpkg or apt for about 2 months. I am seeing lots of apps get uninstalled and others installed. Is this part of the problem?
3) what's the best advice to update frequently, but avoid the breakage?
4) and remind me how to put an html link under text so I can click on it.
Title: Re: Light DM issues
Post by: statmonkey on September 27, 2014, 01:54:28 AM
I can only speak for myself.  These are all very good questions and I think the answer is still unclear.  There is evidence that there are various issues.  There have been changes to the libgt packages (most of which are resolved I think), I have several packages that seem to be changed in structure and I also am trying to better understand what services are running and what are not and why.  I have been surprised a few times when I go to do something and it doesn't work.  If anyone knows of a good place to learn the nitty gritty of what systemd does and how it is supposed to work I am all ears.  I don't know of any issues with apt or dpkg, with Sid we sometimes go through this but it has been a couple of years since I have seen it like this, I do think it will work itself out.

As for upgrading frequently the best advice I can give is to watch what it going on, don't update unless you are entirely comfortable with what is changing on your system and if you have questions post something in here for advice.  Understanding how to hold packages is a plus and better to not upgrade than to wipe out something you need or want.  Example I waited a couple of days for Calibre to work through it's in and out before upgrading.

FWIW I am still having issues with lightdm doing what it is supposed to do and with it configuring properly.  If and when I figure it out I will post something here.  Maybe one of the guru's here have better advice?
Title: Re: Light DM issues
Post by: jedi on September 27, 2014, 02:07:43 AM
Tis my belief this is still related to libglib2.0-0 and/or Gtk3.  I have not had any issues with apt of dpkg.  We have had a pretty smooth ride with SID the past couple of years, and have been spoiled by the awesomeness of our distro.  I think it says tons of VastOne that VSIDO has had such a smooth run.

I believe that this is indeed SID throwing a tantrum, and will be over soon.  Fingers crossed.  Reading through that 'other' thread, doesn't shed any light for me on the current state of events, and I'm fairly certain has nothing to do with what is happening now.

A few days of patience, all will probably be sorted out...
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 02:11:06 AM
@superwow

This is SID... this is expected in some ways but as has been indicated and ESPECIALLY after such a mass kernel update, there will be major updates to nearly all applications in some way or another or they die. In that process there are apt to be issues (pun intended)

The borkage is 'expected' in some channels and you will most likely hear "that is what you should expect running SID"

We do not believe in that Bull Shit here... Most of us have been running SID for 5 years or more and have never seen anything quite like this but we know it is possible.  We do not run from issues ... the reason why we are strong and stay with it?  We expect these issues and it is not painful because it is 'broke' it is painful because we cannot solve it, we are solution driven to seek out and find the solution and NOT to be given it ...

lightdm decided to pull back it's own default setup files for whatever reasons and only a blank lightdm setup seems to work.. File a bug report with them ..

ligbt is also an issue with the mutex problems and that one will most likely resolve itself soon, or applications will need to patch it to get it to work or if not maintained they may not (spaceFM)

Some folks think it is a major systemd issue .. I do not know but I am watching that closely

Debian nor apt nor the package management side is broke..

What statmonkey says here is a golden rule...
 
Quote
As for upgrading frequently the best advice I can give is to watch what it going on, don't update unless you are entirely comfortable with what is changing on your system and if you have questions post something in here for advice.  Understanding how to hold packages is a plus and better to not upgrade than to wipe out something you need or want.  Example I waited a couple of days for Calibre to work through it's in and out before upgrading

Hold on to your britches if you need to .. SID is being a petulant little bastard at the moment...if you hang with it .. it could be another 6 years of gold running.  Notice I have not updated the ISO's on their normal updated cycles.. When this clears, I will put new ones out.  Until then, enjoy a clean install before all of this shit and do what jedi, statmonkey and lwfitz and several others have suggested.. wait it out ..

I've got your back!
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 02:24:01 AM

I believe that this is indeed SID throwing a tantrum, and will be over soon.  Fingers crossed.  Reading through that 'other' thread, doesn't shed any light for me on the current state of events, and I'm fairly certain has nothing to do with what is happening now.

A few days of patience, all will probably be sorted out...

Well said...

I have not read that other thread at all ... we have enough of our own issues with what is affecting VSIDO and it's users to be concerned with another thread on lightdm and SID
Title: Re: Light DM issues
Post by: statmonkey on September 27, 2014, 02:54:22 AM


I believe that this is indeed SID throwing a tantrum, and will be over soon.  Fingers crossed.  Reading through that 'other' thread, doesn't shed any light for me on the current state of events, and I'm fairly certain has nothing to do with what is happening now.

A few days of patience, all will probably be sorted out...
Well said...

I have not read that other thread at all ... we have enough of our own issues with what is affecting VSIDO and it's users to be concerned with another thread on lightdm and SID



Hey Jedi, I did read that thread and most of it is polkit stuff so always good to see what others have run into.  I will point out that the aptosid forums have been really quiet, I think we are seeing more in VSIDO because of the particular lean and mean way the distro is built. 

This is a distro again that is built to be just what it needs to be.  That means not more is there than should be and not less.  That is, paraphrasing Col. Kurtz "like a snail crawling along the edge of a razorblade".  It also recognizes how amazing that we have not had bigger issues since ... well forever.  I did see something like this in my first Sid experience on ... (oy can't remember the name aptosid was in the olden dayz) any way its been a long time.  It will get sorted.  I again think it is a great many things in Debian being worked on at once, kind of a perfect storm.  I am also not sure that systemd has anything to do with it at all, but the fact that the individual is standing over the body with a smoking gun, powder burns and a wry smile on her face makes me suspicious :) 

VO has your back and we all have his.  Just hang in there.
Title: Re: Light DM issues
Post by: lwfitz on September 27, 2014, 04:59:31 AM
Ive been threatening VastOne for two years that I am going to format my drives and install Windows 98 and this time I just might do it!

Seriously though, growth comes more from failure than it does success. So while this breakage is an inconvenience to some and a serious pain in the butt to others I think its important to look at the big picture. VSIDO goes two+ years without any real issue and hits a plateau as far as growth goes. Now just a few days later we are digging in trying to figure out what we can change or fix.

SID by definition is unstable and although "we" dont accept that as gospel its important that when things do break we react accordingly.

Title: Re: Light DM issues
Post by: PackRat on September 27, 2014, 02:24:08 PM
Quote
I am thinking that your degree of problems is going to be directly related to what customizations you have made and where you have made them.

I'm leaning toward this one - other than the mutex issues with mirage and maybe a couple other apps, I've had no issues - none with lightdm.

Quote
Some folks think it is a major systemd issue .. I do not know but I am watching that closely

unfortunately, this will be a first response for a while as systemd gets more integrated into the various distros; downside is a person could be chasing their tail for a while and overlook something that would have otherwise been - for lack of a better word - obvious. Kind of reminds me of those strategy sessions in the TV series House.
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 02:30:19 PM
That is a perfect analogy Packrat, good one.  Any House references is a win-win
Title: Re: Light DM issues
Post by: PackRat on September 27, 2014, 02:36:54 PM
So we can rule out Lupus?
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 04:12:02 PM
Organophosphate poisoning is my guess... deliberate and has everyone fooled   :o
Title: Re: Light DM issues
Post by: jeffreyC on September 27, 2014, 06:20:36 PM
Though I hate to disrupt a good House riff;

Has anyone considered switching to SLiM or some other login manager?
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 06:24:49 PM
Yes.  I have SliM all lined up and ready to replace lightdm. The issue I  have is SliM is no longer maintained.. anything else I have tried has flat out SUCKED... and SliM has none of the features LightDM has

I am open to suggestions
Title: Re: Light DM issues
Post by: PackRat on September 27, 2014, 07:02:01 PM
Couple of items -

Linux Mint uses (used?) a fork of GDM-2 as their display manger; looks to still be maintained - https://github.com/linuxmint/mdm (https://github.com/linuxmint/mdm)
If it's being used on Mint Debian Edition, it may be easy enough to set it up in the apt sources. I may go ahead and build that from source later in the week if I get motivated. Might require Does require a boat load of gnome dependencies though.

Any VSDIO user have the skills to code a display manager in bash (python, PERL)? I know there are some display managers written in bash that the Arch users came up with. I unfortunately, do not have coding skills.

Go without a display manager. Fluxbox is the only window manager installed by default. Create a .xinitrc that launches with the appropriate services for automounting etc ... and launch startx by default. Would require adding xinit to the iso.
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 07:39:12 PM
^ I did build and setup MDM and it appears to have issues and depends on a shitload of junk.. (IMO) thanks for that suggestion

I have also installed and am playing with xinit and it's rc.  I have easily setup fluxbox but will research Arch wiki and forum to get the 'appropriate services for automounting etc' settings needed

If you have examples or knowledge fire away... I have no issue getting rid of it all to get it right
Title: Re: Light DM issues
Post by: PackRat on September 27, 2014, 08:08:14 PM
my .xinitrc for fluxbox; should provide automounting and work with any window manager of choice -

Code: [Select]
#!/bin/sh

########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

########################################################################
##  Start xfce Desktop Environment                                    ##
########################################################################

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session /usr/local/bin/startfluxbox
else
  exec dbus-launch --exit-with-session /usr/local/bin/startfluxbox
fi

if you have multiple window managers -

Code: [Select]
#!/bin/sh

DEFAULT_SESSION="$HOME/.defaultWM"
case $1 in

#if pgrep dbus-daemon ; then killall dbus-daemon ; fi # kill all pre-existing dbus instancesi
#eval `dbus-launch --sh-syntax --exit-with-session` # start dbus and export DBUS_* environment variables

fluxbox)
########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session /usr/local/bin/startfluxbox
else
  exec dbus-launch --exit-with-session /usr/local/bin/startfluxbox
fi
;;


i3)
########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session /usr/bin/i3
else
  exec dbus-launch --exit-with-session /usr/bin/i3
fi
;;

fvwm)
########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session dbus-launch --exit-with-session /usr/local/bin/startfvwm
else
  exec dbus-launch --exit-with-session /usr/local/bin/startfvwm
fi
;;


# --- do not edit below this line --

*)
exec  $DEFAULT_SESSION
;;

esac

for multiple window managers, I use:

Code: [Select]
xinit [window manager]
to start the window manager of choice; needs to match one of the .xinitrc entries. Using startx will start the DEFAULT_SESSION listed; defaltWM is basically the same as the .xinitrc for fluxbox that I use. Note that DEFAULT_SESSION is not one of the .xinitrc entries, it is an actual command so it needs to be something separate.

I use to use the multiple window manager .xinitrc with the older versions of slim that read the ~/.xinitrc. Doesn't work as well with the newer versions, the slim.conf needs some modifications to work like the older versions.

I use to go without a display manager because gdm got bloated, and I was never really a fan of lightdm or slim because I never considered them as light on resources as they advertise. It's easy enough to just issue the startx command. I like automounting of removable media, so as long as I can get that into a .xinitrc I'm good.

Using lightdm at the moment so as not to stray from default VSIDO setup. Works better to help you track bugs etc ...

In the wishful thinking category, I always thought it would be cool to have an ncurses based display manager similar in aethetics to ceni that would read the files in /usr/share/xsessions and do all the under the hood stuff that apps like lightdm do.
Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 08:42:44 PM
^ Thanks PackRat! I am going to test this now... I am going to remove SliM now and only boot to the .xinitrc for fluxbox example

I like your ncurses idea... that would be the perfect answer to this simple task

Or perhaps a zenith solution... it seems very easy as well, a gui wrapper for commands
Title: Re: Light DM issues
Post by: statmonkey on September 27, 2014, 09:06:00 PM
But not today, just peeking in here between races to see what is new.

I am pretty nervous about slim.  I hadn't seen the stuff in arch will look at that.  I don't have a problem working something up and creating a deb out of it assuming I am not re-inventing the wheel (from a time perspective).  Having our own deb has the obvious advantage of our code/our tweaks/and all that good stuff.  I will also peek at what you have posted here PackRat all good stuff.  I looked at MDM and rejected that option for the reasons discussed (at least rejected it for my purposes).  Also I used to have the lightdm code somewhere I can look at tomorrow.  I think working something up would not be a huge deal.  I was planning on re-writing makethumb code this weekend since the glib stuff has made the zenity part of it look very dirty.  I can have a look at this stuff then as well.

Title: Re: Light DM issues
Post by: VastOne on September 27, 2014, 09:20:27 PM
@PackRat

Booted to .xinitrc no issue... though I was a bit surprised that I actually had to initiate it with a startx command... Is there anyway to login and have a startx start upon that login... easy fecking peasy indeed

@statmonkey... I have no issue in getting the code the way we want/need it and creating a deb just for that also... dpkg-repack tool is awesome just for that

Will talk later... need to do some shopping

This has been a productive day for V-Ger
Title: Re: Light DM issues
Post by: VastOne on September 28, 2014, 01:42:30 AM
FECK LightDm and any other BS login managers

Thanks to PackRat I began looking closely at xinit and startx and .xinitrc

I created this file .bash_profile and now when I login from the initial tty screen, fluxbox starts perfectly.. If I find a way to have a background image or statement on that tty, it will be perfect

First install xinit

Code: [Select]
sudo apt-get install xinit
or

Code: [Select]
get xinit
~/.bash_profile

Code: [Select]
# Created by V-Ger for use in the VSIDO env
# ~/.bash_profile: executed by bash(1) for login shells.

# the default umask is set in /etc/login.defs
#umask 022

# include .bashrc if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi

# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ] ; then
    PATH=~/bin:"${PATH}"

fi

#start X at login
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
  exec startx

fi

This will be the default .xinitrc

Code: [Select]
#!/bin/sh

########################################################################
##  Created by V-Ger for use in the VSIDO env                         ##
########################################################################

########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

########################################################################
##  Start FluxBox Desktop Environment                                    ##
########################################################################
 
  exec dbus-launch --exit-with-session /usr/bin/startfluxbox
fi

This will be on the next ISO released
Title: Re: Light DM issues
Post by: PackRat on September 28, 2014, 02:05:00 AM
Quote
Booted to .xinitrc no issue... though I was a bit surprised that I actually had to initiate it with a startx command... Is there anyway to login and have a startx start upon that login... easy fecking peasy indeed

Just like you did it with the .bash_profile, or - with sysv  or bsd init - you can put startx in the rc.local. I don't know if the rc.local file will become deprecated as systemd moves forward. I suppose you could write a startx.service file to get you where you want to go. And take a look with htop to see how much memory you save by not using a display manager.

there is also this method

Quote
#start X at login
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
  exec startx
fi

I believe that will startx when you log in from tty1 and then log you out when you exit X.

And since you are calling xmodmap and xrdb in your .xinitrc, you can comment those commands out of your ~/.fluxbox/startup  - no harm calling them twice, just being efficient.

As far as images go, you may be able to do what slackware and some other distros do with the Tux penguine image in the upper left - I don't know how that is accomplished. Another option would be some ascii art like FreeBSD does. A full screen image may be out of the question - even if you put it in the frame buffer, I think it would cover the login prompt.

Finally, I'm not sure if the ck-launch-session part is necessary any more. That refers to console kit which is now handled by systemd - the example I posted earlier was for slackware bsd init. Doesn't seem to matter, just another of those efficient coding things. It's a learning process, no doubt in my mind you'll master it.
Title: Re: Light DM issues
Post by: VastOne on September 28, 2014, 04:53:16 AM
^ Thanks for those PackRat...  I have made the changes you suggested and it is becoming a clearer picture now.  One I am enjoying

The changes are reflected in the post above and the config files

I will look at putting some kind of image there eventually..

Today has been a good day

Thanks to everyone who assisted...

Title: Re: Light DM issues
Post by: jedi on September 28, 2014, 06:06:42 AM
Works perfectly, of course!  Nice work PackRat, you've inspired VastOne!  This works beautifully.  I had removed lightdm on Sunday last, and started using SliM.  Today I removed SliM as well, and am using the above two files to login and out.
Beautiful work guys...   ;D
Title: Re: Light DM issues
Post by: PackRat on September 28, 2014, 11:45:09 AM
cool it's working for you two.

This is a good read - explains how all this works together on logins:
 
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/profile.html (http://www.linuxfromscratch.org/blfs/view/svn/postlfs/profile.html)

I have never used a .bash_logout file, but that looks like it could be interesting.
Title: Re: Light DM issues
Post by: VastOne on September 28, 2014, 12:11:37 PM
^ Thanks for that... A really well done read and explanation. I will be following that closely for the VSIDO standards.
Title: Re: Light DM issues
Post by: PackRat on September 28, 2014, 05:38:15 PM
No problem.

Right now I'm setting up the .xinitrc for multiple window managers ( we all have at least 3 installed, correct  :D ).

Automounting removable drives is a bit trickier; I have a work-around-and-around-and-around going that works just fine, but there has to be something more elegant.

Seen some references to systemd.automount (for Manjaro) for external drives, nfs shares and that sort of thing never heard of that service before. Will need to investigate it at some point.
Title: Re: Light DM issues
Post by: jeffreyC on September 28, 2014, 05:51:57 PM
I think that they have done something like what you are working on over at LinuxBBQ, I know they have no love for login managers.
Maybe worth a look, why spend time reinventing the wheel?
The fish may be biting or............
Title: Re: Light DM issues
Post by: PackRat on September 28, 2014, 06:02:47 PM
thanks

just looked at their cream edition with all the wm's. Got the ncurses list of wm's going; just need to figure out automounting for removable media.
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 12:21:39 AM
Got this in a tweet... Thought it was nice ... have not had a chance to follow up yet

Too busy being sick

 Eugenio Paolantonio @eugenio_g7   From Semplice Linux (http://semplice-linux.org/)

@VSIDO I'm reading in your forums that you have issues with lightdm,  here's the fix we used: (https://github.com/semplice/openbox-default-settings/blob/master/debian/postinst#L31) Hope it helps!
Title: Re: Light DM issues
Post by: PackRat on September 29, 2014, 01:10:33 AM
That's cool those people visit the vsido forum and offer up some help. Kudos to semplice.
Title: Re: Light DM issues
Post by: lwfitz on September 29, 2014, 01:36:57 AM
Did someone say the fish are biting?
Title: Re: Light DM issues
Post by: PackRat on September 29, 2014, 01:38:20 AM
I wish.
Title: Re: Light DM issues
Post by: statmonkey on September 29, 2014, 02:02:03 AM
That is beyond cool.  Semplice is a nice package, really well put together.  I actually have my Mother using it, can't be too bad if it's usable for an 86 year old.  I also found the people over there very helpful.
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 02:40:14 AM
thanks
 Got the ncurses list of wm's going; just need to figure out automounting for removable media.

devmon?

devmon is a configuration-less bash daemon script which automounts optical discs and removable drives. It can also selectively autostart apps or execute commands after mounting, ignore specified devices and volume labels, and manually mount and unmount devices (From IgnorantGuru's Blog)
Title: Re: Light DM issues
Post by: superwow on September 29, 2014, 02:55:30 AM
How about that, you got some buds over at Semplice. Their distro looks pretty good too. I'll have to follow him on Twitter.
Title: Re: Light DM issues
Post by: PackRat on September 29, 2014, 03:03:13 AM
I've never used devmon; heard of it though.

Figured it out, though, cleaning up the scripts and putting it through it's paces. Get a nice ncurses based list of wm's as well as tmux, shutdown, and reboot. Nice piece of work by the BBQ grillers. I just made a couple changes to get automounting to work. Their Cream edition had all the scripts I needed, but was setup to manually mount removable drives - makes sense since the BBQ crowd is a security conscious bunch of power users.

It's not vital, but I do want to figure out how to drop out of the wm list into the console, or add that to the list.

Kudos to the BBQ grillers for a really slick way to login graphically without a dm. Saves about 25M in memory.
Title: Re: Light DM issues
Post by: jedi on September 29, 2014, 03:12:04 AM
Made sure to tweet them back thanking them for the fix!  Nice when Linux communities can collaborate...
Title: Re: Light DM issues
Post by: ozitraveller on September 29, 2014, 06:04:54 AM
'udevil' is currently unsupported, isn't it? Is there an alternative?

Just curious.
Title: Re: Light DM issues
Post by: airtime on September 29, 2014, 08:32:57 AM
Just wanted to say thank you to Vastone and PackRat .. Great job everyone. This really help me. I am not sure why I didnt think about using xinit since that is the setup I use on my test Fedora system.  :-[
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 02:57:43 PM
Welcome to VSIDO airtime.. We are glad to have you!
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 03:03:15 PM
'udevil' is currently unsupported, isn't it? Is there an alternative?

Just curious.

hehe .. just curious my a**

That is a very good question Ozi... I think of udevil as more of a static or config type application and see it as less of an issue as spacefm... of course I could be dead wrong.  And yes there are alternatives already installed that have been in place long before udevil .. udisks2 and gvfs
Title: Re: Light DM issues
Post by: PackRat on September 29, 2014, 03:45:53 PM
Edit - You will need to purge lightdm from your system before setting this up. I used systemctl to disable the lightdm service, but the next lightdm upgrade re-enabled it.

For those of us who use more than one window manger, I have my system configured now to log in from an ncurses based display manager - courtesy of the linuxBBQ cream edition. On my system, for now, there are three files that require configuration. The login procedure takes advantage of startx being able to call any file. By default,

Code: [Select]
startx
calls the $HOME/.xinitrc file, but you can also use:

Code: [Select]
startx <path/init file> <window manager>
to call some other init file with the .xinitrc syntax - note that the full path to the init file is required.

The following files are configured for my system, but should be self-explanatory.

.xinitrc    <-- I have a separate .xinitrc as a failsafe, this one will start fluxbox with support for automounting removable media.

Code: [Select]
#!/bin/sh

########################################################################
##  Merge in defaults and keymaps                                     ##
########################################################################

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi

########################################################################
##  Start fluxbox Desktop Environment                                 ##
########################################################################

#if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
#  exec ck-launch-session dbus-launch --exit-with-session /usr/local/bin/startfluxbox
#else
#  exec dbus-launch --exit-with-session /usr/local/bin/startfluxbox
#fi

exec dbus-launch --exit-with-session /usr/local/bin/startfluxbox


.wminitrc       <-- just a .xinitrc for multiple window managers. $HOME/defaultWM is the same as my .xinitrc (as I recall, a symlink didn't work). Files like dwm-session are startup scripts similar to /usr/bin/startfluxbox. This is the file to be used by the display manager, I have it $HOME:

Code: [Select]
#!/bin/sh

DEFAULT_SESSION="$HOME/.defaultWM"

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

if [ -f $sysresources ]; then
    /usr/bin/xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    /usr/bin/xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    /usr/bin/xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    /usr/bin/xmodmap $usermodmap
fi


case $1 in

fluxbox)

exec dbus-launch --exit-with-session /usr/local/bin/startfluxbox

;;


i3)

exec dbus-launch --exit-with-session /usr/bin/i3

;;


openbox)

exec dbus-launch --exit-with-session /usr/bin/openbox-session

;;


fvwm)

exec dbus-launch --exit-with-session /usr/local/bin/fvwm-session

;;

dwm)

exec dbus-launch --exit-with-session /usr/local/bin/dwm-session

;;

spectrwm)

exec dbus-launch --exit-with-session /usr/local/bin/spectrwm-session

;;

# --- do not edit below this line --

*)
exec  $DEFAULT_SESSION
;;

esac

.wmselectrc  <-- this is the script to start the ncurses based display manager; run when you log in. I have it $HOME because I'm the only user that needs it. It can reside in /usr/bin or some other location on the PATH for system-wide use. There are two main areas to edit - the "alist=( window managers list )" line where any installed window managers you want selectable are listed, and the "case $wm in" section where the window manager list is matched up with the appropriate startx command. Note how the names used for the window mangers need to match up between the alist and the .wminitrc

Code: [Select]
#!/bin/bash

# taken and modified from linuxBBQ cream edition pick-wm file
# kudos to the grillers at linuxbbq.org

VERSION="cream-0.1"     # updated for cream

# WMLIST='/usr/bin/wmlist'      # name of the wm list file; last entry should be 'POWEROFF'
# README="$HOME/README" # name of the readme file

RELEASE="VSIDO"

# the list of window managers can be read from a file, one line at a time
# alist=($(cat $WMLIST))

# or set here inside the script. either way the last entry should always be POWEROFF

alist=( Fluxbox i3 Fvwm Dwm Spectrwm Openbox Tmux Reboot Poweroff )

let num=${#alist[*]}-1     # number of items in the array (minus one to account for zero index)
tmpfile=$(mktemp)          # make a temp file for dialog return value

# make a list in menu format, with a number first, then the name
for i in $(seq 0 $num); do
    blist[i]=$(echo $i ${alist[i]})
done

while true; do
    # display the list in a dialog, save the return value (the index number) in the tmpfile
    dialog --backtitle "$RELEASE" --no-tags --menu 'please choose a window manager' 20 50 50 ${blist[*]} 2>$tmpfile
    [[ $? = 1 ]] && exit # user chose "cancel"

    chosen=$(<$tmpfile)    # get the index from the tmpfile

    # index into the WM array to get the name of the WM
    wm=${alist[$chosen]}
    case $wm in
        Fluxbox )
            startx "$HOME/.wminitrc" fluxbox
            ;;
        i3 )
            startx "$HOME/.wminitrc" i3
            ;;
        Fvwm )
            startx "$HOME/.wminitrc" fvwm
            ;;
        Dwm )
            startx "$HOME/.wminitrc" dwm
            ;;
        Spectrwm )
            startx "$HOME/.wminitrc" spectrwm
            ;;
        Openbox )
            startx "$HOME/.wminitrc" openbox
            ;;
        Tmux )
            tmux
            ;;
        Reboot )
            sudo reboot
            ;;
        Poweroff )
            sudo poweroff
            ;;
        * )
            xinit $wm
        ;;
    esac
done

I'm using startx instead of xinit (the default for linuxBBQ Cream) because that is the only way I could get automounting of removable drives working (I have yet to find the reason for this). If you don't want to automount removable drives,  you can go back to the origianl xinit $wm used in linuxBBQ. The original files from the linuxBBQ Cream iso are bbqlogin, pick-wm, and the xinitrc.

To start the display manger when logging in edit your $HOME/.bash_profile

Code: [Select]
# Created by V-Ger for use in the VSIDO env
# ~/.bash_profile: executed by bash(1) for login shells.

# the default umask is set in /etc/login.defs
#umask 022

# include .bashrc if it exists
if [ -f ~/.bashrc ]; then
    . ~/.bashrc
fi

# Add $HOME/ items to PATH #
PATH=$PATH:$HOME/bin:$HOME/conky:./

#HISTORY
HISTSIZE=250
HISTFILESIZE=50

export EDITOR=/usr/bin/'nano -w'

#start X at login
##if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
##  exec startx

##fi

# ncurses list of wm's

if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
exec "$HOME/.wmselectrc"

fi


Get a window like this  -

(http://en.zimagez.com/miniature/september14120028031366x768.jpg) (http://en.zimagez.com/zimage/september14120028031366x768.php)

I'm sure there is a much more elegant and efficient way to code this, so suggestions are welcome.

Edit #2 - Bit of an issue with having this script and startx in the $HOME/.bash_profile (on my system anyway). If I want to drop out of the X session into a tty console, the script (or startx) will run again when logging in. Also Ctl-Alt-F1 doesn't work (apparently tty1 is in use with these methods). I can log into as a user that doesn't have the X session started by the $HOME/.bash_profile. Finally, exit or Ctl-Alt-F7  do not quit the tty and return to the original X session; Ctrl-Alt-Backspace does not kill X.

Edit #3 - fixed syntax error in .bash_profile. Can now drop into tty with Ctrl+Alt+F2, but cannot exit back to X-session.
Edit #4 - Ctrl+Alt+F1 will return to the X-session but not kill tty2. Curious, I have never known Ctl+Alt+F7 not to handle that, or "exit"
Title: Re: Light DM issues
Post by: statmonkey on September 29, 2014, 04:30:59 PM
'udevil' is currently unsupported, isn't it? Is there an alternative?

Just curious.

hehe .. just curious my a**

That is a very good question Ozi... I think of udevil as more of a static or config type application and see it as less of an issue as spacefm... of course I could be dead wrong.  And yes there are alternatives already installed that have been in place long before udevil .. udisks2 and gvfs

Already mentioned this elsewhere but I really would advise against udevil.  I think what ozi meant was are there not efficient/elegant alternatives to udevil ... that would preclude udisks2 and gvfs :)  The answer would be (to the best of my knowledge NO).
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 04:56:50 PM
'udevil' is currently unsupported, isn't it? Is there an alternative?

Just curious.

hehe .. just curious my a**

That is a very good question Ozi... I think of udevil as more of a static or config type application and see it as less of an issue as spacefm... of course I could be dead wrong.  And yes there are alternatives already installed that have been in place long before udevil .. udisks2 and gvfs

Already mentioned this elsewhere but I really would advise against udevil.  I think what ozi meant was are there not efficient/elegant alternatives to udevil ... that would preclude udisks2 and gvfs :)  The answer would be (to the best of my knowledge NO).

Where exactly does that leave it then?  PolKit to allow for click and mount in apps like Thunar require those as a minimum. Stick with something that is unsupported or go back to something that is not well received... tough choices
Title: Re: Light DM issues
Post by: statmonkey on September 29, 2014, 05:33:26 PM
Yes, I believed I mentioned a snail moving across the edge of a razor blade before.  It is a bit Gordian, in the knot sense.  I think you go with what is not well received and rely on the community to do it's magic.  I know of several people who are looking at the udevil stuff as well as some other alternatives and think once things settle something will "turn" up.  PolKit  :'( what a disaster imho.  I think polkit is going to mature but for now it's not what it should be.
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 05:38:22 PM
@statman,

Well said.. Time will tell...
Title: Re: Light DM issues
Post by: ozitraveller on September 29, 2014, 11:19:44 PM
'udevil' is currently unsupported, isn't it? Is there an alternative?

Just curious.


hehe .. just curious my a**

That is a very good question Ozi... I think of udevil as more of a static or config type application and see it as less of an issue as spacefm... of course I could be dead wrong.  And yes there are alternatives already installed that have been in place long before udevil .. udisks2 and gvfs

Already mentioned this elsewhere but I really would advise against udevil.  I think what ozi meant was are there not efficient/elegant alternatives to udevil ... that would preclude udisks2 and gvfs :)  The answer would be (to the best of my knowledge NO).

Where exactly does that leave it then?  PolKit to allow for click and mount in apps like Thunar require those as a minimum. Stick with something that is unsupported or go back to something that is not well received... tough choices


 ;D You just never know what will fall out until you shake all the trees.
Title: Re: Light DM issues
Post by: VastOne on September 29, 2014, 11:34:49 PM
So true Ozi and thanks for posting that!  :D
Title: Re: Light DM issues
Post by: VastOne on September 30, 2014, 08:09:59 PM
Does anyone know of anything other than SpaceFM using udevil? 

I do not...
Title: Re: Light DM issues
Post by: PackRat on September 30, 2014, 08:26:10 PM
I don't.

Is there an apt command you can use to see which packages have it as a dependency?
Title: Re: Light DM issues
Post by: statmonkey on September 30, 2014, 09:36:38 PM
Doesn't apt-cache depends do that?
Title: Re: Light DM issues
Post by: VastOne on September 30, 2014, 09:42:34 PM
^ I think that shows what it needs/conflicts with/suggests

I think it is

apt-cache show udevil
Title: Re: Light DM issues
Post by: statmonkey on October 01, 2014, 12:20:05 AM
Hmmm need to get up to date on my apt-fu thanks VastOne