Wish I knew, David. I've not seen that before EVER! Seems you may have managed to copy a corrupt version of ROX into your pup_save file somehow and it's sitting in a layer above the inbuilt original.

I think not, for at least three reasons: (1) I booted pfix=ram so there was nowhere for a corrupt file to come from; (2) my previous pup_save file didn't contain a corrupt version of ROX; (3) I looked in /usr/local/bin and there was no ROX listed at all; there was neither a corrupt nor an incorrupt version.

When you first run ROX is called from the pup_420.sfs file into RAM. If it crashes there, or corrupts, or whatever, it is possible that the system will think you deleted it and cover the original with a .wh file at the higher level. You won't see ROX (not even the original) and the system will believe it doesn't exist. Those are the joys of a layered file system. The good news is that the original, uncorrupted ROX binary is still there and appears again when you delete the pup_save file along with the .wh mask file that prevents it from being seen.

You could even copy the original back from /initrd/pup_ro2/usr/local/bin but only IF you have another working file manager that will let you do that.

pa_mcclamrock wrote:

Quote:

Delete your pup_save file and try again from a clean install.

Done. No problem now. But I wish I knew what caused the problem before, and whether any other users are going to have it!

Could be flakey RAM, power transients, etc. It doesn't take much to cause a problem for a mounted squash file system (pup_save IOW) to have a bit or two throw things out. That's why you should always make a clean copy of your working pup_save before doing anything critical.

Hope that helps._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

There is evidently a misbehaving cups daemon at work here. I noticed a problem with earlier CUPS installations but haven't had a repeat since. The daemon simply refuses to throttle back after completing some operation or other.

Next time instead of killing the process, try manually stopping CUPS and then restarting it again from the CLI.

Hope that helps._________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

Ain't going to pursue it further, as I'm more than happy (and familiar) with my backdrop of >15 years. Just reported an observation I made, I will not, personally, use any of the supplied wallpapers.

>15 years with the same backdrop!?!? That's gotta be some sort of record, MHHP! _________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

The fix was only evident AFTER the RC2 release was uploaded or it would have been patched before I uploaded it. ITM I have asked tempestuous to look at the wireless problems for a more permanent solution, if he has the time and the inclination. After all we are all VOLUNTEERS!

It would be nice if we had Warren Woodford's resources (Ubuntu founder) to throw at these issues, but I believe we still manage to produce a better, faster, more efficient OS with just a little personal commitment and patience.

Cheers, from one of "the young 'uns". _________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

There is evidently a misbehaving cups daemon at work here. I noticed a problem with earlier CUPS installations but haven't had a repeat since. The daemon simply refuses to throttle back after completing some operation or other.

Next time instead of killing the process, try manually stopping CUPS and then restarting it again from the CLI.

Well it doesn't tell ME anything, because I'm not that good , but I'm sure hoping it will speak volumes to Dougal, Patriot, ttuuxxx or one of the other devs quietly working away in the background! Thanks for trialling, dogone.

Cheers_________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

can I just mention again that this problem was not a problem with 4.1.2 (confirmed by others) That version recognised wireless interface and ipw220 drivers loaded every time - and works.

so seems to me not likely to be a kernel or fundamental problem?

Agreed. I think I remember patching the wireless drivers early in the Alpha cycle for 4.2, and I think it's that patch that is masking the earlier (working) driver set. That's why deleting that directory, or renaming it, works; it takes the driver set back to the inbuilt ones from the kernel.

jabu2 wrote:

- minnesota detected file differences in 4.2 rc1 from 4.1.2 and gave samples (back on p4 of rc1 thread)

I am not knowledgeable enough to know if he/she was onto something, but if correct this seems like a short cut to a soution.....?

trying to help. ATVB (all the very best)

Help is always welcome, jabu2. The file differences reported relate to the updated driver set vs the original set. It gave me the clue as to why the problem existed but not how to correct it without reverting to the earlier driver set. I'm hoping tempestuous will have a solution. If he doesn't then I'll simply roll back to the 4.12 driver set and leave it there. _________________Actions speak louder than words ... and they usually work when words don't!
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

Ok I finally loaded up 4.2RC2 and well this is what I found
- a whole row of icons was moved in icewm to where the pwidgets sits and then gets trashed by pwidgets, That never happened before? Why now?
The xdg menu that I supplied with the last icewm package I provided wasn't used or was ignored, I had changed
prog "Shutdown" shutdown24 /usr/bin/shutdown
to
prog "Shutdown" exit24.png /usr/bin/shutdown
that is a way better look to the icons and matches the Refresh Menus icon perfectly.
Also the new Seamonkey icon wasn't used, That took hours to improve and its actually3/4 smaller than the default icon.

also beside the time on the taskbar theres a extra "space" thats using the "space" from the clock, which I don't think I have a space icone being used before the numbers, and if you switch to the 'Citrus' theme you'll see a black box, any ideas? Oh is this one for my new list of things to do ?
ttuuxxx

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