qreator-discuss team mailing list archive

[Stefan Schwarzburg <stefan.schwarzburg@xxxxxxxxx>]

Hi David,
I'm not able to access that information, but it seems very valuable indeed!

"
Sorry, you are not a member of a group that is allowed to see the data from
error reports. A non-disclosure agreement is being written that will allow
for wider access.
"

Cheers,
Stefan

On Mon, Jun 3, 2013 at 11:14 AM, David Planella
<david.planella@xxxxxxxxxx>wrote:

> Hi,
>
> I've just discovered that Qreator crashes and tracebacks are
> automatically sent to the Error Tracker:
>
> https://errors.ubuntu.com/?package=qreator&period=year
>
> This provides an invaluable resource to catch bugs in Qreator. I'll be
> looking into this in the next few days, and we might need to file some
> new bugs in light of these results.
>
> The way it works is the following:
>
> - All crashes are sent to errors.ubuntu.com according to the user's
>   privacy settings
> - Bugs are created against the Ubuntu package *only* if the package is
>   in main or universe (Qreator is not there yet)
> - Bugs are created against the Ubuntu package *only* for the
>   development series
> - Bugs can be created for the upstream project if the package ships an
>   apport hook (*).
>
> Cheers,
> David.
>
> (*) To create an apport hook:
> - Documentation: /usr/share/doc/apport/package-hooks.txt.gz,
>   section "Customize the crash DB to use"
> - Upstream bug report example:
>   /usr/share/apport/package-hooks/source_linux-nexus7.py
>
> --
> Mailing list: https://launchpad.net/~qreator-discuss
> Post to     : qreator-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~qreator-discuss
> More help   : https://help.launchpad.net/ListHelp
>