On Tue, Mar 13, 2012 at 12:27, Thomas Zander 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
> knowledge
On Tue, Mar 13, 2012 at 09:47, 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 ?
well, that's off topic for this thread. But still would probably
make sense to h
On Mon, Mar 12, 2012 at 22:20, Teemu Rytilahti 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 in
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
>> insta
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 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
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 Sun, Mar 11, 2012 at 20:54, Gary Greene wrote:
> Ubuntu has something similar iirc, same goes with the Linux Kernel project.
> (I recall hearing about it a couple years ago while at Google, so my memory
> could be a little fuzzy….)
>
yes they have apport, see: https://wiki.ubuntu.com/CrashRep
Am 11.03.2012 17:34 schrieb "Steven Sroka" :
>
>
> 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
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
12 matches
Mail list logo
