S/MIME signed/encrypted messages started crashing my Mail app long
ago, after one of the first updates to 10.4. I probably sent in a
couple dozen of those crash reports, with absolutely zilch feedback,
and of course I still have the problem. From my end of things, those
crash feedbacks are worthless, and I don't send them in anymore as I
see them as a waste of my time.
On Jul 7, 2007, at 10:36 PM, Ian Ollmann wrote:
> When an app crashes, you should be getting a little dialog box with
> the option to send a problem report of some kind to Apple. Send in
> the report. This sends in some diagnostic details about Mail.app
> state when the crash occurred to Apple. Like crash reports are
> grouped together in a database and in a few weeks someone inside
> Apple gets a automated bug report with a title something like "172
> crashes in _funcname" along with some crash stack backtraces. If
> you have the opportunity to do so, please also send in information
> about what steps you can take to reproduce the crash. Usually, the
> hardest thing about fixing bugs is reproducing them.
>
> If you are a software developer registered with ADC you can short
> circuit the process and directly file a bug through
> bugreporter.apple.com. Please attach a crash log and explain how to
> reproduce the problem.
>
> This one sounds serious enough that it might be a candidate for a
> quick fix for the next MacOS X.4 support update, provided that the
> right people find out about it soon enough.
>
> Ian
>
> On Jul 7, 2007, at 1:15 PM, Douglas L. Theobald wrote:
>
>> Hey, I have the exact same problem. I haven't been able to read
>> SMIME signed/encrypted emails now for some time (Mail just
>> crashes). It is an intel apple bug of some sort. If you find
>> the email in ~/Library/Mail, you can plain text cut out the sig
>> and read the email. [Ick] This is especially annoying since
>> apple Mail used to have such nice native integration of SMIME.
|