> Siddhartha Sahu wrote:
> Ah. Why did I not think of that. Obvious in hindsight :D
>
> Discarding the RR then. Thanks!
>
> Teemu Rytilahti wrote:
> This is probably not the proper forum to ask, but the annoying problem of
> jumpy brightness would in my o
> On March 29, 2015, 6:34 p.m., Kai Uwe Broulik wrote:
> > Thank you for this patch!
> >
> > However, we chose to remove the percentage from the brightness sliders in
> > the battery monitor since you basically change the brightness to your
> > liking and not to some odd percentage, so adding
Martin Sandsmark wrote:
> On Thu, Feb 07, 2013 at 01:58:14AM +0100, Teemu Rytilahti wrote:
>> What kind of reports are those useless ones? Dupes? Downstream bugs?
>> Missing information? In my opinion reporting bugs to b.k.o is not that
>> easy (or I've become lazy) as i
;t
> want to see anything done to make it easier.
>
> And no, we cannot expect users to recognize a duplicate crash, That's too
> difficult, we can also not expect users from recognizing whether a
> backtrace is useful.
True, it's up to the system to handle dups and invalid backtraces, imo.
--
Best Regards,
Teemu Rytilahti
r (though when collecting all the crashes to a separate crash reporting
system, it'll give nice stats how common the crash is) without even adding
that information to the bug-tracker.
--
Best Regards,
Teemu Rytilahti
ows sending the traces for aggregation. That doesn't
apply for regular bugs though...
--
Best Regards,
Teemu Rytilahti
gs? Missing
information? In my opinion reporting bugs to b.k.o is not that easy (or I've
become lazy) as it should be and that's why I'm wondering..
Bogus & spam can probably be handled more or less automatically, when we
know what we want and what's are the problems currently.
--
Best Regards,
Teemu Rytilahti
I'm sure there are plenty of cases where a "work-
around" information would be really useful also in cases when the bug is not
easily fixable (see Akregator&Metakit crashes, some KWin crashes probably
too?).
--
Best Regards,
Teemu Rytilahti
in their Bugzilla are then linked (and
vice-versa?) to the crash reports, see https://crash-
stats.mozilla.com/products/Firefox .
Btw, what kind of reports are they mostly you're marking as dupes/invalids?
Not crashes I assume, as DrKonqi should do dupe-checking before letting one
to submit reports..
--
Best Regards,
Teemu Rytilahti
> backtraces.
> +1
> The existing solutions are very complex and have lots of features. And
> they solve different
> use cases.
Have you already looked into traceparser (or any other similar system) to
see how it does the tricks? Just wondering if code from there could be
reused.
--
Best Regards,
Teemu Rytilahti
ould store all crashes, also duplicates
> - maybe it's a false positive (that's what Teemu is talking about I think)
> - it's an important fact to see how common a crash is
Exactly.
--
Best Regards,
Teemu Rytilahti
bugs, as
an example). Same applied to other apps might cause some need to sanitize
and/or let users to choose what to send.
--
Best Regards,
Teemu Rytilahti
:
>> 1. User encounters a crash and is asked whether to send a
>> report.
>> 2. If yes, a backtrace is being send to the server.
>> 3. If there's a complete match, just inform the user about it
>> and give a
>> link to a bug report / perhaps allow add a new comment to
>> report?
>
> only if: bug is not fixed or current version is *higher* than the assumed
> fixed-in version.
Yes.
> 8. developer fixes bug, associates a "solution" to the crash, user that
> reported the crash gets an email notification.
>
> this is pretty crucial and the whole point of this proposal...
Indeed. Sounds good to me.
--
Best Regards,
Teemu Rytilahti
e being, I think. Sorry for the
lengthy mail, but
hope there's some food for thought in there.
[1] https://blog.mozilla.com/webdev/2010/05/19/socorro-
mozilla-crash-
reports/
[2] https://crash-stats.mozilla.com/products/Firefox
[3]
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.148.716&rep=rep1&type=pdf
[4] http://www.piware.de/2011/11/apport-1-90-client-side-
duplicate-checking/
[5] https://launchpad.net/bugzilla-traceparser
[6] https://git.reviewboard.kde.org/r/102921/
--
Best Regards,
Teemu Rytilahti
14 matches
Mail list logo
