Re: i guess it's pointless to report bugs on pulseaudio in lubuntu
On Mon, 16 Apr 2012 20:25:38 -0400 Karl Anliot wrote: > after installing pulseaudio, youtube in chromium crashes consistently, > and the mute button on my keyboard is broke. I guess It's pointless > to report these... coz lubuntu doesn't use pulseaudio? > Just because PA is not on the ISO doesn't mean it shouldn't work with Lubuntu. So it is still worth reporting. I have Lubuntu 11.10 working with PA OK and intend to update that machine to 12.04 at some point so the less problems the better ;) -- Steve -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: build
On Mon, Mar 12, 2012 at 02:08:14PM -0400, Nicholas Skaggs wrote: > In addition, I don't believe the period in the date is intentional -- > someone correct me if I'm wrong here :-) > > IE, 20120301.1 should actually be 201203011 No, if the daily image gets respun, the date gets a .N suffix appended to it; .1 is the first respin, .2 is the second. -- Steve Beattie http://NxNW.org/~steve/ 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
apt-term.log in jenkins only shows removals on upgrade, not installs?
Hi folks, When trying to confirm whether bug #911659 is still present, I noticed that in the most recent successful upgrade test in jenkins, <https://jenkins.qa.ubuntu.com/view/Precise%20Upgrade%20Testing%20Dashboard/job/precise-upgrade-lucid-main/ARCH=amd64,LTS=lts,PROFILE=main-all,label=upgrade-test/30/>, includes an apt-term.log that *only* shows removals, no upgrades/installs. I believe this is because this is the log of the *second* apt invocation by do-release-upgrade, to remove unnecessary packages from the system after the main body of the upgrade has been completed. Is the terminal log of the upgrade itself available in another location, that can be attached to the jenkins build report? Or has this been irremediably clobbered? (In the latter case, should we perhaps be invoking do-release-upgrade in such a way that it doesn't do the post-upgrade cleanup, so that we preserve the term log for the upgrade phase?) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org 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: Meeting 2010-10-06 - 17:00 UTC - #ubuntu-quality
On Tue, Oct 05, 2010 at 11:04:45PM +0200, Sulu Mayer wrote: > Frist of all i cant veryfie that pgp signature and dont know why. probably > forgot soething. lol It verified here just fine, how is it failing for you? Do note that firegpg, which you appear to be using, has been discontinued due to the author's inability to cope with the frequent changes to the gmail interface; see http://blog.getfiregpg.org/2010/06/07/firegpg-discontinued/ for more info. Sorry you can't make the meeting. Thanks. -- Steve Beattie http://NxNW.org/~steve/ 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: A script I wrote to quickly download the daily builds
On Thu, Aug 26, 2010 at 06:11:09PM -0400, Jeff Stone wrote: > I hope this is appropriate to share here, Most definitely, thanks for the interest in testing daily isos. > I've written the following script to help download daily builds. I > call it zsync-ubuntu-daily-live. As it is right now, if you execute > it with no parameters, it will automatically download the ubuntu > and ubuntu-netbook daily build, but it also supports kubuntu and > xubuntu. Extending it for other *buntus is straightforward. First it > checks for a new build by comparing the timestamp of MD5SUMS. If > there's a new build, it will use zsync or wget as appropriate. You > need the zsync package installed. A number of the people who test isos are using the dl-ubuntu-test-iso script: http://bazaar.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master/annotate/head%3A/dl-ubuntu-test-iso/dl-ubuntu-test-iso from the ubuntu-qa-tools project: https://code.launchpad.net/~ubuntu-bugcontrol/ubuntu-qa-tools/master It's a tad overcomplicated and somewhat hackish for what it does, but it supports picking and choosing the various *buntus and flavors (daily-live, alternate, dvd) as well as arches (though it doesn't support arm varieties yet). It also attempts to use zsync first and falls back to anonymous rsync access (which cdimages.ubuntu.com supports) if zsync isn't available. At least a few of us run it out of cron to keep our set of daily images up to date. Ideally, it would integrate well with the testdrive tool: https://launchpad.net/testdrive for quickly spinning up isos in VMs for testing, but no one's had the time to take that on this cycle (that I'm aware of). (I also had grandiose plans of adding jigdo support as well as support for feeding into an apt caching daemon like apt-cacher or apt-cacher-ng.) You're obviously welcome to use and develop whatever tool you find most convenient. Thanks again for the interest. -- Steve Beattie http://NxNW.org/~steve/ 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
Ubuntu QA Meeting Minutes - 2010-06-03
== Meeting logs == http://irclogs.ubuntu.com/2010/06/02/%23ubuntu-meeting.html == Actions from last meeting == * sbeattie: archive SRU reports in the Ubuntu wiki: DONE, see https://wiki.ubuntu.com/QATeam/SRUReports * hggdh: ask stgraber how often they are having Edubuntu meetings (at 19:00 UTC): Missed contact, but Edubuntu does appear to hold weekly meetings * ara: send txwikinger an overview of the ISO tracker work: DONE txwikinger is now looking in to it, and will get back to ara when he's ready to contribute. * ara: send email to awbancroft about Sound Card Compatibility Testing: 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_) == The Bugsquad team are doing a great job keeping the bug days weekly cadence. Last week they had one focused on the Epiphany Web Browser and they triaged 52 bugs! On the same day, the KDE triagers held a bug day focused on KDEPim, and, despite the confusion of holding it on the same day as the Epiphany Bug Day, managed to triage 13 bugs! If you know these people, evfool, vish, kamusin, micahg, dmitrij.ledkov, skarottes, txwikinger, yuriy, keffie_jayx, NickNak and sinzui, give them a hug. They help make Ubuntu better. Thanks! Today they are running a Compiz Bug Day: https://wiki.ubuntu.com/UbuntuBugDay/20100603 and the KDE Triagers will be holding a kdenetwork Bug Day on Monday, June 7th: https://wiki.ubuntu.com/UbuntuBugDay/20100607 Help always welcome! You can join the Bugsquad at #ubuntu-bugs == Blueprints update (all) == === qa-maverick-mago-daily === ara has been playing around with Hudson to run Mago tests as local "builds" and is starting to work on getting them run on satellite systems rather than the Hudson server. To encourage people to play around with it, she will publish a branch with sample configurations and write up some documentation for the wiki. == Sound Card Compatibility Testing (awbancroft) == Unfortunately, awbancroft could not make it again. Hopefully we can discuss it at next week's meeting. == Alpha 1 ISO Testing status (ara) == ara reported that the Alpha 1 testing coverage was looking good, though there were a few images that still needed coverage. For early alphas, we don't expect 100% coverage, but we do expect 100% test image coverage. == Firefox 3.6.4 security update testing - ara == Because xulrunner 1.9 is no longer supported, the upcoming security update for Firefox will involve upgrading the versions in Hardy, Jaunty and Karmic, as well as Lucid (which already had the 3.6 series). These need lots of testing; to help out, follow the steps at https://wiki.ubuntu.com/Testing/Firefox3.6.4Upgrade The Firefox update got pushed back to June 7th, so there is a little more time available to help with testing. == Actions == * ara to create hudson+mago branch and write some docs * ara to talk with IRC council to set up bot in #ubuntu-quality Next meeting: June 9th, 19:00 UTC, at #ubuntu-quality *** Note new time and location *** Meeting chair will be fader. Thanks! -- Steve Beattie http://NxNW.org/~steve/ 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
QA Meeting reminder and call for topics
Hello all! Just a quick reminder that tomorrow, June 2nd, we are having our weekly IRC meeting at 17:00 UTC, in #ubuntu-meeting on irc.freenode.net. Please, add your topics to https://wiki.ubuntu.com/QATeam/Meetings So far, the agenda is: * review previous action items (all) * SRU testing -- sbeattie (Steve Beattie) * Bug Day status -- pvillavi * meetings schedule - ara * Blueprints update -- all * Sound Card Compatibility Testing - awbancroft * Selection of new chair - sbeattie Thanks! -- Steve Beattie http://NxNW.org/~steve/ 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: log-in to ubuntu iso test track
On Thu, May 20, 2010 at 03:09:52PM +0200, alessandro wrote: > l 19/05/2010 23:15, Steve Beattie ha scritto: > If you're still having issues, perhaps you can send me your login id > offlist and I can reset your password; I looked briefly through the > admin interface for your account but could not find it. > > I have already created an accont to iso tracker but I have no e-mail > password Just so we don't have conflicting password resets going on, I've responded to alessandro off list. -- Steve Beattie http://NxNW.org/~steve/ 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: log-in to ubuntu iso test track
Hi Alesandro, On Wed, May 19, 2010 at 09:17:11PM +0200, alessandro wrote: > hi everybody... i can not log-in to: http://iso.qa.ubuntu.com/ > > why? Hrm, I'm able to log in successfully to the iso tracker. Do note that logins on the iso tracker have not been integrated with launchpad logins, so you need to create a separate account with the tracker. If you're still having issues, perhaps you can send me your login id offlist and I can reset your password; I looked briefly through the admin interface for your account but could not find it. Thanks, and sorry you're having troubles with the tracker. -- Steve Beattie http://NxNW.org/~steve/ 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, 26 Apr 2010 11:49:41 +0100, 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 ? > > Thanks for any hint, > Pavel > > Try having a look at this https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and see if it helps -- Steve (Yorvyk) http://www.lubuntu.net -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: dls-003 testcase.
Hi Sergio, On Fri, Mar 12, 2010 at 07:31:54PM +0100, Sergio Zanchetta wrote: > 2010/3/12 Sergio Zanchetta : > > On DesktopLiveSession wiki page, I think that dls-003 case needs to be > > updated. > > USB creator already provides casper-rw and you don't need to create a > > dedicated partition or add persistent on boot. > > > > Am I wrong? > > > > Sorry, I forgot to add the page: > http://testcases.qa.ubuntu.com/Install/DesktopLiveSession It's quite possible I'm mistaken, but I think the situation covered is subtly different. The test case dls-003 tests whether a USB device (or another partition) can be used as persistent storage for the livecd environment; that is, booting off of the LiveCD and storing any changed data to the persistent partition. My understanding of the USB creator tool is that it copies over the entire live environment to the USB device and makes that bootable and persistent. While that's arguably more useful in that only the USB device is needed to subsequently boot and run, I think it's still worth testing to make sure persistence still works with the LiveCD. There are still systems out there that refuse to boot off of USB devices. Also note that USB creator has it's own set of testcases at http://testcases.qa.ubuntu.com/Applications/StartupDiskCreator that cover the use cases for it pretty well. These have recently been added as standard testcases to be covered during our milestone ISO testing under "Generic Tests". You can see the results from the alpha 3 testing at http://iso.qa.ubuntu.com/qatracker/test/3661 ; alas, they did not get very good coverage. -- Steve Beattie http://NxNW.org/~steve/ 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
Upcoming 8.04.4 point release: SRU validation, ISO testing needed
Hi folks, The fourth and final point release for Ubuntu 8.04 LTS is scheduled for next Thursday, January 28. There are a few SRUs that need to be verified before then: Bug #185878 - GRUB installation fails if installing to certain non-ext3 filesystems Bug #175324 - Klibc: ipconfig fails on network with DHCP relays Can someone help with the SRU verification on these? (I uploaded both of them, so I'm disqualified...) The klibc change still needs to be accepted into the archive, so probably won't be available for validation until Thursday. klibc isn't used as the DHCP client in the installer - we don't need to have new CDs posted that include the new klibc to be able to verify this. But speaking of CDs, I expect to have candidate CDs out before the end of the week that are ready for smoke testing - will there be people available to help with the ISO testing late this week and early next? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org 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: killall NetworkManager in Ub 9.10 and Ub 9.04
On Tue, Nov 17, 2009 at 05:20:48PM -0500, Mackenzie Morgan wrote: > On Tuesday 17 November 2009 3:09:46 pm Lee, Ju-hyoung wrote: > > All, > > > > I see the different behavior according to 'killall NetworkManager' on 2 OS. > > On Ub 9.04, NetworkManager could be removed by this command, but Ub 9.10 > > changed the behavior. The init process monitors this process, and keeps > > resuming back. > > It's network-manager, not NetworkManager, in 9.10. Also, the correct way to > stop services is (and has been) either: > sudo /etc/init.d/ stop > or > sudo serivce stop > > not killall. In 9.10, Network Manager has been converted to upstart, so the recommended way to stop it in that release and going forward is: sudo stop network-manager -- Steve Beattie http://NxNW.org/~steve/ 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: new member and SRU Verification
Hi Vikram! On Fri, Dec 04, 2009 at 11:20:24PM -0500, Vikram Dhillon wrote: > How is everyone doing? I have been a member of Ubuntu testing > team, but I just learned how to test ISO's and such for releases. That's great. Lucid Alpha 1 is coming this week, so any help you can give on that front will be appreciated. > I understand packaging software in Ubuntu, so I wanted to join SRU > Verification team to take on more responsibility and learn more. Please > give me more guidance on what steps do I need to take further. Sure, thanks for your interest. For the record, SRUs are Stable Release Updates, and SRU Verifications are the process we go through to verify a proposed SRU so that it can be released as an update. The SRU process is documented at <https://wiki.ubuntu.com/StableReleaseUpdates>. SRU verification is a great way to participate in the Ubuntu project as well as learn more about the software itself. Basically, what we'd like to see for membership in sru-verification is a demonstration of understanding of how to perform an SRU verification, typically in the form of some example bugs where feedback was given (similar to the bugcontrol team application process). Basically, an applicant needs to demonstrate that they're able to: 1) install the relevant software packages, 2) attempt to reproduce the bug (hopefully successfully) 3) install the versions from the -proposed pocket 4) again, attempt to reproduce the bug (hopefully failing), 5) look for regressions introduced by the update In your case, I'm unable to find any any such feedback in any of the bug reports that the sru-verification is subscribed to; if you could point me to some examples, I'd be happy to approve your membership. (Fair warning, the sru-verification team is subscribed to a large number of bug reports, and thus gets a non-trivial amount of bugmail. Filtering incoming email is recommended.) There are other ways to contribute to the sru-verification team; currently, there are a couple different web pages we use to track which packages are in the proposed queue: http://people.canonical.com/~ubuntu-archive/pending-sru.html (archive admin view) http://people.canonical.com/~sbeattie/sru_todo.html (mostly covering main) Unifying and improving those would appreciated, as well as helping to improve the documentation at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification would be greatly appreciated. Thanks again for your interest! -- Steve Beattie http://NxNW.org/~steve/ 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: killall NetworkManager in Ub 9.10 and Ub 9.04
On Tue, Nov 17, 2009 at 06:19:44PM -0500, Mackenzie Morgan wrote: > On Tuesday 17 November 2009 5:02:22 pm Steve Beattie wrote: > > In 9.10, Network Manager has been converted to upstart, so the > > recommended way to stop it in that release and going forward is: > > > > sudo stop network-manager > > Upstart has new ways to do things? Is this on the wiki or something? Hrm, I can't find anything on wiki.ubuntu.com; http://upstart.ubuntu.com/getting-started.html documents it in the Job Control section. The other way it's documented is that, at least in karmic, sysv-style initscripts that have been converted to upstart get backwards compatible symlink to an upstart utility that warns you that it's been deprecated like so: $ sudo /etc/init.d/network-manager stop Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service network-manager stop Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the stop(8) utility, e.g. stop network-manager -- Steve Beattie http://NxNW.org/~steve/ 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: killall NetworkManager in Ub 9.10 and Ub 9.04
On Tue, Nov 17, 2009 at 05:20:48PM -0500, Mackenzie Morgan wrote: > On Tuesday 17 November 2009 3:09:46 pm Lee, Ju-hyoung wrote: > > All, > > > > I see the different behavior according to 'killall NetworkManager' on 2 OS. > > On Ub 9.04, NetworkManager could be removed by this command, but Ub 9.10 > > changed the behavior. The init process monitors this process, and keeps > > resuming back. > > It's network-manager, not NetworkManager, in 9.10. Also, the correct way to > stop services is (and has been) either: > sudo /etc/init.d/ stop > or > sudo serivce stop > > not killall. In 9.10, Network Manager has been converted to upstart, so the recommended way to stop it in that release and going forward is: sudo stop network-manager -- Steve Beattie http://NxNW.org/~steve/ 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
