[05:32] <BigWhale> Morning
[06:07] <pitti> Good morning
[06:11] <RAOF> Good morning pitti!
[06:13] <pitti> hey RAOF, how are you? how's the jet lag?
[06:13] <RAOF> Mitigated by the extreme length of time it took to actually get back :)
[06:13] <RAOF> (I got back home *yesterday*)
[06:16] <pitti> !
[06:16] <pitti> RAOF: how's that? you didn't fly with TheMuso?
[06:16] <RAOF> No.  I was flying with Kate and William and Ian.
[06:16] <RAOF> QF 10 to Melbourne, then Melbourne→Hobart
[06:17] <RAOF> So I spent Saturday night in a hotel outside Heathrow, QF 10 got in to Melbourne at 7pm Monday which was just in time to miss the last plane to Hobart for the day.  So I spent Monday night in a hotel opposite Melbourne airport, and then got back Tuesday morning.
[06:18] <RAOF> It was *totally awesome*
[06:19] <pitti> hmm, spending the night in a hotel for a change!
[06:20] <pitti> we really should do a sprint on a camping site one of these days!
[06:21] <RAOF> I was saying that on Friday.
[06:21] <RAOF> We should have an open-air sprint.  Somewhere nice and sunny, but not too sunny.
[06:24] <pitti> with a forest and a lake, too
[06:30] <RAOF> Yes.
[06:30] <RAOF> It would obviously need to be *in* the forest, because working in the direct sunlight sucks.
[06:46] <TheMuso> Morning pitti.
[06:46] <TheMuso> RAOF, pitti, yeah I agree, an open air sprint would be nice.
[06:56] <micahg> wow, LibreOffice on armel, almost 5 days and still going...
[06:59] <didrocks> good morning
[07:02] <pitti> bonjour didrocks
[07:05] <didrocks> hey pitti! how do you feel?
[07:05] <pitti> didrocks: much better, thanks!
[07:05] <pitti> almost no pain any more, and I can eat bananas again
[07:07] <didrocks> pitti: waow, seems you were quick to recover! You are quite lucky :)
[07:08] <pitti> didrocks: fortunately it was relatively easy indeed; no horizontal teeth or other jaw-breaking actions :)
[07:19] <didrocks> RAOF: hey, it seems that the nvidia driver is not kind with me from my Monday upload
[07:20] <didrocks> RAOF: I had to remove my xorg.conf (two monitors), rebooting just display on my external screen, and when I start nvidia-settings: http://paste.ubuntu.com/808272/ which is the laptop screen
[07:21] <ricotz> didrocks, hello
[07:23] <ricotz> didrocks, you missed the soname bump of librhythmbox
[07:23] <didrocks> hey ricotz, how are you?
[07:23] <ricotz> didrocks, thanks i am fine
[07:23] <didrocks> ricotz: oh? didn't see it in configure.ac. Should have been already in latest snapshot
[07:23] <ricotz> hoping you too?
[07:23] <didrocks> yeah, I'm fine, thanks!
[07:23] <ricotz> it got bumped on release 4 to 5
[07:24] <ricotz> *release,
[07:25] <didrocks> ricotz: indeed, tweaking that. Thanks
[07:25] <ricotz> yw
[07:53] <didrocks> pitti: looking for the slow "shutdown" issue, seems that users are mainly pointing network-manager as being guilty
[07:53] <didrocks> (reported my findings there: https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-01-24)
[07:54] <pitti> didrocks: interesting, thanks!
[07:55] <didrocks> yw :)
[08:19] <chrisccoulson> good morning everyone
[08:19] <pitti> hey chrisccoulson
[08:19] <didrocks> hey chrisccoulson, how are you?
[08:19] <chrisccoulson> hi pitti, how are you?
[08:19] <chrisccoulson> hi didrocks, i'm good thanks. and you?
[08:20] <didrocks> chrisccoulson: i'm fine, thanks :)
[08:20] <pitti> chrisccoulson: quite well, thanks! almost no pain any more, and I can eat bananas again :)
[08:20] <bryce> pitti, pain?  what happened?
[08:20] <chrisccoulson> ah, that's good :)
[08:20] <pitti> bryce: got two wisdom teeth pulled yesterday
[08:20] <bryce> ahh
[08:21] <chrisccoulson> pitti, was it the lower wisdom teeth?
[08:21] <pitti> chrisccoulson: both on left side; right side will follow in a few weeks
[08:22] <bryce> pitti, good to hear you're recovering; I had mine out when I was in high school
[08:23] <didrocks> same here, got them pulled out almost 10 years from now.
[08:35] <chrisccoulson> yeah, i had my bottom ones removed a few years ago
[08:36] <chrisccoulson> i actually quite enjoyed it, because i was given midazolam whilst they were being removed ;)
[08:36] <pitti> chrisccoulson: that must be a hell of a drug; I didn't particularly enjoy when they crowbared them out, felt like my jar was getting torn off
[08:39] <chrisccoulson> pitti - yeah, they had to cut my gums and drill the side of the socket out so that they could pull them out sideways (I've still got one of my top wisdom teeth in the way)
[08:39] <bryce> pitti, ow, sucks :-(
[08:39] <chrisccoulson> but i didn't really mind whilst they were doing it :)
[08:40] <pitti> chrisccoulson: *shudder*
[08:40] <bryce> guess I was lucky.  Doctor said, "Breathe deeply," and next thing I knew I was in my Dad's car being driven home with wads of cotton in my mouth.
[08:40] <chrisccoulson> oh,you had a general anaesthetic?
[08:41] <bryce> yup, don't know exactly what it was but it sure did the trick
[08:45] <smspillaz> chrisccoulson: oh man, prepare for a world of pain
[08:45] <chrisccoulson> hi smspillaz
[08:45] <smspillaz> or rather, they injected so much local anaesthetic into my mouth when they did that that I couldn't eat or speak for about 3 days
[08:46] <chrisccoulson> heh :)
[08:55] <didrocks> chrisccoulson: ubuntu-fr has a worse blackout FYI: http://www.ubuntu-fr.org/
[08:56] <didrocks> hey smspillaz
[08:56] <chrisccoulson> didrocks, nice!
[08:56] <chrisccoulson> it's a shame we don't officially participate in this ;)
[08:57] <didrocks> yeah
[08:57] <didrocks> http://linuxfr.org/ is nice too
[08:57] <chrisccoulson> lol
[08:57] <didrocks> a SOPA-compatible image :)
[08:59] <didrocks> smspillaz: do you know where we are with the "transparency regression" in the SRU? (so that we can upload a new version)
[09:00] <seb128> hey desktopers ;-)
[09:00] <didrocks> salut seb128
[09:00] <pitti> bonjour seb128, ca va?
[09:00] <seb128> lut didrocks, pitti
[09:01] <pitti> c'est l'heur de boulot?
[09:01] <agateau> hey seb128 !
[09:01] <seb128> how are you?
[09:01] <seb128> pitti, en effert !
[09:01] <chrisccoulson> ████████ seb128
[09:01] <pitti> or "l'hour"?
[09:01] <smspillaz> didrocks: I had a quick look at the code and it doesn't look like any recent changes would have directly caused it. Looks like a nux state leak, I'll need to talk to jay
[09:01] <seb128> effet
[09:01] <seb128> pitti, "l'heure"
[09:01] <pitti> ah, merci
[09:01] <seb128> chrisccoulson, can't read that but hey to you ;-)
[09:01] <seb128> lut agateau
[09:01] <agateau> chrisccoulson: did you just say something inappropriate to seb128 :)
[09:01] <seb128> everybody is awake today it seems ;-)
[09:01] <didrocks> smspillaz: ok, I think we will have to hold on the SRU because of it
[09:01] <agateau> chrisccoulson: luckily sopa is here to protect us
[09:01] <smspillaz> guh :/
[09:01] <chrisccoulson> heh :)
[09:02] <smspillaz> didrocks: we should just remove that option, though I guess we can't do that in an sru
[09:02] <seb128> chrisccoulson, wth! you don't respect the coc there!
[09:02] <smspillaz> didrocks: sucks, because that branch should really boost performance
[09:02] <chrisccoulson> lol
[09:02] <didrocks> pitti: there is a regresssion in the unity SRU ^^ (if you change the transparency for the panel in unity, it affects the decoration transparency (and some windows transparency as well)
[09:02] <seb128> ;-)
[09:02] <didrocks> smspillaz: not really an option in a stable release
[09:02] <pitti> didrocks: ah, thanks for the warning; so we'll wait for a followup?
[09:02] <seb128> didrocks, how do you change that option? is that only ccsm?
[09:02] <smspillaz> didrocks: yeah I know, thats why it sucks
[09:03] <smspillaz> seb128: yes
[09:03] <seb128> "who cares"?
[09:03] <didrocks> seb128: ccsm only, so not officially supported
[09:03] <smspillaz> but people will hate on us so ...
[09:03] <didrocks> but a lot of people seems to do that, even at canonical and I got  pinged a lot
[09:03] <seb128> like users who are able to shot themself in the feet with ccsm can deal with it
[09:03] <seb128> ok...
[09:03] <smspillaz> I can add a workaround in compiz for it, but thats about it
[09:03] <didrocks> well, nobody made the link with the unity option apparently
[09:03] <didrocks> they thought something changed into compiz :)
[09:03] <seb128> well if we stop on any option provided in ccsm that will be sport ;-)
[09:04] <didrocks> seb128: that options that *we* provide
[09:04] <didrocks> (for unity)
[09:04] <seb128> didrocks, I don't count ccsm as "provided"
[09:04] <didrocks> well, if you take the blame, I'm ok ;)
[09:04] <seb128> no, that's fine, I just wish we would stop shipping ccsm ;-)
[09:04] <didrocks> people will use gconf-tools, they are sneaky!
[09:04] <smspillaz> ccsm is not really the problem problem
[09:05] <smspillaz> *really the problem
[09:05] <seb128> didrocks, if they use gconf tools they are really on their own and deserver breakages they get though ;-)
[09:05] <didrocks> smspillaz: I'm fine with the workaround, if it can be in unity as well :)
[09:05] <smspillaz> didrocks: yeah its just ... ugh, hang on
[09:05] <didrocks> (for the SRU only)
[09:05] <seb128> smspillaz, the problem is the number of untested or not well maintained options we expose to users
[09:05] <seb128> well, anyway
[09:05] <seb128> pitti, how do you feel today?
[09:06] <seb128> pitti, did you manage to sleep normally?
[09:06] <smspillaz> seb128: indeed
[09:07] <smspillaz> didrocks: I can't test it directly right now, but unityshell.cpp:449 in trunk can be changed to
[09:07] <smspillaz>   glPushAttrib(GL_VIEWPORT_BIT | GL_ENABLE_BIT |
[09:07] <smspillaz>                GL_TEXTURE_BIT | GL_COLOR_BUFFER_BIT | GL_SCISSOR_BIT);
[09:07] <smspillaz> erm
[09:07] <smspillaz>   glPushAttrib(GL_VIEWPORT_BIT | GL_ENABLE_BIT | GL_COLOR_BIT |
[09:07] <smspillaz>                GL_TEXTURE_BIT | GL_COLOR_BUFFER_BIT | GL_SCISSOR_BIT);
[09:08] <agateau> is there a web page somewhere which describe the changes between each values of debian/compat?
[09:08] <agateau> *value
[09:08] <didrocks> smspillaz: ok, thanks, I will try to deal with that and get back to you :)
[09:08] <seb128> agateau, man debhelper
[09:09] <seb128> agateau, look for "COMPATABILITY LEVELS"
[09:09] <seb128> agateau, it has the details of each version
[09:09] <agateau> seb128: oh thanks, I didn't scroll down enough
[09:09] <seb128> yw
[09:11] <agateau> seb128: it is a nice description of the mess I am in :/
[09:11] <agateau> seb128: I am still working on sorting the installation dir of lightdm tools
[09:12] <seb128> agateau, ok, sorry but the update is taking time, my bzr skills suck, I need didrocks help
[09:12] <agateau> seb128: the only way to get libexecdir not to be /usr/lib/lightdm and thus pkglibexecdir not to be /usr/lib/lightdm/lightdm is to set debian/compat to 9...
[09:12] <agateau> seb128: but then we enter the world of multiarch...
[09:12] <seb128> agateau, the packaging is derivated from the 1.0 serie and we want to switch to 1.1 but they diverged, I'm not sure how to deal with it
[09:13] <agateau> seb128: meaning the tools are then installed in /usr/lib/$arch-dir/lightdm
[09:13] <seb128> hum, "nice"
[09:13] <agateau> seb128: which makes it painful to call them from postinst
[09:13] <seb128> agateau, you need a postinst.in generated from the rules or something
[09:14] <agateau> wow
[09:14] <didrocks> I'm wondering why it went force and back for pkglibexecdir
[09:14] <seb128> but yeah, that's non trivial
[09:14] <didrocks> from /usr/lib/lightdm to /usr/lib and then now back to /usr/lib/lightdm
[09:14] <seb128> good question
[09:14] <seb128> drop him an email ;-)
[09:14] <agateau> seb128: can't we just get the tools to install in /usr/bin or /usr/sbin?
[09:14] <agateau> that would be much simpler
[09:14] <didrocks> seb128: it's a tooling issue, not robert's (the patch is mine, after a debian guy told it changed from /usr/lib/lightdm to /usr/lib in the tooling)
[09:15] <didrocks> which was right at the time :)
[09:15] <seb128> agateau, what problem do you try to solve?
[09:15] <seb128> like is there anything not working now?
[09:15] <agateau> I want to be able to call lightdm-set-defaults from unity-greeter and lightdm-kde-greeter postinst
[09:15] <seb128> out of the dir being theorically wrong on disk from an unedeed subdir?
[09:15] <seb128> well you can do that today
[09:16] <agateau> it does not work right now because the postinst look for the script in /usr/lib/lightdm, not in /usr/lib/lightdm/lightdm
[09:16] <seb128> just fix the scripts?
[09:17] <agateau> you mean use "/usr/lib/lightdm/lightdm/lightdm-set-defaults" ?
[09:17] <agateau> that would be super ugly, no ?
[09:18] <agateau> especially since it has to be duplicated in all lightdm greeters
[09:18] <seb128> well, I guess we could install the utility in sbin
[09:19] <agateau> that's what I think as well
[09:19] <agateau> this should be done upstream, right?
[09:19] <seb128> I don't like much putting non-user-commands in the path
[09:19] <seb128> but you could argue that lightdm-set-defaults is a tool admin could be wanting to run as well
[09:20] <seb128> upstream> better yes
[09:20] <agateau> /usr/sbin is not in the path by default, so that won't affect non-root users
[09:21] <agateau> we already install the greeters in /usr/sbin, which makes even less sense imo
[09:21] <seb128> ok
[09:21] <seb128> let's do that then
[09:22] <agateau> ok, thanks, I am going to make a merge-request for this then
[09:22] <didrocks> (think you need to change casper, ubiquity and some other sessions postinst IIRC ;))
[09:22] <agateau> oh fun
[09:23] <agateau> didrocks: maybe on the packaging side we can ship a transition script in /usr/lib/lightdm?
[09:23] <agateau> didrocks: on the other hand, they are already broken right now
[09:23] <agateau> didrocks: so it won't be worse
[09:24] <didrocks> agateau: well, it's quick enough to fix, just look at the impacted places
[09:24] <didrocks> I can help you if needed
[09:24] <agateau> didrocks: I mean: sure I want to fix these, but it may not be worth setting up a transition script
[09:25] <didrocks> agreed, if it's broken today :)
[09:25] <agateau> I assume it is, since precise lightdm package does not put the script in the right dir
[09:26]  * didrocks wonders how daily image starts then
[09:27] <agateau> that is weird indeed
[09:28] <seb128> we are not broken
[09:28] <seb128> only the ppa version has the wrong dir no?
[09:28] <seb128> the precise version should be ok?
[09:28]  * didrocks dpkg -L
[09:29] <agateau> seb128: ah, correct!
[09:29] <seb128> agateau, didrocks: I will workaround it from the packaging for 1.1.1
[09:29] <seb128> i.e put it back to /usr/lib/lightdm
[09:29] <agateau> precise still has 1.0.6
[09:29] <didrocks> /usr/lib/lightdm/lightdm-set-defaults
[09:29] <seb128> didrocks, yeah, that's the correct location
[09:29] <didrocks> yeah, that was my latest patch
[09:29] <didrocks> something changed meanwhile on the toolchain again
[09:30] <seb128> ?
[09:30] <seb128> didrocks, agateau: http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/revision/1358
[09:30] <seb128> that's your issue right?
[09:30] <seb128> hum no
[09:30] <seb128> similar but for the guest session
[09:30] <agateau> seb128: if you are into "beautiful" fixes, I did that yesterday: http://pastebin.com/bYRx0n6i
[09:31] <agateau> seb128: as ugly as it is, it works :)
[09:31] <agateau> but I guess there are better ways to do that
[09:31] <didrocks> so, we were using libexec_PROGRAMS before
[09:31] <agateau> I assume passing --libexecdir=/usr/lib to configure would be enough
[09:32] <seb128> agateau, yes, I was going to say
[09:32] <seb128> that's a less hackish workaround ;-)
[09:32] <didrocks> then, we got: https://bugs.launchpad.net/lightdm/+bug/861371
[09:32] <ubot2> Launchpad bug 861371 in lightdm "use pkglibexecdir instead of libexecdir for lightdm-set-defaults" [Low,Fix released]
[09:32] <didrocks> ah here we go
[09:33] <didrocks> so, in fact, it's assuming we are using dh9
[09:33] <didrocks> but now dh9 move pkglibexecdir to arch-based, isn't it?
[09:33] <pitti> mvo: good morning! sorry, was offline yesterday
[09:34] <agateau> I love this part: "(well in fact in now use multi-arch dirs but it's irrelevant here)."
[09:34] <pitti> mvo: I don't know how to get a real gobject pointer from a pygi wrapper
[09:34] <seb128> didrocks, we are not on v6 though
[09:34] <seb128> v9
[09:34] <agateau> as long as you don't try to call the script, it's indeed irrelevant :)
[09:34] <didrocks> seb128: indeed, we discussed with robert and he planned to move to it :)
[09:34] <pitti> mvo: if you need real GI bindings for gtkspell, perhaps you can open a bug for it? or do you get along with the ctypes hack for now?
[09:34] <seb128> well, let's put it in sbin
[09:34] <seb128> with a compat symlink to the old location in the packaging
[09:35] <didrocks> agateau: maybe ask slangasek? there is maybe another autotools variable for installing in /usr/lib/<pkgname> without being arch-linked?
[09:35] <didrocks> or sbin :)
[09:36] <agateau> I wonder how other packages handle binaries installed in multi-arch dirs, I looked on my system and there are a few of them. I am afraid the answer will be "generate the scripts which calls those binaries" :/
[09:36]  * agateau likes the sbin solution :)
[09:37] <seb128> agateau, well usually stuff in libexecdir are not meant to be called by others
[09:37] <mvo> pitti: its quite cool, hash(gobject) is the pointer to the gobject (which makes sense). the ctypes hack works, but it seems a much better idea to annotate the gtkspell, I guess thats all thats needed and looks like its not too much work
[09:37] <mvo> I will try to look into it later today
[09:38] <didrocks> so, we need to do: the greeters, gnome-session, casper and the xubuntu settings package (maybe some edubuntu ones?) as far as I see
[09:38] <pitti> mvo: hash(object)> heh
[09:38] <agateau> didrocks: if we set up a symlink as seb128 suggested we don't have to do them all at once, though
[09:38] <didrocks> agateau: indeed, but still, better to drop it before the end of the cycle :)
[09:38] <agateau> didrocks: agreed
[09:39] <mvo> ctypes really allows for crazy stuff, its fun (and unforgiving, each mistake -> SEGV)
[09:40] <seb128> didrocks, gnome-session?
[09:40] <seb128> didrocks, where,why does it set the lightdm greeter?
[09:41] <agateau> seb128: maybe it calls another bin from /usr/lib/lightdm?
[09:42] <didrocks> seb128: it sets the lightdm default session
[09:42] <didrocks> same tool :)
[09:42] <agateau> ah right
[09:42] <seb128> oh right
[09:42] <seb128> well in any case I'm going to do 1.1.1 with the old path still
[09:42] <seb128> I don't want to mix update and transition
[09:42] <didrocks> pitti: closed the "focus" nautilus issue as ubuntu10 I uploaded this morning now unconditionnaly opens in a new window (which makes more sense, thinking about it)
[09:42] <seb128> we can do another revision which moves the bin to sbin and add a symlink
[09:43] <pitti> didrocks: thanks
[09:43] <seb128> but I would like robert_ancell to ack the move to sbin first
[09:43] <didrocks> pitti: for the crash, it's the one I discussed with seb yesterday, quite tricky, and mixing libunity issue and nautilus one
[09:59] <didrocks> smspillaz: are you sure about GL_COLOR_BIT? got a FTBFS/ error: 'GL_COLOR_BIT' was not declared in this scope
[10:01] <smspillaz> didrocks: oh, hmm, its a little more involved than that actually
[10:01] <smspillaz> I'll try it out later today
[10:01] <didrocks> ok
[10:02] <smspillaz> I would say GL_CURRENT_BIT but I'm not keen on that since iirc it was broken on nvidia
[10:25] <seb128> didrocks, agateau: ok, lightdm uploaded and vcs updated, sorry it took a while
[10:26] <seb128> didrocks, thanks for the help sorting the merge issues
[10:28] <agateau> seb128: thanks! looking at it right now
[10:31] <agateau> seb128: gdmflexiserver and lightdm-guest-session-wrapper are still in /usr/lib/lightdm/lightdm, that is going to cause troubles I am afraid
[10:31] <seb128> agateau, why?
[10:32] <agateau> seb128: aren't there other packages calling them... mmm, maybe not actually
[10:32] <seb128> agateau, the first one has its dir injected to the path by lightdm and the second is called by lightdm
[10:33] <seb128> agateau, well user switching and guest session still work for me
[10:33] <didrocks> seb128: yw ;)
[10:33] <agateau> seb128: right, so moving them would actually cause trouble... you are correct
[10:33] <seb128> ;-)
[10:33] <seb128> well it wouldn't cause trouble, well at least not trouble over a restart
[10:33] <seb128> but the currnet path doesn't create issues either
[10:35] <agateau> seb128: I am currently looking into moving stuff to sbin, but we can't move gdmflexiserver there. I was thinking about adding a --with-gdmflexiserver-dir to ./configure, do you think it makes sense?
[10:36] <seb128> agateau, well, ideally we would drop that stuff and get a dbus service equivalent
[10:37] <seb128> it doesn't hurt where it's stored at the moment I would bother trying to change that
[10:37] <agateau> seb128: I am not exactly sure what gdmflexiserver does, I just know it must not be in $PATH by default :)
[10:37] <seb128> if I was to invest time on it that would rather be to deprecate the concept, and have a cross dm dbus service rather than a wrapper with gdm in the name ;-)
[10:38] <agateau> makes sense :)
[10:38] <seb128> agateau, it's an utility which can be used to give commands to gdm
[10:38] <seb128> like "switch to this user"
[10:38] <seb128> lightdm emulates it because that's what gnome-screensaver use to switch user
[10:39] <seb128> well having it in the path wouldn't be an issue, but it would make lightdm and gdm conflict since they would ship the same file
[10:39] <agateau> seb128: ok, makes sense
[10:40] <seb128> one other way to "fix" it would be to have a standalone source,binary with a gdmflexiserver wrapper
[10:40] <seb128> so gdm, lightdm, etc could depends on that
[10:40] <seb128> the wrapper would have the path location
[10:40] <seb128> other dms would rename theirs to i.e gdmflexiserver.gdm
[10:42] <agateau> and the wrapper would call the appropriate server based on the currently running dm?
[10:42] <seb128> right
[10:43] <agateau> would be nicer indeed
[10:43] <seb128> I don't like much how they did it for lightdm
[10:43] <seb128> they basically inject /usr/lib/lightdm to PATH
[10:43] <agateau> indeed
[10:44] <agateau> interestingly, there is a package named kdm-gdmcompat, which diverts gdmflexiserver, calling kdmctl if kdm is running and the original gdmflexiserver if not
[10:44] <agateau> that's a bit similar to your solution
[10:44] <seb128> right
[10:44] <seb128> we should consolidate all that ;-)
[10:44] <pitti> didrocks: do you happen to have a way to reproduce bug 901689 ?
[10:44] <ubot2> Launchpad bug 901689 in pygobject "oneconf-service crashed with signal 5 in g_object_newv()" [Medium,Confirmed] https://launchpad.net/bugs/901689
[10:45] <didrocks> pitti: no, that's part of the issue in pygobject, everytime I tried to reproduce them, I don't get anything :/
[10:45] <pitti> ok
[10:45] <didrocks> I have no clue how to shake this thing
[10:49] <pitti> didrocks: might be another "only happens on shutdown" errors then?
[10:49] <pitti> if it's reproducible and happens to many people, I'm interested in looking into it
[10:50] <pitti> but not much that I can do without a reproducer :(
[10:50] <pitti> the stack trace doesn't help there, one needs the python code
[10:50] <didrocks> pitti: agreed, can totally be a "happens on shutdown"
[10:50] <pitti> but it doesn't seem to be that important after all?
[10:53] <didrocks> pitti: if it's the case, no it's not. The thing is that i have various (but different pygobject crashes) and I really would like to help there
[10:53]  * didrocks needs to find time to look at the code
[11:20] <Sweetshark> Hi all.
[11:20] <pitti> hey Sweetshark
[11:21] <Sweetshark> pitti: bug 917153 is looking fun
[11:21] <ubot2> Launchpad bug 917153 in libreoffice "failed to upgrade from oneiric to precise: /usr/lib/libreoffice/program/unopkg.bin: error while loading shared libraries: libicule.so.48: cannot open shared object file: No such file or directory" [High,New] https://launchpad.net/bugs/917153
[11:21] <pitti> missing dependency?
[11:21] <Sweetshark> -common postinst needs unopkg (from -core), but -core depends on -common
[11:22] <seb128> didrocks, interesting comment on the nautilus bug, it does segfault when you try to use the ql but no nautilus dialog is open
[11:22] <seb128> didrocks, which I can confirm here
[11:22] <seb128> didrocks, which might be a different issue than the bookmark refresh one you mentioned
[11:22] <Sweetshark> possible solution: make unopkg an package itself and depend on it from -core and -common. do you have a better idea?
[11:22] <didrocks> seb128: hum, even with the version I gave to you yesterday?
[11:22] <seb128> didrocks, yes
[11:22] <seb128> that's the one I'm running
[11:23] <seb128> the one which spawns new dialogs
[11:23] <Sweetshark> pitti: do you have a better idea?
[11:23] <pitti> Sweetshark: ah, cyclic dependency
[11:24] <pitti> Sweetshark: either this, or make it work also if the postinst didn't run yet
[11:24] <seb128> didrocks, it might explain the number of duplicates, I guess people try to use the ql to open nautilus when no dialog is open yet
[11:24] <didrocks> seb128: oh you're right
[11:24]  * didrocks run nautilus and attach gdb
[11:24] <didrocks> seb128: not sure it's the same stack than what we had yesterday though
[11:24] <didrocks> seb128: is there a duplicate handy with ubuntu10 ?
[11:26] <Sweetshark> pitti: well, -common cant really do much without -core anyway (an extension to a product that isnt installed yet?!), but at some point in time, the postinst has to run.
[11:26] <seb128> didrocks, no but the stacktrace seems the same than bug #917821 here
[11:26] <ubot2> Launchpad bug 917821 in nautilus "nautilus crashed with SIGSEGV in g_file_is_native()" [High,Confirmed] https://launchpad.net/bugs/917821
[11:26] <didrocks> hum, that is really weird then :/
[11:27] <pitti> Sweetshark: does -core really need -common that much then? you might be able to drop that from Depends: to recommends;?
[11:27]  * didrocks installs dbg there
[11:27] <Sweetshark> pitti: one could move the registering of extension to the -core postinst though.
[11:27] <seb128> didrocks, well with activate_bookmark_in_menu_item -> activate_bookmark_by_quicklist
[11:28] <seb128> didrocks, but the top 3 functions are still the same ones
[11:28] <didrocks> yeah, that's what is weird, I would expect it to crash when I get the application
[11:28] <Sweetshark> pitti: I guess -core is half of a metapackage thus I would need to add -common then to all the stuff that depended on -core before
[11:29] <Sweetshark> s/depended on -core/depended only on -core/
[11:30]  * Sweetshark loves debtree btw for this ...
[11:31] <pitti> hehe
[11:31]  * pitti -> lunch, bbl
[11:31] <pitti> Sweetshark: if -common is just meant to provide the arch: all data, then moving the registration into -core sounds fine as well
[11:32] <pitti> Sweetshark: but then you still need to break the dependency loop
[11:32] <pitti> apt breaks those in an arbitrary position, so you won't know which one will be configured eventually
[11:33] <Sweetshark> oh, there is no loop as -common doesnt yet depend on -core
[11:40] <didrocks> seb128: the stack is different there
[11:40] <didrocks> which makes sense :)
[11:40] <seb128> didrocks, is it?
[11:40] <seb128> what do you get?
[11:40] <didrocks> seb128: http://paste.ubuntu.com/808450/
[11:41] <didrocks> but this is due to ubuntu10, not ubuntu9 which is the quicklist race I bet
[11:41] <seb128> didrocks, hum, weird, I guess 10 has both issue and I ran into the other one
[11:42] <didrocks> seb128: yeah, the other issue isn't fixed
[11:42] <didrocks> so you totally can have it, but with a window opened or not
[11:42] <seb128> didrocks, I've tried to valgrind without much luck
[11:42] <didrocks> I asked kamstrup for an idea on the quicklist failure
[11:42] <didrocks> as we more or less know why and that there is no magical way to fix it on the nautilus side alone :)
[11:43] <didrocks> (well, meaning we need a proper fix)
[11:43] <didrocks> looking at the other issue now
[11:44] <RAOF> Urgh.  Unity's alt-tab now hates my dual-head setup, it seems.
[11:46] <didrocks> seb128: confirmed, I can get both issues there
[11:46] <seb128> didrocks, http://pastebin.ubuntu.com/808459/
[11:46] <seb128> didrocks, there is an invalid unref call somewhere
[11:48] <didrocks> seb128: hum? it seems quite different from the stacktraces we have
[11:48] <didrocks> as it doesn't crash on a gobject_unref
[11:50] <seb128> didrocks, well, valgrind showed that error, it might be yet another issue, or the invalid unref might be what lead to the segfault a bit later
[11:50] <seb128> btw when running under valgrind and use the ql I get some of those "GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkWindow'
[11:50] <seb128> "
[11:50] <didrocks> when you have new opened window, isn't it?
[11:51] <seb128> yes
[11:51] <didrocks> yeah, I think I can fix this issue quite easily
[11:51] <seb128> it would help if I didn't get screens and screens of
[11:51] <seb128> ==6934== Conditional jump or move depends on uninitialised value(s)
[11:52] <seb128> ==6934==    at 0x521C650: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.24.0)
[11:52] <seb128> ==6934==    by 0x5208E28: ??? (in /usr/lib/i386-linux-gnu/libpixman-1.so.0.24.0)
[11:52] <seb128> ==6934==    by 0xE3BC743: ???
[11:52] <seb128> wth libpixman!
[11:52] <seb128> didrocks, well anyway I think nautilus could use with some fixing and valgrinding out of your issue, but I will do that later
[11:52] <seb128> didrocks, let me know if I can help you with anything, meanwhile I let you look at the segfault; no need to look at 2 people at the same issue
[11:53] <didrocks> seb128: yeah, I'm just fixing first the case of "can't open if no windows there"
[11:53] <didrocks> but that clearly won't fix the second one
[11:53] <seb128> yeah, we already new about the other one
[11:53] <seb128> I think the one you fix is the most frequent one
[11:53] <didrocks> shold be :)
[11:53] <didrocks> should*
[12:03] <kamstrup> didrocks: did you try putting a g_signal_handlers_disconnect_matched(child, ...) where you remove the quicklist items?
[12:09] <didrocks> kamstrup: no, I didn't, good idea!
[13:56] <vuntz> kenvandine: hey
[13:56] <vuntz> kenvandine: will gwibber 3.4 require vala 0.14 or 0.16?
[13:56] <pitti> bonjour vuntz
[13:56] <vuntz> pitti: hello
[13:56] <vuntz> pitti: good catch on the XSelectInput stuff; hadn't noticed that :-)
[13:57] <pitti> vuntz: currently working on a global wnck_shutdown() patch; it seems to me that you'd prefer that instead of just a _stop/_restart(), right?
[13:58] <pitti> i. e. I now destroy all screens and WnckWindows and xselectinputs
[13:59] <vuntz> pitti: I do want the shutdown() one, but if it makes a visible difference, I'm welcoming the stop/restart thing too. I don't think it'll matter much in the end, though
[13:59] <pitti> vuntz: I actually have a global shutdown now, I'm just missing some windows to un-select
[13:59] <vuntz> (both approaches are expensive)
[13:59] <pitti> WIP :)
[13:59] <vuntz> cool!
[14:00] <GunnarHj> seb128: Hi Sebastien! There is a regression bug from today's lightdm update for those who use the language chooser in lightdm-gtk-greeter. This MP fixes it: https://code.launchpad.net/~gunnarhj/lightdm/language-options/+merge/89032
[14:00] <pitti> expensive> you bet.. (but so is keeping to listening all events at all times, IMHO)
[14:00] <pitti> MacSlow|lunch: ^ I wish there was a cheaper way to determine if there is a fullscreen window than having to iterate through al WnckWindows..
[14:01] <pitti> "all"
[14:01] <seb128> GunnarHj, hey, shouldn't that be fixed in upstream lightdm rather than in the packaging? why did that break, I didn't change it in the update I think?
[14:02] <GunnarHj> seb128: No, this effect was expected, since Robert didn't want to have Ubuntu specific stuff upstream.
[14:02] <seb128> GunnarHj, why was that patch not needed before?
[14:03] <kenvandine> vuntz, vala 0.14
[14:03] <GunnarHj> seb128: It's part of a larger patch that was dropped.
[14:03] <seb128> hey kenvandine
[14:03] <kenvandine> vuntz, i'll probably make sure it is buildable with either
[14:03] <kenvandine> hey seb128
[14:03] <vuntz> kenvandine: ah, I was hoping 0.16, but oh well :-)
[14:04] <kenvandine> vuntz, any particular reason?
[14:04] <vuntz> kenvandine: I'd like to avoid shipping vala 0.14 in next openSUSE
[14:04] <kenvandine> i see
[14:05] <kenvandine> well making sure it builds with 0.16 is on my todo list, but not high on the priority list
[14:05] <kenvandine> but i could bump that up a bit :)
[14:05] <vuntz> :-)
[14:05] <seb128> GunnarHj, hum, I see, there was quite some changes in 10_available_languages.patch that I dropped, should I restore those as well?
[14:05] <seb128> GunnarHj, I hate all those locale handling patches, that's too complicated ;-)
[14:06] <vuntz> I haven't tried to build it; it might just work
[14:06] <kenvandine> vuntz, it might... :)
[14:06] <GunnarHj> seb128: No, they were fixed upstream.
[14:06] <seb128> GunnarHj, so locale -a doesn't work? i.e the upstream code is buggy?
[14:06] <seb128> kenvandine, wrong way, you are supposed to say "vuntz: patches are welcome if you want to work on it" ;-)
[14:07] <vuntz> kenvandine: btw, thanks for the NEWS file!
[14:07] <kenvandine> seb128, vuntz sends patches, so i don't want to give him grief :)
[14:07] <kenvandine> vuntz, your welcome!
[14:07] <kenvandine> sorry i neglected that in the past... shame on me
[14:08] <seb128> GunnarHj, could you open a bug describing what is wrong and why we need this patch?
[14:08] <seb128> GunnarHj, I'm fine uploading it but I would like some public record of the issue and a space for comments or discussion if needed
[14:08] <GunnarHj> seb128: No... It depends on how respective distribution deals with languages. As long as people stick with a 'locale -a' list for selecting language, the upstream code is ok.
[14:09] <GunnarHj> seb128: Ok, I'll do that.
[14:09] <seb128> GunnarHj, thanks
[14:11] <seb128> chrisccoulson, hey, did you mention that you fixed bug #917598 in gpm before and want to fix it again in gsd this cycle?
[14:11] <ubot2> Launchpad bug 917598 in gnome-settings-daemon "batterie low warning has cancel button but does not cancel standby" [Undecided,New] https://launchpad.net/bugs/917598
[14:11] <seb128> chrisccoulson, I seem to recall you mentioning something like that but I'm not sure so checking ;-)
[14:12] <seb128> chrisccoulson, it's basically "it uses notification actions which trigger the notify-osd fallback dialog"
[14:14] <slangasek> didrocks, agateau: there's --libdir and --libexecdir; the latter should be used for installation of executables, and can be made to point to /usr/lib instead of /usr/lib/$arch.  (dh w/ compat 9 doesn't do this however - that was a thinko on my part when implementing)
[14:15] <didrocks> slangasek: thanks for the notice
[14:16] <agateau> slangasek: so your advice would be to explicitly pass --libexecdir at configure step?
[14:18] <slangasek> agateau: if you're needing a single helper binary installed for all archs, yeah
[14:19] <agateau> slangasek: we were considering getting them installed in /usr/sbin instead
[14:19] <slangasek> depends on whether it should be invoked by a user
[14:20] <slangasek> if it's only internal to the library, /usr/lib/ is better
[14:20] <agateau> slangasek: they can be invoked by postinst of other packages
[14:20] <vuntz> seb128, didrocks: since I don't see mterry here... do you happen to know if deja-dup targets vala 0.14 or 0.16 for this cycle?
[14:21] <seb128> vuntz, no idea
[14:21] <pitti> it shouldn't be that difficult to make stuff work with 0.16 if it works with 0.14?
[14:23] <seb128> pitti, it's only code yes ;-)
[14:23] <vuntz> I don't know, vala is a pain from time to time
[14:23] <seb128> it's not difficult, it takes some time and sometime when you make it work for the new version it stops working for the old one which annoys other users
[14:23] <kenvandine> vuntz, ok, it builds with 0.16 with minimal changes
[14:24] <kenvandine> minimal == 1 line :)
[14:24] <vuntz> heh
[14:25] <vuntz> that's cool
[14:25] <kenvandine> actually 2 lines
[14:25] <kenvandine> i'll test it a bit and make it build with either
[14:25] <kenvandine> vuntz, so don't worry about 0.14 :)
[14:26] <vuntz> kenvandine: thanks!
[14:26] <kenvandine> vuntz, anytime :)
[14:26] <chrisccoulson> seb128, yeah, i know what we need to fix there
[14:27] <pitti> kenvandine: btw, I landed libgnome-keyring introspection upstream, and uploaded to Debian; once it's through binNEW, I'll sync it
[14:27] <kenvandine> woot!
[14:27] <kenvandine> pitti, you rock!
[14:27] <pitti> kenvandine: if you want it now, I can put it into ubuntu-desktop?
[14:27] <seb128> chrisccoulson, ok, assigned to you
[14:27] <chrisccoulson> thanks :)
[14:27] <kenvandine> pitti, no rush, won't have time this week
[14:27] <pitti> kenvandine: ok; binNEW is fast these days, I figure I can sync it tomorrow
[14:28] <seb128> pitti, libxlavier upstream rolled a 5.2 tarball with your work btw
[14:29] <pitti> seb128: right, I noticed; needs one extra patch which is sitting in git now
[14:29] <pitti> seb128: I already have the stuff backported (didn't get an answer to "when release?"), so it's not that urgent; but I'll update Debian soon
[14:29] <seb128> pitti, do you know why http://cgit.freedesktop.org/libxklavier/commit/?id=7aac231e369f372cec2a1c030506b6e789907680 ?
[14:29] <pitti> seb128: it's because I misunderstood how VERSION_INFO works
[14:29] <seb128> pitti, so it's not a soname change?
[14:30] <pitti> seb128: it didn't bump soname, no
[14:30] <kenvandine> seb128, shotwell already requires valac-0.16 right?
[14:30] <seb128> ok, excellent
[14:30] <seb128> kenvandine, yes
[14:30] <pitti> seb128: it's .so.16.2 now
[14:30] <kenvandine> and i bet fedora won't have a problem with 0.16
[14:30] <pitti> seb128: apparently the soname == version - age
[14:30] <kenvandine> maybe instead of hacking around to support both i just move to .16
[14:30] <seb128> pitti, right
[14:30] <pitti> kenvandine: yes, 16 is in precise, and I figure we want to build as much as we can with it
[14:31]  * kenvandine updates the NEWS file :)
[14:31] <seb128> kenvandine, btw dobey filed a few u1 sponsoring requests
[14:31] <seb128> kenvandine, just for info, I will have a look at the end of the afternoon if you didn't before
[14:31] <kenvandine> tedg, any eta on those releases?
[14:31] <dobey> yep, and a couple more to come still
[14:32] <kenvandine> seb128, ok... i would appreciate it if you can, i'll be out tomorrow and still playing catchup
[14:32] <seb128> kenvandine, can do
[14:32] <kenvandine> seb128, thx!
[14:32] <seb128> kenvandine, yw ;-)
[14:32] <seb128> dobey, still no ubuntuone-client though, the new -gnome doesn't require it?
[14:34] <dobey> no. the new -gnome doesn't have any changes even (aside from version bump and apparently new autotools bits generated some changes in the generated files)
[14:35] <dobey> the only one i've proposed so far that does have real changes is ubuntuone-dev-tools
[14:37] <seb128> dobey, what's the point to rolling stuff which have no new code nor translations?
[14:38] <dobey> seb128: to force us into a habit of releasing on a schedule
[14:38] <dobey> rather than just when stuff gets in
[14:38] <dobey> so we aren't pushing for 50 uploads 2 days after feature freeze and such :)
[14:39] <seb128> ok, I can buy in that ;-)
[14:39] <seb128> why oh why is launchpad such a piece of crap
[14:39] <seb128> I had to remove the oneiric line from a bug to be able to reassign it to the current source without timeout
[14:39] <seb128> to add the oneiric line back
[14:39] <kenvandine> yuck
[14:40] <seb128> took me 3 tries to add the oneiric component back without hitting a timeout...
[14:40] <dobey> seb128: does it have multiple source packages marked as being affected?
[14:41] <seb128> dobey,  if you count bugzilla.gnome and fedora are "sources" yes
[14:41] <seb128> it has 2 upstream tracker watches
[14:41] <dobey> seb128: no, i mean ubuntu source packages
[14:41] <seb128> no
[14:41] <dobey> hmm
[14:42] <dobey> because i noticed there was a recent-ish change (not sure when exactly) where LP will want to add a series for every source package that is listed in the bug, when you try to target a series for one of them
[14:42] <dobey> even for the ones that are already marked invalid or whatever
[14:43] <dobey> which is a rather not-so-bright thing to do :-/
[14:43] <seb128> dobey, that's not recent
[14:43] <seb128> well at least now you have those delete buttons so you can delete lines ;-)
[14:45] <dobey> deleting is good yeah, but having the timeouts all the time is crap
[14:45] <seb128> indeed
[14:46] <dobey> and i still can't say "this only affects stable-X-Y series"
[14:46] <dobey> oh well
[14:48] <seb128> speaking about sponsoring
[14:48] <seb128> mvo, did you notice you were pilot yesterday? ;-)
[14:59] <GunnarHj> seb128: Ok, bug 918225 about the lightdm issue filed.
[14:59] <ubot2> Launchpad bug 918225 in lightdm "List of options in lightdm-gtk-greeter's language chooser not correct in Ubuntu" [Undecided,In progress] https://launchpad.net/bugs/918225
[14:59] <seb128> GunnarHj, thanks!
[14:59] <seb128> will look at it once I'm done with dobey's sponsoring requests
[15:00] <GunnarHj> seb128: Great.
[15:00] <GunnarHj> seb128: Talking about lightdm, there is a suggested SRU (approved by Robert) in bug 897166. Could you possibly upload it to oneiric-proposed?
[15:00] <ubot2> Launchpad bug 897166 in lightdm "lightdm-gtk-greeter in Xubuntu, has one untranslated item" [Low,In progress] https://launchpad.net/bugs/897166
[15:01] <mvo> seb128: *COUGH*
[15:01] <seb128> GunnarHj, I will try a look, you can also try pinging the patch pilot of the day (mdeslaur)
[15:01] <seb128> or mvo who tried to sneak out from sponsoring :p
[15:01] <seb128> mvo, ;-)
[15:03] <mdeslaur> GunnarHj: I'll take a look, give me a mment
[15:04] <GunnarHj> mdeslaur: Great, that was fast. :)
[15:04] <mdeslaur> GunnarHj: when seb128 says jump, I jump
[15:04] <seb128> lol
[15:04] <seb128> mdeslaur, thanks for looking at it ;-)
[15:04] <mdeslaur> hehe :)
[15:05] <GunnarHj> mdeslaur: seb128 must be a tough boss. ;-)
[15:05] <seb128> GunnarHj, I'm not a boss ;-)
[15:05] <seb128> but apparently eveybody fear the french :p
[15:05] <mdeslaur> lol
[15:05] <GunnarHj> Aha.
[15:10] <mdeslaur> GunnarHj: could you please use the patch system that's in the oneiric package, instead of inline patching it?
[15:12] <mdeslaur> GunnarHj: once you do that, ping me, and I'll upload it
[15:13] <GunnarHj> mdeslaur: I don't understand that.
[15:13] <GunnarHj> mdeslaur: Do you prefer a separate patch instead of an MP?
[15:13] <mdeslaur> GunnarHj: no, do you know what a patch system is in a debian package?
[15:14] <mdeslaur> GunnarHj: take a look at the debian/patches directory
[15:14] <mdeslaur> GunnarHj: and look at https://wiki.ubuntu.com/PackagingGuide/PatchSystems
[15:16] <GunnarHj> mdeslaur: Ok, now I see. Will make a patch instead.
[15:16] <mdeslaur> GunnarHj: thanks. Once you do, ping me and I'll sponsor it
[15:16] <GunnarHj> mdeslaur: Great, will do.
[15:19] <pitti> vuntz: yay, got it working now
[15:19] <pitti> vuntz: took a while to track down and clean up all that global state :) (I shyed around from that the first time, and so only disabled/re-enabled the event listeners)
[15:22] <vuntz> cool
[15:22] <pitti> vuntz: writing a slightly more elaborate test script now, to ensure that after shutdown and restart stuff really works
[15:22] <pitti> then I'll update the bug
[15:23] <pitti> vuntz: there's one thing I had to work around for now, but I'll better discuss in the bug
[15:32] <hallyn> as of latest update, x brings me to a blank screen.  I'm currently booted from a kde livecd...  known issue?
[15:33] <hallyn> (thanks to nvidia drivers i can't switch to a text console to be useful as they are always black)
[15:35] <seb128> hallyn, not known, what did you upgrade?
[15:36] <seb128> hallyn, do you usually have autologin? do you see the login screen?
[15:36] <hallyn> i usually have lightdm.  no, it blanked as soon as it was switching to lightdm
[15:36] <hallyn> i upgraded everything - which i had also done yesteryda, so it's something from the last 24 hrs
[15:37] <hallyn> lemme chekc if lightdm itself got upgraded.  i know libgtk did
[15:37] <seb128> hallyn, can you check you /var/log/lightdm/lightdm.log ?
[15:37] <seb128> your
[15:37] <seb128> hallyn, yes, lightdm got a new release
[15:38] <hallyn> lightdm.log *looks* ok...
[15:39] <hallyn> tbh this looks like an nvidia driver bug, but nvidia didn't get upgraded today
[15:39] <seb128> hallyn, what about Xorg.0.log?
[15:39] <pitti> hallyn: dkms status -> does that show that you actually got the driver?
[15:39] <pitti> hallyn: or lsmod | grep nv ?
[15:40] <pitti> hallyn: we also got a new kernel recently
[15:40] <hallyn> pitti: i can't do "dkms status".  I can't get a (*$&(*%&*  console.  I'm on a livecd
[15:40] <seb128> pitti, wouldn't work to run that from his liveCD
[15:40] <pitti> why not?
[15:41] <seb128> hallyn, can you edit xorg.conf and go back to nouveau?
[15:41] <pitti> mount the installed file system and chroot into it
[15:41] <hallyn> pitti: new kernel, that would seem likely to blame
[15:41] <seb128> see if that makes a difference?
[15:41] <hallyn> seb128: yeah, I was going to look for the instructions for that.  do i need to install the drivers, or are they already there?
[15:41] <hallyn> uh, not nouveua.
[15:41] <seb128> pitti, well that will not tell you if nv is loaded on the booted system
[15:41] <hallyn> but vesa i'd do
[15:41] <pitti> seb128: no, but dkms status at least
[15:41] <seb128> right
[15:42] <hallyn> pitti: i don't understand, is there a log file where i can see what you're looking for?
[15:43] <pitti> hallyn: if you don't want to chroot, you can also check in /lib/modules/3.2.0-9-generic/ whether you find an nvidia module there
[15:43] <hallyn> i'm fine chrooting, didn't think that would suffice
[15:43] <pitti> hallyn: dkms also has a log file somewhere, but I don't know where off-hand (not using it on my machine)
[15:44] <pitti> hallyn: dkms status should be fine; perhaps it wants /proc/ or so
[15:44] <hallyn> ok, one min
[15:44] <hallyn> ZOUNDS
[15:44] <hallyn> livecd is 32-bit :)
[15:44] <pitti> hallyn: while you are there, you could also try sudo dpkg-reconfigure nvidia-current
[15:44] <pitti> ah, bummer
[15:45] <pitti> hallyn: so, try to find the dkms log file; probably right in /var/log ?
[15:45] <hallyn> find var/log "*dkms*" shows nothing
[15:45] <hallyn> and grepping only provides update info for dkms
[15:45] <pitti> hallyn: in /var/lib/dkms/ somewhere?
[15:46] <pitti> hallyn: find /lib/modules nvidia* ?
[15:46] <hallyn> there is a /var/lib/dkms/nvidia-current
[15:46] <pitti> my last find might show if it is present for an older kernel, but not the current one
[15:46] <pitti> (also worth trying to boot into the previous kernel)
[15:47] <hallyn> yeah 3.2.0-9-generic does show up
[15:48] <hallyn> hm, no wait
[15:48] <hallyn> yeah
[15:48] <hallyn> nvidia-current.ko is there
[15:49] <hallyn> ok, so maybe i'll try vesa.  It's just it takes 20 mins for livecd to boot so i can't take this lightly :)
[15:49] <pitti> hallyn: hm, try checking /var/log/lightdm.log ?
[15:49] <pitti> sorry, /var//log/lightdm/lightdm.log
[15:49] <hallyn> pitti - that file looks ok, is there anything i can look for
 hallyn, can you check you /var/log/lightdm/lightdm.log ?
[15:49] <hallyn> in particular?
 lightdm.log *looks* ok...
[15:49] <pitti> hallyn: that dir also has the X.org looks, which might have a failure
[15:49] <pitti> s/looks/logs/
[15:50] <pitti> seb128: ah, sorry
[15:50] <hallyn> lemme isntall pastebinit and upload those, maybe you'll see something
[15:50] <seb128> pitti, no worry, seems you just go through the same question I asked a few minutes ago there though ;-)
[15:50] <seb128> hallyn, pastebin seems a good idea
[15:52] <hallyn> http://paste.ubuntu.com/808697/   lightdm.conf
[15:52] <hallyn> well fooi
[15:52] <hallyn> :0.log in lightdm does show "failed to load nv"
[15:52] <hallyn> (EE) Failed to load module "nv" (module does not exist, 0)
[15:53] <seb128> seems likely to be your issue
[15:53] <hallyn> http://paste.ubuntu.com/808700/   <- /var/log/lightdm/:0.log

[15:54] <hallyn> that ships with the kernel?
[15:54] <seb128> no, but that needs to match the kernel version
[15:55] <hallyn> oh it's an X lib?
[15:55] <hallyn> trying to find an older version
[15:55] <seb128> pitti, ^ back to you, you know better how the nvidia driver updates work
[15:55] <pitti> hallyn: "nv"?
[15:56] <pitti> hallyn: nv was dropped in oneiric or even earlier
[15:56] <seb128> oh, nv is the opensource one? I always confuse nv and nvidia :p
[15:56] <pitti> nv is gone
[15:56] <hallyn> oh, yeahm, that log file is from september
[15:56] <pitti> the open source one -> nouveau
[15:56] <pitti> closed source -> nvidia
[15:56] <hallyn> well but x-0.log has the same
[15:57] <hallyn> yeah the open source one would hang twice a day
[15:57] <hallyn> with no means to facilitate debugging
[15:57] <hallyn> so i stopped using it...
[15:57] <seb128> hallyn, do you have an /etc/X11/xorg.conf?
[15:57] <hallyn> am i supposed to be using it again>
[15:57] <hallyn> it would seem so, but it's sparse
[15:58] <seb128> what is in it?
[15:58] <hallyn> http://paste.ubuntu.com/808711/
[15:59] <seb128> hum
[15:59] <hallyn> (sorry, pastebinit wouldt install, it takes me awhile to switch over and copy/paste it)
[15:59] <seb128> what about /var/log/Xorg.0.log?
[16:01] <hallyn> http://paste.ubuntu.com/808714/
[16:01] <pitti> looks fine to me
[16:02] <pitti> hallyn: perhaps try downgrading to the previous lightdm
[16:02] <pitti> or did you already try that?
[16:02] <pitti> you can download the .debs from the live CD, place them into the root fs, reboot into recovery, and dpkg -i them
[16:02] <pitti> I need to run out now, sorry; see you tomorrow!
[16:02] <seb128> 'night pitti
[16:03] <hallyn> http://paste.ubuntu.com/808720/
[16:03] <hallyn> there is the whole thing
[16:03] <hallyn> pitti: no, i didn't.  thanks, good night
[16:04] <hallyn> seb128: waht's the simplest way (preferably doable with sed from rescue boot) to switch between vesa and nvidia or nouveau?
[16:04] <seb128> hallyn, good question for #ubuntu-x
[16:05] <seb128> but I guess editing xorg.conf
[16:05] <hallyn> i thought that file was actualy no long ersupposed to exist...
[16:05] <seb128> #ubuntu-x will know the syntax better than me though, I didn't do that for years ;-)
[16:05] <hallyn> ok, thanks
[16:05] <seb128> well it doesn't by default
[16:05] <seb128> it's still the way to specify a driver for example
[16:05] <seb128> if you i.e want to force vesa
[16:05] <hallyn> i'll google it right quick.  thanks for your help.
[16:06] <hallyn> (once i can do taht easily, i'll try the older lightdm)
[16:15] <GunnarHj> mdeslaur: I've change the MP at bug 897166 as requested.
[16:15] <ubot2> Launchpad bug 897166 in lightdm "lightdm-gtk-greeter in Xubuntu, has one untranslated item" [Low,In progress] https://launchpad.net/bugs/897166
[16:18] <mdeslaur> GunnarHj: thanks, looking now
[16:35] <jbicha> seb128: thanks for pushing libsoup2.4, I didn't get around to transforming it into a full merge proposal yet
[16:35] <seb128> jbicha, you're welcome
[16:37] <Laney> jbicha: I just realised I forgot your email. ubuntu-desktop is managed automatically so we cannot manually control what goes into (or out of) it.
[16:38] <micahg> didn't I respond to it?
[16:38] <Laney> yes, but you didn't say that :-)
[16:38] <Laney> I meant to but then forgot
[16:42] <seb128> Laney, what do you mean? what are the automatic criterious?
[16:43] <Laney> seeds?
[16:43] <Laney> There's also an override list
[16:43] <seb128> Laney, so to get something in a sed we are forced to sed it?
[16:43] <seb128> Laney, it seems a bit suboptimal to have to sed all the libs
[16:43] <Laney> but it's not controlled by the DMB editing the lists through Launchpad like the other packagesets
[16:45] <micahg> seb128: I don't know that you have to necessarily do that, I'm guessing it uses germinate in some form, but cjwatson would know better
[16:46] <mdeslaur> GunnarHj: uploaded, awaiting SRU team processing. Thanks.
[16:46] <micahg> the issue here is stuff is getting put in core where it doesn't seem to be needed there
[16:47] <Laney> https://code.launchpad.net/~cjwatson/+junk/packageset
[16:49] <seb128> Laney, yeah, we usually just end up by "please email cjwatson asking him to add the package to the set"
[16:49] <seb128> but that seems suboptimal for obvious reasons
[16:49] <seb128> i.e it spams Colin, and it means we rely,block on one person
[16:50] <Laney> indeed. but regardless I wanted to inform that telling us that stuff needs to be moved around in core/desktop-core/desktop isn't the way
[16:50] <micahg> Laney: thanks, I'll have to look at that later so I can understand how these things are generated
[16:51] <seb128> Laney, thanks, I've to admit I didn't catch the start of the discussion so I'm not sure what the topic is
[16:51] <seb128> was it about libsoup2.4 not being in the desktop set?
[16:51] <micahg> https://lists.ubuntu.com/archives/devel-permissions/2012-January/000320.html
[16:52] <seb128> oh ok
[16:52] <seb128> micahg, thanks
[17:13] <GunnarHj> mdeslaur: Thanks for sponsoring! Please see my latest comment on bug 897166, though.
[17:13] <ubot2> Launchpad bug 897166 in lightdm "lightdm-gtk-greeter in Xubuntu, has one untranslated item" [Low,In progress] https://launchpad.net/bugs/897166
[17:29] <Sweetshark> pitti: ok, I have a 3.4.5 release ready (if l10n finishes too). I will upload to chinstrap tonight.
[17:30] <Sweetshark> pitti: ah, crap need to change series to oneiric-proposed still
[17:31] <Sweetshark> pitti: anyway -- that should go into oneiric-proposed and can be tested there in the two weeks while i am on vacation
[17:33] <Sweetshark> and then I will now care about getting beta3 or 3.5.0rc1 into precise (or even the ppa, so that the bhs 2 can work with it).
[17:34] <Sweetshark> http://blog.documentfoundation.org/2012/01/17/tdf-announces-the-second-bug-hunting-session-to-put-first-release-candidate-of-libreoffice-3-5-on-the-test-bench/
[17:36] <hallyn> i *do* wonder who thought it would be a good idea to have the "your x is in a bad state, what would you  like to do?" window not have any kbd bindings...
[17:41] <mdeslaur> GunnarHj: ok, I've set it back to triaged
[17:42] <GunnarHj> mdeslaur: Ok, good.
[17:49]  * didrocks waves good evening, time for dancing :)
[17:49] <chrisccoulson> so, how are people coping without reddit?
[17:49] <didrocks> never used it, enotenoughtime ;)
[17:56] <seb128> chrisccoulson, what is reddit?
[18:07] <smspillaz> seb128: O________________________________O
[18:07] <smspillaz> you don't know what reddit is ?
[18:07] <balloons> seb128, reddit is a discussion site, where links/text is posted and people comment
[18:07] <balloons> I would give you a wikipedia link, but of course, it's blacked out too :-)
[18:08] <seb128> smspillaz, no
[18:08] <seb128> balloons, ok
[18:09] <seb128> well I'm not really into social websites ;-)
[18:12] <mdeslaur> seb128: reddit is where people bitch and moan about unity
[18:12] <seb128> mdeslaur, oh, that makes me want to be there :p
[18:12] <mdeslaur> hehe
[18:14] <smspillaz> see, SOPA is a good thing, wait
[18:14] <cyphermox> "PIPA and SOPA, NOPA!"... interesting
[18:17] <achiang> we should black out facebook, g+, reddit, twitter, irc, and email and call it "world productivity day"
[18:19] <smspillaz> January 18 - NEVER FORGET
[18:33] <Ursinha> achiang, lol
[18:53] <kenvandine> a net gain in LOC on  porting to non-deprecated gtk APIs seems icky to me
[18:53] <kenvandine>  16 files changed, 141 insertions(+), 96 deletions(-)
[18:54] <nessita> chrisccoulson: hello there! may I ask you a firefox-related question?
[18:54] <kenvandine> not as bad as the gdus port of the indicators though :)
[18:54] <seb128> nessita, poor chris
[18:54] <chrisccoulson> hah
[18:54] <nessita> seb128: hey! :-)
[18:54] <seb128> he got pinged all around during the whole day ;-)
[18:54] <chrisccoulson> nessita, only if you can provide beer :)
[18:54] <nessita> chrisccoulson: I certainly can! you coming to .ar?
[18:55] <seb128> nessita, btw still waiting on dobey's ubuntuone-client update to sponsor yours
[18:55] <nessita> seb128: yeah, I know. Thanks :-)
[18:55] <seb128> yw ;-)
[18:56] <chrisccoulson> nessita, i don't think so ;)
[18:56] <chrisccoulson> i can wait for beer though :)
[18:56] <nessita> chrisccoulson: in firefox, I used to double click on the area next to the tabs and I was able to open a new tab doing that.  I'm now running precise with the "default" theme, and the double click is ignored. But if I change the theme, the double clicks work. Any idea what's going on, and what to report?
[18:57] <nessita> chrisccoulson: actually, it works no when changing the theme, which I can't do (I can't find from where do that), but if the settings manager crash I can double click
[18:58] <chrisccoulson> nessita, oh, that hasn't worked for a while with tabs on top has it?
[18:58] <dobey> seb128: not any more :)
[18:58] <nessita> chrisccoulson: hum, sorry, I'm not following. Tabs on top of what?
[18:58] <dobey> seb128: it *just* finsiehd in pbuilder, and i just now uploaded it :)
[18:58] <seb128> dobey, great ;-)
[18:58] <seb128> dinner time
[18:58] <seb128> will look at that after dinner
[18:59] <dobey> seb128: bon apetit
[18:59] <seb128> dobey, merci ;-)
[18:59] <seb128> bbl
[18:59] <chrisccoulson> nessita, what happened is that when tabs were moved on top, upstream made it possible to grab the tab area to drag the window around (as the tab area blends in with the titlebar on our dark theme)
[18:59] <chrisccoulson> and i think that functionality disappeared
[19:00] <nessita> chrisccoulson: would you know if I can somehow have it back?
[19:00] <desrt> hey guys
[19:00] <nessita> perhaps changing the theme?
[19:00] <desrt> is reddit down for anyone else?
[19:00] <chrisccoulson> nessita, not sure about that
[19:00] <chrisccoulson> but the bug is https://bugzilla.mozilla.org/show_bug.cgi?id=635397
[19:00] <ubot2> Mozilla bug 635397 in Theme "when tabbar and menubar have unified appearance, tabbar should be just as draggable as menubar" [Normal,Verified: fixed]
[19:00] <dobey> nessita: there is an option to have tabs below the url entry again
[19:00] <dobey> nessita: it might work
[19:00] <chrisccoulson> desrt, yeah, did you notice a productivity increase?
[19:01] <chrisccoulson> nessita, yeah, moving tabs below the addressbar will work, as dobey said
[19:01] <dobey> desrt: nah, it works fine for me
[19:01] <nessita> dobey: option where? I want to try it!
[19:01] <desrt> chrisccoulson: productivity increase maybe.  increase in withdrawl symptoms?  definitely.
[19:01] <dobey> nessita: in the preferences dialog :)
[19:01] <chrisccoulson> nessita, View -> Toolbars -> Tabs on Top
[19:01] <nessita> dobey, chrisccoulson: YES IT WORKS
[19:02]  * nessita hugs everyone!
[19:02] <dobey> oh right, it's in the toolbar customization, not the prefs
[19:02]  * chrisccoulson hugs nessita
[19:02] <dobey> chrisccoulson: did you see my regression report btw?
[19:02]  * nessita haz doubleclicks again! she's happy!
[19:03] <chrisccoulson> dobey, not yet. i really need to do some other work first ;)
[19:03] <dobey> chrisccoulson: bug #917008
[19:03] <ubot2> Launchpad bug 917008 in firefox "Mouse Interactivity Regression with Global Menu bar" [Undecided,New] https://launchpad.net/bugs/917008
[19:03] <dobey> it's a fun one :)
[19:03] <dobey> sure, i know fixing isn't easy
[19:03] <chrisccoulson> dobey, that's a duplicate
[19:03] <dobey> ah
[19:04] <chrisccoulson> and is a limitation of dbusmenu, the panel and pretty much every other part of the stack ;)
[19:04] <dobey> well launchpad sucks at suggesting duplicates then
[19:04] <chrisccoulson> ie, firefox is the wrong place to report it ;)
[19:04] <tkamppeter> pitti, Alioth is back, I have pushed my last changes.
[19:04] <dobey> yes i know why it's broken
[19:04] <dobey> well firefox is affected
[19:04] <dobey> even if dbusmenu had API to do it, the extension would have to use it
[19:04] <dobey> and it obviously doesn't :)
[19:05] <kenvandine> vuntz, good timing on asking about valac-0.16 and gwibber, spot just pinged me about rawhide build failures
[19:05] <kenvandine> nice to have a branch ready for him :)
[19:18] <czajkowski> Riddell: ping
[19:50] <vuntz> kenvandine: :-)
[19:50] <vuntz> kenvandine: I already merged your patch
[19:51] <kenvandine> cool
[19:54] <BigWhale> changed status to Fix Released on six bugs... yay happy!
[19:54] <kenvandine> BigWhale, woot
[19:55] <BigWhale> ken! :) Back home? :)
[19:55] <kenvandine> yup
[19:56] <BigWhale> Canonical leaves, Budapest bars go back into recession ...
[19:57] <kenvandine> indeed
[20:01] <desrt> czajkowski: there is a good chance that Riddell is still in the hospital
[20:02] <czajkowski> desrt: still..poked one of the other kubuntu council folks, but thanks
[20:06] <BigWhale> Hmm, what do do with old bugs that were tied to a functionality that is not supported anymore?
[20:08] <BigWhale> mark them as invalid?
[20:10] <micahg> BigWhale: depends if they qualify for SRU or not
[20:10] <BigWhale> SRU?
[20:10] <dobey> bugs in ubuntu, or bugs in your app?
[20:10] <BigWhale> bugs in my app
[20:10] <BigWhale> :)
[20:11] <dobey> then whatever you want to do with them
[20:11] <BigWhale> sorry, forgot to mention. I was asking in a general matter
[20:11] <dobey> your app, your bugs. make a decision :)
[20:11] <BigWhale> dobey, I'd like to stick as close to the ubuntu practise
[20:11] <BigWhale> that's why I am asking
[20:12] <dobey> then decide what you want to provide support for, and how you want to deal with that support. 5 years is a long time to support something
[20:12] <dobey> heck, 18 months is a long time to support something
[20:14] <BigWhale> dobey, indeed. That is why I wanted to get rid of some features that were now present, but not working as they should and start clean. and reimplement those things during this LTS cycle
[21:39] <dobey> kenvandine: around?
[21:41] <kenvandine> dobey, for a few minutes :)
[21:41] <kenvandine> what's up
[21:47] <dobey> kenvandine: i'm wondering about transitional packages
[21:47] <dobey> kenvandine: and if i should bother with them, for some changes in libubuntuone
[21:47] <kenvandine> examples?
[21:48] <kenvandine> they are often needed
[21:48] <dobey> so the 2.99.2 release of libubuntuone drops the static python bindings, and the mono bindings. it's still gtk2-only, but it's the start of the move to gtk3 support
[21:49] <kenvandine> ah
[21:50] <dobey> should i provide empty packages for those, or just add Breaks: for them to the lib package or something?
[21:50] <kenvandine> i think breaks
[21:51] <Laney> no more banshee store then?
[21:51] <kenvandine> will the static bindings work if the older version of the lib is installed?
[21:54] <dobey> kenvandine: yes, but you can't both versions of the lib installed. the api and soname are still the same
[21:54] <kenvandine> ugh
[21:55] <kenvandine> so actually the static bindings will still work?
[21:55] <dobey> well in so much as you can't use them for anything useful now, sure
[21:56] <dobey> well, we removed them from trunk, so there are no more static python bindings in trunk
[21:56] <kenvandine> dobey, so perhaps the package can just stop producing that binary package
[21:56] <dobey> (or in 2.99.2)
[21:56] <kenvandine> is that python-ubuntuone-client ?
[21:56] <dobey> python-ubuntuone
[21:57] <kenvandine> nothing seems to depend on it
[21:57] <dobey> right
[21:57] <kenvandine> but apps do depend on python-ubuntuone-client
[21:57] <dobey> yes, which comes from ubuntuone-client
[21:57] <kenvandine> ok, so that isn't affected?
[21:57] <dobey> no
[21:58] <kenvandine> ok, so i think a breaks and replaces will probably be enough
[21:58] <kenvandine> sometimes you need to throw in a conflicts, but i can never remember the cases where you need that :)
[21:58] <dobey> actually i guess i should put the breaks/rpelaces for that on the gir package?
[21:59] <kenvandine> yeah
[22:00] <kenvandine> maybe the library too, since that is what people will already have installed
[22:00] <kenvandine> dobey, i'll be out tomorrow, but have seb128 review it
[22:00] <dobey> ok
[22:00] <kenvandine> he knows the cases where you need the conflicts too
[22:01] <kenvandine> s/too/better than i/
[22:03] <dobey> maybe i'll just go watch BttF 2 for now, and ask him tomorrow :P
[22:03]  * kenvandine heads out 
[22:04] <dobey> thanks kenvandine
[22:04] <kenvandine> anytime
[22:53] <desrt> mterry: hey
[22:54] <mterry> desrt, heyo!
[22:54] <desrt> mterry: having some weird dejadup issues
[22:54] <desrt> since changing to ubuntu, whenever my backup tries to start i get the dialog asking me my password
[22:54] <desrt> i enter the password
[22:55] <desrt> then.... (short pause)... i get the dialog asking me my password
[22:55] <desrt> repeat
[22:56] <mterry> desrt, OK.  It's more likely that DD is being bonkers than that you're continually entering the wrong password
[22:56] <mterry> desrt, if you could run DD in a console with DEJA_DUP_DEBUG=1, then you should be able to see the response we're getting from duplicity
[22:56] <mterry> Which should give a hint
[22:57] <desrt> okay
[22:57] <mterry> run DEJA_DUP_DEBUG=1 deja-dup --backup
[22:57] <desrt> i'll do that when i get home tonight
[22:57] <mterry> desrt, cool, thanks
[22:57] <mterry> desrt, I should still be online
[23:41] <Riddell> czajkowski: pong
[23:42] <Riddell> desrt: I'm out of hospital (don't you read my blog!)
[23:49] <chrisccoulson> lol - https://twitter.com/#!/MCHammer/status/159747504433401857/photo/1