Lucid Puppy Revitalized as 5.2.8.7 - Nov., 2017 - Final
Precise is new dog in Puppy kennels. Developed to support the newest hardware. Newest Linux kernel, etc... However being so new it is not fully bug fixed and tested.
Does implement newest changes to Puppy core programs.
Lucid Puppy has been developed over the past 3 years and been tested to the max.
Closes thing to a long term support version of Puppy.
Tries to stay updated to the newest changes to Puppy core programs that work.
Has had very good support from everyone, in trying to make it 100% bug free.
Has good software support.
Generally supports a large range of hardware from very old to very new.
Supporting the very new is the biggest issue, but newer versions of Puppy do that.
Does implement newest changes to Puppy core programs.
Lucid Puppy has been developed over the past 3 years and been tested to the max.
Closes thing to a long term support version of Puppy.
Tries to stay updated to the newest changes to Puppy core programs that work.
Has had very good support from everyone, in trying to make it 100% bug free.
Has good software support.
Generally supports a large range of hardware from very old to very new.
Supporting the very new is the biggest issue, but newer versions of Puppy do that.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Lucid Puppy Revitalized as 5.2.8.6!
Manual frugal install to an 8gb SDHC card, computer is an AAO 721-3801
netbook.
video-info-glx 1.5.3 Thu 28 Nov 2013 on Lucid 528 Linux 2.6.33.2 i686
5.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200]
oem: ATI ATOMBIOS
product: RS880M 01.00
X Server: Xorg Driver: fglrx
X.Org version: 1.7.6
dimensions: 1024x600 pixels (270x158 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4200 Series
OpenGL version string: 3.3.11672 Compatibility Profile Context
AMD Athlon(tm) II Neo K125 Processor
Core 0: @1695 MHz
Network controllerBroadcom Corporation BCM43225 802.11b/g/n (rev 01)
The network setup with SNS,sound is working.
I compiled the amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
proprietary driver after installing the xorg hi driver in quickpet.
5.2.8.6 is working great so far.
netbook.
video-info-glx 1.5.3 Thu 28 Nov 2013 on Lucid 528 Linux 2.6.33.2 i686
5.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200]
oem: ATI ATOMBIOS
product: RS880M 01.00
X Server: Xorg Driver: fglrx
X.Org version: 1.7.6
dimensions: 1024x600 pixels (270x158 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4200 Series
OpenGL version string: 3.3.11672 Compatibility Profile Context
AMD Athlon(tm) II Neo K125 Processor
Core 0: @1695 MHz
Network controllerBroadcom Corporation BCM43225 802.11b/g/n (rev 01)
The network setup with SNS,sound is working.
I compiled the amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run
proprietary driver after installing the xorg hi driver in quickpet.
5.2.8.6 is working great so far.
- Attachments
-
- screenshot.jpg
- (42.48 KiB) Downloaded 3549 times
Lucid Puppy Revitalized as 5.2.8.6!
Manual frugal install to a 4gb flash drive, computer is an hp desktop.
video-info-glx 1.5.3 Thu 28 Nov 2013 on Lucid 528 Linux 2.6.33.2 i686
0.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600]
oem: ATI ATOMBIOS
product: RV530 01.00
X Server: Xorg Driver: radeon
X.Org version: 1.7.6
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 (RV530 71C2) 20090101 AGP 4x x86/MMX+/3DNow!+/SSE2 TCL
OpenGL version string: 1.5 Mesa 7.7.1
AMD Athlon(tm) 64 Processor 3300+
Core 0: @2410 MHz
Multimedia audio controller
Creative Labs CA0106 Soundblaster
Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
I installed xorg hi from quickpet.
Also installed Ratpoison window manager.
5.2.8.6 is working well on this pc.
video-info-glx 1.5.3 Thu 28 Nov 2013 on Lucid 528 Linux 2.6.33.2 i686
0.0 VGA compatible controller: ATI Technologies Inc RV530 [Radeon X1600]
oem: ATI ATOMBIOS
product: RV530 01.00
X Server: Xorg Driver: radeon
X.Org version: 1.7.6
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
OpenGL vendor string: DRI R300 Project
OpenGL renderer string: Mesa DRI R300 (RV530 71C2) 20090101 AGP 4x x86/MMX+/3DNow!+/SSE2 TCL
OpenGL version string: 1.5 Mesa 7.7.1
AMD Athlon(tm) 64 Processor 3300+
Core 0: @2410 MHz
Multimedia audio controller
Creative Labs CA0106 Soundblaster
Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
I installed xorg hi from quickpet.
Also installed Ratpoison window manager.
5.2.8.6 is working well on this pc.
- Attachments
-
- screenshot.jpg
- (61.23 KiB) Downloaded 3435 times
Lucid was built with Woof from 5.0 to 5.2.8. Then 001-005 were done with rerwin's excellent remasterpup2 program.remasters, which is how playdayz, as I understand, maintained lupu.
The version number basically showed the Puppy's place in the development of Woof. The last official Lucid was 5.2.8 because it was to be supplanted by Slacko which debuted at 5.3. I do not think that version number should be changed unless Lucid was to be substantially revamped, such that, for instance, the basic libraries would be updated so that lucid could run the latest browsers without errors; as it is it is limited to Firefox and Seamonkey. But that would be a huge amount of work, recompiling all the libraries, and then retesting everything--it would be as much work as the original development. The the lucid Lynx programs would be out of date anyway. But with that much trouble why not start from scratch--in fact, starting from scratch would be easier.
Lucid was great, and rerwin's update provides a treat and some continued lifespan for Lucid. But the reason Lucid was great was all the testing it received--look back, there were about 100 pages or more of forum pages for *each* version of Lucid.
One thing that was different at the time of the development of Lucid was that everyone in the Puppy community participated in testing. All of the puplets and derivatives are fabulous, but IMHO there ought to be one Puppy that gets the full treatment--testing by everyone. And that Puppy ought to be the one that newcomers to Puppy should try first. I notice that Slacko is beginning the development cycle for 5.7. It already has the latest programs and the latest libraries and I urge everyone to get over there and test the hell out of it. Find any bugs and hardware incompatibilities now, run up 100 pages of testing, and make 01micko work for his money!!!
The main difference IMHO is that some rare (and some new) hardware will run in some Puppies and not in others--also some new software, particularly "hi-spec browsers" will not run in older Puppies. Other than that, again IMHO, 99% of the difference is mainly design choices in the GUI by the person who built the Puppy--not to say that those are not important to the user experience. You want the new browsers, try the Puppy I mentioned that is just beginning 5.7 development--and have your own input into how it works for you--that's much of the fun. Precise is a special case, IMHO (how many times can I say that in one paragraph) someone needs to adopt it and do what I did in the development of Lucid, and what 01micko has done with Slacko. It is extremely hard work.I'm sure more knowledgeable people than I can just compare the version descriptions, but I'd love even just two sentences on what makes one version of Puppy preferred over another .
Last edited by playdayz on Thu 28 Nov 2013, 16:54, edited 2 times in total.
Was... I have yet to move up to lucid for day to day use ...its just sat ready for the day .
And I remember having to fix some of those woof bugs too...my sympathies. I was making a custom 525 at the time.
Its normal in the software world to have a stable version...only here are beginners offered the beta releases primarily.... one reason this forum is so busy. Its also nice to build for a stable release too...less to deal with and your produce will generally be good for the newest kids in the block too.
Never got this new hardware = new kernel thing.... drivers can usually be built on a wide range of kernel versions.
Anyway if not for Lucid I would have probably would have strayed a long time ago... so i hold you all responsible.
mike
And I remember having to fix some of those woof bugs too...my sympathies. I was making a custom 525 at the time.
Its normal in the software world to have a stable version...only here are beginners offered the beta releases primarily.... one reason this forum is so busy. Its also nice to build for a stable release too...less to deal with and your produce will generally be good for the newest kids in the block too.
Never got this new hardware = new kernel thing.... drivers can usually be built on a wide range of kernel versions.
Anyway if not for Lucid I would have probably would have strayed a long time ago... so i hold you all responsible.
mike
- Moose On The Loose
- Posts: 965
- Joined: Thu 24 Feb 2011, 14:54
Re: Lucid Puppy Revitalized as 5.2.8.6!
[quote="rerwin"
To manage the cases where a pet package has been installed and becomes part of a later upgrade of lupu, after replacement of the main files in a frugal installation and subsequent boot-up, a check is made for packages now included in the main (lupu_528) file. If a conflict is found, a (pop-up) recommendation is made to uninstall the conflicting package, so as to utilize the new version in lupu.
{/quote]
I have made a SFS package for CAD that works with what I downloaded as 5.2.8.006. There are a couple of issues you may be able to help me with:
1) The SFS needs to bring along some libraries and I need to run ldconfig before they are seen. There is no ldconfig in the base system so I have to bring along my own. This seems slightly dangerous as it may conflict with the devxxx.sfs. Do you know of a good way to deal with this?
2) The SFS currently brings along a "default" design so that there is an example. I worry that if I make a upgraded version it may result in trouble,
Any advice?
To manage the cases where a pet package has been installed and becomes part of a later upgrade of lupu, after replacement of the main files in a frugal installation and subsequent boot-up, a check is made for packages now included in the main (lupu_528) file. If a conflict is found, a (pop-up) recommendation is made to uninstall the conflicting package, so as to utilize the new version in lupu.
{/quote]
I have made a SFS package for CAD that works with what I downloaded as 5.2.8.006. There are a couple of issues you may be able to help me with:
1) The SFS needs to bring along some libraries and I need to run ldconfig before they are seen. There is no ldconfig in the base system so I have to bring along my own. This seems slightly dangerous as it may conflict with the devxxx.sfs. Do you know of a good way to deal with this?
2) The SFS currently brings along a "default" design so that there is an example. I worry that if I make a upgraded version it may result in trouble,
Any advice?
Why not doing the following?:Any advice?
Grab the ldconfig binary from the devx and put it into the SFS Module. Add a /root/Startup/ldconfig-execute-script - sfs_load will run this after loading the SFS Module.
For the use in different Puppies one can modify the /root/Startup/ldconfig-execute-script for the use of $DISTRO_FILE_PREFIX in /etc/DISTRO_SPECS and renaming such different ldconfig binaries like ldconfig_lupu, ldconfig_precise etc.pp.
Once setup it should work without any problem or getting in conflict with any Puppy's devx.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
Yes mikeb, tempestuous built quite a few drivers for Lucid which are all in 5.2.8.6 (and were in Lucid Plus 5.2.8.005). I hope no one thinks I am criticizing Lucid--I use it myself still on the machines I used to develop it, though it does bug me that current browser choice is limited. It feels very good that people still find it worthwhile. And what rerwin has done is great. My point is that much of the goodness of Lucid was because it was the *One Official* Puppy and got all the testing and development attention--so tempestuous could build all those drivers, etc. If we want another Lucid we have got to test as much as we did then, that's all. I commit myself to testing Slacko 5.7.drivers can usually be built on a wide range of kernel versions.
BTW, you mention "stable" and I have found that Debian Wheezy 7.2 works very well, as does pemasu's dpup now built on 7.2 wheezy binaries.
Choice is always limited when dealing with this weeks incarnations.... I have a huge choice of browsers if I do not constrain myself with paranoia or gimmick chasing
Hmm stable as in whose binary sources or stable as in puppy configuration or stable as in good support.... the definition gets a bit hazy for me here. I and others can see the effort that has been put into Lucid and its still continuing and that to me made this a quality release...credit where credit is due.
Anyway I don't want to distract this thread just wanted to pop in my 10cents worth.
mike
Hmm stable as in whose binary sources or stable as in puppy configuration or stable as in good support.... the definition gets a bit hazy for me here. I and others can see the effort that has been put into Lucid and its still continuing and that to me made this a quality release...credit where credit is due.
Anyway I don't want to distract this thread just wanted to pop in my 10cents worth.
mike
- Moose On The Loose
- Posts: 965
- Joined: Thu 24 Feb 2011, 14:54
So may answer that with "because I'm stupid"RSH wrote:Why not doing the following?:Any advice?
This next bit is really obvious (now) but I do have a question I will put on the end:
My current plan is to put the ldconfig into some directory like:Grab the ldconfig binary from the devx and put it into the SFS Module. Add a /root/Startup/ldconfig-execute-script - sfs_load will run this after loading the SFS Module.
For the use in different Puppies one can modify the /root/Startup/ldconfig-execute-script for the use of $DISTRO_FILE_PREFIX in /etc/DISTRO_SPECS and renaming such different ldconfig binaries like ldconfig_lupu, ldconfig_precise etc.pp.
Once setup it should work without any problem or getting in conflict with any Puppy's devx.
Code: Select all
/root/kicad
Oh, no.So may answer that with "because I'm stupid"
I'm sorry, but I did not wrote it and also I did not meant it.
It was also not intended to give such impression etc.pp.
Sorry. Never ever heard the word "munging".My current plan is to put the ldconfig into some directory like:I then can do a "which ldconfig" and us it only if there isn't one in the normal path. This does mean, however, that I either have to as you suggest put in an ldconfig per version of puppy or hope that the one from 528 won't mung a different distro. What are the odds of munging?Code: Select all
/root/kicad
I think I've got a better idea - much smarter I think.
Build yourself a dependent SFS Module. Into this SFS Module put in all ldconfig binaries of your puppies. Each into a unique directory or renamed to a unique name.
The /root/Startup/ldconfig-execute-script should now be used to get the $DISTRO_FILE_PREFIX and $DISTRO_VERSION of the running puppy and to load the dependent SFS Module by sfs_load in cli mode:
Code: Select all
sfs_load --cli --skip-fixmenus --quiet "Dependent_SFS_Module_Here"
Code: Select all
sfs_load --unload --cli --skip-fixmenus --quiet "Dependent_SFS_Module_Here"
No GUIs to click out of the way (when the dependent SFS Module is stored at boot partition or boot directory (PSUBDIR).
Btw: I'm using something similar in my SFS P.L.U.S. Kit. Each SFS Module knows its dependent SFS Module (like Java, Python etc.) and it loads automatically after its main SFS Module is loaded and before the application is executed.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
- Moose On The Loose
- Posts: 965
- Joined: Thu 24 Feb 2011, 14:54
Don't fret it is just me being sillyRSH wrote:Oh, no.So may answer that with "because I'm stupid"
The verb mung is an acronym for "Mung Until No Good". It is an old computer science term that is used in place of "F%$K It up totally" in polite circles.Sorry. Never ever heard the word "munging".
I think I may have an even smarter smarter ideaI think I've got a better idea - much smarter I think.
At this step, basically the same but make the directories within the SFS named /thing/stuff/morepath/$DISTRO_FILE_PREFIX/$DISTRO_VERSIONBuild yourself a dependent SFS Module. Into this SFS Module put in all ldconfig binaries of your puppies. Each into a unique directory or renamed to a unique name.
Instead why not mount the SFS via a loopback use the ldconfig and then dismount. It never needs to be pulled into the normal file system just to run it once at start up.The /root/Startup/ldconfig-execute-script should now be used to get the $DISTRO_FILE_PREFIX and $DISTRO_VERSION of the running puppy and to load the dependent SFS Module by sfs_load in cli mode:
Code: Select all
sfs_load --cli --skip-fixmenus --quiet "Dependent_SFS_Module_Here"
Now executing the needed ldconfig and immediately unloading the Dependent_SFS_Module
No extra binaries needed inside the Main SFS Module (Main = the one to load, not the puppy's one). Easily usable in different puppies just by the /root/Startup/ldconfig-execute-script in the Main SFS Module (Main = the one to load, not the puppy's one).Code: Select all
sfs_load --unload --cli --skip-fixmenus --quiet "Dependent_SFS_Module_Here"
No GUIs to click out of the way (when the dependent SFS Module is stored at boot partition or boot directory (PSUBDIR).
Btw: I'm using something similar in my SFS P.L.U.S. Kit. Each SFS Module knows its dependent SFS Module (like Java, Python etc.) and it loads automatically after its main SFS Module is loaded and before the application is executed.
That's how things usually do evolve.I think I may have an even smarter smarter idea
That's just where the expert is split from the newbie.Instead why not mount the SFS via a loopback use the ldconfig and then dismount. It never needs to be pulled into the normal file system just to run it once at start up.
A hint, though: what about a temp file to be created after it has been executed once (to avoid re-running/-loading when just X is restarted for another reason)?
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
Re: Libralies come with an extra SFS
If the libraries confrict with the main SFS, I think running ldconfig is not a good idea. How to repair the links when the extra SFS is unloaded?Moose On The Loose wrote:1) The SFS needs to bring along some libraries and I need to run ldconfig before they are seen. There is no ldconfig in the base system so I have to bring along my own. This seems slightly dangerous as it may conflict with the devxxx.sfs. Do you know of a good way to deal with this?
A better way is to place all the things under an optional directory, say /opt/kicad, /opt/kicad/bin, /opt/kicad/lib.
And make a wrapper script /usr/bin/kicad:
Code: Select all
#!/bin/sh
PREFIX=/opt/kicad
export LD_LIBRARY_PATH="$PREFIX/lib:$LD_LIBRARY_PATH"
exec $PREFIX/bin/kicad "$@"
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Is this the same sfs where the defaultbrowser file does not show?
Is the problem you have libraries that do not show as well as I cannot recall a time when I had to run ldconfig with an application sfs.... only time I have seen it was with slax loading its dev file but that's understandable...at least the sfs load script they have detects when ldconfig is needed in some way I have not looked into.
mike
Is the problem you have libraries that do not show as well as I cannot recall a time when I had to run ldconfig with an application sfs.... only time I have seen it was with slax loading its dev file but that's understandable...at least the sfs load script they have detects when ldconfig is needed in some way I have not looked into.
mike
- Moose On The Loose
- Posts: 965
- Joined: Thu 24 Feb 2011, 14:54
I could put it in init.d so it only happens on boot. To make it only happen if really needed seems a bit harder. The user may add the SFS to the boot list, remove it and then add it again. If ldconfig was run with it unplugged, it needs to run again with it plugged in.RSH wrote:That's how things usually do evolve.I think I may have an even smarter smarter idea
That's just where the expert is split from the newbie.Instead why not mount the SFS via a loopback use the ldconfig and then dismount. It never needs to be pulled into the normal file system just to run it once at start up.
A hint, though: what about a temp file to be created after it has been executed once (to avoid re-running/-loading when just X is restarted for another reason)?
Perhaps I can just live with it happening more than needed. Putting it in Startup is nice because I can ask permission which I always want to do in such a case.
Code: Select all
if ! ( ldconfig -p | grep -q THENAME ) ; then
do the stuff
else
don't do the stuff
fi
trackpad click won't die!
Hi,
Long-term Puppy user here (puppeee 4.1, then Lucid 528 which has worked like a charm for the past few years) popping back in now that I've got a new laptop and trying to get the latest Lucid tuned to my taste. Sorry if this isn't the right place for my troubleshooting, let me know if it should be somewhere else.
The problem is, despite TouchPad Tapping being disabled in Setup > Mouse/Keyboard > Choose Type of Mouse, the trackpad is still acting as the primary mouse button. (By the way, it's installed on a Lenovo X130e which has a synaptic trackpad. Clicking when I press hard enough to click the physical button under the trackpad is fine, but the "soft clicking" of the trackpad when I'm trying to move the mouse is driving me insane!)
The synaptic device is showing up:
But when I tried
It brought up the message "Restart X-server to control from synclient". Restarting didn't help.
Another observations is that synaptics appears to be working, because right-clicking on the trackpad (which only has one physical button) works fine.
Can someone please help work out how to disable my trackpad clicking?
Thanks,
Simon
Long-term Puppy user here (puppeee 4.1, then Lucid 528 which has worked like a charm for the past few years) popping back in now that I've got a new laptop and trying to get the latest Lucid tuned to my taste. Sorry if this isn't the right place for my troubleshooting, let me know if it should be somewhere else.
The problem is, despite TouchPad Tapping being disabled in Setup > Mouse/Keyboard > Choose Type of Mouse, the trackpad is still acting as the primary mouse button. (By the way, it's installed on a Lenovo X130e which has a synaptic trackpad. Clicking when I press hard enough to click the physical button under the trackpad is fine, but the "soft clicking" of the trackpad when I'm trying to move the mouse is driving me insane!)
The synaptic device is showing up:
Code: Select all
grep Synaptics /proc/bus/input/devices:
Name="PS/2 Synaptics TouchPad"
Code: Select all
synclient TapButton1=0
Another observations is that synaptics appears to be working, because right-clicking on the trackpad (which only has one physical button) works fine.
Can someone please help work out how to disable my trackpad clicking?
Thanks,
Simon
Some small issues with LupuLibre latest on a Asus U36SD
PDFViewer fails to start. Kust shows a "blink" of the PDF and then gone
Video will not play on Mplayer. Just says "stopped"
Gnome alsamixer and alsamixer does not work. Usually works on other Lucid out of box on same PC.
Its not bugs but some issues that normal users might disagree with.
1) Default package manager GUI is set to "Classic", while "Ziggy" is cleary the best as for new users.
2) It looks like many of the downloads STILL points to slow slow ibiblio, while the other mirrors are rocket fast.
Just some fast input.
Best
atle
PDFViewer fails to start. Kust shows a "blink" of the PDF and then gone
Video will not play on Mplayer. Just says "stopped"
Gnome alsamixer and alsamixer does not work. Usually works on other Lucid out of box on same PC.
Its not bugs but some issues that normal users might disagree with.
1) Default package manager GUI is set to "Classic", while "Ziggy" is cleary the best as for new users.
2) It looks like many of the downloads STILL points to slow slow ibiblio, while the other mirrors are rocket fast.
Just some fast input.
Best
atle
Thanks, your posts help clear things up. Well Puppy 5.2.8 is working great for me, and honestly Chromium is running just fine ... so I do not feel any need for changeplaydayz wrote:You want the new browsers, try the Puppy I mentioned that is just beginning 5.7 development--and have your own input into how it works for you--that's much of the fun.
Thanks for your report. To give us a starting point, could you try running all 3 of these (one at a time) and then run pdiag to get a diagnostic file. Either post it or PM it to me.Atle wrote:Some small issues with LupuLibre latest on a Asus U36SD
PDFViewer fails to start. Just shows a "blink" of the PDF and then gone
Video will not play on Mplayer. Just says "stopped"
Gnome alsamixer and alsamixer does not work. Usually works on other Lucid out of box on same PC.
The PDF viewer works on my P4 system, so I need to see if something prevents it for you. For mplayer and the alsamixers, we need help from someone knowledgeable in those areas. I, too, have seen similar mplayer behavior but do not know what to do about it.
Richard