Puppy 4.3 Beta2 -- bugs and reports

[veronicathecow]

Frugal on Atom (1.6ghz) based machine with 2gb RAM

Major problem for me is that when using Puppy for some reason it sets the superblock time in the future and causes a fsck to occur on all disks meaning a 25 minute delay before being able to use other linuxes. Any one else having this problem? Time zones for all 3 OS's seem correct and I don't get that problem going from Sidux to PClinuxos or back the other way.


MP4 still no link to Gxine

Flac works fine (Thanks)

CUPS did not give option to choose .ppd file (Perhaps not available in this version of cups?)

Am trying to run Samsung 2510 (Can use Splitx 2. ML-2150 (Not a typo) driver if I can choose it.

At boot "Searching for Puppy files on HDD takes over 10 seconds out of total 32 second boot time. Any way around this?

Thanks for tip about easy change of icons, works a treat.

Everything else nice and fast

It's a while since I have used Puppy properly and it is now so much more polished, well done to everyone!
Tony

[mawebb88]

Looks good. I like the new theme.

Had to use ndiswapper as the loaded ath5k module (on my Acer 5100) would not find my router

The Alsamixer now has a Master volume (did not before on earlier versions of 43 at least for me).

Can't get any of the players to work with my playlist.m3u's. Gxine in 412 works fine with these.

Pnethood continues to work fine using cif's with my Samba LANdisk

Rgds Mike

[ttuuxxx]

Er... you would not believe how easy woof is... no kernel compiling involved at all! As a matter of fact.. no as in zero.. compiling by user.. all done in the scripts!

(Sorry for getting off topic)

Mick your like a newbee in Candy store, I know compiling isn't one of strong points, so yes woof is excellent, I always figured you would of tried it sooner for your retro pc. you could really make a nice small version for it., with a retro kernel
ttuuxxx

[BarryK]

darwin

I just converted and load OpenOffice 3.0 sfs, all works perfectly, including menu items and desktop icons

Trio,
Where can I download the working oo sfs from?

[BarryK]

jakfish

One thing.. when BarryK uploads a version (be it a beta or whatever) he usually uploads a 'woof' to go with it. That 'woof' usually has BarryK's latest configuration, such as, what distro, what packages ...etcetera .. (without going into too much detail.. it is a 4.3beta2 bug thread!). BarryK also offers a variety of kernels and of the four or five woofs I've built k2.6.25.16 has always been an option.

So, if you don't mind downloading a few hundred meg and have a spare five hours and a fastish (1.5GHz plus with 512 ram) box, build 4.3 yourself with the older kernel. It will come out essentially the same but may have bugs.

BarryK

I notice the gtk theme is identical to the one in upup-476. Maybe.. (and there is time) you should put out a request for a matching gtk theme for the Raymond Levang (provided by zigbert) wallpaper. Those blokes in the eyecandy thread go nuts when there is a challenge thrown out! Trio has made it easy too, with his 'maker' series, 'JWM theme maker', 'gtk theme maker'.. etc.

Just some food for thought.

Yes certainly! If anyone wants to mess around with the default theme in 4.3beta2 and improve it, go for it!
Otherwise, I may just leave it as is for the final!

[BarryK]

gtkam hangs and has to be killed after accessing my canon ixus750 (SD550).
it correctly identifies and connects to the camera. I descend the directory tree in the left pane, then once i clikc on the "100CANON" directory the "initialising camera" progress bar fills, stops and then the whole application is dead and has to be killed.
according to the output of dmesg it seems to have segfaulted

Gtkam has been flakey as long as we have used it. This has been going on for a long time, and with each new release I have hoped it would become more stable, but no.

I think we need to write our own equivalent.
There is a commandline utility that apparently works well, so we could knock up a GUI for it.

[BarryK]

oops, my bad - completely missed the "you must not use a FAT directory" warning when upgrading old sfs to sfs4 - have now done so and all seems well. Perhaps we should make it flash a bit and shout "no really, all your simlinks will break if you do not obey this simple command"

Not just symlinks, file permissions may also get corrupted, which will break some apps.

[BarryK]

Er... you would not believe how easy woof is... no kernel compiling involved at all! As a matter of fact.. no as in zero.. compiling by user.. all done in the scripts!

(Sorry for getting off topic)

Mick your like a newbee in Candy store, I know compiling isn't one of strong points, so yes woof is excellent, I always figured you would of tried it sooner for your retro pc. you could really make a nice small version for it., with a retro kernel
ttuuxxx

Yes, and I must get onto adding dependency checking into Woof, to make it easier to choose a cutdown selection of packages. It's on the to-do list.

[shinobar]

can be not a bug but for an information:

i have 2 HDD on IDE primary master and slave.
The 4.3bata1 shows all partitions on HDDs,
But 4.3beta2 does not show some partitons on the slave HDD.

sdb1, sdb2 or sdb3 could not see at 4.3beta2 but sdb6 sees.
'probepart' reports sdb1-3 file systems 'none'.
'fdisk -l /dev/sdb' replies nothing.

pmount does not show sdb1, sdb2 or sdb3.
i ticked 'mut' on pmout settings.
then pmount shows all partions.

then after, 'probepart' and 'fdisk -l /dev/sdb' works correctly,
and all the drive icons appeared on the desktop.

at first:

Code: Select all

# probepart
/dev/sda1|vfat|41029946
/dev/sda2|ext3|41013944
/dev/sda3|vfat|894724110
/dev/sdb1|none|208782
/dev/sdb2|none|43006004
/dev/sdb3|none|43006004
/dev/sdb4|none|2
/dev/sdb5|swap|4192902
/dev/sdb6|ext3|886354182
/dev/sr0|iso9660|237856
# fdisk -l /dev/sdb
# 

(...no reply)

after 'mut' ticked on pmout settings:

Code: Select all

# probepart
/dev/sda1|vfat|41029946
/dev/sda2|ext3|41013944
/dev/sda3|vfat|894724110
/dev/sdb1|ext3|208782
/dev/sdb2|ext3|43006004
/dev/sdb3|ext3|43006004
/dev/sdb4|none|2
/dev/sdb5|swap|4192902
/dev/sdb6|ext3|886354182
/dev/sr0|iso9660|237856
# fdisk -l /dev/sdb

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          13      104391   83  Linux
/dev/sdb2              14        2690    21503002+  83  Linux
/dev/sdb3            2691        5367    21503002+  83  Linux
/dev/sdb4            5368       60801   445273605    5  Extended
/dev/sdb5            5368        5628     2096451   82  Linux swap / Solaris
/dev/sdb6            5629       60801   443177091   83  Linux

[trio]

Barry,

I downloaded OO 3.0 sfs a long time ago, but it may be came from this link, (I hope):
http://www.murga-linux.com/puppy/viewtopic.php?t=34325

[arby]

I just now got the chance to get beta2 on disk and booted...
pup-424.iso prints over my LAN again without issues.

Must've been the 6.29.6 kernel causing my previous issues.

(This is just the 424.iso, no additional packages)

Yay!

[rerwin]

The HSF modem dialup hang/freeze is due to an error in the firmware tarball pinstall script. The line, "cd /" should be "cd /etc/hsfmodem".

Attached is a patch/workaround containing the corrected tarball and logic to enable a re-initialization of the modem upon reboot. Anyone with an HSF modem should install this dotpet and reboot, for it to take effect.

This problem probably is not a factor in the HDA soundboard issue posted by tlchost..

Barry: please update the hsfmodem firmware tarball either by substituting the version in the dotpet, or correcting the pinstall.hsfmodem.sh file in the "master" tarball. Thanks.
Richard

[charlie6]

Hi,
I wrote this post as this happened repetitively on 2 different PC's with 4.3beta2 (frugal installed) and eth0 network connection.

This is the first time since my "puppy conversion" that I get this on two different PC's with the same ethernet hardware. So I believe that the hardware is not to consider in this problem.

What happens:
- running Network Wizard (or click on 'Connect' icon), select network LAN;
- first step: there click on 'eth0' for eth0 interfacing;
here sometimes I get a dialog box displaying the interfacing progress (horizontal bar); sometimes not, as it is quite instantaneous (as it was the case on former puppy issues); sometimes it looks so frozen...that I end and start again the process...one time I even went to reboot...!;

- next step is DHCP connection: same behaviour: sometimes fast, (sometimes very) slow process, and sometimes frozen...reboot seems to be the only way to get DHCP.
One time I got the internet connection cut while browsing across the web...needed to reboot to get it runnig again!

Hope this can help.
Cheers, Charlie

[aragon]

I think we need to write our own equivalent.
There is a commandline utility that apparently works well, so we could knock up a GUI for it.

gphotofs would be nice for that, as it mounts your cam to the 'regular' filesystem using fuse. maybe this could be used to simply add a cam-mount to pmount.

aragon

[Dpup]

Have several zd1211rw based USB wifi adapters. These have worked very well since Puppy 3.01. And they work fine in Puppy 4.3b1 advanced kernel. However in Puppy 4.3b2 netwiz, fails to detect any wireless, or after several trys detects router 15 feet away, shows a weak signal, and if it connects has a very slow transfer rate.

Have tried several different adapters on several different desktop PC's that all worked in Puppy 4.3b1 advanced and all have the same problem in Puppy 4.3b2.

Very strange, but several other USB wifi adapters not based on the zd1211rw worked fine in both Puppy 4.3b1 and 4.3b2. And I have several netbook computers that work fine in Puppy 4.3b2.

[richwa4sxz]

BarryK,

I've tried this from console and as part of the setup, on several various computers, and no sound card is ever detected by the script. The sound cards all have been detected at boot and are usable by running the alsamixer from the speaker icon or console. This seems to be something new since changing the alsa version to the newer one.

Have run this beta on a variety of older P3 & P4 computers and have not run into any other setup issues, using a manual frugal installation to HD.

Rich

[panzerpuppy]

@BarryK: Looks like happypuppy found a way to reproduce the JWM theme changing bug. See the post in the dev blog.

I always edit the .jwmrc-tray file first to remove unnecessary stuff.
For example, I don't need asapm (i don't use a laptop), xload (I don't need it) ,the pager (i don't use virtual desktops) and the show desktop icon ,so I edit .jwmrc-tray and remove the stuff.

Then when I use the GUI to change the theme, the taskbar disappears

As happypuppy said in the blog post, this worked perfectly in Puppy 4.1.2.

[edoc]

Is the ath9k driver module for the newer "n" wifi devices included?

Also, for my Puppy-newbie friend - is there a driver for the Buffalo wli-u2-g300n?

Or does he have to do the ndiswrapper thing?

[panzerpuppy]

More bugs:

- In PupX (set properties of X) , unchecking the 'enable screen saver' checkbox has no effect. The screensaver still kicks in after a while.

- Some apps behave strangely when locale is set to anything but en_US:
i.e. ExpenseTracker refuses to save expenses.

- Nathan Wallpaper Setter doesn't work (EDIT: fixed with the .PET patch)

P.S. 'Top' (the process viewer) looks much better / easier on the eyes with a white background.
It's a simple fix: just edit /usr/share/applications/Top-view-running-processes.desktop and change the bg color from #c0c0c0 to #ffffff


------------------
panzerpuppy

[James C]

The pet to fix the wallpaper setter is already posted earlier in this thread.