Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012

[shinobar]

I find that SFS-Load 1.3 sometimes has problems unloading sfs files in Lucid 5.2.8-004.

Unloading sfs may have some problem depends on many issue. I guess it is not the sfs_load version problem. SFS-Load 1.3 has many fix from v1.2, and i still have not found new bugs in v1.3.

# 28 Oct 2011 v1.2.9: support kernel 3.x and unionfs, special characters in path, profile.d
# 13 Nov 2011 v1.3: fix could not unload excess sfs(>6) with some version of busybox, PUPMODE=7(same as PUPMODE=2), error message at unload failure, wait before removing layer

Report on the sfs_load topic please if we can reproduce the issue.
http://www.murga-linux.com/puppy/viewtopic.php?t=64354

[James C]

Better late than never......fresh frugal install of the latest testing release.Zero problems so far on this Athlon XP box.

[Ray MK]

What would be nice for laptop users - Acpi.
ie - close the lid and laptop sleeps - open lid and it wakes up.

If one were to copy the files from another similar puppy to /etc, and add a few bits in startup, would it work?

Is there any danger of doing damage to the computer, bios, or similar?

Seem to remember trying this before on a much older laptop and it has not worked since - dead completely.

Not a biggy - but if it were built in - would be nice.

Using Opera-11.62.sfs to post this and all seems well - insanely fast.

So far for me Luvly Puppy - many thanks - regards - Ray

[Tman]

Unloading sfs may have some problem depends on many issue. I guess it is not the sfs_load version problem. SFS-Load 1.3 has many fix from v1.2, and i still have not found new bugs in v1.3.

Thanks for the info, Shinobar, I will reinstall SFS-Load 1.3 and see how it goes. The last issue occured when I was editing my own SFS files and was unmounting and remounting the SFS file a lot for testing and bugfixing.

I got an error message saying something like "the SFS could not unload from the unionfs." Then it ask me if I wanted to put it in the queue so that I could unload it after reboot. I found that message strange becuause I thought that only very old Puppies used unionfs..then aufs was adopted, until Barry decided to give unionfs another try in his newer Wary/Racy.

[shinobar]

I got an error message saying something like "the SFS could not unload from the unionfs."

The message maybe confusing, but it means both unionfs or aufs(AnotherUnionFS).
It occurs when the sfs is in use.

[Tman]

The message maybe confusing, but it means both unionfs or aufs(AnotherUnionFS).
It occurs when the sfs is in use.

Ah, now I understand. I maybe be nit-picking a little bit, but perhaps a statement such as, "Failed to unload the SFS file" would be less confusing.
SFS-Load is a great tool; Thank You for having created it.

[shinobar]

"Failed to unload the SFS file" would be less confusing.

Maybe.
By the way, restart X and try again if you failed to unload SFS. Sometimes it will resolve.

[bigpup]

Program updates:

PupClockset 1.9
http://www.murga-linux.com/puppy/viewtopic.php?t=61633

PupControl 1.8.9
http://www.murga-linux.com/puppy/viewtopic.php?t=61961

PupSysinfo 2.1.3
http://www.murga-linux.com/puppy/viewtopic.php?t=73101

[playdayz]

Google Chrome 17 for Lucid
This is the Stable (Official Release)

http://diddywahdiddy.net/Puppy500/Googl ... -Lucid.pet
.

[peebee]

Because I can't leave problems unsolved.....

In the light of the problems reported earlier with the Broadcom wl driver in the Testing ISO working but not surviving a reboot -

I've tried the following:

1. Made a vanilla, pristine, manual, frugal install of Lupu528-004
2. Blacklisted the b43 module
3. Installed broadcom_sta-5.6.48.36-i486.pet
4. Rebooted
5. Used Network Wizard to create a WPA-PSK-TKIP connection
6. Rebooted

And this time it's successful - see attached lsmod and dmesg outputs.

Note - the module I remarked on before - michael-mic - is now still there after the reboot....

Conclusion? the broadcom-sta driver is working OK with my BCM4311 with Version13 firmware but something in the combination of changes in the Testing ISO is not quite right.

If anybody can suggest the next "change" to make and test then I'll try that.

Cheers
peebee

[otropogo]

I'm having to switch to Windows and Adobe 8 more and more in order to search searchable pdf files, and often even to open them at all with the pdf viewer that comes with lupu 5.2.8.

Is there a compatible installation package that offers a more up to date viewer?

[smokey01]

Foxit is rather large but very good.

http://cdn01.foxitsoftware.com/pub/foxi ... .0.tar.bz2

[bigpup]

Foxit reader is also in Puppy Package Manager.

[otropogo]

Foxit reader is also in Puppy Package Manager.

Thanks, have installed Foxit 1.1 via the packet manager and will give it a try.

Have also found that the find function in ePDFviewer does exists, but it's a royal PIA to use, since there doesn't appear to be a way to configure it to display in the toolbar. Foxit 1.1 does have this option. I always assumed that any pdf viewer would show a search field by default, unless the pdf isn't searchable.

Hopefully it will be able to open more recent pdfs. Today I downloaded two pdf files from the Government of Canada, and ePDF was only able to open one of them.

I use Adobe Reader v. 8.1.2 in Windows, and it's hardly the latest version. The copyright says 2007... Yet I haven't come a across a pdf file yet that it wouldn't open.

Now to find the procedure for making foxit the default pdf reader...

[kevin bowers]

Now to find the procedure for making foxit the default pdf reader...

Open /usr/local/bin/defaulthandler as text; change "epdfview" to "foxit" or, I have had better luck with using the full path, usually /usr/bin/foxit or /usr/local/bin/foxit, wherever foxit installs to. Usually works, good luck!

ps. This is Linux--don't forget to save! Also, don't forget to boogie, but that's different.

[otropogo]

Now to find the procedure for making foxit the default pdf reader...

Open /usr/local/bin/defaulthandler as text; change "epdfview" to "foxit" or, I have had better luck with using the full path, usually /usr/bin/foxit or /usr/local/bin/foxit, wherever foxit installs to. Usually works, good luck!

ps. This is Linux--don't forget to save! Also, don't forget to boogie, but that's different.

Thanks for the suggestions, but no cigar...

I renamed defaulthander to .bak, then changed epdfview to foxit and saved as defaulthandler. Tried opening a pdf file, still using pdfview 0.1.7

Tried restarting X, same result.

Searched for foxit with pfind, and found three entries, /usr/bin/FoxitReader; /usr/lib/Foxit;/usr/lib/Foxit/FoxitReader

Edited defaulthandler replacing foxit with /usr/bin/FoxitReader, and saved.

Reopened pdf file, still using ePDFview. Rebooted system, checked text of defaulthandler, reopened pdf file - still us9ing ePDFview.

I noticed that pfind gives the path for ../bin/FoxitReader as /usr/bin/,

whereas it's actually /.usr/bin/, Have tried that also, and still no change.


I've looked for a separate default file for PDF viewers in the /usr/local/bin directory (as exist for other categories, like browser), but can't see any.

So now I'm puzzled. How is lupu getting its direction to open PDF files with ePDFview, given that the defaulthandler file doesn't contain any reference to it? And if it gets it's direction from elsewhere, what purpose does the defaulthandler file serve?

[sheldonisaac]

So now I'm puzzled. How is lupu getting its direction to open PDF files with ePDFview, given that the defaulthandler file doesn't contain any reference to it? And if it gets it's direction from elsewhere, what purpose does the defaulthandler file serve?

Apparently none?

See file://localhost/usr/local/apps/ROX-Filer/Help/Manual.html

Is there a tutorial that would have saved us this searching?

[otropogo]

So now I'm puzzled. How is lupu getting its direction to open PDF files with ePDFview, given that the defaulthandler file doesn't contain any reference to it? And if it gets it's direction from elsewhere, what purpose does the defaulthandler file serve?

Apparently none?

See file://localhost/usr/local/apps/ROX-Filer/Help/Manual.html

Is there a tutorial that would have saved us this searching?

I went, I saw, but I couldn't find "defaulthandler".

Meanwhile, I've found another promising method of getting nowhere. It's called "PuppApps" and sits in the Menu/utilities section. When you open it, it seems to show you the default app for a number of app categories, including one for /document/PDF Reader.

You're also able to change this setting, and I used the procedure to replace ePDFview with Foxit. I know it worked, because now, when I put the cursor on the pdf viewer icon in PuppApps, a popup displays "FoxitReader". There is further proof in that clicking on the icon opens a Foxit window. Very nice, and almost as easy as opening Foxit from the menu/documents/list, in fact a mere 100% more clicks (4 instead of 2), and a bit more searching through the longer list.

But is Foxit now the default pdf viewer? Noooooo!

So what is the purpose of the PuppApps module? Apparently, to provide a slower, more complicated way of opening an app than that provided by the main program menu.

[drblock2]

Try changing this file, replacing epdfview with FoxitReader:

Code: Select all

/root/.config/rox.sourceforge.net/OpenWith/.application_pdf/Open with PDF viewer

This should do it. You have to right click on the pdf icon in ROX and select "Open with PDF viewer" from the menu. Simply left-clicking on the icon (as you would for a jpg-file) does not seem to work anymore.

[sheldonisaac]

some snipping

How is lupu getting its direction to open PDF files with ePDFview, given that the defaulthandler file doesn't contain any reference to it? And if it gets it's direction from elsewhere, what purpose does the defaulthandler file serve?

See file://localhost/usr/local/apps/ROX-Filer/Help/Manual.html

I went, I saw, but I couldn't find "defaulthandler".

It seems that in Lucid 5.2.8, the defaulthandler file does _NOT_ control file associations.

Rather, the process would be as below; I'll do it now:
In rox, right-click on
/mnt/sdb6/jbl/User_Manual.pdf
Follow File 'User_Manual.pdf' to Set Run Action
In the space under Enter a shell command , replace existing command
with /usr/bin/nicoedit "$1"

Now left click opens pdf files with nicoedit.
(This was just a test. I'll now replace it with the actual pdf viewing software.)