[01:30] kenvandine, I think I figured out how to write a GUI to choose which desktopcouch databases to synch [01:30] I'll try it tonight, seems like it would take about an hour or so [01:41] kenvandine, http://imgur.com/qnfuD [02:28] rickspencer3, sweet! [02:29] slip cover... lol [02:29] :) [02:33] :) [02:39] kenvandine, accessing the gwibber_preferences couchdb immediately pegs my CPU [02:39] wow [02:39] gwibber-server and desktopcouch-se [02:39] got a test case? [02:39] I'll package the app I just wrote [02:39] and you can run it yourself [02:39] great [02:39] it's 100% reliable [02:39] hold on [02:40] i would like to get ryan to do it to [02:40] kenvandine, can i just email you the deb? [02:40] sure [02:40] or IM it to me :) [02:40] empathy rocks [02:41] $quickly package ftw [02:41] sure, good idea [02:41] quickly rocks too [02:41] kenvandine, so when you run this, it will list out each of your desktopcouch databases as a button [02:42] see what happens when you click gwibbermessages [02:42] ok [02:43] i get a crash dialog :) [02:43] from slip-cover [02:43] but [02:43] oh well [02:43] not for other dbs [02:43] it doesn't even run? [02:43] let me change my passwords to plaintext so i can run gwibber [02:43] :) [02:43] it does [02:44] just clicking on gwibbermessages gives me a crash dialog [02:44] it doesn't seem to crash though [02:44] oh [02:44] I bet my way of getting the records from it doesn't work [02:44] I used a super convenience method [02:44] let me see if there is a better way [02:45] oh crikey [02:45] oh... here [02:45] File "/usr/lib/python2.6/dist-packages/desktopcouch/records/server_base.py", line 454, in get_records [02:45] raise KeyError("View doesn't already exist.") [02:45] KeyError: "View doesn't already exist." [02:45] I have to do hard things [02:45] right [02:45] that was in the terminal [02:46] no worries [02:46] ok, gwibber is running [02:46] so get_records() doesnt' quite work reliably [02:46] let me make sure the cpu doesn't peg [02:46] kenvandine, if you run photobomb first, and go to the gwibber tab, it should work [02:46] slipcover, that is [02:47] actually, I wonder if that will pin the CPU [02:48] i just did 3 refreshes [02:48] with plaintext password... no load [02:48] ok, time for slip-cover again [02:48] I have plane text passwords too [02:48] you said gwibberpreferences pegs it? [02:48] yes [02:49] kenvandine, can you see if photobomb pegs it for you? [02:49] bzr branch lp:~rick-rickspencer3/+junk/photobomb [02:49] yeah, one sec [02:49] so just opening gwibberprefernces pegs it for you? [02:49] yes [02:50] but I've run photobomb, which asks gwibber_preferences to create a view for get_records [02:50] that's why slip-cover works for me on that database [02:50] I'll have to write a few lines to create a proper view [02:52] i ran it [02:52] waiting now :) [02:52] gwibber_messages is pretty big [02:54] http://pastebin.ubuntu.com/407861/ [02:54] rickspencer3, ^^ [02:54] wtf [02:54] and i am not seeing the CPU load [02:55] kenvandine, do you have quickly-widgets installed from universe? [02:55] yes [02:55] 10.02.2 [02:56] weird [02:56] *sigh* [02:56] i wonder how your accessing it that causes it [02:57] do you read in all the records? [02:58] kenvandine, yes [02:58] db.get_records() [02:59] kenvandine, photobomb also causes the cpu to pim [03:00] not for me [03:00] when you refresh on the gwibber tab? [03:00] it does not peg your CPU? [03:00] refresh? [03:00] on photobomb, there is a gwibber tab [03:01] oh [03:01] let me do that [03:01] you have to hit the refresh button for it to start grabbing photos from your gwibber accounts [03:01] it also reads you gwibber settings database and pulls your facebook credentials [03:03] wow... photobomb is using a ton of ram [03:04] 2G and growing [03:04] hehe [03:04] a tad leaky? [03:04] hehe [03:05] not really seeing any load problems though [03:05] kenvandine, so the gwibber page didn't peg your CPU? [03:05] nope [03:05] this is soooo weird [03:05] you said it does it to desktopcouch too [03:06] desktopcouch-service? or beam.smp? [03:06] so certain apps, when they access gwibber preferences, cause the CPU to peg [03:06] kenvandine, both [03:06] all [03:06] but the thing is, the apps that do this are different for different people [03:06] IT MAKES NO SENSE [03:06] very weird [03:06] so if it is making gwibber-service spike [03:06] it must be changing records [03:07] otherwise gwibber would never even know it [03:07] like something is listening for record changes? [03:07] but, gwibber-service does have "Monitors" setup for the dbs it cares about [03:07] yeah, so gwibber sees records added or updated as events [03:08] and then gwibber writes records in response to these events, gets invoked, etc...? [03:08] but you are doing a get_record [03:08] no [03:08] gwibber sees something else writing to it [03:08] it wouldn't get an event for it at all if there aren't records changing [03:08] my desktopcouch-se is just running one of my CPUs at 99% [03:08] which is weird [03:08] for like the last 5 mins [03:08] right [03:08] ok... well... that is familiar :) [03:09] is slip-cover still running? [03:09] no [03:09] gwibber though [03:09] i bet that is the same thing i was seeing [03:09] killall gwibber gwibber-service [03:09] but I never saw this until I accesssed gwibberaccounts [03:09] which is weird [03:10] we need chad [04:10] kenvandine, oh well, at least you found that bug in DictionaryGrid for me [04:10] was happy to fix that [04:10] g'night [04:10] :/ [04:10] good night [04:10] kenvandine, we'll figure it out tomorrow [04:10] the answer is staring you guys in the face, I am convinced [04:11] a good night's sleep will prolly help ;) [04:11] :) === JanC_ is now known as JanC [07:34] morning [07:38] huats: hello [07:38] hello vuntz [07:39] didrocks: any idea why simple-scan is at 0.9.10 in the ubuntu packages, but the latest tarball is 0.9.9? [08:14] vuntz: robert_ancell probably forgot to create the milestone and upload the tarball. Do you want it? I can apt-get source and push it somewhere [08:14] vuntz: that's why Quickly rules: it does it for you :p [08:14] hey huats [08:14] hello didrocks [08:33] didrocks: better to annoy rob when he'll be here :-) [08:33] vuntz: sure, do not hesitate :p [08:57] vuntz: hey [08:57] didrocks: hello [08:57] hey desrt, quite late for you, isn't it? [08:57] can't sleep [08:57] argh :/ [08:57] didrocks: might i be able to harass you about some universe stuff? [08:58] desrt: sure [08:58] normally i bother seb, but he's committed to vacationing today :) [08:58] two things: [08:58] (yeah, it's a shame :)) [08:58] 1) can you guys update to the freshly-released valac version? [08:58] (that's the easy one) [08:59] 2) http://packages.debian.org/source/sid/zeromq [08:59] (that's the hard one) [09:00] i'm not really familiar with how difficult it is to get new package into the archive this late in the cycle if they have upstream versions already existing in debian [09:01] desrt: nothing too risky in the new vala release? ("Infer type arguments when calling generic methods." <- no impact?) [09:01] didrocks: it's the stable release [09:01] vuntz: ok, 0.7.10 isn't? it follows odd number == unstable too? [09:01] so better to have a stable release than a development one, I'd say [09:01] right [09:01] didrocks: no. 0.8. [09:02] quite freshly released [09:02] desrt: yeah, I was asking if "0.7.10" (the current one we have) is unstable. Understood, will update :) [09:02] for the new package [09:02] it should be easy to get a Feature Freeze Exception [09:02] i don't think vala really follows the normal stable/unstable versioning scheme in a meaningful way [09:03] desrt: care about opening a bug telling why this package is necessary? Then we will subscribe ubuntu-archive to get a grant [09:03] didrocks: i'm not sure it *is* necessary :) [09:04] but it seems like a relatively easy (and entirely zero-risk) inclusion [09:04] and there's a good chance that dconf will use it [09:04] desrt: well, let's say "it's good to have and there is no risk" [09:04] desrt: just open a bug stating that and I will subscribe to get the grant [09:04] ok. cheers. [09:04] what do i file against, exactly? [09:05] updating vala now [09:05] desrt: ubuntu itself [09:05] ok [09:09] didrocks: what do you guess the chances are? [09:09] god i hate launchpad [09:09] every time i try and use it it's a timeout error :( [09:13] desrt: for the new package? it's high has there is no impact on existing things [09:14] desrt: but it will be treated probably after beta2 (next thursday) [09:14] of course [09:15] https://bugs.launchpad.net/ubuntu/+bug/553858 [09:15] Ubuntu bug 553858 in ubuntu "please pull zeromq from debian" [Undecided,New] [09:15] didrocks: thanks [09:15] desrt: thanks, subscribing now :) [09:16] I'm updating vala now and try to build something with it [09:16] desrt: btw, do you know what's the best practice for vala is concerning upstream? [09:16] didrocks: the best test case for vala is vala itself :) [09:16] I mean, I see some upstream generated the .c file in the tarball, and some not [09:16] didrocks: bugzilla [09:16] oh. that. [09:16] the widely accepted practice is to have .c in the tarball [09:17] but not in git [09:17] sure, only in the tarball [09:17] ok, I'll track down upstreams which don't do that :) [09:17] well [09:17] there's nothing wrong with shipping tarballs without .c [09:17] it's just non-standard behaviour [09:18] yeah, I mean, I guess that most of the time, they don't really know it's best for packagers [09:18] and everyone, really [09:18] note also: the automake vala rules do this automatically [09:18] add the .c files to the dist tarball [09:19] so the only time you'll encouter .vala-only is in cases were people have homebrew makefiles or have manually worked-around the standard automake behaviour [09:19] desrt: oh, so they just don't include it [09:19] right [09:19] if you're going to file bugs with upstreams it might be useful to point that out [09:19] the vala support came with automake version 1.11 [09:20] yeah, I note that down to be able to help upstream making this [09:23] * desrt plays with zeromq a bit as a sleep-deferal strategy :) [09:25] heh :) [09:26] didrocks: thanks for the vala refresh and the zeromq sponsor [09:26] desrt: y/w ;) [09:27] desrt: note that the vala refresh, even in universe, should be pushed manually in the repo by an archive admin [09:27] desrt: so, probably Monday or Tuesdsay with Easter week-end :) [09:27] (beta freeze is no more a soft freeze, even for universe) [09:28] yes. that's quite reasonable. [10:10] what is needed to get auot login nowadays? [10:11] is that gconf setting? [10:11] didrocks: ^^ [10:11] asac: no, it's in /etc/gdm/custom.conf. One sec [10:12] ok... thats enough info [10:12] ok :) [10:12] we just wondered if thats still it because it doesnt work here for someone [10:12] ;) [10:12] we will figure [10:12] asac: hum, it should work :) the live system use that :) [10:12] ok, good luck! [10:12] Hi didrocks! [10:12] <- can't sleep :) [10:12] didrocks: yeah. you probably get a bug ;) [10:13] hey Nafai, you should go to sleep :) [10:13] I will go back in a bit [10:13] asac: I'm sure you will file one and assigne to me :) [10:13] rick mentioned yesterday that I should collaborate with you on UNE stuff [10:13] Nafai: how was your first official day as Canonical employee? :) [10:14] Good, just a lot of "meta" work (reading wiki, subscribing to mailing lists, etc) [10:14] right, first days is that :) [10:14] didrocks: seems he had wrong gnome session file for une [10:14] didrocks: installed just ubuntu-netbook [10:14] why doesnt that install the right one? [10:15] asac: asac if you install ubuntu-netbook, the session is set to une if no default session has been set previously [10:15] asac: DefaultSession=gnome in custom.conf? [10:15] hmm , is seb on vac today? [10:15] didrocks: =une was in there [10:16] just installed ubuntu-minimal ... then ubuntu-netbook [10:16] then a few times worked and rebooted [10:16] suddenly it was broken [10:16] asac: hum, apart from the fact they he unlog, set a different one into gdm (and so populate .dmrc), I don't see what changed it [10:16] let me ask [10:17] vish: right, Lorraine and some countries are on national holidays today [10:17] didrocks: ok. afte rinstallin ghtere was no custom.conf [10:17] oh , :( [10:17] so he added that manually [10:17] didrocks: thanks .. [10:17] so guess was a user bug [10:18] asac: yeah, no custom.conf is quite strange, let's blame the user :) [10:18] vish: some for next Monday btw [10:19] where are the keyboard layout options stored? [10:19] didrocks: ah, ok.. do you have any info about the humanity update? seb was doing it last night , but it seems to have not landed.. [10:19] didrocks: whats the gnome-session file installed [10:19] ? [10:20] vish: he maybe pushed it but as we are in beta freeze, an archive admin has to accept it [10:20] didrocks: ah , the admins .. thanks [10:20] asac: gnome-session file? ~/.config/gnome-session or /etc/X11/Xsession.d/55gnome-session_gnomerc? [10:21] didrocks: wasnt there a .desktop file? [10:21] oh, the desktop file [10:21] right, so, concerning session management [10:21] you have .desktop file in /usr/share/xsessions/ [10:22] (n-m, gconf) [10:22] gnome.desktop for the gnome session, you get the failsafe session and when installing une, you got the une.desktop file [10:23] basically DefaultSession={name_of_the_file_without_extension} [10:23] didrocks: yeah. thx. we have to check something here [10:32] y/w [10:36] * debian/patches/70_glib2.0-gatomic-arm.patch: [10:36] - dropped since that patch was added without details nor reference [10:36] to a launchpad or upstream bug and it's not clear if it's still required [10:36] now with the change done upstream recently [10:36] thats ANNOYING [10:37] when seb comes back i will have to talk to him [10:38] especially because HE added that patch on his own [10:38] two uploads before [10:39] asac: he will be there on Tuesday [10:41] i know [10:50] didrocks: what should be in custom.conf to start proper une? [10:51] we get a full gnome + the launcher if we use une in there [10:51] imo this feels not natural ;) [10:52] ok we figured [10:52] asac: just DefaultSession=une, but if user changed it, it's in .dmrc [10:52] using une-efl seems to start full gnome + launcher [10:52] why does it need to be like that? [10:53] thats a bug i guess? [10:53] e.g. using just une works [10:53] asac: right, I told you that we should create a setting package [10:53] asac: I pinged you and Jamie about it a while ago [10:53] yeah sorry. long time ago that was ;) [10:53] yeah :) [10:54] asac: that can be easily done. I can have a look next week if you want. You want the same settings than une? [10:55] didrocks: is there anything that strikes you that we wpuldnt want from the une setting [10:55] ? [10:56] asac: hum… we hide some items on the menu but it will make sense for you too… and now that go-home-applet is compatible, I don't see anything you won't want [11:01] whats going on: [11:01] "You are not the bug assignee nor the maintainer of glib2.0 (Ubuntu), and therefore cannot edit this bug's status. " [11:01] core devs cant change bug status anymore? [11:01] or is that because launchpad is currently read-only? [11:05] asac: I guess it's a side effect about the read-only yeah [11:08] hmm. its not coming back :( [11:08] its supposed to be back since 10 minutes ;) [11:08] oh its still one more hour [11:15] yeah :/ [12:54] anyone sees the searchplugin being amazon here? [12:54] please test http://people.canonical.com/~asac/tmp/ubufox_0.9~rc1-0ubuntu1_all.deb [12:54] to see if its fixed there [12:59] asac: how can I reset to the default one to check if it's fixed? [13:01] didrocks - you could try a fresh profile in a guest session [13:02] chrisccoulson: right, good idea, let's try this [13:02] didrocks - i tried it in french already :P [13:02] oh ok, no need so :) [13:02] you can still test it ;) [13:03] it's ok there :) [13:03] hello [13:03] asac - did you see the gnome-shell module proposal on desktop-devel-list? [13:04] they mentioned briefly about the dependency on spidermonkey, but nobody seems to think it's a real issue :/ [13:07] chrisccoulson: jump in there and say thats a dead end ;) [13:07] one second [13:08] let me see if i can find the bugzilla bug [13:08] asac - yeah, i think i will draft a response later, but i want to do it in a way that doesn't get me shot-down by everybody ;) [13:11] chrisccoulson: spidermonkey is so bad? [13:11] didrocks - yes [13:12] didrocks - we're actively trying to reduce the number of dependencies on spidermonkey, to fit more with the new mozilla support model [13:12] chrisccoulson: i need to find the upstream bug where they made it clear that they dont want to make any efforts to maintain a stable API even in securty updates [13:13] asac - ok, thanks, that would be interesting [13:13] chrisccoulson: hum, right, that doesn't sound good at all [13:13] ^^^didrocks - asac's response summarizes quite well why we are doing this ;) [13:13] chrisccoulson: yeah, I was at the UDS discussion about the new mozilla support model [13:14] didrocks - so, there is no guarantee of API stability even between minor versions, and consider that we are going to move to a model where we follow major updates throughout the life of a release.... [13:14] so, that's weird that they rely on a mozilla component [13:14] ....that would make something like gnome-shell unsupportable [13:14] right [13:15] mozilla bug 506890 [13:15] Mozilla bug 506890 in Build Config "Make it possible for Ubuntu to provide libmozjs.so as a system library" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=506890 [13:15] read that and there you go [13:16] chrisccoulson: ^^ [13:16] reading this ... everyone using mozjs needs to go somewhere else [13:16] if they ask "where?" ... i dont have an answer [13:16] but the answer is definitly not "stay with mozjs" [13:16] they should complain on that bugt [13:17] maybe having upstreams complain that they wasted all their effort etc. will change their minds [13:17] asac - thanks, that's interesting to read [13:17] i tried to discuss this in various ways [13:17] distro pushing doesnt help [13:17] only upstream folks going to that bug might help [13:17] they should appeal to mozillas foundation approach ... e.g. they want to be the good guys and want to make the web a better place [13:17] imo having a js lib is the way to go [13:17] maybe if they notice how many folks they bust they will move a bit [13:18] chrisccoulson: the folks commenting there are all senior ... VP etc. [13:18] its not that its some random developers saying that [13:18] its their official strategy in order to compete against chrome [13:19] similar folks should go to chrome and tell them that v8 should become stable [13:19] they have the same answer: "dont use us .. we dont care if there is no other solution ... but its not us" ;) [13:19] asac: may I ask what are you talking about? js library? [13:20] yes ... [13:20] read above [13:20] i think the right way would be someone coming up with a small subset of essential js funcs [13:20] and then writing a wrapper for mozjs [13:20] I read but I'm a little puzzled, is the question about having a stable (api-wise) js library? [13:20] that can be maintained in case they break api [13:21] zyga: yes. if that exists now ( i think there was something for gnome now) ... thats the way to go [13:21] we cant really let anything in the archive with a straight face that uses mozjs or v8 [13:21] asac: what about jscore from webkit? [13:22] asac: it's not v8 but it's was good enough for a long while [13:22] havent checked with them [13:22] maybe thats a choice [13:22] we should try [13:22] but we should first check if its stable with them ;) [13:22] asac: what's the target for that library (I assume it's not a browser) [13:22] desktop apps needing js [13:22] asac: I think that's your choice then [13:22] everyone uses mozjs ... and complains that we dont make a system lib out of it (e.g. we make it intentionally hard to use it=) [13:23] right. i think i pointed a few folks to webkit in the past [13:23] asac: what's the point with mozilla not willing to make it stable api-wise [13:23] (disregarding the fact that mozilla has horrible api that doesn't look like anything else) [13:23] but then webkit has problems on its own wrt to stability/security updates from what i was told by security team [13:23]