[03:26] Good morning [05:06] is there a documented way to get the ia32-libs functionality working on 13.10? [05:06] seems to have broken a bunch of packages [05:20] jetsaredim: Which packages in particular? === tkamppeter_ is now known as tkamppeter [07:53] * didrocks reboots === tvoss|eod is now known as tvoss [08:07] morning [08:08] hey Laney! how was your party? [08:09] we just went to the pub for dinner / beers [08:09] but it was nice! [08:09] how are you? looking forward to the weekend? [08:14] it's weekend for me :D [08:16] Laney: yeah, waiting for it, no party in my city though (for 2 cycles :( ) [08:17] aww [08:20] Laney: do you know where is the configuration used to make those kinds of mount? /var/lib/schroot/chroots/quantal-amd64 on /var/lib/schroot/union/underlay/quantal-amd64-7d9b8eb9-5432-41df-b0aa-62dbe9e76537 type none (rw,bind) [08:20] I think it's sbuild, but not sure where the config file is [08:20] (tried to grep -r in /etc, but no luck) [08:20] hmm? [08:20] What do you want to do? [08:21] The schroot configuration files are in /etc/schroot/ [08:21] hum grep -r quantal /etc/schroot/* [08:21] Laney: I want to remove my quantal chroots (and mounts) [08:22] you have that even after a reboot? [08:22] not sure why they are mounted at boot as well [08:22] yeah [08:22] O_O [08:23] does schroot -l --all-sessions show anything? [08:23] W: No chroots are defined in ‘/etc/schroot/schroot.conf’ or ‘/etc/schroot/chroot.d’ [08:23] session:quantal-amd64-7d9b8eb9-5432-41df-b0aa-62dbe9e76537 [08:24] so, not sure where this definition is [08:24] that's bizarre [08:25] anyway, you should be able to end it with schroot -e --all-sessions [08:25] ok, the session ended [08:25] let me reboot to see [08:27] Laney: ok, at least, the session didn't autobindmount this time, thanks! [08:28] * didrocks is looking at how to remove it cleanly now [08:40] * Laney hugs attente [08:40] that layout change bug is noisy === vrruiz_ is now known as rvr [10:45] didrocks: hi! Regarding updating of cu2d-config with the new saucy branches - what should we do with touch only projects? Should we enable them for daily release only in head? Or only in saucy and leave them disabled as 'to_transition' in head? [10:45] (probably the latter?) [10:46] sil2100: no, please put them in head [10:46] I guess that's what makes more sense [10:46] and disable in saucy [10:46] didrocks: ok, so daily_release: False? [10:47] sil2100: check with fghinther, maybe we need to direcly remove those so that there is no duplication in the upstream merger [10:49] didrocks: ok, he's currently on holiday right now I guess, and he only did a desktop-only stack right now, but maybe I'll catch him for a moment ;) [10:50] sil2100: yeah, let's see :) === sil2100_ is now known as sil2100 [11:26] Hi! Does anyone know if indicator-network-prompt is touch only? [11:26] $ seeded-in-ubuntu indicator-network-prompt [11:26] indicator-network-prompt's binaries are not seeded. [11:26] sil2100: so, not in any ubuntu image, should be touch only ^ [11:27] I didn't see it in the manifest as well, but been wondering if it's indeed used in touch as well, since the dependencies are not explicit [11:27] erm [11:27] seeded-in-ubuntu works for touch too [11:28] $ seeded-in-ubuntu indicator-network [11:28] indicator-network (from indicator-network) is seeded in: [11:28] ubuntu-touch: daily-preinstalled [11:28] oh indeed :) [11:28] sil2100: so it's used, nowhere ;) [11:28] I wanted to catch Pete, but he's not around [11:28] didrocks: I guess I'll split it then ;p ? [11:28] sil2100: no, on the contrary, don't split it [11:28] no maintenance to do on it :) [11:28] Hey Laney [11:29] Ah, so treat it as touch only and let it stay in head? [11:29] hey darkxst [11:29] how goes? [11:29] sil2100: yeah, the question is in fact "do we maintain it for older release?" [11:29] not great right now, car-less still [11:29] oh no [11:30] yah, write-off, with complications [11:30] you crashed it? [11:30] :S! [11:30] nope, it was just parked outside my house [11:31] didrocks: it's only in saucy it seems! [11:31] sil2100: yeah, so will be T only in term of support :) [11:31] sil2100: but please, reach to Pete, not sure why it was developped if not installed === Sweetsha1k is now known as Sweetshark [11:32] don't you guys ever rest, take the day off after a release ;) [11:33] Laney, anyway, all that aside, do you think I would get PPU for ubuntu gnome package set if I applied? [11:33] darkxst: yeah, almost certainly [11:33] I saw jbicha left the team === MacSlow is now known as MacSlow|lunch [11:34] yeh jbicha is gone [11:34] czajkowski: heh, I can see sun + week-end from my window, so week-end is near! ;) [11:34] :/ [11:34] hope you guys find some more manpower [11:34] anyway, yeah, get it in [11:34] ricotz is still there doing is own thing [11:34] which helps a lot with the pre-packaging [11:35] * Laney nods [11:35] I'd +1 you for ubuntu-desktop too, FWIW [11:38] xnox: is ubuntu-installer@ ever used by humans? [11:39] Laney: as in the ubuntu-installer@lists.ubuntu.com mailing list? well ABI bumps are mailed by human, and occasionally installer help / debugging is done there (by human posts) [11:40] ok [11:40] but it is low traffic. [11:40] was going to suggest A lanBell forwards his ubuntu-desktop email there [11:40] still, known bug ... [11:42] Laney, oh thanks! I suppose that would be handy, but means more seb [11:42] haha [11:42] Laney: I wish there was ATK api I could call into to suppress / add events. I re-arrange half of the screen widgets, or change them, and screen-reader doesn't say anything. Or vice-versa, "bling" is animated and is pointlessly announced. [11:42] yeah I don't know anything about that stuff [11:43] hey desktoppers ... [11:43] maybe you want to work on it with TheMuso [11:43] I'm hearing that this bug is a bit urgetnt ... https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1218322 [11:43] Launchpad bug 1218322 in gnome-settings-daemon (Ubuntu) "Can't set keyboard layout change to alt+shift, ctrl+shift, etc." [High,In progress] [11:43] rickspencer3: attente is actively working on that one [11:44] thanks Laney [11:44] he should be on in a little bit if you need more info [12:08] * Laney arghs at PNG optimisation [12:08] This should be able to be parallelised [12:15] quite painful in some packages, isn't it? :) === alan_g is now known as alan_g|lunch === m_conley_away is now known as m_conley [12:32] What is / was: "indicator-session-devices" ? === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g === m_conley is now known as m_conley_away [13:49] tedg: larsu: please review/accept branches linked to bug 1241539, i'd like them merged to trunk. I know there is no t-series to release this stuff to.. but still. [13:49] Launchpad bug 1241539 in indicator-sound (Ubuntu) "ubiquity-dm is missing keyboard, input, sound, system indicators" [High,Triaged] https://launchpad.net/bugs/1241539 [13:54] xnox, K, trunk is 14.04. Do you want them to hit 13.10 branch as well? [13:55] xnox, Also, have you guys discussed switching ubiquity over to being an upstart session for 14.04? [13:56] xnox, Is that on the table for work items? [13:59] tedg: no point for 13.10, cause we are not re-releasing .isos, but i guess at least people will see the fix / indicators in the oem config stage.... [13:59] tedg: i think for 14.04 only. [14:00] tedg: i think investing to make ubiquity upstart session, only if when we switch to mir by default on desktop and start requiring ubiquity to run in mir. [14:00] xnox, I don't see how those are related? [14:01] * tedg assumes that xnox knows Mir and Upstart do different things [14:01] :-) [14:01] tedg: at the moment ubiquity-dm: bypasses lightdm, bypasses X, session upstart, gnome-session. [14:02] tedg: and I'd rather have same feature-parity, if ubiquity-dm becomes user-session and looses ability to spawn fallback X server and the like. [14:04] tedg: thus if i make it user-session, without mir and engineer replacements around X technology, it's a waste of time, cause i'll have to redo it under Mir not so long after. [14:04] xnox, My issue is that I want to move the indicators over to being Upstart jobs. Would you consider running Upstart with no startup event, and then starting the ones you want? [14:04] tedg: yeah, i'd be fine with that. [14:05] tedg: ubiquity-dm already spawns it's own everything, so no reason it can't spawn a custom / small upstart to launch a couple of jobs. actually that might be unintrusive babysteps. [14:06] xnox, Okay, sounds good [14:07] mterry, Do you think that could work for unity-greeter as well? ^ [14:07] tedg, potentially [14:07] tedg: mterry: do note that even system-init has two distict startup events. [14:08] we complete sub-vert boot and do $ init --start-up-event recovery to start in recovery mode with menu-selection. [14:08] and once done we simply emit normal "startup" event to kick off / complete normal boot. [14:09] similarly there is no reason why indicators can't all start on "indicators" event [14:09] and then for normal login we have a dummy "emit indicators" upstart job. [14:09] and in case of ubiquity/unity-greeter, spawn init --start-up-event indicators. [14:10] All the indicators do start on an indicator event. [14:10] It's emitted by Unity 7/8 [14:10] When they're ready to have indicators. [14:17] ooh, nice. [14:17] so i can start init, and emit indicators after panel is up. [14:17] but i guess my panel.c just force loads them... [14:20] Yeah, I think that makes sense. [14:21] Then effectively all the indicators are "one PID" from the greeter/ubiquity's perspective. [14:21] Means that we can easily reshuffle them without breaking. === alan_g is now known as alan_g|tea [14:32] happy friday desktopers! [14:33] someone please review my patch update in the g-c-c packaging branch [14:33] happy friday seb128! [14:33] Laney, hey, you yoo! [14:33] Laney, looking to g-c-c [14:44] xnox: sure === alan_g|tea is now known as alan_g [14:57] Laney, that seems a weird way to do it [14:57] what do you recommend? [14:57] Laney, what we have been doing in other places is what 51_unity_options_in_display_panel.patch do [14:58] + schemas = g_settings_list_schemas (); [14:58] + while (*schemas != NULL) [14:58] + { [14:58] + if (g_strcmp0 (*schemas, UNITY2D_GSETTINGS_LAUNCHER) == 0) [14:58] well, your way seems fine, it's just not what we are doing in other places [14:58] is that better? [14:58] I stole this idea from the 'gsettings' tool [15:00] Laney, desrt says your way is about the best we can do [15:00] Laney, so +1 [15:00] Laney: seb lies [15:00] the best we can do is to have the panel in the indicator itself, as with datetime [15:00] that is the correct thing to do [15:00] since we diverge from gnome upstream on the panels anyway.... [15:01] completely fork it? [15:01] that's what datetime did [15:01] Don't know how much that has in common with the upstream panel [15:01] this just adds one label/combo [15:01] the other alternative is to have gsettings-ubuntu-schemas and depend on that [15:01] that's why gnome does gsettings-desktop-schemas [15:01] it'd be a bit annoying to do a whole fork for that [15:02] well [15:02] we keep talking about wanting to do u-c-c anyway [15:02] yes, /that/ would be good [15:02] because then you get easy merging with upstream [15:03] Laney, desrt: well, that change is the easiest thing to do/right fix until we have a proper fork [15:03] ya [15:04] thanks for the review [15:12] https://errors.ubuntu.com/problem/a070e0e0f342f3d445cf13bf28f08d2868be0ba3 [15:12] this seems noisy [15:16] Laney, I talked to robru about that one yesterday [15:18] yeah? [15:18] Laney, he said that it happens when running friends from raring with pygobject from saucy [15:19] Laney, it's likely it's happening during upgrades, pygobject gets upgraded first and during the time in between pygobject and friends are upgraded, the friend-dispatcher is started (its keeps going up and down) [15:22] okay, then a Breaks should fix it [15:22] or fixing the code in raring to work with both [15:23] seb128: precisely the sort of thing ostree fixes, btw [15:24] walters, yeah... [15:25] (and unlike Image Based Upgrades, it has a sane story for how it interoperates with packages) === seb128_ is now known as seb128 [16:29] rickspencer3, hey, I read the backlog and I saw you pinged about that keyboard/keybinding issue, do you have any specific on what bits are important? [16:30] rickspencer3, (it's being actively worked but it mixes several issues and some of those are non trivial to fix, just trying to figure out if there is a workaround we could use that would it less of an issue for users until it's properly resolved) [16:31] seb128, I dunno, silbs mentioned that a lot of folks were pinging her about it [16:31] Laney said it was being handled, so that was good enough for me :) [16:31] rickspencer3, can you get specifics about the ping/what is the main concern? [16:32] rickspencer3, well, "being handled", attente has been spending the last few days on it (as you can see from the bug comments/ppa roundtrips) [16:32] rickspencer3, so yeah, it's actively worked, but we don't have a solution fixing all the problems yet [16:33] hmm, the latest LC_stuff change is a bit buggy [16:34] rickspencer3, though part of the issue is that users can't set the keybinding to some value (e.g l-shift+r-shift), I wonder how much of an issue that is [16:34] rickspencer3, or if changing the default to e.g ctrl-alt and having that working would be good enough for most users [16:34] Laney, in u-s-s? [16:34] Laney, how so? [16:35] hang on, trying to get the output [16:35] don't distract Will though; I'll look at it (maybe on Monday) :-) [16:35] Laney, right [16:35] no hurry for u-s-s [16:35] it's not like those changes would land on an image this week anyway [16:36] indeed [16:36] http://paste.ubuntu.com/6258334/ [16:37] Laney, it's like the 2 calls were done using different locales [16:40] Laney, [16:40] [16:40] 162 [16:40] act_user_set_language(user, qPrintable(languageCode.left(languageCode.indexOf('.')))); [16:40] [16:40] 163 [16:40] act_user_set_formats_locale(user, qPrintable(languageCode)); [16:40] shouldn't they both use "languageCode.left(languageCode.indexOf('.')"? [16:40] Dunno [16:40] I'm guessing it was deliberate [16:41] attente, ^ [16:43] hmm [16:44] the dbus api documentation says they should be the same [16:44] Laney, he's doing the '.' stuff to filter the UTF-8 out [16:48] seb128: https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/accountsservice/saucy/view/head:/data/org.freedesktop.Accounts.User.xml#L153 [16:50] Laney, ok, does dropping the ".indexOf('.')" resolve the issue? [16:50] let's see [16:52] hmm [16:52] sil2100, fginther: do we have mergers for 13.10 branches? [16:52] sil2100, fginther: https://code.launchpad.net/~larsu/libindicator/always-create-widgets/+merge/191701 is sitting there with no CI nor merge happening [16:54] seb128: I doubt we have those yet - fginther is on holiday today, and the merge for updating cu2d-config for indicators is still awaiting review [16:56] Laney, seb128: I tested if the locales were changing with that branch attente prepared and they were, didn't check the api docs though [16:56] I was assuming those were deliberate as well [16:57] Well, AS actually rejects it if you pass e.g. de_DE on its own [16:57] so I don't really get what it set [16:57] the property was actually set to de_BE.UTF-8 [16:57] needs more debugging [16:58] Laney, k [16:58] Ok, so maybe I approved to hastily? [16:58] sil2100, should I just manually SRU that libindicator fix then? [16:58] it's still an improvement [16:59] we can fix in followups [16:59] cyphermox, ^ (the SRU question) [16:59] cyphermox, hey btw [16:59] Laney, yeah [16:59] seb128: I would guess if it's important, let's do that - since today we won't get CI and mergers prepared for sure [16:59] Since we need fginther to be around for that [17:00] sil2100: what>? why? [17:00] isn't that commit merged yet? [17:00] Laney, seb128: right, sorry about that - I think I probably tested such a case where all locales got set to the same thing [17:00] cyphermox: which one? [17:00] sil2100, ok, let's do that [17:00] tedg, ^ side effect of your early branching btw :/ [17:00] seb128: yeah, upload directly [17:01] seb128: I don't think it's an issue with branching [17:01] cyphermox, sil2100: thanks [17:01] but I'll take a look at the config again to check what'sup [17:01] cyphermox, well, it's an issue of creating stable branches without making them be under CI [17:02] seb128: they should be under CI already [17:02] cyphermox, sil2100 says it's a fginther thing [17:02] https://code.launchpad.net/~sil2100/cupstream2distro-config/apps_click_friends_hud_indicators_13.10/+merge/191788 <- this would have to be in, and fginther would have to set up the mergers/CI for those new branches [17:02] cyphermox: they can't be in CI if they're not in cu2d-config [17:02] the config should be sufficient for the branch to be covered [17:02] cyphermox, https://code.launchpad.net/~larsu/libindicator/always-create-widgets/+merge/191701 didn't get CI review/comments nor merging though :/ [17:02] k [17:02] cyphermox: if cu2d-config doesn't have the /13.10 branches in it and fginther doesn't pull that in on the mergers side, there's no CI [17:03] Is anyone on devicekit-devel? [17:03] sil2100: I understand that but it should have been added as part of the procedure of branching, a few weeks ago [17:03] Laney, pitti maybe? [17:03] If so, please bounce me hadess' email [17:03] cyphermox: sadly it was not [17:04] cyphermox: me and fginther started doing that yesterday evening [17:04] Removed signals: [17:04] - changed (both UpClient and UpDevice), device-changed (connect to the [17:04] "notify" signal for the properties that interest you instead) [17:04] Changed [17:04] ignore "Changed" [17:04] sil2100: ping the ci team on #ubuntu-ci-eng, they can do it [17:04] it shouldn't ever have to be only fginther [17:05] Laney, is that going to create issues? [17:05] It's going to create porting [17:06] It now implements the proper PropertiesChanged signal which is great, but killing the old interface without any transition period is unfortunate IMO [17:06] yeah :/ [17:06] (D-Bus and GLib API changes are pretty much the same) [17:07] ok, noted to follow that up on monday too [17:07] have a good weekend ;-) [17:08] Laney, thanks, you too [17:08] have a good weekend Laney! [17:09] yeah, we have http://gamecity.org/about in town which I'll check out :D [17:09] * Laney waves [17:09] nice [17:09] Laney, have fun! [17:12] seb128, To be fair, I asked the CI folks before doing it. They told me it wasn't a big deal, and I should start branching. [17:15] tedg, sure, easy for them to tell, they don't have code to land [18:00] why would I still be receiving empathy messages even though i've quit empathy ? [18:00] how does one completely turn off empathy ? [18:00] is that more of a #ubuntu question tho, i'll head over there [18:04] hmm, i c.. it's directly integrated into the status set in messaging-menu. If you're not "offline" on there, you will still continue to receive messages [18:24] i take my previous statement back, im offline and still receiving messages [18:31] bcurtiswx, that seems buggy [18:31] bcurtiswx, the fact that closing the empathy UI doesn't send you offline is a known/normal [18:32] bcurtiswx, but setting the status offline should work === m_conley_away is now known as m_conley [18:40] seb128, OK thanks, i'll get a bug report done soon :) [18:40] bcurtiswx, thanks [20:06] should the hud-service be taking up 15% of my 8GB of RAM ? [20:57] bcurtiswx: discovering the amount of memory actually used is somewhat difficult. Or maybe, subtle. Check out the 'smem' tool, it tries to place blame on applications for memory usage in a different way that might be more instructive [21:26] Hi! I just upgraded to 13.10 amn everything work great, but I got two network-manager icons in my systray. One had all the functionality and the other just the possibillity two turn the NIC's on/off... I tried uninstalling and reinstalling network-manager but now I only got one icon but its not working at all... Anyone got a clue?