Bluetooth starting file is and has been in /etc/init.d...do you mean something else ?1) your bluetooth start-up file (that lives in /root/Startup) is missing
I believe the pet really overwrites some existing files. It has been packaged and tested by stu90. I dont have working bluetooth system so I cant much test it. Of course I could inspect the overlapping files but...if it works...2) when I downloaded .5 bluetooth pet, for the first time in my dpup try-outs, it warned me of copying over libs. I knew I needed .5, so I went ahead and installed. But the file is necessary, and you don't want to scare off new users and bluetooth. Maybe this pet should come pre-installed
I believe Jemimah could answer better to that problem. You could pm her ? And if you get working solution...please post the procedure here.3) fn brightness works, but with no on-screen scale (similar to volume control). I don't mind, but is a file missing (the way volup, etc was missing from previous version)?
Well...that is the best part of puppy land. You can find working solution from other puppy. There is so many kind hardware and needs that several puppies complements each other...There is official Puppies for older hardware and so on... I cant much use Racy because the xorg does not like my touchpad. The same problem with Saluki and also with Precise Pangolin...which has Barrys compiled xorg-server:I hadn't realized that Racy 5.2.2 had a 3.07 kernel, so I tried that out. Racy saw my router, but couldn't connect, nor was the ClickPad fully functioning. My xorg re-config crashed Racy.
Somewhere in this compile happened the same kind intolerance to my touchpad which affects Racy and Saluki. So...I stick with Dpup. It supports my hw perfectly.There were some issues, such as the xorg-server segfaulting, so I recompiled it, used version 1.11.4 instead of 1.11.3 used by Ubuntu.
It seems to be gtk-theme related..whether you see the changing selected box or not. Nodoka themes shows the selected box alright. Aurora doesnt. So....it might be better to change the default theme for next version...sniff...Strange for me, the PupShutdown does not accept keyboard.
I pressed the power-button, the PupShutdown dialog arises, but it cannot be managed by the keyboard.
PupShutdown-1.8.1shinobar wrote:Strange for me, the PupShutdown does not accept keyboard.
I pressed the power-button, the PupShutdown dialog arises, but it cannot be managed by the keyboard.
pemasu wrote:It seems to be gtk-theme related..whether you see the changing selected box or not. Nodoka themes shows the selected box alright. Aurora doesnt.
Great. Both works fine. With keyboard:radky wrote:PupShutdown-1.8.1
-Added keyboard shortcuts for the eight standard shutdown options: Alt+P (Power-Off), Alt+R (Reboot), Alt+L (Log-Out), Alt+S (Lock Screen), Alt+X (Restart X), Alt+W (Restart WM), Alt+T (Manage Task) and Alt+F (Backup Files).
Updated the pet (timestamp 14:19:09). Only the file /etc/acpi/actions/acpi_poweroff.sh to be configurable the behavior.pemasu wrote:Thanks Shinobar. I will test.
Skipping the dialog is preferable for the keyboard-less systems. I frequently use Puppy for the keyboard-less monitoring systems in manufacturing factories. Boot from USB flash, no HDD, and no saving back thanks to the pupsaveconfig.#!/bin/sh
# Patriot Jan 2009 for Puppy Linux 4.1.1 GPL
# Revision 0.0.6
# 13sep09 dialogbox by shinobar
# 4nov09 TIMELIMIT 30sec
# 26dec09 wmpoweroff, adjustable less than 10sec.
# 4apr2012 shinobar: PupShutdown with time limit
TIMELIMIT=60 # in second, 0: eternal wait, negatives: skip dialog
SOUND="/usr/share/audio/bark.au"
PLAY="aplay"
[ -f "$SOUND" ] && which $(basename $PLAY) >/dev/null && $(basename $PLAY) "$SOUND"
#echo "DISPLAY=$DISPLAY" >> /root/acpi.log
X_pid=`ps ax | awk '{if (match($5, "X$") || $5 == "X") print $1}'`
if [ "$X_pid" != "" ]; then
#if [ "$DISPLAY" != "" ]; then
[ $TIMELIMIT -ge 0 ] && [ -x /usr/local/PupShutdown/PupShutdown ] && P="/usr/local/PupShutdown/PupShutdown $TIMELIMIT"
[ "$P" = "" ] && P=wmpoweroff
else
P=poweroff
fi
exec $P
Code: Select all
# 4Apr2012 shinobar: tieout
[ $TIMEOUT -eq 0 ] && exit
for I in $(seq $TIMEOUT); do
sleep 1
pidof PSD-bin &>/dev/null || exit
done
wmpoweroffThe brightness scale only works on the EEEPC, which sends acpi events when you changes the brightness. With other machines the kernel changes the brightness silently and AFAIK there's no easy way to know from a script when it happens or how bright it is.pemasu wrote:I believe Jemimah could answer better to that problem. You could pm her ? And if you get working solution...please post the procedure here.3) fn brightness works, but with no on-screen scale (similar to volume control). I don't mind, but is a file missing (the way volup, etc was missing from previous version)?
Right. Was missing:pemasu wrote:I have tested now PupShutdown-timeout-20120404.pet. It seems that from script /etc/acpi/actions/acpi_poweroff.sh the part: && P="/usr/local/PupShutdown/PupShutdown $TIMELIMIT"
does not carry the TIMELIMIT value to the modified script: /usr/local/PupShutdown/PupShutdown.
Code: Select all
TIMEOUT=$1 # 5Apr2012 shinobar: timeout# 5Apr2012 shinobar: timeout
...
TIMEOUT=$(echo $TIMEOUT| tr -dc '0-9-')
[ "$TIMEOUT" ] || TIMEOUT=0
Code: Select all
PSPEFD="`ps -C pup_event_frontend_d | grep 'pup_event_front' | grep -v 'defunct'`"
done
sleep 0.2
killall enlightenment
syncTmanjim3630 wrote:Tman thanks for the help. on this startup of ff and closing problem is gone.Tman wrote:Jim, try modifying /usr/local/bin/defaultbrowser to the following:jim3630 wrote: only issue is firefox when reopen gives error msg ff is already running.And then create an icon entry for defaultbrowser, or just type it in the terminal.Code: Select all
#!/bin/sh yaf-splash -bg red -fg white -placement center -timeout 2 -text "loading.." & killall firefox 2> /dev/null sleep 0.3 exec /usr/lib/firefox/run-mozilla.sh /usr/lib/firefox/firefox "$@"
this has happened in the past with other pups but don't recall why occurred.
will keep your fix saved away.
