<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>
<br>----- Original message -----
<br>> Hi,
<br>>
<br>> ext Randall Arnold wrote:
<br>> > Thanks Attila! I just uploaded a more recent update to the PDF
<br>> > (<a href="http://maemo-daemons.org/MeeGo_User_Experience_Framework.pdf">http://maemo-daemons.org/MeeGo_User_Experience_Framework.pdf</a>)
<br>> > based on helpful feedback so far.
<br>>
<br>> Some comments on the bug reporting thing.
<br>>
<br>> We already have Crash reporter which collects crashes.
<br>>
<br>>
<br>> Creating automated bug reports from crashes isn't useful because:
<br>>
<br>> * Users don't write detailed enough use-case descriptions
<br>> to the crash uploads. It's slightly too inconvenient to
<br>> do that with the device.
<br>>
<br>> * Bugs are related to use-cases, not crashes. Without a reproducible
<br>> use-case, bugs are usually worthless as you cannot even verify
<br>> potential fixes to them i.e. tell when the issue is fixed.
<br>>
<br>>
<br>> Telling for which _already existing_ bug crash is related to is
<br>> useful though and Crash reporter already supports that for (internal)
<br>> bugs. Due to screen size constraints bug number is given as a keyword
<br>> in note field instead of there being a separate field for it though.
<br>> There are going to be some updates to Crash reporter soon so that user
<br>> can select which bugs to upload (so that unrelated core dumps can be
<br>> uploaded separately or ignored).
<br>>
<br>>
<br>> Crash reporting isn't currently targeted for normal users
<br>> for few reasons:
<br>>
<br>> * Crash dumps are large and can contain private information
<br>> (like passwords). Hopefully in Harmattan we can can use
<br>> minidumps that contain only enough information for backtraces,
<br>> not all the process data.
<br>>
<br>> * Installing syslog means that user's rootfs can run out of space
<br>> if the log file grows too large (syslog is run as root). Syslog
<br>> can also contain private information (user names etc).
<br>>
<br>> * Crash dumps in heavily loaded device will make the situation
<br>> worse (whole crashing process needs to be swapped in for core
<br>> dump etc).
<br>>
<br>>
<br>> - Eero
<br>
<br>Thanks for the information Eero.  However, I'm looking to overcome the issues you cite rather than just accept them as inescapable.
<br>
<br>Randy</p>
<br><br>
--------------------------------------------------------------</br>
<div style="clear:both">Ovi Mail: Create an account directly from your phone<br>
http://mail.ovi.com<br>
</div>
</body>
</html>