[03:39] <phillw> would it be rude to ask why it has taken over 6 hours to add 14 ISO's to the RC tracker from the due date of 21:00 UTC?
[04:45] <pitti> Good morning
[05:02] <jibel> Good morning
[05:07] <elopio> good morning pitti, jibel.
[05:08] <pitti> hey elopio
[05:09] <jibel> Good morning elopio
[05:10] <elopio> hey, do you know how can I debug when the key strokes send by autopilot are being ignored?
[05:10] <elopio> for example, on a textfield on the phone I do keyboard.press_and_release('End'), and most of the times nothing happens.
[05:11] <elopio> but sometimes it works. I have no idea where's the problem, or how to find it.
[05:12] <phillw> pitti: jibel elopio elfy good morning :) I'm hoping the 21:00 UTC for yesterday may not be too prolonged :D. But, with my dark humour around... get the RC's as good as you can :)
[05:13] <elfy> phillw: morning
[05:13] <elopio> o/
[05:14] <thomi> elopio: based on past experiences, the problem is almost always in qtubuntu
[05:14] <phillw> hi elfy, I've got about one more hour left in my personal battery.. just trying to help a team out...
[05:14] <elfy> phillw: my batteries are flat
[05:14] <elopio> thomi: hey, you are still here. Any pointers to debug?
[05:15] <thomi> elopio: sorry, no.. I usually complain to someone like ricmm
[05:15] <elopio> well, that's a good tip.
[05:15] <phillw> Chilean Merlot... does wonders, the side effect is that you speak your mind and people don't like that sort of thing :D
[05:17] <elopio> phillw: :)
[05:19] <phillw> Is there anyone on the channel who is familiar with WordPress ? and, yes. it is for a team.
[05:31] <elopio> phillw: wordpress was a long time ago. Haven't touched it in 3 years.
[05:33] <phillw> elopio: I'm reading through http://wordpress.org/support/topic/edit-home-page as found my a well known search engine :)
[05:33] <phillw> s/my/by
[05:37] <phillw> elopio: yikes!
[05:43] <veebers> elopio: I filed this bug https://bugs.launchpad.net/mir/+bug/1238417 and this bug was helpful https://bugs.launchpad.net/mir/+bug/1233944 for getting details on input, not sure if it helps you in this instance though
[05:43] <veebers> elopio: namely the 2 commands:
[05:43] <veebers> initctl set-env MIR_SERVER_INPUT_REPORT=log
[05:43] <veebers> initctl set-env MIR_SERVER_LEGACY_INPUT_REPORT=log
[05:43] <veebers> elopio: again, not sure if it will be helpful, just thought that I would mention :-)
[05:44] <elopio> veebers: I was debugging it without Mir. But I'll take a look at that, thanks.
[06:09] <DanChapman> morning all
[08:13] <om26er> ubuntu-qa with the very latest image. can you use the OSK ?
[08:13] <om26er> OSK comes up but tapping on it does nothing
[08:30] <rhuddie> om26er, with 20131010.2 I can use OSK
[08:31] <om26er> rhuddie, right. I rebooted the phone and it works for me too. I think its a race. trying to see if I can recreate it again
[08:32] <rhuddie> om26er, good luck :)
[09:02] <pitti> om26er: image 92 here (from this morning), OSK works in messaging app
[09:03] <pitti> om26er: also works in network indicator for connecting to my wifi (first time, entering passwd)
[09:04] <pitti> except that the changed design to input the password into that popup box is horrible
[09:04] <pitti> (no option to show the password any more)
[09:05] <om26er> pitti, yeah, I talked to MacSlow about that and there is no design for that..
[09:06] <pitti> the point is, this already worked :/
[09:06] <pitti> there was nothing wrong with the previous one..
[09:06] <pitti> om26er: but anyway, OSK works here
[09:06] <pitti> (mako)
[09:07] <om26er> right, that was inside the menu, design wanted that as a snap decision and here we are :/
[09:07] <om26er> pitti, right. I couldn't reproduce the issue here either. probably something to do with unity8 restart in my session
[09:07] <pitti> om26er: bug 1238417 again?
[09:08] <slickymaster> morning all
[09:09] <jaywink> hey people .. tried my first ISO testing and this page https://wiki.ubuntu.com/Testing/ISO/Walkthrough says virtualbox, testdrive needed. However, I also found qemu-system package is needed otherwise: "qemu-system-x86_64: not found" .. is this normal, should it be in the wiki? (can add if so)
[09:09] <om26er> probably, not really sure. as in my case the problem was with "real" touches. probably some stacking problem
[09:10] <pitti> uinput devices are not more or less real than touchpads from the perspective or Mir
[09:10] <pitti> they are just standard linux evdev devices
[09:11] <slickymaster> balloons: Hi, do you have any info on the RC images? Has it been pulled? Neither http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55393/downloads nor http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55394/downloads contains anything.
[09:25] <jaywink> to my previous question = it seems testdrive is defaulting to kvm (which required qemu), selecting virtualbox from preferences launched in virtualbox .. this is missing from wiki
[09:38] <rhuddie> om26er, did you raise a bug on the OSK not working?
[09:39] <om26er> rhuddie, I couldn't reproduce the issue again
[09:40] <rhuddie> om26er, ok. I've found it doesn't work in landscape mode... you can try it in Messaging and Notes apps. I'll raise a bug on it.
[09:42] <om26er> for the landscape mode there is already a bug
[09:42] <om26er> its being worked on (probably got a branch attached to it as well)
[09:43] <rhuddie> om26er, ok, I don't need to raise that then
[09:43] <rhuddie> om26er, I presume the problem you saw earlier was in portrait mode?
[09:44] <om26er> rhuddie, yes I saw that issue in portrait
[10:14] <davmor2> Morning all
[10:23] <slickymaster> balloons: Also, http://cdimage.ubuntu.com/xubuntu/daily-live/20131011/saucy-desktop-i386.iso is a broken link
[10:57] <slickymaster> balloons: disregard my last entry, the links is now reestablished
[11:52] <slickymaster> knome: ping
[11:53] <knome> slickymaster, pong
[11:54] <slickymaster> knome: hi, good morning
[11:55] <knome> slickymaster, good day :)
[11:55] <slickymaster> just a quick one. On the Xubuntu-docs there is a phrase which I think has an error: "To see all available connections, click the NetworkManager icon"
[11:56] <slickymaster> Shouldn't it be "To see all available connections, click the <application>NetworkManager</application> icon" instead?
[11:57] <slickymaster> knome: translating it in Launchpad it's line/item 287
[11:59] <knome> possibly, but you should still translate as it is
[12:00] <slickymaster> knome: will do it then, but do you think I should filed a bug againts it?
[12:00] <knome> slickymaster, yep. you can file a bug against xubuntu-docs in launchpad
[12:01] <slickymaster> knome: will do it then
[12:01] <slickymaster> knome: thanks
[12:02] <knome> np, thanks
[12:12] <slickymaster> knome: just one last question, is https://bugs.launchpad.net/ubuntu/saucy/+source/xubuntu-docs the right place to file the bug?
[12:12] <knome> slickymaster, yep
[12:12] <slickymaster> knome: thanks again ;)
[12:45] <om26er> ubuntu-qa does pause (||) button work for you while on call ?
[12:56] <om26er> rhuddie, the issue that I was facing is bug 1238637
[12:56] <om26er> it happens once unity is restarted
[12:57] <rhuddie> om26er, thanks for the info
[13:26] <phillw> balloons: ping
[13:33] <phillw> knome: would you do me a massive favour, please?
[13:34] <davmor2> om26er: did you get a replay on the pause issue you saw?
[13:34] <om26er> davmor2, that was pause issue, I think.. In the call app
[13:35] <davmor2> om26er: yes did anyone respond to it?
[13:36] <om26er> davmor2, the devs responded. I proposed a branch to disable that button because the feature is not implemented yet
[13:37] <davmor2> ah right no probs then
[14:08] <slickymaster> knome: ping
[14:09] <knome> slickymaster, pong
[14:10] <knome> phillw, tell me
[14:11] <slickymaster> knome: still about what we discuss this morning, do see any issues with me assigning myself to the bug and correct it? there are at least 5 occurrences of that mistake on xubuntu-docs
[14:11] <knome> slickymaster, nope, that's fine
[14:12] <slickymaster> knome: i can get the branch and make the corrections, but I can't upload to the branch. How do I go about that?
[14:12] <knome> slickymaster, send a merge proposal
[14:13] <slickymaster> knome: so there's no problem with pushing it, even though I can not upload to it?
[14:14] <knome> slickymaster, pust to ~yourlpnick/xubuntu-docs/mybranch
[14:14] <knome> slickymaster, then do a merge proposal against lp:xubuntu-docs
[14:15] <elopio> good morning!
[14:16] <slickymaster> knome: your a real savior. I'll do everything this weekend and I'll have the merge proposal ready for review saturday or sunday
[14:16] <slickymaster> knome: thnaks
[14:17] <slickymaster> thanks
[14:18] <knome> slickymaster, *you're ;)
[14:18] <knome> slickymaster, cheers!
[14:18] <knome> morning elopio
[14:19] <elopio> o/
[14:19] <slickymaster> knome: :) you're right, my fingers don't always do what my brain told them to do
[14:27] <slickymaster> knome: sorry for annoying you, but the corrections are made in the xml files residing in the xubuntu-docs/desktop-guide/C/ folder, right?
[14:28] <phillw> knome: would you be so kind as to let the -release team know that the lubuntu alternate images are not on http://iso.qa.ubuntu.com/qatracker/milestones/305/builds
[14:31] <jibel> davmor2, I added a test case to the home scope search bug 1238671
[14:31] <jibel> jfunk, ^ another important bug
[14:31] <knome> phillw, they're available now, i went and activated them
[14:33] <davmor2> jibel: cool thanks
[14:40] <slickymaster> knome: sorry for annoying you, but the corrections are made in the xml files residing in the xubuntu-docs/desktop-guide/C/ folder, right?
[14:42] <davmor2> jibel: http://ubuntuone.com/7K5qnmXlJGBKPuuC27V8sT   and then http://ubuntuone.com/28ZVXDeOvhbf9QWYbgBJyD is what I get so I'd say that is confirmed :)
[14:47] <jibel> davmor2, thank you :)
[15:08] <phillw> knome: thanks!
[15:51] <elopio> ping ubuntu-qa. Somebody with a nexus 7? For gatox, it crashes when opening the launcher.
[15:52] <elopio> it would be nice if somebody can give it a try.
[15:52] <davmor2> elopio: on what image?
[15:53] <elopio> davmor2: yesterday's. He's reflashing.
[15:54] <davmor2> grabbing 93 now
[16:00] <balloons> ping elopio
[16:01] <elopio> balloons: pong.
[16:02] <balloons> elopio, so I found an app that doesn't like to open the toolbar with the swipe action (it doesn't go high enough). However it's a custom toolbar and is still failing because it doesn't respect the .open property
[16:02] <elopio> balloons: I have a branch that swipes to the full high of the toolbar.
[16:02] <elopio> https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/drag_toolbar/+merge/189206
[16:02] <balloons> elopio, ahh nice.. That's what I was going to ask about :-)
[16:03] <elopio> I think it hasn't landed because they disabled the automatic landing.
[16:03] <balloons> lol, it's like you read my mind
[16:04] <elopio> balloons: I have. Tell me another request and I'll give you the URL to the branch in 5 seconds.
[16:12] <cgoldberg> elopio, i have the old Nexus7.. would that help?
[16:17] <davmor2> elopio: pulling the launcher out is fine clicking on it isn't
[16:19]  * robotfuel waves at cgoldberg
[16:20] <cgoldberg> robotfuel, you are on Mir team right?
[16:20] <robotfuel> cgoldberg: yes
[16:21] <cgoldberg> robotfuel, have you heard of any discussions about developing something similar to Xvfb for Mir?  Basically a Mir-VirtualFramebuffer.
[16:21] <cgoldberg> .. or how do you run a Mir test headless?
[16:22] <elopio> cgoldberg: thanks. davmor2 is already on that.
[16:22] <robotfuel> cgoldberg: hmm you might be able to create a surface and run it there. I haven't tried. I will ask about it on monday during the standup.
[16:22] <elopio> thanks davmor2.
[16:23] <robotfuel> cgoldberg: I am sure there is a way to do it.
[16:24] <cgoldberg> robotfuel, great... because Xvfb is a vital tool for testing and CI.  so eventually we need some way to run tests that use Mir without a display.
[16:25] <cgoldberg> robotfuel, I'm also maintainer for a python wrapper for Xvfb... would be cool to do a similar one for Mvfb (the name I'm giving said project :)
[16:36]  * DanChapman waves to balloons o/
[16:36]  * balloons waves back
[16:37] <balloons> DanChapman, did jibel get back to you?
[16:37] <DanChapman> balloons: not yet mate. Not sure if he did after I went, should probably check the logs
[16:38] <balloons> it's a late friday afternoon for him ;-) We can pow-wow on monday
[16:41] <DanChapman> balloons: yeah sounds good to me (Gives me a bit more time to finish my TODO's). Would be good to get it running for release :-)
[16:41] <balloons> Yes, I'd like it to run all week next week so we can see how it does
[16:42] <balloons> i'd like to monitor it as new respins come out, et
[16:42] <balloons> to see if it catches any regressions
[16:43] <DanChapman> balloons: Yeah, will be good to see the output. Whats been the most common regression in the past?
[16:44] <balloons> mm.. I would suspect we might see breakage with the new stuff, aka the new screens
[16:44] <balloons> regressions in the past were the more complex things generally by this time in the cycle. failing to install under specific conditions
[16:44] <balloons> but there are also UI glitches.. I wonder how many we'll catch
[16:48] <DanChapman> well i've found one UI glitch today which i'm looking to see if a bugs been already filed for. When selecting 'something else' and going to the next page the page title briefly displays 'Something else' and then falls back to the page before's title 'Installation type' until you click install now and then it comes back to 'Something else'. Been causing me a right PITA today
[16:51] <balloons> DanChapman, we should keep notes on this.. hmm, ideas on a place/
[16:51] <balloons> DanChapman, perfect example
[16:54] <DanChapman> balloons: well theres already one filed for it. bug 1066152. THe thing is should i be getting the tests to fail on this or skip over it until its fixed?
[16:54] <balloons> DanChapman, right that's kind of the fun thing isn't it
[16:54] <balloons> the tests are failing as they should because of the bug
[16:57] <balloons> DanChapman, I'm wondering if we don't add some try blocks around things and not stop the tests, but simply throw errors..
[16:57] <balloons> I mean the point is we'll have some errors we might find that won't prevent finishing attempting the install
[16:58] <balloons> if we could mark those and still fail the tests, but in theory have it continue to see if more errors can be found
[16:59] <DanChapman> balloons: ok i see what your saying so for minor errors try and hold them back failing until the end
[17:01] <balloons> DanChapman, yea thinking aloud that might be the way to sustainably move forward
[17:01] <balloons> in theory that means we could have several errors occur during the install
[17:02] <balloons> I mean certain errors, like say a screen not being accessible would halt the test, but a bad label shouldn't necessarily do so
[17:02] <balloons> what do you think?
[17:03] <balloons> it's a bit different
[17:03] <balloons> DanChapman, yea I mean you could wrap things and if they fail throw a nice warning and continue. At the end of the test you can fail it if you threw any warnings
[17:05] <DanChapman> Yeah i agree i think things like 'label' values not being correct isn't worthy of of an early fail. I will have a play and see what I can come up with :-)
[17:06] <balloons> awesome.. this just keeps getting more interesting doesn't it?
[17:07] <balloons> DanChapman, btw I've failed to get this going, but if you'd like, fill it in: https://wiki.ubuntu.com/QATeam/AutomatedTesting/ubiquity
[17:07] <DanChapman> balloons: it does indeed :-) Yeah i can add some bits to it
[17:08] <balloons> I want that page to function as a pesudo status page, but mostly as a page to kickstart anyone who wishes to help out
[17:08] <balloons> so if you want to braindump what it would take for someone else to help out, I think that would be good :-)
[17:09] <DanChapman> Yeah sure thing :-)
[17:09] <balloons> DanChapman, right.. the testcase spec you wrote for instance.. perfect spot
[17:10] <balloons> DanChapman, people use it for living specs so to speak, like https://wiki.ubuntu.com/SoftwareUpdates
[17:10] <DanChapman> balloons: cool well I will add as much as I can
[17:11] <balloons> DanChapman, right.. it can stay a gdoc if we wish, but we'll link to it then. Anyways, see how you do. Post release we'll be able to focus on this
[17:37]  * elopio goes to eat.
[18:08] <slickymaster> knome, FYI https://code.launchpad.net/~slickymaster/xubuntu-docs/xubuntu-docs/+merge/190739
[18:29] <JRThump> just got a laptop. having trouble with the touchpad. as soon as I touch the soft(?) button (is it called that, the left mouse button on touchpad) the pointer does not move any longer. why? is this a correct behaviour or a bug? can it be fixed?
[20:04] <phillw> my apologies for earlier, for some reason my 3G device decided to have a fall out with my IRC
[20:05] <elfy> I didn't notice ...
[20:05] <elfy> too much ;)
[20:06] <phillw> I had to hard kill the process, it just kept re-spwaning... I'm hoping it is not a new bug :)
[20:06] <elfy> :)
[20:08] <phillw> elfy: do you know if balloons is about at the present time? There is a bug that is creeping up on the priorities list for the installer...
[20:08] <elfy> not seen him
[20:09]  * balloons hovers, high enough elfy is unable to notice him
[20:10] <phillw> balloons: when you next float down, bug 1220165 needs allocating to someone.
[20:10] <forestpiskie> unfortunately for balloons - forestpiskie sees all
[20:10] <elfy> oh that bug that keeps coming and going
[20:11] <elfy> it isn't just ppc - I saw it in xubuntu a couple of times - didn't read the bug report properly at the time
[20:12] <phillw> elfy: it's one of those bugs that we just ignore and get around. shame on us, as for a newcomer it would scare them to death... :(
[20:12] <balloons> can we isolate when / why it's happening?
[20:12] <balloons> also let's edit it and specify it's not just ppc
[20:12] <phillw> balloons: it does not state ppc only :)
[20:13] <elfy> balloons: let me see what I wrote
[20:13] <balloons> the original description does
[20:13] <phillw> balloons: "Error informing the kernel about modificatons"
[20:13] <balloons> to the extent possible let's try and summarize what's going on
[20:14] <elfy> balloons: the only time I was able to confirm it to myself was when I was overwriting a 64bit with 32bit or a 32bit with a 64bit
[20:14] <phillw> balloons: it is marked against both linux and linux-ppc.
[20:14] <balloons> jsalisbury is asking for some folks to help determine when it started occuring
[20:14] <balloons> he's your guy for getting it fixed :-)
[20:15] <elfy> balloons: I'll see if I can get it to do the same thing tomorrow - I'll be running a bunch of both testcases - so I'll be overwriting each with the other
[20:15] <phillw> lars 1st registered it on the bug date. We had a brief discussion on email before it was filed.
[20:16] <elfy> balloons: if I can replicate it tomorrow I will write a bunch of stuff in the bug description
[20:18] <balloons> elfy, perfect.. ty
[20:18] <balloons> afaict it's on joesph's list, so I don't see the need to do anything further to it
[20:18] <balloons> other than encourage folks to help pinpoint what is going on and when it started ;-)
[20:18] <elfy> yep
[20:19] <phillw> balloons: I can put a call out for our testers, but as psychological thing, having a bug have an 'owner' does encourage people :)
[20:22] <phillw1> I'm hoping it is not a new bug, as my Tor IRC and failbook accounts are not seeing drop outs.
[20:23] <elfy> balloons: can you check out https://code.launchpad.net/~elfy/ubuntu-manual-tests/U1changes
[20:24] <elfy> if that's what you want - I'll look at others that need it doing
[20:24] <balloons> elfy, sure thing.. I see you've got 2 out there
[20:24] <elfy> yea - I thought the resize thing got done - a bit confused
[20:33] <alesage> ubuntu-qa, I'm not able to reproduce this, are you? https://bugs.launchpad.net/indicator-network/+bug/1237951
[20:35] <phillw> soz people, not too sure what is going on with IRC. I've just installed Xchat and will see how that behaves.
[20:37] <phillw> balloons, as I mentioned, would it be possible for jsalisbury to allocate the bug to himself so people know there is someone looking into it.
[20:38] <balloons> phillw, I can't speak for him.. if someone is actively working on it they would assign themselves to it
[20:39] <balloons> at this point it's in a needs more info state
[20:42] <phillw> balloons, in that case, it needs some one to take up the bug and ask the many people who have seen the bug what more information is needed.
[20:43] <phillw> bug reporters report bugs, devs ask us for what extra information is needed. Without being asked, we have no idea what they need.
[20:45] <phillw> It is quite evident as a bug (just from the small number of dupe bugs). It will not "go away" and really does need a bit of tender loving care from a dev who can let us know what and how to get the extra information that is needed for them to squish it.
[20:51] <balloons> phillw, joesph asked on the bug for some information that as far as I can see was not answered
[20:54] <phillw> balloons, the only comment from him is https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1220165/comments/17
[20:54] <phillw> whiich is no where near the comments that brian murray has made.
[20:55] <balloons> phillw, yes afaict it was not answered. regardless the bug needs more information. no one can fix it. lars is already following along the bug and updating it. it needs to be narrowed to something that is reproducble. if we can pinpoint it happens on this kernel but not kernel version x.x, then something can be done
[20:55] <phillw> So, I can answer that question.. we are not sure on what day the bug arrived.
[20:56] <balloons> if you don't know what versions of the kernel it is and is not affecting, not much can be done
[20:56] <phillw> balloons, then we need a method to capture the installer and have a back trace.
[20:57] <phillw> I have seen it on different kernel releases. the error is reported by Ubiquity; so it knows the error is there.
[21:00] <phillw> So, how you launch gdb on a clean system and then run the ISO installer? answer that and we'll give a backtrace :)
[21:11] <balloons> https://wiki.ubuntu.com/DebuggingUbiquity
[21:13] <phillw> balloons, I'll add it to the bug report, at least then people have a reference to look to. (I'll refrain at stating my thoughts as to why the link had not earlier been added to the bug... ::SIGH:: )
[21:14] <balloons> ubiquity -d is your friend
[21:14] <balloons> things to learn
[21:14] <knome> oi balloons
[21:14] <balloons> oi oi
[21:15] <elfy> evening boss
[21:15] <phillw> balloons, on what part of https://wiki.ubuntu.com/Testing/Activities is that? I could not find it.
[21:20] <phillw> balloons, as I have no idea of how to PM with X-chat, would you pop into ##phillw for a quick chat?
[21:21] <knome> phillw, /query balloons
[21:22] <balloons> elfy, re: https://code.launchpad.net/~elfy/ubuntu-manual-tests/U1changes/+merge/189794
[21:22] <balloons> does this make sense? If Ubuntu One setup is available in your FAMILY
[21:23] <elfy> it does to me
[21:23] <elfy> but only because I'm under the impression FAMILY is supposed to do something :)
[21:23] <balloons> it will say xubuntu right there for instance
[21:24] <elfy> except I have never actually seen it do that - everytime I see a testcase it just says FAMILY
[21:25] <elfy> balloons: If Ubuntu One setup is available complete the next step, otherwise ...
[21:27] <balloons> elfy, I updated the mp a little
[21:28] <elfy> ok - I'll look later tomorrow - beginning to fray at the edges here a bit now
[21:29] <elfy> not likely to get any of this done before the 17th anyway
[21:29] <elfy> balloons: thanks
[21:29] <balloons> right
[21:29]  * balloons brain is also shot
[21:30] <elfy> lol
[21:30] <balloons> elfy, this is good to go
[21:30] <balloons> https://code.launchpad.net/~elfy/ubuntu-manual-tests/resizechange/+merge/189668
[21:30] <elfy> ok
[21:30] <balloons> is there more needing changed, or we good/
[21:30] <balloons> ?
[21:30] <elfy> that was it for that
[21:31] <elfy> so that's 2 of those bugs done then
[21:32] <elfy> balloons: I'll look at the U1 stuff over the weekend hopefully and ping you on Monday
[21:33] <balloons> sounds great :-)
[21:33] <balloons> many thanks elfy
[21:35] <elfy> balloons: no problem - I'm filing these things away under 'bribes for Nick when I need them' :p
[21:35] <robotfuel> alesage: ping
[21:35] <alesage> whola robotfuel
[21:36] <balloons> elfy, haha!
[21:37] <robotfuel> alesage: have you noticed if you open an indicators and the system settings for the same indicator getting out of sync?
[21:37] <alesage> robotfuel, describe out of sync?
[21:37] <robotfuel> alesage: it  looks like if you use the indicator, then use the system settings page, then use the indicator the system settings page doesn't update to the new setting
[21:38] <robotfuel> alesage: the battery slider is the one I am using
[21:38] <robotfuel> alesage: wifi has the same issue (it's on the same page)
[21:39] <alesage> robotfuel which is laggy? settings or indicator?
[21:39] <robotfuel> alesage: the settings page doesn't update, the indicator is always correct
[21:39] <alesage> robotfuel, aha settings can be laggy, good one :)
[21:39] <alesage> robotfuel, I assume only b/c in the indicator has to render, e.g.
[21:40] <alesage> robotfuel, want to file, or should I?
[21:40] <robotfuel> alesage: I will file it
[21:40] <alesage> robotfuel, ok ping and I'll confirm
[21:54] <robotfuel> alesage:https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1238985
[21:54] <alesage> robotfuel, thx
[21:55] <robotfuel> alesage: do you know who can triage and assign the bug?
[21:56] <alesage> robotfuel, I'll add some tags and I'm sure seb128 will see it
[21:58] <alesage> thanks robotfuel