Hi Harald,
Did you try using machine translation to understand users' reports?
Regards,
Alexander Potashev
On Fri, Apr 15, 2022 at 11:38 AM Harald Sitter wrote:
>
> Moin
>
> for the longest of times we have drkonqi say that crash reports must
> be in english, yet people still file reports in ot
On 23.09.20 12:08, Harald Sitter wrote:
> On 17.09.20 17:00, Hannah von Reth wrote:
>> So with the availability of KDE applications in the Windows store we
>> don't need drkonqi.
>>
>> We get perfect reports, if the users privacy settings allow it, for each
>> submitted app separately.
>>
>> Every
On 17.09.20 17:00, Hannah von Reth wrote:
> So with the availability of KDE applications in the Windows store we
> don't need drkonqi.
>
> We get perfect reports, if the users privacy settings allow it, for each
> submitted app separately.
>
> Every maintainer can request access to the store, for
So with the availability of KDE applications in the Windows store we
don't need drkonqi.
We get perfect reports, if the users privacy settings allow it, for each
submitted app separately.
Every maintainer can request access to the store, for submissions and
reports.
So I guess we should fo
Hi,
looks like some quoted text is missing.
I have no idea bout the state of drkonqi on windows,
ages ago a gsoc student did *things* but I don't think anybody was ever
able to use it.
I can remember a more recent communication that people where trying
again to get it to work.
But I don't
And for the build error:
*10:53:51* CMake Error at CMakeLists.txt:26 (find_package): *10:53:51*
Could not find a configuration file for package "Qt5" that is compatible
*10:53:51* with requested version "5.15.0". *10:53:51* You'd need to ask
Ben to update the image used for the ci, normal setu
On Thu, Sep 17, 2020 at 4:17 PM Hannah von Reth wrote:
>
> Hi,
>
> looks like some quoted text is missing.
>
> I have no idea bout the state of drkonqi on windows,
> ages ago a gsoc student did *things* but I don't think anybody was ever
> able to use it.
>
> I can remember a more recent communica
On Thu, Sep 17, 2020 at 1:07 PM David Edmundson
wrote:
>
> >yet it gets built on windows. shall we stop
> doing that
>
> AFAIK it is used and this was something explicitly requested.
I seem to recall it not being used and Hannah also not knowing why we
would. Ccing.
> There is a KF6 workboard ta
>yet it gets built on windows. shall we stop
doing that
AFAIK it is used and this was something explicitly requested.
There is a KF6 workboard task to get into frameworks for kf6
David
Yay for split! Well done \o/
On Sun, Aug 13, 2017 at 10:16 PM, David Edmundson
wrote:
> Harald, can you sort out all the cmake of both relating to your fancy unit
> test.
cmake logic is isolated inside the tests dir, so plasma-workspace and
the new drkonqi should be fine as is.
https://build.kd
On Fri, Jul 28, 2017 at 2:27 PM, David Edmundson
wrote:
> Please can someone review kde:scratch/davidedmundson/drkonqi
LGTM
(not split defects but: README, AUTHORS, LICENSE, ToDo and doc could
be moved into the main dir, conversely config-x11.h could be merged
into config-drkonqi.h and removed f
Please can someone review kde:scratch/davidedmundson/drkonqi
David
This came up during akademy with someone.
I've split drkonqi into its own repo. (Not pushed). It's a git-filter
branch with all history looking neat.
I don't intend to move it outside of workspace as that's always an absolute
nightmare. Being a standalone repo will hopefully be enough, and we can
On Sunday, 19 March 2017 at 16:22, Martin Gräßlin wrote:
> Am 2017-03-19 14:19, schrieb Kai Uwe Broulik:
> > I'd be fine with splitting drkonqi into its own repository, René
> > recently brought this up as well.
>
> Ideally it would be part of KF5, e.g. a kcrash-runtime tier-3 repo.
So how should
On Mon, Mar 20, 2017 at 12:14 AM, Andreas Sturmlechner <
andreas.sturmlech...@gmail.com> wrote:
> On Sunday, 19 March 2017 at 14:19, Kai Uwe Broulik wrote:
> > I'd be fine with splitting drkonqi into its own repository, René recently
> > brought this up as well.
>
> Since I was pondering the idea
On Sunday, 19 March 2017 at 14:19, Kai Uwe Broulik wrote:
> I'd be fine with splitting drkonqi into its own repository, René recently
> brought this up as well.
Since I was pondering the idea anyway, might as well attach my patch to build
drkonqi standalone from its subdir.
commit 1ee858f194fd2c8
Am 2017-03-19 14:19, schrieb Kai Uwe Broulik:
I'd be fine with splitting drkonqi into its own repository, René
recently brought this up as well.
Ideally it would be part of KF5, e.g. a kcrash-runtime tier-3 repo.
It might need some adjustments to the environment it runs in, though.
In Plasma
I'd be fine with splitting drkonqi into its own repository, René recently
brought this up as well.
It might need some adjustments to the environment it runs in, though. In Plasma
we show an SNI and an interactive notification. Other platforms might not
support interactive notifications.
On 19.03.2017 11:56, Christoph Feck wrote:
> Using openSUSE packages here, installing drkonqi does not drag in the
> Plasma workspace, only some KF5 frameworks. So the splitting can also be
> done by the distribution.
Them fixing it in packaging does not make it right though. Everone building
d
On 19.03.2017 11:52, Jasem Mutlaq wrote:
Problem is DrKonqi is now part of plasma-workspace. This makes it a *HUGE*
dependency just for crash reporting. I obviously cannot ask non-KDE users
to install plasma-workspace _just_ to have crash reporting capabilities.
Using openSUSE packages here, in
Martin Klapetek wrote:
>> Bug trackers are not trace trackers. Spending time on solving the
>> actual problem is the best thing https://retrace.fedoraproject.org/
>> https://errors.ubuntu.com/
>
>
> They're not, yet we're using it as one. So might as well improve
> the experience at least a bit
On Wed, Nov 2, 2016 at 6:32 AM, Harald Sitter
wrote:
> On Wed, Nov 2, 2016 at 11:04 AM, René J. V. Bertin
> wrote:
> > Martin Klapetek wrote:
> >
> >
> >> For improving readability, there is bugzilla-traceparser plugin, that
> can
> >> dynamically
> >> hide long backtraces with a bit of
On Wed, Nov 2, 2016 at 11:04 AM, René J. V. Bertin wrote:
> Martin Klapetek wrote:
>
>
>> For improving readability, there is bugzilla-traceparser plugin, that can
>> dynamically
>> hide long backtraces with a bit of JS magic to expand them and much
>> more
>> like finding duplicates and
Martin Klapetek wrote:
> For improving readability, there is bugzilla-traceparser plugin, that can
> dynamically
> hide long backtraces with a bit of JS magic to expand them and much
> more
> like finding duplicates and also auto-dupe. I still think this would help
> tremendously to
> all
On Tue, Nov 1, 2016 at 6:24 AM, David Edmundson
wrote:
> On Tue, Nov 1, 2016 at 9:28 AM, René J.V. Bertin
> wrote:
>
>> Hi,
>>
>> Sorry if this has already been answered somewhere where I've missed it:
>>
>> DrKonqi has lost much of its interest (in v5.8.2) due to recent changes
>> in BKO. Most
David Edmundson wrote:
> As attachments is awful. You cannot search if it's in an attachment.
> Searching is ridiculously important.
True. FWIW, the bug I tried to report this morning (which led to this mail)
came
up with 0 possibly related reports, while it turned out I'd already reported
al
On Tue, Nov 1, 2016 at 9:28 AM, René J.V. Bertin
wrote:
> Hi,
>
> Sorry if this has already been answered somewhere where I've missed it:
>
> DrKonqi has lost much of its interest (in v5.8.2) due to recent changes in
> BKO. Most of the crashes I've been trying to report via the tool have led
> to
FYI: https://bugs.kde.org/show_bug.cgi?id=371934
R.
28 matches
Mail list logo
