Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 28 Jul 2014, 04:51
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Lucid Puppy 5.2.7 RC2
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 73 of 91 [1351 Posts]   Goto page: Previous 1, 2, 3, ..., 71, 72, 73, 74, 75, ..., 89, 90, 91 Next
Author Message
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Sun 31 Jul 2011, 19:12    Post subject:  

pemasu and don570, You have made me a believe in the right-click convenience. I am already starting to rely on it Wink I think it will be a big hit among users. Thanks for all the work.
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Sun 31 Jul 2011, 19:15    Post subject:  

playdayz wrote:
Quote:
@ playdayz
In talking to Bert, he taught me that the version of mplayer gnome was not the same between 266 and 526.
266 => 1.0.4 gnome mplayer
526rc => 1.0.3 gnome mplayer
What is the reason for this change in version?

The pursuit of the elusive vdpau message was the basic reason. It seemed that 1.0.3 did not generate that message, but 1.0.4 did, so I reverted. I have learned more and the version I am currently building has 1.0.4 again.

mplayer isn't the only application which generates this series of VDPAU messages. As I said already SeaMonkey does it also.

But I have news.
I installed the 526 on the dreaded Medion 8818.
It has an nvidia graphics card.
After booting and only using SeaMonkey, xerrs.log stays at some 57 lines.
No VDPAU messages.
It's logic, as nvidia is VDPAU ready. Others not.

So I wonder if there could be:
- a kernel parameter to disable VDPAU
or better
- disable automatically VDPAU in case a nvidia graphics isn't installed.

Just my 2¢.

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

Last edited by Béèm on Sun 31 Jul 2011, 20:08; edited 1 time in total
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 5000
Location: Charleston S.C. USA

PostPosted: Sun 31 Jul 2011, 19:30    Post subject:  

rerwin wrote:
Essentially, the updater will not delete your old app versions, which should override the newer versions.

If I am understanding this.
What good is an update of the save file?
The whole purpose of upgrading is to get the newer version, of a program, with the bug fix.

_________________
I have found, in trying to help people, 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 Shocked
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1503
Location: Maine, USA

PostPosted: Sun 31 Jul 2011, 20:16    Post subject:  

playdayz,
I have discovered a surprising situation. It appears that the udev rules in the relatively new /lib/udev/rules.d directory are not being processed. I have been frustrated by my inability to solve dalderton's issue of the modeswitch rules being ignored. As a test, I moved a working test rules file from /etc/udev/rules.d to /lib/udev/rules.d. It no longer works!

This implies that not only are the modeswitch rules being ignored, but also the rest of the rules files in /lib/udev/rules.d. Maybe we should pause a little longer to resolve that.
Richard


Here is evidence that the udev version (124-2) in lupu does not know about the "default" rules directory. That must have come in later.
Quote:
Content of RPM udev-core-124-2.i586.rpm :
/etc/modprobe.d/udev_blacklist.conf
/etc/scsi_id.config
/etc/udev
/etc/udev/links.conf
/etc/udev/rules.d
/etc/udev/rules.d/05-udev-early.rules
/etc/udev/rules.d/10-udev-example.rules
/etc/udev/rules.d/40-alsa.rules
/etc/udev/rules.d/50-udev-default.rules
/etc/udev/rules.d/51-modprobe.rules
/etc/udev/rules.d/55-hotplug_map.rules
/etc/udev/rules.d/60-cdrom_id.rules
/etc/udev/rules.d/60-persistent-input.rules
/etc/udev/rules.d/60-persistent-storage-tape.rules
/etc/udev/rules.d/60-persistent-storage.rules
/etc/udev/rules.d/61-persistent-storage-edd.rules
/etc/udev/rules.d/64-device-mapper.rules
/etc/udev/rules.d/80-drivers.rules
/etc/udev/rules.d/95-udev-late.rules
/etc/udev/udev.conf
/lib/udev
/lib/udev/ata_id
/lib/udev/cdrom_id
/lib/udev/create_floppy_devices
/lib/udev/devices
/lib/udev/edd_id
/lib/udev/firmware.sh
/lib/udev/net_helper
/lib/udev/path_id
/lib/udev/scsi_id
/lib/udev/usb_id
/lib/udev/vol_id
. . .

It appears that lucid lynx uses udev 151-12. I cannot find similar evidence, but the ubuntu pages such as http://www.ubuntuupdates.org/packages/show/248972 mention both directories.

We have two alternatives:
1. "Right" way: Upgrade lupu to use the Lucid Lynx udev version (or similar, as in wary).
2. Expedient way: Move all of the rules files into /etc/udev/rules.d.

Now I can get a good night's sleep, having solved dalderton's mystery.
Richard

Last edited by rerwin on Sun 31 Jul 2011, 21:30; edited 2 times in total
Back to top
View user's profile Send private message 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Sun 31 Jul 2011, 20:18    Post subject: Right clicks and Puppy Help 101  

Smokey01 Playdayz

I would be happy to write the HowTo. How urgent is it? I have never used Notecase, is there much of a learning curve? I don't see any picture in 101 at the moment, are they possible or do I have to get that sort of detail over by being clever with links?

Playdayz I am very, very pleased that you now see the use of right-clicks. If it helps you, just think how good it is for the casual user. If I write the HowTo, it would be my preference to assume that you have binned the "Customise" menu options, for the reasons that I have given above. Would this be acceptable to you? It's your distro after all.

I had a mad idea about right clicks. The .desktop files already hold info about icons and executable files and are a Linux standard, unlike RoxApps. Wouldn't it be nice if you could use the .desktop instead of duplicating the same info in the form of a Roxapp? So I tried adding the "$1" parameter to the Exec= line in a .desktop and then symlinking the .desktop to the Open-with subdirectory. Alas it doesn't work, nor does "$@". Pity.
Back to top
View user's profile Send private message 
Béèm


Joined: 21 Nov 2006
Posts: 11782
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Sun 31 Jul 2011, 20:27    Post subject:  

Snail,
Notecase is very easy and intuitive.
It is based on creating nodes and eventually nodes on nodes.

Just make up your mind about a structure and hierarchy you want to set up.

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Sun 31 Jul 2011, 20:59    Post subject: Right click howto  

Thanks for the reassurance Béèm.

I have thought a bit more about the subject, should have done it before my last post Embarassed I know how to set up a right click, provided that the filetype is one already assigned a mime-type. For the case of an entirely new file-type that doesn't have an existing mime-type, I will have to do some research. If we drop the "Customise" options in the menus, the user also needs to check if his particular file-type is already known to Rox or not. Anyone got any pointers?
Back to top
View user's profile Send private message 
Snail

Joined: 18 Oct 2009
Posts: 238

PostPosted: Sun 31 Jul 2011, 21:50    Post subject: Puppy Help 101
Subject description: File location
 

Smokey01

Quick question. Is there a reason that PH101-001.ncd is in /usr/share/doc and not /usr/share/doc/help? Shouldn't it be PH101-002.ncd?
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 5000
Location: Charleston S.C. USA

PostPosted: Mon 01 Aug 2011, 02:07    Post subject:  

Got the idea from here
http://murga-linux.com/puppy/viewtopic.php?t=39505

Product key for your computer
puppy-product-key2.png
 Description   
 Filesize   49.7 KB
 Viewed   837 Time(s)

puppy-product-key2.png


_________________
I have found, in trying to help people, 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 Shocked
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 5000
Location: Charleston S.C. USA

PostPosted: Mon 01 Aug 2011, 02:19    Post subject:  

Got idea from here:
http://murga-linux.com/puppy/viewtopic.php?t=39505

Sticker for the front of computer
powered_by_puppy.png
 Description   
 Filesize   44.9 KB
 Viewed   851 Time(s)

powered_by_puppy.png

puppy-inside.png
 Description   
 Filesize   71.17 KB
 Viewed   847 Time(s)

puppy-inside.png


_________________
I have found, in trying to help people, 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 Shocked
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4776
Location: GB

PostPosted: Mon 01 Aug 2011, 03:10    Post subject:  

rerwin:
Quote:
Your question is something every upgrader needs to know.

- care to advise on precautions relating to FULL installation upgrades, please?
Back to top
View user's profile Send private message 
smokey01


Joined: 30 Dec 2006
Posts: 1795
Location: South Australia

PostPosted: Mon 01 Aug 2011, 04:09    Post subject: Re: Puppy Help 101
Subject description: File location
 

Snail wrote:
Smokey01

Quick question. Is there a reason that PH101-001.ncd is in /usr/share/doc and not /usr/share/doc/help? Shouldn't it be PH101-002.ncd?


Snail, no reason really.

I have already started on PH101-002 in fact playdayz already has a copy of it. You don't need to do any fancy programming just PM me a text file.

Answer to your question above. Yes you can add graphics but the file would become very large and would not make it into Lucid.

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send private message Visit poster's website 
peebee


Joined: 21 Sep 2008
Posts: 1369
Location: Malvern, Worcs, UK

PostPosted: Mon 01 Aug 2011, 06:00    Post subject: smbc printer error  

Hi playdayz

I did my usual setup of a remote smbc printer to my XP box.

Got the attached error when I tried to print.....

Cheers
peebeee
error010811.png
Description 
png

 Download 
Filename  error010811.png 
Filesize  63.22 KB 
Downloaded  110 Time(s) 

_________________
LxPup-14.03 = Puppy + LXDE
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 8909
Location: Stratford, Ontario

PostPosted: Mon 01 Aug 2011, 08:28    Post subject: Re: smbc printer error  

peebee wrote:
I did my usual setup of a remote smbc printer to my XP box.Got the attached error when I tried to print....

The solution is to make the following symlink
Code:
ln -s /lib/libreadline.so.6.1 /usr/lib/libreadline.so.5


But I have no idea why 526 requires this but 525 does not.
Back to top
View user's profile Send private message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Mon 01 Aug 2011, 08:57    Post subject:  

Playdayz and rerwin. About udev 151-12. I remember when Playdayz tested it and got some bad experience about it. I just cant remember what went wrong.

But....I had to change to the udev 151-12 when I started to use kernel 2.6.35.7. I couldnt get audio working otherwise. I have used udev 151-12 since then with 2.6.38.2, 2.6.38.4 and now with 2.6.39.3 kernels. Audio has worked. I havent noticed any problems with using it.

Now...People have woofed using ez woof 525 and they have used my kernels 2.6.38.4 and maybe 2.6.39.3 and they have had a lot problems with audio. Maybe older udev is one reason of the audio problems with ez woof 525

If....you are going to create ez woof 527 and there is plan to test newer kernels with it....updating the udev to 151-12 is again current.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 73 of 91 [1351 Posts]   Goto page: Previous 1, 2, 3, ..., 71, 72, 73, 74, 75, ..., 89, 90, 91 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1087s ][ Queries: 12 (0.0195s) ][ GZIP on ]