(old)Puppy Linux Discussion Forum

[quote="tempestuous"][/quote]
Would you happen to know how to fix the 'Xlib: extension "SHAPE" missing on display ":0.0' error, I've read about it and its looking for the
When i go online and find a fix, this is what they say

To get the SHAPE extension, you need to load the extmod module in your xorg.conf:

Section "Module"
Load "extmod"
# load some other stuff ...
EndSection

When I go to the xorg.conf I get this,
## Dougal: moved module section into xorgwizard.

When I search for 'extmod' on 2.14 <-- Barry's version.2.15ce,2.14R,2.14X there is no module called extmod, there is one called libextmod in all of them. Is this the same? Should be, Man its confusing, should I just take the xorgwizard out of say 2.15 and the xorg.conf out of 2.15 and see if that works? And if so will we loose any added features that 2.14.1 has?
This issue does need to be fix due to the size of the error file /tmp/xerrs.log The same log error repeats hundreds of times and about 1 hr using 2.14x it takes up 610kb, after a few days its really big unless you restart X server and it deletes.
If have any Idea on fixing this it would be great.
Thanks for your help
ttuuxxx

ok added the BMP fix to page 1 of this thread.
any other new/old issues?
ttuuxxx

Hello,
@Ttuuxxx, Jwm config starts from the menu, but here is the error for jwmconfig from the CLI:

I symlinked the files, and got rid of that error.
When run from the menu it starts, but any attempt to change anything gets:


As for org, I meant it worked fine in 214rx4, (not 4.xx series Puppy)
Yes, it is the radeon driver,

As for frugal install, Ive been trying it manually...
I will try from the installer....

Also, Firefo finally did crash....caused by scrolling to fast...Hmmm..
Other than that, works wonderfully...

puppyluvr wrote: Hello,

Here's a question, are you using version4 and not version5, version 5 has that fixed, I just tried it and this is what I got
sh-3.00# jwmconfig
Could not find environment variable 'JWM_Display_Manager'.

and it came right up and also works in the menu. All that 'c' locale stuff is fixed in version 5, You might also check and see if you have the pup_214R.sfs in one of your hard drive partitions, if so it will load the older version and not load the latest version on disk, a good way to tell, is when you boot up, is one of your hard drive icons on the bottom of the screen mounted? if so its found a older pup_214R.sfs and its using that one.
It happened to me today when I tried the v5 version, I even booted as 'puppy pix=ram' that only ignores saved sessions, but doesn't ignore pup_214R.sfs files.
ttuuxxx

If anyone likes Snes emulators, I posted one for 2.14X located on http://murga-linux.com/puppy/viewtopic. ... 903#322903
ttuuxxx

ttuuxxx

Maybe a symlink to /usr/X11R7/lib/xorg is needed in usr/lib
I have no room on my hard drive to try it myself, sorry.

Thanks for the idea tubby but it didn't work
But then I figured why not revert back to the way 2.15ce was before dougal changed things, i moved about 5 scripts, change back xorgwizard and gave it a shot. It work!!!!!!!!!!!! that error is now gone,
now to remember what I did, lol
I'll get it
but that is cool, I just hope we won't be missing any added modules/screen sizes by reverting to 2.15ce specs. I'm not usingany modules just the xorg scripts.
ttuuxxx

Glad you sorted something out, sorry if my idea gave you a headache.

V6 is out and boy what a difference now when you check for errors
Forget about V5, go straight to V6, details on page 1, This release is a milestone !!
ttuuxxx

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.18-inside-sandbox i386
Current Operating System: Linux puppypc 2.6.18.1 #1 Thu Feb 1 23:05:39 PUP 2007 i686
Build Date: 08 August 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 12 03:51:51 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "glx" (module does not exist, 0)
killall: HotPup.sh: no process killed
1024
992
992
killall: glipper: no process killed
3914: old priority 0, new priority 19
Pathname: /usr/share/audio/2barks.wav
Device: /dev/dsp
Sampling Rate: 8000 Hz
Mode: Mono
Samples: 4728
Bits: 16

ps that report is after 30 mins of use before it would of been 50 pages long,
ttuuxxx

WhoooHooooo! All hail ttuuxxx! Am writing this in ff 3.5 in 214X5, and this system seams to really rock! We should keep building puppy on 2.xx series and quit upup thingies and stuff

BTW, added pgprs package and am connected with my huawei e220, successfully connected to irc and msn, tried bmp, plays good, and now will test this ff if it stays stable and so slick gonna reinstall my HD puppy xD. Oh and system is faaaaast!

Great job ttuuxxx!

puppyluvr wrote:... And "init" is still the parent of all processes...
(Still cant frugal install it...will try full eventually)
Did I miss the answer for that one somewhere?? ...

A few weeks ago I got very frustrated, being told over and over again, that "init is still the ..." when trying to make 214X3 work frugally. I couldn't do it my usual way, just copy the files to where I wanted them, and make the appropriate? changes in GRUB's menu.lst . Very frustrating, I even resorted to burning the iso to a CD, and thereafter trying the pup-installer, you'll probably guess what I was told - "init is the ....." .
Then I tried something I saw way further up this thread:and having the root=/dev/ram0 PMEDIA=idehd instead of what I thought from my experience with pup-series 3, 4 and 5, as well as what was suggested by the pup-installer (root=/dev/hda6, in my case), fixed my problem with "init is the, init is the init is the .............. ".
This "semi-solution" meant that I could have vmlinuz and initrd.gz in a subdirectory, while having pup_214R.sfs and pup_save-?.2fs in the root of the partition.
Later on, I decided to wade through this thread backwards, looking for answers, tough work, but it paid off; I found this post and now I can have all the puppy-files for a certain pup214X? in a subdirectory of my choice . Thanx, vg1 .
Present menu.lst that allows this is, in my case: Hope that this long rant helps/
MHHP

ttuuxxx, ttuuxxx, you're too fast !
Downloaded X5 last night, gave it a spin for a bit, decided to leave the bug-report writing for today. Turned out to be a very good decision since, when I got home this evening, there was already yet another version . I will give it a thorough run-through tonight and report back.
By the way, "save settings" in Pup-Shots is implemented since last night, I'll upload it later on .

cheers/
MHHP

Huh? X6? I haven't even noticed that! xD ttuuxxx you devil!
OK, now i recall what i didn't like in 2.xx
while playing with beep player and browsing net with ff bmp hick-ups
(maybe this is just me, dunno)
Also: When I close tab in gaim whole gaim crashes? Bug?
terminal output:

Gaim has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.

It is possible that this bug is already fixed in CVS.
If you can reproduce the crash, please notify the gaim
maintainers by reporting a bug at
http://gaim.sourceforge.net/bug.php

Please make sure to specify what you were doing at the time,
and post the backtrace from the core file. If you do not know
how to get the backtrace, please get instructions at
http://gaim.sourceforge.net/gdb.php. If you need further
assistance, please IM either SeanEgn or LSchiere and
they can help you.
Aborted

Greetings!

Save Settings-feature implemented, just fool-proofed the case, should the settings-file somehow have gotten accidentally deleted (OK, not baby-sitter proof, but almost ) .

Try it out, shout out loud if it doesn't work!

Now, I'll finally take 214X6 for a spin!

cheers/
MHHP

One more question.

I do use the openoffice2.2.0.sfs made by BK for Puppy 2 (&3) a lot.
Is there any way to auto-mount it and get it unioned, so that all the desktop icons, menu items, short-cuts and such works?
I know how to mount it, and use it, but my knowledge of the commands involved in unioning FS:s is extremely scarce, to say the least. Is it possible?

Just wondering if there's an easier solution than my "mount openoffice2.2.0-dismount-remove without a trace - script" that I'm using now, have I missed a point somewhere??

Cheers/
P

@MinHundHettePerro: Thanks for explaining the workaround for getting pup_214R to live in a subdirectory.

Perhaps others are able to use it in a subdirectory using a different trick?

Downloading x6 now... Thanks, ttuuxxx.

ttuuxxx,
I was going to scream with joy it works to just set my keyboard to "se" (had to restart Xserver once more, though ) and I could use jwmconfig to set 3 virtual desktops .

But, then I set my locale to sv_SE (for testing, I don't usually set my locale) and result can be seen in screenie 1; setting the locale back to the dreaded default, en_US , produces screenie 2 (which shows some strange, but seemingly, unimportant error messages).

FWIW/
MHHP

raffy wrote:@MinHundHettePerro: Thanks for explaining the workaround for getting pup_214R to live in a subdirectory.

Perhaps others are able to use it in a subdirectory using a different trick?...

Is there a trick to it? I'd really like to learn. Myself, I just followed (official?) directions, relayed by vg1 in page 5 of this thread.
raffy, you were around by then (2.14, 2.14R), is there an easier way to do it (a trick )? Please, I'd really want to know . (I wouldn't know by heart, I only got into the Puppy-world with 2.16) .

Still Learning/
MHHP

Hello,
Well, the testing continues...Now on X6....
First, thank you to MinHundHettePerro for saving me on blank CD`s..
I realized the subdir was the prob...for me: Let the installer put it in /boot..

title = Puppy 214R X6
rootnoverify (hd0,2)
kernel /boot/puppy214R/vmlinuz root=/dev/ram0 PMEDIA=idehd
initrd /boot/puppy214R/initrd.gz

Did the trick.....
Duh...Now I can edit it to where I want...

I was wrong about Xorg...its locked to 640x480....period....
But Xvesa is working fine..so..no biggie...

Jwm config launches from the menu now....but what happened to changing the jwm theme?? ( Love all the GTK themes tho..)

Also, cant shut down in Xvesa...must switch to (640x480) org and use ctrl-alt-bkspc to save and shutdown..
Xvesa wont even go to a prompt without restarting, but this has nothing to do with 214r but Xvesa and my machine...

So far Id say it runs like a scalded monkey..
Everything else works perfectly so far...
Of course we only get a day or less between releases...LOL
Work-a-holic indeed....
It just goes to show how far the 2.xx series can go after all...
Puppy moves too fast.. LOL.. But then again, so do you..