On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Friday 24 February 2012 02:15:54 Sven Burmeister wrote:
Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin:
Personally I'm not sure whether the MeeGo bugzilla can be compared to
the KDE one (technical
On Friday 24 February 2012 21:03:42 Ben Cooksley wrote:
On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin mgraess...@kde.org wrote:
On Friday 24 February 2012 02:15:54 Sven Burmeister wrote:
Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin:
Personally I'm not sure whether the
On Friday, February 24, 2012 08:06:41 Martin Gräßlin wrote:
Consider that we have to ask again and again for all those things to find
out in the end that it is a known issue with $foo driver in combination
with $bar feature. All these things could so easily be handled by a first
level
On Thursday, February 23, 2012 04:57:16 PM David Edmundson wrote:
First of all, the bugzilla is supposed to be a communication tool between
the user and the developer.
Or is it?
If I understand Martin correctly, he wants bugzilla to be a list of
things broken in my app, not a
On Tuesday, February 21, 2012 11:37:23 PM Milian Wolff wrote:
What version will the new bugzilla have? Are the REST/JSON/XMLRPC APIs
going to be enabled?
And then maybe someone can revive kbugbuster.
Andras
On Friday 24 February 2012 10:58:39 Andras Mantia wrote:
I know this does not affect regular releases in distributions, but it is
very bad for those working/testing KDE master.
Not only master, the same happens to me in my self-compiled KDE-4.8
environment.
Let's just fix this the BC way, by
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets broken for kde installed from source due to
incorrect plugin path is an issue with Qt installantion, and/or with
On 02/24/2012 11:21 AM, Hugo Pereira Da Costa wrote:
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets broken for kde installed from source due to
incorrect
On 02/24/2012 11:25 AM, Hugo Pereira Da Costa wrote:
On 02/24/2012 11:21 AM, Hugo Pereira Da Costa wrote:
Hi Andras,
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
the fact that oxygen gets
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
Then please correctly bump its SONAME, instead of using the same SONAME
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104054/#review10864
---
kdepasswd/kcm/chfacedlg.cpp
On 02/24/2012 11:43 AM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
no there is no guarantee for liboxygenstyle.so.4, and I don't plan to
guarantee it.
It is all internal to kde-workspace, and has no public api.
Then please correctly bump its SONAME,
On sexta-feira, 24 de fevereiro de 2012 11.49.44, Hugo Pereira Da Costa wrote:
despite the fact that you have a local kde build, the pluggins that gets
loaded by Qt when running a KDE or Qt application are not the ones you
compiled. An old one is used instead, that is inconsistent with the
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
Correct.
Make sure that your new KDE's installation is found by the Qt plugin
system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I have this:
printenv QT_PLUGIN_PATH
On 02/24/2012 11:51 AM, Thiago Macieira wrote:
On sexta-feira, 24 de fevereiro de 2012 11.49.44, Hugo Pereira Da Costa wrote:
despite the fact that you have a local kde build, the pluggins that gets
loaded by Qt when running a KDE or Qt application are not the ones you
compiled. An old one is
On 02/24/2012 11:56 AM, Andras Mantia wrote:
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
Correct.
Make sure that your new KDE's installation is found by the Qt plugin
system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I have this:
printenv
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
On 02/24/2012 12:01 PM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
On 02/24/2012 11:43 AM, Pino Toscano wrote:
Alle venerdì 24 febbraio 2012, Hugo Pereira Da Costa ha scritto:
no
On Friday, February 24, 2012 12:01:37 PM Hugo Pereira Da Costa wrote:
are other applications also crashing (like, e.g. plasma workspace, or
kwin) ? (It should)
if not it might be a QtCreator specific issue.
Yes, also kde apps crash, like kdesvn, kate, etc.
Andras
On Fri, 24 Feb 2012, Alex Merry wrote:
On 24/02/12 09:22, Thorsten Zachmann wrote:
Why not have a state for bugs that you know are worth fixing? Then the
developers can concentrate on those and Other people can do the initial
cleaning to get the bugs to a state they can be closed or the proper
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104054/
---
(Updated Feb. 24, 2012, 1:25 p.m.)
Review request for KDE Base Apps.
On Friday 24 February 2012, Martin Gräßlin wrote:
On Friday 24 February 2012 21:03:42 Ben Cooksley wrote:
On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin mgraess...@kde.org
...
Consider that we have to ask again and again for all those things to
find out in the end that it is a known
On Friday 24 February 2012, Ben Cooksley wrote:
On Fri, Feb 24, 2012 at 11:41 AM, Kevin Ottens er...@kde.org wrote:
On Thursday 23 February 2012 17:39:12 Trever Fischer wrote:
Random, possibly entirely unhelpful suggestion: Perhaps using our
redmine install of projects.kde.org for this kind
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for what else... a bug (and wishlist)
reporting tool for users.
The problem here that this is noise prone and the low entropy isn't
helping anyone (and i'm not talking about users should not
On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote:
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for what else... a bug (and wishlist)
reporting tool for users.
The problem here that this is noise prone and the low entropy
On 2012-02-24, Hugo Pereira Da Costa h...@oxygen-icons.org wrote:
I understand that. The point I was trying to make, is that you would
still get the old pluggin, admittingly without crashing, but which
would nonetheless be not correct.
Whattabout just linking liboxygenstyle static into the
On Friday 24 February 2012 19:32:10 Andras Mantia wrote:
On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote:
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for what else... a bug (and
wishlist)
reporting tool for users.
On 2012-02-22, David Faure fa...@kde.org wrote:
up with was the few cases where bugs turned into actual political flamewars;
his answer was obviously give rights to everyone, and remove rights when
someone abuses them. This is also what we do for SVN/GIT, so why don't we do
this for
Am Freitag, 24. Februar 2012, 08:06:41 schrieb Martin Gräßlin:
My claim is that most of that user support only ends-up in bugzilla
because people did not get help somewhere else, e.g. because only
developers are familiar enough with the code to understand the issue.
No, that is clearly
Am Freitag, 24. Februar 2012, 18:51:11 schrieb Martin Gräßlin:
On Friday 24 February 2012 19:32:10 Andras Mantia wrote:
On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote:
Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia aman...@kde.org:
Bugzilla is not a to-do list, it is for
On Friday 24 February 2012 19:11:12 Sven Burmeister wrote:
Am Freitag, 24. Februar 2012, 08:06:41 schrieb Martin Gräßlin:
My claim is that most of that user support only ends-up in bugzilla
because people did not get help somewhere else, e.g. because only
developers are familiar enough
On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote:
- first level support
issues are not opened on the bug tracker but in a user support management
system - e.g. forums.kde.org. Only if the supporters figure out that there
is a real bug, they will open a bug report. This is high
On Friday 24 February 2012 19:27:09 Sven Burmeister wrote:
yes, of course, we have to help the users. But they need to get a tool for
user support, not a tool for developer communication. We need a
first-level- support to help the users. Developers are the
third-level-support.
I doubt
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104062/
---
Review request for kdelibs and David Faure.
Description
---
We need
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104065/
---
Review request for kdelibs and David Faure.
Description
---
Add a
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104067/
---
Review request for kdelibs and David Faure.
Description
---
We can
On Fri, Feb 24, 2012 at 11:56, Andras Mantia aman...@kde.org wrote:
On Friday, February 24, 2012 11:51:51 AM Thiago Macieira wrote:
Correct.
Make sure that your new KDE's installation is found by the Qt plugin
system, either by setting QT_PLUGIN_PATH or by editing Trolltech.conf.
I
On Fri, Feb 24, 2012 at 8:44 AM, Andras Mantia aman...@kde.org wrote:
On Thursday, February 23, 2012 04:57:16 PM David Edmundson wrote:
First of all, the bugzilla is supposed to be a communication tool between
the user and the developer.
Or is it?
If I understand Martin correctly, he wants
On Friday, February 24, 2012 07:28:33 PM Martin Gräßlin wrote:
User asking on distro/KDE mailinglist/forum/IRC because xyz does not work.
1. he gets an answer
1.1 known bug
1.2 me too - the user might open a bug report
1.3 it works like this…
2. he does not get an answer
On Friday 24 February 2012 20:31:46 Andras Mantia wrote:
On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote:
- first level support
issues are not opened on the bug tracker but in a user support management
system - e.g. forums.kde.org. Only if the supporters figure out that
(please CC me, I'm not subscribed to k-c-d)
Hello everyone,
given the discussion going on with how to handle bug reports, I've seen a few
mentions of first line support that would help reduce the number of improper
bugs filed in bugs.kde.org.
Well... the good news is that such a thing already
On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote:
On 2012-02-24, Hugo Pereira Da Costa h...@oxygen-icons.org wrote:
I understand that. The point I was trying to make, is that you would
still get the old pluggin, admittingly without crashing, but which
would nonetheless be not
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104071/
---
Review request for KDE Base Apps and David Faure.
Description
---
42 matches
Mail list logo
