Lucid Puppy 5.2.1beta "256"

Playdayz has announced beta release "256", which may be the last beta before Lucid Puppy 5.2.1-RC:

http://murga-linux.com/puppy/viewtopic.php?t=65136

I'm downloading it now, will help with testing it. Actually, what has mostly motivated me to do this is that Buildroot is more Ubuntu-friendly and not so Wary-friendly. There seem to be two main problems:

1. Buildroot is very sensitive to package versions in the host, and some of Wary's packages are too old.

2. Buildroot gets upset with the location of Xorg in /usr/X11R7 in Wary, even though I have symlinks from the "normal" /usr paths.

So, I am going to run Lucid 256, and do a build with Buildroot. This will be testing Lucid at the same time and I will report any issues.


Posted on 20 Mar 2011, 20:03


Comments:

Posted on 20 Mar 2011, 22:50 by BarryK
Running Luci
My first feedback: a lovely experience

Everything is very streamlined, very nice first-time impression. The getting-started GUIs are superb. So far, it seems to me like release-quality.



Posted on 20 Mar 2011, 23:18 by bigpup
Upgrade testing
Barry,
There has been a lot of testing in Lucid 5.2.1 concerning upgrading from one version to the next.
You can look threw the last 20 pages or so of the topic and see various examples of the results. Basically, results are hit or miss. Really needs your input.


Posted on 21 Mar 2011, 2:10 by BarryK
No UTF-8 checkbox
When I ran "make" for Buildroot, it immediately exited with an error message that the host must have UTF-8 locale enabled.

I have got Luci set to en_US.

So I clicked on the 'setup' icon on the desktop, and got to the 'Country setting' window. It has a dropdown list to choose English/US, English/AU, etc., however no checkbox to enable UTF-8.

What I had to do was open a terminal and type "chooselocale", which is the original Woof locale chooser GUI app. This does have a checkbox for UTF-8.

I then restarted X, and Buildroot is now chugging along, compiling packages.

This is probably more of an annoyance thing for a few people who know that they must have UTF-8 enabled. Most users won't even be aware of the issue.



Posted on 21 Mar 2011, 2:19 by BarryK
No xload in tray
Ha ha, it's only a small usability preference... I have Buildroot running in a terminal, hidden behind my browser window, and I keep glancing down to the xload applet in the tray, to see if the CPU is still busy compiling -- but it isn't there. So, I have to click on the rxvt tab in the tray to bring it to the top so that I can see how it's coming along.





Posted on 21 Mar 2011, 3:31 by playdayz
utf8
Ah, If you change the language you get the utf8 checkbox. I think it should be default utf8 but I must have overlooked something. Thanks for noticing.



Posted on 21 Mar 2011, 7:59 by playdayz
xload lives in jwm
You can use Desktop -> WMSwitcher to switch to JWM, complete with xload!

No xload in tray

Ha ha, it's only a small usability preference... I have Buildroot running in a terminal, hidden behind my browser window, and I keep glancing down to the xload applet in the tray, to see if the CPU is still busy compiling -- but it isn't there. So, I have to click on the rxvt tab in the tray to bring it to the top so that I can see how it's coming along.



Posted on 21 Mar 2011, 8:53 by BarryK
The answers
playdayz,
Thanks very much for the reply. Yes, I didn't change the default en_US, just clicked the OK button. But if I had changed it, then I should have got the UTF-8 option. Ok. Xload, still available, good!

Buildroot has been running all night, and I have been playing around doing things in Luci, it looks good to me!



Posted on 21 Mar 2011, 10:11 by playdayz
I love to show it off ;-0
But if I had changed it, then I should have got the UTF-8 option.

Yes, Even if you had selected English from the drop down menu the next screen would have had the UTF-8 box. It's late to change this--I might add some explanatory text.

Ok. Xload, still available, good!

Also, fbpanel in Openbox has its own cpu monitor. Desktop setting -> fbpanel config -> plugins -> General OK


Posted on 22 Mar 2011, 2:08 by GCMartin
Taking advantage of PCs with lots of RAM
Barry, I don't know if you've seen this forum discussion. Might be something to consider or advise.

Hope this helps


Posted on 23 Mar 2011, 11:13 by BarryK
Luci sound bug
I have tested Luci 256 on one of my PCs that has a particular sound bug. At first startup of Luci, the barks don't stop. I have to open a terminal, then kill 'aplay'.

This is a bug with the ALSA driver for certain saound hardware, I'm not the only one who has this problem. Sound does play properly in the media players though.

The thing is, this problem was solved long ago in Woof. The /usr/sbin/delayedrun script kills aplay a few seconds after it starts, ensuring that only the first 2-3 barks will be heard.

It seems that Luci has replaced the default delayedrun script with something else that does not kill aplay. I suggest that the appropriate code snippet be imported into Luci's script.



Posted on 23 Mar 2011, 23:40 by playdayz
Thanks
[ "`pidof aplay`" != "" ] && killall aplay


Posted on 2 Apr 2011, 17:11 by 01micko
lupu-525 is out
Barry,

I guess you haven't checked your PMs/gmail.
Playdayz has announced lupu-525 as 'official'.
After a couple of false starts the ver num ended up as 525.. better anyway as it is a little more than a bugfix.
Cheers