I can confirm majorfoo's Seamonkey 2.3 bug. I've only tested in 529. If you clear cookies, via Clear Private Data, you are locked out of Seamonkey once you leave it. Rebooting restores the access. It occurs if you set Edit->Preferences->Privacy and Security to always clear private data and tick cookies. The bug also occurs if you use Tools->Clear private data and tick cookies. (I probably did not actually have any cookies in the system when I did this testing.)

I can confirm majorfoo's Seamonkey 2.3 bug. I've only tested in 529. If you clear cookies, via Clear Private Data, you are locked out of Seamonkey once you leave it. Rebooting restores the access. It occurs if you set Edit->Preferences->Privacy and Security to always clear private data and tick cookies. The bug also occurs if you use Tools->Clear private data and tick cookies. (I probably did not actually have any cookies in the system when I did this testing.)

What is really strange is that this only happens in lucid series.I have tried 525,528 and 529. Problem exists in all three.

If i go to slacko-4.99.1 or next 500 alpha2, problem does not exist.
Posting now from next 500 alpha2, installed seamonkey-2.2-Lucid525.pet, then updated to seamonkey 2.3. No problems here

I can confirm majorfoo's Seamonkey 2.3 bug. I've only tested in 529. If you clear cookies, via Clear Private Data, you are locked out of Seamonkey once you leave it. Rebooting restores the access. It occurs if you set Edit->Preferences->Privacy and Security to always clear private data and tick cookies. The bug also occurs if you use Tools->Clear private data and tick cookies. (I probably did not actually have any cookies in the system when I did this testing.)

What is really strange is that this only happens in lucid series.I have tried 525,528 and 529. Problem exists in all three.

If i go to slacko-4.99.1 or next 500 alpha2, problem does not exist.
Posting now from next 500 alpha2, installed seamonkey-2.2-Lucid525.pet, then updated to seamonkey 2.3. No problems here

majorfoo

I'm running SeaMonkey 2.3 on 525,528,529 and Lucid Retro (in 529 at the moment)....all set up to clear private data and cookies on exit....and I haven't seen this problem yet.

Everything appears to be working pretty well,nothing really to complain about.Naturally, SeaMonkey will start acting up now probably.......

I'm running SeaMonkey 2.3 on 525,528,529 and Lucid Retro (in 529 at the moment)....all set up to clear private data and cookies on exit....and I haven't seen this problem yet.

Everything appears to be working pretty well,nothing really to complain about.Naturally, SeaMonkey will start acting up now probably.......

DId you check ALL boxes in Privacy&Security - Note your screen shot on another post did not have all boxes checked. Once all boxes are checked, close browser and then reopen- Sometimes it opens on first try but not on second. Open and close a few times and see if you can create the problem.

I'm running SeaMonkey 2.3 on 525,528,529 and Lucid Retro (in 529 at the moment)....all set up to clear private data and cookies on exit....and I haven't seen this problem yet.

Everything appears to be working pretty well,nothing really to complain about.Naturally, SeaMonkey will start acting up now probably.......

DId you check ALL boxes in Privacy&Security - Note your screen shot on another post did not have all boxes checked. Once all boxes are checked, close browser and then reopen- Sometimes it opens on first try but not on second. Open and close a few times and see if you can create the problem.

thanks
majorfoo

I'll confirm that with all boxes checked when SeaMonkey 2.3 is closed there is a process or processes continuing to run in the background preventing SeaMonkey from reopening.
Unchecking boxes did not help,had to do a browser reinstall.

Apparently Three-Headed-Dog already contains the new ath9k_htc wifi driver, thanks to its modern kernel version,
but I don't think it contains the necessary firmware that this new wifi driver requires.

I now attach the firmware, plus updated configuration files so that the Network Wizard will recognise the ath9k_htc driver as compatible with WPA/WPA2 wifi encryption.
Plug in your USB wifi device only AFTER you have installed this dotpet. Otherwise, you will need a reboot.

These are the USB wifi devices which should (in theory) be supported by the ath9k_htc driver:

I just had to OK some message about Puppy not knowing whether WPA/WPA2 was supported by the USB driver (or something along those lines). After that I plugged in the USB dongle again and there it was on the network interface list!

Thanks Tempestuous and thanks Playdayz for releasing this, at long last (for me), fully functional and smooth-running Puppy!

This is experimental but it has been working for me. It does 2 things--first, it makes the newer chromium based browsers work without the pinwheel of death problem with loading, and second, it lets Seamonkey and other gecko based browsers work when installed along with the Chromium browsers.

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