This bug entered so as to *bump* this bug... https://bugs.documentfoundation.org/show_bug.cgi?id=96954 ...and also to request change of severity of said bug from normal to major. Sorry for the duplicate, but it's not clear in this bug tracker UI if notifications sent when a bug is edited are same/different as notifications sent when a new bug is recorded, so to play it safe, I figured I'd enter a new bug, since this is a major bug, and also, the UI doesn't let me edit the severity of the existing bug, but does let me edit the severity of the new bug.
update... even though I don't have permissions to set severity of the bug, bugzilla doesn't seem to be able to figure this out until after offering me the opportunity to set the severity of my new bug, and even then, fails to give me any error to let me know that the severity field didn't take. fun times. oh well I tried
1. Don't add duplicates to "bump" anything. And even more: don't "bump" anything in bug tracker at all - the only thing that is useful to a bug is adding *missing* information - e.g., when you have something substantial to add, or when the bug has a request for additional input. 2. Don't "confirm" your own bugs - only independent confirmation should change a bug from UNCONFIRMED to NEW. As this report was filed with there multiple problems, it is INVALID.
It's useful for a bug to get attention, and it's just not clear to me what attention a 2+ year old bug will get when I add a "it happens to me too" comment to it. It's a major bug, but the Severity of it is set to "normal". I'm just trying to help this bug get the attention it deserves so that users can have this basic functionality of Calc not be broken. Is that too much to ask? The bug is independently confirmed, as you can see in the bug report I linked to. You have set status to resolved, but you have not addressed the issues/concerns/questions raised in this present bug report. I suggest either addressing these concerns or save yourself time and delete my account because I'm not going away.
*** This bug has been marked as a duplicate of bug 96954 ***
(In reply to Elliot from comment #3) > It's useful for a bug to get attention, and it's just not clear to me what > attention a 2+ year old bug will get when I add a "it happens to me too" > comment to it. It's a major bug, but the Severity of it is set to "normal". > I'm just trying to help this bug get the attention it deserves so that users > can have this basic functionality of Calc not be broken. Is that too much > to ask? The bug is independently confirmed, as you can see in the bug > report I linked to. You have set status to resolved, but you have not > addressed the issues/concerns/questions raised in this present bug report. > I suggest either addressing these concerns or save yourself time and delete > my account because I'm not going away. Please don't do things inappropriate for a resource with some specific rules, however you wanted the world to be another place. 1. It is *not* appropriate to write "me-too" comments anywhere in the bug tracker - so your "it's just not clear to me what attention a 2+ year old bug will get when I add a "it happens to me too" comment to it" is wrong from the start, because such a comment should not have appeared there at all, and should be hidden as irrelevant "me too" is appeared. This bug tracker has this policy set by those who created it, so please comply. 2. It is *not* appropriate to clear INVALID resolution from duplicates created to bump things. The entry you have created *is* INVALID, and is marked as such. *This* bug report is RESOLVED INVALID, which doesn't make the original tdf#96954 resolved or something - it will continue to patiently wait for its developer. 3. It is *not* appropriate to try bumping and driving attention to anything here. A bug will only receive attention, when it's triaged appropriately (a task for QA team; and that already happened), and then *an interested developer* comes across it. There's no body out there that checks for issues bumped repeatedly; and moreover, an issue with multiple irrelevant and arrogant comments gets less chances to get attention at all - developers usually treat such issues as difficult to understand (requiring one to read multiple comments with little, often contradicting, information, instead of small number of concentrated useful information). The only useful thing an interesting party can do is to *help*, not to bump: one might try to find a developer (find a developer friend; start a crowdfunding campaign; become a developer oneself); or try to add something substantial (e.g., narrow down a problem: find additional constraints - OS or LO versions; relevant settings; whatever might be missing but relevant to the problem). All other things in bug tracker make its issues filled with noise, and make it useless. It doesn't matter if your pet bug is 3 or 30 years old - doing such things is harmful. Thanks for understanding.
And it is *NOT* a duplicate. A duplicate is a bug that is filed by someone unaware of the original bug; thus it adds to that bug's dupe count. Filing a bug knowing that it's a dupe is INVALID - artificially trying to affect stats here.