On Tuesday, December 7, 2010, Benoit Jacob wrote:
> Hi,
>
> I would like to share some hopefully interesting thoughts, from a
> comparison of a few things in KDE and in Mozilla, in the hope that it
> helps KDE borrow good ideas from elsewhere.
thanks :)
> *
> 1. Issue tracker (Mozilla) vs. M
On 07.12.10 14:28:57, Benoit Jacob wrote:
> 2010/12/7 Andreas Pakulat :
> > On 07.12.10 11:22:47, Benoit Jacob wrote:
> >> *
> >> 4. Crash reports handling (KDE: poor, Mozilla: good)
> >> * Have a look at Socorro, Mozilla's crash report tool:
> >
> > Your info is outdated I think, try out a KD
2010/12/7 Stephen Kelly :
> Benoit Jacob wrote:
>
>> Hi,
>>
>> I would like to share some hopefully interesting thoughts, from a
>> comparison of a few things in KDE and in Mozilla, in the hope that it
>> helps KDE borrow good ideas from elsewhere.
>>
>> *
>> 1. Issue tracker (Mozilla) vs. Mail
On Tuesday, 7 de December de 2010 22:39:21 Boudewijn Rempt wrote:
> I implemented a socorro server and integrated breakpad in the desktop app I
> developed at Hyves. It was rather frightening, especially to maintain. And
> it seemed to only work with binaries you create and distribute yourself --
>
On Tuesday 07 December 2010, Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
> >> 2010/12/7 Thiago Macieira :
> >> > How are you going to properly find the stack without debug symbols?
> >> >
> >> > Imagine one frame that didn't k
On Tue, Dec 7, 2010 at 11:14 PM, Thiago Macieira wrote:
> On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > How are you going to properly find the stack without debug symbols?
>> >
>> > Imagine one frame that didn't keep the frame pointer properly?
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > How are you going to properly find the stack without debug symbols?
>> >
>> > Imagine one frame that didn't keep the frame pointer properly?
>>
>> If the stack is damaged
Benoit Jacob wrote:
> Hi,
>
> I would like to share some hopefully interesting thoughts, from a
> comparison of a few things in KDE and in Mozilla, in the hope that it
> helps KDE borrow good ideas from elsewhere.
>
> *
> 1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
Hi,
Are you sugg
On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > How are you going to properly find the stack without debug symbols?
> >
> > Imagine one frame that didn't keep the frame pointer properly?
>
> If the stack is damaged, then indeed I can't do anything;
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 21:13:53 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira :
>> > On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> >> So do crash reports now automatically land in a database that's easy
>> >> to do queries on? (See the
On Tuesday, 7 de December de 2010 21:13:53 Benoit Jacob wrote:
> 2010/12/7 Thiago Macieira :
> > On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
> >> So do crash reports now automatically land in a database that's easy
> >> to do queries on? (See the web interface provided by Socorro
2010/12/7 Benoit Jacob :
> 2010/12/7 Thiago Macieira :
>> On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>>> So do crash reports now automatically land in a database that's easy
>>> to do queries on? (See the web interface provided by Socorro)
>>>
>>> If I want to get a list of all
2010/12/7 Thiago Macieira :
> On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> So do crash reports now automatically land in a database that's easy
>> to do queries on? (See the web interface provided by Socorro)
>>
>> If I want to get a list of all KDE crashes that happened in lib
On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
> So do crash reports now automatically land in a database that's easy
> to do queries on? (See the web interface provided by Socorro)
>
> If I want to get a list of all KDE crashes that happened in libGL.so*,
> how do I go about that?
Phonon is currently preparing to move its repositories from Gitorious
to Git.KDE.org. Unfortunately we noticed that our current main Phonon
repository suffers from some metadata problems.
Due to this unfortunate situation we will have to rewrite the affected
part of the Git history to comply with
On Tuesday 07 December 2010 20:28:57 Benoit Jacob wrote:
> 2010/12/7 Andreas Pakulat :
> > On 07.12.10 11:22:47, Benoit Jacob wrote:
> >> *
> >> 4. Crash reports handling (KDE: poor, Mozilla: good)
> >
> >> * Have a look at Socorro, Mozilla's crash report tool:
> > Your info is outdated I thi
2010/12/7 Andreas Pakulat :
> On 07.12.10 11:22:47, Benoit Jacob wrote:
>> *
>> 4. Crash reports handling (KDE: poor, Mozilla: good)
>> * Have a look at Socorro, Mozilla's crash report tool:
>
> Your info is outdated I think, try out a KDE 4.5 app crashing. Dr.Konqi
> improved a _lot_ in the l
On 07.12.10 11:22:47, Benoit Jacob wrote:
> *
> 4. Crash reports handling (KDE: poor, Mozilla: good)
> * Have a look at Socorro, Mozilla's crash report tool:
Your info is outdated I think, try out a KDE 4.5 app crashing. Dr.Konqi
improved a _lot_ in the last year or so and its being actively
Hi Andreas
I tried to compile the plugin, however it seems that it does not support
kdeveplatform versions higher than 1.1.50. Is the plugin located in a repo
somewhere that compiles against newer versions of kdevplatform?
Regards
Morten
2010/12/4 Andreas Pakulat
> Hi everybody,
>
> I'm glad
> 4. Crash reports handling (KDE: poor, Mozilla: good)
To be clear, I know about Dr Konqi but afaics it relies on the user to
install debug symbols by himself, that's unrealistic. The symbols
lookup needs to be done server-side if you want this to work on a
large scale with non-technical users.
B
Hi,
I would like to share some hopefully interesting thoughts, from a
comparison of a few things in KDE and in Mozilla, in the hope that it
helps KDE borrow good ideas from elsewhere.
*
1. Issue tracker (Mozilla) vs. Mailing lists (KDE).
KDE uses a Mailing list for most its development discu
El Miércoles, 3 de Noviembre de 2010 06:08:15 kunal ghosh escribió:
> Hi,
>
> I just downloaded KDE 4.5.2 iso image from http://home.kde.org/~kdelive/
> and verified the sha256sum
>
> i am getting the checksum as
>
> ku...@kunal-desktop:~$ sha256sum KDE-Reloaded.x86_64-4.5.2-Build1.6.iso
> *a5ce
On Tue, 7 Dec 2010 06:21:49 PM Aaron J. Seigo wrote:
> On Monday, December 6, 2010, lindsay.mathie...@gmail.com wrote:
> > Any chance of https://bugs.kde.org/show_bug.cgi?id=229614 being
> > confirmed?
>
> confirmed isn't important (since we lack a formalized triage system in the
> first place).
On Monday, December 6, 2010, lindsay.mathie...@gmail.com wrote:
> Any chance of https://bugs.kde.org/show_bug.cgi?id=229614 being
> confirmed?
confirmed isn't important (since we lack a formalized triage system in the
first place). what's important is having a way to reproduce it. which we don't
24 matches
Mail list logo
