Re: [SD4L-user] Problems with Scramdisk (?) 1.3-0 on Gutsy 7.10

[Hans-Ulrich J. <han...@t-...>]

Hello Stewart,

Millen, Stewart wrote:
>>From a post made on the Ubuntu forums:
> 
> 
> Hello all,
> 
> I'm running Gutsy 7.10 on a Dell Inspiron 1525N laptop (essential
> hardware listed on the Dell site, if it's of interest) just recently
> purchased. I also use Scramdisk for Linux version 1.3-0 to which I have
> containers (formatted in ext3) copied from a Feisty 7.04 machine which
> were created using a previous version of Scramdisk (but still should be
> compatible). I direct Firefox to look for my user profiles within the
> encrypted containers. 
> 
> On my Feisty machine (until it was murdered recently, great sadness :()
> there were never any problems. However, on my new Gutsy machine, it
> seems that I'm experiencing:
> 
> a) more hangups (like 20 seconds to a minute) on loading web pages (ok,
> this could be at the web server end) but which nearly freeze up my
> system. It does this even though a quick look at the system monitor does
> not show high RAM or CPU usage. 
> 
> b) A lot of times when this happens (but even when it doesn't) when I
> close Firefox and restart it I get a "Firefox is already running, you
> must either close Firefox or restart your system" error. In the system
> monitor it does not show Firefox running. 
> 
(snip)

I'm sorry that my answer is somewhat speculative, due to the
complexity of these failures and the lack of any precise error
message.

Your problems may possibly come from the redirect of your Firefox
user profiles to the encrypted container. If your new machine does
some preloading of Firefox modules or libraries on startup of the
desktop the container with your user profile is probably not yet
mounted. So there is an inconsistency in what theses preloaded modules
see and what is later seen by Firefox as your user profile. Since
Firefox also saves much cache, history, configuration, and state
in the user profile these information may also get corrupted by
being written to different places.

Maybe the applets also have some configuration/state information
which is redirected to the container and crash because of sudden
inaccessibility of their files.

I hope this will be helpful.
Best regards
Ulrich