* Ian Schindler (ian.schind...@gmail.com) wrote:
> On Sun, Nov 23, 2008 at 7:50 AM, Eric Dorland <e...@debian.org> wrote:
> 
> > * Ian Schindler (ian.schind...@gmail.com) wrote:
> > > Package: iceweasel
> > > Version: 3.0.3-3
> > >
> > > When iceweasel is run for the first time, it cannot access the directory
> > > ~/.mozilla/firefox (permisssion denied) which causes it to crash.  (I
> > > installed Etch and immediately upgraded to Lenny before installing
> > > iceweasel.)
> > >
> > >
> > > I solved this problem by running
> > > $sudo iceweasel
> > > $sudo chown -R me:me .mozilla
> > >
> > > I don't know if the first step was necessary.
> > >
> > > I am including the tail of the output from
> > > $strace iceweasel
> >
> > Any idea if the directory existed with the wrong permissions before
> > you ran iceweasel?
> 
> 
> I recently performed 3 installations in which I installed Etch and
> immediately upgraded to Lenny.  I encountered the above bug in 2 of the
> installations.
> 
> I checked the 2 machines where I encountered the bug.  The bug only occurs
> in the account used for upgrading the system from Etch to Lenny (using
> sudo).  All other accounts do not contain a directory ~/.mozilla, and
> iceweasel creates the directories with the correct permissions when started
> for the first time.
> 
> I did a similar installation without encountering the bug.  The difference
> in procedure was that I did not install the standard desktop in Etch before
> upgrading, I only installed the base system, upgraded, and then installed
> the desktop environment by hand.
> 
> The directory ~/.mozilla seems to have been created with the wrong
> permissions by some other package included in the standard desktop
> environment, after which iceweasel is unable to access the directory.
> 
> Hope this helps.

What are the permissions it's created with? Is this before the upgrade
or after?

PS please keep the bug CCed.

-- 
Eric Dorland <e...@kuroneko.ca>
ICQ: #61138586, Jabber: ho...@jabber.com

Attachment: signature.asc
Description: Digital signature

Reply via email to