[opensuse-kde] What went wrong?
Hey everybody! https://bugzilla.novell.com/show_bug.cgi?id=712749 That bug report exists for almost one year and renders amarok useless. The solution to the bug exists almost as long as the bug report itself. I do not want to go into the details of its history but just ask how it could happen that people using official packages did not get a fix yet? Who is responsible? And what has to change in order for this to not happen again? I.e. to take this as an example on how to improve openSUSE's quality – the distro which claims to be the best KDE distro available. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hi Sven,
2012/7/13 Sven Burmeister
Hey everybody!
https://bugzilla.novell.com/show_bug.cgi?id=712749
That bug report exists for almost one year and renders amarok useless. The solution to the bug exists almost as long as the bug report itself.
I do not want to go into the details of its history but just ask how it could happen that people using official packages did not get a fix yet? Who is responsible? And what has to change in order for this to not happen again? I.e. to take this as an example on how to improve openSUSE's quality – the distro which claims to be the best KDE distro available.
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked, also IIRC the bug was fixed twice or three times but kept coming back... so it's not that amarok didn't work for a year -- Christoph fixing this the wrong way: maybe someone could add a strict versioned mysql requirement to amarok -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag, 13. Juli 2012, 22:36:10 schrieb Christoph Obexer:
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked,
Tumbleweed has a more recent version of amarok, KDE etc. than 12.1, does it not?
also IIRC the bug was fixed twice or three times but kept coming back...
so it's not that amarok didn't work for a year
I only stated that the issue is known for a year. Nevertheless the "amarok-breaking" patch was shipped without shipping the amarok fix at the same time. AFAIK amarok is still unfixed if one sticks to only official packages for 12.1. Who is responsible? Or is that the actual problem with openSUSE causing this kind of issue? One should not "make fun" of users that use unofficial repos in case it breaks their system but rely on users having to do exactly that in order to have a working amarok. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday, July 13, 2012 10:36:10 PM Christoph Obexer wrote:
Hi Sven,
2012/7/13 Sven Burmeister
Hey everybody!
https://bugzilla.novell.com/show_bug.cgi?id=712749
That bug report exists for almost one year and renders amarok useless. The solution to the bug exists almost as long as the bug report itself.
I do not want to go into the details of its history but just ask how it could happen that people using official packages did not get a fix yet? Who is responsible? And what has to change in order for this to not happen again? I.e. to take this as an example on how to improve openSUSE's quality – the distro which claims to be the best KDE distro available.
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked, also IIRC the bug was fixed twice or three times but kept coming back...
so it's not that amarok didn't work for a year
-- Christoph
fixing this the wrong way: maybe someone could add a strict versioned mysql requirement to amarok
It was fixed on KDE repositories like KDE App Updates, KDE4.8.x. , etc.. This issue ( Amarok-MySQLe Grep error message on Amarok startup with Audio Collections hidden) seems only to appear on the Standard or Official openSUSE with no additional KDE repositories added. I figure out that's Sven is talking about. Regards, -- Ricardo Chung | Panama Linux & FOSS Ambassador openSUSE Projects -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, 13 Jul 2012 23:49:11 +0200
Sven Burmeister
Who is responsible?
Someone who is: - developer - knows KDE - has time, but - didn't patch official version of Amarok. I'm afraid that above is resolving to "no one".
Or is that the actual problem with openSUSE causing this kind of issue?
To be honest, I don't see actual issue, besides, maybe, for one category of SUSE (openSUSE) users; long time users that consider official update channel the only safe way to solve problems. Although, there is no patch for officially supported Amarok, there are solutions in other repos that offer not only working version of one program, but improved KDE for fraction of developer effort to patch all of that. We live in a different times and patching is not the only right way. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Fredag den 13. juli 2012 20:52:26 Rajko skrev:
Although, there is no patch for officially supported Amarok, there are solutions in other repos that offer not only working version of one program, but improved KDE for fraction of developer effort to patch all of that.
We live in a different times and patching is not the only right way.
Ignoring breakage of main default applications sends a very clear message to users that openSUSE/KDE simply doesn't care. An official patch is the only _right_ way. Unless it's not technically possible/feasible - in which case at least the bugreport should be closed as wontfix. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 14/07/12 07:49, Sven Burmeister wrote:
Am Freitag, 13. Juli 2012, 22:36:10 schrieb Christoph Obexer:
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked, Tumbleweed has a more recent version of amarok, KDE etc. than 12.1, does it not?
also IIRC the bug was fixed twice or three times but kept coming back...
so it's not that amarok didn't work for a year I only stated that the issue is known for a year.
Nevertheless the "amarok-breaking" patch was shipped without shipping the amarok fix at the same time. AFAIK amarok is still unfixed if one sticks to only official packages for 12.1.
Who is responsible? Or is that the actual problem with openSUSE causing this kind of issue?
One should not "make fun" of users that use unofficial repos in case it breaks their system but rely on users having to do exactly that in order to have a working amarok.
Sven
I can understand you questioning as to why a bug which has been reported some 12 months ago is still around. This is a matter of principle about why bugs aren't attended to and remain a bug after a year, and I agree with you. But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine? What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hi Dne So 14. července 2012 18:01:08, Basil Chupin napsal(a):
On 14/07/12 07:49, Sven Burmeister wrote:
Am Freitag, 13. Juli 2012, 22:36:10 schrieb Christoph Obexer:
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked,
Tumbleweed has a more recent version of amarok, KDE etc. than 12.1, does it not?
also IIRC the bug was fixed twice or three times but kept coming back...
so it's not that amarok didn't work for a year
I only stated that the issue is known for a year.
Nevertheless the "amarok-breaking" patch was shipped without shipping the amarok fix at the same time. AFAIK amarok is still unfixed if one sticks to only official packages for 12.1.
Who is responsible? Or is that the actual problem with openSUSE causing this kind of issue?
One should not "make fun" of users that use unofficial repos in case it breaks their system but rely on users having to do exactly that in order to have a working amarok.
Sven
I can understand you questioning as to why a bug which has been reported some 12 months ago is still around. This is a matter of principle about why bugs aren't attended to and remain a bug after a year, and I agree with you.
I don't have problem to use workaround, but it is real shame, that default application stays broken for 12 months when people use default repositories. A lot of people do so and they are not able to use workarounds with modifying repos, locking MySQL and so on.
But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine?
Amarok IMHO is good application, I like it, it does what I want. VLC is good, but as far as I know, it does not work with collections in certain directory as Amarok does. And Xine IMHO is not so good.
What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time.
Well, it is actively developed and it is default KDE application. It has a lot of functions, it works well. There is no reason to change it to let it broken for a year. ;-)
BC
Best regards, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
Am Samstag, 14. Juli 2012, 10:12:04 schrieb Vojtěch Zeisek:
I can understand you questioning as to why a bug which has been reported some 12 months ago is still around. This is a matter of principle about why bugs aren't attended to and remain a bug after a year, and I agree with you.
I don't have problem to use workaround, but it is real shame, that default application stays broken for 12 months when people use default repositories.
Exactly, the question is not bound to amarok or any other particular app. It is about a default application broken for two months for those using the official packages, i.e. long enough (and even with a patch available) in order to use it as an example to find out how this can happen and how to make sure it does not happen again, i.e. answering the simple question: who is responsible? If nobody is responsible this will happen again with the current maintenance model. Not only for issues that break an app completely, as in this case, but also regarding less severe but still important bugfixes not shipped as official update. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 14/07/12 18:12, Vojtěch Zeisek wrote:
Hi
Dne So 14. července 2012 18:01:08, Basil Chupin napsal(a): [.........]
But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine? Amarok IMHO is good application, I like it, it does what I want. VLC is good, but as far as I know, it does not work with collections in certain directory as Amarok does.
I would like to know what you mean by this. What "collections in certain directory" vlc won't work? vlc has yet to fail me in anything I want it to play/view/record.
And Xine IMHO is not so good.
With this I agree. vlc is superior to xine, although I used to use xine as a "backup" to vlc - until I installed the first test version of openSUSE 12.2 after which the wheels fell of xine (and the wheels have yet to be recovered) :-( .
What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time. Well, it is actively developed
Umm, would you like to rephrase this? :-) Applications which are being "actively developed" don't have 12-month old unfixed bugs :-) . BC
and it is default KDE application. It has a lot of functions, it works well. There is no reason to change it to let it broken for a year. ;-)
I think that you do need to rephrase your comments! :-D BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Lørdag den 14. juli 2012 10:28:56 Sven Burmeister skrev:
Exactly, the question is not bound to amarok or any other particular app. It is about a default application broken for two months for those using the official packages, i.e. long enough (and even with a patch available) in order to use it as an example to find out how this can happen and how to make sure it does not happen again, i.e. answering the simple question: who is responsible?
That's easy to answer. The openSUSE KDE team/community is responsible as a whole. And we fail abyssmally. But of course not everyone in the community has the skills required to build a patched amarok and submit it to updates. In my opinion the real question is about priorities - i.e. why are default applications in our official flagship release used by hundreds of thousands of people left to rot, while plenty of attention is given to OBS repos used by a few thousand geeks. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dne So 14. července 2012 19:10:06, Basil Chupin napsal(a):
On 14/07/12 18:12, Vojtěch Zeisek wrote:
Hi
Dne So 14. července 2012 18:01:08, Basil Chupin napsal(a): [.........]
But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine? Amarok IMHO is good application, I like it, it does what I want. VLC is good, but as far as I know, it does not work with collections in certain directory as Amarok does.
I would like to know what you mean by this.
What "collections in certain directory" vlc won't work?
vlc has yet to fail me in anything I want it to play/view/record.
As You know, in Amarok You choose Your music directory and it then shows Your music sorted according to interpret, genre, ... as written in ID3 tags. As far as I know VLC does not do this. It is useful feature. ;-)
And Xine IMHO is not so good.
With this I agree. vlc is superior to xine, although I used to use xine as a "backup" to vlc - until I installed the first test version of openSUSE 12.2 after which the wheels fell of xine (and the wheels have yet to be recovered) :-( .
What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time. Well, it is actively developed
Umm, would you like to rephrase this? :-)
Well, is it bug of Amarok? MySQL? SUSE specific or general problem? Amarok is default KDE application for music playing. As long as it is part of default installation, it has to be kept working. Any statements about "Use XY" are useless - it's like say "Dolphin does not work, use Nautilus!" It is default application and it has to work without any problems for not skilled users. As far as I know, practically no one cares about Kaffeine.
Applications which are being "actively developed" don't have 12-month old unfixed bugs :-) .
How did other distros faced this issue?
BC
and it is default KDE application. It has a lot
of functions, it works well. There is no reason to change it to let it broken for a year. ;-)
I think that you do need to rephrase your comments! :-D
BC
Have a nice day, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-07-14 03:52, Rajko wrote:
Although, there is no patch for officially supported Amarok, there are solutions in other repos that offer not only working version of one program, but improved KDE for fraction of developer effort to patch all of that.
Yes, there are other solutions, yes, but nevertheless amarok should also have gotten a patch via the official update method. To ignore Bugzillas for a year doesn't speak well of openSUSE.
We live in a different times and patching is not the only right way.
But it is a very valid right way. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlABVrMACgkQIvFNjefEBxrioACgyo+SxPXqr7hoI/Rv1RyzCxda aQQAoKYb4xA7Eek6jPjn4DseCl9Lt+xO =cg/3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 13 July 2012 21:36, Christoph Obexer
Hi Sven,
2012/7/13 Sven Burmeister
Hey everybody!
https://bugzilla.novell.com/show_bug.cgi?id=712749
That bug report exists for almost one year and renders amarok useless. The solution to the bug exists almost as long as the bug report itself.
I do not want to go into the details of its history but just ask how it could happen that people using official packages did not get a fix yet? Who is responsible? And what has to change in order for this to not happen again? I.e. to take this as an example on how to improve openSUSE's quality – the distro which claims to be the best KDE distro available.
I did a quick test with a openSuSE 12.1 Tumbleweed VM and a Factory VM and both worked, also IIRC the bug was fixed twice or three times but kept coming back...
so it's not that amarok didn't work for a year
It's still two months. And the question, "What went wrong?" is very valid. (for the fix and workarounds, people please use bugzilla). I didn't know about the problem until now. I'm not KDE maintainer, but I'm interested in KDE and perhaps I could be interested in receiving notifications for bugs assigned to kde-maintainers <at> suse <dor> de. Who is in that list? How could someone be added to it? The more people that knows about KDE problems the better. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 14. Juli 2012, 11:18:18 schrieb Martin Schlander:
Lørdag den 14. juli 2012 10:28:56 Sven Burmeister skrev:
Exactly, the question is not bound to amarok or any other particular app. It is about a default application broken for two months for those using the official packages, i.e. long enough (and even with a patch available) in order to use it as an example to find out how this can happen and how to make sure it does not happen again, i.e. answering the simple question: who is responsible?
That's easy to answer. The openSUSE KDE team/community is responsible as a whole. And we fail abyssmally.
Isn't that the standard "don't blame anyone specific"-answer given for the past few months, maybe years, whenever something went wrong. Isn't that exactly what has led to the current situation? At least I do not see any improvements since that answer is given to any problem named. Also, I do not see that the community failed, quite in contrast.
But of course not everyone in the community has the skills required to build a patched amarok and submit it to updates.
In my opinion the real question is about priorities - i.e. why are default applications in our official flagship release used by hundreds of thousands of people left to rot, while plenty of attention is given to OBS repos used by a few thousand geeks.
I think my perception differs a lot. I do not see any relevant attention given to non-official KDE repos by the KDE devs. KDF is part of the openSUSE development, i.e. any work on it is not wasted by definition. KRxy are just links that need updating from time to time and were broken for a long time which should prove that they get even less attention than e.g. KDF. KUSC is mainly maintained by Raymond. So where exactly do KDE devs waste their time on anything unofficial? I'd rather say there are no people at openSUSE left who are dedicated to KDE by the management, i.e. those that are supposed to be the KDE team get assigned to other things. No team restart will solve that problem – as was shown in the past. I think it contradicts itself if you blame the community if something goes wrong but want to decrease the priority of the platform the community participates most in. In fact, the community repos are better off as the official distro – because of the community, not because of its failure. Yet that work is withhold from the "official" openSUSE users and even marked as wasted – instead of used for all users. So here is my claim. The failure is to hold on to an unrealistic distro maintenance model. Official updates do not work, no time, no money, you name it, they simply don't. The current amarok issue is the best example. The community found the bug a year ago, the community created the patch, the community submitted it to KDF, all unofficial repos are fixed – yet the small step from not only accepting a fix into KDF but also submitting it as an official update was skipped by the KDE devs. Again, it does not matter why or how or whatsoever, it just shows that obs works a lot better, i.e. faster than the official distro because it is community-driven and does not rely on openSUSE dedicating people to KDE. Those on the kde maintainers list could have noticed the bug for a long time before it became relevant for the official distro. And here is my solution. Forget about official updates, they are a waste of time – of which KDE devs seem to have none. Does anyone know of any regressions people would have suffered if everybody was using KRxy? Any of those fixed slower than e.g. the amarok one? On top of that, since oss is always available, reverting from KRxy to oss is always possible in case somebody really finds a significant regression. AFAIK it's even possible to keep several versions of a package in a repo, so reverting would even be possible within KRxy. A few points: Finally establish a formal process for maintainers as promised here: https://bugzilla.novell.com/show_bug.cgi?id=706813#c16 Get rid of STABLE, the fixes are in KRxy anyway. Get rid of KDF, use KUSC for packaging unreleased KDE versions and move them to KRxy as soon as they are released upstream. Use KRxy's packages to create a snapshot for an openSUSE release and enable that KRxy repo as update repo by default. Let those that want non-upstream bugfixes and backports buy a SuSE product. This sums-up to care more about those that participate in openSUSE and KDE, i.e. use obs to package KDE and fix bugs upstream, than those that don't, i.e. contribute nothing but usage. That might sound harsh, but those relying on the official packages are left alone anyway – I guess because of a lack of time on the openSUSE devs' side. If nobody is paid to be responsible for KDE then one should not hold on to a distro model which relies on exactly that. Instead one should start to use the community's and upstream's effort to maintain packages and distribute them to openSUSE users – officially. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 14. Juli 2012, 13:22:21 schrieb Cristian Morales Vega:
I didn't know about the problem until now. I'm not KDE maintainer, but I'm interested in KDE and perhaps I could be interested in receiving notifications for bugs assigned to kde-maintainers <at> suse <dor> de. Who is in that list? How could someone be added to it? The more people that knows about KDE problems the better.
AFAIK this list is still SUSE-internal. For help with bug screening for KDE the suggestion is: You can watch any bugzilla account in Novell bugzilla by adding it to the list in Preferences->Email Preferences, near the bottom of the page. For watching changes in shared bugreports, including all new KDE bugreports, add 'kde- maintainers@suse.de'. (taken from http://en.opensuse.org/openSUSE:Bug_Screening_KDE) However only very few people have done this so far AFAICT. Christian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 14 July 2012 18:22, Christian Trippe
Am Samstag, 14. Juli 2012, 13:22:21 schrieb Cristian Morales Vega:
I didn't know about the problem until now. I'm not KDE maintainer, but I'm interested in KDE and perhaps I could be interested in receiving notifications for bugs assigned to kde-maintainers <at> suse <dor> de. Who is in that list? How could someone be added to it? The more people that knows about KDE problems the better.
AFAIK this list is still SUSE-internal. For help with bug screening for KDE the suggestion is:
You can watch any bugzilla account in Novell bugzilla by adding it to the list in Preferences->Email Preferences, near the bottom of the page. For watching changes in shared bugreports, including all new KDE bugreports, add 'kde- maintainers@suse.de'.
(taken from http://en.opensuse.org/openSUSE:Bug_Screening_KDE)
However only very few people have done this so far AFAICT.
My bad. I just did it. Thanks. IMHO the answer to "what went wrong" is that not enough people knew about the problem. But unless somebody has a plan to foment people watching kde-maintainers I can't think of anything to fix it. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 16. Juli 2012, 09:48:51 schrieb Cristian Morales Vega:
IMHO the answer to "what went wrong" is that not enough people knew about the problem. But unless somebody has a plan to foment people watching kde-maintainers I can't think of anything to fix it.
I don't buy that since openSUSE KDE devs, i.e. people that should be on kde- maintainers, accepted the fix into KDF, updated the links to KR48 and so on and hence knew about it. Some of them even commented on the report. Lack of time? There was no need to find out what the solution to the bug is, no need to code – just the one step of creating a maintenance request from the available submit request. So watching is not the problem. Lack of self-motivation in combination with a lack of time to work on KDE would be my guess – and explain the current situation, including this incidence. Since that situation won't change – unless management dedicates somebody to have a KDE-only job – one should simply acknowledge the current situation and adapt the maintenance model accordingly, i.e. no backporting, just packaging in obs and distributing those packages as official. That way the community contribution to obs and upstream efforts to fix bugs are send directly to openSUSE users without any need to backport/patch/create official patches and submitting them to the maintenance team etc. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dnia sobota, 14 lipca 2012 18:01:08 Basil Chupin pisze:
But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine?
Neither supports KIO, and xine UI is completely bro-ken.
What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time.
Because, with all due respect, the distro is not only for you. Cheers, Chris -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday, July 14, 2012 06:01:08 PM Basil Chupin wrote:
On 14/07/12 07:49, Sven Burmeister wrote:
Am Freitag, 13. Juli 2012, 22:36:10 schrieb Christoph Obexer:
[Snip]
I can understand you questioning as to why a bug which has been reported some 12 months ago is still around. This is a matter of principle about why bugs aren't attended to and remain a bug after a year, and I agree with you.
I would like to know how to fix it on the main repo. So I would contribute to make it available. A few hands on is better approach. Afer all this is a community development, it belongs to all of us. And fixing anything is time consuming for any developer too (paid or not) BTW, I am not developer but I make efforts to recruit it. So, more contributors on these spots will speed up the patches and fixes.
But, to be honest, why would anyone bother with amarok when there are more superior applications available, for example vlc or xine?
Because Amarok works differently from VLC or Xine. And the last one is now broken. In matter of fact, it's not possible to make a detailed comparison between VLC and Amarok to put one of them on the side. Amarok is a specialized audio player with great features added ( not included on VLC ). If you prefer VLC for audio you could miss plenty info only available on Amarok. Do not misunderstand me. I love to use VLC and Banshee too. You should recognize what application serve you best for the purposes needed.
What *I* would be questioning is why amarok automatically installed? And why also automatically install kaffeine which does the same thing as amarok, as far as I am concerned? Waste of space and time.
Why not? After all, you could install what you want if you prefer another one (e.g. Clementine, MPlayer, Rythmbox, Banshee,..). Some basic applications to start your fun are needed. As far as I have installed KDE those programs come to show the KDE easier recognized apps (flagship) for multmedia. Time to time some bugs come to alive and we are able to report or fix them (it's not openSUSE the only one with these issues). If the community users prefer to show other applications instead should vote on openFATE.
BC
Regards, -- Ricardo Chung | Panama Linux & FOSS Ambassador openSUSE Projects -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (11)
-
Basil Chupin -
Carlos E. R. -
Christian Trippe -
Christoph Obexer -
Cristian Morales Vega -
Křištof Želechovski -
Martin Schlander -
Rajko -
Ricardo Chung -
Sven Burmeister -
Vojtěch Zeisek