Puppy 4.2 "Deep Thought" - Bugs & Fixes

[davesurrey]

But you cannot have two 4.2 sfs in the same partition even seperated by directories

Was unaware of that. But as I said above they are in separate partitions so should be okay.
Cheers

[joel]

i have found 3 bugs.

I have a compaq evo n610c laptop.

when i close the lid while the puter is still running, the screen will not relight when opened up. i can still see puppy there as if the backlight is not activated. th only choice i have is to shutdown and restar. i am sure this is a software issue because it does not happen with windoze xp.

second is an issue where puppy say it is not allowed when trying to play fullscreen videos

third item is that some times the screen will out of nowhere get fuzzy and pixley as if the screen is streched. puppy is still running but everything is pixley. again if i restart its fine.

[ICPUG]

Trio,

Quote:

But you cannot have two 4.2 sfs in the same partition even seperated by directories

Why do you say that? I have standard and no bling version frugally installed in the same partition - in different subdirectories - with differently named save files in the appropriate subdirectory. It appears to work, as I would expect it to. Serious problem if it doesn't cos this is one of the big plus points of frugal install - the ability to have different puplets in different subdirectories.

The init script for 4.1.x certainly coped and I don't think that for 4.2 has changed in this respect.

[Béèm]

Dave

No, I'm serious, if let's say you have 4.1 and 4.2 in the same partition but different directory, than it's ok. But you cannot have two 4.2 sfs in the same partition even seperated by directories

I have subdirectories from alpha 1 on to final.
The only thing I have to take care of, f.e. if I want to look at alpha 1 again, that I copy the pup_420.sfs corresponding to alpha 1 to /mnt/home first before booting and selecting alpha 1 in the grub menu.lst.

Prior to 4.2 this wasn't necessary as there was a pup_xxx.sfs where xxx was a sub level version indication.

[ttuuxxx]

[quote="oztules"][/quote]
Open up Pprocess and find what process is running that card. and try to kill it, Then write down word for word the name of it, or even take a snapshot of Pprocess and circle the hanging program, then a simple little update to the shutdown menu with a killall and you should be good
so post you findings here
ttuuxxx

[mawebb88]

I've mentioned this elsewhere, but wot wiv this being the bugs thread, I'll repeat it here. Hope that's ok...

I have a frugal install on a Dell D610 laptop.
Shutdown doesn't work, and more recently had problems with reboot.
Screen goes black and system locks up - also happens when trying to change locale.
This laptop has run several varieties of Puppy before without problem.

[EDIT]
Mmm... Reboot not working, but just tried a shutdown and it worked correctly for the first time. No idea why (although I'm not complaining - if someone fixed it by the power of thought, I'm very grateful.)

which wm do you use? and could it be a broken download?

I also have this black screen of death (BOD) problem with a frugal install of 4.2 standard on my Eee PC901's SSD. There appears to be more than one cause but certainly for me one of them is switching WM from JWM to ICEWM and back .and then shutting down when I then get the BOD. Never seen this with 4.1.2.

Rgds Mike

[mawebb88]

Tried hard last night to get this working with 4.2 standard on my Eee PC901 from a frugal SSD install. Everything in CUPS looks fine (except I have to use http://localhost:631 from SeaMonkey as the normal CUPS interface does not see to commit anything) but nothing is sent to the printer (no lights blink etc) although in the Job's list it says its finished.

Only clue I have is to try the stuff in this thread:

Puppy 4.2 Alpha4 Seamonkey Bugs & Fixes
http://www.murga-linux.com/puppy/viewtopic.php?p=274516
by ttuuxxx (PostPosted: Fri Feb 13, 2009 1:17 pm) where he says "and it worked Smile)))))) for the first time on Puppy this Cannon printer works, yahoooooooo."

BTW I started from scratch with 4.2 so no save file contamination from 4.1.2.

Rgds Mike

I normally have to resort to printing from Windoze XP to another PC loaded with Puppy 4.1.2 set up as a pass-through printer server but am afraid to boot this today with all that Conficker virus stuff around.

[mawebb88]

I have lost Blnky! I stupidly made the mistake of on the right click options hiding both of my interfaces and now I would like to get the WiFi one back but can't figure out how to as Blinky has gone as one would expect. I searched for a configuration file eg. /root/.blinky but this lists (CSV) both interfaces but could not find where the hide option is stored?

Rgds Mike

[rcrsn51]

Yesterday, user jakfish solved his printing problems on a EEE by installing CUPS 1.3.9. Read here. Then go here for details. You might want to make a backup copy of your pup_save file before starting, just in case.

[mawebb88]

I had to again (like with 4.1.2) edit the init script in initrd.gz. to force PUPMODE=13 on my Eee PC901 SSD (to minimise wear and tear) as reported in:

Booting and running with CF card in IDE adaptor (Solved)
http://www.murga-linux.com/puppy/viewtopic.php?t=28551

HairyWill had proposed a non hard coded solution in that thread but if it has been implemented (??) then it does not work for me hence editing the init script was required to overcome PUPMODE=12.

Rgds Mike

[mouldy]

Not sure what the idea with the calendar with black numbers on dark part of desktop screen. On my old lcd screen with my old eyes, I CANNOT see the numbers. I had to create a png background that is bright yellow in order to see the white days and the little black numbers. Can the calendar widget be easily modified some way from some menu or config file so I can determine what colors of numbers should be?

And played some with pupdial. The probe on second try actually finds serial modem with usb converter cable. Congradulations, somebody finally fixed that little bug where wvdial couldnt deal with /dev/usb/ttyUSB0 by simple fix of copying so now have /dev/ttyUSB0.

But now when it dials out and starts negotiating with my isp, starts off ok but quikly goes to monotone sound where its obviously not communicating with isp and nothing gets done. I cant connect. If you let wvdial go long enough it times out and tries again to same end. And its same modem, same converter cable, same isp that I am posting this with now only using Puppy 3.01.

I will eventually make it work, if nothing else ripping wvdial stuff out by shorthairs and reinstalling it from scratch out of an older Puppy, but it should work out of box without such hassle.

Also the poweroff computer entry on menu now wants to pop up a screen and make me push a button to poweroff just like the windows philosophy of "are you sure???, are you really sure?????, are you reall, really, really sure?????????????......" That sucks. When I click poweroff, I want it to start process of shutting down, not play twenty questions with me. Then when I push the shutdown button it just hangs. I had to use the power switch on the back of my computer to shut things down. That sucks big time. This isnt even acpi stuff, this doesnt get that far, it just hangs at the desktop, doesnt even start shutting down.

Is anybody even trying the releases of Puppy on older computers anymore or with dialup? Sure doesnt look like it. I am on dialup so downloading 100mb of beta eyecandy just isnt in the cards to give feedback earlier in the process. I wait until I can get to library to get new final release.

[mawebb88]

Yesterday, user jakfish solved his printing problems on a EEE by installing CUPS 1.3.9. Read here. Then go here for details. You might want to make a backup copy of your pup_save file before starting, just in case.

Thanks rcrsn51 I will check it out. As I intimated getting printing working with the printer I already have will be a a big step to dumping Windoze.

Mike

[trio]

@ all who asked

I said not to put two 4.2 sfs in one partition because I had rc4 and final one the same partition in an usb frugal. When booting, it always boot rc4. I have to remove rc4 in order to boot final.they are in different directories of course, no pup save, and yes I know how to configure grub menu.lst

[trio]

I have lost Blnky! I stupidly made the mistake of on the right click options hiding both of my interfaces and now I would like to get the WiFi one back but can't figure out how to as Blinky has gone as one would expect. I searched for a configuration file eg. /root/.blinky but this lists (CSV) both interfaces but could not find where the hide option is stored?

Rgds Mike

Well, you should get blinky back after reboot

[jayargent]

I just want to say that I also have multiple 4.2 frugal installations on the same partition. What might not be generally known is there is code and a new parameter, psubok=TRUE, in Init (Thanks to Crash) that works with psubdir to really zero in on the subdirectory that contains the puppy files. This is documented in these two threads.:


http://murga-linux.com/puppy/viewtopic.php?t=38030

and

http://www.murga-linux.com/puppy/viewtopic.php?t=36703

I use these parameters plus PDEV1= which specifies the partition and really cuts down on the search time. Here is part of my menu.lst file:

Code: Select all

title Puppy 4.20
fallback 6
rootnoverify (hd0,4)
kernel /Puppy420/vmlinuz pmedia=idehd pdev1=sda5 psubok=TRUE psubdir=/Puppy420
initrd /Puppy420/initrd.gz

Hope this helps.....

Jay

[trio]

Not sure what the idea with the calendar with black numbers on dark part of desktop screen. On my old lcd screen with my old eyes, I CANNOT see the numbers. I had to create a png background that is bright yellow in order to see the white days and the little black numbers. Can the calendar widget be easily modified some way from some menu or config file so I can determine what colors of numbers should be?

Hi,

go to menu -- desktop -- pwidgets -- plugins -- theme
choose which color theme suits best for your eyes

another one is the Today widget, which will show only today's date (off course) with BIGGER numbers, should suit your eyes better

Cheers

[trio]

I just want to say that I also have multiple 4.2 frugal installations on the same partition. What might not be generally known is there is code and a new parameter, psubok=TRUE, in Init (Thanks to Crash) that works with psubdir to really zero in on the subdirectory that contains the puppy files. This is documented in these two threads.:


http://murga-linux.com/puppy/viewtopic.php?t=38030

and

http://www.murga-linux.com/puppy/viewtopic.php?t=36703

I use these parameters plus PDEV1= which specifies the partition and really cuts down on the search time. Here is part of my menu.lst file:

Code: Select all

title Puppy 4.20
fallback 6
rootnoverify (hd0,4)
kernel /Puppy420/vmlinuz pmedia=idehd pdev1=sda5 psubok=TRUE psubdir=/Puppy420
initrd /Puppy420/initrd.gz

Hope this helps.....

Jay

Hey, Thanks!
Is 4.2 capable of this? Did I miss something (I don't know this)? This should be a great feature and should be stated somewhere easily noticeable for users to see

[Grenville Grimace]

Gxine gives a fatal error - segmentation fault when it's launched.
SeaMonkey exits if you try to download a file with 'Save it to disk'.

(Edit) Sorry, please ignore.
Looks like my SD card install was corrupted.
A quick format and clean new install fixed everything.

[jayargent]

@Trio Yes, that code is included for the first time in the 4.2 Init. and I agree it should probably be documented more prominently.

[vanchutr]

@himagin
Thank you very much
Follow to your post, I'd made SCIM run in Puppy 420Final