Lucid Puppy 5.2 feedback and bug reports

[Jim1911]

Running Lucid 5.2 full install.
No problem getting Libreoffice installed from Quickpet.
All menu entries made. Works great.
Hope your full install is not on a partition formated ext4.
Ext4 not fully supported in Puppy.

Why,? Ext4 is faster and more stable. My full installation is on an ext4 partition. Ext4 has been fully supported by puppy for quite a while. However, presently, the only pup that I am aware of that supports a 4fs save file for a frugal installation is Lighthouse 5.0.2.

. . . .Added: I recommend that you follow the advice from the capable hands of Jim1911 in his post . . . .

Thanks for the kind comment.

Incidently, I have uploaded the latest LibreOffice 3.1.1 to playdayz, so it should be available for download using Quickpet after Quickpet is updated prior to release of Lucid-521.

[bigpup]

Why,? Ext4 is faster and more stable. My full installation is on an ext4 partition. Ext4 has been fully supported by puppy for quite a while. However, presently, the only pup that I am aware of that supports a 4fs save file for a frugal installation is Lighthouse 5.0.2.

I agree if you have a version of Puppy made from the latest version of WOOF.
But have you looked at the bug list for ext4 lately?
https://bugzilla.kernel.org/buglist.cgi ... onent=ext4
Also not sure how some of the programs will support a ext4 filesystem.

[eeepuppy]

I have installed puppy 5.2 on a usb hd and i tried to boot on my new HP Pavilion dv6 laptop with intel i7 and ATI graphic HD 5600. The startup was fine and all feel good, but at shut-down the Lupusave did not create and then each restart is equal to the first. It is possible to force the creation of the file lupusave?

[nooby]

I have installed puppy 5.2 on a usb hd and i tried to boot on my new HP Pavilion dv6 laptop with intel i7 and ATI graphic HD 5600. The startup was fine and all feel good, but at shut-down the Lupusave did not create and then each restart is equal to the first. It is possible to force the creation of the file lupusave?

Should be possible if you boot with puppy pfix=ram on the kernel line or at boot up hit Space bar on the keyboard or p for puppy and then write puppy pfix=ram and then hit enter?

Hope I remember it correctly. Then it should start all over and ask at reboot or shutdown if you want to save

[JJohnson]

Hello,

I successfully (and easily) installed Puppy 5.2 on a bootable USB Flash drive and it worked great. Thank you for an easy start.

Here are some of the issues I ran into (minor and otherwise).

1. When I first logged in, I had to connect to my wireless network and type in the WEP password. On the next reboot, I had to retype it. I was using the Simple Network tool. I'll try out the Network Wizard and see if it works better.
2. There is a save icon at the top middle of the desktop. I pressed it and it worked, but I'm not sure what it does for me? (Sorry if this is obviously in the documentation.)
3. Where is everything saved? I know it all goes back to my USB drive, but I'm looking for more details. For example, I installed Firefox. Does it go into my special 'SFS' file or elsewhere on the USB drive? Also, I created a text document in "~/my documents". Where does that get saved? Are there some technical (or semi-technical) documents I can read to better understand how Puppy works?
4. When I type 'modprobe' at the command line, I get an error message about an obsolete config file.
5. When I type 'lsusb -v' at the command line, I don't get any verbose messages. It appears that lsusb is using busybox and maybe there is a standalone lsusb that is more full featured? If my guess is correct, how can I find the package to install?

Thanks for helping me learn Linux!

--Jeff

[eeepuppy]

I have installed puppy 5.2 on a usb hd and i tried to boot on my new HP Pavilion dv6 laptop with intel i7 and ATI graphic HD 5600. The startup was fine and all feel good, but at shut-down the Lupusave did not create and then each restart is equal to the first. It is possible to force the creation of the file lupusave?

Should be possible if you boot with puppy pfix=ram on the kernel line or at boot up hit Space bar on the keyboard or p for puppy and then write puppy pfix=ram and then hit enter?

Hope I remember it correctly. Then it should start all over and ask at reboot or shutdown if you want to save

No the problem isn't starting the system. The problem start when the system shut-off because the lupusave file cannot be create (i don't know why). The system power off simply an not save the work done.

[bigpup]

How was Puppy installed to USB hard drive?
Give details in answer.

[Jim1911]

Why,? Ext4 is faster and more stable. My full installation is on an ext4 partition. Ext4 has been fully supported by puppy for quite a while. However, presently, the only pup that I am aware of that supports a 4fs save file for a frugal installation is Lighthouse 5.0.2.

I agree if you have a version of Puppy made from the latest version of WOOF.
But have you looked at the bug list for ext4 lately?
https://bugzilla.kernel.org/buglist.cgi ... onent=ext4
Also not sure how some of the programs will support a ext4 filesystem.

I didn't see any bugs reported for the kernel that the latest pups are using. I have been using ext3 and ext4 exclusively since 4.3 with no problems. That's not the case with ext2 partitions on which the corresponding 2fs files periodically crashed.

[eeepuppy]

I have installed puppy 5.2 on a usb hd and i tried to boot on my new HP Pavilion dv6 laptop with intel i7 and ATI graphic HD 5600. The startup was fine and all feel good, but at shut-down the Lupusave did not create and then each restart is equal to the first. It is possible to force the creation of the file lupusave?

Should be possible if you boot with puppy pfix=ram on the kernel line or at boot up hit Space bar on the keyboard or p for puppy and then write puppy pfix=ram and then hit enter?

Hope I remember it correctly. Then it should start all over and ask at reboot or shutdown if you want to save

No the problem isn't starting the system. The problem start when the system shut-off because the lupusave file cannot be create (i don't know why). The system power off simply an not save the work done.

It isn't the best way, but I solved the problem in this way:
I booted from cd on a desktop Puppy5.2 and I created a lupusave file with nothing.
I restarted the desktop and I copied the newly created file on a pendrive.
I inserted the pendrive in the laptop and I started Puppy 5.2.
Puppy5.2 recognized the lupusave file and uploaded it, so I completed the quick start Puppy. The first time you reboot, it seems that it is not done correctly the closure procedure. On the next reboot, the changes were saved and then took over the classic procedure at the end of the session.
I solved and I hope I have helped others to solve a problem, however, shows a bug of Puppy5.2 at least in the configuration I mentioned.

[average novice user]

I'm not sure if this is a bug with puppy 5.2 or something else. I have solved the problem my doing a fresh install, I'm just posting this as an FYI, if it is infact bug.

I was doing some research online, collecting info for a paper for school. at midnight exactly, while I was saving something to PDF format using the 'print to PDF' in the print menu. The computer completely locked up. I shut it off. When I rebooted, it wouldn't finish the 'incorrect shutdown' procedure, it would just stop half way and the cursor would appear. I'm not a programmer so I don't know what to write to make puppy boot up. So I booted up with the live CD, and then shut the computer off again took the live CD out. and booted up again, and it did. But I noticed little things that were different. The blue 'Grub' screen was a different resolution, and normally when loading puppy linux there are several usb ports that the computer recognizes, and it counts them 1,2,3,4,5,6. and then continues with the list of stuff it does. But it not do this after the 'incident'. Once puppy was fully booted up, it looked normal. And all my files were there and untouched. the browser I was using was opera. I have the firewall turned on, and I updated and scanned with clamscan and found nothing.

I have no idea what the heck happened, but the fresh install worked, everything is normal. Again if this is a bug or something I thought I should mention it. Sorry this post is sooooo long.

Average novice user

[Sage]

If you start up with the liveCD without using the cheat code pfix=ram, any installed system will be upgraded. At least that's the theory - in practice it can be imperfect, as I related yesterday. You should probably do what I did, ie overwrite the update with the PUI.
Your original issue would've been an app. feature. Pass.

[ariszlo]

There is kernel panic if Puppy is installed to a usb key, session is saved directly to an ext2 partition and Puppy is trying to load additional sfs files, e.g. java_jre-6u22-Lucid-sfs4.sfs or LibreOfc3-en-us_3.3.0.4_final_sfs4.sfs.

Used to be OK in Puppy 5.0.

More details here: loaded sfs causes kernel panic on ext2

[Sylvander]

Lupu-520

BUG:
1. When using Xfe...
If I right-click on a file and choose "Open with..."...
Only /usr/bin/mtpaint is listed...
And even if I add some other to the list [like Leafpad]...
And click the "Save" icon to save the change...
[I'm using a lupusave on an internal HDD, but changed a config setting in a file in the ISO so this Puppy treats the lupusave as if on a Flash Drive]
Next time I boot into the Puppy, there's still only /usr/bin/mtpaint listed.

[ttuuxxx]

you know the metacity package I made for lucid has been downloaded 110 times already, with those numbers you might want to make it default wm and use any old taskbar,on yeah by the numbers of views of the screenshot VS actual downloads. Its one out of ten people who viewed it, downloaded it.
http://www.murga-linux.com/puppy/viewto ... 288#487288 <-- post
http://gnome-look.org/index.php?xcontentmode=101 <-- hundreds of themes
ttuuxxx

[Salamander]

Been experimenting with making packages in 5.2 since I got my new netbook (and installed full hard-puppy on it), and I noticed there are a few quirks in the new2dir script. Most noticeably, the inner loop at line 290:

Code: Select all

#line 217...
cat ${RELPATH}/${EXE_PKGNAME}.files |
while read ONEFILE
do

##Lots of stuff here

#line 285...
 if [ "$EXESPLIT" = "yes" ];then
  mkdir -p "${EXE_TARGETDIR}/${ONEPATH}"
  cp -af "$ONEFILE" "${EXE_TARGETDIR}/${ONEPATH}/" 2>/dev/null
  [ $? -ne 0 ] && fixfilelistfunc $ONEFILE
  #fix for empty directories...
  cat /tmp/${EXE_PKGNAME}.dirs |  ## ---->  LINE 290  <------
  while read ANEWDIR
  do
   [ "`ls -1 $ANEWDIR`" = "" ] && mkdir -p ${EXE_TARGETDIR}${ANEWDIR}
  done
 fi
done

The loop will attempt to recreate every single directory that was created during installation, and it will attempt to do so for almost every single file the script processes.
The only time it is not executed is if the script has been told to split files into docs/development files/internationalisations folders and the file should be put in one of those three other folders.

Why is this a problem? When I was attempting to perform a medium install of TeX Live (about 26k files and 1700 directories), it took 8 seconds to process a single file. At that rate, it would take sixty hours to complete.

How can it be fixed?
Simply moving the inner loop to just before the outer loop starts changed that speed to more than three files every second.

[ttuuxxx]

Been experimenting with making packages in 5.2 since I got my new netbook (and installed full hard-puppy on it), and I noticed there are a few quirks in the new2dir script. Most noticeably, the inner loop at line 290:

How can it be fixed?
Simply moving the inner loop to just before the outer loop starts changed that speed to more than three files every second.

nice first post and a heck of a way to make a entry
do you have a new new2dir pet ? to test
ttuuxxx

[Sage]

Just now tried Lupu5.2.4beta in live mode. The speed of Opera is staggering (not interested in the also rans!) At 127Mb .iso, difficult to beat for comprehensiveness - why bother with the rest - well done Pd.

[Salamander]

do you have a new new2dir pet ? to test

Just to clarify, do you mean a pet which will replace /usr/bin/new2dir with the modified version?

[manelapb]

Hi everyone,

BUG: if a internal multi memory card reader connected by USB is mounted in the PC the part of "Waiting for usb partitions" of the step "Loading drivers needed to access disk drives" takes 17 seconds more (this wait are the red dots).

The problem is a new (puppy 5.2) wait for partitions in all USB sdX drives when most/all of them are empty so they will never show a partition. The timeout takes 17 seconds.

My SD/MMC/xD/MS/Pro/Duo/CF/Microdrive memory reader uses sdb, sdc, sdd, sde, and sdf, and last fourl of them are empty on boot

I boot from USB stick.


Ideas:
1) Remove that code
2) Add a boot parameter e.g.: "waitdev=sdb1" to wait only the USB drive we know it has the save file for people who really needs that.
In any case 17 seconds of timeout is too much... it should be reduced to lets say 5 seconds


How did I measured that? take a look to http://www.murga-linux.com/puppy/viewtopic.php?t=65726

[ttuuxxx]

do you have a new new2dir pet ? to test

Just to clarify, do you mean a pet which will replace /usr/bin/new2dir with the modified version?

yes for users to test. Its always easier with a pet
ttuuxxx