Throwing this out there for discussion ... and hopefully a place of knowledge in case it happens to someone else

I did an update yesterday to the www/v-ger server that is home to secondary apps that supports VSIDO.  The update was to bring it to the 3.13 kernel and systemd and was done the same as I have done several other machines, nothing out of the ordinary debian apt-get install blah blah blah...

All went well until I rebooted to just a login screen... No X, just tty

I wanted to first eliminate a delay on the boot and knew the issue was a faulty swap setting in fstab and off to nano I went...

The first sign of 'dafuq is this? ' was trying to save fstab and being told that the file system was read only..  WELL NO SHIT!... I was su so whats the fucking problem?  ... checking around, I confirmed on everything I tried, the system was locked down.. I searched and found several things that could cause this and even ran a few things (remount of / and fsck) but nothing worked...

I went back to fstab on a hunch and found the issue.... There was no statement there for / at all!  This line had been totally removed:

/dev/sdb4 / ext4 relatime,errors=remount-ro 0 1

I put that back and the system booted to X immediately...

Looking back on the past couple of weeks, both jedi and I had similar issues where we did new updates and was faced with no X and just a login.  We both attacked it as a X / nouveau / nVidia issue on the update and nothing really solved my issues... I just got 'lucky' and fixed it with  the right settings of xorg.conf.

Now I am not so sure it had anything to do with luck or timing at all and that it may have been a systemd cycle (process) that was not completed and eventually did.  The only variable to all of the issues I have seen was adding systemd to a setup and then been met with no X and a login only.  Did Jedi and I both misdiagnose that these were X issues and not access issues? 

Open for debate and discussion...

• Implemented the default SID 3.13 kernel
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

A sad day today having just found out what happened in early January

We will miss you Crip, and will always appreciate and honor your work

• Implemented systemd
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Resolved a udevil installation  issue
• Implemented new Iceweasel Settings
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Updated to post Xorg deletion SID levels
• Corrected several conky settings
• Corrected the x64 ISO with correct smplayer
• Installed latest Pithos 0.3.18
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

xserver-common and xserver-xorg-core are trying to update in SID today ... you must stop this from happening or risk your system tanking...

If you do an dist-upgrade, those packages will update but you will not be able to boot to a DE login, only a tty1.  If you try to reinstall xorg, you will be met with:

fails due to depends on xorg-video-abi-14 but it is not installable

To get by this until it is resolved simply put xserver-common and xserver-xorg-core on hold like this:

sudo apt-mark hold xserver-common
sudo apt-mark hold xserver-xorg-core

And look back here until this is cleared...

EDIT - This has been cleared and resolved in Debian packaging

Run

sudo apt-mark unhold xserver-common
sudo apt-mark unhold xserver-xorg-core
sudo apt-get update && sudo apt-get dist-upgrade


and programming will resume back to normal channels

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Updated to latest SID kernel 3.12.9-1 (2014-02-01)
• Corrected conky width
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

Perl script for Xchat to show whats going on in Pithos

Save this to ~/.xchat2/pithosplayer.pl and make it executable

in xchat, run it as

/pit_play

#!/usr/bin/perl

## pithosplayer.pl
## Perl script for Xchat to show whats going on in Pithos


use strict;
use Net::DBus;

# Pithos XChat script
# (c) Copyright 2014 - VSIDO/VastOne>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

my $script_name        = "Pithos XChat";
my $script_version     = " 0.0.6";
my $script_description = "Displays the current Pithos playing song in XChat.";
my $bus = Net::DBus->session;
#check for Pithos on Dbus
pit_live();

# message string
my $playing ="is listening to"; #replace with your own message

Xchat::register($script_name,$script_version,$script_description,"");

Xchat::print("Loaded \002".$script_name.$script_version."\003:");
Xchat::hook_command("pit_start", "pit_live");
Xchat::hook_command("pit_play", "pit_play");

#print "/me utilise $script_name $script_version \n";

sub pit_play{
if (pit_run()){
my $service = $bus->get_service('net.kevinmehall.Pithos');
my $object = $service->get_object('/net/kevinmehall/Pithos', 'net.kevinmehall.Pithos');
my $info= $object->GetCurrentSong;
# hash keys are : album, artist, disc, length, title, track
# $info hash contains the keys value above. you can change below to display information you need. keep "me" (command will generate the slash).
Xchat::command "me $playing $info->{artist} - $info->{title} - from the album $info->{album} playing in Pithos";
}
}


sub pit_live{
my $localbus = Net::DBus->find;
my $localservice = $localbus->get_service("org.freedesktop.DBus");
my $localobject = $localservice->get_object("/org/freedesktop/DBus");
my $gtrouver=0;
  foreach (@{$localobject->ListNames}) {
    if (m/pithos/){
      Xchat::print "found pithos\n";
      $gtrouver=1;
      last;
    }
    }
 
}

sub pit_run{
my $localbus = Net::DBus->find;
my $localservice = $localbus->get_service("org.freedesktop.DBus");
my $localobject = $localservice->get_object("/org/freedesktop/DBus");
my $gtrouver=0;
  foreach (@{$localobject->ListNames}) {
    if (m/pithos/){
      #Xchat::print "found pithos\n";
      $gtrouver=1;
      last;
    }
    }
    unless ($gtrouver){
Xchat::print "You need to restart pithos use pit_start.\n";
}
  return $gtrouver;
}

Starting in this thread we talked about issues with tint2 and how it fails to work from the systray panel

@PackRat

I am still seeing issues where the  tint2 top right panel stops working... It does still work, for instance xchat blinks when there is a message, but no right or left click functions work at all on any of the icons.. in fact on a right click on the panel, I get the FB menu

I have moved it down to the bottom right and have not had an issue with it since...

I am beginning to think this has something more to do with FluxBox and it's layering than tint2... I do not use anything but Flux so it is hard for me to test it..  What would be nice is if the current setup could be tested in OB or any WM to confirm it fails on any of those

Any insight to this is appreciated

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Updated to latest SID kernel 3.12.8-1 (2014-01-19)
• Corrected tint2 systray setup
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

In the build processes of VSIDO this is the most frustrating part...

Take a look at the dist-upgrade below

Where does these new packages come from? Why are these packages suddenly needed and were not before? ... These new packages (the 89.1 MB of additional disk space will be used) translates to a 20 MB raise in the ISO from 380 to 400MB... I would like to know why and get thoughts from the brilliant minds we have here

I think it is a transitional phase between kernels perhaps? ... Thoughts please! 

The following packages will be REMOVED:
  spacefm-common
The following NEW packages will be installed:
  gir1.2-gtk-2.0 libatk1.0-dev libcairo-script-interpreter2 libcairo2-dev
  libdrm-dev libegl1-mesa-dev libexpat1-dev libfontconfig1-dev
  libfreetype6-dev libgdk-pixbuf2.0-dev libgl1-mesa-dev libgtk2.0-dev
  libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0 libice-dev libicu52
  libpango1.0-dev libpixman-1-dev libpng12-dev libpthread-stubs0-dev libsm-dev
  libx11-dev libx11-doc libx11-xcb-dev libxau-dev libxcb-dri2-0-dev
  libxcb-glx0-dev libxcb-render0-dev libxcb-shm0-dev libxcb1-dev
  libxcomposite-dev libxcursor-dev libxdamage-dev libxdmcp-dev libxext-dev
  libxfixes-dev libxft-dev libxi-dev libxinerama-dev libxrandr-dev
  libxrender-dev libxxf86vm-dev mesa-common-dev x11proto-composite-dev
  x11proto-core-dev x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev
  x11proto-gl-dev x11proto-input-dev x11proto-kb-dev x11proto-randr-dev
  x11proto-render-dev x11proto-xext-dev x11proto-xf86vidmode-dev
  x11proto-xinerama-dev xorg-sgml-doctools xtrans-dev
The following packages will be upgraded:
  acpid autopoint base-passwd colord cpp cpp-4.8 dictionaries-common dpkg
  dpkg-dev ffmpeg g++ g++-4.8 gcc gcc-4.8 gcc-4.8-base gettext gettext-base
  libasan0 libasprintf-dev libasprintf0c2 libatomic1 libaudit-common libaudit1
  libav-tools libavcodec55 libavdevice55 libavfilter3 libavformat55
  libavresample1 libavutil52 libbluray1 libcolord1 libcolorhug1 libcups2
  libdpkg-perl libffi6 libgcc-4.8-dev libgcc1 libgettextpo-dev libgettextpo0
  libgfortran3 libgomp1 libio-socket-ssl-perl libitm1 libnss-mdns
  libpam-modules libpam-modules-bin libpam-runtime libpam0g libperl5.18
  libportaudio2 libpostproc52 libquadmath0 libstdc++-4.8-dev libstdc++6
  libswresample0 libswscale2 libthai-data libthai0 libtsan0 logrotate lynx
  lynx-cur manpages manpages-dev perl perl-base perl-modules spacefm sudo
70 upgraded, 59 newly installed, 1 to remove and 0 not upgraded.
Need to get 72.6 MB of archives.
After this operation, 89.1 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Switched back to tint2 as default panel/launcher/systray
• Updated GMusicBrowser to 1.1.11
• Switched to SMPlayer and removed UMPlayer
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

For the last month, changes in Googles simple image search scripts had been broken and no longer usable in GMusicBrowser

Quentis Sculo (GMB dev) has now fixed that and added additional image search engines.  They are now ready in the git version of GMB, which is what is the default in VSIDO

To get the latest git version simply do this in terminal:

rm -rf ~/gmusicbrowser

get git-core

or

sudo apt-get install git-core

git clone http://github.com/squentin/gmusicbrowser.git

Done

The first rm of ~/gmusicbrowser is needed to clear what is already there so that git can recreate it

The second is to make sure git-core tools are installed

The third is to get the latest git version of GMB

The next versions of the ISO will have this installed already

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Added alias deps='apt-cache show
• Added apps ntp nptdate roxterm parted
• Added the following to vsido-welcome clipit bashburn keepassx numlockx
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

This is a thread to discuss individual apps that 'should' or 'could' be added to the application base

We have a really good base of apps that have hit the spot for a lot of people...

Occasionally we all run across something that is really good and should be considered for VSIDO.  The only requirements I will have is that it is light on dependencies and size

I'll start with one that I have known about and used forever... Grsync

It is light (200k) and is a gui frontend for rsync.  I use it all the time and I nominate it as a VSIDO default application

Quote from: PackRat on January 03, 2014, 07:12:38 PM
I didn't want to bog down the systemd thread, or start a new one - so feel free to copy-n-paste this somewhere in the forum.

For dual booters of VSIDO and Windows 7 (Vista, 8?) there is an issue with VSIDO resetting the hardware clock to UTC; Windows needs it at local time. I've had this happen on my desktop (AMD) and laptop (i3) which are currently both dual boot linux-win7. I've since put Slackware on my desktop.

During the install, I have to make sure that I select that the hardware clock is set to local time. VSIDO will install fine with that, but at some point will reset the hardware clock to UTC which messes up the Windows clock - VSIDO still shows the local time. It's a bit of a pain to get it reset correctly.

I don't know if this is something in Sid or the VSIDO installer, or if it can even be tracked down. I noticed ntp is not installed by default in VSIDO, maybe that would be a fix?

I live in the western hemisphere, so there is no real damage - Windows time is moved forward so I have no files living in the future. An easy fix would be to move my Windows time zone to the west and make DST changes manually.

Of course, the best fix would be for MS to change Windows so it understands UTC an timezones. How about you get Gates and Balmer on a conference call and line them out. 

PackRat sent me that in a PM and I think it should be addressed by all... I do not have any windows installs to test

On my installs I have always said no to 'installed to local time' question and have never seen an issue with it

Anyone else seeing anything like this?

@PackRat, does installing NTP resolve it for you?

Gates and Ballmer have not answered my calls since Raptor went live... 

PackRat originally started this discussion in the ScreenShot thread where he let us all know Siduction had moved to systemd

If debian goes with upstart,  I may have to will rethink everything.  I see no value in that move at all

I'll tear apart siductions implementation of systemd and see how they did it... perhaps engage with them on any pitfalls

Both ISO's were updated, built, installed, tested and uploaded today with no issues.

• Updated the kernel to Debian 3.12.6-2 (2013-12-29)
• Corrected WICD to include wlan0 as the default
• Removed a broken Iceweasel Add On
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page

Both ISO's were updated, built, installed, tested and uploaded today with no issues

• Updated the kernel to Debian Sid 3.12.6-1 (2013-12-21)
• Corrected the default theme
• Updated bash_aliases
• Updated SpaceFM setup of Bookmarks
• Updated all applications to the latest SID levels

All files and torrents can be downloaded from the VSIDO Download page