On Thursday 03 Jan 2008, Peter Makholm wrote: > A J Stiles <[EMAIL PROTECTED]> writes: > > If I already have 64-bit Iceweasel running, and try to start 32-bit > > Iceweasel from inside the chroot, I get another instance of the 64-bit > > browser. If I kill the 64-bit browser, I can start a 32-bit one. If I > > then try to start a 64-bit Iceweasel from the K menu while the 32-bit > > Iceweasel is running, I get another 32-bit Iceweasel. > > You can try to use the -a switch to iceweasel such that the two > iceweasels runs with different application-id's. If that works you can > make an alias for iceweasel inside you chroot to use a non-default > application-id.
Thanks for your help! I successfully invoked the 32-bit firefox using $ iceweasel -a firefox32 from within the chroot while simultaneously running a 64-bit instance. Flash, Java &c. work fine. So next, I edited the script .../usr/lib/iceweasel/iceweasel (inside the chroot) so the default application ID is now firefox32. This is what I changed: ##### WAS ##### APPLICATION_ID=firefox ##### NOW ##### APPLICATION_ID=firefox32 ##### ENDS ##### Hope someone else finds this useful. -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
