slacko-5.6 Final - plus testing next
Slacko 5.6.1
Using Firefox browser installed in Slacko 5.6.1.
Tried to download an image file and got this screen for selecting location to save to. Notice blank screen. Seemed to go blank at random times, trying to navigate to a location in file system.
Using Firefox browser installed in Slacko 5.6.1.
Tried to download an image file and got this screen for selecting location to save to. Notice blank screen. Seemed to go blank at random times, trying to navigate to a location in file system.
- Attachments
-
- Screenshot.png
- (35.08 KiB) Downloaded 933 times
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)
Not a bug bigpup, you are running firefox as Spot. It will only be able to open /root/spot (spots home) and any sub-directory. If you don't wan to be spot, quit firefox, open menu>system>Login and Security Manager, uncheck firefox and click Ok.
- Attachments
-
- ffspot.jpg
- (61.05 KiB) Downloaded 991 times
Puppy Linux Blog - contact me for access
01micko,
I was wondering if Spot was the problem, but was not sure.
Now you know why I never use spot.
Test results:
Spot operation mode seems to be working in Firefox
Computer just gave me the coffee warning.
I was wondering if Spot was the problem, but was not sure.
Now you know why I never use spot.
Test results:
Spot operation mode seems to be working in Firefox
Computer just gave me the coffee warning.
- Attachments
-
- coffee.jpg
- (16.56 KiB) Downloaded 951 times
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)
Slacko 5.6.1
PPM (initial default setup)
Repositories showing in PPM are 5. OK.
Max number able to list at one time 5.
In configure PPM
6 repositories are selected initially, by default.
The Puppy-noarch offical repository is not showing.
This one should be seen by a new user for no other reason then this.
PPM (initial default setup)
Repositories showing in PPM are 5. OK.
Max number able to list at one time 5.
In configure PPM
6 repositories are selected initially, by default.
The Puppy-noarch offical repository is not showing.
This one should be seen by a new user for no other reason then this.
- Attachments
-
- Screenshot2.png
- (36.54 KiB) Downloaded 731 times
-
- Screenshot1.png
- (14.63 KiB) Downloaded 747 times
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)
While looking at PPM as a new user of Puppy and Linux for that matter.
I feel there would be less confusion for a new user, if PPM initial default setup, would have
package types
defaulted to:
any type.
Let them change it to other options, when they understand what those options are.
As it is now, default is GUI apps only.
Do you even understand all of these options?
I feel there would be less confusion for a new user, if PPM initial default setup, would have
package types
defaulted to:
any type.
Let them change it to other options, when they understand what those options are.
As it is now, default is GUI apps only.
Do you even understand all of these options?
- Attachments
-
- Screenshot3.png
- (14.01 KiB) Downloaded 693 times
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)
Hi, Mick.
Bad news here... V. 5.6.1 has the first save bug. The size determination
dialogue is skipped, and we end up with a negative value of -1 Mb for
the pupsave file. (Please see attached illustration.)
It may be tempting to blame the problem on my 10-year old machine,
but it has 2 Gb's of RAM and 1.128 Tb of mass storage attached to it,
so it still has plenty of power. Moreover, this machine does not have
save-file (or equivalent) problems with other types of Puppies, nor
on other distros that accept save files for frugal mode (e.g. Debian
Squeeze).
I did peruse the shutdown code, but I won't touch it. Some people are
better and more experienced at editing it than I am. Especially code
by BK.
That said, here are a couple of ideas.
1) If the set_pupsize function (not exact name) could default the
SIZEPFILE (exact name) variable at 16 or 32 Mb's when there is an error
at first save in this frugal mode (is it mode 12 or 13?), it would prevent
frustrations. The user could fatten the pupsave file easily at 2nd or 3rd
boot.
2) If the "DO NOT SAVE" button halted the script, the user would be
able to save his/her configurations to another medium, again
preventing frustrations, and saving time.
Best of luck with your new version, but this tester is out for the above
reason. However, I did provide sufficient test information (I think) about
this problem in a thread that I created yesterday, so if you or anyone
wants to draw on my experience of this bug, you know where to look:
http://murga-linux.com/puppy/viewtopic. ... ost#739203.
BFN.
musher0
Bad news here... V. 5.6.1 has the first save bug. The size determination
dialogue is skipped, and we end up with a negative value of -1 Mb for
the pupsave file. (Please see attached illustration.)
It may be tempting to blame the problem on my 10-year old machine,
but it has 2 Gb's of RAM and 1.128 Tb of mass storage attached to it,
so it still has plenty of power. Moreover, this machine does not have
save-file (or equivalent) problems with other types of Puppies, nor
on other distros that accept save files for frugal mode (e.g. Debian
Squeeze).
I did peruse the shutdown code, but I won't touch it. Some people are
better and more experienced at editing it than I am. Especially code
by BK.
That said, here are a couple of ideas.
1) If the set_pupsize function (not exact name) could default the
SIZEPFILE (exact name) variable at 16 or 32 Mb's when there is an error
at first save in this frugal mode (is it mode 12 or 13?), it would prevent
frustrations. The user could fatten the pupsave file easily at 2nd or 3rd
boot.
2) If the "DO NOT SAVE" button halted the script, the user would be
able to save his/her configurations to another medium, again
preventing frustrations, and saving time.
Best of luck with your new version, but this tester is out for the above
reason. However, I did provide sufficient test information (I think) about
this problem in a thread that I created yesterday, so if you or anyone
wants to draw on my experience of this bug, you know where to look:
http://murga-linux.com/puppy/viewtopic. ... ost#739203.
BFN.
musher0
- Attachments
-
- 59.png
- (44.59 KiB) Downloaded 682 times
Last edited by musher0 on Sun 24 Nov 2013, 11:35, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Just wanted to report that I ran Slacko 5.6.1 off and on all day with no real problems. Installed some pets,did some visual tweaks and made Firefox run as root....... really nothing bad to report.Used both the Athlon XP and the P4 installs.... a bit slower on the Athlon XP box but no real difficulties.
Switched over to Sid a bit ago........
Switched over to Sid a bit ago........
Code: Select all
Sun Nov 24 03:02:41 CST 2013
james@lxde:~$ uname -r
3.12-1.towo-siduction-686
james@lxde:~$
fine
Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power and firefox 15% with just the forum active - these are higher than usual (The white load line is generally visible. Anyway, don't pay attention to it, am just a spoiled puppy user ). I thought that this should be normal with a new kernel.
As to musher0's negative pupsave file, I haven't encountered it yet in any recent puppy.
As to musher0's negative pupsave file, I haven't encountered it yet in any recent puppy.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Hello, people.
I did manage to get a pupsave. Please see how at http://murga-linux.com/puppy/viewtopic. ... ost#739203
However, upon reboot, I got the gdk bug, as in Precise 5.7.1 "non-retro".
Shucks.
BFN.
I did manage to get a pupsave. Please see how at http://murga-linux.com/puppy/viewtopic. ... ost#739203
However, upon reboot, I got the gdk bug, as in Precise 5.7.1 "non-retro".
Shucks.
BFN.
- Attachments
-
- IMG_0132.JPG
- I had to take a real picture. The program calling system in ROX being broken, mtpaint did not launch. I apologize for the fuzziness.
- (24.54 KiB) Downloaded 630 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I too can not recreate the negative size of savefile (nor PPM hang) yet...
@Musher0: you could launch shutdownconfig from terminal - maybe some errors will show up..?
@Mick: Slacko has (in devx) strings, but named as "strings-GNU" - shouldn't it be just "strings" (like in Precise's or Dpup's devx)?
Greetings!
@Musher0: you could launch shutdownconfig from terminal - maybe some errors will show up..?
I'm getting the same on AMD C60 netbook. But after installing fglrx (when will be available) this should drop ~3-5%.raffy wrote:Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power[...]
@Mick: Slacko has (in devx) strings, but named as "strings-GNU" - shouldn't it be just "strings" (like in Precise's or Dpup's devx)?
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Musher, what SFR says might shed some light (run wmpoweroff in terminal with original shutdown script), it may be a 'mount' error or something silly. This was the case with the ntfs bug which I fixed about a year ago but it was a bit more than just running in the terminal, however yours should get that far since it's still in GUI when you see the bug.SFR wrote:I too can not recreate the negative size of savefile (nor PPM hang) yet...
@Musher0: you could launch shutdownconfig from terminal - maybe some errors will show up..?
I'm getting the same on AMD C60 netbook. But after installing fglrx (when will be available) this should drop ~3-5%.raffy wrote:Works fine in my AMD E-350 laptop. X usually consumes 10% of cpu power[...]
@Mick: Slacko has (in devx) strings, but named as "strings-GNU" - shouldn't it be just "strings" (like in Precise's or Dpup's devx)?
Greetings!
SFR, already have a work around. I actually had an argument about this with Barry, then he changed busy box strings to be used, but then for some reason changed it back! Slackware has strings in util-linux package but other distros (all of them according to Barry - see the template for util-linux in woof) have it in bin-utils. Now I am just renaming strings-GNU (part of slackware bin-utils). See how that works.
Puppy Linux Blog - contact me for access
Hello, all.
@SFR and 01micko:
Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.
That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.
@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.
So partial success, again.
When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...
BFN.
musher0
@SFR and 01micko:
Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.
That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.
@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.
So partial success, again.
When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hope it is okay with my noob question.
How do I know which version is best for my computer
slacko-5.6-4G-NON-PAE.iso or slacko-5.6-PAE.iso
I have a Desktop HP/Compaq AMD Athlon X2 Dual Core
rather old computer CPU now. ?
3GB RAM Doing frugal install on the NTFS HD
The Graphics are nVidia G98 (GE Force 9300 )
How do I know which version is best for my computer
slacko-5.6-4G-NON-PAE.iso or slacko-5.6-PAE.iso
I have a Desktop HP/Compaq AMD Athlon X2 Dual Core
rather old computer CPU now. ?
3GB RAM Doing frugal install on the NTFS HD
The Graphics are nVidia G98 (GE Force 9300 )
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Now its me also about to complain about rc.shutdown !!!musher0 wrote:Hello, all.
@SFR and 01micko:
Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.
That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.
@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.
So partial success, again.
When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...
BFN.
musher0
Save-file was created correctly to vfat in size of 128 MB with ext3 .
Then I went wmexit to prompt and reboot then failed to copy /initrd/pup_rw into the save-file .
/dev/sdb1 1018084 845548 172536 84% /mnt/sdb1
Today's boot failed with kernel panic about smp, shed and hrtimer .
e2fsck -v /mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs
e2fsck 1.42.6 (21-Sep-2012)
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: recovering journal
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: clean, 11/32768 files, 9804/131072 blocks
/dev/loop1 126931 5663 121268 5% /mnt/+mnt+sdb1+WoofCEtest+slackosave-2013_11_23.3fs
Only empty lost+found in that
Either will produce a very stable operation on your PC. Either will work without fail. System operation for the user is the same as well as the application selection offered.nooby wrote:... How do I know which version is best for my computer? ...
The ONLY difference, per se, is that PAE can be used, on just about every PC since 1995, but also no matter how much RAM you have from 384MB to as much as you can add to your PC all the way to 64GB. Non-PAE is limited by its inability to take advantage of any RAM beyond 3GB.
Again, either will work on your current system.
Here to help
I was finally the first at something !Karl Godt wrote:Now its me also about to complain about rc.shutdown !!!musher0 wrote:Hello, all.
@SFR and 01micko:
Success using shutdownconfig directly, as a standalone program.
The size dialog showed correctly.
That seemed to do something to the rc.shutdown script in /etc, since
it ran correctly, in full, and I got another valid pupsave file on
the "official" reboot run.
@SFR:
I ran shutdownconfig from console with < set -xe > added at the top
of the script, and the run displayed no errors.
So partial success, again.
When I got back in, on second boot with this new pupsave file, though,
the gdk bug was staring me in the face! But let's handle only one insect
at a time, shall we?!...
BFN.
musher0
Save-file was created correctly to vfat in size of 128 MB with ext3 .
Then I went wmexit to prompt and reboot then failed to copy /initrd/pup_rw into the save-file .
/dev/sdb1 1018084 845548 172536 84% /mnt/sdb1
Today's boot failed with kernel panic about smp, shed and hrtimer .
e2fsck -v /mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs
e2fsck 1.42.6 (21-Sep-2012)
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: recovering journal
/mnt/sdb1/WoofCEtest/slackosave-2013_11_23.3fs: clean, 11/32768 files, 9804/131072 blocks
/dev/loop1 126931 5663 121268 5% /mnt/+mnt+sdb1+WoofCEtest+slackosave-2013_11_23.3fs
Only empty lost+found in that
KG said:
>Then I went wmexit to prompt and reboot then failed to copy
/initrd/pup_rw into the save-file.
Ah! But the shutdown script is supposed to bounce us out of the bar! show
us the door! kick us out! Not allow us to go out in our own good time!
Nah-nah-nah, once you're done, you have maybe 30 seconds left to kiss
the girlfriend good-bye, and that only in GUI mode; then out, out, out
you go!
You shouldn't have had the time to type wmexit and reboot. You weren't
supposed to. Maybe a conflict of powerful commands corrupted your save
file. Typing wmexit and reboot probably interfered while normal creation
of pupsave. My 2¢.
BFN.
musher0
Last edited by musher0 on Sun 24 Nov 2013, 19:13, edited 2 times in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
PPLOG, or actually hiawatha issue - server cannot be stopped in a normal way.
'hiawatha' binary seems to be hardcoded to use (non-existant) /usr/var/run/ to store its PID in, whereas 'hiawatha.run' script tries to read from /var/run/.
It seems to affect only Slacko since 5.5; latest Precise and Raring-3.9.8.1 are fine (PID stored in /var/run/) and transplanting 'hiawatha' bin from there into Slacko fixes that indeed.
Greetings!
Code: Select all
# hiawatha.run start
Starting webserver: Warning: can't write PID file /usr/var/run/hiawatha.pid.
Hiawatha
#
# hiawatha.run stop
Hiawatha is not running
#
# ps | grep hiawatha | grep -v grep
9249 webuser 0:00 /usr/sbin/hiawatha
#
Code: Select all
# grep -m1 'PIDFILE' /usr/sbin/hiawatha.run
PIDFILE="/var/run/hiawatha.pid"
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Thanks 01 micko seems to work on my machine too.
Did a frugal install on NTFS HDD made save file.
rebooted and here I am using slacko.
Now I need to find out how to handly that Lupu
put .mozilla on HDD and a lot of other things on hdd too.
This Firefox is 17.0-1 and refuses to go up to FF 25 and beyond
.cache if I remember.
Thanks to gcmartin for encouragement
I gave it a chance.and it did work.
Did a frugal install on NTFS HDD made save file.
rebooted and here I am using slacko.
Now I need to find out how to handly that Lupu
put .mozilla on HDD and a lot of other things on hdd too.
This Firefox is 17.0-1 and refuses to go up to FF 25 and beyond
.cache if I remember.
Thanks to gcmartin for encouragement
I gave it a chance.and it did work.
Last edited by nooby on Sun 24 Nov 2013, 22:01, edited 2 times in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Nope, ran shutdownconfig from urxvt terminal, then wmexit .Ah! But the shutdown script is supposed to bounce us out of the bar! show
us the door! kick us out! Smile Not allow us to go out in our own good time!
Nah-nah-nah, once you're done, you have maybe 30 seconds left to kiss
the girlfriend good-bye, and that only in GUI mode; then out, out, out
you go!
You shouldn't have had the time to type wmexit and reboot. You weren't
supposed to. Maybe a conflict of powerful commands corrupted your save
file. Typing wmexit and reboot probably interfered while normal creation
of pupsave. My 2¢.
shutdownconfig just cre-ates the save-file .
shutdownconfig gets usually called by wmreboot or wmpoweroff .
That way you would not have time to do anything, except pup_event_frontend_d is stubborn and refuses to be killed . In such case I would have had one minute for opening a urxvt console terminal to type
# whoami
Spock
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P