Lucid Puppy 5.2 feedback and bug reports

[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

[Salamander]

Pet containing the modified new2dir script attached to this post.
After thinking about it a bit more, I realised that there is a slight logic difference in the two versions:
In the original, it would only create the directory structure in the executable package folder if there was at least one file that was not considered a doc, dev, or locale file (Which would be pretty rare that there isn't at least one file).
In the modified file, it will always create the directory structure in the executable package folder (Unless you tell the script not to bother with the exe package altogether).
Not a significant difference, but worth noting.

I'll continue looking into this script, as I think it may have a hatred for spaces and ampersands in some cases.

[ttuuxxx]

Pet containing the modified new2dir script attached to this post.
After thinking about it a bit more, I realised that there is a slight logic difference in the two versions:
In the original, it would only create the directory structure in the executable package folder if there was at least one file that was not considered a doc, dev, or locale file (Which would be pretty rare that there isn't at least one file).
In the modified file, it will always create the directory structure in the executable package folder (Unless you tell the script not to bother with the exe package altogether).
Not a significant difference, but worth noting.

I'll continue looking into this script, as I think it may have a hatred for spaces and ampersands in some cases.

Just tried it on 2.14X and its a lot quicker Thanks
ttuuxxx

[Salamander]

Found another one in the new2dir script.
If a folder is moved during the install phase, the script will lose track of all the files in it, and it will not be able to separate those files into their appropriate packages.

Should I create a new thread to post bugs related to this script (and bugfixes when I come up with them), or just keep posting them in here?

[Sage]

Update:
- except instability with Logitech Mouseman Wheel continues.
Used to happen with all sorts of distros, all sorts of mice years ago but the rest of the bunch, including Wary/Quirky & co. seem to have fixed it once and for all.
- new feature has crept in. During PUI, srx, where files are located from a pfix=ram, is not auto-mounted leading to a bunch of crazy messages.
- updating Opera to 11.01 leaves two entries in the menu: both are v11.01 ! And the Opera icon still appears against Pup-Advert-Blocker?

[01micko]

Sage, put on the extra-strength lenses ..

[Sage]

Yes, indeed! To see the intimate detail on the tiny Menu/Internet icon an electron microscope might be needed. But now I see it all at the alternative location you give. It's the wrong icon! See Fluppy13, which uses the industry standard 'HALT - Road Ahead' international standard.

[awagnerur]

Hey guys,

I think I might have open the thread in the wrong topic... could you have a look at it? I don't have a lot of time troubleshooting, and this issue is strange to me...

Thanks in advance,

awagnerur

[Luluc]

Well, I haven't had the time to read all the posts in this thread, but at any rate, if I say anything that has been said, it will serve to confirm other people's opinions.

I got sick of my big, fat, clumsy Ubuntu installation. I got sick of KDE, too. I am looking for alternatives. I've been testing Puppy for a few days and here are my impressions.

WHAT I LIKE:

* Very, lean and fast! Just what I was looking for.
* Excellent configuration tools. They really work! Amazing.
* More intelligent than most distros what with the modularity, the use of SFS and how it is not afraid of using/booting many different types of media (HD, CD, USB etc.) and the bold statement of running as root!

WHAT I DON'T LIKE:

* The menus are an incredible mess. Holy cow, it's all over the place, and some menus have submenus, and the configuration tools are straightforward, but convoluted at the same time because there are so many tabs and submenus and options and detours and simply running of programs/utilities in the configuration sections... Aaaargh! Very, very messy.

* Lack of packages. The Ubuntu compatibility doesn't quite cut it. For example, I really need VIM and cryptsetup/LUKS. There are no Puppy packages and I can't make these work correctly from Ubuntu. I really would like to see more packages. That was the number one reason why I chose Ubuntu as my current distro. Please clap your hands and do the Steve Ballmer dance with me: packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages...

WHAT I LOATHE:

* The package management system. Abysmal. The UI is very badly designed, very clumsy, doesn't adapt well to my screen size, I can't resize/adjust panes properly, the amount of information is not good enough (I am used to Ubuntu's Adept Manager)... Then I select one package and it takes too long to install. Too many steps and waiting around in the process. Even worse, I can only install ONE at a time! No batch operation. If I could at least select a dozen and go do something else while Puppy chugs along its lengthy installation process (like APT), it wouldn't be as brutal. But noooo, the thing forces me to sit through the whole ordeal because it only installs one package at a time and also because this annoying child keeps asking me to click OK in 3 or 4 dialogs for every each damn package... Grrrrrrr! This is even worse than Windows!

Being able to use Ubuntu repositories is nice, but besides the compatibility problems (messy dependencies, for example), it is not smart. We have to download the list of packages first, fine, APT does that too. But then it downloads and compiles the list... Man, that took forever! Excruciating. Then I removed two repositories and added other two. What happened? The stupid procedure went over the entire process again, not only for the new repositories, but also for the old ones again, again, again... And it took forever plus inifinity! Awful. Just damn awful.

Despite the problems, I love this distro and I want to use it. I can live with the messy menus and even the horrible package manager since I don't install new software that often. The deal breaker for me so far is the lack of support to cryptsetup/LUKS. I absolutely need that, really can't live without it.

Thank you for this opportunity.

[ttuuxxx]

Well, I haven't had the time to read all the posts in this thread, but at any rate, if I say anything that has been said, it will serve to confirm other people's opinions.

I got sick of my big, fat, clumsy Ubuntu installation. I got sick of KDE, too. I am looking for alternatives. I've been testing Puppy for a few days and here are my impressions.

WHAT I LIKE:

* Very, lean and fast! Just what I was looking for.
* Excellent configuration tools. They really work! Amazing.
* More intelligent than most distros what with the modularity, the use of SFS and how it is not afraid of using/booting many different types of media (HD, CD, USB etc.) and the bold statement of running as root!

WHAT I DON'T LIKE:

* The menus are an incredible mess. Holy cow, it's all over the place, and some menus have submenus, and the configuration tools are straightforward, but convoluted at the same time because there are so many tabs and submenus and options and detours and simply running of programs/utilities in the configuration sections... Aaaargh! Very, very messy.

* Lack of packages. The Ubuntu compatibility doesn't quite cut it. For example, I really need VIM and cryptsetup/LUKS. There are no Puppy packages and I can't make these work correctly from Ubuntu. I really would like to see more packages. That was the number one reason why I chose Ubuntu as my current distro. Please clap your hands and do the Steve Ballmer dance with me: packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages, packages...

WHAT I LOATHE:

* The package management system. Abysmal. The UI is very badly designed, very clumsy, doesn't adapt well to my screen size, I can't resize/adjust panes properly, the amount of information is not good enough (I am used to Ubuntu's Adept Manager)... Then I select one package and it takes too long to install. Too many steps and waiting around in the process. Even worse, I can only install ONE at a time! No batch operation. If I could at least select a dozen and go do something else while Puppy chugs along its lengthy installation process (like APT), it wouldn't be as brutal. But noooo, the thing forces me to sit through the whole ordeal because it only installs one package at a time and also because this annoying child keeps asking me to click OK in 3 or 4 dialogs for every each damn package... Grrrrrrr! This is even worse than Windows!

Being able to use Ubuntu repositories is nice, but besides the compatibility problems (messy dependencies, for example), it is not smart. We have to download the list of packages first, fine, APT does that too. But then it downloads and compiles the list... Man, that took forever! Excruciating. Then I removed two repositories and added other two. What happened? The stupid procedure went over the entire process again, not only for the new repositories, but also for the old ones again, again, again... And it took forever plus inifinity! Awful. Just damn awful.

Despite the problems, I love this distro and I want to use it. I can live with the messy menus and even the horrible package manager since I don't install new software that often. The deal breaker for me so far is the lack of support to cryptsetup/LUKS. I absolutely need that, really can't live without it.

Thank you for this opportunity.

too bad your not using 2.14X I compiled it and combined it all into one single pet install, ummm Ubuntu this and that, baaaaaaa humbug pet's are easier when you do this http://www.murga-linux.com/puppy/viewto ... 782#505782
ttuuxxx

[Lobster]

The menus are an incredible mess. Holy cow

They are. Puppy is bloated or to be more precise well endowed . . . m m m
We haz loads of software . . . that is wot I mean.

You could install wbar

I believe in the future we need to cut out everything that is now available in Pupcontrol
I have also mentioned the 3 layers of menu as overkill but this is because of woof and compatibility with multiple window managers.

One possibility is 3 types of menu
beginner / essentials
intermediary / more apps
advanced / full

Usability and easy packages is an important goal.
Quickpet I believe is a step in the right direction

We have to be a bit geeky
otherwise everyone will use Puppy
and then how can we say:

Puppy Linux
My OS is better than yours