Re: issue submitting crashes
On Fri, Oct 19, 2012 at 10:48:14AM +0200, Marius Kotsbak wrote: On 18. okt. 2012 21:33, Brian Murray wrote: On Thu, Oct 18, 2012 at 12:24:23PM -0700, Jeremiah Njoroge wrote: Is there an issue in yesterday and today's daily Quantal builds with submitting crash reports? What I am observing is as follows: An app/process crashes A pop up shows asking if I want to report a problem After clicking on OK, I get the pop up to Send an error report to help fix the issue after clicking on continue, nothing happens after. I also see this by trying to submit the crash report using the ubuntu-bug command Crash reports regarding stable releases, which Ubuntu 12.10, is go to errors.ubuntu.com and not the Ubuntu bug tracker in Launchpad. You can verify that the crash was upload by looking for a .uploaded file corresponding to the .crash file in /var/crash/ for the particular application or service that crashed. Please clarify. Do you say that there are not anymore reported bug reports for crashes? The idea is that bug reports have already been created (during testing of the development release) for the majority of crashes that people will encounter. Additionally, submitting bug reports uses valuable resources on the local system and on Launchpad. However, the crashes are still submitted to errors.ubuntu.com and there you can see relationships between crashes and bug reports. It that case, the crash dialog should be modified to give the user an indication that the crash report has been uploaded. Like it is now for me, it just disappears and I think itself has crashed... Is there an existing bug report about this? I believe the thought is the process should be as non-disruptive as possible and a second dialog saying 'your crash was successfully sent' is disruptive. If you wanted to submit a bug about this apport is the correct package. -- Brian Murray Ubuntu Bug Master -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: The crash belongs to a package that is not installed. ???
On Wed, Sep 26, 2012 at 11:02:35AM +0100, Brendan Donegan wrote: On 25/09/12 15:54, Brian Murray wrote: On Tue, Sep 25, 2012 at 09:44:25AM +0200, Gabor Toth wrote: Just a question here. From time to time I get a system crash window popping up and saying that there was a crash. I click on send the report - of course - and then it comes up with another window saying The crash belongs to a package that is not installed. I do not get it. How can a package crash that is not even installed? Can anyone light my way in this? Knowing what the contents of /var/crash is would be helpful in determining which application crashed. For example: /var/crash/_usr_share_apport_apportcheckresume.1000.crash indicates the application /usr/share/apport/apportcheckresume crashed and I know that is a part of apport. (You could check via dpkg -S /usr/share/apport/apportcheckresume.) Then I can use apt-cache policy to see if apport is installed: apport: Installed: 2.5.2-0ubuntu4 Candidate: 2.5.2-0ubuntu4 -- Brian Murray Ubuntu Bug Master Something similar happens when the version of the package that crashed does not match the one in the archive. It is intended to stop bugs from being reported on old package versions, but the text is deeply confusing. I wonder is it that? Are you referring to this Unreportable Reason? http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/quantal/apport/quantal/view/head:/apport/ui.py#L122 That doesn't seem terribly confusing to me. If it isn't that particular reason search for other Unreportable Reason instances and please let me know which one is confusing. Thanks! -- Brian Murray Ubuntu Bug Master -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: The crash belongs to a package that is not installed. ???
On Tue, Sep 25, 2012 at 09:44:25AM +0200, Gabor Toth wrote: Just a question here. From time to time I get a system crash window popping up and saying that there was a crash. I click on send the report - of course - and then it comes up with another window saying The crash belongs to a package that is not installed. I do not get it. How can a package crash that is not even installed? Can anyone light my way in this? Knowing what the contents of /var/crash is would be helpful in determining which application crashed. For example: /var/crash/_usr_share_apport_apportcheckresume.1000.crash indicates the application /usr/share/apport/apportcheckresume crashed and I know that is a part of apport. (You could check via dpkg -S /usr/share/apport/apportcheckresume.) Then I can use apt-cache policy to see if apport is installed: apport: Installed: 2.5.2-0ubuntu4 Candidate: 2.5.2-0ubuntu4 -- Brian Murray Ubuntu Bug Master -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: problems with ubuntu-bug
On Wed, Aug 22, 2012 at 05:32:33PM +0200, Carla Sella wrote: On Wed, Aug 22, 2012 at 5:31 PM, Carla Sella carla.se...@gmail.com wrote: On Wed, Aug 22, 2012 at 5:26 PM, Brian Murray br...@ubuntu.com wrote: On Wed, Aug 22, 2012 at 02:58:47PM +0200, Fabio Marconi wrote: On Wed, 2012-08-22 at 14:53 +0200, Carla Sella wrote: Hello, I am testing Unity GSetting Migration in Unity for Unity Compiz Testing and I have reported a bug using ubuntu-bug unity. After having filled in the bug report I clicked on submit bug, but I got a message saying that there was one error, I tried a bit everything but couldn't get the bug submitted. So I opened a bug using launchpad (bug #1040049), now I was trying to submit some data using ubuntu-bug -u 1040049 to help with more info, but when I launch this command in the terminal window I get this error: ERROR: The launchpadlib Python module is not installed. This functionality is not available. I installed python-launchpadlib and also python-launchpadlib-toolkit, but when I use ubuntu-bug -u bug-number I keep on getting the same error. I am doing this on a new install of Quantal Alpha3 on a partition on my PC with all updates applied and after having added the ppa:timo-jyrinki/prerelease for Unity testing. I used to use ubuntu-bug -u without problems. What can I do to submit more information for the bug I just opened ? Hallo Carla dunno if the one i've encountered, but b efore to click on submit, click extra option and in the tag box search and sustitute with - the tilde (~) What tag had a ~ in it? -- Brian Murray -- rc-6.2.0-0ubuntu3-test4 was c-6.2.0-0ubuntu3~test4 Sorry rc-6.2.0-0ubuntu3-test5 was c-6.2.0-0ubuntu3~test5 This is a bug in the apport package hook for unity or maybe even in apport itself. A ~ is not allowed in tags in Launchpad and either the package hook or apport should replace a ~ with - as you did. -- Brian Murray -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: problems with ubuntu-bug
On Wed, Aug 22, 2012 at 06:33:57PM +0200, Carla Sella wrote: Brian Murray br...@ubuntu.com wrote: On Wed, Aug 22, 2012 at 05:32:33PM +0200, Carla Sella wrote: On Wed, Aug 22, 2012 at 5:31 PM, Carla Sella carla.se...@gmail.com wrote: On Wed, Aug 22, 2012 at 5:26 PM, Brian Murray br...@ubuntu.com wrote: On Wed, Aug 22, 2012 at 02:58:47PM +0200, Fabio Marconi wrote: On Wed, 2012-08-22 at 14:53 +0200, Carla Sella wrote: Hello, I am testing Unity GSetting Migration in Unity for Unity Compiz Testing and I have reported a bug using ubuntu-bug unity. After having filled in the bug report I clicked on submit bug, but I got a message saying that there was one error, I tried a bit everything but couldn't get the bug submitted. So I opened a bug using launchpad (bug #1040049), now I was trying to submit some data using ubuntu-bug -u 1040049 to help with more info, but when I launch this command in the terminal window I get this error: ERROR: The launchpadlib Python module is not installed. This functionality is not available. I installed python-launchpadlib and also python-launchpadlib-toolkit, but when I use ubuntu-bug -u bug-number I keep on getting the same error. I am doing this on a new install of Quantal Alpha3 on a partition on my PC with all updates applied and after having added the ppa:timo-jyrinki/prerelease for Unity testing. I used to use ubuntu-bug -u without problems. What can I do to submit more information for the bug I just opened ? Hallo Carla dunno if the one i've encountered, but b efore to click on submit, click extra option and in the tag box search and sustitute with - the tilde (~) What tag had a ~ in it? -- Brian Murray -- rc-6.2.0-0ubuntu3-test4 was c-6.2.0-0ubuntu3~test4 Sorry rc-6.2.0-0ubuntu3-test5 was c-6.2.0-0ubuntu3~test5 This is a bug in the apport package hook for unity or maybe even in apport itself. A ~ is not allowed in tags in Launchpad and either the package hook or apport should replace a ~ with - as you did. -- Brian Murray Do I have to report a bug or will you look into the matter? https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1040189 It'd help to have a complete list of tags that Launchpad doesn't allow. I did not find one quickly. -- Brian Murray -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Partial upgrade Can't guess meta-package
Actually update-manager is a better package here as Russell indicated that he had already installed the system and the problems were trying to upgrade after installing the system. Additionally, the update-manager apport package hook will give us better log files to debug this issue. On Tue, Apr 17, 2012 at 06:23:32PM -0400, Nicholas Skaggs wrote: Russell, I would report this via ubuntu-bug ubiquity and note you encountered the bug in the iso tracker. Thanks for helping test! Nicholas On 04/17/2012 06:12 PM, Russell Hart wrote: Hi, I doing the 'Install (ubiquity) in Ubuntu DVD amd64 for Precise Daily' test case in a Virtual Machine with Oracle VirtualBox. It installed OK and rebooted as expected. After running sudo apt-get update and opening Update Manager it asked, 'Not all updates can be installed' 'Run a partial upgrade, to install as many updates as possible. ' I tried the Partial Upgrade but got an error message 'Can't guess meta-package' 'Your system does not contain a ubuntu-desktop, kubuntu-desktop, xubuntu-desktop or edubuntu package and it was not possible to detect which version of Ubuntu you are running. Please install one of the packages above first using synaptic or apt-get before processing. ' ubuntu-desktop is installed and the newest version (sudo apt-get install ubuntu-desktop). Thanks, Russell Hart -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa -- Brian Murray Ubuntu Bug Master -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Should the installer be showing 12.04 yet?
On Thu, Feb 02, 2012 at 12:45:33AM +1030, Andrew McDonnell wrote: Hi, all I was testing the Xubuntu WUBI install and noticed that in the second phase of the install the screenshots in the installer wizard had Xubuntu 11.10 Is this a bug or does that not get changed until the last minute? https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/899503 It has been reported as a bug. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: QA tasks available
On Mon, Dec 05, 2011 at 04:24:19PM +, Gema Gomez wrote: Dear QA Team, as promised, here it is a list of tasks that need to be done and we are in the process of doing that you could own if you have the time: - ISO testing tasks (https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing): 1) Compile a list of applications that are installed by default by the ISO installers (one for Desktop, one for Server) and propose two or three basic test cases that could be run post install giving us basic confidence that the ISO is good for further testing (i.e. compile a list of post-install smoke tests that we could run with Jenkins). - This task is not about generating code, but about thinking of what packages of the ones installed are important and worth testing in a daily test suite. We could split it in different tasks for different people if we generate first a list of apps that we can use for the generation of test cases. 2) We need to fix the existing test cases in the tracker and convert them to a better, more understandable format. Basically we need to convert them to unambiguous and meaningful test cases. Some of them are redundant, some of them are too long to be just one test case, some others do not make sense anymore. This is a tidy up task that needs to be done. - Metrics (https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-metrics): 3) I have some tasks here that could use some help. We need to look at the codebase of Ubuntu main and see how to instrument the code so that we can start generating code coverage metrics. This is about compiling the Ubuntu code with gcov and generating binaries that can be used (still to be seen how to install them) for this end. - This task requires code in-depth knowledge and familiarity on how things are built and can be changed to build in a different way. We should decide where to start instrumenting and why. 4) Look into how to do test escape analysis with launchpad. TEA is an analysis that will tell us, after Precise, if we missed some problems that were found by someone after we did our testing and that should help us understand whether we should be adding new test cases in those missed areas or not. 5) Gather test cases from defects. This is about making a list of defects that have been fixed for Oneiric and that have a set of steps to reproduce the problem that needs to be gathered and written into a proper test case. Here are some Launchpad searches that should help: Bugs with an oneiric task that are Fix Released and have been tagged 'testcase'. https://bugs.launchpad.net/ubuntu/oneiric/+bugs?field.searchtext=orderby=-importancefield.status%3Alist=FIXRELEASEDassignee_option=anyfield.assignee=field.bug_reporter=field.bug_supervisor=field.bug_commenter=field.subscriber=field.component-empty-marker=1field.tag=testcasefield.tags_combinator=ANYfield.status_upstream-empty-marker=1field.has_cve.used=field.omit_dupes.used=field.omit_dupes=onfield.affects_me.used=field.has_no_package.used=field.has_patch.used=field.has_branches.used=field.has_branches=onfield.has_no_branches.used=field.has_no_branches=onfield.has_blueprints.used=field.has_blueprints=onfield.has_no_blueprints.used=field.has_no_blueprints=onsearch=Search Bugs about Ubuntu that are Fix Released and tagged 'testcase' and 'oneiric'. This one is timing out and causing an OOPs although it would be easy to get a list of the same bugs using the Launchpad API. https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=orderby=-importancefield.status%3Alist=FIXRELEASEDassignee_option=anyfield.assignee=field.bug_reporter=field.bug_supervisor=field.bug_commenter=field.subscriber=field.component-empty-marker=1field.tag=oneiric+testcasefield.tags_combinator=ALLfield.status_upstream-empty-marker=1field.has_cve.used=field.omit_dupes.used=field.omit_dupes=onfield.affects_me.used=field.has_no_package.used=field.has_patch.used=field.has_branches.used=field.has_branches=onfield.has_no_branches.used=field.has_no_branches=onfield.has_blueprints.used=field.has_blueprints=onfield.has_no_blueprints.used=field.has_no_blueprints=onsearch=Search My bug bot automatically tags bugs with the words TEST CASE in the description 'testcase' and has been doing so for some time now. -- Brian Murray -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Workaround field for bugs
On Tue, Jun 28, 2011 at 05:47:33PM +0200, Paolo Sammicheli wrote: Hi everybody, Unfortunately I missed the last IRC Meeting but I've seen on the log that Brian Murray informed you about his research (thanks again Brian!). For those who don't know what I'm talking about, this is the relevant links: https://wiki.ubuntu.com/BugsKnownWorkAround https://bugs.launchpad.net/launchpad/+bug/54652 So, at moment around 10.000 bugs have information about workaround but the point is that the information is not properly exposed. One example is the bug #753971 ( http://pad.lv/753971 ) Workarounds for this bug would be: - Log in on Classic Mode since only Unity is affected - Downgrade unity to 3.8.10-0ubuntu2 sudo apt-get install unity=3.8.10-0ubuntu2 unity-common=3.8.10-0ubuntu2 But the information is spread on the comments, although this is a well known bug in Natty in which many well known developers have ran into (and as far I understand this case isn't included in Brian research because there's no workaround keyword on the description). So, my opinion is still that we need to improve the workaround exposition improving launchpad itself, but I don't know where to move the next step. Suggestions? I'd suggest creating an official bug tag for workaround and using the tag to search for bug reports with workarounds as it is not easy to search bug descriptions. We could then take the list of bugs with variations of the word 'workaround' in the bug description and tag them with the workaround tag. Some of this could be done automatically but the majority would need to be done manually. Then going forward we could update the description with the workaround and also tag the bug reports. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Mago Tests
I recently ran across http://launchpad.net/bugs/761094 (download updates while installing Ubuntu does nothing) and was wondering if a test for it would be appropriate for Mago. If not where can we test this to ensure that it doesn't happen again? Actually, I think there is probably a fair bit of stuff that could / should be tested post-install. Thanks, -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Laptop testing: Backlight test needed
On Sun, Mar 27, 2011 at 03:48:22PM -0700, Joseph Areeda wrote: James, How did you modify grub for backlighting? Is there a thread or a wiki page on how to do it? I never did get it to work on my Thinkpad 510 with Lucid or Maverick. Until I get better dependability on my desktop, I can't risk my laptop. This Kernel Team wiki page contains some information on debugging issues with the backlight on laptops. https://wiki.ubuntu.com/Kernel/Debugging/Backlight -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: I'd like to introduce myself and ask newbie questions
On Fri, Mar 11, 2011 at 10:26:26AM -0800, Joseph Areeda wrote: On 03/11/2011 09:58 AM, Eliseo Duarte wrote: this is not a meet and greet! OK. But I've been reading this list for months and you are the first one to say that. I apologize, I thought I had enough issues with the Alpha release to at least start a discussion. You did and thank you for bringing them up. Could you direct me to some reading on how best to use this list? I'm trying to get started in the QA process and my reading of the Wiki and everything else I've found on the website leaves me with questions. This is a perfectly acceptable place to ask questions regarding the Quality Assurance process. For real time answers you might also try #ubuntu-quality on Freenode's IRC servers. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: I'd like to introduce myself and ask newbie questions
On Thu, Mar 10, 2011 at 10:01:03AM -0800, Joseph Areeda wrote: Greetings all, I am retired from a career in software development and medical research. I've been using Unix since 1983 (at least that's the first comment in my .cshrc file) and Ubuntu for about a year. I like Ubuntu and would like to give back a little by participating in QA and perhaps a bit of coding. I've been reading Wiki's and this mailing list, signed up for the mentor thing, but that seems slow moving, so let's try this list. I need some help or focus to get started. I've read that testing on a virtual machine is not as good as a hardware install, but it seems to a good place to start with an alpha release, especially one like Natty which has extensive UI changes. One can do lots of testing in a virtual machine and we welcome any help! I thought I'd start with VirtualBox and load my favorite packages and get the feel of it before I loaded it onto hardware but I can't seem to get it to load. I'm running 10.04 LTS (Linux jsa 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11 20:52:10 UTC 2011 x86_64 GNU/Linux) on a laptop (I5 4Gb) and a desktop (AMD Phenom X6 16GB). I downloaded the latest Vbox from Oracle (4.04). I use zsync to update a few times over the last week, they all behave the same. The install iso boots but never makes it past the first screen Preparing to Install Ubuntu, attached is the VM log, if anyone can see what I'm missing I'd appreciate it. As mentioned in another post you've certainly hit a bug here. I can run Meerkat (Linux meerkat 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:29 UTC 2011 i686 GNU/Linux) in a VM with the same settings. I've tried a bunch of different ones and both 32 and 64 bit versions. You could test the distribution upgrade process and then be running the development release that way. You'd need to use 'update-manager -d' to get update manager to check for the development release though. In case you didn't run across it here is some documentation regarding testing - https://wiki.ubuntu.com/Testing. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: I'd like to introduce myself and ask newbie questions
Identifying the bug reports that the original post was experiencing was a huge help and I've escalated one of them. So thank you! On Fri, Mar 11, 2011 at 07:58:05PM +0100, Mads ¤ wrote: Hi. I am very sorry, no rudeness is intended. I have not been participating long myself and is very unsure about how to do things right. I have not been able to install Natty because of these two bugs and just wanted to help. Mads On 11 March 2011 18:58, Eliseo Duarte duarteeli...@ymail.com wrote: this is not a meet and greet! -Original Message- Date: Friday, March 11, 2011 8:58:12 am To: ubuntu-qa@lists.ubuntu.com From: Mads ¤ motepr...@gmail.com Subject: Re: I'd like to introduce myself and ask newbie questions The install iso boots but never makes it past the first screen Preparing to Install Ubuntu, attached is the VM log, if anyone can see what I'm missing I'd appreciate it. Your problem is real and there is a reported bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/723990 Booting from a USB stick on a real machine (Phenom II x6) was worse. Problem mounting Sr0 after I tried to install. CD worked a bit better, it at least gave me an error message: ubi-partman failed with exit code 141. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing... I could try it with the live CD on this system. I may This one to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/730209 -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Writing a mago test
I was looking at http://launchpad.net/bugs/675063 today and was wondering if this was something that we could test with mago. I wasn't sure about how to test the contents of a specific cell in gnome-sudoku. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Packages to investigate
On Tue, Nov 30, 2010 at 11:51:19AM +0100, Jean-Baptiste Lallement wrote: On 11/22/2010 10:22 PM, Brian Murray wrote: As we all know there are a lot of packages and bugs to keep track of in Ubuntu. One idea that occurred to me recently, to help identify packages in need of triage, was to calculate an average bug heat for the particular package. I've made a first pass at this using all the packages in the ubuntu-desktop package set. Here are the top 10 packages: usb-modeswitch-data - median: 764, mode: 1448 language-pack-gnome-fa-base - median: 408, mode: 408 language-pack-gnome-pt - median: 318, mode: 318 couchdb-glib - median: 210, mode: 210 netbook-meta - median: 145, mode: 408 pyopenssl - median: 136, mode: 259 shotwell - median: 124, mode: 6 appmenu-gtk - median: 122, mode: 408 gnome-python-extras - median: 114, mode: 3 telepathy-gabble - median: 104, mode: 49 As I ran this last Friday there might be some variance in the numbers. I'm curious whether or not you think the bug reports for these packages really need reviewing. Thanks, Thanks Brian. This is really interesting. If we apply this calculation to the packages installed by default in Natty, the top 10 looks like: shotwell - median: 189 empathy - median: 91 gcalctool - median: 86 gbrainy - median: 86 gwibber - median: 81 simple-scan - median: 76 software-center - median: 68 pitivi - median: 68 transmission - median: 60 gnome-bluetooth - median: 59 Compared to the list based on the number of bugs: evolution firefox gdmsetup nautilus nm-connection-editor ooffice software-center totem update-manager So I can not say that this is the list that I had in mind, but the result is expected. When we build the list based on volume of bugs, we get the most used applications. But when we use the bug heat we get the applications with fewer bugs but which are in need of triage (I'm not saying that the applications with a large number of bugs don't need triage) The list needs a closer look though. For instance: - shotwell is in 1rst position, but when I look at the reports, there are 2 bugs with a heat of 3491, and I don't see anything specific that could explain such a value. Is it the weight of untriaged report being a bit too important or something else ? It doesn't seem to match the bug heat algorithm. Looking closer at the bug heat algorithm it seems that a fair bit of it is based on recent activity. From some of the documentation the theory follows: Bug has been active within the past 24 hours Add 25% of the project's hottest bug's score divided by the number of days since the first activity on the bug in question Bug has not been active* in within the past 24 hours Subtract 1% of the bug heat score for every day of inactivity So it seems to follow that the newest bugs will the highest heat. I guess there is a larger question of what we think makes a bug hot. Initially, I thought the number of users affected, number of subscribers and number of duplicates (among some other things) was a good indicator. Two out of those three things are now cached on the bug table so we could recreate the bug heat without taking into account recent activity. I feel like this might provide a more useful number. - gbrainy, I was surprised to find a game in the list. In fact, there is a very limited number of bugs filed against this package and some of them with high heat. I've triaged the report with the highest heat (300) and it fell to a heat of 12. So the next run of your script should move it lower into the list. - gcalctool, same thing, the first bug had a heat of 237, and after asking for more information it fell to 8. So, yes, this is useful to help us to direct our testing and triaging effort. But the calculation of the bug heat needs to be clarified. Maybe this could be added to the 'Opportunities' list in harvest ? By this do you mean the hottest, those outside the standard deviation, bugs for a package should be listed as an opportunity in harvest? Thanks, -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Packages to investigate
As we all know there are a lot of packages and bugs to keep track of in Ubuntu. One idea that occurred to me recently, to help identify packages in need of triage, was to calculate an average bug heat for the particular package. I've made a first pass at this using all the packages in the ubuntu-desktop package set. Here are the top 10 packages: usb-modeswitch-data - median: 764, mode: 1448 language-pack-gnome-fa-base - median: 408, mode: 408 language-pack-gnome-pt - median: 318, mode: 318 couchdb-glib - median: 210, mode: 210 netbook-meta - median: 145, mode: 408 pyopenssl - median: 136, mode: 259 shotwell - median: 124, mode: 6 appmenu-gtk - median: 122, mode: 408 gnome-python-extras - median: 114, mode: 3 telepathy-gabble - median: 104, mode: 49 As I ran this last Friday there might be some variance in the numbers. I'm curious whether or not you think the bug reports for these packages really need reviewing. Thanks, -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re:
On Tue, Jul 20, 2010 at 06:29:10PM -0600, Charlie Kravetz wrote: On Tue, 20 Jul 2010 15:23:31 -0700 Brian Murray br...@ubuntu.com wrote: On Mon, Jul 12, 2010 at 04:31:09PM -0400, Mackenzie Morgan wrote: On Sun, Jul 11, 2010 at 9:09 PM, Bradley Spearpoint bradley.spearpo...@yahoo.com wrote: i would like a ubuntu disk sent to me please You can request CDs from http://shipit.ubuntu.com This list is for the quality assurance team. I wonder if there something about the list name / description that could be clarified to prevent messages like this. At lists.ubuntu.com it currently says: Ubuntu Quality Assurance discussion list Any ideas on what might help? Thanks, -- Brian Murray Ubuntu Bug Master Many think of Quality Assurance as the place to resolve issues, since any issue is a degradation of quality. Perhaps something like: Ubuntu Quality Assurance (bug triage, testing, etc) discussion list would more clearly define it while keeping it short. Thanks for the idea I've gone with this easy change in the hopes that it may have some effect. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Ubuntu QA Meeting Minutes - 2010-06-09
On Thu, Jun 10, 2010 at 02:45:57PM -0400, Ronald McCollam wrote: == Meeting logs == I do not believe that #ubuntu-quality is logged (at least I have been unable to find the logs) so I have put a transcript here: http://people.canonical.com/~fader/20100609.txt == Actions from last meeting == * ara to create hudson+mago branch and write some docs: DONE, see https://wiki.ubuntu.com/FoundationsTeam/Specs/SharingTestingInfrastructure#Mago%20Tests * ara to talk with IRC council to set up bot in #ubuntu-quality: DONE == SRU Testing (sbeattie) == The latest report as well as an archive of previous ones can be found at: https://wiki.ubuntu.com/QATeam/SRUReports Help testing Stable Release Updates is always needed! You can check what needs testing at: http://people.canonical.com/~ubuntu-archive/pending-sru.html == Bug Day status (pedro_) == Last week the Bugsquad team ran a Bug Day for Compiz: https://wiki.ubuntu.com/UbuntuBugDay/20100603 Turnout was low due to Alpha 1 also being released that week, using a lot of testing resources. ~15 bugs were triaged that day. The next Bug Day is on gnome-games and work has already begun: https://wiki.ubuntu.com/UbuntuBugDay/20100610 Help always welcome! You can join the Bugsquad at #ubuntu-bugs == Blueprints update (all) == Status toward Alpha 2 is available here: http://people.canonical.com/~pitti/workitems/maverick/canonical-platform-qa-maverick-alpha-2.html sbeattie and hggdh are re-evaluating the server tests to verify what is possible and drop the tests that cannot be performed. == Kernel Triage Summit (JFo) == The kernel team is redefining their triage methods. Work is ongoing on this front, but the following wiki pages have information already: https://wiki.ubuntu.com/Kernel/Tagging https://wiki.ubuntu.com/Kernel/BugReview Additionally they are planning what is hoped to be a twice-yearly event called the Kernel Triage Summit. This will be an online event to help triagers learn how to work with various types of kernel bugs. There will be sessions on how to triage bugs for specific kernel subsystems as well as some general kernel triage sessions. JFo is still preparing information about the event and will be sending out information on several mailing lists. He has also agreed to return to the QA meeting to provide this information there. Finally, he has discussed this on the Ubuntu UK podcast: http://podcast.ubuntu-uk.org/2010/06/09/s03e09-the-talk-of-the-town/ == Sound Card Compatibility Testing (awbancroft) == awbancroft has pointed out that audio is an area of concern for bugs in Ubuntu. After some discussion, we decided to try a targeted testing program similar to the one we ran last cycle for proprietary video driver tests. awbancroft has agreed to head up this effort and will put together a plan for testing with ara acting as a mentor. There are also several wiki pages with information about audio testing. JFo is working on a central location for these, but until that is ready, the information is available here: https://wiki.ubuntu.com/Audio https://wiki.ubuntu.com/DebuggingSoundProblems == Selection of new chair (fader_) == bladernr has agreed to act as chair next week. The meeting will take place at 1700 UTC in #ubuntu-quality. == Location of meetings == ara and bladernr proposed that we keep the meetings in #ubuntu-quality rather than #ubuntu-meeting for flexibility and control purposes. A vote was had and was unanimously in favor of this. Future meetings will take place in #ubuntu-quality. Shouldn't there be an action to update the Fridge about the meeting location then? == Actions == * sbeattie and hggdh to reevaluate server tests * AWB to put together a structured testing program for audio testing (with mentorship from ara) -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: ISO testing: reporting bugs on current versions
On Mon, Jun 07, 2010 at 09:17:53AM -0400, J wrote: On Mon, Jun 7, 2010 at 06:44, Byte Soup bytes...@gmail.com wrote: Hi All, I just signed up for some ISO testing and it seems ive missed the boat on getting the right image now as every image reference on the tracker page points to one thats not there anymore: http://iso.qa.ubuntu.com/qatracker/ Anyway if I find a problem with a current version, whats the best way to report this bug? I guess I cant submit the results into the tracker can I? The same way we file bugs during ISO testing. Via Launchpad. The only catch is, if you do not add the bug to a result in the ISO tracker, you need to manually add the tag iso-testing to the bug you file in Launchpad. Normally, if you open Bug 123456 against something during ISO testing, and then you note that bug in your testing status and submit, the isotracker will automagically add the iso-testing tag to bug 123456. BUT, you only need to do this during iso testing, really. If you find a bug, just open it as you would with any bug for any other version at any time. I usually put the release in the Bug subject line, something like this: [Maverick A1]Something happened that was bad and this broke. It'd be best if you did not use the bug's title for inserting information like [Maverick A1] as this used by Launchpad's duplicate finding feature and will likely create false positives. Instead I'd tag the bug maverick, which would be done automatically if you report it with apport, and only include the image information (in the description) if it may be specific to that ISO and not the release as a whole. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: howto report suspend failure
On Mon, Apr 26, 2010 at 12:49:41PM +0200, Pavel Kukačka wrote: Hello, my laptop does not wake up after suspend and I would like to file a bug report for that. But I only see that the laptop doesn't do anything (the screen is blank (after pressing the on/off button while suspended) and the only way out is to switch off the laptop and start it from batteries, with the power cable unplugged) and I consider that too few information for a bug report. Do you know where should I look, what logfile to add to the bugreport? It seems that it's a hardware or BIOS bug (tafkos's comment on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/308820 ). Or is it better to subscribe myself to one of these - similar - issues: * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/308820 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/349980 ? Suspend and resume functionality is very much hardware dependent. So unless one of those bug reports is about the exact same model laptop as yours it is best to file a new bug report using the command 'ubuntu-bug linux'. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: UNSUSCRIBE PLEASEEE
On Tue, Apr 20, 2010 at 01:56:13PM -0400, Scott Howard wrote: Hello, Follow the instructions on the bottom of every mail from the mailing list to unsubscribe (see the instructions at the bottom of your email too). For what its worth I already unsubscribed them using listadmin. -- Brian Murray Ubuntu Bug Master signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: package nip2 (7.20.6-1ubuntu2) [universe] in lucid needs updating
On Mon, Mar 15, 2010 at 10:54:44AM +, jcup...@gmail.com wrote: Hi everyone, I'd like to get package nip2 (7.20.6-1ubuntu2) [universe] updated to the version currently in Debian (http://packages.debian.org/testing/nip2). I filed a bug about it: https://bugs.launchpad.net/ubuntu/+source/nip2/+bug/525783 Is there anything else I can do to give this a push? Did I tag the bug incorrectly? At this point in time we are past feature freeze in Lucid's development you will need to follow the Freeze Exception Process: https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze -- Brian Murray Ubuntu Bugmaster Days running lucid: 34 signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Application Testing - wiki pages and QA website
On Mon, Dec 14, 2009 at 08:30:23AM +0100, Ara Pulido wrote: Hello Scott, Thanks for noticing this. On 12/13/2009 11:41 AM, Scott Ritchie wrote: While editing the testing wiki pages I was creating a section for Application Testing when I noticed that https://wiki.ubuntu.com/Testing/Applications and http://testcases.qa.ubuntu.com/Applications appear to be two different things. http://testcases.qa.ubuntu.com/Applications is a wiki and everyone can edit it. In fact, it is supposed to be the place to hold any written test case (Canonical or Community driven) and I think it should be a better place to put them. I noticed that the X team has some test cases[1] that don't appear at testcases.qa.ubuntu.com. Should these be moved to that site so that they are visible to more people? [1] https://wiki.ubuntu.com/X/Testing -- Brian Murray @ubuntu.com signature.asc Description: Digital signature -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
