Existing users, 
I spend one day/week downloading updates and performing general maintenance. I was happy to note that a Camino update was available, although reading a comment from a Camino person to the effect that a bug was noted and that the update was posted regardless just didn't sit right. Regardless, I launched it after the post-maintenance restart and the whole system immediately seized up--it took a good half-hour to pull up System Services in order to restart again. I trashed the update, replaced it with 1.5.1 (I'd kept the dmg), and all is well. Phew!
I really like Camino, in particular because of its ability to configure cookie acceptance (bar none, the most elegant and sophisticated of any browser) and the fact that I can retain history for a long time (now, if only it could handle PDF files). I've had some minor gripes in the past but this was a disaster. And yeah, I think this is the place to mention it--isn't this why we're offered a "troubleshooting" option?
Camino
Mac-native Web browser with Mozilla's rendering engine.
Version: 2.0
Oy...
Feedback Type: Troubleshooting Report
Contributed by: MacGuffin Sunday, October 21 2007 @ 06:22 PM PDT
Product Platform: MacOSX
Used Product For: Less than a month
Recommend Product: NO
System Info:
Comments
Oy... - MacGuffin
Thanks for the reply. You could very well be right, but the problem disappeared when I reverted to 1.5.1. It could be coincidence, but I'm disinclined to repeat the trial, especially since the incident cited occurred after running maintenance scripts, a DiskWarrior rebuild of my directory, etc., which usually leaves my system purring. As previously noted, I actually like Camino which is, in fact, my #2 browser (for some reason, no matter how I configure cookies, I can't complete an eBay transaction, so it's not going to be elevated to the default slot anytime soon). In fact, I invariably recommend it to my new-to-Mac buddies who, as computer scientists, are inclinded to opt for Firefox. But this update just didn't seem to work for me, despite my success with previous builds with which other users reported issues. It never even launched successfully--just ground down to a halt and took everything else hostage to boot. Very frustrating.Monday, October 22 2007 @ 01:38 PM PDT
Oy... - FalstaffA
McGuffin, please indicate your system profile, as well as, haxies if applicable. It seems as if you may have had a temporary software or hardware glitch, that as s_morgan indicated, coincided with your Camino launch.Tuesday, October 23 2007 @ 12:17 PM PDT
Oy... - s_morgan
> reading a comment from a Camino person to the effect that a bug was noted and that the update was posted regardless just didn't sit rightIf you are referring to the Quicktime drawing bug mentioned below, that's a very long-standing bug in the Mozilla core with plugin content. If we waited to release until we had fixed every known bug (even those that are largely cosmetic and part of the Mozilla core, which the Camino project doesn't control) then there would be no Camino. Essentially all software releases with some known bugs (e.g., I can guarantee you that there has never been a version of OS X that shipped without any known bugs).
> I launched it after the post-maintenance restart and the whole system immediately seized up--it took a good half-hour to pull up System Services in order to restart again.
An important feature of a modern OS such as OS X is that no one user-level application can cause system-wide failure, so this sounds like an issue with your OS installation that happened to coincide with launching Camino.
Reply to This
Sunday, October 21 2007 @ 11:20 PM PDT