[12:51] <BluesKaj> Hey folks
[18:33] <Tuxist> i have repacked jack so that not conflict with pipewire https://launchpad.net/~jan-koester/+archive/ubuntu/pipewiremaster
[18:33] <Tuxist> now i'am working on pulseaudio
[20:25]  * mamarley kicks LP
[20:25] <mamarley> Looks like the build farm fell over again…


[06:59] <pitti> Good morning
[06:59] <pitti> hi asac
[07:00] <pitti> robert_ancell: I saw the "enter" bug in gdm, can reproduce
[07:31] <didrocks> good morning
[07:31] <pitti> bonjour didrocks
[07:31] <didrocks> Guten Morgen pitti, how are you?
[07:35] <pitti> I'm great, thanks!
[07:36] <pitti> I need to leave for ~ 3 hours for an appointment
[07:36] <pitti> see you later
[07:40] <didrocks> pitti: see you!
[08:49] <mvo> hey, could someone running natty please let me know if http://pastebin.com/dgwVq9ap work? i.e. if clicking on the url produces the print message. it dosn't on my system, but seems to be super strange
[08:55] <didrocks> mvo: clicking on the url doesn't print anything on the terminal
[08:55] <didrocks> hey mvo
[08:56] <mvo> didrocks: thanks! meh, that works just fine in maverick and should according to the docs, I looked over the pygtk debdiff but the changes there look like they can not cause anything like this
[08:56] <mvo> didrocks: at least I know I'm not crazy :)
[08:57] <didrocks> mvo: hehe, happy to keep you in a certain sanity ;)
[09:13] <rodrigo_> morning
[09:14] <mvo> hey seb128, good morning :) I have a bug for you - bug #687732
[09:14] <ubot2> Launchpad bug 687732 in pygtk (Ubuntu) "gtk.Label <a href> link-activate signal broken in natty (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/687732
[09:14] <didrocks> morning rodrigo_
[09:14] <mvo> seb128: have you seen anything like tihs?
[09:14] <mvo> hey rodrigo_
[09:14] <didrocks> mvo: waow, you are quick to open a bug and ping people :)
[09:15] <rodrigo_> hi didrocks, mvo
[09:15] <mvo> didrocks: it blocks me! well, a bit :) I added search suggestions to software-center, i.e. if you mispell didrocks, it will ask you if you meant ditrack
[09:15] <seb128> hello mvo
[09:15] <seb128> hey rodrigo_, rickspencer3_
[09:15] <mvo> didrocks: keyboard navigation works, so its not terrible
[09:16] <didrocks> mvo: oh nice for search suggestions :)
[09:16] <mvo> didrocks: yeah, it works quite well - except that you can't click on them ;)
[09:17] <mvo> but yeah, I should let the matter rest a bit and work on something else in the meantime
[09:17] <seb128> mvo, confirmed, and it's a bug in GTK
[09:17] <seb128> mvo, you get the same issue in the gedit about dialog for example
[09:17] <mvo> ha!!!! itz compiz (it seems)
[09:17] <mvo> I just switched to metacity and there it works
[09:18] <seb128> didrocks!
[09:18]  * mvo shakes his fist
[09:18] <didrocks> what what? ;)
[09:18] <mvo> dear compiz, mouse events are mine, kthxbye!
[09:19] <didrocks> mvo: can you open a bug, set it high and assign to smspillaz ? :)
[09:19] <Laney> jcastro: MIR: yes afaik. Don't know how to make it happen...
[09:19] <seb128> hey, let's blame it on smspillaz
[09:20] <Laney> seb128: gnome# and mono-addins: After squeeze or when something needs it
[09:20] <Laney> wouldn't worry about those two
[09:20] <seb128> Laney, I'm basically trying to clean the versions list
[09:20] <Laney> yeah I thought as much
[09:22] <seb128> mvo, I guess reassign the bug from pygtk to compiz
[09:22] <seb128> then assign to smspillaz
[09:23] <seb128> Laney, what are the mir you are waiting on?
[09:23] <Laney> banshee banshee-community-extensions
[09:23] <Laney> and deps
[09:23] <seb128> ok, I will try to unblock that
[09:24] <seb128> didrocks, softwares not working in appmenu are bugs there usually
[09:24] <seb128> not in the software
[09:24] <Laney> thanks
[09:24] <seb128> especially if the said software is using gtk
[09:25] <didrocks> seb128: oh really? I thought it wasn't based on gtk as I didn't use it, sorry my bad, fixing
[09:25] <rodrigo_> hmm, I can't use the mouse / keyboard on gdm after a full upgrade
[09:26] <seb128> didrocks, I didn't say acroread is based on GTK
[09:26] <didrocks> seb128: fort those not based on GTK, we workarounded it in the package by not exporting the variabla
[09:26] <seb128> didrocks, though apt-cache seems to indicate it is
[09:26] <didrocks> variable
[09:27] <seb128> didrocks, well, I'm not sure why non GTK softwares should get any change
[09:27] <seb128> since we patch GTK
[09:27] <seb128> we don't patch ie motif to behave differently
[09:27] <seb128> so softwares out of GTK and Qt should not care about what to do GTK
[09:28] <seb128> not sure what I say makes sense ;-)
[09:28] <seb128> I know we filter out firefox but that seems rather a workaround to a bug in appmenu as well
[09:28] <didrocks> seb128: I agree on the principle :-) I just saw that we removed the env variable in the desktop files in those case
[09:28] <mvo> seb128, didrocks: reassigned and assigned - thanks
[09:28] <seb128> mvo, thanks!
[09:28] <didrocks> mvo: thanks :)
[09:29] <didrocks> seb128: then, I don't really care if the blacklist is in appmenu or in the desktop file app package :)
[09:29] <rodrigo_> seb128, btw, already fixed the 'needs-fixing' in https://code.launchpad.net/~rodrigo-moya/ubuntu/natty/gnome-control-center/2_91_3_release/+merge/42134
[09:29] <didrocks> seb128: just tell me where you want me to assign to :)
[09:30] <seb128> didrocks, let it there for now, I'm pretty sure the acroread is a duplicate one anyway ;-)
[09:30] <didrocks> probably, yeah :)
[09:30] <seb128> bug #664647
[09:30] <ubot2> Launchpad bug 664647 in indicator-appmenu (Ubuntu) (and 1 other project) "acroread menu captions not transfered (affects: 3) (heat: 97)" [High,Confirmed] https://launchpad.net/bugs/664647
[09:30] <seb128> didrocks, ^ if you want to dup it
[09:30] <didrocks> ok
[09:30] <didrocks> thanks :)
[09:30] <seb128> rodrigo_, sorry I forgot about this one, I will sponsor the pending merge requests today
[09:31] <rodrigo_> seb128, no problem, and thanks :)
[09:31] <seb128> Laney, well, seems robert_ancell did the gnome# update this night
[09:31] <seb128> Laney, which solves the issue of knowing if debian will do it or not I guess
[09:32] <Laney> err, alright
[09:44] <seb128> didrocks, you will get compiz or unity updates out today?
[09:44] <didrocks> seb128: unity for sure, compiz not sure
[09:45] <didrocks> seb128: there is not a lot of "hard focus" fixes for us
[09:45] <didrocks> like the gnome-panel crash, no progress on the menu still not working with the fix
[09:45] <seb128> I want compiz to not block my sessions for 15 seconds when closing one!
[09:46] <seb128> when do you think that fix will land?
[09:46] <seb128> ;-)
[09:47] <didrocks> seb128: this fix can land, but it needs to rebuild everything and the pending fix on gnome-panel crash can have another abi bump. I wanted to avoid two abi bumps in a row :)
[09:49] <seb128> didrocks, the session saving is an abi break?!
[09:49] <seb128> hum, k
[09:49] <seb128> compiz sucks :p
[09:49] <seb128> weird that such details impact the abi
[09:50] <didrocks> seb128: not the session saving particularly, but I think we are more in a point that we want to make dist than cherry-pick patches
[09:51] <seb128> didrocks, ok, with some luck those bugs will be fixed before your holidays
[09:51] <seb128> I've the feeling we will get that broken session thing for another 3 weeks :-(
[09:51] <didrocks> seb128: if there is still nothing new, I'll definitively upload a make dist on Monday
[09:51] <didrocks> at least, that's my plan :)
[09:51] <seb128> ok great
[09:51] <seb128> thanks
[09:56] <rickspencer3_> hi seb128, and everyone
[09:56] <seb128> hey rickspencer3_
[09:59] <didrocks> hi rickspencer3_
[09:59] <rickspencer3_> hey didrocks
[09:59]  * rickspencer3_ is learning mago
[10:00] <seb128> rickspencer3_, as an user? ie writting test cases?
[10:00] <rickspencer3_> seb128, correct, writing test cases
[10:00] <rickspencer3_> working on shotwell atm
[10:00] <seb128> great ;-)
[10:01] <rickspencer3_> it's a bit different than other test frameworks I've used, so a bit of ramp up
[10:01] <rickspencer3_> and have to learn a bit of python-ldtp too
[10:02] <seb128> ok
[10:03]  * seb128 kicks firefox
[10:03] <seb128> you stupid browser!
[10:04]  * didrocks gives seb128 a chromium :)
[10:04] <seb128> don't close the download dialog and then the main ui while downloading
[10:04] <seb128> the stupid thing exited while I was downloading a CD iso and didn't resume it on next start but started again
[10:04] <rickspencer3_> seb128, and don't close the main window and not the download dialog, or you can't open the main window with the unity launcher
[10:05] <mvo> rickspencer3_: nice! tbh I found the additional xml file to be a bit redundant (ie description can simply be python docstrings and a conversation like in unittest for what to run). but maybe I just looked close enough into it :)
[10:05] <rickspencer3_> mvo, right
[10:05] <seb128> do we have a nice tutorial on how to use mago?
[10:06] <mvo> but seeing the current acitivty is pretty cool
[10:06] <rickspencer3_> mvo, no, you're correct, it is normal for testing frameworks to use introspection and naming conventions
[10:06] <rickspencer3_> seb128, yes, it is well documented, and ara is very helpful as well
[10:06] <mvo> seb128: when I looked into it, found the ones availalbe not that great, but http://bazaar.launchpad.net/~mago-contributors/mago/mago/revision/155 is a good source
[10:07] <mvo> seb128: i.e. just a commit diff, that shows pretty neatly what is going on
[10:07] <rickspencer3_> mvo, seb128 right, part of the sprint this week is to make it so that the tests *are* great
[10:07] <seb128> I should try to play with it as well
[10:07] <rickspencer3_> however, I guess the fact that I am working on one is not a good sign
[10:07] <rickspencer3_> mvo, I was thinking it would be good if people included a failing test with bug reports
[10:07] <mvo> the other thing that I found difficult is to figure out the names for the menus/buttons etc
[10:07] <rickspencer3_> like you could get a failing test that shows a bug in software-center
[10:08] <seb128> I was going to suggest we should start including tests for bugs we fix
[10:08] <mvo> rickspencer3_: yeah, that would rock
[10:08] <seb128> or for sru fixes at least
[10:08] <rickspencer3_> mvo, ara has created a helper script that generates a list of widget names now
[10:08] <mvo> aha, that is really helpful!
[10:08] <rickspencer3_> seb128, mvo, yeah, if bug reports included tests, then you could add the test to the test library and you wouldn't have to worry about regressions again
[10:09] <seb128> does it mean ideally we would run the tests before doing an upload?
[10:09] <mvo> sounds like I should give it another spin again :) s-c has a gui test suite, but most of it is done without mago
[10:09] <rickspencer3_> seb128, or as part of an upload
[10:09] <rickspencer3_> like upload a package, and if there are mago tests, they get run automatically
[10:09] <mvo> rickspencer3_: much agreed, s-c runs its  tests on bzr-buildpackage and won't continue if one fails
[10:10] <seb128> would be nice
[10:10] <mvo> but having that on a much broader scope would be cool
[10:10]  * seb128 activates unity again
[10:10] <rickspencer3_> mvo, maybe someone on the QA team could take a look at porting your s-c tests to mago for you
[10:10] <mvo> and enabling the community to write them
[10:10] <seb128> let's see if I manage to keep using it now ;-)
[10:10] <mvo> seb128: it eats mouse click events!
[10:10] <rickspencer3_> well, I'm hoping to get over the learning curve today ;)
[10:11] <seb128> mvo, I had that under compiz without unity ;-)
[10:11] <mvo> rickspencer3_: well, I should port them myself :)
[10:11] <mvo> seb128: right, its compiz that is the hungry thing
[10:11] <mvo> rickspencer3_: but first I need to write a small inspection tool that spits out the xml for me from the docstrings (well, maybe not first, but it would definitely be nice to not have to touch that file as well for the simple cases)
[10:12] <seb128> mvo, is there a way to do an apt-get update from s-c?
[10:12] <mvo> no
[10:13] <seb128> thanks
[10:13] <mvo> rickspencer3_: is that script you mentioned  for getting the a11y names in the mago bzr tree? or somewhere else?
[10:16]  * seb128 adds a gnome-panel back
[10:18] <rickspencer3_> ara can you help out mvo there ^ ?
[10:19] <mvo> ara: context is that rickspencer3_ mentioned there is a script that scan the app for all the a11y names so that its simpler to know what the buttons are called etc
[10:19] <rickspencer3_> mvo, she's in the room with me here
[10:19] <rickspencer3_> I'll let her know when she's done her current discussion ;)
[10:20] <mvo> haha, ok
[10:20] <mvo> she must be super busy now
[10:22] <ara> mvo, hey!
[10:22] <ara> mvo, so I run a small app using  quickly called magomatic
[10:22] <ara> http://ubuntutesting.wordpress.com/2010/11/11/magomatic/
[10:22] <ara> no better docuementation yet
[10:23] <mvo> ara: sweet
[10:23] <mvo> ara: thanks!
[10:23] <ara> but it tries to create the application helper automatically
[10:23] <mvo> ara: can I upload it into natty?
[10:23] <mvo> ara: I mean, is it ready for the archive :)
[10:23] <mvo> ara: sounds super useful to a lot of people
[10:24] <ara> mvo, I haven't tried to package it yet, but it was created using quickly, so it should work
[10:24] <mvo> cool
[10:24]  * mvo hugs ara
[10:24] <ara> jibel, do you think magomatic is ready for the archive? ^
[10:24] <ara> (looking for second opinions) :D
[10:24] <mvo> that is really helpful as that was my main issue, finding the right names
[10:24] <pitti> re
[10:25] <pitti> ugh, what the heck
[10:25] <pitti> after this morning's upgrade I can't login through gdm any more
[10:25] <pitti> the same gdm still worked yesterday, and .xsession-errors is rather quiet
[10:25] <pitti> did anyone else get that, too?
[10:26] <seb128> I didn't dare dist-upgrading yet
[10:26] <seb128> didn't want to break the python world
[10:26] <seb128> pitti, what happens? session close immediatly?
[10:26] <Sarvatt> dist-upgrade has been broken for 3-4 days here
[10:27] <pitti> seb128: right
[10:27] <pitti> seb128: it tries to start, then X crashes
[10:27] <pitti> seb128: startx does work, though
[10:27] <seb128> weird
[10:27] <seb128> does it do the same for any user?
[10:27] <pitti> it looks a lot like gdm, except that this was working fine until this morning (2.32 I mean)
[10:27] <pitti> seb128: apparently yes
[10:28] <pitti> I'll have a deeper look at this
[10:28] <didrocks> pitti: I didn't dist-upgrade, but just saw same comments by people on the french natty forum
[10:28] <pitti> I only made a partial upgrade
[10:28] <pitti> a dist-upgrade wants to remove half of my desktop
[10:28] <seb128> robert_ancell had the same issue yesterday when he joined
[10:29] <pitti> ah, the CD build logs are quite helpful, too
[10:29] <pitti>  hplip : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti>  python-indicate : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti>  python-launchpad-integration : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti>  python-ubuntuone : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti>  python-uno : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti>  ubuntu-sso-client : Depends: python (< 2.7) but 2.7.1-0ubuntu1 is to be installed
[10:29] <pitti> seems we need to fix those
[10:31] <pitti> I'll start with indicate and lpi, presumably these are the most sensitive
[10:31] <seb128> pitti, you will probably not manage to get the indicate one
[10:31] <seb128> it requires a libdbusmenu
[10:31] <seb128> it requires a libdbusmenu rebuild
[10:32] <seb128> but libdbusmenu doesn't build with the current gir
[10:32] <pitti> right
[10:32] <seb128> kenvandine, and ted were working on landing the libdbusmenu update yesterday
[10:32] <seb128> not sure where that went
[10:32] <pitti> doko already uploaded rebuilds for everything, it seems
[10:32] <pitti> they just FTBFSed
[10:33]  * pitti grabs lpi then
[10:35] <seb128> pitti, do you want me to have a go at ubuntuone?
[10:35] <seb128> libubuntuone
[10:35] <pitti> sure, if you have time
[10:35] <pitti> python-uno is from OO.o
[10:36] <seb128> I will not touch that one :p
[10:36] <pitti> I didn't get it to build yet, need to throw more hours at thi
[10:36] <pitti> s
[10:36] <pitti> I'll try my best monkey-patching it
[10:39] <seb128> rodrigo_, hey
[10:39] <rodrigo_> hey seb128
[10:39] <seb128> rodrigo_, could you try to make libubuntuone build on natty?
[10:40] <rodrigo_> seb128, yes, working on it
[10:40] <seb128> the gir build fails
[10:40] <seb128> thanks
[10:40] <rodrigo_> oh, a different error? I'm fixing the multiple python versions thing
[10:40] <rodrigo_> where is the build log?
[10:40] <seb128> I just tried locally
[10:41] <rodrigo_> ah, ok
[10:41] <seb128> does it build for you?
[10:41] <seb128> I'm not uptodate, let me upgrade first
[10:41] <rodrigo_> no, it fails with the python stuff, not on the gir
[10:41] <seb128> I get a "Namespace is empty" error
[10:41]  * pitti dist-upgrades; this takes ubuntuone, mutter, and software-center into nirvana, but I guess I can live with that
[10:41] <seb128> in the UbuntuOne-1.0.gir build
[10:41] <pitti> ah, I see that a lot (namespace)
[10:42] <rodrigo_> oh, there was an update to fix the python 2.7 thing
[10:43] <rodrigo_> ok, trying the build with the latest
[10:43] <seb128> rodrigo_, thanks
[10:49] <seb128> re
[10:50] <seb128> pitti, did you start on ubuntu sso?
[10:50] <pitti> seb128: not yet; still waiting for dist-upgrade to finish
[10:50] <pitti> then doing lpi
[10:50] <seb128> pitti, ok, I'm doing ubuntu-sso-client
[10:50] <pitti> seb128: but sso is in my queue, unless someone else wants to fix it?
[10:50] <pitti> seb128: ok, thanks
[10:52] <jibel> ara, mvo, sure it's ready for the archive, I have few more features in my pocket, but I'll do that later. ara, can you package it ?
[10:53] <ara> OK, I'll add to my todo list :)
[10:58] <mvo> hrm, I keep typing mango
[10:58] <mvo> I can't help it!
[10:58] <pitti> mvo: others might keep typing meego :)
[10:58] <mvo> lol
[11:02] <seb128> didrocks, do you know if unity got a bug that the launcher should not display tooltips immediatly already?
[11:08] <mvo> jibel, ara: I created a very simple packaging lp:~mvo/magonize/packaging as the basis for this (mostly boilerplaet, but bzr-buildpackage --native will build it fine)
[11:10] <mvo> ara: what license do you have in mind for it? its currently public domain
[11:10] <ara> mvo, GPL should be fine
[11:11] <didrocks> seb128: there is none
[11:12] <seb128> didrocks, thanks
[11:14] <didrocks> yw
[11:15] <pitti> seb128: lpi fixed, too
[11:15] <seb128> pitti, great
[11:16] <pitti> tkamppeter: do you have something to upload in hplip? It needs a rebuild for python 2.7
[11:26] <seb128> didrocks, smspillaz: bug #687960
[11:26] <ubot2> Launchpad bug 687960 in compiz (Ubuntu) "the alt-tab action does nothing until a dialog is clicked sometimes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/687960
[11:26] <seb128> let me know if you can confirm or not
[11:33] <rodrigo_> what's Matthias Klose's irc nick?
[11:33] <seb128> doko
[11:33] <rodrigo_> ok, so he's not arounf
[11:33] <rodrigo_> around
[11:33] <seb128> just not on this channel
[11:33] <rodrigo_> ah, where can I find him?
[11:34] <seb128> rodrigo_, #ubuntu-devel
[11:36] <didrocks> seb128: waow, you're right
[11:36] <didrocks> seb128: even shift + alt + key doesn't work
[11:37] <didrocks> seb128: thanks!
[11:37] <seb128> didrocks, thanks for confirming ;-)
[12:24] <tkamppeter> pitti, no, I have upgraded HPLIP to 3.10.9 some days ago and there are also no "it stopped working" cries around. Looks like that you should simply do a no-change upload to rebuild it.
[12:32] <tkamppeter> pitti, do you know whether there is any problem with libxml2 in Natty? See bug 687973.
[12:32] <ubot2> Launchpad bug 687973 in foomatic-db-engine (Ubuntu) "[FTBFS] package 'foomatic-db-engine' (4.0.5-0ubuntu6) failed to build on natty (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/687973
[12:33] <tkamppeter> pitti, I can already reproduce it by simply running the compiler command line on the upstream source of foomatic-db-engine.
[12:40] <dpm> hi pitti, I've been looking at the maverick langpacks to make the announcement for testing. Before I ask you to copy them to -proposed, I've got a question: looking at https://edge.launchpad.net/~ubuntu-langpack/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick it seems that not all have been built (e.g. language-pack-as). Is this because the build is still in progress, or because something has happen
[12:40] <dpm> ed that interrupted it?
[12:42] <dpm> (or is is just that there wasn't a delta and thus the package did not need to be rebuilt?)
[12:50] <dpm> pitti, if that's the case ^, may I just ask you to copy the latest language packs in the ppa to maverick-proposed and disable the maverick PPA until we're done with testing?
[12:50]  * dpm goes for lunch now
[12:52] <pitti> tkamppeter: I'm not aware of a specific libxml problem
[12:53] <pitti> tkamppeter: doko already gave the reason in the last comment
[12:53] <pitti> dpm: does it need to happen this week?
[12:53] <pitti> dpm: kyleN asked me about doing an urgent update for ubuntu-docs zh_CN
[12:54] <pitti> dpm: it would be great if we could aim for next Wednesday's builds, if possible?
[12:55] <pitti> dpm: https://edge.launchpad.net/~ubuntu-langpack/+archive/ppa/+builds shows that nothing is pending to build there
[12:56] <pitti> dpm: and I don't see any unbuilt source?
[13:02] <seb128> pitti, did you investigate your gdm issue?
[13:21] <seb128> pitti, do you plan to do a g-s-d upload? or you just commited the patch to bzr?
[13:28] <pitti> seb128: the gsd patch is not that urgent, I just didn't want to forget about it
[13:28] <pitti> seb128: gdm> not yet, will do now
[13:32] <seb128> pitti, ok, because seems repete and other people have it
[13:34] <pitti> seb128: have what?
[13:34] <seb128> pitti, the same issue
[13:35]  * rodrigo_ -> lunch
[13:35] <seb128> pitti, recent comments on bug #654578
[13:35] <ubot2> Launchpad bug 654578 in gdm (Ubuntu) "Returned to gdm screen after logging in (affects: 9) (dups: 1) (heat: 32)" [High,Confirmed] https://launchpad.net/bugs/654578
[13:35] <seb128> and repete opened a new bug as well
[13:36] <seb128> pitti, well,  it was just to say that it's not only you
[13:36] <seb128> in case that's an useful info ;-)
[13:36] <didrocks> and some people complained on the french forum too
[13:41] <didrocks> seb128: (being late), thanks for fixing the g-s-d debian/rules with gcc wrong order
[13:41] <didrocks> I didn't notice you did
[13:41]  * didrocks hugs seb128
[13:41] <seb128> lol, you're welcome
[13:41]  * seb128 hugs didrocks
[13:42] <didrocks> seeing the discussion on #ubuntu-devel I was thinking "hum, still something pending on my list, let's do it :)"
[13:42] <seb128> didrocks, especially that you didn't add the build-depends I think
[13:43] <seb128> it's on the ftfbs list lucasn did
[13:43] <didrocks> seb128: oh really? but I don't remember of a FTBFS, I was maybe lucky
[13:43] <seb128> gcc-4.4 not found
[13:43] <seb128> didrocks, 4.4 was probably still on the buildds
[13:43] <didrocks> yeah
[13:43] <didrocks> it built, but they have removed it later it seems :)
[13:43] <didrocks> seb128: thanks in any case!
[13:44] <seb128> yw ;-)
[14:02] <seb128> kenvandine, hello
[14:02] <seb128> mterry, hey
[14:03] <kenvandine> hey seb128
[14:03] <seb128> kenvandine, so no pressure by natty installability is broken until python-indicate is rebuilt
[14:03] <kenvandine> i know!
[14:03] <kenvandine> :)
[14:03] <seb128> how is the libdbusmenu update going? ;-)
[14:04] <kenvandine> scary... seems the gdbus port really introduces an issue, we really do need to upload all the indicators at once
[14:04] <seb128> do they need to all be ported to the new abi?
[14:05] <seb128> or api rather
[14:05] <kenvandine> i don't think so
[14:05] <kenvandine> but i think they will all need a rebuild
[14:05] <kenvandine> when i installed it yesterday, not even nautilus would start
[14:05] <kenvandine> i think because indicator-appmenu wasn't working
[14:05] <seb128> urg
[14:06] <seb128> did you try to remove appmenu-gtk?
[14:06] <kenvandine> well, it was working well enough for nautilus to think it needed appmenus
[14:06] <kenvandine> no, i was trying to rebuild enough bits to make it work
[14:06] <kenvandine> but gave up late last night and decided to do it all in a VM :)
[14:06] <kenvandine> got a VM prepared for it now and my laptop usable again
[14:07] <sabdfl> is anybody else seeing explosive failures to login?
[14:09] <seb128> sabdfl, pitti said he was about to debug it
[14:09] <seb128> sabdfl, I've the feeling it's affecting everybody
[14:09] <seb128> I didn't update yet though since the python transition is in the middle
[14:10] <sabdfl> phew, thought i was being thpethial
[14:10] <seb128> sabdfl, you can use startx to start a session meanwhile
[14:10] <kenvandine> i haven't seen that problem yet, but tedg couldn't login last night
[14:10] <sabdfl> ok, thanks seb128
[14:10] <kenvandine> i had to get him up using startx so we could work :)
[14:10] <seb128> np
[14:11] <seb128> mterry, is there any chance you could get some of the banshee mir reviews going?
[14:11] <seb128> I'm sure Laney and jcastro will pay you back in beers at UDS
[14:13] <pitti> sabdfl: yep, still debugging; for me it started with this morning's dist-upgrades, I already had the new gdm at that time
[14:13] <mterry> seb128, sure.  I'm dealing with the other rebuilds for libgirepository now, but when I'm done.  Thanks for doing python-gobject for me, and sorry for the delay
[14:13] <seb128> mterry, no worry
[14:13] <seb128> mterry, you will need a new epiphany upload btw
[14:13] <seb128> mterry, we dropped gir-repository from the archive
[14:14] <seb128> you need to clean the build-depends on gir-repository-dev
[14:14] <mterry> seb128, OK
[14:17] <seb128> chrisccoulson, is there any chance I could abuse your lucid owning again? ;-)
[14:17] <seb128> chrisccoulson, bug #683076
[14:17] <ubot2> Launchpad bug 683076 in pidgin (Ubuntu) "pidgin can no longer log in to ICQ (affects: 26) (heat: 480)" [Undecided,Confirmed] https://launchpad.net/bugs/683076
[14:18] <chrisccoulson> seb128 - yeah, sure
[14:18] <seb128> chrisccoulson, thanks a lot!
[14:19] <dpm> pitti, ok, back. re: the maverick langpack updates, would it not be possible to do both? I.e the update this week as planned and a selective update for zh_CN next week?
[14:20] <dpm> We've been delaying this update several times, a community member has been working hard to get the language pack schedule in shape and I explained on the translators list that we are about to do a call for testing for new langpacks.
[14:20] <pitti> dpm: would be possible, yes
[14:20] <dpm> I'm just worried that people are starting to get put off by the delays.
[14:20] <dpm> so that would perhaps help
[14:20] <pitti> dpm: I just wondered why the current maverick ones in the PPA are already two weeks old
[14:21] <pitti> dpm: ah, seems we got a new delta export on Sunday
[14:21] <dpm> pitti, yes
[14:21] <pitti> hm, why didn't the cron job fire yesterday then
[14:21] <dpm> pitti, which cron job, the one for the LP exports or the one for the builds?
[14:21] <pitti> for the builds
[14:21] <pitti> hm, the logs are current
[14:22] <dpm> pitti, perhaps because there wasn't an export?
[14:22] <pitti> hm, and they look good
[14:22] <pitti> Delta language pack: 2010-12-05 04:08:57 CET download icon
[14:22] <dpm> pitti, I mean yesterday there wasn't an export
[14:22] <dpm> err tuesday, I meant
[14:22] <pitti> dpm: oh, it seems I looked wrong
[14:23] <pitti> https://launchpad.net/~ubuntu-langpack/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick -> that does have the 1204 langpacks
[14:23] <pitti> just not for some languages, which presumably just didn't get any updates since 1123
[14:23] <pitti> dpm: so, want me to copy the lot to -proposed?
[14:23] <dpm> pitti, they look good to me, the only thing that confused me as I said earlier was that
[14:23] <cyphermox> good morning!
[14:23] <dpm> pitti, yes please, if you could copy them to maverick-proposed, that'd be great
[14:24] <dpm> then I'll send the call for testing
[14:24] <pitti> dpm: note that it'll take some time until they get built
[14:24] <pitti> buildds are pretty busy right now
[14:25] <pitti> dpm: ok, copying in progress
[14:25] <dpm> pitti, ok, no worries. Do you have a rough estimate on how long (i.e. hours, days...)?
[14:25] <dpm> pitti, awesome, thanks!
[14:25] <pitti> dpm: I hope ~ 24 hours or less
[14:25] <pitti> https://edge.launchpad.net/builders
[14:25] <pitti> oh, it's not actually that bad, they caught up well
[14:25] <pitti> (except powerpc)
[14:25] <dpm> pitti, ok, great.
[14:25] <pitti> dpm: so, I think about 10 hours
[14:27] <dpm> pitti, cool. Do I need to do anything else re: the zh_CN update next week? Otherwise I'll just give a heads up to kyleN that we're releasing langpacks this week as well
[14:27] <pitti> dpm: maybe, but if we need anything, we'll contact you
[14:27] <dpm> ok, sounds good
[14:29] <seb128> hey cyphermox
[14:29] <seb128> how are you?
[14:30] <cyphermox> pretty good. yesterday was quite useful, I had been meaning to work on a /etc/hosts updates patch for NM for a little while and this time I was actually able to make it work
[14:30] <cyphermox> seb128, and you?
[14:30] <seb128> cyphermox, I'm fine thanks
[14:34] <seb128> cyphermox, how busy are you?
[14:34] <cyphermox> not overly
[14:35] <cyphermox> seb128, can I help you out with something?
[14:35] <seb128> cyphermox, could you try to get bug  #403534 to resolution?
[14:35] <ubot2> Launchpad bug 403534 in checkbox (Ubuntu) (and 1 other project) "Should use GtkBuilder rather than libglade (affects: 1) (dups: 1) (heat: 7)" [Wishlist,Triaged] https://launchpad.net/bugs/403534
[14:36] <seb128> cyphermox, btw should bug #403547 be closed?
[14:36] <ubot2> Launchpad bug 403547 in synaptic (Ubuntu) "Should use GtkBuilder rather than libglade (affects: 1) (heat: 11)" [Wishlist,In progress] https://launchpad.net/bugs/403547
[14:36] <cyphermox> seb128, I'll dou
[14:36] <cyphermox> gah
[14:36] <seb128> thanks
[14:36] <cyphermox> i'll double check synaptic, unless mvo has already merged the gtkbuilder changes?
[14:36] <seb128> if someone is wanting to update xchat-gnome to the current git that would be nice
[14:36] <seb128> is there any take for the task?
[14:36] <seb128> it would fix the ftbfs, close some open bugs and drop the libgnome use
[14:37] <cyphermox> as for checkbox, there's a branch done and ready for gtkbuilder, it's just not been reviewed so much by cr3 yet, but as soon as he comes in i'll ask him
[14:37] <cyphermox> seb128, I can do that too
[14:37] <seb128> cyphermox, I saw mvo uploaded a synaptic using gtkbuilder
[14:37] <seb128> cyphermox, ok great, thanks!
[14:37] <cyphermox> then I'll close the bug :)
[14:37] <seb128> great work on it ;-)
[14:37] <cyphermox> thx
[14:37] <cyphermox> next is gtk3, already started too :)
[14:38] <seb128> hehe
[14:38] <didrocks> hum :/ bzr: ERROR: Tree transform is malformed [('duplicate id', 'new-74', 'new-1')]
[14:38] <seb128> well first maybe try to make it stop filling .xsession-error
[14:38] <cyphermox> I'll just finish the unity manpage first :)
[14:38] <seb128> ;-)
[14:38] <didrocks> can't solve the conflicting between nux and the packaging branch…
[14:38] <seb128> it = nm-applet
[14:38] <cyphermox> seb128, I already have that change locally for nm-applet, I was testing it before upload :)
[14:38] <seb128> didrocks, you need james_w I guess
[14:40] <james_w> didrocks, could you try with lp:bzr-builddeb?
[14:40] <didrocks> seb128: yeah :/ I have tons of conflicts in the branch since last release
[14:40] <didrocks> james_w: ok, can have a try
[14:40] <james_w> thanks
[14:41] <didrocks> james_w: what should I launch, still bzr resolve?
[14:41] <james_w> didrocks, what command were you running? merge-upstream?
[14:42] <didrocks> james_w: not for that one, I'm just cherry-picking commits and have a tons of conflicts
[14:42] <didrocks> james_w: not really sure why btw
[14:42] <james_w> didrocks, oh, trying lp:bzr-builddeb probably won't help then
[14:42] <didrocks> right, that was my guess :)
[14:42] <james_w> didrocks, could you file a bug please? I'm in the middle of something right now, otherwise I would help you debug
[14:42] <didrocks> so, as I have more than 50 files conflicting, I was just thinking about bzr resolve --take-others
[14:42] <james_w> didrocks, asking in #bzr might get you unblocked
[14:43] <didrocks> james_w: ok, will try, thanks :)
[14:45] <rodrigo_> pitti, (re: our previous conversation on #ubuntu-devel) so, you said I should create the build trees, but every package I see they only have a 'mkdir build-$* && cd build-$* && configure'
[14:45] <pitti> seb128: hah, got it!
[14:46] <seb128> pitti, \o/
[14:46] <seb128> what is it?
[14:46] <rodrigo_> pitti, so, do I need to copy the sources over to each build tree?
[14:46] <pitti> rodrigo_: no; just call ../configure in the build tree
[14:46] <pitti> seb128: I purged libcanberra-gtk{,3}-module and now it works again
[14:46] <pitti> of course that was the one in my list which I suspected least -- I almost dropped it up front :)
[14:47] <seb128> weird
[14:48]  * pitti checks http://launchpadlibrarian.net/60333072/libcanberra_0.26-0ubuntu2_0.26-1ubuntu1.diff.gz
[14:48] <pitti> +debian/52libcanberra-gtk-module_add-to-gtk-modules /etc/X11/Xsession.d/52libcanberra-gtk3-module_add-to-gtk-modules
[14:48] <pitti> that looks like the only significant diff to me
[14:49] <pitti> debugging further, offline again
[14:49] <mvo> cyphermox, seb128: yep, synaptic is uploaded \o/
[14:50] <seb128> pitti, weird
[14:50] <pitti> seb128: perhaps it tries to run both startup sounds now, for gtk2 and 3?
[14:50] <seb128> well, even if that's the case why would the session crash?
[14:51] <seb128> or gdm
[14:51] <pitti> gdm itself doesn't really "crash"
[14:51] <pitti> it starts the session, but it ends immediately
[14:51] <seb128> well, why does the session end?
[14:51] <pitti> oh, wait, hang on
[14:52] <pitti> /etc/X11/Xsession.d/52libcanberra-gtk3-module_add-to-gtk-modules
[14:52] <cyphermox> mvo, sweet, I'll get back to you about gtk3 port soonish :)
[14:52] <pitti> why is that a directory?
[14:52] <pitti> that might upset Xsession
[14:52] <seb128> seems a bug
[14:52] <pitti> checking
[14:52] <pitti> /etc/X11/Xsession.d/52libcanberra-gtk3-module_add-to-gtk-modules/52libcanberra-gtk-module_add-to-gtk-modules
[14:53] <pitti> mterry: ^ I suppose that was meant to be something like 52libcanberra-gtk-module_add-to-gtk3-modules, without the extra dir?
[14:54] <mterry> pitti, hrm, yeah probably.  It came from Debian, I didn't vet that change carefully.  I'll fix
[14:54] <pitti> confirmed, if I move away the directory, it works
[14:55] <mvo> cyphermox: cool
[14:56] <pitti> mterry: confirmed; if I move it to be a file, it works
[14:56] <pitti> mterry: oh, you want to? ok, thanks; can you please add a preinst snippet to rm -r that faulty dir when upgrading from 0.26-1ubuntu1?
[14:57] <mterry> pitti, OK
[14:58] <seb128> mterry, you should be able to upload
[14:58] <pitti> ugh, that was a nice debugging exercise
[14:58] <seb128> cjwatson added exception for the 2 from yesterday
[14:58] <seb128> pitti, thanks for doing it
[14:58] <seb128> still seems we have a gdm bugs
[14:58] <seb128> the xsession should not bail out on Xsession.d issues
[14:58] <pitti> correct
[14:59] <pitti> I'll add a gdm task
[14:59] <seb128> thanks
[14:59] <seb128> pitti, can you run easily the apport tests locally?
[14:59] <seb128> pitti, having the retracers down is going to be an issue for unity
[15:00] <pitti> seb128: I was going to look at bug 687440 anyway, so while I"m at it..
[15:00] <ubot2> Launchpad bug 687440 in gdm (Ubuntu) "[Natty] gdm login-screen does not work with "enter" (affects: 4) (heat: 24)" [Undecided,Triaged] https://launchpad.net/bugs/687440
[15:00] <seb128> not sure where to investigate, the dc ones stop on the "starting a webbrowser for getting a token"
[15:00] <seb128> not sure if the auth file is just outdated
[15:00] <seb128> or if there is an apport bug that makes apport-retrace --auth= not work
[15:00] <pitti> seb128: which tests?
[15:00] <pitti> seb128: you can run apport-retrace locally, sure
[15:01] <pitti> it's nothing magic
[15:01] <pitti> it'll ask you for LP authentication the usual way
[15:01] <seb128> pitti, well the point is that I gave it a --auth=lpauth
[15:01] <seb128> where lpauth in the token on ronne
[15:01] <pitti> seb128: just do that, it should create a new file for you
[15:02] <seb128> pitti, well, I've the feeling we might just need to renew the token
[15:02] <seb128> but I don't have the password for the apport account...
[15:02] <seb128> I don't really want to put my token on ronne ;-)
[15:03] <seb128> pitti, I will do a retracing locally to see how it goes
[15:03] <pitti> seb128: oh, you mean you can't use your own because you don't have a public bug with a core dump?
[15:03] <pitti> seb128: shouldn't matter
[15:03] <pitti> seb128: just take any bug
[15:04] <seb128> pitti, I rather mean "if we need to update the retracer one I don't have the login password to do it"
[15:04] <pitti> seb128: if it can login and fetch the bug details, and complain about not finding a core dump, then I guess you are way past the point where it hangs in the DC?
[15:04] <pitti> seb128: ah, sure; I can update the auth file
[15:04] <pitti> seb128: but I seriously doubt that this is the case
[15:04] <seb128> pitti, thanks
[15:04] <pitti> seb128: all my local LP auth files keep working fine
[15:04] <seb128> ok
[15:05] <seb128> well I did a manual retracing in the dc yesterday
[15:05] <seb128> the usually way
[15:05] <pitti> seb128: how far does it get?
[15:05] <seb128> ie apport-retrace --auth=file <number> -o
[15:05] <seb128> pitti, it displays the "press enter once logged in the webbrowser" text
[15:05] <seb128> and never move from it since it waits for input
[15:05] <pitti> o_O
[15:05] <pitti> so it's not a firewall issue
[15:05] <pitti> seb128: oooh
[15:06] <pitti> seb128: I know
[15:06] <seb128> ;-)
[15:06] <pitti> seb128: it was the broken python-launchpadlib 1.8.0
[15:06] <seb128> you are made of awesome, you know?
[15:06] <seb128> ;-)
[15:06] <pitti> seb128: upgade to my 1.8.0+really.1.6.5
[15:06] <pitti> (downgrade)
[15:06] <pitti> seb128: bug 686690
[15:06] <ubot2> Launchpad bug 686690 in launchpadlib "1.8.0 breaks login_with() API compat with existing credentials files, and forces keyrings (affects: 1) (heat: 10)" [High,Triaged] https://launchpad.net/bugs/686690
[15:06] <pitti> (that made me pull my hair out)
[15:06] <seb128> pitti, oh, nice catch
[15:06] <pitti> seb128: sorry, I should have thought about that right away
[15:06] <seb128> I will try that now, thanks!
[15:07] <seb128> which copy needs to be updated?
[15:07] <pitti> instead of letting you waste time on it; I thought it would hang on the socket again
[15:07] <seb128> the one in the retracers?
[15:07] <pitti> seb128: in the fakechroots, yets
[15:07] <pitti> yes
[15:07] <seb128> ok
[15:07] <seb128> I'm on it
[15:07] <seb128> thanks!
[15:07] <pitti> seb128: ideally, if we restart them now, they should just auto-upgrade
[15:07] <seb128> right, I will try that first
[15:08] <seb128> then go in manual mode next if needed ;-)
[15:08]  * pitti hugs seb128
[15:08]  * seb128 hugs pitti back
[15:08] <pitti>  . o O { this entire week feels like "stuff breaking underneath you all over" }
[15:09] <pitti> python, gdm, OO.o, launchpadlib..
[15:11] <seb128> pitti, Setting up python-launchpadlib (1.8.0-1) ...
[15:11] <seb128> in the retracer log currently
[15:11] <pitti> :-(
[15:11] <seb128> so yes, they picked the buggy version
[15:11] <pitti> that's the broken one
[15:11] <seb128> pitti, yeah, I've just restarted them
[15:12] <pitti> ah, ok
[15:12] <seb128> let's see if they upgrade
[15:12] <pitti> python-launchpadlib | 1.8.0.is.1.6.2-0ubuntu1 |         natty | source, all
[15:12] <pitti> it should be available
[15:15] <scott-work> hi, i'm scott lavender, the project lead for ubuntu studio, can someone help me identify how to set gnome2 as the default session instead of unity for the ubuntu studio images?
[15:20] <seb128> didrocks, ^
[15:21] <seb128> I guess the trick is to make gnome-classic.desktop the default
[15:21] <seb128> you might want to check what xubuntu does to change the gdm default session
[15:26] <scott-work> thanks seb128
[15:26] <rodrigo_> aha, found the issue in libu1 package!!
[15:27] <seb128> rodrigo_, oh, what was it?
[15:28] <rodrigo_> seb128, hmm, I get another error, but the previous issue was that it was using the same build dir for the main target and for the different python version builds
[15:28] <rodrigo_> so, I changed rules to use a separate build dir for the main build
[15:28] <rodrigo_> now I get another error though
[15:28] <seb128> ok, makes sense
[15:28] <seb128> style python error?
[15:28] <rodrigo_> but at least it seems to build ok
[15:28] <rodrigo_> no, hold on, I'll paste it
[15:29] <rodrigo_> no, now it works ok, I had forgotten to use the separate build dir in install: rule
[15:29] <rodrigo_> so, phew, it took a long time to fix this, but at least it is now, it seems!! :)
[15:30]  * rodrigo_ dances
[15:31] <hallyn_> i'm on the natty desktop on my netbook - is there any recommended way right now to get rid of the window borders?
[15:49] <rodrigo_> seb128, hmm, now I remember about your git issues with libu1, I didn't see them at all, so maybe I'm missing an update to newest g-i?
[15:50]  * rodrigo_ apt-get update
[15:51] <seb128> rodrigo_, it's likely my box which is not uptodate
[15:51] <seb128> if you have it locally feel free to upload
[15:52] <rodrigo_> seb128, ah, was it complaining about --identifier-prefix?
[15:52] <seb128> yes
[15:55] <rodrigo_> ok, then indeed, you need to update
[15:55] <rodrigo_> hmm, although it should have detected the old g-i
[15:58] <seb128> rodrigo_, well I'm not on an old version
[15:58] <rodrigo_> hmm
[15:58] <seb128> I've the current one from before yesterday's rebuild
[15:58] <seb128> but some of the .gir might be outated
[15:59] <seb128> well just upload we will see if it builds on the buildds
[16:00] <seb128> pitti, retracers are working \o/
[16:00] <rodrigo_> seb128, yes, uploaded
[16:00] <rodrigo_> seb128, I see I don't have the latest g-i, but:
[16:00] <rodrigo_>  gobject-introspection : Depends: libgirepository-1.0-1 (= 0.9.12+git20101124-0ubuntu3) but it is not going to be installed
[16:01] <seb128> wait for mterry's rebuilds
[16:03] <rodrigo_> ok
[16:03] <cyphermox> ls
[16:06] <pitti> seb128: \o/
[16:07] <seb128> pitti, ;-)
[16:07] <seb128> "import os, apport.packaging, apport.hookutils"
[16:07] <seb128> pitti, ^ you said that was not required?
[16:09] <pitti> seb128: none of those are used
[16:10] <seb128> oh right
[16:11] <seb128> well I usually just put them so they are there when needed
[16:12] <pitti> seb128: don't worry, they don't hurt
[16:15] <seb128> ok, hum, apport is unhappy, I can really test my update now
[16:15] <seb128> bug #686585
[16:15] <ubot2> Launchpad bug 686585 in apport (Ubuntu) "UnicodeDecodeError: 'ascii' codec can't decode byte because of non unicode UnreportableReason (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/686585
[16:16] <seb128> didrocks, get the same issue than you had ;-)
[16:17] <didrocks> seb128: ahah \o/
[16:19] <mterry> rodrigo_, my g-i changes have intersected the general python2.7 rebuilds and things are complicated now.  Sorry
[16:20] <rodrigo_> mterry, no problem, just wanted to check if it breaks the build for a package
[16:20] <rodrigo_> so it can wait :)
[16:21] <pitti> seb128, mterry: FYI, I fixed gdm to not fall apart on Xsession.d/ dirs
[16:22] <seb128> pitti, \o/
[16:22] <mterry> pitti, awesome!
[16:23] <bcurtiswx>  rodrigo_, you are constantly using the GNOME 3 PPA.. right ?
[16:23] <rodrigo_> bcurtiswx, yes
[16:24] <bcurtiswx> rodrigo_, do you get a segfault when trying to double click "background" in gnome-control-center ?
[16:24] <rodrigo_> hmm, let me try
[16:25] <rodrigo_> hmm, g-c-c segfaults now, does not even show the window
[16:25] <bcurtiswx> yes, me too
[16:26] <rodrigo_> hmm, seems gtk's fault
[16:27] <bcurtiswx> rodrigo_, what about going to Places--> Home Folder  then double clicking the Desktop icon ?
[16:27] <rodrigo_> bcurtiswx, nautilus also crashes for me now, it needs an upstream change which hasn't been released yet
[16:27] <rodrigo_> does it crash also for you?
[16:28] <rodrigo_> hmm, no more g-c-c crashes after a gtk3 update
[16:28] <bcurtiswx> rodrigo_, thats great news to my ears.  I think this GTK bug is also the cause of why empathy windows don't open with 2.91.3
[16:28] <rodrigo_> but still, weird warnings, seems it needs a rebuild
[16:28] <bcurtiswx> rodrigo_, 2.91.7 ?
[16:28] <rodrigo_> bcurtiswx, which GTK bug?
[16:28] <rodrigo_> bcurtiswx, 2.91.6
[16:29] <bcurtiswx> the g-c-c bug sorry
[16:29] <seb128> pitti, how do I tell apport that a .crash has been handled already?
[16:29] <rodrigo_> bcurtiswx, (gnome-control-center:11516): GLib-GObject-WARNING **: specified class size for type `CcPanel' is smaller than the parent type's `GtkBin' class size
[16:29] <pitti> seb128: remove the needs-*-retrace tag
[16:29] <rodrigo_> that's what I get, so it indeed looks like it needs a rebuild
[16:29] <seb128> pitti, no, I mean locally, I want it to make the "collecting infos" again
[16:29] <rodrigo_> is that the same for empathy?
[16:29] <pitti> seb128: ubuntu-bug /var/crash/foo.crash should do it
[16:30] <seb128> pitti, no, it did it once, now it opens the summary immediatly
[16:30] <bcurtiswx> rodrigo_, http://paste.ubuntu.com/541512/
[16:30] <seb128> pitti, I want to test changes to the hook
[16:30] <pitti> seb128: ah, right, because it sees that it's already got a stack trace
[16:30] <seb128> pitti, but it seems to not be used
[16:30] <pitti> seb128: I'd just do ubuntu-bug package
[16:30] <pitti> seb128: that'll run the hooks
[16:30] <seb128> well the hook is smart with the Stracktrace content
[16:30] <pitti> seb128: and then check in the "details" expander
[16:30] <pitti> ah
[16:30] <bcurtiswx> empathy doesn't even error out.. its the same behavior as the nautilus crash.. i double click a contact and it just quickly removes and replaces the emapthy contact list.
[16:30] <seb128> so I need to test on a crash
[16:30] <pitti> seb128: try editing the .crash file and drop the Stacktrace field
[16:31] <pitti> seb128: hang on, checking code
[16:31] <seb128> hum, that's the one I want to give to my hook
[16:31] <rodrigo_> bcurtiswx, hmm
[16:31] <seb128> pitti, thanks
[16:31] <pitti> seb128: but it'll regenerate it through gdm
[16:31] <rodrigo_> bcurtiswx, that menu_proxy_module_load is from dbusmenu, right?
[16:31] <seb128> pitti, gdb?
[16:31] <pitti> seb128: ah - drop the "Dependencies" field -- that's the one it's checking for
[16:31] <bcurtiswx> rodrigo_, i don't know
[16:31] <pitti> seb128: sorry, autofingers (debugging gdm now..)
[16:31] <mvo> pitti: silly question, will the WI tracker deal with something like "[isd] (server) define datamodel for "this review was helpful" (even if not exposed in the UI/API initially): DONE and exposed (rnrclient has a report_abuse() method)." or does the DONE has to be the last word?
[16:32] <pitti> mvo: that looks broken
[16:32] <pitti> it needs to be : (todo|done|postponed|blocked)$
[16:32] <pitti> not ":done and some other gibberish"
[16:33] <bcurtiswx> rodrigo_, if it helps to test yourself http://ftp.gnome.org/pub/GNOME/sources/empathy/2.91/empathy-2.91.3.tar.gz and the ./autogen.sh with make & make install
[16:33] <rodrigo_> ok
[16:35] <mvo> thanks pitti
[16:35] <mvo> pitti: fixed i tnow
[16:35] <pitti> thanks mvo
[16:38] <seb128> didrocks, I've a tweak to the unity apport hook
[16:38] <seb128> should I just commit?
[16:38] <didrocks> seb128: yeah, just commit
[16:41] <scott-work_> didrocks: would you be able to point me at the package that it may be possibel to set the gnome session as default rather than unity?  this is for ubuntu studio
[16:42] <didrocks> scott-work_: you should change to the ubuntu desktop classic session by default
[16:43] <didrocks> scott-work_: there is a script in /usr/lib/gdm/gdm-set-default-session
[16:43] <didrocks> scott-work_: look at what I've done in ubuntu-netbook-default-settings
[16:44] <scott-work_> didrocks:  outstanding!  i will definitely look at that, thank you :)
[16:44] <didrocks> scott-work_: you're welcome :)
[16:45] <scott-work_> didrocks: is this the correct code?   http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/ubuntu-netbook-default-settings/natty/files
[16:45] <didrocks> scott-work_: it's only for armel now contrary to maverick one, but yeah, look at postinst
[16:48] <scott-work_> didrocks: okay, i think i found the part (i'm not really a programmer), thanks again :)
[16:48] <didrocks> yw :)
[17:17] <pitti> need to run out now, have a nice evening everyone!
[17:18] <cyphermox> bye pitti
[17:18] <bcurtiswx> cya pitti
[17:19] <seb128> bye pitti
[17:19] <kenvandine> bye pitti
[17:19] <kenvandine> seb128, all the indicators need a rebuild for dbusmenu, but good news is it seems painless
[17:20] <seb128> kenvandine, ok
[17:20] <kenvandine> anyone know what broke gtk apps with a sidebar?
[17:20] <seb128> nothing?
[17:20] <seb128> wfm
[17:20] <kenvandine> i have no treeview in xchat-gnome
[17:20] <kenvandine> or evolution
[17:20] <kenvandine> not sure why yet... will debug after i get this stuff uploaded
[17:21] <seb128> ok
[17:32] <scott-work_> didrocks: i'm sorry to keep bothering you but can you help me understand exactly what you did for setting the default session ?
[17:32] <scott-work_> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/ubuntu-netbook-default-settings/natty/annotate/head%3A/debian/postinst
[17:32] <didrocks> scott-work_: I can tomorrow, I'm doing a unity release right now
[17:34] <scott-work_> didrocks: certainly, thank you
[17:34] <didrocks> scott-work_: just ping me tomorrow :) sorry for not being available right now
[17:41] <seb128> cyphermox, http://git.gnome.org/browse/evolution/commit/?id=61999b493fc4266300eab2907909867e73e4cc1e
[17:41] <kenvandine> ugh... i need ted
[17:41] <seb128> cyphermox, do you think you could backport that and check the recent evo bugs in launchpad and prepare an update today or tomorrow?
[17:42] <kenvandine> seb128, the treeview problem is appmenu related somehow
[17:42] <seb128> cyphermox, there is at least one bug about the face plugin which got dropped in the update but not in the description
[17:42] <seb128> cyphermox, I'm off tomorrow but you can probably get didrocks to upload for you if you need sponsoring
[17:43] <seb128> kenvandine, hum ok
[17:43] <seb128> kenvandine, do you have an update of that in some way?
[17:43] <kenvandine> just rebuilt with newer dbusmenu
[17:43] <kenvandine> if i unset UBUNTU_MENUPROXY it works fine
[17:43] <kenvandine> but with it i get no sidebar in xchat-gnome or evo
[17:43] <kenvandine> and...
[17:44] <kenvandine> if i hit F9 to show the sidebar, it flickers...
[17:44] <kenvandine> quickly makes room for it and it goes away
[17:44] <kenvandine> just don't know how that could be related
[17:44] <didrocks> sure, tomorrow is fine
[17:44] <seb128> didrocks, thanks
[17:45] <seb128> kenvandine, weird
[17:45] <didrocks> I want also to upload evo for switching to express mode
[17:45] <didrocks> so, will be the perfect timing :)
[17:45] <seb128> we need an evo upload for the python transition
[17:45] <seb128> so in any case please one of you backport that one commit and upload tomorrow ;-)
[17:46] <didrocks> can do it if cyphermox just planned to backport that commit
[17:46] <didrocks> if nothing more involved
[17:46] <didrocks> oh the mailto:
[18:13] <seb128> time for sport
[18:13] <seb128> see you later
[18:13] <cyphermox> seb128, didrocks, I'll look at at shortly
[18:15] <kenvandine> cyphermox, is there any known problem where nm-applet won't control my network?
[18:15] <cyphermox> kenvandine, known, kind of. I've seen it stop responding to clicks in the menu, I have no idea why though :(
[18:15] <kenvandine> humm
[18:15] <kenvandine> mine seems to respond
[18:16] <didrocks> cyphermox: if it's only backport this commit, I have other evolution changes pending so I can do it :)
[18:16] <kenvandine> but it says networking is disabled
[18:16] <kenvandine> and it won't let me enable it
[18:16] <cyphermox> didrocks, trying to figure it out now.. I guess it's just a backport
[18:16] <cyphermox> kenvandine, then it's different
[18:16] <kenvandine> i can setup my network from the cli
[18:16] <didrocks> cyphermox: well, don't bother, it's just wget the patch + build
[18:17] <cyphermox> that should have been fixed... but maybe check /var/lib/NetworkManager/NetworkManager.state
[18:17] <didrocks> cyphermox: and I have other stuff to upload as well :)
[18:17] <kenvandine> ah... says it is disabled
[18:17] <cyphermox> didrocks, have you seen the three evo / e-d-s bugs from a few weeks ago ?
[18:17] <didrocks> cyphermox: for maverick or natty?
[18:17] <cyphermox> didrocks, mav
[18:17] <kenvandine> perhaps it got  confused when my indicator stack was completely hosed :)
[18:17] <cyphermox> they were srus about proxy for images
[18:18] <didrocks> cyphermox: completely went of my head, can you just add a ping on the merge requests?
[18:18] <cyphermox> huh, they weren't merge requests, I think it was debdiffs. not sure why I did it that way though
[18:18] <cyphermox> but yeah, I'll take another look
[18:19] <didrocks> cyphermox: ok, thanks :)
[18:19] <didrocks> cyphermox: so, just ping me/refactor the maverick sru
[18:19] <cyphermox> didrocks, ah, I remember, there was no maverick branch
[18:19] <didrocks> cyphermox: I'll deal next evo upload for adding things with my wi
[18:19] <didrocks> cyphermox: oh ok
[18:19] <didrocks> cyphermox: so just email me :)
[18:19] <cyphermox> okie dokie :)
[18:19] <didrocks> thanks a bunch!
[18:20] <cyphermox> kenvandine, that shouldn't happen though, unless maybe if hibernate/suspend was to fail badly (because even that should be fixed by now)
[18:33] <cyphermox> brb, switching to xchat-gnome :)
[18:49] <kenvandine> cyphermox, http://pastebin.ubuntu.com/541576/
[18:50] <kenvandine> any ideas?
[18:50] <cyphermox> err, sorry, where should I look?  ^.^
[18:50] <cyphermox> I'm hungry so I can't find what's wrong ;)
[18:50] <kenvandine> hehe
[18:51] <kenvandine> well it is cycling
[18:51] <kenvandine> i get that over and over again
[18:51] <kenvandine> it was fine this morning :)
[18:51] <cyphermox> ah, right, I see it now
[18:51] <cyphermox> I didn't upload any changes since a few weeks ago :)
[18:51] <kenvandine> setting up the interface with ifconfig works
[18:52] <kenvandine> and it makes NM stop cycling like that
[18:52] <kenvandine> but i never get access to the wireless device with it
[18:52] <kenvandine> and the only script in /etc/network/if-up.d that has an "exit 1" in it is wpasupplicant
[18:52] <cyphermox> do you have stuff in /etc/network/interfaces?
[18:53] <cyphermox> nah, 01ifupdown has nothing to do with it :)
[18:53] <kenvandine> auto lo
[18:53] <kenvandine> iface lo inet loopback
[18:53] <kenvandine> ok, that was the only error looking thing i had
[18:53] <cyphermox> maybe dbus-monitor and check if you get dbus sleep messages sent to NM
[18:54] <kenvandine> ok
[18:54] <cyphermox> unless it was triggered when you changed /var/lib/NetworkManager/NetworkManager.state, if you did
[18:57] <cyphermox> brb, I'm starving, must get food now. I'll be back in ten
[19:01] <kenvandine> whoops... been disconnected
[19:01] <kenvandine> cyphermox, ok... so should i look for org.freedesktop.NetworkManager ?
[19:01] <kenvandine> only occurances in NetworkManager in the output is for org.freedesktop.Notifications
[19:01] <kenvandine>  nothing talking to org.freedesktop.NetworkManager at all
[19:02] <kenvandine> cyphermox, sorry... did you get that? xchat-gnome doesn't handle the network changing without NM very well :)
[19:13] <cyphermox> kenvandine, yeah I go it..
[19:13] <cyphermox> not sure what it could be otherwise. does this keep going across reboots?
[19:17] <kenvandine> yeah
[19:17] <kenvandine> several reboots now
[19:17] <kenvandine> but
[19:17] <kenvandine> i am wondering if it is appindicator/dbusmenu related
[19:18] <kenvandine> clicking on those menus, should make it call out the nm_dispatcher over dbus right?
[19:18] <kenvandine> i thought clicking those menus was triggering the service to loop over and over
[19:18] <kenvandine> but maybe that is happening independently
[19:18] <kenvandine> cyphermox, i am running newly built appindicator and dbusmenu
[19:19] <kenvandine> which broke ABI
[19:20] <kenvandine> i am rebuilding nm-applet now with the rebuilt appindicator
[19:26] <cyphermox> ah, maybe there's something waiting to break in my patch ^.^
[19:28] <cyphermox> what are the ABI/API changes?
[19:33] <kenvandine> cyphermox, should the service be listening on org.freedesktop.NetworkManager?
[19:34] <kenvandine> and should it be service activatable
[19:34] <cyphermox> usually yes
[19:34] <cyphermox> well, NM should be listening
[19:34] <kenvandine> so the service is running, and d-feet doesn't see that inteface name
[19:34] <cyphermox> ah
[19:34] <kenvandine> and if i stop network-manager
[19:34] <kenvandine> and run nm-applet
[19:35] <kenvandine> it complains about not being able to connect to org.freedesktop.NetworkManager
[19:35] <cyphermox> right
[19:35] <kenvandine> but if i start network-manager again, it doesn't complain
[19:35] <kenvandine> but d-feet still doesn't see it
[19:35] <cyphermox> maybe that's just the dbus rules
[19:35] <kenvandine> oh
[19:35] <kenvandine> duh
[19:36] <kenvandine> system bus
[19:36] <cyphermox> yep
[19:36] <kenvandine> explains why d-feet can't find it :)
[19:36] <kenvandine> i just dunno... weird
[19:36] <cyphermox> oh good, I was starting to be scared ;)
[19:39] <kenvandine> cyphermox, ok... monitoring the system bus i see the events from the indicator
[19:39] <kenvandine> so i feel better about the appindicator now :)
[19:39] <kenvandine> it gets sets it to true
[19:39] <kenvandine> then immediately to false ago
[19:39] <kenvandine> again
[19:39] <kenvandine> wtf
[19:40] <cyphermox> after rebuilding it?
[19:40] <kenvandine> yeah
[19:40] <kenvandine> i assume it did before too
[19:40] <kenvandine> i was just monitoring the wrong bus
[19:41] <cyphermox> there must be something with how it rewrites the menus. can you see if it happens right after a dbusmenu signal with the menu to add, and about every 5 seconds?
[19:41] <cyphermox> what was changed in appindicator? could a signal on indicator click have been added? 'cause then I could rip out this fugly kludge and also get the memory leaks under control ;)
[19:42] <kenvandine> your using the C library right?
[19:43] <kenvandine> Fixing the Watcher Interface
[19:43] <kenvandine> and
[19:43] <kenvandine> A race fix on the dbus name (LP: #526499)
[19:43] <kenvandine> bug 526499
[19:43] <ubot2> Launchpad bug 526499 in indicator-application (Ubuntu) (and 2 other projects) "Application Indicator users launched at start-up skip the applet and fall back instead (affects: 8) (dups: 4) (heat: 64)" [Medium,Fix released] https://launchpad.net/bugs/526499
[19:43] <kenvandine> that is all that is in the changelog from upstream
[19:44] <cyphermox> ah :/
[19:48] <micahg> mterry: did you use dch -R for the rebuild versions?
[19:49] <mterry> micahg, no, didn't know that flag.  neat
[19:49] <micahg> mterry: yep, generally the ubuntu version is just incremented for rebuilds and dch -R should just DTRT
[19:49]  * mterry notes that it does the right thing for Ubuntu
[19:49] <mterry> So many magic switches!
[19:50] <micahg> mterry: yeah, I was happy when I found that one
[20:05] <cyphermox> kenvandine, you use xchat-gnome right, do you get a crash if in preferences you turn on showing the user list in the main window?
[20:12] <didrocks> pitti: if you are there tomorrow before me, can you new nux-tools and unity-common, please (2 binary packages from nux and unity)?
[20:12] <didrocks> time for sport :)
[20:13] <didrocks> see you tomorrow
[20:29] <cyphermox> kenvandine, is your new libappindicator and dbusmenu available in a ppa?
[20:55] <kenvandine> cyphermox, they are in natty now!
[20:55] <kenvandine> appindicator was getting built last i looked
[20:55] <kenvandine> cyphermox, i think i have a lead
[20:55] <kenvandine> cyphermox, in making dbusmenu build without gtk deprecations, the check item stuff changed a bit
[20:55] <kenvandine> the menus are getting toggle events
[20:56] <kenvandine> so when you click it, it almost immediately gets the next toggle
[20:56] <kenvandine> so it is toggling on and off
[20:56]  * kenvandine wonders where tedg is!
[20:59]  * bcurtiswx teleports tedg onto his desk chair
[21:00] <cyphermox> kenvandine, yeah, figured it would be something like that, every 5 seconds when the menu gets re-built
[21:01] <kenvandine> that was my initial thought
[21:01] <kenvandine> but
[21:01] <kenvandine> it isn't happening then
[21:01] <cyphermox> oh, just checking is broken
[21:01] <kenvandine> it is happening immediately
[21:01] <kenvandine> yeah
[21:01] <kenvandine> i added some debug statements
[21:01] <cyphermox> anyway, if you have a change in mind, let me know... I'll wait to apply this to the upload I want to do RFN ;D
[21:01] <kenvandine> and it gets state TRUE then immediately state FALSE
[21:01] <cyphermox> :(
[21:02] <kenvandine> i guess nothing else using appindicators is using check items
[21:02] <bcurtiswx> should they?
[21:03] <kenvandine> nah
[21:03] <kenvandine> only if they need them
[21:03] <kenvandine> just not seeing a problem anywhere else
[21:04] <cyphermox> right... and nm-applet is the only one, or one of the very few, redrawing the menu
[21:09] <kenvandine> oh... appmenu is broken for the same reason
[21:09] <kenvandine> damn!
[21:09] <kenvandine> it is a dbusmenu bug
[21:10] <kenvandine> woot
[21:10] <kenvandine> tedg, so dbusmenu has a nasty bug
[21:10] <kenvandine> check items don't work
[21:10] <tedg> kenvandine, :(
[21:10] <tedg> kenvandine, Really?  Hmm, that's odd.
[21:10] <tedg> kenvandine, 0.3.90 or 0.3.91 ?
[21:10] <kenvandine> they aren't drawing and they are toggling twice
[21:10] <kenvandine> 0.3.90
[21:11] <kenvandine> breaks nm-applet and appmenu
[21:11] <tedg> Hmm, that's odd.  Not really that much changed in 0.3.90.
[21:11] <kenvandine> for example, in xchat-gnome and evolution... anything that has a check item in the menu gets unchecked
[21:11] <kenvandine> so the tree view in xchat-gnome gets hidden
[21:11] <kenvandine> and you can
[21:11] <kenvandine> t get it back
[21:12] <kenvandine> all of mterry's changes
[21:12] <kenvandine> for building with gtk deprecated
[21:12] <kenvandine> genericmenuitem.c
[21:12] <kenvandine> although i don't see anything in the diff that should cause this
[21:13] <kenvandine> i added some debugging in nm-applet
[21:13] <kenvandine> and it gets the toggle event when you click it
[21:13] <kenvandine> and it gets a second toggle immediately
[21:14] <tedg> Hmm, okay.  I'll look.  Good to know it happened before the "big change" though.
[21:14] <tedg> Should make less variables.
[21:14] <kenvandine> yeah
[21:14] <kenvandine> but this has built in natty now
[21:14] <kenvandine> :)
[21:18] <cyphermox> hrm... tedg or kenvandine; looking at setup_dbusmenu in indicator-application. shouldn't the new dbusmenu_menuitem get freed at some point before being re-created (through calling setup_dbusmenu again in _set_menu or client_menu_changed ?
[21:18] <cyphermox> I may well be misunderstanding things though, I just started looking at the code
[21:19] <kenvandine> i really don't know that code either
[21:19] <kenvandine> the problem must be in dbusmenu though, not appindicator
[21:19] <cyphermox> kenvandine, looking at something else ;)
[21:19] <kenvandine> indicator-appmenu is affected too
[21:19] <kenvandine> ah
[21:20] <cyphermox> kenvandine, I'm trying to understand how things get done so I can figure out why nm-applet leaks so much
[21:24] <tedg> cyphermox, I don't have time to look right now, but it seems possible.  Try it, see if it breaks :)
[21:24] <cyphermox> ok, I will :)
[21:25]  * cyphermox likes to see things go boom ;)
[21:25] <tedg> kenvandine, So wait, you've got two versions of libdbusmenu-glib then?  libdbusmenu-glib1 and libdbusmenu-glib2.
[21:26] <tedg> kenvandine, Because things haven't rebuilt all against the new version, right?
[21:26] <kenvandine> probably
[21:26] <kenvandine> should we make them break?
[21:26] <tedg> Well, I don't know that we need that.
[21:27] <tedg> But just since it is an ABI change I want to be sure people aren't linking with the one they didn't build with.
[21:27] <tedg> Otherwise the fields will be all off.
[21:27] <kenvandine> i've rebuilt everything against 0.3.90
[21:27] <tedg> Ah, okay.
[21:28] <tedg> Then you should be able to remove libdbusmenu-glib1, right?
[21:28] <kenvandine> ugh... removing libdbusmenu-glib1 wants to remove unity
[21:28] <kenvandine> but i rebuilt unity... wonder why it linked
[21:29] <kenvandine> oh, well i rebuilt it for a different reason
[21:29] <kenvandine> i was only worried about things that linked against libdbusmenu-gtk1
[21:37] <kenvandine> tedg, so i know appindicator, appmenu and nm-applet aren't linked with libdbusmenu-glib1
[21:37] <kenvandine> and they all suffer from this problem
[21:38] <kenvandine> do you think just having it installed is a problem?
[21:42] <tedg> I don't think so... we'll see.  The test suite is failing this as well... so it needs to be fixed regardless.
[21:48] <tedg> Okay, one is because of the set_active function will signal :-/
[21:48] <tedg> Probably part of the whole issue.
[21:49] <kenvandine> oh!
[22:00] <kenvandine> mterry, around?
[22:00] <mterry> kenvandine, yeah.  was watching a bit of your conversation
[22:00] <mterry> kenvandine, did I break something?
[22:00] <kenvandine> unrelated :)
[22:01] <kenvandine> got another MIR related to indicator-datetime... and it is kind of urgent... gonna block getting the whole indicator stack rebuild for this dbusmenu change
[22:01] <mterry> kenvandine, ok, can look
[22:01] <kenvandine> for ofono
[22:01] <kenvandine> filing the bug now
[22:01] <mterry> kenvandine, ah right
[22:01] <kenvandine> i just reviewed the package
[22:01] <kenvandine> sorry i missed it, i thought we did the MIR for this last cycle :/
[22:01] <kenvandine> turns out we differed it :)
[22:02] <cyphermox> yeah...
[22:02] <cyphermox> I was about to start writing the mir bug but I don't know ofono so much
[22:06] <kenvandine> cyphermox, i see you have a branch waiting for upload
[22:07] <cyphermox> xchat-gnome?
[22:07] <cyphermox> or do you mean ofono?
[22:08] <kenvandine> ofono
[22:08] <kenvandine> mterry, bug 688286
[22:08] <ubot2> Launchpad bug 688286 in ofono (Ubuntu) "[MIR] ofono (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/688286
[22:08]  * mterry goes to work
[22:08] <cyphermox> kenvandine, yeah, micahg was going to look again tonight
[22:08] <kenvandine> cool, not going to try to do that before the MIR
[22:08] <kenvandine> mterry, thx!
[22:09] <cyphermox> ok, there is one thing missing from it I'll commit now anyway
[22:10] <kenvandine> cyphermox, cool, we need it in main for geoclue, which is needed for indicator-datetime... which has become more urgent because of deps getting rebuilt
[22:10] <cyphermox> kenvandine, alright :)
[22:13] <kenvandine> tedg, i have rules out libdbusmenu-glib1
[22:24] <robert_ancell> kklimonda, awesome work on the gtkmm stuff btw!
[22:29] <kklimonda> robert_ancell: thanks :)
[22:30] <robert_ancell> kklimonda, are all the packages being tracked here: http://people.canonical.com/~platform/desktop/versions.html?
[22:31] <robert_ancell> kklimonda, also, do you plan on updating the GNOME3 versions in the GNOME3 PPA?
[22:32] <kklimonda> robert_ancell: yes, I plan to work on 3.0
[22:32] <kklimonda> robert_ancell: atkmm is missing from this page
[22:32] <robert_ancell> awesome
[22:34] <kklimonda> wow, unity in natty has some serios mem leaks :/
[22:34] <kklimonda> serious even
[22:35] <robert_ancell> :/
[22:35] <robert_ancell> kklimonda, I've updated versions to track atkmm now, thanks
[22:37] <tedg> kenvandine, Could you try lp:~ted/dbusmenu/check-item-fix/
[22:39] <robert_ancell> RAOF, Natty X doesn't seem to work in qemu at the moment, know anything about that?
[22:41] <RAOF> robert_ancell: I'm not aware of anything specifically which might break it, and I haven't checked recently.  I'm also not aware of any open bugs to that effect.
[22:42] <Sarvatt> robert_ancell: are you sure it's X? you see the splash progress before it stops?
[22:43] <kenvandine> tedg, sure
[22:45] <robert_ancell> Sarvatt, I see the splash screen, but in a weird low colour mode (also happing on my main natty box).  I can disable gdm and startup fine to a text login.  If I run X manually, the qemu window disappears and a graphical one doesn't appear
[22:46] <RAOF> Got any logs out?
[22:47] <robert_ancell> I haven't been able to work out what the IP address of my qemu instance is/how I get a ssh port to it.  Do you guys know?
[22:47] <kenvandine> tedg, building now
[22:47] <Sarvatt> qemu actually dies on your host machine?
[22:47] <RAOF> robert_ancell: I always do the reverse; ssh out of my VM.
[22:48] <robert_ancell> RAOF, that's the issue, I have no quemu window when it's running, so I can't do anything except Ctrl+C!
[22:48] <RAOF> But can't you load up X in the VM, kill it, then grab the saved log?
[22:49] <RAOF> Writeback permitting?
[22:50] <robert_ancell> RAOF, I'll have a look...
[22:55] <kenvandine> tedg, that fixed it
[22:55]  * kenvandine uploads :)
[22:58] <robert_ancell> RAOF, no errors in the log
[22:58] <tedg> kenvandine, Woot!
[22:59] <kenvandine> tedg, yeah, that seems to work well
[22:59] <RAOF> robert_ancell: Of course not.  That would be entirely too useful!
[22:59] <kenvandine> fixes xchat-gnome, evo and indicator-appmenu too
[22:59]  * kenvandine takes a lunch break, finally!
[22:59] <kenvandine> mterry, any red flags with ofono?
[23:00] <RAOF> robert_ancell: Maybe it really is a qemu bug? :/
[23:00] <robert_ancell> RAOF, yeah, or kernel?
[23:01] <robert_ancell> qemu seems very silent on the matter
[23:01] <RAOF> Possible I guess.  qemu's trying to load vesa, or cirrus?
[23:02] <RAOF> Could you pastebin the log you got out?  Maybe there's something non-obvious wrong?
[23:02] <Sarvatt> could try with starting qemu with -vga vmware (I'd recommend that regardless)
[23:02] <RAOF> Have I mentioned before that btrfs deals really, really badly with write-contention? :(
[23:05] <robert_ancell> RAOF, cirrus
[23:05] <robert_ancell> Sarvatt, works, awesome!
[23:07] <Sarvatt> now hopefully you can check out your old logs, I'd *really* recommend using -vga vmware always because it's much better if you're doing anything in X in there
[23:10] <robert_ancell> Sarvatt, do you know why they don't default to that then?
[23:11] <robert_ancell> http://paste.ubuntu.com/541672/
[23:12] <robert_ancell> RAOF, Sarvatt ^^ X log
[23:13] <robert_ancell> The other nice thing is at some point the qemu window wasn't the correct size, and X would be fuzzy.  It's very hard to manually resize it to 800x600 exactly :)
[23:13] <robert_ancell> But that doesn't seem to occur with the VGA driver
[23:13] <Sarvatt> it wouldn't be so great in a really old release and dont really need it in a server image, cirrus being limited to like 1024x768 really sucks though :)
[23:14] <Sarvatt> nothing in there, go figure
[23:14] <Sarvatt> robert_ancell: is it possible the qemu window just disappears? i've been having that problem with wine for the past few days in natty
[23:14] <Sarvatt> sometimes I can move my panel aside and see a tiny corner of the window up top
[23:15] <robert_ancell> It used to be off the top of the screen, and I had to move it.  But it doesn't show in the window list, so it really seemed to have never opened
[23:15] <Sarvatt> but other times it just disappears and isnt on the window list but its still running
[23:15] <robert_ancell> is there a tool to list open windows?
[23:15] <RAOF> Sarvatt: It hasn't just been moved entirely off the visible workspace?
[23:15] <Sarvatt> RAOF: nope its not on any workspace
[23:16] <Sarvatt> things disappear UP for some reason
[23:16] <Sarvatt> making windows fullscreen and going back to unmaximized gradually moves them upwards too
[23:17] <RAOF> Oooh - I remember that problem.
[23:17] <RAOF> There was a bug in the placement code that wasn't taking into account the window decoration, so every time you did $X the window would move up by the height of the titlebar.
[23:18] <Sarvatt> yeah that matches what i'm seeing, can reproduce that easily in totem
[23:18] <Sarvatt> (in a classic gnome session)
[23:18] <RAOF> There would undoubtedly be someone in #ayatana who knew exactly what that problem will be.
[23:19] <RAOF> Woot.  Who loves BUG_ON() + a mutex deadlock in filesystems?  That's me!
[23:21] <Sarvatt> well it looks like it just goes to (0,0) and window controls are underneath the panel when I go windowed to fullscreen and back
[23:22] <RAOF> Why is plymouth so ugly all of a sudden?  Who turned off anti-aliasing?
[23:22] <Sarvatt> unmaximized windowed->maximized windowed->unmaximized windowed is working fine atm, sure as heck wasn't earlier. unmaximized windowed->fullscreen->unmaximized windowed goes to 0,0
[23:22] <robert_ancell> RAOF, I've been wondering too
[23:23] <Sarvatt> almost looks like its drawing to an 8 bit framebuffer now or something to me
[23:24] <Sarvatt> and the drm backend never gets used anymore so you just get that lovely crappy 640x480x8 one resized to native res from the looks of it
[23:28]  * Sarvatt wishes we could switch to a text plugin that only draws progress dots on a purple background so it looks good everywhere instead of this vesafb mess :(
[23:28] <Sarvatt> the Ubuntu 11.04 text is the only part that looks bad without a framebuffer driver loaded
[23:30] <Sarvatt> and the drm renderer would be used for KMS and be pretty again :)
[23:30] <RAOF> And we'd see if nouveau would lock with multiple displays again :)
[23:31] <Sarvatt> that was fixed in maverick!
[23:31] <RAOF> Fixed, fixed?  Or “don't use the drm renderer on nouveau” fixed?
[23:56] <Amaranth> Sarvatt: iirc windows moving up like that is already fixed in compiz git
[23:58] <Amaranth> The bug in compiz+unity that annoys me the most right now is actually the fast that expo is no longer centered because it doesn't take the unity dock in to account :P
[23:59] <Amaranth> s/fast/fact/


[04:09] <mup> PR snapcraft#3320 opened: [RFC] python v2 plugin: consistent linking for interpreter <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3320>
[15:54] <mup> PR snapd#9510 closed: tests: new os.query tool <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9510>


[06:07] <LocutusOfBorg> jbicha, Debian told me they still want to fix armhf, this is why I didn't do it
[06:27] <LocutusOfBorg> jbicha<EMAIL_ADDRESS>autopkgtest works, dkms module looks at least building fine


[03:22] <lotuspsychje> good morning
[21:01] <Bashing-om> UWN: Issue830 now available to our reading public: https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-issue-830/43010 :D


[08:58] <tjaalton> RAOF: whee, you found the commit to fix the mesa assert?
[08:58] <tjaalton> I was told that the assert itself was unnecessary, but that there probably was something to it
[09:06] <tjaalton> nouveau dri hasn't crashed on me during the weekend.. helps if the window count is kept low
[09:07] <tjaalton> but can't understand why links from TB don't work on my desktop, laptop is fine
[09:07] <tjaalton> (ffox opens them as 'www.%u.com')
[09:14] <RAOF> tjaalton: You're after the nv50 hunk of 7401590de for the mesa assert.
[09:15] <RAOF> Which, piglit pending, should totally be nominated for 7.10
[09:21] <hyperair> hi. where can i find xrandr's C functions documentation?
[09:22] <hyperair> that monolithic manpage isn't bringing me anywhere
[09:22] <jcristau> read the protocol spec
[09:22] <jcristau> the libXrandr api is a thin wrapper around that.
[09:22] <hyperair> hmm okay
[09:22] <hyperair> but what about the strange datatypes that it returns?
[09:23] <hyperair> all i'm trying to do is get the current resolution
[09:23] <jcristau> like what?
[09:23] <hyperair> of individual outputs
[09:23] <hyperair> XRRScreenConfiguration*
[09:23] <hyperair> XRRScreenSize*
[09:23] <hyperair> yeah, stuff like that
[09:24] <jcristau> what's strange about a struct?
[09:24] <hyperair> oh wait a sec, the structs are documented!
[09:24] <hyperair> =O
[09:24]  * hyperair facepalms
[09:27] <tjaalton> RAOF: ah, cool.. will check
[09:27] <RAOF> hyperair: :)
[09:43] <hyperair> RAOF: are the stuff mentioned inside XRandr(3) all the functions i can use? the protocol document seems to mention some other stuff..
[09:43] <hyperair> like RRGetOutputInfo and the like
[09:43] <jcristau> no, the manpage wasn't updated after 1.1
[09:44] <RAOF> hyperair: I'd be looking at the protocol doc in x11proto-randr-dev
[09:44] <hyperair> oh okay.
[09:44] <jcristau> and <X11/extensions/Xrandr.h>
[09:44] <hyperair> thanks.
[11:07] <klattimer> Does anyone have any ideas about this bug; https://bugs.launchpad.net/compiz/+bug/718663
[11:07] <ubot4> Launchpad bug 718663 in xserver-xorg-driver-vesa (and 2 other projects) "Blank unity desktop (affects: 1) (heat: 8)" [Undecided,New]
[11:09] <jcristau> not enough info there.
[11:11] <tjaalton> yep, best to use 'ubuntu-bug' when filing a new bug
[11:11] <tjaalton> there are three "upstreams" marked for that bug
[11:12] <tjaalton> or projects, none of which is ubuntu
[11:18] <klattimer> tjaalton: ah :/
[11:18] <klattimer> what info do you need?
[11:24] <tjaalton> klattimer: please run 'apport-collect 718663'
[11:25] <tjaalton> it'll attach relevant information to the bug
[11:25] <klattimer> tjaalton: done
[11:26] <klattimer> this'll take a minute
[11:27] <tjaalton> hmm does it have a poulsbo in it?
[11:27] <tjaalton> guess we'll see
[11:27] <tjaalton> ah no
[11:28] <klattimer> tjaalton: sorry I'm having trouble with apport now :/
[11:29] <klattimer> running it as user works but fails to collect log files, running it as root tells me gtk couldn't be initialised
[11:29] <klattimer> :/
[11:29] <tjaalton> it should ask for your password
[11:29] <tjaalton> to collect the logs
[11:30] <klattimer> tjaalton: that doesn't happen :/
[11:30] <tjaalton> wait, you're on 10.10?
[11:31] <tjaalton> aka maverick
[11:31] <klattimer> tjaalton: nope natty
[11:31] <klattimer> ah, it appears gdm was causing problems
[11:32] <tjaalton> then you don't have all the updates
[11:32] <klattimer> hmm
[11:32] <tjaalton> since xserver-xorg should be 1:7.6~3ubuntu4
[11:32] <klattimer> I just updated this morning
[11:32] <tjaalton> from maverick?
[11:32] <klattimer> tjaalton: no on natty
[11:32] <klattimer> this is a natty install
[11:32] <klattimer> right through
[11:32] <klattimer> I'm working on indicator-datetime (contracted)
[11:32] <klattimer> so I need to use natty
[11:33] <tjaalton> ok so what does 'apt-cache policy xserver-xorg' show as the installed version?
[11:33] <klattimer> installed 7.5, candidate 7.6
[11:33] <tjaalton> see
[11:34] <klattimer> hmm, maybe something was a little wrong during the update
[11:34] <klattimer> thanks tjaalton
[11:34] <tjaalton> how did you upgrade?
[11:35] <klattimer> tjaalton: apt-get update, apt-get upgrade
[11:36] <klattimer> but it seems all of the xorg stuff was either half installed, or not installed
[11:36] <klattimer> maybe something went wrong during the upgrade
[11:36] <tjaalton> it refuses to remove packages
[11:36] <tjaalton> so doesn't always work during the devel phase
[11:38] <tjaalton> use dist-upgrade or update-manager..
[11:39] <klattimer> tjaalton: thanks ;)
[13:50] <gordboy> so why are x-swat/x-updates offering a beta nvidia driver (that doesn't work properly) when their mission statement says they offer *stable* upsteam ? it would be very nice if you offered 260.19 nvidia driver, instead
[14:00] <tseliot> gordboy: maybe because they're supposed to work with the new Xserver with the IgnoreABI option. I don't have a real answer for you though
[14:03] <gordboy> tseliot: interesting. if that were the case, then why are the xorg-edgers (the bleeding cutting edge, break your system weekly ppa) offering the stable driver ? seems to me there is a bit of confusion ...
[14:04] <tseliot> gordboy: I wouldn't know, maybe 270.18 was really meant to be uploaded to xorg-edgers instead
[14:12] <ricotz> bjsnider, ^^^ ;)
[14:20] <tjaalton> klattimer: so do things work better after the upgrade?
[14:21] <tjaalton> klattimer: all that the logs reveal is that compiz had segfaulted three times
[14:21] <tjaalton> the x log was fine
[14:27] <tjaalton> hmm, I take that back, the xserver had crashed as well
[14:32] <bjsnider> gordboy, what distros is this?
[14:35] <gordboy> bjsnider: lucid
[14:35] <gordboy> i know maverick had trouble with 260 and the NVRM: os_raise_smp_barrier(), invalid context! thing. but lucid doesn't
[14:36] <bjsnider> well, i uploaded the 270 blob because nvidia doesn't generally break things retroactive to previous x-servers. it works fine here on maverick
[14:37] <klattimer> tjaalton: yeah thanks
[14:37] <klattimer> you can close the bug
[14:38] <tjaalton> klattimer: cool
[14:40] <gordboy> bjsnider: ok. well just so you know, the 270 on lucid gives freezes and full log files. the 260 is fine. tested on 8500gt, 9500gt and ge210
[14:40] <bjsnider> alright, well if i were you i'd go back to using the standard lucid driver
[14:42] <gordboy> bjsnider: the problem with that, is that flash 10.2 crashes immediately with 195, and libvdpau1. i know this is an inexact science ...
[14:42] <bjsnider> yeah but thi is above our pay grade
[14:43] <bjsnider> we can't fix closed-source flash and a binary graphics driver
[14:43] <bjsnider> at some point we have to throw up our hands and bow to the absurd
[14:43] <gordboy> point taken. but the 260 works well with lucid, and is the current stable offering. just saying
[14:43] <jcristau> then use that?
[14:44] <gordboy> the only place to get it is from xorg-edgers :)
[14:45] <jcristau> or nvidia.
[14:46] <bjsnider> gordboy, it works well for _you_ in lucid. i could probably scare up a dozen bug reports from others who say it causes problems for them
[14:48] <gordboy> i'll trade my 3 definites for your dozen maybes, any day :)
[15:15] <bjsnider> tseliot, i submitted a bug about some packaging issues with nvidia-current, as you requested
[15:16] <bjsnider> 704607
[15:16] <tseliot> bug 704607
[15:16] <ubot4> tseliot: Bug 704607 on http://launchpad.net/bugs/704607 is private
[15:16] <bjsnider> what?
[15:17] <tseliot> bjsnider: thanks for reporting. I'm working on nvidia today so I should fix it now in my git branch
[15:18] <bjsnider> very trivial changes. easy to implement
[15:19] <bjsnider> tseliot, i also created a bug about moving the nvidia preinstall script to jockey-common from nvidia-common. can you tell pitti about it? i don't think he was alerted it's bug 704597
[15:19] <ubot4> bjsnider: Bug 704597 on http://launchpad.net/bugs/704597 is private
[15:21] <tseliot> bjsnider: oh, right the hook for the installer. Thanks for reminding me about it. I'll talk to pitti
[15:22] <bjsnider> good, because i don't know what channels he's in
[15:43] <thesheff17> RAOF: ping.....I finally believe I got the backtrace  from the crash through gdb. http://pastebin.com/Hc19Q0fg not sure if that helps at all but let me know if you have any ideas to fix it.
[15:45] <jcristau> well, fglrx.
[15:50] <thesheff17> jcristau: yea I know...I'm really looking for a 4 port video card PCI-express that supports up to 4 monitors without breaking the bank. I got this ATI FirePro 2450 512MB PCI-e x16 Graphics Video Card for about 150 off ebay :-/
[17:13] <kklimonda> hey, does nouveau in natty support power managment?
[17:17] <Sarvatt> kklimonda: http://nouveau.freedesktop.org/wiki/PowerManagement
[17:20] <kklimonda> Sarvatt: btw, I've had a problem with Firefox causing X to use 100% of cpu (pretty much halting everything) when I browsed google images, or other pages with a lot of images using nouveau. Any idea what would cause it? That was the reason I went back to nvidia
[17:23] <kklimonda> so, from the matrix is seems that there is some power managment for nv50, as long as I don't have a fan connected to it? :)
[17:25] <Sarvatt> it could be a lot of things :( have you been able to narrow it down any? only happen with compiz or something like that?
[17:25] <Sarvatt> kklimonda: no fan speed adjustment control which isn't a big deal since your laptop doesn't have a separate fan
[17:25] <kklimonda> Sarvatt: no, but it did happen every time.
[17:25] <kklimonda> Sarvatt: I think I didn't run compiz
[17:26] <kklimonda> I could check it - it should be simple test :)
[17:26] <ricotz> Sarvatt, hi :)
[17:27] <Sarvatt> hiya! whats up ricotz?
[17:27] <ricotz> i wanted to play a bit with wayland
[17:27] <ricotz> Sarvatt, do you think pixman 0.21.4 would be considered for a sync?
[17:27] <Sarvatt> oh yeah we need a cairo-gl in xorg-edgers
[17:28] <ricotz> Sarvatt, is it? the current cairo package builds its gl extension?
[17:28] <Sarvatt> ricotz: really I've been torn on that, I dont think 0.21.x is a good idea for natty since 0.22 wont be out and its the development branch but 0.21 already went into unstable.. was hoping to put the stable 0.20.x in unstable once squeeze released
[17:29] <jcristau> yeah a development snapshot in natty doesn't seem like a good plan
[17:29] <ricotz> Sarvatt, there was a 0.20 release in exp once, perhaps this one can be pulled
[17:30] <Sarvatt> it didn't build on our toolchain until that -O2 bug got fixed in our GCC a few weeks ago so we couldn't sync it then
[17:31] <ricotz> ok, but isnt this package saved somewhere?
[17:31] <Sarvatt> ricotz: also waiting for notify-osd to get updated to not be screwed up with the newer pixman, I pinged MacSlow about it
[17:32] <Sarvatt> ricotz: well it's already up to 0.20.2 upstream and that never had a debian release
[17:32] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/654921
[17:32] <ricotz> so making an ubuntu only version of it, is no option?
[17:32] <ubot4> Launchpad bug 654921 in notify-osd (Ubuntu) "Black border in the notifications when effects are turned off (affects: 10) (dups: 1) (heat: 68)" [Undecided,Confirmed]
[17:34] <Sarvatt> ricotz: thats pretty much our only option besides staying at 0.18.4 and losing out on all the arm speedups :D
[17:35] <ricotz> so should be worth it ;)
[17:39] <ricotz> Sarvatt, i will do it
[17:39] <Sarvatt> ricotz: awesome, thank you for doing that!
[17:41] <jcristau> i'm wondering if i should get pixman 0.20 into testing
[17:54] <ricotz> Sarvatt, http://people.ubuntu.com/~ricotz/pixman/
[18:02] <ricotz> jcristau, are you going to do an upload to testing?
[18:03] <jcristau> i don't know yet.
[18:04] <ricotz> next debian release can probably wait for 0.22
[18:16] <Sarvatt> kklimonda: firefox directly from mozilla might be worth testing, they bundle their own pixman in that one and nouveau+pixman 0.18.x have had problems specifically with google image search in the past
[18:17] <kklimonda> Sarvatt: ok, I will test it out tomorrow
[18:18] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/608613 i'm looking at you
[18:18] <ubot4> Launchpad bug 608613 in pixman (Ubuntu) "Nouveau tiling problem with firefox (affects: 2) (heat: 17)" [Undecided,Fix released]
[18:19] <Sarvatt> they use their own heavily patched cairo too
[18:32] <ricotz> Sarvatt, do you if natty will ship the needed firmware for nouveau 3d support of nvc0?
[18:32] <Sarvatt> ricotz: very much doubt it
[18:32] <ricotz> Sarvatt, hmm :(
[18:32] <Sarvatt> I dont even know how to get it at the moment, its actual code from the blob so I doubt we could ever ship it :(
[18:33] <Sarvatt> I believe*
[18:54] <bryceh> thesheff17, what bug # is this for?
[18:56] <Sarvatt> ricotz: wonder if its in here - https://github.com/pathscale/envytools/
[19:00] <ricotz> Sarvatt, yeah, i found that, there are the tools to get ;)
[19:06] <thesheff17> bryceh: I was working with RAOF to troubleshoot this problem...I haven't filed a bug yet.  It is completely random about every 48 hours with that ATI FirePro 2450 card.  Do you want me to file a bug?
[20:38]  * penguin42 isn't too sure how to report a bug he's currently seeing - when windows appear they have junk in and then quickly get rendered a fraction of a second later; that's KDE on Radeon HD4350 open driver - any ideas for nailing it down?
[20:40] <jcristau> goes away when you turn off compositing?
[20:41] <penguin42> let me try - there appears to be a 'suspend desktop effects' button
[20:42] <penguin42> jcristau: No, harder to spot though because stuff is faster, but you can still see it
[21:48] <RAOF> thesheff17: Hm.  That looks like it's probably a fglrx problem.  The backtrace suggests that it's occurring when something is changing the cursor image, though, so that might help you reproduce it.
[22:02] <thesheff17> RAOF: ah ok...I will have to see if I can pin point it.  I wonder if it is only happening when it changes over a certain app running...maybe chrome
[22:03] <RAOF> Something like that would seem likely.
[22:03] <RAOF> I think the time has come to file a bug on fglrx with that backtrace attached.
[22:04] <RAOF> The backtrace makes it look like it really is a fglrx bug, so it's not likely to be fixable by us, but I understand that the amd guys check launchpad every now and then.
[22:05] <thesheff17> RAOF: sure will do...it isn't horrible since it only happens every 48 hours or so. should I use these steps to report a bug? https://wiki.ubuntu.com/X/Reporting
[22:07] <RAOF> thesheff17: Yes, please.  For you, the main thing to attach will be that backtrace.
[22:07] <thesheff17> RAOF: ok sounds good.
[22:08] <thesheff17> RAOF: Thanks for the help.
[22:12] <RAOF> No problem!
[22:16] <thesheff17> RAOF: not that this would have anything to do with the bug but so I have 2x2 monitors.  The top two monitors I cannot drag applications through the top two monitors.  but I can drag an app down to the bottom monitor and then over to the other one and then up to the other monitor. Does that make sense?
[22:18] <RAOF> That does make sense, but it might be a fglrx quirk?  There's no X-y reason why you shouldn't be able to have a rectangular array of outputs.
[22:18] <thesheff17> RAOF: yea not a huge deal just another strange thing I ran into.
[23:23] <afiestas> Hey, my X's (or maybe the kernel, I'm not sure) are crashing a looooot in Natty
[23:23] <afiestas> how can I provide more debug info?
[23:24] <afiestas> it happens randomly when I use Xv (via mplayer/vlc/whatever)
[23:24] <penguin42> afiestas: What graphics card?
[23:25] <afiestas> penguin42: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (pr
[23:25] <penguin42> ok, so it starts up, just sometimes dies?
[23:26] <afiestas> it crashes when I use Xv (the X video accelerator api)
[23:26] <afiestas> via Kamoso (Webcam app) Vlc mplayer etc
[23:26] <penguin42> how does it crash? Does the whole thing lock up? Does it log out? Does it draw aliens?
[23:27] <afiestas> it stop refreshing, and after a few seconds everything turns black
[23:27] <afiestas> I can't switch to any tty, but if for example I'm watching a film I still can hear the sound
[23:28] <penguin42> can you ping it?
[23:28] <afiestas> mm no idea, but I can try the next time
[23:28] <afiestas> also I can leave sshd open and get info if needed
[23:29] <penguin42> yeh, so look for any errors at the bottom of dmesg, and also look for the errors at the end of /var/log/Xorg.0.log
[23:30] <afiestas> ookiz, I'm going to do some patche for Kamoso now (webcam application) so I will reproduce it hopefully
[23:33] <RAOF> afiestas: Hm.  Does the apport hook trigger?
[23:34] <afiestas> RAOF: mm as far as I can tell, nope
[23:34] <afiestas> can I check it someway?
[23:35] <RAOF> You could ssh in and grab the error state.
[23:36] <afiestas> what is error state exactly? what I have to grab?
[23:38] <RAOF> The output of intel_gpu_dump and /sys/kernel/debug/dri/0/i915_error_state are good.
[23:39] <RAOF> If it's Xv related I could also throw up a testing package for you; there's a possible problem that may be what you're hitting.
[23:40] <afiestas> okz
[23:40] <afiestas> well I'm quite sure that it is Xv related
[23:40] <afiestas> it crashes only when I'm doing some video stuff
[23:42] <bryceh> afiestas, grab `dmesg` as well
[23:42] <afiestas> ookz
[23:47] <RAOF> Aha!  We have a candidate commit for the i965 gpu hangs.
[23:49] <bryceh> RAOF, if you mean ae8877e3, I'm already packaging it :-)
[23:50] <RAOF> Hm.  I means 23f9b1
[23:50] <RAOF> s/means/meant
[23:52] <bryceh> oh, then we have fixes for two gpu hangs, lovely
[23:52] <bryceh> ah wait, same patch
[23:53] <bryceh> gah I'm on crack
[23:54] <bryceh> RAOF, yes that's the commit I meant.  I'm also pulling in ae8877e3
[23:54] <RAOF> :)
[23:54] <bryceh> RAOF, why do you put up with me
[23:55] <afiestas> ue ue, package package! xD
[23:56] <afiestas> right now work on Video stuff in Natty is deadly xd
[23:56] <bryceh> RAOF, btw what are you working on at the moment?  Would you have time to look at recent commits to mesa?  jcristau said there were some cherrypicks worth including in ubuntu, but looks like I'm not going to get to them today
[23:57] <bryceh> RAOF, also we're a couple revs behind debian with mesa, although mostly looks like fixes for tangential stuff; still, might be nice to pull in anyway so we're up to date
[23:57] <RAOF> I'm currently looking at mesa; specifically unbreaking Unity on nv5x+.  I'll check out the cherry-picks.
[23:58] <bryceh> btw, I uploaded a fix to mesa earlier this morning
[23:58] <RAOF> Thanks.  I'll pull that in.
[23:59] <RAOF> Did jcristau happen to mention what cherrypicks were worthwhile, or just following the 7.10 branch?


[19:18] <rlaager> Can someone please re-open this bug? It's an issue, exactly as described, on Xenial. https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1268466
[19:21] <rlaager> Well, it's actually slightly different on Xenial. I guess gir1.2-spice-client-gtk-3.0 is required, which is currently a Recommends. So maybe that's okay then.
[19:47] <hggdh> rlaager: if thre is another dependency -- real, hard, dependency, then a new bug is warranted