Rox won't start; error message: No pinboard-solved) tks oscar,mike.big

[rburkartjo]

how to fix this error message
No pinboard was in use... the 'Default' pinboard has been selected. Use 'rox -p=Default' to turn it on in future./tks

[rburkartjo]

and i cant open the rox file manager weird.

[rburkartjo]

and when i clock the icon layout button in jwmdesk get error puppy rox [inboard (puppypin) is not running you cant use this app

[mikeslr]

@ rburkartjo,

See bigpup's post, viewtopic.php?p=816#p816.
Only your mother can read your mind. . We know only what you tell us.

I'm sure you know what things you did before this problem arose. I don't. If you can't devote your time to tell us what those things are, I'm not going to devote my time to search the Forum for your prior posts, try to guess, then suggest a solution. I recommend that no one else does.

[rburkartjo]

mike only thing i did was use psch to run /sbin/poweroff at 23 hrs. error started when powered up this am

[OscarTalks]

Sounds like rox has failed to start.
Have you tried turning it off and on again?
Open a terminal (from Menu) and enter rox -p=Default as mentioned in the first post and see if that starts it.
Using the poweroff command while X is running is probably a bad idea, is that what you did?
If you need to shut down from command line while X is running (with rox and jwm) you should use wmpoweroff

[rburkartjo]

oscar tks. been using that as a crontab command (/sbin/poweroff) for awhile. didnt find anything on google about not using in puppy. will keep thread open to see if anyone knows a fix. since i cant open rox will have to be done with terminal command. havent been able to find one on internet that actually works

[OscarTalks]

Are you able to open a terminal?
Have you tried entering the command I already mentioned (and you already mentioned) above, and if so, what was the result?

[rburkartjo]

oscar yes i opened a terminal and ran it. did not fix

[OscarTalks]

What was the terminal output? That often gives clues as to what is wrong.

[mikewalsh]

@rburkartjo :-

Far, far better to use wmpoweroff, as Oscar suggests. Simple reason being that the 'wmpowereoff' script is written to shut the various components down in the correct sequence.

Losing pinboard icons on boot used to be a favourite occurrence on Pups at one time, a few years back....at least for me. Given that the /root/Choices/Rox-filer/PuppyPin file (which controls placement, etc, of these) is what I call a 'live' file - any changes you make are immediately echoed to it - I've had a bunch of wee scripts in place for some time that copy the PuppyPin file to an external 'backup' location immediately prior to shut-down. These sit 'between' the shutdown GUI and the 'wmpoweroff'/'wmreboot' scripts.

If by any chance my pinboard HAS gone AWOL in the meantime, I have another script, accessible from the Menu, that allows me to quickly reset everything.

There's all sorts of 'hacks' & 'stunts' you can pull with Puppy when you know how.....but shutting down the correct way IS important, bearing in mind all the aufs/'loop' file-system stuff Puppy employs. It doesn't take a lot to chuck a spanner in the works.

Mike.

[rburkartjo]

root# !36
rox -p=Default
root#
no additional output

[rburkartjo]

tks mike again my bad i used the /sbin/poweroff in ubuntu all the time and didnt think it would negatively affect puppy. so am i sol?

[mikewalsh]

It might be worth checking to see if your 'PuppyPin' file is actually where it's supposed to be, y'know. Can you access Fossapup from outside Puppy? Have you got a 'Live' Puppy DVD/CD or USB stick you can use?

(Needs to be another Puppy, really, because mainstream distros don't understand the Puppy set-up.....especially if you're running a save-file, rather than a save-folder.)

If you can, look in /root/Choices/ROX-filer, and see if the default "PuppyPin" file actually exists. I have known it to just mysteriously 'disappear'.....

Mike.

[rburkartjo]

mike
root# cd /root/Choices/ROX-filer
bash: cd: /root/Choices/ROX-filer: No such file or directory
root#
okay can i reinstall from terminal and if so how

[mikewalsh]

/sbin/poweroff is fine in Ubuntu; it's only shutting down a standard set-up. What makes Puppy's case unique is all those aufs/loop "layers" she uses. They take more looking-after, it's true.....but they're the very things that enable so much of the Puppy "magic" to work.

You really DO need to stop thinking of Puppy as just "another" Linux distro. Yes, a lot of things will work the same once up-and-running, but those boot & shutdown sequences are quite different to what you may have been used to previously. It's no shame to admit ignorance, mate; it took ME well over two years before I finally began to get a handle on how all this stuff works.....even by Linux standards, Puppy's considered "odd" by many in the community, and yes, there IS a bit more of a learning curve......but my God! it's well worth the effort. Once you've mastered things, you'll have an OS you can make sing'n'dance, sit, beg, play ball, fetch, etc., and run rings around most any other distro you care to name.

Needs a wee adjustment of the mind-set, that's all. We employ a LOT of "lateral" thinking here in Puppyland...!

Mike.

[OscarTalks]

NOTE - "ROX-Filer" has upper case "F"
If /root/Choices/ROX-Filer/PuppyPin is present
Try command in terminal rox -p /root/Choices/ROX-Filer/PuppyPin

[rburkartjo]

oscar
root# cd /root/Choices/ROX-Filer/PuppyPin
bash: cd: /root/Choices/ROX-Filer/PuppyPin: Not a directory
root# whereis /root/Choices/ROX-Filer/PuppyPin
PuppyPin:
root# rox -p /root/Choices/ROX-Filer/PuppyPin

** (ROX-Filer:19448): WARNING **: 10:30:57.628: Existing ROX-Filer process is not responding! Try with -n
root#
root# rox -n /root/Choices/ROX-Filer/PuppyPin
root#
still didnt fix

[OscarTalks]

Try the command killall ROX-Filer
Repeat this until you get the output "no process killed"
Then try the command rox -p /root/Choices/ROX-Filer/PuppyPin again

[rburkartjo]

root# killall ROX-Filer
root# killall ROX-Filer
killall: ROX-Filer: no process killed
root# rox -p /root/Choices/ROX-Filer/PuppyPin
root#
no luck

[mikewalsh]

Mm. Me, I reckon you've gone and buggered-up either the pup_ro2 or pup_rw layers, somehow. Possibly, file-system corruption from incorrect shutting-down.

Are you running 'frugal' these days, or are you still on a 'full' install?

@OscarTalks :-

Oscar, what d'you think? I'm not much cop with the terminal, but rb appears to have no way to actually LOOK at what's going on. This is why I suggested a Live Puppy, take a look from 'outside', like.....

Mike.

[OscarTalks]

One easy way to see if PuppyPin is present is
cd /root/Choices/ROX-Filer
followed by
ls
to list the files in that directory

[rburkartjo]

oscar
root# cd /root/Choices/ROX-Filer
root# ls
globicons PuppyPin PuppyPin-norm PuppyPin-sml README.txt
root#

[rburkartjo]

ok got a live puppy on a stick. and my messed up install is on another stick. can i copy anything from the live to fix and if so how to proceed./tks

[OscarTalks]

Are these both frugal installs on USB flash drives with save folders?
Or do they have save files?
If so, you might be able to make the bad one into a copy of the good one, if that would be any use to you?
Fixing the bad one by manipulating files using the good one is also possible, but we would first need to identify what has gone wrong and what needs to be corrected. The normal shutdown process handles certain things and I don't know much about those things so I am running out of ideas now.

[bigpup]

Boot the bad USB install not using the save.
Should be option in the boot menu to do that.
ram only menu entry.

If it boots OK and everything is working.
The save is bad.

Use Rox and click on the save file/folder to open and see what is in it.
Open the save and navigate to /root/Choices/ROX-Filer that is in the save.
If there is a backup of the PuppyPin
Delete the PuppyyPin that is bad and replace with the backup, by removing BACKUP from the name.
Close the save.
If no backup of PuppyPin. Delete the one that is there.
Reboot, now booting using the save.

Any help?

Could also delete what is in /root/.config/rox-sourceforge.net/ROX-Filer (hidden files)

Note:
As long as the save is not being used.
You can delete anything in it that could be bad.
On next boot using it, Puppy OS will use the original version of whatever you deleted.

Better would be to just replace the save file/folder, with the good save backup copy, that you should have made, like we all do

[rburkartjo]

oscar,mike, and big thank you all for your help. before posting problem here did a lot of searching to fix on own. i have been using /sbin/poweroff in cron job since feb and never had an issue so never considered it as a possible cause of my problem. just did a new install of puppy. was easier since my computer doesnt recognize my harddrive. /tks all