I get that and I'm not blaming IgnorantGuru for the being fed up with the bs, but still this whole mutex issue seems just sloppy, maybe that is just due to a lack of understanding?   

Honestly, I didn't live with 4pane that long, I discovered spacefm shortly after I tried it and being a photographer the thumbnails made the choice easy.  This probably could answer any questions about 4pane.  http://www.4pane.co.uk/manual/Contents.htm

Personally I'd rather ditch debian than let them break spacefm, but I feel like I should mention 4pane which is a strong runner up to spacefm, it only loses due to its lack of visual effects like thumbnails.

Quote from: orbea on September 20, 2014, 11:50:36 PM
maybe I just need to reboot to break it...

Yep... 

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...

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...

Thanks for the thought, I've been bashing my head against this on and off ever since I installed vsido a few weeks ago, thankfully my #! with sid is not experiencing any of this outside of the occasional 404s, but then I also didn't install that during all this release upheaval.  The lightdm issue doesn't bug me personally as much as I've been meaning to give just xinit a go for a while and if I get tired of that I've been wanting to try cdm.

Nope, I don't have java-8, i tried installing it the other day to see if that helped, but as it didn't I removed it again...

Quote from: 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

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

I'm fully updated minus "live-config-sysvinit" which needs the dpkg issue resolved.  If I full remove openjdk-7 openjdk-6 gets automatically selected for installation and vica versa, both have the same issues, openjdk-8 too....

Did you install the xinit package?  I was surprised when I noticed vsido didn'thave xinit by default which has startx.

So whenever I try to dist-upgrade i get stuck at:

Setting up icedtea-netx:amd64 (1.5.1-1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group itweb-settings is broken
update-alternatives: warning: not replacing /usr/share/man/man1/itweb-settings.1.gz with a link
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/itweb-settings because link group itweb-settings is broken
update-alternatives: warning: not replacing /usr/share/man/man1/itweb-settings.1.gz with a link
update-alternatives: error: alternative path /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/javaws doesn't exist
dpkg: error processing package icedtea-netx:amd64 (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
icedtea-netx:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

If I purge icedtea-netx I get:

The following packages will be REMOVED: 
  alsa-base{p} console-tools{p} libappindicator1{p}
  libass4{p} libavcodec54{p} libavcodec55{p}
  libavdevice55{p} libavfilter3{p} libavfilter4{p}
  libavformat55{p} libavresample1{p} libavutil52{p}
  libavutil53{p} libbind9-80{p}
  libcairo-script-interpreter2{p} libcolord1{p}
  libcolorhug1{p} libdb5.1{p} libdbusmenu-glib4{p}
  libdbusmenu-gtk4{p} libdirac-decoder0{p}
  libdns88{p} libdns99{p} libexiv2-12{p}
  libfftw3-long3{p} libgconfmm-2.6-1c2{p}
  libglademm-2.4-1c2a{p} libgphoto2-2{p}
  libgphoto2-port0{p} libgssglue1{p}
  libharfbuzz-gobject0{p} libharfbuzz0a{p}
  libhdb9-heimdal{p} libindicator7{p} libisc84{p}
  libisccc80{p} libisccfg82{p} libkdc2-heimdal{p}
  liblcms1{p} libllvm3.3{p} liblognorm0{p}
  liblwres80{p} libmagick++5{p} libmagickcore5{p}
  libmagickwand5{p} libmbim-glib0{p} libmozjs27d{p}
  libmozjs28d{p} libnfsidmap2{p} libopenjpeg2{p}
  libpackagekit-glib2-16{p} libparted0debian1{p}
  libpcrecpp0{p} libpostproc52{p} libprocps1{p}
  libpython3.3-minimal{p} librtmp0{p}
  libspice-server1{p} libsqlite0{p}
  libswresample0{p} libswscale2{p} libtcl8.5{p}
  libtiff4{p} libtirpc1{p} libvidstab0.9{p}
  libvorbisidec1{p} libvtv0{p} libx264-133{p}
  libx264-140{p} libx265-13{p} libx265-21{p}
  libx265-25{p} libx265-7{p} libxatracker1{p}
  nfs-common{p} pcmciautils{p} python3.3{p}
  python3.3-minimal{p} rpcbind{p} sysvinit-core{p}
  tcl8.5{p}
0 packages upgraded, 0 newly installed, 81 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]

and reinstalling icedtea-netx:

$ agi icedtea-netx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  icedtea-netx
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/24.5 kB of archives.
After this operation, 156 kB of additional disk space will be used.
Selecting previously unselected package icedtea-netx:amd64.
(Reading database ... 122234 files and directories currently installed.)
Preparing to unpack .../icedtea-netx_1.5.1-1_amd64.deb ...
Unpacking icedtea-netx:amd64 (1.5.1-1) ...
Processing triggers for man-db (2.6.7.1-1) ...
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas how to fix this?

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...

$ 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...