Re: bugzilla situation

Am 24.02.2012, 18:32 Uhr, schrieb Andras Mantia : If you can moderate it, it means you have time and resource to do it, so you could have done until now as well. You cannot moderate bugzilla atm. (maybe Dr. Konqui is, but then you will also lose valid reports). Any other suggestion? Regard

Re: Re: bugzilla situation

On Friday 24 February 2012 20:36:12 Andras Mantia wrote: > 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 u

Review Request: Always request small icons for Konqueror's status bar.

--- 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 --- The

Re: Binary compatiblity for liboxygenstyle.so

On Friday, February 24, 2012 05:48:36 PM Sune Vuorela wrote: > On 2012-02-24, Hugo Pereira Da Costa 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. > > Wh

First line support outside of bugs.kde.org (cf. Bugzilla discussion)

(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

Re: Re: bugzilla situation

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

Re: bugzilla situation

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

Re: bugzilla situation

On Fri, Feb 24, 2012 at 8:44 AM, Andras Mantia 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 bu

Re: Binary compatiblity for liboxygenstyle.so

On Fri, Feb 24, 2012 at 11:56, 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 th

Review Request: Test also the prefix value

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104068/ --- Review request for kdelibs and David Faure. Description --- We need t

Review Request: Test and add prefix value

--- 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 ha

Review Request: Test Global extended header

--- 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 tes

Review Request: Fix readLongLink method

--- 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 t

Re: Re: bugzilla situation

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 d

Re: bugzilla situation

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

Re: Re: bugzilla situation

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 famili

Re: bugzilla situation

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 : > > > > Bugzilla is not a to-do list, it is for what e

Re: bugzilla situation

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 c

Re: bugzilla situation

On 2012-02-22, David Faure 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 bugzilla? Presu

Re: Re: bugzilla situation

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 : > > > Bugzilla is not a to-do list, it is for what else... a bug (and > > > wishlist) > > > reporting tool for users. > > >

Re: Binary compatiblity for liboxygenstyle.so

On 2012-02-24, Hugo Pereira Da Costa 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 oxygen style? Prob

Re: bugzilla situation

On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > 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 > h

Re: bugzilla situation

Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : 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 state their o

Re: bugzilla situation

On Friday 24 February 2012, Ben Cooksley wrote: > On Fri, Feb 24, 2012 at 11:41 AM, Kevin Ottens 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 of t

Re: bugzilla situation

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 ... > > > 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 $f

Re: Review Request: kdepasswd KCM: add option to remove the user image

--- 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. Cha

Re: bugzilla situation

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

Re: bugzilla situation

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 state set. That would be "assigned", I'

Re: Binary compatiblity for liboxygenstyle.so

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

Re: Binary compatiblity for liboxygenstyle.so

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:

Re: Binary compatiblity for liboxygenstyle.so

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 there is no guarantee for liboxygenstyle.so.4, and I don't plan to guaran

Re: Binary compatiblity for liboxygenstyle.so

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 QT_PLUGIN_PAT

Re: Binary compatiblity for liboxygenstyle.so

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 there is no guarantee for liboxygenstyle.so.4, and I don't plan > >> to guarantee it. > >> It is all internal t

Re: Binary compatiblity for liboxygenstyle.so

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 us

Re: Binary compatiblity for liboxygenstyle.so

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 /opt/qt4/plugins:/opt/kde4/lib64/kde4/

Re: Binary compatiblity for liboxygenstyle.so

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

Re: Binary compatiblity for liboxygenstyle.so

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, ins

Re: Review Request: kdepasswd KCM: add option to remove the user image

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/104054/#review10864 --- kdepasswd/kcm/chfacedlg.cpp

Re: Binary compatiblity for liboxygenstyle.so

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 (liboxygen

Re: Binary compatiblity for liboxygenstyle.so

On Friday, February 24, 2012 11:25:13 AM Hugo Pereira Da Costa wrote: > If I remember correctly, the recipy for getting the right pluggin path > (and thus avoid the crashes -always-), is to edit > $HOME/.config/Trolltech.conf, and remove (or fix) the "libraryPath" > section in [qt]. Hm, I would

Re: Binary compatiblity for liboxygenstyle.so

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 broken

Re: Binary compatiblity for liboxygenstyle.so

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 plugi

Re: Binary compatiblity for liboxygenstyle.so

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

Re: Binary compatiblity for liboxygenstyle.so

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, b

Re: Bugzilla upgrade.

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

Binary compatiblity for liboxygenstyle.so

Hi, is there any BC guarantee for liboxygenstyle.so.4? If not, i think there should be... It is not the first time that you cannot run application installed by your distribution under a self-compiled KDE master, because BIC issues in lliboxygenstyle.so. The apps from there load the oxygen.so p

Re: bugzilla situation

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 com

Re: bugzilla situation

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 supp

Re: Re: Re: bugzilla situation

On Friday 24 February 2012 21:03:42 Ben Cooksley wrote: > On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin 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 bugz

Re: Re: bugzilla situation

On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin 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 oriented vs.