1.0.6 final bugs

Message

GuestToo · #1 Post by **GuestToo** » Tue 08 Nov 2005, 22:34

these wrappers use $@ to pass parameters, so if there are spaces in the PATH to the file(s) passed as parameters, it won't work

defaultcalendar
defaultcontact
defaultemail
defaulthtmleditor
defaulttexteditor
defaultwordprocessor

for example, if you click readme.txt in /mnt/home/My Documents, nothing will happen

of course, changing $@ to "$@" fixes the problem

BarryK · #2 Post by **BarryK** » Tue 08 Nov 2005, 23:47

Thanks, will fix.

...no, I just checked.
they already have quotes around the $@.
This must be an upgrade problem, the new ones not overwriting the old ones.

GuestToo · #3 Post by **GuestToo** » Tue 08 Nov 2005, 23:50

i could put a bugfix in SP106

GuestToo · #4 Post by **GuestToo** » Tue 08 Nov 2005, 23:52

burniso2cd has the same problem, parameters are passed using $@

BarryK · #5 Post by **BarryK** » Tue 08 Nov 2005, 23:58

they already have quotes around the $@.

I take that back. I put quotes in the original files, but not in all cases in the
post-install scripts, pinstall.sh, in each unleashed package.
Okay, I'll go through the packages now, find the culprits, also burniso2cd.

...so, looks like a candidate for the service pack.

Note, some of them, like defaultpaint, should have the quotes, do for me anyway, as they were not overridden by any pinstall.sh script.

#6 Post by MU » Wed 09 Nov 2005, 00:29

Pmount shows completely wrong values on my system.
The old one worked ok.

It does not display all drives, and it says every drive is 1984 M in size.

I just wanted to submit a screenshot with MUT (works mostly correct) for comparison, but MUT does not start with the KDE-usr_more.sfs

I will add one later.

Mark

#7 Post by MU » Wed 09 Nov 2005, 01:56

http://noforum.de/pics/pmountbug.jpg

Please tell me what you need for additional info.
MUT does not display hda10, but that is since Pupy 104.

Maybe my corrupt partitiontable confuses it, but the old version worked ok.
This is what I get on the commandline:
# pmount
/usr/sbin/pmount: line 36: 11166 Terminated xmessage -bg "#ff00ff" -title "Puppy drive mounter" -center -buttons "" "Please wait for the usb-storage driver to load...

Note: A USB1 interface takes longer to initialise than a USB2 interface,
in the former case up to 25 seconds, in the latter about 4 seconds.
If a plugged-in USB drive does not show up in the next window, click
the REFRESH button to probe the hardware again."
Warning: ignoring extra data in partition table 9
Warning: extra link pointer in partition table 9

Mark

GuestToo · #8 Post by **GuestToo** » Wed 09 Nov 2005, 05:07

i put a fix for the default-wrappers-spaces bug in my SP106 package

i uploaded an (experimental) pmount bugfix dotpup-package here
if it seems to work ok, i could add it to SP106

it only fixes the incorrect size information bug ... it does not fix problems with non-standard/corrupt partition tables

i don't think pmount tries to show you every partition you might have on your drive

#9 Post by MU » Wed 09 Nov 2005, 05:31

yes, that fixes the size

Thank you, G2

> i don't think pmount tries to show you every partition you might have on your drive

Hm, but the old version in Puppy 105 did.
So is it intended not to display all, or is it a bug?
i would prefer to see all.
It is not that important, as there is MUT, but I thought I better let you know.

Mark

GuestToo · #10 Post by **GuestToo** » Wed 09 Nov 2005, 06:30

partview does not display the used and free sizes ... it displays 1/2 the values

i don't know if this is a bug or an intentional feature

anyway, i uploaded a hacked version that displays the true values, here

i could put it in SP106 if it actually is a bug, and if my bugfix seems to work ok

noip · #11 Post by **noip** » Wed 09 Nov 2005, 23:07

HD Install / MUT bug

MUT
MUT will not recognize /dev/hdb10 (I notice above that it will not recognize /dev/hda10 either). Pmount does.

HD Install
Sadly, I chose to install Puppy to /dev/hdb10. The HD install script will not recognize /dev/hdb10 and fails. HOWEVER, if you use the "install-hd2.sh" script that was introduced as a bug-fix in 1.0.5 then everything is OK.

Rgds

GS

"vp&ftgs"

BarryK · #12 Post by **BarryK** » Thu 10 Nov 2005, 00:48

noip wrote:HD Install
Sadly, I chose to install Puppy to /dev/hdb10. The HD install script will not recognize /dev/hdb10 and fails. HOWEVER, if you use the "install-hd2.sh" script that was introduced as a bug-fix in 1.0.5 then everything is OK.

You mean, the install-hd2.sh in 1.0.6 is not work, but the bugfix one will?
...hmmm, that's odd. Do you have the bugfix one handy and can post it,
I'll need to compare the two, see what I neglected to fix.

klhrevolutionist · #13 Post by **klhrevolutionist** » Thu 10 Nov 2005, 00:51

I installed puppy to it's own partition with no problems.

GuestToo · #14 Post by **GuestToo** » Thu 10 Nov 2005, 07:01

rpm2cpio is still broken

my unrpm dotpup still works ok

# ldd -d `which rpm2cpio` | grep not

libbz2.so.1.0 => not found
librpm-4.2.so => not found
librpmdb-4.2.so => not found
librpmio-4.2.so => not found

libbz2.so.1.0 just needs to be symlinked

Guest · #15 Post by **Guest** » Thu 10 Nov 2005, 07:08

Barry,

Here's the script I'd kept from 1.0.5. I tried the HD install script in 1.0.6 twice, and it failed both times when it couldn't recognize /dev/hdb10. However, trying the script that I'd downloaded for 1.0.5 to allow it to install worked like a charm first time.

Not sure why, since I thought the CD one would work ....

Rgds

GS

vp&ftgs

noip · #16 Post by **noip** » Thu 10 Nov 2005, 07:10

Note to self ....

Remember to log in before posting

GS

vp&ftgs

#17 Post by MU » Thu 10 Nov 2005, 07:12

There is a dotpup with these libs, but it is quite huge

Code: Select all

# pwd
/mnt/hda8/usr/local/dotpups/rpm4.2libs/FILESYSTEM/usr/lib
# ls -l
lrwxrwxrwx    1 root     root           15 Oct  1 09:10 libbz2.so.1.0 -> libbz2.so.1.0.0
-rwxr-xr-x    1 root     root        65676 Oct  1 09:10 libelf-0.84.so
lrwxrwxrwx    1 root     root           14 Oct  1 09:10 libelf.so.1 -> libelf-0.84.so
-rwxr-xr-x    1 root     root       309104 Oct  1 09:09 librpm-4.2.so
-rwxr-xr-x    1 root     root       951080 Oct  1 09:09 librpmdb-4.2.so
-rwxr-xr-x    1 root     root       361896 Oct  1 09:09 librpmio-4.2.so

http://www.murga.org/%7Epuppy/viewtopic ... rpm4+2libs

jcoder24 · #18 Post by **jcoder24** » Sat 12 Nov 2005, 13:35

I was able to print from 1.0.6 RC with the builtin printing support easily without any problems. However, with the final release I got errors where gs was unable to find some libraries. I had to copy the following files to /usr/lib

/.usr_cram/X11R6/lib/libSM.so.6
/.usr_cram/X11R6/lib/libICE.so.6
/.usr_cram/X11R6/lib/libXt.so.6
/.usr_cram/X11R6/lib/libXext.so.6
/.usr_cram/X11R6/lib/libX11.so.6

Has anything changed related to printing since the rc?

BarryK · #19 Post by **BarryK** » Sat 12 Nov 2005, 15:15

Nothing has changed, or rather nothing that I would think would make any difference, between 1.0.6rc and 1.0.6.

gs is okay on my system.
Those libraries are in /usr/X11R6/lib and gs finds them ok.

Try this:
# echo $LD_LIBRARY_PATH
...is /usr/X11R6/lib in the path?

jcoder24 · #20 Post by **jcoder24** » Thu 17 Nov 2005, 02:27

I forgot to mention that I was using a multisession cd.
The path looked fine on the cd that had the problem.

Strangely enough I burnt a new cd and had no problems.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

1.0.6 final bugs

1.0.6 final bugs

no go

Printing problem in 1.0.6 final