There's a missing package required for building stuff against gnutls: libp11-kit-dev.

It's a new dependency of gnutls (which appeared in later Ubuntu releases and Slackware 14.0). If this package is missing, many applications with optional SSL/TLS support will build without it. Some won't tell you, until you notice you can't use SSL URLs, verify certificates, encrypt stuff, etc'.

So far, aria2 failed to build and BitlBee's configure script simply turned that support off (how rude!) and went on. I guess that's just the beginning - more things should fail.

EDIT: oh crap, it seems OpenSSL is problematic because of conflicts between 0.9.8 and 1.0.0. libcrypto.so does not exist and applications try to link against 0.9.8, while they build against 1.0.0's headers.

I happened to have one "mostly black screen" Pup in a frugal
install on a old IBM NetVista. The Pup is Racy 5.3.90 The video
hardware is Intel and Racy is set for 1280 X 1024 The cpu is
a p4 2.0ghz and RAM is 512 meg.

I tried modifying both sleep settings in the .initrc from 0.5 to
various values from 0.1 to 6.0 None of the settings fixed the
problem. I verified that the ,initrc file was indeed modified by
checking it after each reboot. I could tell when the sleep was
set to a high value since the startup screen remained totally
black (except for cursor) for a seemingly long time before a gui
(or toolbar at least) appeared.

OK, could I stretch your patience a bit more, for some more testing?

If you get the JWM tray, with menu, and that all looks OK, but the actual desktop is black (no wallpaper) and no desktop icons, then it is just about certain that ROX-Filer failed to start, meaning it is most likely not a video-driver problem.

if you get other display issues, such as the JWM menu not displaying properly, or a completely black screen, then it is a video driver problem.

If your case is likely to be a ROX-Filer startup problem, here are some more tests:

1. Make sure that /root/.xinitrc is restored to pristine, before you edited it.

2. Reboot until you get the black-screen problem. Examine /tmp/xerrs.log -- this will usually have an error message if ROX-Filer had failed to start.

3. In a terminal window, run "ps" and you should be able to see if ROX-Filer is running, or not.

4. If, from above tests ROX-Filer is not running, or is outputing an error message, edit /root/.xinitrd as follows:

I've been unable to test with the modified .xinitrd since removing the
comments results in a inability to startup Precise. I get stuck endlessly
in xorgserver trying things to no avail. Please show exactly what the
uncommented code should be and I'll try again.

I first tried this with sleep 3 as above and eventually changed it to
sleep 1. I've done a total of 17 hard machine reboots so far with
no black screens. I've counted seconds from the last text message
(starting x server) until a gui appears during startup. It has varied
from a low of 6 seconds to 31 seconds but most of the time it's
21 seconds (even with sleep 1).

BTW, I'm a old engineer-programmer who knows BASIC and
assembly language but I'm unfamiliar with the scripting language
used here ... just for your info. It appears that fi acts as a END IF
and one was missing.

I've mentioned before that all my test machines are similar, The
one I used for this test is a DELL Dimension 2350 having a 1.8 ghz
Pentium 4 and 768 meg RAM.

This is a continuation of a Precise 5.4.2 discussion started on the Precise 5.4 thread.

(By the way, to avoid confusion, does the name of the Precise 5.4 thread (currently named "Precise Puppy 5.4 and 5.4.2") need to be corrected, and should this thread -- the real Precise 5.4.2 thread -- be made sticky?)

Although there are a number of reports of the symptoms you are experiencing (text characters turning into little squares when installing a package) from folks running in PUPMODE 2 (full install), this is the first I have seen for PUPMODE 13.

Barry has a fix for users running PUPMODE 2, but it applies only to that mode.

Since many things could cause the text characters to be corrupted, your problem may be something totally unrelated to the problem PUPMODE 2 users ran into. But because it happens during package installation (as was the case for the other problem), it could well be related to the other problem.

That said, I have not yet found anything in the code that would explain what you are seeing in PUPMODE 13.

I have no experience with PUPMODE 13, so may not be able to help with this. But I can suggest a few items of information that you could provide which might help someone else figure this out.

1. The problem experienced by PUPMODE 2 users also caused the desktop icons to change. Did this also happen for you?

2. Do you remember what package you were installing when you ran into this problem?

3. What output do you get for these commands?

Code:

ls -ld /lib/i386-linux-gnu
ls -ld /usr/lib/i386-linux-gnu

(This will tell us if those items are still symbolic links, as they should be, or if the installation of the package changed them to directories or removed them entirely.)

4. What output do you get for this command?

Code:

grep -E "PUP_LAYER|SAVE_LAYER" /etc/rc.d/PUPSTATE

(These variables are used by the installation script, so we need to see if they are set correctly.)

I just installed precise puppy. Wpa supplicant doesnt work with my eeepc 1000H with Ralink rt2860 .
Network manager stays stuck at scanning and associating.
WPa supplicant is not detected...
I dont know what to do!

Upup Precise 54X5 has newer Woof fixes that weren't in Puppy Precise 5.4.2, but will be in Service Pack 5.4.2.2, including the fix for PUPMODE 2 users. I don't quite see how that fix would affect PUPMODE 13 users, but, like I said, I have no experience with PUPMODE 13. So it is worth a try.

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