Husse wrote:We now have bugtracking on Launchpad
But if you do not want to register there please report here and emorrp1 will take care of the rest
- 14/12/09 bug reported in launchpad
- 30/01/10 Bug still not even acknowledged
ranyardm wrote:This is getting ridiculous. What is the point of reporting bugs if they don't even get acknowledged.
ranyardm wrote:It takes probably a minute to follow the testcase in a well-formulated bugreport and acknowledge that the bug is reproducible.
ranyardm wrote:If the person getting the bug report emails from launchpad isn't willing to do that in over a month from report, I posit that the job should be given to somebody or a group of people who will.
emorrp1 wrote:Well, the only bugs that were reported on 14th Dec do not match your description - #496730 was fixed by Clem the following day and #496353 was a dupe that was commented on and bypassed the very same day. Please provide a link.
emorrp1 wrote:Firstly I agree, you should probably know that your chances of getting a new bug report even noticed in Ubuntu is slim (just see the Mint ones I've acknowledged and sent upstream). My main aim when I volunteered to be bug supervisor was to have some sort of response as quickly as possible, to prevent the frustration of uncertainty you're feeling. This worked well over the summer when I could spend time chasing down a bug, but wasn't so effective once I started back at Uni and became even worse with the explosion of bug reports for Helena, I can't keep up.
emorrp1 wrote:Unfortunately, it takes a lot longer than that on average. Mainly because there are very few "well-formulated" bug reports (just scroll through the list on launchpad) and they often involve random hardware or software that I don't have, but also because there's always a lot of background reading to be done. Not to let this dis-hearten me, I set up numerous virtual machines - one for each edition and version of Mint and the corresponding upstream Ubuntu release. I also formulated a number of standard responses and often marked a bug as "Incomplete" rather than "invalid" or "won't fix" to give the bug reporter a chance to respond.
A good example is bug #499475 (https://bugs.launchpad.net/linuxmint/+bug/499475), which I mistook for your bug before noticing the exact date and so went through with it, total time: >30mins First I had to realise the reporter meant "tab" rather than "tag", I then checked *my* Mouse prefs (Gloria) had the touchpad tab. Next I loaded up my Helena VM - sure enough there was no Touchpad tab. However I realised it could be a fancy app that only shows that tab if a touchpad is detected, so I loaded up my Gloria VM, to show yep, no Touchpad tab (whereas I know it's capable of it since it works on my native Gloria system). I then searched launchpad for similar issues: Possibility number 1 - touchpad not correctly detected [hardware]. I could have stopped there (mark "incomplete") and just asked them to run through a number of touchpad troubleshooting routines and probably never heard from the reporter again (approx time taken 10-15mins).
At this point I was going to try installing Helena in my native test partition, but discovered my optical drive isn't working - I'm not counting this 10mins. I was working on the assumption that this was your bug report (ignoring your "well-formulated" comment anyway) so I assumed (for the time being) that Mint was correctly identifying the touchpad. I therefore turned to the fount of all knowledge: http://www.lmgtfy.com/?q=karmic+touchpad+preferences and discovered an upstream change for Karmic that meant you couldn't disable the touchpad fully. This was also echoed in bug #404638 and the other google links, so I loaded up my VMs again to find where this option would be (general/accessibility), but obviously it's still not showing unless a touchpad is detected: Possibility number 2 - upstream changes. At this point (just under 15mins) I gave up and edited the bug report with my findings, was generous in leaving it "Incomplete" rather than "Won't Fix" dues the ambiguity of the exact upstream changes, but writing up the bug report usually takes about 5mins to collate all the info.
Total time investigating this one bug: >30mins
emorrp1 wrote:Again I agree, I have in fact said as such to the Mint Team. The problem is really one of manpower, there's only so much any one of us can do with outside commitments - If you're willing to volunteer for the job, I'll recommend you and give you all the help I can in starting out. Incidentally, I elected to stop receiving e-mails from launchpad almost immediately upon become the bug supervisor because there're so many and whenever I do have time, I just logon to launchpad and see what's new. Also, just a reminder that Ubuntu bug reports often remain untouched for months, sometimes years.
emorrp1 wrote:I don't mean to be harsh towards your comments or anything, but I do want to emphasise that I still care about the Mint project, I just can't donate as much time during term.
emorrp1 wrote:Total time taken to respond to your comments about bug supervising (inc. marking a couple of bugs duplicate, the touchpad bug [and finding it - no date filter on lp], discovering my optical drive doesn't work, writing this post [about an hour] etc.): 2hrs
Watching Husse's never-ending efforts to improve the organisation and effectiveness of the Team: priceless
ranyardm wrote:There are multiple launchpads for linux mint - one for the distro, which I'm assuming is the one you're checking, then one for mintupdate, one for mintmenu, one for mintupload... I picked the most appropriate one for my bug - mintmenu. In my opinion, these extra launchpads need closing down.
ranyardm wrote:Thanks for your time on this, but I would be tempted to separate those two things out - the point of my post is not to get my bug looked at, but to get the bug-reporting structure of Linux Mint looked at, which would hopefully have the knock-on effect of the bug in question looked at.
Users browsing this forum: Bing [Bot], Google [Bot] and 26 guests