[07:12] <ara> morning all :)
[07:32] <ara> remember that we have a testing day focusing the new notification system: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090316
[07:37] <ara> hey jcollado :-)
[07:37] <jcollado> ara: Buenos días
[07:53] <sabdfl> moin moin everybody
[07:53] <ara> morning sabdfl
[07:57]  * ara reboots
[07:59] <sabdfl> hi mdz
[08:00] <mdz> sabdfl: good morning.  helping out with some testing today?
[08:00] <sabdfl> indeed :-)
[08:00] <eeejay> morning folks
[08:01] <sabdfl> keen to see how this work has landed and where the glitches are
[08:06] <DisSsha> Hi, can someone tell me how Ubuntu tests  regression before add upgrade package ? I don't find your framework or list of test cases
[08:07]  * eeejay  notes that you will need this for testing: http://testcases.qa.ubuntu.com/Applications/Notification?action=AttachFile&do=get&target=notify-osd.py
[08:17] <mdz> sabdfl: there are about 21 bugs which the desktop team feels need to be addressed for beta freeze (which is this Thursday)
[08:18] <ara> I am testing duration of notifications
[08:18] <ara> brightness notifications should last 2 seconds
[08:18] <ara> but they are lasting 5s
[08:19] <ara> I have filed a bug https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/343553
[08:19] <ubot4> Launchpad bug 343553 in notify-osd "Brightness notifications have a duration of 5000ms" [Undecided,New]
[08:19] <ara> eeejay: do you experience the same?
[08:19] <eeejay> ara: i filed a bug too, it was invalidated since it is expected behavior
[08:20]  * eeejay looks for bug number
[08:21] <ara> mdz: is there a public list of those bugs somewhere?
[08:21] <eeejay> https://bugs.launchpad.net/bugs/342291
[08:21] <ubot4> Launchpad bug 342291 in notify-osd "Synchronous bubbles last for 5 seconds" [Undecided,Invalid]
[08:21] <mdz> ara: I'm emailing a list right now, would you like a CC (and is there anyone else I should include)?
[08:21] <mdz> (note these are not all notifications issues but a general DX team list)
[08:22] <ara> mdz: yes, CC me. pedro also would like to know about this. thanks :)
[08:23] <ara> eeejay: the bug I filed is a different one
[08:23]  * eeejay looks
[08:23] <ara> eeejay: I am experiencing 5 seconds for brightness, even though I haven't an asynchronous one
[08:24]  * eeejay tries
[08:24] <mdz> ara: sent
[08:24] <eeejay> ara: yup. good catch!
[08:25] <ara> mdz: ta!
[08:27] <ara> morning davmor2 :)
[08:27] <eeejay> morning davmor2
[08:27] <davmor2> ara: morning
[08:28] <davmor2> eeejay: morning too
[08:28] <davmor2> morning everyone else :)
[08:30] <davmor2> ara: before I get started today keybuk has asked me to test the new hardened version of the lvm/partitioning fix and evand has asked me to test the latest wubi against vista
[08:30] <davmor2> just to let you know :)
[08:30] <ara> davmor2:  :-) np
[08:44]  * eeejay grabs breakfast
[08:57] <DisSsha> Please, what is Motu ?
[08:57] <davmor2> Masters Of The Universe
[08:58] <davmor2> devs that maintain the universe repo
[08:59] <DisSsha> ok thanks
[09:30]  * ara takes a break
[09:33] <davmor2> ara: when you get back on startup do you get notify-osd info about your interweb connection ie. wifi connected, ethernet connected etc?
[09:51] <eeejay> davmor2: you should, yes.
[09:51] <eeejay> davmor2: when nm establishes a connection
[10:14] <ara> davmor2: I do get those notifications
[10:29] <davmor2> so just me then :)   I get them if I click on it again just not from startup
[10:31] <Shane_Fagan> Is anyone having trouble with pulseaudio in jaunty?
[10:32] <davmor2> you need to be more specific than that Shane_Fagan
[10:33] <Shane_Fagan> Jaunty 64bit. Pulseaudio makes weird noises (crackling) and the only way to fix it is to restart pulseaudio or restart the computer.
[10:34] <ara> Shane_Fagan: does this bug apply to your problem? https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/301755
[10:34] <ubot4> Launchpad bug 301755 in pulseaudio "Crackling noise after update to pulseaudio" [Low,Fix released]
[10:35] <ara> Shane_Fagan: maybe updating should fix your problem
[10:35] <Shane_Fagan> All upgrades installed it happened 10 minutes ago
[10:39] <Shane_Fagan> It has been happening for about week
[10:39] <davmor2> I'm not getting crackly sound from today's cd
[10:40] <weboide> What is the "attached program" in the test cases?
[10:41] <davmor2> weboide: click on attachments
[10:41] <eeejay> weboide: and get notify-osd.py
[10:41] <weboide> Thanks davmor2 and eeejay ;)
[10:42] <eeejay> weboide: no no, thank _you_ for testing ;)
[10:42] <weboide> hehe :)
[10:44] <davmor2> meh ubiquity is broken today :(
[10:48] <Shane_Fagan> My problem isnt persistent so ill wait to see if an update fixes it.
[10:49] <davmor2> Shane_Fagan: is your issue only on the login music
[10:49] <Shane_Fagan> No login music was fixed. Its with the regular sound.
[10:50] <davmor2> right I'll try it out when I get a working system :)
[10:51] <davmor2> Shane_Fagan: what audio hw do you have?
[10:51] <Shane_Fagan> Nvidia
[10:52] <davmor2> Shane_Fagan: type in lspci -vvnn and add it to the bug above and say your still having issues on today's date
[10:53] <davmor2> Shane_Fagan: better still type in lspci -vvnn > lspci.txt and add the .txt file
[10:55] <Shane_Fagan> I already posted it as a comment.
[11:07] <Shane_Fagan> davmor2: Did you find anything interesting in my lspci -vvnn ?
[11:07] <davmor2> Shane_Fagan: similar hw to what I've got so I can have a play after :)
[11:10] <Shane_Fagan> What happens is that it works normally then I leave my computer for a while (long enough for the monitor to go on standby). Then when I get back the sound crackles.
[11:13] <davmor2> okay I'll try it out after :)
[11:22] <davmor2> eeejay, ara: notify-osd does do the connections in todays image :)
[11:22] <eeejay> davmor2: is it not supposed to?
[11:22] <ara> davmor2: good to know
[11:22] <davmor2> eeejay: yes :)
[11:23] <davmor2> it didn't in alpha 6 but does now :)
[11:23] <eeejay> davmor2: ah, good news! you don't hear enough good news on testing days :)
[11:24] <davmor2> eeejay: your not meant to we are looking for broken stuff not fixed ;)
[11:24] <eeejay> davmor2: i know, what a depressing job..
[11:25] <davmor2> eeejay: No it isn't you make Ubuntu better :)
[11:25] <eeejay> davmor2: true, but thanks to undertakers, there are no dead bodies on the street either :)
[11:41] <ara> eeejay: congrats on the new accerciser release ;-)
[11:42] <eeejay> thanks ara, no more bugs
[14:30] <svesmeralda> This is my first time on an IRC.  I have been using Ubuntu for almost 2 years and would like to get involved with the the testing.  I have some experience with virtualbox and have it installed.  Any help will be appreciated.
[14:37] <davmor2> Hi Chris Gregan you back home dude?
[14:39] <ara> svesmeralda: Hello, we maintain a website with the available test cases at http://testcases.qa.ubuntu.com
[14:40] <ara> svesmeralda: we also run weekly testdays on mondays. To see the topic of today's test day you can check https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090316
[14:40] <svesmeralda> ara:  Okay, I will go there to see what it is about.  I am just feeling my way through and should have the hang of it soon.  Thanks.
[14:50] <nicolaide> hi... When you talk about Start attached program. in the test cases... What try to say? to start the notifications with someting like notify-send testingNotifiation in the console?
[14:51] <davmor2> nicolaide: if you click on attachments there is an app to download :)
[14:52] <davmor2> run that app and it will trigger the various notifications :)
[14:52] <nicolaide> upssss
[14:52] <nicolaide> my mistake... i need to sleep more :P
[14:53] <davmor2> :)
[14:59] <nicolaide> nice... all tested now :P
[15:01] <ara> nicolaide: you can also play around and find new test cases :)
[15:02] <nicolaide> nice...
[15:06] <nicolaide> guys... if i make a new notification and i play with the sound by increasing and decreasing the volume, the first notification steel showed... Only desapear if the sound notification are closed before i finish to "play with the sound". The result i expect is that... After 5 seconds the first notification need to be closed and no need to depend of other notifications... Im rigth?
[15:09]  * ara reads
[15:10] <ara> eeejay: this is a similar test case ^ to the one we talked in the sprint, but the other way round. do you know more?
[15:11] <eeejay> ara, nicolaide, yes, let me fish out the bug number again... davidbarth explained the behavior there
[15:11] <nicolaide> the result i spect is similar like the first mockup showed by mark here... http://www.markshuttleworth.com/wp-content/uploads/2008/12/jaunty904_notifications_example1_web_092.swf ... see when jorge talk and the wifi signal lost...
[15:11] <nicolaide> okey
[15:12] <nicolaide> i go to lunch... back in half hour!
[15:12] <nicolaide> thanks!
[15:12] <eeejay> https://bugs.launchpad.net/bugs/342291
[15:12] <ubot4> Launchpad bug 342291 in notify-osd "Synchronous bubbles last for 5 seconds" [Undecided,Invalid]
[15:12] <eeejay> nicolaide: see if the last comment in this bug makes sense ^
[15:43] <nicolaide> eeejay: i back... yeah... i read the last comment, but i like the example of the notifications that i showed in the example... other implementation can be that... if the volume notification are showed just extend the time of the other notification 50% of the original time displayed... what do you think?
[15:45] <sbeattie> dumb notification question; is the app or notify-osd supposed to have the final say as to how long the notification bubble appears?
[15:46] <davmor2> sbeattie: notify-osd does
[15:46] <davmor2> looks like it's pretty much set to 5 seconds
[15:46] <sbeattie> it does; is it supposed to? Is that the intended behavior?
[15:47] <davmor2> sbeattie: looks like it yes bug 342291
[15:48] <ubot4> Launchpad bug 342291 in notify-osd "Synchronous bubbles last for 5 seconds" [Undecided,Invalid] https://launchpad.net/bugs/342291
[15:49] <sbeattie> that is, if an app requests a 1 second timeout (assuming it asks "correctly", which may not be true in the example I have), is the ex
[15:49] <sbeattie> erk, nm
[15:52] <ara> sbeattie: what it is your use case?
[15:53] <sbeattie> oh, I was just poking at notify-send (from the libnotify-bin package) and seeing how it behaved under notify-osd.
[15:53] <ara> sbeattie: those should last 2seconds
[15:54] <ara> sbeattie: sorry, 5s
[15:54] <sbeattie> notify-send --expire-time=1 foo lasts for 5 seconds.
[15:54] <ara> sbeattie: yes, that's expected
[15:54] <sbeattie> thanks.
[15:54] <ara> 5 sec for asyn notifications, 2s for sync
[15:55] <ara> sync for things like: ejecting a cd, changing the volume, brightness, etc
[16:18]  * eeejay heads out
[16:21] <ara> eeejay: have a nice flight :)
[16:48]  * ara heads out
[17:41] <stgraber> ogasawara: around ?
[17:41] <ogasawara> stgraber: yup, what's up
[17:42] <stgraber> ogasawara: are you familiar with CIFS in Hardy's kernel ? We had some weird error message at a customer and possibly two related kernel panics.
[17:43] <stgraber> ogasawara: http://paste.ubuntu.com/132097/
[17:43] <ogasawara> stgraber: I'm not really familiar, but I could try to investigate a bit
[17:44] <ogasawara> stgraber: which kernel version (cat /proc/version_signature) and did it just recently start happening (ie regression)
[17:46] <stgraber> ogasawara: not a regression AFAIK, happened the first time we tried cifs there
[17:46] <stgraber> Ubuntu 2.6.24-23.48-server
[17:53] <ogasawara> stgraber: don't suppose you were able to get logs of the panic?
[17:54] <ogasawara> stgraber: I see a few samba bugs with similar error messages, but both have been marked invalid
[17:54] <ogasawara> stgraber: bug 207671 and bug 209402
[17:54] <stgraber> ogasawara: unfortuantely not, they're now in a bladecenter so next time it happens I'll be able to get it, though I hope it never will :)
[17:54] <ubot4> Launchpad bug 207671 in samba "CIFS VFS error each 4 seconds in Ubuntu 8.04" [Undecided,Invalid] https://launchpad.net/bugs/207671
[17:54] <ubot4> Launchpad bug 209402 in samba "Samba shares die with input/output error" [Undecided,Invalid] https://launchpad.net/bugs/209402
[18:12] <stgraber> ogasawara: doesn't seem to be what we're experiencing there, we get those messages when mounting a samba share then everything works fine except in two cases where we got kernel panics
[18:13] <stgraber> for now we're doing testing on that solution but it should be moved to production for 40k users in a week or two :)
[18:32] <stgraber> ogasawara: who's likely to know about cifs related bugs ?
[18:35] <ogasawara> stgraber: good question, I don't think we have a specific expert on the team.
[18:39] <stgraber> ogasawara: I believe slangasek is familiar with samba but I don't know about cifs
[20:27] <apw> cr3, i thought there was going to be an upload of checkbox for alpha-6
[20:27] <cr3> apw: tomorrow
[20:28] <apw> that doesn't seem to have happened, and we don't therefore have the test scripts out there
[20:28] <cr3> apw: I wanted to get your logging window in before then, but it doesn't look like it's going to happen
[20:28] <apw> hmmm, i was sure there was meant to be an upload for a-6 generally to carry existing things
[20:29] <apw> so we will _definatly_ have something for beta freeze?  else our suspend call will go to hell
[20:29] <apw> s/call/call for testing/
[20:32] <cr3> apw: yes, tomorrow for sure
[20:34] <cr3> apw: I had requested for an update before FF in bug #331402, but never got a response
[20:34] <ubot4> Launchpad bug 331402 in checkbox "Please update Checkbox to latest stable 0.6 in Jaunty" [Undecided,New] https://launchpad.net/bugs/331402
[20:35] <cr3> I guess I'll close that bug...
[20:35] <apw> or use it to push the 0.7 update on ?
[20:36] <apw> let me know if you are having trouble getting the upload done
[20:36] <cr3> schwuk: ^^^
[20:36] <apw> i will go twist some arms to make sure it gets done
[20:36] <cr3> apw: he'll be taking care of the upload
[20:37] <cr3> ... because I seem to be on the /ignore list ;)
[20:37] <crashsystems> I'm not seeing any notify-osd action when I change brightness or volume.
[20:37] <apw> our testing strategy for beta depends on it, and we have visibility from on high, so i will be checking up on it too
[20:37] <schwuk> apw: Cool - thanks
[20:38] <apw> schwuk, cr3, if you could let me know when the upload is ready/submitted whatever and where i can track it, and i'll do what i can to greese the wheels
[20:38] <schwuk> apw: will do.
[20:38] <cr3> apw: is it alright if schwuk simply subscribes you to the bug?
[20:39] <cr3> schwuk: just make sure to set the summary to "enlarge your manhood" so that apw pays particular attention to it
[20:40] <schwuk> cr3: I thought only you read those e-mails ;)
[20:40] <apw> heheh
[20:40] <cr3> schwuk: not only read but respond too!
[20:41] <crashsystems> So now that I've found something with notify-osd that does not work on my system, what do I do? Is there some diagnostics for me to run, or somewhere to report the issue?
[20:43] <cr3> crashsystems: you might like to simply report a bug in launchpad or make sure one is not there already
[20:43] <crashsystems> ok, will do
[20:43] <cr3> crashsystems: thanks!
[21:01] <crashsystems> https://bugs.edge.launchpad.net/notify-osd/+bug/343896
[21:02] <ubot4> Launchpad bug 343896 in notify-osd "No notifications for volume & brightness change" [Undecided,New]
[21:04] <mrooney> crashsystems: ahh yes that is a popular one
[21:05] <crashsystems> I did a bunch of searching but did not see it in LP
[21:05] <crashsystems> unless it was filed without using the words "volume" and/or "brightness"
[21:05] <mrooney> yeah that is a dupe
[21:05] <mrooney> nope I think the title is almost identical :)
[21:05] <crashsystems> when why did search not find it?
[21:05] <mrooney> well it may not be upstream
[21:06] <crashsystems> so I reported it in upstream, instead of, say, "jaunty"?
[21:07] <mrooney> ah, I was thinking of bug 331311
[21:07] <ubot4> Launchpad bug 331311 in gnome-settings-daemon "volume/brightness notifications are blank (all black)" [High,Fix released] https://launchpad.net/bugs/331311
[21:07] <mrooney> which is apparently fixed
[21:07] <crashsystems> and is that fix built and in the repos?
[21:08] <crashsystems> also, I hear talk of icons, so take not that I'm _not_ running the default icon theme
[21:09] <mrooney> crashsystems: here we go: bug 338837
[21:09] <ubot4> Launchpad bug 338837 in notify-osd "New notification does not work if icon theme is changed from Human" [High,In progress] https://launchpad.net/bugs/338837
[21:09] <mrooney> that also has a work around that apparently works
[21:09] <mrooney> I'll mark yours as a dupe, but thanks for filing because you caused me to find the real one :)
[21:09] <crashsystems> lol
[21:11] <crashsystems> Yeah, I changed my icon theme to human and it worked. I much prefer Mashup though