Slacko full install won't "Shut Down" or "Reboot"
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
Slacko full install won't "Shut Down" or "Reboot"
[Slacko 5.7, full hard-drive install]
There was some problem with "pet" files not launching, so I rebooted. Puppy couldn't get into the GUI. I reinstalled without "Wiping" from the CD. Now Puppy boots fine; but doesn't "Shut Down" or "Reboot" by clicking on the menu buttons or pushing the power button and confirming.
If it's complicated to try to fix this - just tell me how to backup the applications; so I could reinstall and wipe or even format the partition.
Thanks.
There was some problem with "pet" files not launching, so I rebooted. Puppy couldn't get into the GUI. I reinstalled without "Wiping" from the CD. Now Puppy boots fine; but doesn't "Shut Down" or "Reboot" by clicking on the menu buttons or pushing the power button and confirming.
If it's complicated to try to fix this - just tell me how to backup the applications; so I could reinstall and wipe or even format the partition.
Thanks.
- Colonel Panic
- Posts: 2171
- Joined: Sat 16 Sep 2006, 11:09
I've not used 5.7 much but I had the same problem with an earlier version of Slacko.
I got around it by exiting X Windows and then typing "poweroff" at the command prompt (which always worked to shut the machine down).
I got around it by exiting X Windows and then typing "poweroff" at the command prompt (which always worked to shut the machine down).
Gigabyte M68MT-52P motherboard, AMD Athlon II X4 630, 5.8 GB of DDR3 RAM and a 250 GB Hitachi hard drive running Ubuntu 16.04.6, MX-19.2, Peppermint 10, PCLinuxOS 20.02, LXLE 18.04.3, Pardus 19.2, exGENT 200119, Bionic Pup 8.0 and Xenial CE 7.5 XL.
MrAccident ,
What pet package you installed will be big clue as to what happened.
Also, what is the format of the partition, the Slacko full install is on?
You can try this:
In PPM Puppy Package Manager uninstall the pet package that you think caused this.
Reboot.
If still having problems.
This is a way to repair a full install.
This only works for full installs.
Boot with the live CD of Slacko
Use boot option puppy pfix=ram
At desktop select install icon
Select button to run Universal installer
Do a full install of Slacko to the same location as the none working full install.
Very important
During the setup for the full install you will get option to upgrade
Choose that option upgrade
Do nothing to bootloader. Old settings will still work.
When installer is finished remove CD
Reboot to the full install.
(Because you where running the live CD, it will ask about making a save file. Say no.)
What pet package you installed will be big clue as to what happened.
Also, what is the format of the partition, the Slacko full install is on?
You can try this:
In PPM Puppy Package Manager uninstall the pet package that you think caused this.
Reboot.
If still having problems.
This is a way to repair a full install.
This only works for full installs.
Boot with the live CD of Slacko
Use boot option puppy pfix=ram
At desktop select install icon
Select button to run Universal installer
Do a full install of Slacko to the same location as the none working full install.
Very important
During the setup for the full install you will get option to upgrade
Choose that option upgrade
Do nothing to bootloader. Old settings will still work.
When installer is finished remove CD
Reboot to the full install.
(Because you where running the live CD, it will ask about making a save file. Say no.)
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
BigPup - I don't think it was the packages. I found them on the net. The application was "netsurf-2.6". There were 3 PET files. I think that they didn't work because of some random problem; maybe because the OS ran for a long time. I think so because after rebooting - I was able to install it; and it worked. Moreover - I already uninstalled it, and the same problem continued.
I think the problem is because I didn't install them till the end and/or powered-off forcefully.
The partition is ext4.
I pretty much tried what you describe; but without starting Puppy in the PFix mode; so I'll try that.
(Edit) I tried, but there was no "pfix" option.
I think the problem is because I didn't install them till the end and/or powered-off forcefully.
The partition is ext4.
I pretty much tried what you describe; but without starting Puppy in the PFix mode; so I'll try that.
(Edit) I tried, but there was no "pfix" option.
The scripts that launch the poweroff or reboot processes are
/usr/bin/wmpoweroff
and
/usr/bin/wmreboot .
Check first if they are ok .
Also check the /root/.jwmrc file ( hidden ) that contains lines to call tese scripts :
That should have lines as
<Program label="Shutdown" icon="shutdown24.png">exec /usr/bin/poweroff</Program>
and similar for reboot .
Another : If your Sudo environment is not OK anymore /etc/sudoers file might cause problems too .
/usr/bin/wmpoweroff
and
/usr/bin/wmreboot .
Check first if they are ok .
Also check the /root/.jwmrc file ( hidden ) that contains lines to call tese scripts :
That should have lines as
<Program label="Shutdown" icon="shutdown24.png">exec /usr/bin/poweroff</Program>
and similar for reboot .
Another : If your Sudo environment is not OK anymore /etc/sudoers file might cause problems too .
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
That is correct.n the file ".jwmrc"
The word "reboot" - does not exist in the document.
Slacko 5.7 uses a logout menu
In Slacko 5.7 menu->Shutdown runs logout_gui
The file is at /usr/sbin/logout_gui
You could try and replace the logout_gui file with the one from the Slacko 5.7 iso file.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
If you did power off in an abnormal way, there is a chance you may have some file system corruption of the partition.powered-off forcefully.
Run the program Gparted and have it do a check of the hard drive.
To use Gparted:
Boot with the Puppy live CD
At the Puppy boot screen hit F2 key.
Use the boot option puppy pfix=ram.
This keeps the hard drive from being mounted.
Hard drive can not be mounted for Gparted to work.
In Gparted
right click on a partition
Select check
If it finds anything wrong it will correct.
If you have more than one partition on hard drive
run a check on all of them.
Remove the live CD
Reboot
Because of the way you are running with the live CD. You will be asked about making a save file.
Choose no.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
WOW, nothing worked.
I think that I couldn't boot in the "pfix=ram" mode; it said something about not being able to load something, I think. It did boot; I just don't know if in that mode.
GParted couldn't check the disk. There was an option to save the error details; but it didn't actually save it where I tried.
I replaced the file "logout_gui"; didn't change anything.
When I run "wmpoweroff", it says - "kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -
1 [sigspec]".
I think that I couldn't boot in the "pfix=ram" mode; it said something about not being able to load something, I think. It did boot; I just don't know if in that mode.
GParted couldn't check the disk. There was an option to save the error details; but it didn't actually save it where I tried.
I replaced the file "logout_gui"; didn't change anything.
When I run "wmpoweroff", it says - "kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -
1 [sigspec]".
Did you enter puppy pfix=ramI think that I couldn't boot in the "pfix=ram" mode;
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Gparted live CD or USB.
For partitioning I would suggest you use the Gparted live CD or USB that you can get from here.
You can download a free version to make your own Gparted live CD or USB.
It is up to date and specifically made to run Gparted.
Info:
http://gparted.sourceforge.net/livecd.php
Download:
http://sourceforge.net/projects/gparted ... ve-stable/
For partitioning I would suggest you use the Gparted live CD or USB that you can get from here.
You can download a free version to make your own Gparted live CD or USB.
It is up to date and specifically made to run Gparted.
Info:
http://gparted.sourceforge.net/livecd.php
Download:
http://sourceforge.net/projects/gparted ... ve-stable/
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
If you are saying you tried to use the Gparted live CD.
Tried to do a partition check using Gparted.
Gparted could not check the partition and gave you an error message.
Can you remember what the error was?
Even if you can not remember all of the error. In general what was it?
This is going to be the clue to figure out what is going on.
If Gparted is refusing to do a partition file system check it usually indicates there is something really wrong with the partition.
It could be telling you it found something wrong and is asking if you want to correct or telling you to do something first, before it can check.
Tried to do a partition check using Gparted.
Gparted could not check the partition and gave you an error message.
Can you remember what the error was?
Even if you can not remember all of the error. In general what was it?
This is going to be the clue to figure out what is going on.
If Gparted is refusing to do a partition file system check it usually indicates there is something really wrong with the partition.
It could be telling you it found something wrong and is asking if you want to correct or telling you to do something first, before it can check.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
- MrAccident
- Posts: 361
- Joined: Mon 31 Mar 2014, 20:53
Mostly it's FireFox that I need to backup; I have a million ad-ons. But I think they have a few ways to do that; I'll look into that.
Actually I'm considering TinyCore; I pretty much want to change all the programs; and I can't uninstall most of them in Puppy.
I also don't like this problem; it's pretty severe!
So I'll just hang on until I'll switch.
Thanks.
Actually I'm considering TinyCore; I pretty much want to change all the programs; and I can't uninstall most of them in Puppy.
I also don't like this problem; it's pretty severe!
So I'll just hang on until I'll switch.
Thanks.
I've used TinyCore. It's pretty solid, though I haven't done a full install. If you're veering away from Puppy, you might also want to look at http://www.bodhilinux.com/
I did a full install of this one and it worked pretty nicely with Ubuntu packages. Ubuntu is another nice option but Bohdi is lighter, I think.
Don't be discouraged by your use of Slacko, though. Keep in mind, Puppy was originally built to run as a live offering (off cd or usb) so the little nagging issues aren't really a problem when you can just reboot a live cd. BTW, Slacko has never been one of my favorite puppies.
I suggest you install something else but keep a puppy live cd or two hanging around. It's come a long way in the past year or so and I'm sure its progression will continue. Also, the people on this board are really great and helpful!
I did a full install of this one and it worked pretty nicely with Ubuntu packages. Ubuntu is another nice option but Bohdi is lighter, I think.
Don't be discouraged by your use of Slacko, though. Keep in mind, Puppy was originally built to run as a live offering (off cd or usb) so the little nagging issues aren't really a problem when you can just reboot a live cd. BTW, Slacko has never been one of my favorite puppies.
I suggest you install something else but keep a puppy live cd or two hanging around. It's come a long way in the past year or so and I'm sure its progression will continue. Also, the people on this board are really great and helpful!
-
- Posts: 597
- Joined: Thu 13 Nov 2008, 13:45
Yes, don't use the program manager, but go to the repositories (for example ibiblio) directly with your browser and save the .pets you want.MrAccident wrote:Can I save only the applications part of Puppy, and reinstall Puppy? I think it will be easier; it's not Windows. :-J
Frugal installs can make this much easier if you do something to bork the o.s., simply start over. If you search the forum you can figure out how to do certain things, if not, ask I guess.
By the way, I had the same problem with Slacko 5.4 and 5.5, and with certain FatDogs (but only after installing certain .pets with FatDog).