Hopefully some of this advice will help. 

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ 
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ 
G e h! r- y+ 
------END GEEK CODE BLOCK------
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sure, though I'm gonna hit the sack within some minutes, I'll give you
what I know right now :) .

As the person uses 1.0.6 I presume that he has migrated to X.org,
although at a first glance I don't see a hint of which x server is used.
I myself have never used ff in a chroot (using dchroot, dchroot -c ia32
- -d mozilla-firefox & ) prior to the move of sid to X.org, if you think
it could be useful information I could try switching to xfree86 temporarily.

The behaviour described reminds me of #316566, which I at that time
blamed on fluxbox. Right now I'm using gnome (because of
#316566 ) and chrooted firefox works wonderful here. If you wish I can
try doing the following things tomorrow:

- - check wether #316566 still occurs since the migration to X.org (by
trying to use ff in fluxbox again);
- - if #316566 is still there, see if a chrooted firefox makes a difference;
- - run xfree86 + gnome and try to run a chrooted firefox;

Btw, I use unstable for both the main system and the chroot. And can the
person who reported the bug start other XUL apps like thunderbird? Can
he see firefox in the process list? What happens when he tries it using
a firefox build from the mozilla web site?

If you need more specific info, just ask what you'd like to know, I'd be
happy to help where I can.

Good luck with squashing bugs, being the maintainer of such a popular
package must be quite some work, I really appreciate it :) .

Eric Dorland wrote:
> * Tjaard de Vries ([EMAIL PROTECTED]) wrote:
> 
>>Package: mozilla-firefox
>>Version: 1.0.6-1
>>Followup-For: Bug #319336
>>
>>
>>The latest i686 version from unstable in a 32-bit chroot works without
>>problems. Therefore it seems an amd64 specific problem.
> 
> 
> Somewhat off topic, you actually have firefox running in a chroot? Can
> you take a look at #299619 and offer some insight?
> 


- --
Tjaard

Get Firefox and earn me some points ;) :
http://www.spreadfirefox.com/?q=affiliates&amp;id=110049&amp;t=1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC6rx6CqxgDAdoJzURAtaZAJ90QHLpFPLgH9qWX6MOvaM85YE0fACgqXKi
fiqHyuRbB0YbehoFcPIXfeo=
=WAtQ
-----END PGP SIGNATURE-----


--- End Message ---

Attachment: signature.asc
Description: Digital signature

Reply via email to