[05:33] <yaboo> how can I force the screen resolution in 11.10 desktop
[05:34] <yaboo> seems it tries to do 1600x1200 when my monitor only does 1280x1024 res
[06:07] <BigWhale> Good Morning.
[09:11] <pitti> Good morning
[09:29] <pitti> dobey: not sure whether someone already told you, but the distro uploading question was resolved with jasoncwarner_/rickspencer3; so it's fine to continue what we have always done, i. e. you can upload
[09:30] <rickspencer3> pitti, dobey of course with the caveat that the distro acceptance tests were run and passed!
[09:30] <rickspencer3> :)
[09:30] <pitti> sure; I checked the policy, and it doesn't say "canonical platform team", just "distro"
[09:30] <pitti> as distro == ubuntu developers, you as an uploader are responsible for the distro side
[09:31] <pitti> the AC still applies, of course
[09:34] <micahg> dobey: and since that was resolved, if you still want a U1 packageset, the DMB is open to it
[09:41] <TheMuso`> /c/c
[09:49] <nerochiaro> Kaleo: (and Saviq): I updated the list of tasks in https://wiki.ubuntu.com/UbuntuTV/MergePlan, and i'm starting to go through it in order. Pleae confirm you're ok with it when you have time.
[10:14] <mpt> mvo, hi, I have a work item to "[mpt] Invite people to port release-upgrader to aptdaemon"
[10:14] <mpt> mvo, would you have a few minutes to tell me what I need to know to write something informative? :-)
[10:20] <lool> Hey
[10:21] <lool> New rhythmbox has file conflicts with -plugins on upgrades
[10:21] <lool>  tentative de remplacement de « /usr/share/rhythmbox/plugins/artdisplay/rhythmbox-missing-artwork.svg », qui appartient aussi au paquet rhythmbox 2.90.1~20111126.89c872b0-0ubuntu3
[10:27] <mpt> and speaking of broken upgrades...
[10:28] <mpt> kenvandine, seb128: I have a work item to "Specify how unity and other critical packages shouldn't be removed by an update". The idea is that we'd have a list of packages where, if the an update wants to remove it, Update Manager would know the update is broken. Does that seem like a good idea to you?
[10:29] <seb128> lool, hey, seems a  buggy replaces in ricotz's update, do you want to add the replaces? I can try to have a look later, at a the platform rally and in a meeting atm though
[10:39] <seb128> mpt, don't we do that with what ubunt-desktop depends on already?
[10:41] <mpt> mvo, does update-manager do anything special if an update would remove ubuntu-desktop?
[10:42] <lool> seb128: The bzr branch seems out of date; missing push?
[10:42] <lool> (I mean at lp:~ubuntu-desktop/rhythmbox/ubuntu)
[10:42] <seb128> lool, done, sorry about that
[10:42] <seb128> ups
[10:45] <seb128> lool, ok, fixed, please check I didn't screw, I was missing a revision when I sponsored the update yesterday
[10:46] <seb128> so pulled, fixed the conflict and push, should be ok
[10:50] <lool> seb128: ok
[10:50] <seb128> lool, thanks
[11:02] <lool> uploaded
[12:49] <BigWhale> what's up with the build farm? It'll take nine more hours for my packages to build? :'(
[12:59] <cyphermox> BigWhale: backlog appears to be disappearing slowly now
[13:14] <seiflotfy> kenvandine: how safe is it to update to precise
[13:14] <seiflotfy> ?
[13:15] <pitti> seiflotfy: no known major breakages today; you might run into a rhythmbox file conflict if your mirror is slightly behind
[13:16] <pitti> but another run of dist-upgrade will sort that out
[13:16] <pitti> and update-manager just ignores these anyway
[13:16] <seiflotfy> pitti so on an x201 it should be ok?
[13:16] <pitti> seiflotfy: yes, I've used precise on this since day 1
[13:16] <seiflotfy> u on an x201 too ?
[13:16] <kenvandine> seiflotfy, should be safe
[13:17] <seiflotfy> how is the battery issue?
[13:17] <seiflotfy> is it covered now
[13:17] <seiflotfy> my last ubuntu caused me a whole new battery
[13:17] <seiflotfy> it was draining like crazy
[13:18] <pitti> seiflotfy: yes, I have an x201 (Arrandale)
[13:18] <pitti> seiflotfy: "issue"?
[13:18] <pitti> seiflotfy: I've run natty, oneriric, and precise on this box without an issue
[13:18] <seiflotfy> well somehow power consumption wiht the last kernel was terrible
[13:18] <pitti> in the train I got 9 W (11.5 hours)
[13:19] <seiflotfy> ok i just got me a new battery today
[13:19] <seiflotfy> 9 cells
[13:19] <seiflotfy> and
[13:19] <seiflotfy> 6 hours and 11 minute
[13:19] <seiflotfy> not bad
[13:19] <seiflotfy> but i need more
[13:20] <seiflotfy> :P
[13:20] <pitti> seiflotfy: well, my 11 hours is with wifi killswitch and 50% brightness
[13:20] <pitti> with wifi I only get 8 h
[13:22] <seiflotfy1> do have anything in you rc.local settings?
[13:22] <pitti> no, stock ubuntu install
[13:23] <seiflotfy1> seriously ?
[13:23] <seiflotfy1> ok wow
[13:23] <seiflotfy1> let me install precise then
[13:23] <pitti> seiflotfy1: you might want to check powertop what's draining your bat
[13:23] <pitti> seiflotfy1: wasn't much different in oneiric/natty, though
[13:23] <pitti> 10W with wifi and reasonably active, 8W with killswitch and idle
[13:23] <seiflotfy1> and precise?
[13:23] <pitti> same
[13:23] <seiflotfy1> hmmmmmm
[13:23] <pitti> I think precise is a tad better
[13:24] <pitti> I didn't keep exact records
[13:24] <pitti> and of course it's hard to reproduce workloads exactly over several hours
[13:24] <pitti> seiflotfy1: powertop is pretty good to debug rogue processes or devices
[13:24] <seiflotfy1> http://www.omgubuntu.co.uk/2011/11/linux-power-regression-overheating-problem-on-thinkpad-fixed/
[14:12] <dobey> pitti: thanks
[14:49] <mvo> mpt: sorry, I didn't manage to respond to the aptdaemon question yet, I will try to get it later today
[14:50] <mpt> mvo, I wasn't sure whether you saw my other question too: <mpt> mvo, does update-manager do anything special if an update would remove ubuntu-desktop?
[14:54] <desrt> pitti: http://paste.ubuntu.com/800630/
[14:56] <mpt> mvo, those questions might be quicker to answer on Mumble
[14:56] <pitti> desrt: pushed
[14:57] <mvo> mpt:  I have a real-life meeting in 5min :/ - I have not seen this question, but the anser is that if that happens it will fail hard and refuse to upgradde
[14:57] <desrt> pitti: thanks
[14:58] <mpt> mvo, how can I test how update-manager presents that failure?
[14:58] <mpt> (Does it put up an error message?)
[15:03] <mvo> mpt: hm, i don't think there is a really easy way, but its the generic: http://paste.ubuntu.com/800640/
[15:03] <mvo> message
[15:05] <mpt> thanks mvo, I'll tweak that text
[15:08] <mvo> thanks!
[15:53] <ricotz> cyphermox, hello
[15:54] <ricotz> cyphermox, are there known issues with nm with probing wired interfaces which arent connected?
[16:02] <cyphermox> nm probing wired interfaces which are not connected?
[16:03] <cyphermox> ricotz: not that I know of. If you're mentioning some errors in dmesg about speed/duplex, I investigated that yesterday
[16:03] <cyphermox> I'm not *certain* it's not NM, but reasonably sure since NM listens for netlink messages to know when there is carrier
[16:04] <pitti> chrisccoulson: git://gitorious.org/performance-scripts/mainline.git
[16:05] <nessita> hello all! quick scream for help: the precise fresh installation in my laptop is stuck in "removing conflicting operating system files..." any idea what should I do?
[16:05] <pitti> chrisccoulson: http://people.gnome.org/~federico/news-2006-03.html#timeline-tools
[16:12] <ricotz> cyphermox, i mean nm seems to try to connect while is there no cable plugged in and doenst give up trying
[16:13] <cyphermox> ricotz: I'll need much more information than that -- please file a bug (ubuntu-bug network-manager) and include syslog, and the output of 'ethtool <interface>'
[16:14] <cyphermox> ricotz: I'm thinking that might be something device-specific, maybe some carrier-detection pieces got broken
[16:15] <ricotz> cyphermox, i will try to get some better information, thanks
[16:15] <cyphermox> thanks!
[16:15] <ricotz> btw the driver is skge
[16:15] <cyphermox> yeah.. one funky one or something :)
[16:15] <cyphermox> ethtool will probably be the key
[17:35] <pitti> good night everyone
[18:18] <cyphermox> pitti: oops. there's https://bugzilla.gnome.org/show_bug.cgi?id=638117 that specifically mentions not saving the state in gnome-bluetooth
[18:18] <ubot2`> Gnome bug 638117 in general "Remember off/on state between sessions" [Normal,Unconfirmed]
[18:19] <cyphermox> guess there's a way to fix this in bluez though; the init script or upstart job could save the state on shutdown, kind of like alsa does
[19:17] <broder> anybody around? i'm looking at bug #631638. it sounds like upstream is unlikely to pick this up in time for precise, so it seems like it would make sense for us to pick up the patch...
[19:17] <ubot2`> Launchpad bug 631638 in hundredpapercuts "palimpsest thinks that USB2 is 480MB/s instead of 480Mb/s" [Undecided,In progress] https://launchpad.net/bugs/631638
[19:49] <jbicha> broder: yes we should definitely take that patch for precise
[19:49] <broder> jbicha: ok, cool. i'll put something together
[19:51] <broder> or rather, i'll have one of the people at this bug jam with me put something together :)
[19:52] <cyphermox> \o/
[19:59] <oakdog8> steve holt
[20:14] <dobey> where the heck is the shotwell irc channel?
[20:15] <dobey> or yorba or whatever
[20:17] <bil21al> shotwell developers see those bugs by themself in launchpad ubuntu
[20:18] <bil21al> i guess no need to upstream
[20:18] <bil21al> and i dont know any channel
[20:21] <dobey> bil21al: i don't want to upstream a bug, i want to bug developers with questions
[20:21] <dobey> and i hate mailing lists
[20:22] <bil21al> hmmm  ask seb128 he may be know that oe brain murray in ubuntu bugs channel somebody there must knew about that
[20:53] <dobey> kenvandine: are you around, or at the pub?
[20:53] <kenvandine> dobey, i am around, but still working a bit heads down
[20:53]  * kenvandine should be at the pub :)
[20:54] <dobey> kenvandine: heh. i was just wondering what the plan was to get gwibber to stop using python-webkit for precise :)
[20:54] <kenvandine> dobey, stop hanging out with seb128 :)
[20:54] <kenvandine> he asks me everyday :)
[20:54] <dobey> lol
[20:54] <kenvandine> no plan right now... we need to rewrite the accounts UI
[20:55] <kenvandine> and i have no time for it right now
[20:55] <dobey> kenvandine: well, i'm poking about to find room for pyqt; and you, shotwell, and u1 are the only things that depend on gtk2 webkit still
[20:55] <dobey> the accounts ui is all python right?
[20:55] <kenvandine> dobey, shotwell doesn't anymore:)
[20:55] <kenvandine> yes
[20:55] <kenvandine> don'g say pygi
[20:55] <kenvandine> don't
[20:55] <dobey> kenvandine: well, trunk doesn't. but shotwell in precise still does. there isn't a relase of gtk3 shotwell yet afaict
[20:56] <kenvandine> yes there is
[20:56] <kenvandine> was uploaded today :)
[20:56] <dobey> oh
[20:56] <dobey> well hooray then
[20:56] <kenvandine> yup
[20:56] <kenvandine> :-D
[20:56] <dobey> so gwibber ;)
[20:57] <kenvandine> dobey, shhhhh
[20:57] <kenvandine> it would be hard to use pygi, i think
[20:58] <kenvandine> the accounts dialog does some python import muckery to inject python files from other places
[20:58] <kenvandine> i am sure it would introduce problems
[20:58] <kenvandine> well... s/sure/afraid/
[20:58] <dobey> ugh, lots of stuff uses pygtk, not just accounts :-/
[20:58] <kenvandine> nope
[20:59] <kenvandine> not in gwibber
[20:59] <kenvandine> not that we still use
[20:59] <kenvandine> there is some files that can be removed
[20:59] <dobey> oh
[20:59] <dobey> there is junk in trunk, that shouldn't be there
[20:59] <kenvandine> yes
[20:59] <dobey> that confuses grep :)
[20:59] <kenvandine> gwibber/microblog/plugins/*/gtk/*/
[20:59] <kenvandine> and gwibber/accounts.py
[20:59] <kenvandine> should be all we have that we care about
[21:00] <kenvandine> and there is gwibber-service-{sina,sohu} which are in separate projects
[21:00] <dobey> ok
[21:00] <kenvandine> but provide accounts files
[21:00] <dobey> what projects? same name?
[21:02] <dobey> well i guess they don't use webkit, otherwise they'd show up in rdepends
[21:03] <dobey> kenvandine: oh, new shotwell is in depwait for new valac
[21:04] <BigWhale> kenvandine!!
[21:04] <dobey> weird
[21:05] <dobey> since vala-0.16 was uploaded 8 days ago
[21:05] <BigWhale> kenvandine, there was this guy who's name was JamesT and he wanted to run Gwibber on Net BSD!
[21:05] <kenvandine> wow
[21:05] <BigWhale> (he wasn't really a jamesT ... but ... )
[21:05] <kenvandine> dobey, it is probably in universe
[21:06] <kenvandine> and shotwell is in main
[21:06] <dobey> kenvandine: ah, it is in universe
[21:08] <kenvandine> BigWhale,  i made a huge improvement to gwibber-service's power consumption and CPU usage today
[21:08] <BigWhale> awesome!
[21:08] <BigWhale> people will be happy
[21:08] <kenvandine> dobey, i finally was able to get rid of threading.Thread in gwibber :)
[21:08] <dobey> heh
[21:09] <dobey> multiprocessing too?
[21:09] <kenvandine> python multiprocessing.Pool was causing constant polling looking for jobs to do even when idle
[21:09] <kenvandine> so eating up power
[21:09] <dobey> i bet
[21:09] <kenvandine> dobey, no.... i wish
[21:09] <dobey> i can't wait to get the new twisted in
[21:09] <kenvandine> but i couldn't close the pool when it was run in the thread
[21:09] <dobey> hopefully my reactor will get approved/landed soon
[21:10] <kenvandine> so getting that shit untangled i was able to close the pool down after finishing operations
[21:10] <BigWhale> kenvandine, threading in python is horrible :/
[21:10] <kenvandine> yeah
[21:10] <kenvandine> which fixed the power problem... and a nice side effect is refreshes are now quite a bit faster
[21:10] <kenvandine> and use very little CPU
[21:10] <BigWhale> I have to start hacking on gwibber again ...
[21:11] <kenvandine> i went from 100% cpu usage for ~20s to spiking at 14% over the course of ~10s
[21:11] <kenvandine> and most of that 10s is under 10%
[21:11] <kenvandine> it is in ppa:unity-team/ppa if anyone wants to help test it :)
[21:11] <BigWhale> I am mostly finished with Kazam, just few minor things left ...
[21:11] <kenvandine> along with all the new unity crack and gwibber ported to the new APIs :)
[21:13] <dobey> does compiz no longer wake up 60 times a second with the new unity? :)
[21:14] <kenvandine> no idea
[21:15] <kenvandine> but i know half of the top 12 power hog bugs in precise have been fixed this week
[21:17] <dobey> the big one in u1 is fixed upstream
[21:17] <kenvandine> gwibber-service was causing 7% of the wake ups on a clean install
[21:18] <kenvandine> bug 906916
[21:18] <ubot2`> Launchpad bug 906916 in gwibber "gwibber-service has a child that polls at 10Hz which is causing a lot of wakeup events" [High,Triaged] https://launchpad.net/bugs/906916
[21:18] <dobey> does it run even if not using gwibber?
[21:18] <dobey> or only after you add accounts?
[21:19] <kenvandine> i think even if you have no accounts
[21:19] <dobey> yeah, that's bad :)
[21:19] <kenvandine> i had tried fixing the multiprocessing stuff in the past, but it kept causing more problems... i hit the sweet spot today :)
[21:20] <kenvandine> mixing threading and multiprocessing sucked
[21:20] <dobey> yeah
[21:21] <dobey> as soon as i looked at that code when the couchdb/keyring issues came up, i was thoroughly appalled
[21:21] <kenvandine> yeah... your patch didn't work though :)
[21:21] <dobey> it did work, just didn't fix *all* the cases :-/
[21:21] <kenvandine> well, it fixed some problems and caused others
[21:21] <kenvandine> it was just a mess
[21:22] <dobey> s/caused/exposed/ :)
[21:22] <kenvandine> indeed
[21:22] <dobey> but things are much better now it souns like
[21:22] <kenvandine> yup!
[21:22] <dobey> sounds even; this keyboard is picky sometimes
[21:22] <kenvandine> :)
[21:23] <kenvandine> i need quite a bit of testing though
[21:23] <kenvandine> that code scares me
[21:23] <dobey> heh
[21:24] <kenvandine> you guys need to try the crack in the ppa :)
[21:24] <dobey> i need to upgrade my workstation to precise
[21:24] <dobey> then i can just ignore the fact that gtk 3.2 is apparently broken somewhere
[21:25] <BigWhale> who is responsible for getting software into universe?
[21:25] <dobey> since gtk in precise 'just works' where i'm hitting that brokenness
[21:25] <dobey> BigWhale: anyone with permissions to do so
[21:26] <dobey> BigWhale: motu and core devs all have the power
[21:26] <dobey> or powah, if you prefer
[21:26] <BigWhale> the force, please ...
[21:26] <kenvandine> BigWhale, i could
[21:26] <BigWhale> :>
[21:27] <BigWhale> kenvandine, ahh someone I know! ;)
[21:27] <kenvandine> although i am kind of drowning in work atm
[21:27] <dobey> kenvandine: popey keeps posting pictures of beer on g+ :(
[21:27] <kenvandine> you could create a package and i'll review it :)
[21:27] <BigWhale> kenvandine, well first I'll need few pointers on what still needs to be done
[21:27] <kenvandine> dobey, there has been plenty of beer :)
[21:28] <kenvandine> although i spent last night and tonight working late :(
[21:28] <BigWhale> kenvandine, well there's no real rush, except that I'd like to get it into precise :)
[21:28] <kenvandine> pile of new releases and crap to deal with
[21:28] <dobey> i'm sure there has been
[21:28] <kenvandine> i love it when there is an abi break that requires a bunch of rebuilds
[21:29] <BigWhale> are you guys occupying that bar on the street? :))
[21:29] <kenvandine> and i love api breaks even more where i have to do last might porting
[21:29] <kenvandine> BigWhale, most of the time :)
[21:29] <dobey> kenvandine: i am totally about to break some API :)
[21:29]  * kenvandine smacks dobey
[21:29] <kenvandine> didrocks had me update from a PPA which broke gwibber... forced me to port the lens :)
[21:30] <dobey> kenvandine: do you not want a fast gtk3 version of u1ms? :)
[21:30] <Sarvatt> dobey: the compiz 60 wakeups a second can be worked around by drm.vblankoffdelay=1 if you're on intel
[21:30] <Sarvatt> kernel command line parameter ya can add to grub
[21:30] <kenvandine> dobey, well yes :)
[21:30] <kenvandine> dobey, sometimes it's worth it :)
[21:30] <kenvandine> the libdee api break was totally worth it
[21:31] <kenvandine> huge performance fixes that speeds up unity and gwibber :)
[21:34] <dobey> so dropping libwebkitgtk-1.0-0 off the CD will get us about 7 MB back
[21:35] <kenvandine> woot
[21:35] <Sarvatt> dobey: a unity update wouldn't fix that though, its a kernel problem where vblank interrupts aren't turned off for 5000ms after they are used so you get your refresh rate number of wakeups per second pretty much always. that might be fixed in the 3.3 kernel, but only on intel where vblank interrupts are reliable, or you can add the kernel command line option to work around it without a newer kernel
[21:38] <dobey> Sarvatt: well, a backport of that fix to 3.2 kernel would be fine as well. doesn't have to be a unity or compiz update if the bug is elsewhere. kernel update is fine :)
[21:39] <Sarvatt> maybe post 12.04 release when it actually goes in :)
[21:42] <Sarvatt> in the meantime GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.vblankoffdelay=1" in /etc/default/grub would help if you want to save power, its a seriously small amount though
[21:42] <Sarvatt> like less than 2%, cking on the kernel team did some exact measurements
[21:42] <dobey> Sarvatt: i don't think gaining an extra hour is a "seriously small amount"
[21:43] <Sarvatt> no reducing the 60 wakeups a second from compiz wont give you an extra hour by any stretch of the imagination
[21:43] <Sarvatt> let me dig up ckings power measurement posts on the lists
[21:44] <dobey> Sarvatt: the battery icon's estimated time remaining increased by an hour on my laptop, simply by switching off of unity to fallback gnome, and turing off ubuntuone-syncdaemon (which has 10 wakeups/sec)
[21:44] <Sarvatt> http://mid.gmane.org/4F05A844.6000707@canonical.com
[21:44] <jbicha> dobey: we should totally switch to gnome fallback for precise then! :)
[21:45] <Sarvatt> syncdaemon is keeping the hdd alive afaik, its very different and cant just compare the wakeups
[21:45] <dobey> no it isn't
[21:45] <dobey> it only hits the hdd at most once every 2 minutes, if not actively doing anything
[21:46] <Sarvatt> its touching a log file which is keeping the hdd spun up I mean
[21:46] <Sarvatt> i could be wrong, still digging
[21:46] <dobey> 30 times per hour, yes
[21:46] <dobey> not 10 times per second
[21:46] <Sarvatt> all of his results were here http://zinc.canonical.com/~cking/power-benchmarking/
[21:46] <Sarvatt> he filed that gwibber bug
[21:47] <dobey> yes, he filed a bug or two against u1 as well
[21:53] <dobey> this laptop sucks for power anyway :-/
[22:41] <Stebalien> Can somebody look at this merge proposal and check it for mistakes: https://code.launchpad.net/~stebalien/gnome-disk-utility/fix-units/+merge/88283
[22:56] <dobey> man gsettings is annoying :(
[23:17] <dobey> kenvandine: so, i just changed the color for my twitter account, in gtk3 ;)
[23:18] <dobey> anyway, i need to write this e-mail, and call it a day for sure
[23:18] <kenvandine> dobey, what do you mean in gtk3?
[23:18] <dobey> kenvandine: pygi
[23:18] <dobey> in a branch
[23:18] <kenvandine> oh... do you mean actually loading the accounts panel for the twitter account?
[23:18] <kenvandine> woot!
[23:18] <dobey> yes :)
[23:19] <kenvandine> dobey, you are my hero!
[23:19] <dobey> it still needs some fixes and testing, but i got pretty far already
[23:19] <dobey> and there doesn't seem to be a gnomekeyring gir
[23:19] <kenvandine> push that before it gets lost :)
[23:19] <kenvandine> ugh!
[23:19] <dobey> but maybe we can use txsecrets from ubuntu-sso-client
[23:20] <dobey> which just talks to keyring directly over dbus :)
[23:20] <dobey> so works with any keyring that implements fd.o secrets api
[23:46] <dobey> later, need to not hack for a while :)
[23:57] <BigWhale> Sleepy time for me too