Usually run that script from a terminal. I've used key binding as well.

It works if the shebang is removed; changing it to #!/bin/sh produced the message.

No change in touchpad, but do a message now:

syndaemon: no process found

I'll try some more later - kids out of school early today; got to run.

With my latest clean install when VSIDO switched to systemd -- 2-3 iso builds ago?

The individual commads work just fine; so I just made some new key bindings.

The script itself no longer works. Not even for root user. No messages in the terminal when running the individual commands - the touchpad comes on/off though.

Systemd is the only real change; but like you I can't figure out why that would matter.

I run VSIDO on my HP2000 laptop. I only use the touchpad when I absolutely have to and normally go with a usb wireless mouse (inserting shameless plug for logitech here).

In Debian testing/sid and VSIDO I always used the following script to toggle the touchpad off/on:

#!/bin/bash
pgrep syndaemon &>/dev/null; [ $? = 0 ] && killall syndaemon &&

if [ $(synclient -l | grep TouchpadOff | awk '{print $3}') == 1 ] ; then
synclient touchpadoff=0;
else
synclient touchpadoff=1;
fi


Up until the recently, this script has always worked. I can issue the individual synclient commands in a terminal and toggle the touchpad on/off, but the script just fails without an error message. The script is executable.

My guess is that this is the result of the switch to systemd, but I can't see where the script would need to be modified to account for that.

Anyone else suddenly have issues with bash scripts no longer working?

If you're an advanced user and minimalist, tiny core is good distro.

I would search their forums for your particular eeepc; or post the specs their to see if someone is using it.

With minimal distros like tiny core (slitaz, crux) having all your hardware work out of the box may not be an option - be prepared to search for and install some drivers.

Iceweasel (I think there is another thread about it) and synaptic are typical culprits.

I've always attributed it to a fluxbox-gtk3 issue; never really pursued a fix.

Quote from: VastOne on April 02, 2014, 03:10:13 AM
The thing is, when is SID unstable?  6 years using it now and I can count on two fingers how many times it has borked...

Wait!  One finger, my middle one!  It was Perl Jam I and Perl Jam II that caused both

perl has a shitty way of blind siding all other apps in updating with little or no warning

#! is what it is... something I could never go back to

Never had the issue with perl, the only time I've had sid or testing spontaneously bork was when some gnome library wasn't updated with the rest of gnome. On the other hand, I wish I had a US dollar for every time I managed to bork it.

Welcome back cobaltwolfe.

Have you tried changing the gtk and fluxbox themes from the defaults? I sometimes have the same issue with apps other than steam (which I have never used) and it's usually resolved when I change the themes.

Nice shots.

I was messing around with a drop-down terminal for a couple days; I can see how that would be become a standard setup.

Simple maroon(ish) and gray fluxbox style -

Lindsey Stirling - Transcendence.

Searched out this video in particular because her backing orchestra is a group called Landfill Harmonic - a bunch of impoverished teens from Paraguay who make their own instruments out of trash from the local landfill.

http://www.youtube.com/watch?v=DHdkRvEzW84#

Warning - the last minute and half of the video is promotional stuff for her upcoming album and tour

Have you seen the aurora australis?

The furthest south I've seen the aurora borealis is in Nevada about 120 miles (200 km) north of Las Vegas. That far south it's usually just a red glow.

The sauna thing is very popular in Minnesota and other states around the the Great Lakes where there is a large population of Scandinavian decent. Common to see the Northern Lights there as well.

Enjoy -



Direct link -

http://s28.postimg.org/5z22nztp9/black_pine_image.jpg

Added tabbed windows to Fvwm - work on the colors next:

^ cool

fvwm, CPAN -

Does gdebi write a log file - in /var/log/ maybe? Or can it be configured to do so, then  double-click a deb file.