Closed Bug 337022 Opened 20 years ago Closed 20 years ago

impossibility to open a secondary session with camino 1.0.1 (french version)

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 326668

People

(Reporter: siamois, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 (MultiLang) Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 (MultiLang) with camino 1.0.1 (frenchversion) it impossible to open it in a different session . Reproducible: Always
I assume you mean the ability to run more than one Camino at once. This is since Camino has a user-wide profile, and bad things would happen if more than one copy of Camino were given access at once. However, Camino does have the ability to be made into a portable app, which allows this to happen. One such build is available at http://homepage.mac.com/krmathis/ (but is made by an individual, and isn't supported by the camino project. I'm just being helpful). Anyway, closing as INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You can also make a launcher script which sets CAMINO_PROFILE_DIR to something other than ~/Library/Application Support/Camino before launching any standard Camino build. Please re-open this bug if that's not what you meant, however.
I do not use several camino at the same time. i can open camino in the administrator account but not in the other account. It works with camino version smaller than 1.0.1
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Ah, so this is presumably fallout from the change to tinderbox builds. *** This bug has been marked as a duplicate of 326668 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
Oh, too quick on the trigger verifying this...this could have also been bug 336871. Either way, this will be fixed in 1.0.2, because both of those bugs will be fixed there.
*** Bug 337108 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.