some users reported that juhu 0.8.3 (and previous versions for that matter) crashs at launch. up until now this is confirmed only on ppc-based macs, but due to the help of mikka and lloyd I was able to figure out a small workaround which should do the trick until the next release: the crash is produced by the routines that check for newer versions, so turning the update mechanism off should help. in order to do that, just open
~/Library/Preferences/com.somemorecode.juhu.plist and set autoupdate to NO.
Subscribe to:
Post Comments (Atom)
9 comments:
still crashes in Leopard and the plist file doesn't exist on my machine.
on my intel based MBP, it crashes as well. anyway keep up the great work.
@dan: yeah, the bug itself is not plattform specific, but intel machines seem to handle the caused access violation slightly more gracefully. :) anyway, does turning off the update work?
@jerry: leopard is a topic for itself, since I don't have a copy (500 bugs is a lot of money...) to do some tests, I can't tell you much about it, sorry.
Might sound like a daft question, but open with what?
no, actually that is a very good question. there are two tools you can use for that: the first comes with the apple development tools which ship on your mac os x dvd. the other one is a commercial product with a working trial version download. http://www.fatcatsoftware.com/plisteditpro/
the next juhu release will fix the bug, but until then you could use these tools.
Unfortunatly, I edited the file, switched off autoupdate, but Juhu still crashes :(
Juhu started crashing on me too awhile ago. Its just asking for my account information at launch, and when i type them in, it just disappears without any errors. I should get back to the older version i guess. But still, Juhu has been great!:). And oh, i have a new Intel MBP.
It chash on my iBook G4 (ppc) and I just change de Autoupdate option to NO... :(
it would be really nice if some of you having trouble running or starting juhu would mail the crash log to juhumac@googlemail.com.
the actual crash log file should be in ~/Library/Logs/CrashReporter and is named juhu.crash.log, alternatively you can just look it up using spotlight.
the bug fixing process should be way easier, if I know what exactly crashes. thanks a lot. :)
Post a Comment