Version: unspecified OS: Linux Since kbluetooth is unmaintained, nobody is going to fix bugs in it. Please use Bluedevil instead: http://community.kde.org/Solid/Projects/BlueDevil Please help us warn the Linux distribution (and other OS) packagers to remove kbluetooth from their repositories and use Bluedevil instead. Reproducible: Always Steps to Reproduce: Just install kbluetooth :-) Actual Results: Anything can happen: crashes, features not working, natural disasters, sun flares, even time travels :-) Expected Results: It should work wonderfully, but doesn't. Again: uninstall kbluetooth and install Bluedevil instead.
*** Bug 270681 has been marked as a duplicate of this bug. ***
*** Bug 266786 has been marked as a duplicate of this bug. ***
*** Bug 263056 has been marked as a duplicate of this bug. ***
*** Bug 262706 has been marked as a duplicate of this bug. ***
*** Bug 259698 has been marked as a duplicate of this bug. ***
*** Bug 258287 has been marked as a duplicate of this bug. ***
*** Bug 255555 has been marked as a duplicate of this bug. ***
*** Bug 254660 has been marked as a duplicate of this bug. ***
*** Bug 245685 has been marked as a duplicate of this bug. ***
*** Bug 245160 has been marked as a duplicate of this bug. ***
*** Bug 244994 has been marked as a duplicate of this bug. ***
*** Bug 243579 has been marked as a duplicate of this bug. ***
*** Bug 238610 has been marked as a duplicate of this bug. ***
*** Bug 237735 has been marked as a duplicate of this bug. ***
*** Bug 237071 has been marked as a duplicate of this bug. ***
*** Bug 235087 has been marked as a duplicate of this bug. ***
*** Bug 234202 has been marked as a duplicate of this bug. ***
*** Bug 231470 has been marked as a duplicate of this bug. ***
*** Bug 229922 has been marked as a duplicate of this bug. ***
*** Bug 229911 has been marked as a duplicate of this bug. ***
*** Bug 229076 has been marked as a duplicate of this bug. ***
*** Bug 228350 has been marked as a duplicate of this bug. ***
*** Bug 228293 has been marked as a duplicate of this bug. ***
*** Bug 228095 has been marked as a duplicate of this bug. ***
*** Bug 226861 has been marked as a duplicate of this bug. ***
*** Bug 226132 has been marked as a duplicate of this bug. ***
*** Bug 220207 has been marked as a duplicate of this bug. ***
*** Bug 215149 has been marked as a duplicate of this bug. ***
*** Bug 214834 has been marked as a duplicate of this bug. ***
*** Bug 192090 has been marked as a duplicate of this bug. ***
*** Bug 151906 has been marked as a duplicate of this bug. ***
Lamarque, Bugzilla has an UNMAINTAINED resolution. Please use that instead (or change the product to BlueDevil) of marking bugs as a dupe of this. Thanks.
Since Bluedevil still does no implement kbluelock's features you can vote for the feature request in http://bugs.kde.org/266829 or keep using kbluelock.
Er, it seems that would be product Solid, component Bluetooth.
Yes, but some of the bugs that you are marking as dupes are feature requests. Many of them are still valid for BlueDevil.
I know, but it is time consuming and very boring having to write the same text explaning kbluetooth is unmaintained and to use Bluedevil instead. I also usually have to search the url for the Bluedevil page to guide the users where to find Bluedevil information. It is easier to just mark the bugs as duplicates of this one and since this bug has a major severity it will appear at the top of the list when someone tries to enter a new bug for bluetooth. Hopefully that person will reach here first before they enter a new bug that eventually someone will have to mark as umaintained. I know that because for several weeks I am doing the marking as unmaintained solution. It was not working, so I think this is one works better.
(In reply to comment #35) > Yes, but some of the bugs that you are marking as dupes are feature requests. > Many of them are still valid for BlueDevil. Ok, sorry for that. I tried to mark only bugs that Bluedevil does not solve, but some of them I cannot test myself, so it is better the user test Bluedevil and see if it solves the problem.
> I know, but it is time consuming and very boring having to write the same text > explaning kbluetooth is unmaintained and to use Bluedevil instead. So paste with your middle mouse button, the rest of the procedure is even _easier_ than marking as dupe as you don't have to enter the bug number. By marking as dupe you are causing these problems: 1) The bug is marked with an incorrect resolution, so it may not be implemented even if it is still relevant. 2) All subscribers to all the bugs are getting their mailboxes flooded with your dupes. I've already received over twenty mails: dupe, dupe, dupe 3) All subscribers to all the bugs are now getting spammed with this conversation which is irrelevant to their issue. 4) ??? 5) profit! Please use BKO properly. Thanks.
*** Bug 211420 has been marked as a duplicate of this bug. ***
*** Bug 210527 has been marked as a duplicate of this bug. ***
I've a feeling that you're trying to do good, but that same feeling tells that you're not.
Em Monday 11 April 2011, Juha Tuomala escreveu: > https://bugs.kde.org/show_bug.cgi?id=270702 > > > > > > --- Comment #41 from Juha Tuomala <tuju iki fi> 2011-04-11 20:58:42 --- > I've a feeling that you're trying to do good, but that same feeling tells > that you're not. Well, the idea was to warn uses not to use kbluetooth and where to find Bluedevil information. I just forgot that for each duplicate I marked there would be a new e-mail for each one on the duplicates. I removed everybody from bug 270702 CC list, so there will be no email spams anymore. Sorry for the inconvenience. The main reason for using a bug entry is to make it visible when someone tries to enter a new bug for kbluetooth. Then the user could see that kbluetooth is unmaintained and does not fill a new bug and search for Bluedevil instead.
On Monday 11 April 2011 22:12:05 Lamarque Vieira Souza wrote: > Em Monday 11 April 2011, Juha Tuomala escreveu: > > https://bugs.kde.org/show_bug.cgi?id=270702 > > --- Comment #41 from Juha Tuomala <tuju iki fi> 2011-04-11 20:58:42 --- > > I've a feeling that you're trying to do good, but that same feeling tells > > that you're not. > > Well, the idea was to warn uses not to use kbluetooth and where to find > Bluedevil information. I just forgot that for each duplicate I marked there > would be a new e-mail for each one on the duplicates. I removed everybody > from bug 270702 CC list, so there will be no email spams anymore. Sorry > for the inconvenience. > > The main reason for using a bug entry is to make it visible when someone > tries to enter a new bug for kbluetooth. Then the user could see that > kbluetooth is unmaintained and does not fill a new bug and search for > Bluedevil instead. I didn't follow what you're trying to do. Experience just says that putting a lot of energy and changes into bugzilla - which is a collection, sort of documentation of bugs - is not a good idea. That's because it's quite unlikely that a) all those changes reflect to changes in sources, so that something would have been fixed. b) not likely that there are so many duplicates. So all that energy is just going to piss off people who reported those bugs, like it did me few years ago and I stopped reporting all together to bugs.kde.org. You're likely to drive someone else away too. Not that it would be completely bad thing, I've spent my time elesewhere, and probably to something more useful.
*** Bug 281152 has been marked as a duplicate of this bug. ***