Niko Sams wrote:
>> Personally I'd go for a solution that also tries to register the last 20
>> keystrokes and 20 mouse clicks (qt global event listener) and if and when
>> a crash occurs that info can be send with the backtrace. So even if
>> there are no debug packages installed we get some inf
Niko Sams wrote:
> yeah, those people commenting after every release that the bug is
> still not (magically) fixed :D
One thing could be that the problem is caused by some other component in the
system. Or perhaps it's just the human nature doing its tricks there?
Nevertheless, if there's a ne
Niko Sams wrote:
> Interesting. But no system provides a "solution" I think.
> Socorro looks very powerful - but they need to process much more
> crashes.
Actually at least Microsoft does, not sure about the others. Not sure how
much is it used though, but the system has a capability to give an
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104244/
---
Review request for kdelibs.
Description
---
KJS: Implement Object.Get
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104243/
---
Review request for kdelibs.
Description
---
KJS/Grammar: Introduce ne
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104198/#review11343
---
Ship it!
Ship It!
- John Layt
On March 8, 2012, 11:04 p.m.,
Am Montag 12 März 2012, 19:26:27 schrieb Niko Sams:
> On Sun, Mar 11, 2012 at 13:57, henry miller wrote:
> > Good ideas, if anyone actually implements it. A couple of comments.
> >
> > Most users are not programmers - they will not know how to recogize
> > similear backtraces are the same root cau
On Mon, Mar 12, 2012 at 11:36, Thomas Zander wrote:
> On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
>>
>> I'd like to talk about an idea on how DrKonqi
>
> []
>>
>> What software could crashes.kde.org run? I'm not sure, maybe abugzilla
>> installation or somethingcustom written. Or some other
On Mon, Mar 12, 2012 at 17:32, Thomas Zander wrote:
> On Monday 12 March 2012 16.20.00 David Jarvie wrote:
>> There would be an advantage in giving instant feedback to the user if
>> possible, but if that turns out to be impractical, Thomas's suggestion of
>> using background processing on the ser
On Mon, Mar 12, 2012 at 01:14, Teemu Rytilahti wrote:
> This really depends on how it'd be used, but perhaps yeah,
> this might be a
> good idea indeed. This is something I encountered while
> working on a course
> paper earlier this semester. Similar systems are up there for
> Mozilla
> (Socorro[
On Mon, Mar 12, 2012 at 09:54, Milian Wolff wrote:
> On Monday 12 March 2012 02:14:00 Teemu Rytilahti wrote:
>> - When getting duplicate backtraces from users the bug entry
>> could be
>> updated automatically with the version the crash happened,
>> this would in my
>> opinion be a plus in a sense
On Monday 12 March 2012 19:39:12 Niko Sams wrote:
> On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin wrote:
> > On Monday 12 March 2012 19:26:27 Niko Sams wrote:
> >> On Sun, Mar 11, 2012 at 13:57, henry miller wrote:
> >> > Good ideas, if anyone actually implements it. A couple of comments.
> >> >
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin wrote:
> On Monday 12 March 2012 19:26:27 Niko Sams wrote:
>> On Sun, Mar 11, 2012 at 13:57, henry miller wrote:
>> > Good ideas, if anyone actually implements it. A couple of comments.
>> >
>> > Most users are not programmers - they will not know how
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
> On Sun, Mar 11, 2012 at 13:57, henry miller wrote:
> > Good ideas, if anyone actually implements it. A couple of comments.
> >
> > Most users are not programmers - they will not know how to recogize
> > similear backtraces are the same root caus
On Sun, Mar 11, 2012 at 13:57, henry miller wrote:
> Good ideas, if anyone actually implements it. A couple of comments.
>
> Most users are not programmers - they will not know how to recogize similear
> backtraces are the same root cause. Worse I know of many cases where I - a
> programmer - was
On Monday 12 March 2012 16.20.00 David Jarvie wrote:
> There would be an advantage in giving instant feedback to the user if
> possible, but if that turns out to be impractical, Thomas's suggestion of
> using background processing on the server could be sensible.
I was thinking about this a bit lo
On Mon, March 12, 2012 10:36 am, Thomas Zander wrote:
> On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
>> I'd like to talk about an idea on how DrKonqi
> []
>> What software could crashes.kde.org run? I'm not sure, maybe abugzilla
>> installation or somethingcustom written. Or some other bugtrac
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104149/#review11318
---
This review has been submitted with commit
11c7c9adcce7f476b32
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104149/#review11317
---
Ship it!
Ship It!
- Jeremy Paul Whiting
On March 4, 2012, 2
Milian Wolff wrote:
Hi again,
> While nice this is not required for Niko's proposal. Either the backtrace
> is automatically associated with a solution, or a developer later on
> associates it with a solution or a bug report. In the former case, the
> user gets direct feedback on what's going on.
On Sunday 11 March 2012 11.26.53 Niko Sams wrote:
I'd like to talk about an idea on how DrKonqi
[]
What software could crashes.kde.org run? I'm not sure, maybe abugzilla
installation or somethingcustom written. Or some other bugtracking software.
I'd say this is a great idea, mostly because i
On Monday 12 March 2012 02:14:00 Teemu Rytilahti wrote:
> Niko Sams wrote:
> > Hi,
>
> Hello, more discussion about how to handle bugs are welcome, I
> hope. Wasn't
> able to get in to the earlier thread, so I thought I should
> post something
> here.
>
> > In short: DrKonqi shouldn't create bugs
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104221/#review11310
---
This review has been submitted with commit
5bc91690dff7c3608d3
Niko Sams wrote:
> Hi,
Hello, more discussion about how to handle bugs are welcome, I
hope. Wasn't
able to get in to the earlier thread, so I thought I should
post something
here.
> In short: DrKonqi shouldn't create bugs directly but talk to
a "layer"
> between.
This really depends on how
24 matches
Mail list logo
