Page 144 of 189

Posted: Sat 28 Apr 2012, 22:05
by Brown Mouse
greengeek wrote:
When I try to boot from the usb stick I have loaded Saluki onto (regardless of whether I selected "save to file" or "save to partition") the system will not boot on the first attempt. It will hang forever showing:

SYSLINUX 4.05 EDD 0x4f131b2f Copyright (C) 1994-2011 H Peter Anvin et al.
I see the same thing when booting Lucid 528-05 from an sdhc on my Acer Aspire one netbook.

Posted: Sat 28 Apr 2012, 23:36
by Geoffrey
Karl Godt wrote:(One note about thunar : Thunar uses a trash dir , so i was having problems deleting files larger than the remaining free space in the pupsave-file)
Yes, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.

Posted: Sat 28 Apr 2012, 23:51
by Karl Godt
Geoffrey wrote:
Karl Godt wrote:(One note about thunar : Thunar uses a trash dir , so i was having problems deleting files larger than the remaining free space in the pupsave-file)
Yes, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.
I finally opened a terminal in these trash directories and did a

Code: Select all

rm *
rm .*
cd ..
rmdir *
rmdir .*
to solve this manually

Posted: Sun 29 Apr 2012, 00:13
by greengeek
Karl Godt wrote: Could you please post the output of the

Code: Select all

locale

Code: Select all

locale -a

Code: Select all

locale -m
commands ?
Hi Karl, I have now edited my previous posts to clarify that I was selecting Australian English (ok I am in NZ but I figured that Puppy is an Aussie creation so was hoping I would have less problems by selecting their locale... :-) )

I have attached pics of the locale outputs (sorry I don't know how to save data from a terminal yet..

Posted: Sun 29 Apr 2012, 00:31
by Karl Godt
Yep, greengeek looks pretty OK i think ...

I have absolutely no idea about the different en_EN differences, just had heard there are different scottish dialects in australia ..

and that the neccessary and necessary programms programs ..

If you are running on USB with save to entire partition, could you post the output of the

Code: Select all

mount
command ?

(you could use the mouse left clicking holding the button and move the cursor over the output of the console, release the left button, and middle click to paste it into an empty sheet of an editor and do the same to copy from editor to the inputbox of the browser)

Posted: Sun 29 Apr 2012, 02:13
by greengeek
jemimah wrote:Is it fixed in 21?
Version 21 gives me a slightly different result. It does not reboot into X, but just reverts to a command prompt after the saving process. However, I still have to do a hard shutdown to get out of this state.

Posted: Sun 29 Apr 2012, 03:08
by greengeek
Karl Godt wrote:If you are running on USB with save to entire partition, could you post the output of the

Code: Select all

mount
command ?
OK, I have taken a shot of the mount command in the "fresh boot" state (first boot after hard reset) and also the "loop boot" state (when the shutdown procedure has auto rebooted in error).
(Sorry I couldn't do the middleclick trick till I get a mouse attached)

debugging tool

Posted: Sun 29 Apr 2012, 05:48
by shinobar
greengeek wrote:Version 21 gives me a slightly different result. It does not reboot into X, but just reverts to a command prompt after the saving process. However, I still have to do a hard shutdown to get out of this state.
Yeah, I could reproduce your problem under the locale 'en_US' (left as the default). I think the locale does not affect.
I think your problem is the saving to the partition specific. Or, saving to the partition on the flash, that is PUPMODE=7. Maybe recent woof bug.
I suspect the shutdown problem occurs every PUPMODE, but with different appearance.

Attached the rc.shutdown for debugging for whom the shutdown problem concern. Install the PET. You are warned because it will replace the existing /etc/rc.d/rc.shutdown, but proceed. Shutdown or reboot. The console gives prompt with '?'. Press [Enter]-key to proceed.
As for the PUPMODE=7, greengeek's case,press [S]-key at only one place where you are offered to skip.
at shutdown wrote:Sakuji is now shutting down...
Saving ... ... Done.
Cleaning up some temporary files. OK?
Cleaning up some temporary files... Done.
Unmount stray filesystems?
Unmounting stray filesystems... Done.
Swapoff?
Swapoff... Done.
Kill bad PID's? ('s' for skip) s
Remount SAVE_LAYER?
Remounting SAVE_LAYER ...Done.
Umount ntfs?
All done. Goobye?

respawn

Posted: Sun 29 Apr 2012, 06:12
by shinobar
jemimah wrote:The only reason it would restart X that I can think of, is if it's killing the shell (or logging off) on tty1. If that shell dies, mingetty will respawn it, and rerun /etc/profile.
Short exercise:
Go down to the console, type:

Code: Select all

kill -KILL $$
Its killing myself. logging out and auto login.

Code: Select all

rm -fr /tmp/*
kill -KILL $$
Coming back the desktop because the flag '/tmp/bootcnt.txt' was cleared.
Reasonable.

Test with the debugging tool:
Well, I reproduced the greengeek's case (USB flash install, save the session to the partition). Used the firstrun-debug-shutdown, and foud that the rc.shutdown kills its parent 'reboot'(or 'poweroff') and itself at the last stage. I don't know why, but maybe woof bug. It occurs PUPMODE=7 on saluki-21 but maybe all recent Puppies. I don't know about PUPMODE=6 (save the session in the internal HDD partition). I am not sure if it is related with PUPMODE=2 (Sage's case).
I also suspect that similar case can occur under PUPMODE=5 and/or under other cases, somewhere in the script rc.shutdown.

As for the position of deleting /tmp/*, as greengeek reported. it relates coming up the desktop or not when this happens.

Posted: Sun 29 Apr 2012, 07:36
by Sage
Anyone interested in comparing a copy of rc.shutdown with rc.shutdown.pupdev ? Who instigated the latter? Is it self-generating? Although I do not follow the above detail concerning code, I did find what works and what does not work, at least for a FULL - seems that it must contain the audit trail for the coding fault?

rc.shutdown.pupdev

Posted: Sun 29 Apr 2012, 08:09
by shinobar
Sage wrote:Anyone interested in comparing a copy of rc.shutdown with rc.shutdown.pupdev ? Who instigated the latter?
The rc.shutdown.pupdev is a document text. It does nothing as a script. Nothing do results hard-shutdown in some meaning.
I am very interesting if you report the result of the firstrun-debug-shutdown-2.2.1.pet. We can see, by the test, where it fails.

Posted: Sun 29 Apr 2012, 08:13
by shelezyaka
Karl Godt wrote:
Geoffrey wrote:
Karl Godt wrote:(One note about thunar : Thunar uses a trash dir , so i was having problems deleting files larger than the remaining free space in the pupsave-file)
Yes, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.
I finally opened a terminal in these trash directories and did a

Code: Select all

rm *
rm .*
cd ..
rmdir *
rmdir .*
to solve this manually
In order not to clutter up the trash "rubbish", use the delete missing trash. The right mouse button (in the paragraph the cursor is positioned). Recover deleted in this case is impossible.

Posted: Sun 29 Apr 2012, 08:42
by Sage
The rc.shutdown.pupdev is a document text. It does nothing as a script. Nothing do results hard-shutdown in some meaning.
I am very interesting if you report the result of the firstrun-debug-shutdown-2.2.1.pet. We can see, by the test, where it fails.
As I explained, I don't do coding. I swapped rc.shutdown for rc.shutdown.pupdev and the shutdown failure/desktop looping stopped. If you tell me where to find firstrun-debug-shutdown-2.2.1.pet I will look for it, but presume I would have to invert the swap because shutdown works with the -.-.pupdev.

Yes, I double checked. It may be just a text file but swapping rc.shutdown with ditto.pupdev and back again reproducibly causes and rectifies the shutdown problem. No idea why, but it does. You're the expert, shino....

Posted: Sun 29 Apr 2012, 09:14
by Karl Godt
First impression is that the difference is one mount less in the "return to X-Desktop" mount output .

This could indicate, that the part to unmount stray partitions once did run, and detecting a zombie process killed the parent of the zombie ...

So this might occur randomly, with one Puppy 511 and one racy-5.x i have jwm zombies .. probably by the jwm -restart|-reload command(s) that killing would normally not affect X, pup_event_frontend_d, delayedrun, xinitrc and that likes anymore because they should have been killed already by /usr/bin/wmreboot||/usr/bin/wmpoweroff ...

since the removal of /tmp directory occurs just before umount ing the stray partitions ..

and yes, i have confused Pupmode 6 and 7 ..

it might be, that somehow gettext or eval_gettext could have left a zombie process, maybe because of a typo ..

Posted: Sun 29 Apr 2012, 11:19
by mavrothal
It would appear that retrovol-saluki is broken in 020+. Specifically the icon does not show in the tray, though it works fine (eg responds to right-click etc).
Maybe related to the recent icon dir changes?
Any symlink that could solve this?
BTW where is the source? Barry's source for 0.10 and 0.12 does not compile (without "magic") in 021.

Retrovol

Posted: Sun 29 Apr 2012, 12:25
by Marv
It would appear that retrovol-saluki is broken in 020+. Specifically the icon does not show in the tray, though it works fine (eg responds to right-click etc).
Maybe related to the recent icon dir changes?
Any symlink that could solve this?
I had the same problem starting roughly around 020. Removing the Saluki Retrovol and installing retrovol-Lucid-0.5 ( I believe from the repository) got me back the icon and all works fine.

Posted: Sun 29 Apr 2012, 14:06
by jakfish
I'm trying out luki 021 on a Lenovo S10-3t netbook/tablet.

Looks like a great success (incredibly fast shut down, for starters), but before I get to all the good things, I'm having trouble with xorg.conf and the Lenovo touch screen.

I have a working xorg in dpup exprimo which allows initial calibration and touch screen driver setup (which is needed before using calibration tool):

Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "touchscreen" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/input/event10"
Option "DeviceName" "touchscreen"
Option "MinX" "80"
Option "MinY" "80"
Option "MaxX" "4095"
Option "MaxY" "4095"
Option "ReportingMode" "Raw"
#Option "MaxTapTime" "220"
#Option "MaxTapMove" "220"
#Option "moving_action" "down"
#Option "moving_button" "1"
#Option "maybetapped_action" "click"
#Option "maybetapped_button" "3"
# Option "longtouched_action" "click"
# Option "longtouched_button" "3"
# Option "touched_action" "click"
# Option "touched_button" "1"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection

I've put the above in xorg.conf and I don't believe xorg is reading it upon reboot or X restart.

I do the modprobe hid-multitouch, modprobe evdev in rc.local, and while those commands give me a touchscreen, I'm unable to get calibration or any other of the touch commands that an edited xorg should give me.

Jake

Posted: Sun 29 Apr 2012, 14:11
by jemimah
Karl Godt wrote:First impression is that the difference is one mount less in the "return to X-Desktop" mount output .

This could indicate, that the part to unmount stray partitions once did run, and detecting a zombie process killed the parent of the zombie ...

So this might occur randomly, with one Puppy 511 and one racy-5.x i have jwm zombies .. probably by the jwm -restart|-reload command(s) that killing would normally not affect X, pup_event_frontend_d, delayedrun, xinitrc and that likes anymore because they should have been killed already by /usr/bin/wmreboot||/usr/bin/wmpoweroff ...

since the removal of /tmp directory occurs just before umount ing the stray partitions ..

and yes, i have confused Pupmode 6 and 7 ..

it might be, that somehow gettext or eval_gettext could have left a zombie process, maybe because of a typo ..
This is good detective work.

The question is, why are we getting these reports now. It must be something that changed recently or it could be a coincidence I guess.

Here is the relevant section of the diff:

Code: Select all

 killzombies() {
  #ZOMBIES="`ps -H -A | grep '<defunct>' | sed -e 's/  /|/g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`"
- ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`" #120103 karl godt: because i was getting a bunch of "killall no such process must be either pid or name" on the screen by the killzombies function.
+ #ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`" #120103 karl godt: because i was getting a bunch of "killall no such process must be either pid or name" on the screen by the killzombies function.
+ ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | cut -f 1 -d ' ' | sort -gr | tr '\n' ' '`" #120129 karl godt: improved, see http://www.murga-linux.com/puppy/viewtopic.php?t=73122
  for ONEZOMBIE in $ZOMBIES
  do
   echo "Killing parentless zombie process $ONEZOMBIE"
   kill $ONEZOMBIE
  done
 }
Should I roll the zombie killing code back?

Posted: Sun 29 Apr 2012, 14:12
by jemimah
jakfish wrote:I'm trying out luki 021 on a Lenovo S10-3t netbook/tablet.

Looks like a great success (incredibly fast shut down, for starters), but before I get to all the good things, I'm having trouble with xorg.conf and the Lenovo touch screen.

I have a working xorg in dpup exprimo which allows initial calibration and touch screen driver setup (which is needed before using calibration tool):

Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "touchscreen" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/input/event10"
Option "DeviceName" "touchscreen"
Option "MinX" "80"
Option "MinY" "80"
Option "MaxX" "4095"
Option "MaxY" "4095"
Option "ReportingMode" "Raw"
#Option "MaxTapTime" "220"
#Option "MaxTapMove" "220"
#Option "moving_action" "down"
#Option "moving_button" "1"
#Option "maybetapped_action" "click"
#Option "maybetapped_button" "3"
# Option "longtouched_action" "click"
# Option "longtouched_button" "3"
# Option "touched_action" "click"
# Option "touched_button" "1"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection

I've put the above in xorg.conf and I don't believe xorg is reading it upon reboot or X restart.

I do the modprobe hid-multitouch, modprobe evdev in rc.local, and while those commands give me a touchscreen, I'm unable to get calibration or any other of the touch commands that an edited xorg should give me.

Jake
If you could, run Sysinfo from the System menu and post the results.

Posted: Sun 29 Apr 2012, 14:29
by jemimah
mavrothal wrote:It would appear that retrovol-saluki is broken in 020+. Specifically the icon does not show in the tray, though it works fine (eg responds to right-click etc).
Maybe related to the recent icon dir changes?
Any symlink that could solve this?
BTW where is the source? Barry's source for 0.10 and 0.12 does not compile (without "magic") in 021.
I've fixed retrovol in the repo.