Fatdog64-700/701 [April 22 2015] [CLOSED]

[Atle]

I am not sure what went wrong here.

When trying to start skype from terminal i get these error messages.

Please see the attached image for details of error message.

Skype is in the start menu, but nothing happens when i start skype from there.


atle

[smokey01]

Looks like you need to load the 32bit libraries in Gslapt.

what version of Skype are you using?

[Atle]

Hi and thanks for the quick response...

I use the latest Fatdog 700 with skype-4.3.0.37.sfs from the SFS Manager.

I did the same installation of the very same system at my home PC and it worked all fine. This is a Dell Inspiron 5423.

Atle

[Atle]

I did not try the other version of skype as i believe it does not work anymore. but on the other hand, i guess it would not be there is that is the case so i test that first and report.

EDIT.. tested the other version of skype, the 4.2 one and that did not work.

I did look for some library in Gslapt, but did not find anything that looked like the right thing.

But there are some 32 bits library options in SFS Manager for QT and Slacko(?).

I am not sure what to try then

[smokey01]

Load the slacko 32bit libs.

[Semme]

Not on 700 atm, but I recall "compat" in the package name.

[Atle]

Thanks... loaded the slacko library and it all works GREAT now...

[jamesbond]

@Yoliano - 1,2,3 - don't bother to test. I just tested on my own and found the problem - it was a timing problem as I suspected (don't want to bore you with the details unless you're interested). Install the latest fatdog-update from gslapt and it should be fixed - if not, let me know.
4 - clock settings (on the panel) - right click and choose "configure". Hardware clock UTC/Localtime should have no impact on display.
5 - my build or smokey01 build is equally well (they came from the same source code), so use whatever works for you. smokey01 kindly built and packaged psip for many versions of puppies over the years, fatdog included.

@terrapin231 - Both eztables and aovfirewall are scripts that run once at boot and then stopped. They configure the kernel firewall, and once done they quit - but the firewall in the kernel will continue running invisibly. I "tweaked" eztables to give the impression as if it is running all the time (response to questions to Aung - page 7 of this thread), but actually it isn't. I didn't do the same tweak to aovfirewall as I want to keep as close to original as possible; and because it is much less configurable --- I am making the assumption that anyone using it would be very familiar with iptables if they want to change anything.

To see if the firewall is up, type this in terminal: "iptables -L -v | wc -l". If your result is a lot more than 10 (say, 50 or 60 over) the firewall is up and running. Fatdog 600 has a firewall status icon, perhaps it is time I do one for 700 too.

@prehistoric - thanks for the update. Looks like the problem is in the kernel then. Nothing much we can do until we go for a newer kernel.

[Semme]

Any chance someone could put together a go-mtpfs pkg?

[step]

@smokey01, all is well with your repo now.

[01micko]

Any chance someone could put together a go-mtpfs pkg?

No. It didn't work well with FD64-600 series plus is a prebuilt binary, and pretty much undeveloped for a while so may well suffer bitrot.

Better to go with libmtp and simple-mtpfs (in the fd64-700 repo). Get those installed and reboot (so udev loads the rules).

Here is a script to try, use at own risk.

Code: Select all

#!/bin/sh
sync

TMP=/tmp/mtp_devices$$

splash() {
	MSG="$1"
	[ "$2" ] && T=$2 || T=2 
	yaf-splash -placement top -transparent -timeout $T \
	-font "-misc-dejavu sans-bold-r-normal--16-0-0-0-p-0-iso10646-1" \
	-text "$MSG" 
}


NUM=`simple-mtpfs -l 2>/dev/null|grep '^[0-9]'|wc -l`
[ -z "$NUM" -o "$NUM" = 0 ] && splash "$(gettext "No device found")" \
&& exit

TITLE=$(gettext "Browse Your Phone")
v=0.1

if [ "$NUM" -gt 1 ];then
	simple-mtpfs -l 2>/dev/null > $TMP
	export MAIN_DIALOG='<window title="'$TITLE' '$v'">
		<vbox space-expand="true" space-fill="true">
			<text><label>'$(gettext "Choose the phone or device you wish to browse.")'</label></text>
		<vbox space-expand="true" space-fill="true">
		<frame>
			<tree column-header-active="false" column-resizeable="false">
				<label>'$(gettext 'Device')'</label>
				<variable>SELECTION</variable>
				<width>400</width>
				<height>150</height>
				<input>cat '"$TMP"'</input>
				<action signal="button-release-event">exit:chosen</action>
				<action>echo "The chosen item is '$LIST'"</action>
			</tree>
		</frame>
		</vbox>
		<hbox>
			<button cancel></button>
			</hbox>	
		</vbox>		
	</window>'
	eval `gtkdialog --program=MAIN_DIALOG`
	case $EXIT in
		chosen) DEV=`echo "$SELECTION"|cut -d':' -f1`
				NAME=`echo "$SELECTION"|cut -d' ' -f2`
				echo "You chose $DEV $NAME";;
		*)exit ;;
	esac
else
	DEV=`simple-mtpfs -l 2>/dev/null|grep '^[0-9]'|cut -d':' -f1`
	NAME=`simple-mtpfs -l 2>/dev/null|grep '^[0-9]'|cut -d' ' -f2`
fi

DEV_MTPT="${HOME}/${NAME}_mtpt"
[ -d "$DEV_MTPT" ] || mkdir $DEV_MTPT

MTMSG="$(gettext "Mounting")"
FAILMSG="$(gettext "Failed to mount")"
UMTMSG1="$(gettext "Unmount")"
UMTMSG2="$(gettext "by right clicking and choosing 'Unmount' in Rox file manager")"
splash "$MTMSG $NAME" #& #fork
# mount it
simple-mtpfs --device $DEV "$DEV_MTPT" 2>/dev/null
RV=$?
if [ "$RV" -ne 0 ];then 
	splash "$FAILMSG $DEV_MTPT"
	echo "$FAILMSG $DEV_MTPT :code: $RV"
	rm $TMP 2>/dev/null
	exit $RV
fi
rox -s $DEV_MTPT
rox -x $DEV_MTPT #refresh so green dot shows
splash "$UMTMSG1 $DEV_MTPT
$UMTMSG2" 5
rm $TMP 2>/dev/null
exit $RV

Name it 'mount_phone' or something, put it in $PATH (maybe /usr/local/bin) and execute from cli or drag to desktop and set an icon for it.

It makes the mountpoints in $HOME, so *should* be multiuser friendly (not tested) and will handle 2 devices at once, but better to try one for now.. As said use with caution, I can't guarantee it won't erase data or something silly. That said, it works for me with a sammy i9192 and a nexus7 2012.

The script does not autostart, it is not setup to do that through the udev-rules, but you know when you plug in your phone, right?

[Judes]

Just tried the new Quirky 64bit by Barry and it runs way better than Fatdog64?

Is there any reason that i might be missing to favour Fatdog over quirky 64?

[terrapin231]

@jamesbond

Both eztables and aovfirewall are scripts that run once at boot and then stopped...I am making the assumption that anyone using it would be very familiar with iptables if they want to change anything.

Thanks jamesbond. I'm not familiar with iptables I've been happy to run with the built-in firewalls in the previous puppy distros I've used, without tinkering - but needed the reassurance of the firewall-running-tray-icon - only reason I ended up fiddling with eztables and aovfirewall in FD64 700. So...

Fatdog 600 has a firewall status icon, perhaps it is time I do one for 700 too

I'm sure this would certainly be of assistance/reassurance to novices such as myself.
As per your suggestion, I ran:

Code: Select all

iptables -L -v | wc -l

and got "60" so aovfirewall script would appear to have configured iptables okay - I altered aovfirewall.conf using example in aovfirewall.conf.examples to reflect my needs (I think/hope )

Code: Select all

# For a desktop computer directly connected to Internet, an IP address
# dinamically assigned by a DHCP server (as the ones in ADSL routers) on a
# wireless connection, that have an smtp server and do ocassional BitTorrent
# connections:

ALLOW_TCP="ssh smtp 6881:6889"
ALLOW_UDP="domain"
LIMIT_5MIN="ssh"
FORWARDING=0
NAT=0
DHCP=1
ALLOW_NET=""
IFACE=wifi0 

As a novice, the only reason I chose aovfirewall, is that the script appeared to offer the fastest route to configure iptables to my home setup/use. If eztables essentially offers the same thing, with minimal .conf editing, then I'd be happy to return to eztables. But perhaps there's little point as aovfirewall script appears to be working? Happy to take on board any further thoughts you may have on this.

Thanks again!

[Yoliano]

@smokey01

Thanks for your correction. I followed your instructions for Gslapt and now have Psip v.1.4 installed and configured. I have tested it on 2 live calls and it is working perfectly. But to get it to register with my VoIP server I have to disable the Eztables firewall. Not unexpected, but a considerable nuisance, because I find I cannot disable Eztables in the same session,but need to reboot. So I am interested in how to bypass this problem.

I used Ekiga for several years before Psip appeared and from this experience I know that I have Symmetric NAT. So it is fairly certain that I need to forward ports for Psip for NAT traversal. I already have Port 5060 UDP forwarded in my router. But please advise what other ports are required for Psip.

I understand that forwarding ports from the router simply opens the router firewall for Psip traffic. So I assume that I will have to configure Eztables to do the same. Please confirm if that is correct.

Thank you for your most generous help. I am extremely pleased to have Psip up and running in 700 and so quickly. Thanks again.

@jamesbond

Thank you for your "magic" adjustment of the timing problem. I followed your instructions and all is now OK. Time display is continuous through reboot and ntpd-client is starting at boot. Problem solved as a result of your rapid and skillful attention. Many thanks indeed for all your help.

You will see from the above that I am on the home run with Psip. Thank you also for your most generous help and for this very efficient and effective software.

[smokey01]

@Yoliano,
You shouldn't have to do any port forwarding to get Psip to work, I don't anyway. Sometimes it may be necessary to disable ALG in your router especially if you are doing P2P.

In Eztables you might need to open ports 5060 - 5069. Psip seems to use more than just port 5060.

Personally I don't bother with a firewall in Fatdog or any other Puppy for that matter. The hardware firewall in the router seems to to a pretty good job, well it has so far anyway.

I did write a little script some time back that toggles the firewall on and off. I never had to do a reboot when using it. If you convert it with "Convert to new Package Format" and install it, it should work but use at your own risk as I have not tested it.
http://smokey01.com/software/network/tfw-1.0.pet

@smokey01

Thanks for your correction. I followed your instructions for Gslapt and now have Psip v.1.4 installed and configured. I have tested it on 2 live calls and it is working perfectly. But to get it to register with my VoIP server I have to disable the Eztables firewall. Not unexpected, but a considerable nuisance, because I find I cannot disable Eztables in the same session,but need to reboot. So I am interested in how to bypass this problem.

I used Ekiga for several years before Psip appeared and from this experience I know that I have Symmetric NAT. So it is fairly certain that I need to forward ports for Psip for NAT traversal. I already have Port 5060 UDP forwarded in my router. But please advise what other ports are required for Psip.

I understand that forwarding ports from the router simply opens the router firewall for Psip traffic. So I assume that I will have to configure Eztables to do the same. Please confirm if that is correct.

Thank you for your most generous help. I am extremely pleased to have Psip up and running in 700 and so quickly. Thanks again.

@jamesbond

Thank you for your "magic" adjustment of the timing problem. I followed your instructions and all is now OK. Time display is continuous through reboot and ntpd-client is starting at boot. Problem solved as a result of your rapid and skillful attention. Many thanks indeed for all your help.

You will see from the above that I am on the home run with Psip. Thank you also for your most generous help and for this very efficient and effective software.

[jamesbond]

@Yoliano - glad to hear everything works for you. As for psip, you'd better listen to smokey01. I may be the author of psip but smokey01 is the regular user and tester; he knows a lot more tricks to get it going than myself.

@terrapin123 - Both eztables and aovfirewall do exactly the same thing, so if aovfirewall works for you then there is no need to switch to eztables. The only reason eztables is the default, is because I think is a bit more configurable.

@01micko - thanks for that MTP script!!!

[Yoliano]

@jamesbond

I want to install the Spotify software for Linux, which I have downloaded, but all three elements are .deb files. I have read your posts of March 26 and April 1 on P24 of this thread. Also, I have checked that your deb2txz script is already present in usr/bin, (I have the latest update). In my ignorance my problem is that I don't know how to exploit it from the command line. Please be kind enough to explain and to give the syntax of the commands. Sorry to trouble you with this request, but I don't fully understand what you have written in your posts.

Thanks.

[step]

@jamesbond

I want to install the Spotify software for Linux, which I have downloaded, but all three elements are .deb files. I have read your posts of March 26 and April 1 on P24 of this thread. Also, I have checked that your deb2txz script is already present in usr/bin, (I have the latest update). In my ignorance my problem is that I don't know how to exploit it from the command line. Please be kind enough to explain and to give the syntax of the commands. Sorry to trouble you with this request, but I don't fully understand what you have written in your posts.

Thanks.

1. Start ROX-file manager and navigate to the folder where you keep the deb archives.
2. Open another folder and navigate to /tmp
3. Drag-drop the deb archives from folder 1 to folder 2 and select "copy"
4. Close folder 1, leave folder 2, /tmp, open.
5. Start a command-line console window and type:

Code: Select all

cd /tmp
deb2txz NAME-OF-FIRST-ARCHIVE.deb
deb2txz NAME-OF-SECOND-ARCHIVE.deb

Replace NAME-*.deb appropriately. Run deb2txz on all the deb archives, one at the time.
6. Assuming no error messages (there may be warnings, those are OK), go back to folder 1 in ROX-filer. You should see icons for the original .deb files still there, and new icons for .txz files. For instance, NAME-OF-FIRST-ARCHIVE-DEB.txz.
7. Right click each new icon and select "install".

If installing works out you can try running spotify. I'm incompetent to help you with that. But I suggest you try to run it from a command-line console window, so you can see error messages.

[jackluminous]

--- Also, Acer Aspire ES1-512 trackpad not working so using a usb mouse. Trackpad works in Mint so just needs the driver?

Has this ever been resolved so that the trackpad cab be used?

I have the exact same laptop and when I boot Fatdog the desktop appears ok but there is NO control over the mouse which just stays in the middle

I recently used Knoppix 7.2 which recognises the trackpad/mouse and is usable

[kirk]

jackluminous,

Use the Gslapt package manager to install libinput and xf86-input-libinput and then restart X. Libinput is used for Wayland input devices and xf86-input-libinput is a wrapper so Xorg-server can use it. It does not have all the options that the Xorg Synaptics driver offers, but it's better than nothing. On my laptop using libinput tap to click is disabled and two finger scrolling is enabled. I've read that some distros are shipping libinput by default.