[00:32] <RAOF> Oh, damn.  Alioth's broken again, isn't it.
[00:33]  * RAOF gardens the SRU queue instead.
[00:40] <TheMuso> lol
[00:53] <RAOF> Changing my boot sequence by means of installing an SSD has exposed an absolutely superb bug - hardware initialisation on this hybrid laptop is not deterministic, and the radeon card comes up first now.  Plymouth eagerly throws up the cryptsetup prompts on fb0, provided by radeon.
[00:54] <RAOF> There's only one problem: the radeon card isn't connected to any outputs, so those cryptsetup prompts sit happily in VRAM :)
[00:56] <TheMuso> lol
[00:57] <TheMuso> Thats awesome~!
[01:05] <RAOF> The kernel knows about this, too; once i915 is loaded, the kernel goes ‘Oh, whoops.  The primary console's actually on fb1, chaps, as it's conceivable that the user might be able to see it’.
[01:05] <lifeless> RAOF: \o/
[01:05] <RAOF> Not in so many words, though, because kernel developers are uncouth oafs!
[01:06] <TheMuso> lol
[01:06] <lifeless> RAOF: ITYM uncouth aufs
[01:07] <lifeless> :P
[01:07] <lifeless> TheMuso: what sound do you get for :P ?
[01:07] <RAOF> :P
[01:08] <TheMuso> lifeless: Literally how it is written.
[01:08] <RAOF> colon-P?
[01:08] <TheMuso> Yes.
[01:08] <RAOF> There's a joke in there, if you've got the scope to find it.
[01:09] <lifeless> groan
[01:09] <TheMuso> RAOF: In other news, I think I had a GPU lockup earlier with nouveau, to the point where speech was still reading activity in the channel, but I got no keyboard and no mouse, and no changes on the screen. I couldn't even switch to a VT...
[01:10] <RAOF> TheMuso: Any trigger you could identify?
[01:11] <TheMuso> RAOF: No, this is the first time this has ever happened, I was just in a terminal using irssi. Didn't bring up anything in particular, no Unity features fo any kind.
[01:12] <RAOF> Ok.  I think our ability to debug unreproducible nouveau hangs is somewhere between slim and none; if it happens again please pipe up, but I'm not sure I can do anything about a once-off.
[01:13]  * TheMuso nods, just thought I'd let you know.
[01:15] <RAOF> Thanks.
[01:16] <TheMuso> Probably won't happen again, since this is the first time in weeks that I have had one.
[01:16] <TheMuso> I.e the first time since I ever used nouveau with the NVIDIA GPU.
[01:17] <RAOF> That's nice to hear :)
[01:20] <TheMuso> Yeah.
[01:23] <micahg> RAOF: any idea about my issue?
[01:24] <RAOF> Sorry, that's dropped out of my context.
[01:24] <RAOF> What was it again? :)
[01:43] <desrt> very quiet weekend it's been
[01:50] <RAOF> micahg: What was your problem again?
[01:51] <micahg> RAOF: external monitor won't stay on after upgrade to precise
[01:52] <RAOF> Ok.  It's a DisplayPort monitor, I take it?+
[01:52]  * micahg isn't sure
[01:52] <RAOF> What does the plug look like? :)
[01:52] <micahg> DVI
[01:53]  * RAOF is surprised.
[01:53] <RAOF> Do you have a bug report with more details, or shall I quiz you here?
[01:53] <micahg> no bug report yet
[01:53] <micahg> just upgraded 2 hours ago
[01:54] <desrt> micahg: i'd love to know the circumstances of your confusion :)
[01:54] <micahg> oh, I'm not familiar with X terminology
[01:54] <desrt> ahh
[01:54] <desrt> displayport is just another connector type
[01:55] <RAOF> micahg: What's the GPU?  Intel, ATI, nVidia?
[01:55] <micahg> nVidia
[01:55] <RAOF> And we're talking about the nouveau drivers, not the nvidia binary drivers++
[01:55] <RAOF> ?
[01:55] <micahg> GeForce GTX 460M
[01:55] <micahg> binary nvidia
[01:55] <RAOF> Poot.
[01:56] <micahg> am I better off with nouveau?
[01:56] <RAOF> Maybe.
[01:56] <RAOF> There are definitely tradeoffs involved.
[01:56] <desrt> depends on how you feel about global warming :)
[01:57] <micahg> is there an easy way to make that switch?
[01:57] <desrt> micahg: jocky is probably the easiest way
[01:57] <RAOF> Right.  Nouveau doesn't do reclocking (although this is now enabled in git).  If your BIOS brings the card up in the lowest power state (most do) then you'll have reasonable power consumption.  If your BIOS brings up the card in the high-power state it'll eat electrons like candy.
[01:57] <desrt> 'additional drivers' in the system settings
[01:58] <micahg> umm, jockey shows me 2 proprietary drivers :(
[01:58] <RAOF> Yeah.  “Additional drivers” is easiest.  You can also go manually fiddling around with update-alternatives if you want.
[01:58] <desrt> micahg: disable them!!!
[01:58] <RAOF> Disabling the proprietary driver will get you to the default (ie: open-source nouveau)
[01:58] <desrt> (says the free-software muse sitting on your left shoulder)
[01:59] <desrt> micahg: other one is... wifi?
[01:59] <micahg> it tells me it's required if I want to run unity :)
[01:59] <RAOF> It's lying.
[01:59] <desrt> micahg: that's probably not true
[01:59] <RAOF> We might want to reword that :)
[01:59] <micahg> wifi is enabled, but not active
[01:59] <desrt> although your unity experience will likely suffer
[01:59]  * micahg has been using unity-2d anyways, so not likely :)
[02:00] <RAOF> Maybe.  You'll find that smspillaz runs nouveau in part because he hits fewer 3D bugs on it :)
[02:00]  * desrt notes that the jockey UI looks quite ugly when no proprietary drivers are installed/needed
[02:02]  * micahg tries a reboot
[02:02] <RAOF> Yup, that's easiest
[02:05] <mdeslaur> jockey could use some usability love
[02:08]  * RAOF notes the ominous lack of micahg
[02:08] <jbicha> lol
[02:09] <mdeslaur> micahg: welcome back, we were worried
[02:09]  * desrt files scathing UI review against jockey
[02:09] <desrt> bad jockey
[02:09] <micahg> umm, well, got a low graphics warning
[02:09] <micahg> seems fine now, I can see the screen, but it still won't stay on
[02:10] <RAOF> It turns on, displays something, and then turns off after a while?
[02:11] <micahg> yeah, if I power cycle it, it shows the screen and then goes black
[02:12] <RAOF> That's…
[02:12] <RAOF> Um.
[02:12] <mdeslaur> *cough* hardware issue *cough*
[02:12] <RAOF> Does the screen give a warning message?
[02:13] <RAOF> There would seem to be two obvious options here: (1) the display clocks are drifting, and after a while they've drifted too far for the display to sync, or (2) for no obvious reason both drivers are sending DPMS off requests.
[02:14] <micahg> no warning issue, this happened right after I upgraded
[02:14] <RAOF> Can I get an Xorg.0.log please?
[02:14] <RAOF> And, hey, lets throw in a dmesg for good measure.
[02:17] <micahg> RAOF: e-mailed
[02:22] <RAOF> Hm.  There's nothing particularly odd there, apart from the bit where it changes from cloned → spanned → cloned → spanned.
[02:22] <micahg> I"m going to try in anotherWM
[02:23] <micahg> brb
[02:23] <RAOF> Fair call.
[02:36] <micahg> ok, I don't know where my VGA cable is right now so I can test this with another machine
[02:37] <micahg> I'll have to resort to single monitor mode until I find it I guess
[02:38] <RAOF> The other thing to check would be that the kernel framebuffer is cloned across the monitors.
[02:38] <micahg> same thing in Xubuntu with metacity and unity-3d as well
[02:38] <RAOF> But this is not exactly a common failure mode :)
[02:38] <micahg> how do I do that?
[02:39] <RAOF> Boot into recovery mode, but remove the “nomodeset” from the kernel command line.
[02:39] <RAOF> That should get you the kernel VT, spanned across both monitors.
[02:39] <micahg> why do I need recovery mode for that?
[02:41] <RAOF> Just to stop X starting.
[02:42] <RAOF> That'll remove any possibility of the X driver sending a DPMS off signal or something.
[02:42] <micahg> then how can I test it?
[02:42] <RAOF> The kernel should bring up *both* displays, cloned.
[02:42] <micahg> ah, ok
[02:42] <micahg> brb
[02:42] <desrt> RAOF: i don't recall if we've had this conversation before
[02:43] <desrt> RAOF: is there a way to use xinput to change my laptop's trackpad into an absolute-movement touch device?
[02:43] <RAOF> I don't think we've had that conversation before, and I don't *think* so.
[02:44]  * desrt installed some weird evdev-consuming driver once that did something like this
[02:44] <desrt> it was pretty flaky, though
[02:44] <RAOF> Yeah, with uinput you could do that.
[02:45] <RAOF> pull the evdev events out of the kernel, feed them back in after flipping the absolute bit.
[02:45] <RAOF> Huh.  You could also do that with XTest if you felt the need.
[02:45] <RAOF> desrt: Need to do some testing of absolute devices?
[02:45] <desrt> RAOF: i'm trying to test the gtk multitouch branch
[02:46] <desrt> after some recent X updates it looks like it compiles at least
[02:46] <RAOF> Yeah, the Xserver 1.11 transition included the 1.12 input stack, ie: Xi 2.2 ie: multitouch.
[02:46] <RAOF> Which is what that branch will have been written against.
[02:47] <desrt> it was missing some constants in the headers for a while
[02:47] <desrt> so the thing compiles now, but it appears not to allow me to interact with my trackpad in any useful way
[02:47] <RAOF> You were seeing the prototype, Ubuntu-only, multitouch protocol.
[02:47] <RAOF> Huh.
[02:47] <RAOF> Oh, yeah.
[02:48] <RAOF> synaptics is currently not doing multitouch - Chase is on it.
[02:48] <desrt> ah.  that'll explain it
[02:48] <desrt> meanwhile i have no way to test :)
[02:48] <desrt> maybe i should throw precise on my exopc
[02:48] <RAOF> Yeah.
[02:49] <RAOF> If that uses evdev it should multitouch (I believe)
[02:49] <desrt> it works on fedora
[02:49] <desrt> there's a reasonable chance that this branch could land this cycle
[02:49] <desrt> so i want to make sure that doesn't cause any crisis on ubuntu
[02:49] <RAOF> The multitouch does?  Then it'd work on Ubuntu, too.
[04:56] <desrt> does anyone have a concept of how stable precise is in terms of server-side?
[04:56] <desrt> like, i guess there may be a new kernel or something coming
[04:57] <desrt> but presumably not major new versions of core system components
[05:30] <pitti> Good morning
[05:32] <desrt> pitti: hello
[05:32] <desrt> good weekend?
[05:33] <pitti> pretty relaxed, yes; and you?
[05:33] <desrt> pretty decent.  saw lots of old friends.  ate too much, i think.
[05:33] <TheMuso> Morning pitti.
[05:33] <pitti> hey TheMuso, how are you?
[05:34] <TheMuso> pitti: Not too bad thanks, yourself?
[05:34] <pitti> TheMuso: pretty well, thanks!
[05:56] <desrt> hum
[05:57] <desrt> launchpad email appears to have become useful while i wasn't looking
[06:00] <RAOF> Ha!
[06:00] <desrt> relatively useful?
[06:01] <desrt> you used to get emails from every single event that was vaguely related to any team that you were on and the only way to stop them was to leave the team...
[06:01] <pitti> it still sends out a lot of unwanted ones, but for bug mail they are quite useful indeed
[06:01] <desrt> it seems to only send me mails that are actually relevent to me now
[06:01] <pitti> desrt: you can configure it a lot more these days, too
[06:01]  * desrt had redirected all launchpad emails to his spam folder for some time
[06:02] <desrt> only looked now to find out that it doesn't send nearly as many as it used to
[06:44] <pitti> robert_ancell: hey Robert, how are you?
[06:45] <robert_ancell> pitti, good
[06:45] <pitti> robert_ancell: do you know what creates /etc/lightdm/lighthdm.conf? Is that only ubiquity?
[06:45] <pitti> I don't see anything in lightdm's postinst for this
[06:45] <robert_ancell> pitti, yes, it should be that way now
[06:45] <pitti> robert_ancell: i. e. if it does not exist at all, lightdm still works
[06:46] <pitti> robert_ancell: I want to tackle bug 854431 now
[06:46] <ubot2`> Launchpad bug 854431 in lightdm "GDM automatic login is not transitioned to lightdm automatic login" [High,In progress] https://launchpad.net/bugs/854431
[06:46] <robert_ancell> right
[06:46] <pitti> robert_ancell: i. e. if lightdm gets installed during upgrade, there will be nothing writing the conffile
[06:46] <pitti> robert_ancell: so if it's not there, I'll create one based on gdm custom.conf
[06:47] <robert_ancell> pitti, yes I think that's correct, but you might want to confirm with didrocks as he did a lot of work in that area
[06:47] <pitti> robert_ancell: I took that bug from you, if that's alright with you?
[06:47] <pitti> (unless you want to work on it today)
[06:47] <robert_ancell> pitti, I never complain if people take my bugs :)
[06:47] <pitti> but I'd like it to be in a2
[06:51] <pitti> greeter-session=unity-greeter
[06:51] <pitti> user-session=ubuntu
[06:51] <pitti> robert_ancell: ^ are these two internal defaults?
[06:51] <pitti> robert_ancell: or do I need to set them if lightdm.conf exists?
[06:52] <pitti> robert_ancell: i. e. would it be better to set them or should it only have autologin-user= ?
[06:53] <robert_ancell> pitti, from debian/rules: dh_auto_configure -- --with-greeter-user=lightdm --with-user-session=ubuntu
[06:53] <robert_ancell> I'm trying to work out what sets unity-greeter in there...
[06:53] <pitti> robert_ancell: well, it needs to do something sensible if there is no lightdm.conf at all, so I guess it's ok
[06:53] <pitti> robert_ancell: that's in unity-greeter.postinst
[06:53] <robert_ancell> pitti, ah right, it's done by /usr/lib/lightdm/lightdm-set-defaults in the unity-greeter postinst
[06:53] <pitti> /usr/lib/lightdm/lightdm-set-defaults --keep-old --greeter=unity-greeter
[06:55] <robert_ancell> right, so that just needs patching to handle the autologin user
[06:55] <pitti> robert_ancell: I'll add autologin support to lightdm-set-defaults upstream and backport it
[07:40] <didrocks> good morning
[07:41] <pitti> bonjour didrocks
[07:41] <pitti> ca va?
[07:41] <didrocks> guten morgen pitti! ça va bien, et toi? :)
[07:41] <pitti> je suis bien, merci!
[07:47] <pitti> didrocks: "Make some promotion on user test cases once the tools are ready" (amber graner), do you happen to know whether this happened?
[07:48] <didrocks> pitti: no, it didn't. I warned her that she can do some in uwn
[07:49] <pitti> didrocks: ok, thanks
[07:51] <pitti> didrocks: for the tarmac integration, would you call this done now? (description is fuzzy), or do you plan to do more?
[07:52] <didrocks> pitti: I wanted to add more at first, but it's a little bit difficult to progress on it right now socially speaking…
[07:53] <pitti> didrocks: at least it seems to do its main job now?
[07:53] <didrocks> pitti: yeah, it does
[07:54] <pitti> didrocks: so, perhaps we should call it done now, and you add a new WI for beta-1 with a more specific name if you want to add something?
[07:54] <didrocks> pitti: oh, you are speaking about the autopilot?
[07:54] <didrocks> or the "additional tarmac facility"
[07:54] <pitti> "Help on the tarmac autopilot integration"
[07:54] <didrocks> pitti: no, this one is blocked. I tried to bring the subject back on the table twice
[07:54] <didrocks> but no reaction from the third involved party
[07:55] <didrocks> so I would say "blocked" on my side
[07:55] <pitti> didrocks: ok, updating status and moving to b1
[08:11] <pitti> rodrigo_: good morning, how are you?
[08:11] <rodrigo_> hi pitti
[08:12] <pitti> rodrigo_: would it help you if I upload packagekit with the new LANGUAGE_SUPPORT enum backported?
[08:12] <pitti> rodrigo_: I also did a few other fixes upstream which make "pkcon what-provides" work on the command line, which makes testing easier
[08:12] <rodrigo_> pitti, yes, i already have it on my jhbuild setup, but yes, do it, it will be helpful
[08:13] <rodrigo_> I will push my g-c-c branch later today, just a couple things to finish
[08:13] <pitti> rodrigo_: I haven't implemented it in aptdaemon yet, as glatzor wanted to add plugin support first
[08:13] <pitti> rodrigo_: but I wondered whether you actually test against packagekit itself, or aptdaemon-pkcompat?
[08:14] <rodrigo_> pitti, since I hadn't finished it, I was just compiling against my PK branch
[08:14] <pitti> rodrigo_: ok, that's fine
[08:15] <pitti> rodrigo_: are you using the aptcc or the apt backend?
[08:15] <pitti> rodrigo_: as the apt backend currently just crashes if you try WhatProvides(); I fixed that in trunk, too, and will backport it along
[08:16] <rodrigo_> pitti, hmm, aptcc
[08:17] <pitti> rodrigo_: ok; we can't really implement it there, I think glatzor wants to switch back to "apt" as default
[08:17] <tkamppeter> pitti, hi
[08:17] <pitti> hey tkamppeter, guten Morgen
[08:18] <pitti> tkamppeter: FYI, I did a few changes to cups and cups-filters, but can't push my branch (alioth is down again)
[08:18] <pitti> tkamppeter: if you want to work on it, please ping me, I can put it on LP
[08:19] <tkamppeter> pitti, why did you change the milestone of the cups task in bug 885324? I have fixed this.
[08:19] <ubot2`> Launchpad bug 885324 in imagemagick "Completely replace lcms1 by lcms2 in Ubuntu" [Undecided,In progress] https://launchpad.net/bugs/885324
[08:20] <pitti> tkamppeter: hm, cups still depends on liblcms1
[08:20] <pitti> tkamppeter: and today is alpha-2 freeze
[08:20] <pitti> tkamppeter: oh, it's in cups-filters now, I see
[08:20] <tkamppeter> pitti, what makes cups depending on liblcms1?
[08:21] <pitti> tkamppeter: that was still -15, sorry
[08:21] <pitti> I'll update the bug
[08:21] <tkamppeter> pitti, already done.
[08:21] <pitti> tkamppeter: ah, you already did; moved back the milestone
[08:22] <pitti> rodrigo_: btw, I had to "git merge master" in your branch to build it (failed on wacom stuff)
[08:22] <pitti> then it worked fine
[08:24] <rodrigo_> pitti, oh, already did it over the weekend
[08:24] <rodrigo_> pitti, did you push?
[08:24] <pitti> rodrigo_: no, just locally for testing
[08:24] <rodrigo_> ok
[08:25] <pitti> I really don't want to mess up your branch :)
[08:25] <rodrigo_> :)
[08:28] <pitti> rodrigo_: BTW, does that automatically configure the default ibus module?
[08:28] <pitti> language-selector still has an explicit combobox for this
[08:28] <pitti> but I don't know enough about this to say whether it should be there or nor
[08:29] <pitti> Chinese people tend to use different modules, though
[08:35] <rodrigo_> pitti, hmm, not sure
[08:39] <tkamppeter> pitti, thanks for the quick switchover to the new cups/cups-filters packages.
[08:42] <BigWhale> Morning.
[08:52] <pitti> mvo: can I get the "system architecture" from python-apt somehow, or do I need to call dpkg --print-architecture?
[08:56] <mvo> pitti: python -c 'import apt_pkg; print apt_pkg.get_architectures()'
[08:56] <pitti> >>> apt.apt_pkg.get_architectures()
[08:56] <pitti> ['amd64', 'i386']
[08:56] <mvo> pitti: eh, actually this needs a apt_pkg.init() first (or apt does this implicitely for you) :)
[08:57] <pitti> mvo: can I rely on the first one being the native system one, or is that just ordered alphabetically?
[08:57] <mvo> pitti: yeah, thats the one - the first is the native one
[08:57] <pitti> mvo: sweet, thanks!
[08:57] <mvo> yw
[09:07] <seb128> hey
[09:08] <pitti> bonjour seb128
[09:08] <didrocks> salut seb128
[09:08] <chrisccoulson> good morning everyone
[09:09] <seb128> hey guys
[09:09] <seb128> how are you?
[09:09] <pitti> quite fine, thanks!
[09:19] <BigWhale> is Precise stable enough to be used as development platform? :>
[09:21] <pitti> BigWhale: it's our mission to keep it working and upgradeable every day
[09:21] <pitti> and we use a lot more staging these days for pre-upload testing
[09:21] <pitti> BigWhale: so I'd say yes
[09:21] <pitti> errors still happen, of course, but it feels a lot more stable than earlier releases
[09:22] <pitti> even according to non-developers like rickspencer3 :)
[09:23] <BigWhale> I'm thinking about upgrade ...
[09:23] <BigWhale> How's with restricted graphics drivers? fglrx, to be more exact.
[09:24] <BigWhale> hm drrmd yo nr rok
[09:25] <BigWhale> err... seems to be ok
[09:25] <pitti> BigWhale: yes, nvidia-current works; -173 and -96 don't
[09:26] <chrisccoulson> hey seb128, didrocks, pitti, how was your weekend?
[09:26] <didrocks> chrisccoulson: it was nice, quite quiet because of the weather, but nice, yours?
[09:26] <seb128> quite good, lot of doing nothing, i.e tv and video games ;-)
[09:27] <seb128> what about you?
[09:27] <chrisccoulson> didrocks, yeah, mine was not too bad, although i did work yesterday to get the firefox / thunderbird 10 releases ready
[09:27] <chrisccoulson> seb128, sounds like you had quite a relaxing weekend ;)
[09:27] <didrocks> oh, that's why you blogged about it :)
[09:27] <seb128> indeed
[09:28] <chrisccoulson> didrocks, yeah :)
[09:28] <pitti> chrisccoulson: very relaxed, thanks! wanted to go for some cross-country skiing, but not quite enough snow here yet, so we just went for a long walk
[09:30] <seb128> pitti, for the full source vcs-es like dx components or lightdm you can bzr merge a revision, it's easier than using the patch system
[09:30] <seb128> pitti, next bzr merge-upstream will ignore the commit backported, or rather deal with it, so no added a patch and reverting later
[09:30] <pitti> seb128: ah, I see; I actually started with bzr merge -c
[09:30] <seb128> it's just a "one comamnd, one time"
[09:30] <pitti> seb128: but then saw that there was a debian/patches/
[09:30] <seb128> the patches dir is useful for stuff not coming from the upstream vcs
[09:30] <seb128> like real distro diff
[09:30] <pitti> seb128: ok; will remember next time
[09:30] <seb128> ok ;-)
[09:30] <seb128> well it works also your way, it's just extra work
[09:35] <BigWhale> pitti, ah well, I'll just run an upgrade and see what happens :>
[10:07] <Daviey> Anyone happen to know how to change the keybinding for HUD, for it not to steal alt?
[10:13] <didrocks> Daviey: there is the option on ccsm to assign any keybinding you want
[10:14] <didrocks> (not tested there though)
[10:14] <pitti> I thought that package was unspeakable now
[10:17] <didrocks> pitti: it is, but I can give the gconf key as well :) I trust Daviey to not go crazy on ccsm options
[10:34] <BigWhale> Random trivia: during an upgrade to precise, unity will die and you will end up with all the windows crammed on one screen with no means to move them. quite funny. :>
[10:35] <BigWhale> I'll wait for an upgrade to finish :>
[10:55] <Daviey> didrocks: heh, thanks!
[10:55] <didrocks> Daviey: yw ;)
[11:04] <geser> what's the default terminal background in precise? dark or light?
[11:06] <agateau> hey, does this kind of build error messages ring a bell to any of you: "/bin/sed: can't read /usr/lib/libgtk-3.la: No such file or directory", while trying to build indicator-appmenu on precise
[11:07] <geser> find out which dependencies pulls this in and that one needs fixing
[11:13] <agateau> oneiric package for libgtk-3-dev shipped it, but it does not anymore
[11:22] <pitti> agateau: package was multiarched, it's in (e. g.) /usr/lib/x86_64-linux-gnu/libgtk-3.a now
[11:22] <pitti> agateau: ah, ignore me; .la files are obsolete
[11:23] <pitti> agateau: if some package needs them, please stop that from shipping a .la file, too
[11:23] <agateau> pitti: mmm, I am not sure I know how to do this
[11:23]  * agateau digs into indicator-appmenu build files
[11:23] <geser> my guess: an other .la file still mentions it
[11:24] <seb128> what's the issue?
[11:24] <geser> install the build-depends and grep the .la files for it
[11:24] <pitti> $ find /usr/lib -name '*.la' | xargs grep gtk-3
[11:24] <pitti> $
[11:24] <geser> seb128: FTBFS due to mentioning a non-existant .la file
[11:24] <pitti> agateau: nothing here; can you run this on your boxZ?
[11:25] <agateau> seb128: "/bin/sed: can't read /usr/lib/libgtk-3.la: No such file or directory", while trying to build indicator-appmenu on precise
[11:25] <pitti> agateau: also run it on /usr/local/lib, to be sure
[11:25] <pitti> agateau: often this happens if you do a "make install" from e. g. trunk into /usr/local/
[11:25] <agateau> pitti: what is "boxZ"?
[11:25] <pitti> agateau: "box"
[11:25] <pitti> like "computer"
[11:26] <agateau> pitti: uh ok, I thought it was another tool I didn't know about :)
[11:26] <seb128> agateau, likely a local build, grep for /usr/lib/libgtk *.la in your local build dirs
[11:27] <agateau> could be indeed, the find returns a bunch of libdummy-indicator-*.la files
[11:27]  * agateau rms
[11:27] <agateau> I mean rm them
[11:31] <geser> seb128: do you know if the default terminal background (as we ship it) is dark or light?
[11:31] <seb128> geser, ?
[11:31] <seb128> what do you mean?
[11:31] <seb128> open a guest session and try? ;-)
[11:31] <geser> in Gnome terminal, the background color
[11:31] <seb128> no idea but it seems trivial to test
[11:32] <geser> ok, will try it out then
[11:32] <seb128> though I think the current version is buggy
[11:32] <seb128> chrisccoulson or somebody made it ubuntuish some cycles ago and that has been dropped or broken it seems
[11:32] <mpt> pitti, hi, where can I find a complete list of the drivers that Jockey handles? I've found examples/handlers/, but presumably those are only examples. (This is for the desktop-p-control-center-cleanup work item "Design a replacement for the Jockey interface ready to implement in Q".)
[11:33] <geser> there is vim bug asking to "set background=dark" by default (which only works if we have a dark terminal by default)
[11:33] <seb128> geser, the default seems to be to follow the system theme
[11:34] <agateau> seb128: pitti: ok, problem fixed by removing those manually installed .la files. Thanks for the help!
[11:34] <seb128> agateau, yw
[11:34] <geser> and the default system theme stays like it is or are there any changes planned?
[11:35] <seb128> there is not only one theme, there are 2 themes
[11:35] <seb128> they will not change this cycle afaik
[11:35] <seb128> but you need to make sure it works with the light theme as well I guess
[11:37] <manish> is there a vapi file for gnome control center? Anyone knows how to integrate an applet inside g-c-c?
[11:37] <geser> that's my fear that there is no default which works in every case (GNOME, KDE and the other variants)
[11:38] <seb128> manish, GNOME doesn't allow integration in g-c-c, so if you do that your code will be Ubuntu specific
[11:38] <seb128> manish, you can look at deja-dup as an example
[11:38] <manish> seb128: in this case a new window opens up
[11:38] <manish> I want it to behave like bluetooth, displays etc
[11:38] <manish> not possible?
[11:39] <seb128> manish, in Ubuntu you can, upstream you can't
[11:39] <manish> seb128: I am working on activity-log-manager g-c-c integration
[11:39] <manish> so this means there needs to be an ubuntu specific patch
[11:40] <seb128> manish, oh, then libgnome-control-center-dev
[11:40] <seb128> manish, check /usr/include/gnome-control-center-1/libgnome-control-center/cc-panel.h
[11:40] <seb128> manish, you can use deja-dup as a code example, it does integrate there
[11:40] <manish> yup
[11:40] <manish> that's the file I am looking at
[11:40] <manish> yup, but I am writing alm in vala, so need the vapi file
[11:40] <manish> thanks, checking deja-dup
[11:40] <seb128> oh
[11:41] <manish> thanks for you help, only 2 weeks left and this work is not finished, but activity-log-manager gtk3 port is done
[11:41] <seb128> manish, in fact deja-dup is doing it in C, I guess you can either do that part in C or hack a local vapi...
[11:42] <manish> yup, I am not very good at vala either, this was my first work in vala. Will copy the integration part from deja-dup
[11:42] <seb128> ok
[12:23] <soren> Where does the font settings thing live nowaways?
[12:24] <seb128> soren, in gsettings
[12:24] <soren> Ah, so no UI?
[12:24] <seb128> you can "zoom the text" in the a11y control panel
[12:25] <seb128> but otherwise no
[12:25] <seb128> GNOME considers the font as part of the branding
[12:25] <seb128> so they just give you the ability to zoom if you want bigger or smaller text
[12:26] <soren> Hm. OK.
[12:26] <soren> Where in gsettings can I fiddle with this?
[12:30] <soren> org.gnome.desktop.interface
[12:30] <soren> Found it.
[12:43] <mdeslaur> seb128: I spent the weekend on screen locking. suspend/resume should be consistent with autologin now, both in gnome-shell and unity. Also, auth dialog should consistently appear after resume now, and another bug squashed that preventing locking from working in certain situations.
[12:46]  * didrocks no X anymore…
[12:46] <soren> didrocks: It's overrated anyway.
[12:47] <didrocks> soren: yeah, quite annoying for releasing unity though :)
[12:52] <seb128> mdeslaur, thanks a lot !
[12:52] <mdeslaur> seb128: np, let me know if I broke anything
[12:54] <seb128> mdeslaur, oh sure, I can do that ;-)
[12:54] <mdeslaur> seb128: hehe
[13:03] <jbicha> good morning, I got nautilus working except that the Change Desktop Background and Ubuntu Documentation menu items don't show up
[13:03] <jbicha> it's in https://code.launchpad.net/~gnome3-team/nautilus/ubuntu if someone wants to look at it
[13:05] <seb128> hey jbicha
[13:05] <seb128> jbicha, you mean the unstable serie version? or is something broken in the precise version?
[13:06] <jbicha> seb128: 3.3.4
[13:18] <didrocks> Sarvatt: hey, can I bother you about a latest xorg + nvidia-current issue? :)
[13:19] <pitti> hello jbicha, how are you?
[13:20] <pitti> seb128: FYI, https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages has udisks2 now
[13:21] <pitti> seb128: it apparently still has some trouble with our udev version, though
[13:21] <pitti> seb128: I don't feel 100% sure about it yet
[13:23] <seb128> pitti, \o/
[13:23] <seb128> pitti, ok
[13:23] <pitti> jbicha: do you think we should do a freedrdp upload from the debian git now?
[13:23] <seb128> desrt was asking about it the other day
[13:23] <pitti> jbicha: seems it's stuck in Debian?
[13:24] <pitti> seb128: current g-d-u needs a new GTK
[13:24] <pitti> seb128: I think you were going to package this, according to your discussion with doko
[13:25] <pitti> seb128: when that's in, I can upload gdu to the PPA< too
[13:26] <seb128> pitti, there is no new gtk tarball yet, I think next GNOME tarballs are due next week, but I was pondering maybe backporting some fixes
[13:26] <seb128> we are not in an hurry though
[13:28] <jbicha> pitti: hi, I don't think the Debian maintainer is going to change the freerdp packaging much, it'd be gone to get the mir review completed
[13:29] <pitti> jbicha: "it'd be gone"?
[13:30] <pitti> jbicha: I'd like to add a Breaks:, but I can't commit it as alioth is down; but I could do it locally and upload to Ubuntu for now
[13:31] <pitti> seb128: do we want to go with gvfs 1.11? I can have a go at this now if you want
[13:32] <jbicha> *it'd be good
[13:32] <seb128> pitti, yes, since udisk2 is a new monitor it should be fine
[13:32] <seb128> there are quite some fixes and code cleaning for the new glib
[13:32] <seb128> so it would be good to get
[13:33] <pitti> seb128: roger that, I'll see how it works
[13:34] <seb128> pitti, danke
[14:00] <vuntz> pitti: hello and ping
[14:00] <pitti> bonjour vuntz, ca va?
[14:01] <vuntz> ja, sehr gut!
[14:01] <vuntz> pitti: I'm pushing wnck_shutdown() with my changes (in case you want to look at them)
[14:01] <pitti> vuntz: ah, did I mess up a lot?
[14:02] <vuntz> pitti: one quick question: is there any reason we call _wnck_select_input() with the orig event mask only for WnckWindow, and not for WnckScreen and WnckApplication?
[14:02] <vuntz> pitti: nah, it was good. I'm just cleaning things at the same time ;-)
[14:02] <pitti> vuntz: I don't know the original intent, I just mirrored what the previous code did (i. e. setting it vs. ORing it with the already existing mask)
[14:02] <pitti> vuntz: that might very well be an oversight, of course
[14:04] <vuntz> pitti: I mean, when shutting down. We set the mask to 0 for the root window of the WnckScreen and the window of WnckApplication
[14:04] <vuntz> or actually, we don't even set it back for WnckApplication
[14:06] <pitti> vuntz: I mean that e. g. wnck_screen_construct() just sets it to PropertyChangeMask instead of getting the old flags first and ORing them (as WnckWindow does)
[14:08] <vuntz> pitti: hrm, no, it's the same thing: the OR is done inside _wnck_select_input()
[14:09] <pitti> vuntz: ah, I misremembered, indeed; so I guess these should save/restore the original state, too
[14:09] <pitti> i. e. adding a priv->orig_event_mask
[14:09] <vuntz> ok, will fix it
[14:09] <vuntz> thanks!
[14:09] <pitti> vuntz: want me to update accordingly?
[14:09] <pitti> oh, ok
[14:11] <mpt> pitti, hi, did you see my question before about Jockey?
[14:12] <pitti> mpt: sorry, I didn't; was that here and today? I don't see it in backscroll
 pitti, hi, where can I find a complete list of the drivers that Jockey handles? I've found examples/handlers/, but presumably those are only examples. (This is for the desktop-p-control-center-cleanup work item "Design a replacement for the Jockey interface ready to implement in Q".)
[14:13] <pitti> mpt: /usr/share/jockey/handlers/ has the complete list
[14:14] <pitti> mpt: The most popular ones are NVidia in all its flavours, FGLRX, and the Broadcom wifi driver; we also support sl-modem, DVB USB firmware, and VMWare client tools
[14:14] <pitti> mpt: and then we look up printer drivers on openprinting.org
[14:15] <mpt> pitti, are printer drivers shown inside Jockey currently?
[14:15] <pitti> mpt: not if you open it through control-center, just if you plug in a new printer which doesn't have a packaged driver
[14:15] <pitti> (through system-config-pritner)
[14:16] <mpt> ok, thanks pitti
[14:21] <mpt> tkamppeter, hi, are the printer drivers downloaded from openprinting.org (a) all proprietary, (b) all open source, or (c) a mixture of proprietary and open source?
[14:21] <pitti> mpt: they can be, and are, both
[14:21] <mpt> ok
[14:22] <pitti> mpt: they tell us the license, though
[14:22] <pitti> jockey knows whether they are free software or not
[14:22] <mpt> And I guess that's (at least partly) why it's called "Additional Drivers" not "Proprietary Drivers" :-)
[14:23] <pitti> right :)
[14:23] <pitti> mpt: we also used it in e. g. natty for offering the experimental nouveau 3D drivers
[14:24] <mpt> pitti, so for some graphics cards there might be a choice of three drivers? (Stable OSS, experimental OSS, proprietary)
[14:25] <pitti> mpt: we don't have "stable OSS" drivers
[14:25] <pitti> these are "just there"
[14:25] <pitti> mpt: we used to have experimental/FOSS, but for precise we just have non-free ones
[14:25] <pitti> (for nvidia, that is)
[14:26] <pitti> the only free ones which we might have are the openprinting.org ones
[14:26] <mpt> pitti, what was nv then?
[14:26] <pitti> mpt: we never showed that
[14:26] <mpt> oh
[14:26] <pitti> you eitehr enabled nvidia or disabled it, in which case nv was used (or nouveau these days)
[14:26] <mpt> I see
[14:27] <pitti> I really wish we had something much simpler
[14:27] <pitti> I want to push down the "which driver do I need" logic into packagekit/aptdaemon, then we can use it easily from just about anywhere
[14:28] <pitti> mpt: for the broadcom wifi it's largely obsolete even -- it gets installed through ubiquity without asking if you need it, as there is no alternative
[14:28] <mpt> It might be interesting to have the graphics driver choice in the "Displays" settings for example
[14:28] <pitti> but for graphics drivers we actuallly do want the choice
[14:28] <mpt> pitti, whatever happened to Broadcom open-sourcing their driver? :-)
[14:28] <pitti> I don't know
[14:28] <ogra_> hey, dont forget arm :)
[14:29] <ogra_> we only have the choice between fully proprietary or raw framebuffer there
[14:29] <mpt> ok
[14:29] <ogra_> (and plan to move to jockey for that)
[14:29] <mpt> pitti, I see on Google Images that sometimes there's a choice between multiple versions of the Nvidia driver, too
[14:30] <pitti> mpt: yes, indeed, as they have several "series" of the driver
[14:30] <pitti> mpt: and to add to the confusion, we now have an "-updates" variant for nvidia and fglrx
[14:30] <pitti> i. e. in the end we have 6 nvidia drivers and two fglrx
[14:31] <pitti> a normal one, which pretty much stays what it is after release
[14:31] <pitti> and -updates gets updated to new upstream releases post-release, and thus might both bring you tremendously better support as well as completely brick your box
[14:31] <pitti> it's a little easier with fglrx
[14:32] <mpt> heh
[14:36] <mpt> So, even if we pushed graphic driver choice to the "Displays" settings, wifi/modem choice to the "Network" settings, and printer driver choice to the "Printers" settings ... there would still be VMWare, and and DVB-USB, and other categories that might come along in future (e.g. bug 177355)
[14:36] <ubot2`> Launchpad bug 177355 in jockey "Fetch scanner firmware" [Wishlist,Confirmed] https://launchpad.net/bugs/177355
[14:36] <mpt> so we'd need a general-purpose interface for them anyway
[14:36] <pitti> mpt: potentially yes
[14:37] <kenvandine> good morning everyone!
[14:37] <pitti> hey kenvandine, had a nice weekend?
[14:37] <kenvandine> very, and you?
[14:37]  * kenvandine spent lots of quality time running gwibber in valgrind and fixed the memory leaks :)
[14:38] <pitti> heh, I just spent an hour packaging cups-filters, and otherwise was pretty lazy
[14:38] <kenvandine> lazy is good :)
[14:38] <BigWhale> quality times with debuggers are the best kind! :>
[14:38] <pitti> we did a nice walk through the snow, I finished reading my current book, and we went out dancing again on Saturday
[14:38] <kenvandine> awesome
[14:38] <pitti> it's been a while since I went to bed at 3:30 pm :)
[14:38]  * kenvandine wants to see some snow
[14:39] <chrisccoulson> me too!
[14:39] <kenvandine> we keep having these 70F days here... doesn't feel like winter
[14:39] <BigWhale> kenvandine, we had 1/4" yesterday... gone now tho ... :>
[14:44] <BigWhale> oooh, I like new scrollbars
[14:55] <pitti> seb128: gvfs 0.11.2 uploaded; this does not have support for udisks2 yet
[14:57] <pitti> vuntz: ah, thanks for adding the test-shutdown thingy, that makes it easier to find
[14:59] <seb128> pitti, \o/
[15:03] <vuntz> pitti: you should probably double check I didn't break things and that there's still no wakeup ;-)
[15:05] <pitti> vuntz: confirmed, still working as expected
[15:08] <vuntz> pitti: thanks!
[15:08] <vuntz> */W 1
[15:09] <desrt> vuntz: hey :)
[15:11] <vuntz> desrt: ola!
[15:12] <desrt> vuntz: what've you been up to?
[15:13] <vuntz> desrt: some opensuse stuff, lately
[15:14] <jbicha> kenvandine: lol, it's supposed to be winter still? I at least saw some frost this morning
[15:14] <desrt> vuntz: is it taking over your life to the same degree as gnome did? :)
[15:14] <kenvandine> jbicha, this morning it was close to freezing, but it is going to jump back up to 70 tomorrow
[15:15] <vuntz> desrt: nah, I'm actually using more time for life nowadays :-)
[15:15] <vuntz> desrt: coming to Brussels?
[15:15] <desrt> no.
[15:16] <desrt> hard to justify the trip for just 2 days, you know
[15:16] <kenvandine> vuntz, i'm updating the gwibber NEWS file :)
[15:16] <desrt> if didrocks was still in paris, i'd probably have visited him on the side of the trip as a reason to make it worthwhile
[15:16] <vuntz> kenvandine: :-)
[15:16] <vuntz> desrt: shame
[15:16] <didrocks> desrt: yeah, but I'm in a better place now :)
[15:17] <desrt> didrocks: not gonna argue that :)
[15:17] <desrt> didrocks: i just had a friend of a friend move to lyon, btw
[15:17] <desrt> he seems to agree that it's a nice city :)
[15:17] <didrocks> oh? :)
[15:17] <didrocks> heh
[15:18] <desrt> not sure which area he lives in.  i should ask.
[15:32] <pitti> jbicha: hm, I thought you committed some changes to rename the rdp library for the soname bump?
[15:32] <pitti> jbicha: or do I misremember and you said "upstream did, but I missed it"?
[15:32] <pitti> jbicha: with alioth down, these might still sit in your local git repo?
[15:51] <jbicha> pitti: I pushed to alioth before it went down, but do you have a recommendation where I could push it to you now?
[15:52] <BigWhale> which version of unity will land in precise? 5.2?
[15:54] <seb128> BigWhale, when?
[15:54] <seb128> 5.2 is this week version
[15:54] <seb128> but there will be other versions during the cycle
[15:55] <BigWhale> oh, I didn't know numbers are going up so fast :)
[15:55] <seb128> mvo, help!
[15:55] <BigWhale> is there a ppa for the latest version? the most stable bleeding edge :>
[15:56] <seb128> $ LC_ALL=C sudo apt-get remove --purge libunity-misc0
[15:56] <seb128> ...
[15:56] <seb128> mvo, let me use ubuntu-devel rather
[15:56] <BigWhale> staging ppa?
[15:57] <seb128> BigWhale, yes
[15:59] <BigWhale> seb128, excellent
[15:59] <mvo> seb128: ?
[16:10] <Riddell> Sweetshark: when I export a spreadsheet as PDF from libreoffice how can I specify which sheet to use?
[16:14] <pitti> jbicha: hm, perhaps format-patch 4974713191218... and mail them to me?
[16:26] <chrisccoulson> is anyone here on oneiric?
[16:27] <chrisccoulson> or older? ;)
[16:28] <seb128> what do you need? I've boxes on older versions
[16:29] <jbicha> me too
[16:37] <pitti> good night everyone!
[16:37] <seb128> 'night pitti
[16:38] <chrisccoulson> seb128, could you install http://code.google.com/p/crashme/, crash firefox and send me the crash ID?
[16:38] <chrisccoulson> :-)
[16:39] <chrisccoulson> it seems that crash reports from most of our users are still lacking crash symbols. i'm just wondering if something is broken, or whether people just aren't up-to-date
[16:43] <seb128> chrisccoulson, ok, will do in a bit
[17:01] <DBO> bryce, around?
[17:04] <BigWhale> Hmmm, launcher on both screens sure is nice, but I'd prefer launcher on the right side of my right monitor... or at least a lower 'force' required for mouse to pass from one screen to another.
[17:12] <dobey> BigWhale: launcher on both screens? is that the norm, or customizable?
[17:13] <BigWhale> dobey, no idea... I just installed staging ppa
[17:13] <BigWhale> and I have it on both screens
[17:13] <kenvandine> dobey, feature just merged i think
[17:16] <dobey> kenvandine: glad i don't have two displays then i guess :)
[17:16] <BigWhale> kenvandine, I'll be testing gwibber now... ;> get ready. :P
[17:16] <kenvandine> i'll like 2 launchers, i have 2 1080p displays... the launcher is really far away from the right screen :)
[17:17] <BigWhale> kenvandine, yeah, I agree. but I'd prefer right launcher on the right side :/
[17:17] <kenvandine> that would feel weird to me...
[17:17] <kenvandine> although i hate autohide
[17:18] <kenvandine> so i don't have to deal with revealing it
[17:18] <BigWhale> well, now there's this 'bump' in the middle of the screen
[17:18] <BigWhale> yeah I also have it on all the time
[17:18] <BigWhale> kenvandine, is there a more recent ppa for gwibber than unity staging?
[17:19] <kenvandine> there is precise :)
[17:19] <kenvandine> i just uploaded 3.3.3 this morning
[17:20] <BigWhale> hmm
[17:21] <BigWhale> oh I need to do an upgrade... strange
[17:23] <dobey> kenvandine: well, if i had another one of these screens, i'd have 2x 2048x1152. but i'd also only want stuff on the second screen which i explicitly put there. win/mac get this right, but on linux everyone seems to always want to try and be overly smart about it. :-/
[17:25] <dobey> although, if i end up doing what i've been pondering, i'll end up with 2 screens that are like 3840x2400
[17:27] <dobey> but i probably won't do that ;)
[17:39] <manish> mterry: got a minute?
[17:39] <mterry> manish, sure
[17:39] <manish> first, thanks for your great work caled deja-dup
[17:40] <manish> I am integrating zeitgeist privacy (activity-log-manager) in control center
[17:40] <manish> and looking at preferences of deja-dup folder
[17:40] <manish> to create a binary
[17:40] <manish> as well as .so/.la file
[17:40] <manish> which gets installed in the panels folder
[17:40] <manish> I did that
[17:41] <manish> mhr3: and after installing, the files get installed properly, only to find that they are not being loaded by g-c-c
[17:41] <manish> mterry: : and after installing, the files get installed properly, only to find that they are not being loaded by g-c-c
[17:41] <manish> mhr3: sorry
[17:41] <seb128> manish, do you have a .desktop as well for the panel?
[17:41] <manish> no, havn't created it yet
[17:41] <mterry> manish, yeah, look at the data/ directory for the deja-dup-ccpanel.desktop file and do something similar
[17:42] <mterry> manish, g-c-c only loads panels it finds desktop files for
[17:42] <manish> oh, doing C/vala stuff for the first time. Thanks for the heads up
[17:43] <mterry> manish, the key difference is a new field "X-GNOME-Settings-Panel=XXX" where XXX is your panel's id
[17:43] <manish> so how do I know about the panel's id?
[17:44] <mterry> manish, and you need to add X-GNOME-Settings-Panel to your Categories
[17:44] <mterry> manish, it should be the basename of your .so file
[17:44] <manish> got it. Thanks, trying
[17:44] <mterry> so I install libdeja-dup.so and I use 'deja-dup' as an ID
[17:44] <manish> hmm
[17:52] <BigWhale> if totem, mplayer and vlc crash Xorg in Precise, this would be already known issue, or? :)
[17:54] <chrisccoulson> grrrr, damn you xchat and the stuck messaging indicator
[17:55] <dobey> BigWhale: i haven't seen that
[17:55] <dobey> chrisccoulson: are you sure stuck messaging indicator isn't ubuntu one?
[17:57] <BigWhale> dobey, I'm using laterst fglrx also
[17:58] <BigWhale> might be related
[17:59] <chrisccoulson> dobey, no. xchat has a bug where if somebody pings you and then changes their name, the message recipient can't cancel the indicator
[17:59] <chrisccoulson> and somebody did that to me earlier ;)
[18:00] <mterry> chrisccoulson, that sucks
[18:00] <chrisccoulson> grrrrr, mterry
[18:01] <chrisccoulson2> i bet you're not using xchat, are you?
[18:01] <dobey> oh nice
[18:01] <dobey> heh
[18:02] <kenvandine> chrisccoulson2, i know.. that is annoying
[18:02] <dobey> don't use xchat :)
[18:02] <kenvandine> i can't get a signal for when someone changes their nick though... at least not through the plugin API
[18:02] <dobey> irssi+screen for the triple-double
[18:37]  * didrocks waves good night
[18:37] <cyphermox> night didrocks
[18:39] <seb128> RainCT, hey, do you think you could backport http://bazaar.launchpad.net/~zeitgeist/zeitgeist/bluebird/revision/378 to zg in Debian?
[18:40] <RainCT> seb128: Hey. Sure
[18:40] <seb128> RainCT, thanks ;-)
[18:47] <micahg> which release did glib single include start with?
[18:47] <micahg> (optionally)
[18:48] <dobey> a long long time ago
[18:49] <seb128> http://git.gnome.org/browse/glib/commit/?id=62a133f55dcd5626e9583aabc2d95926936a8475
[18:49] <seb128> so 2.23?
[18:49] <seb128> or before
[18:50] <dobey> glib.h has been around longer than that. i think that's when it started being less optional :)
[18:50] <micahg> seb128: so lucid had support for this?  I just want to know whether or not I can upstream this patch for chromium
[18:50] <dobey> cgit has a very annoing interface then
[18:50] <seb128> micahg, yes
[18:50] <cyphermox> desrt: seb128: how would I go about replacing a menuitem from a GtkMenu/GtkMenuShell in-place? e.g. figuring out its position value or something?
[18:51] <desrt> cyphermox: the only way you do that is by calling gtk_container_get_children() and counting
[18:51] <micahg> excellent :)
[18:51] <cyphermox> desrt: gah.
[18:51] <cyphermox> alright
[18:51] <desrt> cyphermox: or by gtk_container_foreach, same story
[18:51] <cyphermox> sure.
[18:51] <desrt> the foreach is a bit less expensive since you don't allocate the list
[18:51] <cyphermox> desrt: I was mostly afraid this wouldn't map to the same values
[18:52] <desrt> i think it should
[18:52] <cyphermox> worth a try, anyway
[18:53] <micahg> seb128: BTW, chromium builds webkit with -jX, so idk why it doesn't work with webkitgtk
[19:03] <jbicha> seb128: could you push gnome-shell through the oneiric-proposed new queue?
[19:23] <desrt> pitti: so what's the word on udisks?
[19:33] <RainCT> seb128: zeitgeist (0.8.99~alpha2-2) uploaded to experimental
[19:42] <seb128> RainCT, thanks
[19:42] <seb128> desrt, what about it?
[19:42] <desrt> seb128: pitti said (i think) he would package udisks2
[19:42] <seb128> jbicha, no, I'm not in the SRU team, check with pitti and RAOF
[19:43] <kenvandine> desrt, is there a way to query to see if a gapplication is running?
[19:43] <seb128> desrt, he wrote "FYI, https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages has udisks2 now"
[19:43] <desrt> ah.  nice.
[19:43] <seb128> "it apparently still has some trouble with our udev version, though"
[19:43] <seb128> "I don't feel 100% sure about it yet"
[19:43] <desrt> kenvandine: like, check if its bus name is owned?
[19:43] <seb128> desrt, he said also that the new gdu needs a new gtk
[19:43] <kenvandine> yeah, i could do that with dbus
[19:43] <seb128> desrt, so maybe next week
[19:44] <kenvandine> but it seems like something gapplication could solve nicely
[19:44] <desrt> seb128: i think mclasen was talking of doing a pair of releases
[19:44] <kenvandine> dbus_name_has_owner
[19:44] <seb128> desrt, 3.3.5 is next week
[19:44] <desrt> seb128: glib and gtk have been releasing more frequently already
[19:45] <seb128> desrt, we are in soft freeze this week for alpha2 and I want to avoid your gmenu breakages then, so likely next week
[19:45] <desrt> gotcha.
[19:45] <desrt> i actually don't really care about gdu
[19:45] <desrt> i just want jhbuild working :)
[19:45] <seb128> desrt, use the ppa ;-)
[19:45] <seb128> I'm sure pitti welcomes feedback
[19:46] <desrt> not a bad suggestion
[19:46] <desrt> thanks
[19:47] <seb128> yw
[19:55] <manish> mterry: I tried, but it is failing, have a look at the desktop.in file I am providing and the deja-dup's one http://paste.ubuntu.com/822970/
[19:56] <seb128> manish, what is your /usr/share/applications .desktop?
[19:56] <seb128> can you pastebin the content of this one?
[19:56] <manish> something really wrong,
[19:57] <manish> sure
[19:57] <aquarius> pitti, ping about calibre crashe
[19:57] <manish> seb128: this http://paste.ubuntu.com/822975/
[19:58] <manish> and this
[19:58] <manish> $ gnome-control-center alm
[19:58] <manish> ** (gnome-control-center:7574): WARNING **: Could not find settings panel "alm"
[19:58] <manish> ** (gnome-control-center:7574): WARNING **: Could not load setting panel "alm": Unknown error
[19:58] <seb128> aquarius, try tomorrow, it's way after work time for him
[19:58] <aquarius> seb128, yeah, I know, it is for me (and you!) too; I just thought I'd see if I were lucky :)
[19:59] <jbicha> pitti: are you still around?
[19:59] <manish> seb128: I see that deja-dup does not install the .la files
[19:59] <seb128> manish, do you have a /usr/lib/control-center-1/panels/libalm.so ?
[19:59] <manish> yup
[19:59] <manish> $ ls /usr/lib/control-center-1/panels/libalm.*
[19:59] <manish> /usr/lib/control-center-1/panels/libalm.a  /usr/lib/control-center-1/panels/libalm.la  /usr/lib/control-center-1/panels/libalm.so
[20:01] <seb128> manish, strace gnome-control-center alm 2> &1 | grep alm and pastebin the log?
[20:01] <manish> okay
[20:01] <mterry> manish, I'm looking now too
[20:02] <manish> mterry: in case you need, the branch is lp:~activity-log-manager/activity-log-manager/vala-gcc
[20:02] <seb128> jbicha, you should give some context, I guess he will read the log tomorrow morning
[20:02] <mterry> manish, have you forced a regeneration of the desktop file caches?
[20:03] <mterry> manish, (I forget the real command to do it, but 'apt-get install evince --reinstall' will work)
[20:03] <manish> mterry: is it something magical? I just used the same template as deja-dup
[20:03] <manish> mterry: via apt-get?
[20:03] <seb128> manish, mterry: sudo update-desktop-database
[20:03] <manish> seb128: http://paste.ubuntu.com/822982/
[20:04] <mterry> seb128, thanks  :)
[20:04] <manish> looks like it is finding the libalm.so file
[20:04] <manish> but not loading it
[20:04] <seb128> manish, mterry: that strace shows that it finds the .desktop and .so, so I guess you have a code bug
[20:05] <seb128> I will let mterry pick it up from there
[20:05] <seb128> ;-)
[20:05] <manish> seb128: thanks a lot
[20:06] <manish> mterry: I think it should not be a big issue for you. The real integration file is in src/alm-cc.c in the branch I gave you
[20:06] <mterry> manish, let me look
[20:06] <manish> sure
[20:08] <jbicha> seb128: pitti no problem, I'll just ping raof later
[20:09] <seb128> jbicha, what's the question?
[20:10] <dobey> kenvandine: nessita and i won't have to bug you for sponsorship so much now. hooray! :)
[20:10] <kenvandine> woot
[20:10] <kenvandine> congrats!
[20:10] <dobey> thanks
[20:11] <seb128> jbicha, btw looking to the ppa we can probably update gsettings-desktop-schemas  in precise after checking that it doesn't break things
[20:11] <seb128> jbicha, but it seems mostly schemas addition and a few commits
[20:11] <seb128> dobey, on what set did you get upload rights?
[20:11] <seb128> nessita1, dobey: congrats ;-)
[20:12] <dobey> seb128: ubuntuone :)
[20:12] <jbicha> seb128: gnome-shell in the oneiric-proposed new queue
[20:12] <seb128> dobey, so you got a new set? you got both upload for the set?
[20:12] <dobey> seb128: yep
[20:12] <mterry> manish, mmm, hold on a bit, I have to put out a different fire
[20:12] <mterry> manish, will be back
[20:12] <seb128> jbicha, oh ok, there was a version approved today, you have another one?
[20:13] <manish> mterry: sure
[20:13] <jbicha> seb128: same one, but gnome-shell-common is a new package
[20:14] <seb128> jbicha, oh ok, weird for a sru to have a new binary
[20:15] <jbicha> yes, not sure if it was a good idea or not
[20:15] <jbicha> seb128: I thought this commit might be too much: http://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=99cbaf394b520f5b2c23daf892dac2db9035d711
[20:16] <jbicha> unless you want g-c-c and g-s-d after all :)
[20:18] <BigWhale> Err, what happened with Gtk in Precise? configure-event signal is not returning event coordinates in floats
[20:18] <BigWhale> is this how is it supposed to be?
[20:18] <BigWhale> Err, what happened with Gtk in Precise? configure-event signal is _NOW_ returning event coordinates in floats
[20:18] <BigWhale> they used to be integers
[20:20] <seb128> jbicha, well, it's adding keys but they don't hurt if nothing use them?
[20:23] <seb128> nessita, hey, congrats on your upload rights!
[20:23] <jbicha> seb128: yes, but not upgrading it would prevent against an accidental new metacity upload which would then require the new g-c-c to set keyboard shortcuts correctly
[20:24] <seb128> jbicha, ok, your call, I was saying that to reduce the ppa delta
[20:24] <nessita> seb128: thanks! :-) you helped a lot, teaching and sponsoring
[20:24] <seb128> jbicha, we can revisit that at the end of the cycle
[20:24] <seb128> jbicha, to lower a bit the delta if we can
[20:24] <seb128> nessita, ;-)
[20:25] <nessita> :-D
[20:38]  * mterry is back
[20:39] <mterry> manish, I think you forgot to push the alm-cc.c file to the branch?
[20:39] <manish> oh really?
[20:39] <manish> checking
[20:40] <manish> yes, I did. Stupid me
[20:40] <manish> mterry: added and pushed to lp:~activity-log-manager/activity-log-manager/vala-gcc
[20:46] <mterry> manish, I agree that your alm-cc.c seems harmless
[20:46] <manish> can you build and check
[20:46] <manish> is it something to do with my config?
[20:46] <mterry> sure
[20:53] <mterry> manish, I get the same behavior.  looking
[20:53] <m4n1sh_> mterry: any success?
[20:55] <mterry> manish, maybe... hold on for report
[20:55] <manish> sure
[20:56] <mterry> manish, yup.  Comment out "NotShowIn=GNOME;Unity;" in your desktop file.  Your makefile is leaving that in there when it inserts the OnlyShowIn line
[20:56] <mterry> manish, this will give you a new error
[20:56] <mterry> about undefined symbols
[20:57] <manish> mterry: why is that line needed at all?
[20:57] <manish> sed -i "s/^Categories=.*/\0\n\nNotShowIn=$(shell grep OnlyShowIn $(srcdir)/alm-ccpanel.desktop.in | cut -d= -f2)/" $@
[20:57] <manish> so should I remove this?
[20:58] <mterry> manish, depends.  Do you want to target non-Ubuntu platforms?  Only Ubuntu allows 3rd party panels
[20:58] <manish> yes, I saw the patch in g-c-c-
[20:58] <mterry> manish, deja-dup targets other platforms, so I had to do some work to make sure things worked correctly in both environments
[20:59] <manish> so what is your advice in this case?
[20:59] <manish> desktop.in has OnlyShowIn=GNOME;Unity;
[20:59] <mterry> manish, so you do target other platforms?  OK.
[20:59] <manish> yes
[20:59] <manish> in other platforms the .so file is not built
[20:59] <manish> only the binary
[20:59] <mterry> So you're going to need three levels of desktop.  "desktop", "desktop.in" and "desktop.in.in"
[21:00] <mterry> Your original will be .in.in
[21:00] <mterry> Oh...
[21:00] <mterry> What happens on other platforms exactly?
[21:01] <mterry> Do you have a separate preferences binary or is it just part of the main UI?
[21:01] <manish> ActivityLogManager is a Gtk.Window
[21:01] <mterry> If it's part of the main UI this will be simpler.  Deja Dup does some crazy things because it has a separate preferences binary
[21:01] <mterry> manish, I mean...  Like in Fedora.  How do users change preferences?
[21:01] <manish> which contains everything
[21:01] <manish> using g-c-c-?
[21:02] <manish> in alm, now it was before g-c-c integration
[21:02] <manish> class ActivityLogManager is a Gtk.Window
[21:02] <mterry> manish, OK.  So in Fedora, users edit preferences via Edit->Preferences or something in alm.  And in Ubuntu, you're just adding another option to do it in g-c-c?
[21:03] <manish> this entry in g-c-c will only be in ubuntu
[21:03] <manish> in other platforms
[21:03] <manish> this application is just a standlaone binary
[21:03] <manish> check src/Makefile.in
[21:03] <mterry> manish, right...  I think I get it
[21:03] <manish> err
[21:03] <manish> check src/Makefile.am
[21:03] <mterry> manish, then you can just delete that sed -i block in data/Makefile.am
[21:03] <manish> no three layers?
[21:04] <manish> mterry: desktop desktop.in and desktop.in.in not needed?
[21:04] <mterry> manish, no.  That was only because deja-dup did something crazy.  you'll still need desktop.in for normal translation insertion
[21:05] <mterry> But that doesn't need special makefile logic.  that's handled by @INTLTOOL_DESKTOP_RULE@ already
[21:05] <manish> yes
[21:05] <manish> even such a simple application takes more than a min to compile. Don't know what I am doing wrong
[21:11] <mterry> manish, I need to go offline.  But that should get you to a new error about missing symbols, which means you're not adding enough code to the .so via _LIBADD
[21:12] <manish> mterry: not a problem. I will keep trying
[21:12] <manish> thanks
[21:12] <mterry> manish, good luck!
[21:12] <manish> mterry: got it :)
[21:12] <manish> WORKS!
[21:19] <seb128> manish, you got it working?
[21:19] <seb128> great!
[21:19] <manish> seb128: yes. Thanks a lot. It looks like http://i.imgur.com/2IZ7f.png and http://i.imgur.com/vsBZJ.png
[21:20] <seb128> manish, well done! ;-)
[21:25] <BigWhale> Yesterday GdkEventConfigure structure was just fine in GIR, today gint x and gint y turned into floats. Anyone knows something about this?
[21:26] <kenvandine> BigWhale, did the gir change?
[21:27] <BigWhale> kenvandine, I honestly don't know ... I just know that suddenly I was getting floats out ...
[21:27] <BigWhale> and nothing worked :>
[21:28] <BigWhale> and I have no immediate way to check how it was yesterday
[21:28] <BigWhale> (or couple of days ago)
[21:28] <seb128> you can check your dpkg.log to see what you updated
[21:29] <BigWhale> hmm let me check
[21:31] <BigWhale> 2012-01-29 16:31:18 status installed gir1.2-gtk-3.0 3.3.10-0ubuntu3
[21:31] <BigWhale> this must be it
[21:34] <seb128> it would be weird, kenvandine did that update and the patches there shouldn't make any different to gdkevents
[21:34] <kenvandine> yeah, shouldn't
[21:34] <kenvandine> BigWhale, any chance it was working on oneiric and not precise? maybe bouncing around between the two is hurting
[21:34] <BigWhale> this is what event.x contains
 X 632.114868164 Y 472.557556152 SW 640 SH 480
 X 632.114868164 Y 472.557556152 SW 640 SH 480
[21:35] <kenvandine> i've been bit by that before
[21:35] <BigWhale> no, it was working in precise ... popey can confirm
[21:35] <BigWhale> right now it is working in oneiric and not in precise
[21:35] <seb128> xorg changed recently
[21:35] <seb128> but that would be weird
[21:35] <kenvandine> devhelp says it should be gint
[21:35] <BigWhale> gir file seems ok too
[21:37] <BigWhale> kenvandine, http://bazaar.launchpad.net/~kazam-team/kazam/unstable/view/head:/kazam/frontend/window_region.py#L89
[21:37] <BigWhale> this is the code
[21:37] <kenvandine> i just verified in gwibber i am still getting an int
[21:37] <kenvandine> ** DEBUG: gwibber-client.vala:321: CHANGED 554, 1027, 54, 24
[21:37] <kenvandine> vala vs python of course
[21:38] <BigWhale> hmm I get 632.0 value in Oneric
[21:38] <BigWhale> Oneiric
[21:39] <kenvandine> BigWhale, oh, my test isn't getting it from the event... anyway... /me looks
[21:41] <BigWhale> I had to use int() to get it working :>
[21:41] <BigWhale> Casting in python ... Pfft!
[21:43] <kenvandine> BigWhale, line 89 isn't the callback for configure-event
[21:43] <kenvandine> line 131 is
[21:43] <kenvandine> looks like 89 is a button click
[21:43] <BigWhale> err you're right
[21:45] <kenvandine>   gdouble x;
[21:45] <kenvandine>   gdouble y;
[21:45] <kenvandine> for GdkEventButton
[21:46] <BigWhale> why on earth are they different? :>
[21:46] <kenvandine> it's gtk :)
[21:50] <BigWhale> that I can understand, but that it just changed its mind and is returning some arbitrary value instead of rounding it to .0 ... :>
[22:15] <seb128> robert_ancell, hey
[22:15] <robert_ancell> seb128, good evening
[22:15] <seb128> robert_ancell, how are you?
[22:16] <robert_ancell> doing good
[22:17] <seb128> robert_ancell, great ;-)
[22:20] <seb128> robert_ancell, who is doing unity-greeter release nowadays? did you delegate that to mterry?
[22:21] <seb128> robert_ancell, I was wondering who to bother once he lands all the merge requests you approved ;-)
[22:21] <robert_ancell> seb128, I'm still doing the release, but mterry has done most of the changes.  But it really could be anyone
[22:22] <seb128> robert_ancell, ok, I will nag him to merge the stuff you approved tomorrow then and let's see who gets to roll a tarball
[22:22] <robert_ancell> ok
[22:29] <seb128> robert_ancell, btw I added a comment on bug #870297 with what gdm is doing in case that's useful info
[22:29] <ubot2`> Launchpad bug 870297 in lightdm "Lightdm logins not being logged in wtmp" [High,Confirmed] https://launchpad.net/bugs/870297
[22:29] <robert_ancell> seb128, ok, thansk
[22:30] <seb128> robert_ancell, could you also review bug #916477 and https://code.launchpad.net/~agateau/lightdm-gtk-greeter/fix-missing-greeter-ui/+merge/89239 if you have a bit of free time?
[22:30] <ubot2`> Launchpad bug 916477 in lightdm "gio-2.0 missing from liblightdm-gobject-1.pc" [Medium,Incomplete] https://launchpad.net/bugs/916477
[22:30] <seb128> robert_ancell, the second one is what agateau stopped on when trying to package the gtk greeter
[22:31] <seb128> robert_ancell, I know you don't want to spend time on the gtk greeter but since the lightdm update the binary is hanging around not built from source, which means if we get any lib transition or need a rebuild we are screwed until we land the new source ;-)
[22:31] <seb128> robert_ancell, the other bug, somebody mentioned it was blocking the debian packaging, not sure if that's true
[22:32] <robert_ancell> seb128, that bug doesn't make sense - you shouldn't need to add gio into the .pc file as it's not your program that needs to link to gio but the library
[22:32] <robert_ancell> and it should already be
[22:32] <robert_ancell> can you reproduce it?
[22:34] <seb128> robert_ancell, let me try
[22:35] <seb128> but yeah, the description doesn't make sense
[22:35] <seb128> if the binary use a lib it should need to be exposed
[22:36] <robert_ancell> seb128, there is another bug floating around where some X symbols are failing to link and again it looks like a similar issue
[22:37] <seb128> robert_ancell, "‘gtk_hbox_new’ is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:64): Use 'gtk_box_new' instead [-Wdeprecated-declarations]
[22:37] <seb128> "
[22:37] <seb128> it's failing on that :p
[22:37] <seb128> well otherwise it builds fine
[22:38] <robert_ancell> that's only a warning right?
[22:38] <seb128> yes
[22:38] <jbicha> X symbols? like this one I can't figure out why it doesn't work on my computer but does on robert_ance 's https://bugzilla.gnome.org/show_bug.cgi?id=667905
[22:38] <ubot2`> Gnome bug 667905 in general "fails to build: libcanberra undefined references" [Critical,Unconfirmed]
[22:40] <seb128> jbicha, that bug seems a libcanberra one
[22:40] <robert_ancell> jbicha, hi!
[22:41] <seb128> jbicha, like if canberra brings x11 apis it should list X11 in libcanberra-gtk.pc
[22:57] <seb128> robert_ancell, the patch on https://bugs.launchpad.net/lightdm/+bug/898134 seems correct though
[22:57] <ubot2`> Launchpad bug 898134 in lightdm "lightdm-1.1.0 fails to build with: undefined reference to symbol 'XClearWindow'" [Medium,Triaged]
[22:57] <seb128> https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/898134
[22:57] <robert_ancell> seb128, yup, that looks correct
[22:58] <seb128> I wonder why I don't get those error there with --as-needed