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 url
On Mon, Mar 12, 2012 at 22:20, Teemu Rytilahti t...@iki.fi wrote:
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
Hi all,
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
...
*cough*
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
Regards,
Ben
On Tue, 13 Mar 2012, Ben Cooksley wrote:
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
That looks very interesting and user-friendly to me.
Boudewijn
(who still has nightmares
On Tue, Mar 13, 2012 at 09:47, Ben Cooksley bcooks...@kde.org wrote:
Hi all,
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
well, that's off topic for this thread. But still would probably
Quoting Ben Cooksley bcooks...@kde.org:
Whilst I have not evaluated it's compatibility with Bugzilla 4.2, I do
not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
The traceparser might be a good-enough solution for finding duplicates
and helping the reading of
Quoting Niko Sams niko.s...@gmail.com:
On Mon, Mar 12, 2012 at 17:32, Thomas Zander zan...@kde.org 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
On Tuesday 13 March 2012 10:30:59 Thomas Zander wrote:
Quoting Ben Cooksley bcooks...@kde.org:
Whilst I have not evaluated it's compatibility with Bugzilla 4.2,
I do not suppose anyone has looked at
https://launchpad.net/bugzilla-traceparser ?
The traceparser might be a good-enough
On Tue, Mar 13, 2012 at 17:25, Martin Gräßlin mgraess...@kde.org wrote:
On Tuesday 13 March 2012 17:00:29 Christoph Feck wrote:
...
I have long been interested why users keep reporting duplicates.
Instead of guessing, let's just ask them in a nice way. I added
Don't forget security and privacy. The last n keys would be a bad thing to have
if the user just entered a password.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Thomas Zander zan...@kde.org wrote:
Quoting Niko Sams niko.s...@gmail.com:
On Mon, Mar 12, 2012 at
On Tue, Mar 13, 2012 at 12:27, Thomas Zander zan...@kde.org wrote:
Hmm, its indeed not easy to find something fitting. Looking at the code of
one of the links found in this thread, I notice its written in perl. While I
understand the urge to do that, I'm not convinced that there is enough perl
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
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 directly
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
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. In
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 bugtracking
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com 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
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements it. A couple of comments.
Most users are not
On Monday 12 March 2012 19:39:12 Niko Sams wrote:
On Mon, Mar 12, 2012 at 19:34, Martin Gräßlin mgraess...@kde.org wrote:
On Monday 12 March 2012 19:26:27 Niko Sams wrote:
On Sun, Mar 11, 2012 at 13:57, henry miller h...@millerfarm.com wrote:
Good ideas, if anyone actually implements it. A
On Mon, Mar 12, 2012 at 09:54, Milian Wolff m...@milianw.de 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
On Mon, Mar 12, 2012 at 01:14, Teemu Rytilahti t...@iki.fi 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
On Mon, Mar 12, 2012 at 17:32, Thomas Zander zan...@kde.org 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
On Mon, Mar 12, 2012 at 11:36, Thomas Zander zan...@kde.org 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
Hi,
I'd like to talk about an idea on how DrKonqi (which is a really
useful thing btw) could be
further improved.
In short: DrKonqi shouldn't create bugs directly but talk to a layer between.
DrKonqi - crashes.kde.org - bugs.kde.org
crashes.kde.org is a new web application - a bit similar to
Søndag den 11. marts 2012 11:26:53 skrev Niko Sams:
Hi,
I'd like to talk about an idea on how DrKonqi (which is a really
useful thing btw) could be
further improved.
In short: DrKonqi shouldn't create bugs directly but talk to a layer
between.
DrKonqi - crashes.kde.org - bugs.kde.org
On 2012-03-11, at 10:21 AM, Milian Wolff wrote:
On Sunday 11 March 2012 11:26:53 Niko Sams wrote:
Hi,
I'd like to talk about an idea on how DrKonqi (which is a really
useful thing btw) could be
further improved.
In short: DrKonqi shouldn't create bugs directly but talk to a layer
Am 11.03.2012 17:34 schrieb Steven Sroka sroka.ste...@gmail.com:
On 2012-03-11, at 10:21 AM, Milian Wolff wrote:
On Sunday 11 March 2012 11:26:53 Niko Sams wrote:
Hi,
I'd like to talk about an idea on how DrKonqi (which is a really
useful thing btw) could be
further improved.
In
On Mar 11, 2012, at 3:26 AM, Niko Sams wrote:
Hi,
I'd like to talk about an idea on how DrKonqi (which is a really
useful thing btw) could be
further improved.
In short: DrKonqi shouldn't create bugs directly but talk to a layer
between.
DrKonqi - crashes.kde.org - bugs.kde.org
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 wrong.
The more automated detection we can do the better.
30 matches
Mail list logo
