=== wgrant_ is now known as wgrant [01:54] lamlex: ping [01:55] lamlex: how would you feel about a "multi-monitor" tag in lp.net/unity? [07:51] good morning [07:54] good morning [09:50] kamstrup: hi. do you have time for review? https://code.launchpad.net/~kvalo/indicator-network/libconnman-control-technology/+merge/50750 === ogra_ is now known as ogra [10:05] rodrigo_, Settings schema 'org.gnome.desktop.interface' does not contain a key named 'toolkit-accessibility' [10:05] rodrigo_, how do I fix/work-around that? [10:08] rodrigo_, sorry, session died [10:08] still having the same issue [10:08] didrocks, ^ know anything about that? [10:12] njpatel: is that the latest revision? [10:12] yeah [10:12] and updated box [10:12] I can't start unity :/ [10:12] njpatel: I'm still updating, my bet is that the schema is update in /usr/local/share and not in /usr/share [10:13] didrocks, there are no schemas in /usr/local in my system [10:13] didrocks, this schema isn't from unity, I don't think [10:13] njpatel: yeah, it's not, let me see here [10:14] njpatel: so yeah, no /usr/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml in toolkit-accessibility [10:14] awesome [10:14] * njpatel adds a way to disable a11y in unity [10:16] njpatel: oh yeah, please :) [10:17] kvalo: approved [10:17] added UNITY_A11Y_DISABLE [10:17] (in my branch, which I'm proposing in a bit) [10:19] njpatel: so, unity will break in with older gsettings-desktop-schemas [10:19] njpatel: not sure there is a comment in the log telling that we need the new one [10:19] right [10:22] njpatel, we need a new gsettings-desktop-schemas, which you can get from the gnome3 ppa -> https://edge.launchpad.net/~gnome3-team/+archive/gnome3/+packages [10:23] njpatel, take care though to just install that package [10:23] rodrigo_: is it in natty already? [10:23] rodrigo_: because there is a release tomorrow :) [10:23] seb128 was going to upload it to main as soon as debian does the update [10:24] so, if it makes unity fail at start… [10:24] seb128: some info on that? ^^ [10:24] can we just get it in? [10:24] in any case, unity needs to breaks on the older one to avoid cherry-pick upgrade issue [10:28] it should probably depend on 0.1.7 [10:28] (on the phone) [10:29] rodrigo_: rather breaks on older, isn't it? [10:29] rodrigo_: or there is now lib symbols? [10:29] anyway, pochu from debian is going to update it today, and then it will be merged with the ubuntu package [10:29] didrocks, no symbols in gsettings-desktop-schemas, just schemas [10:30] it can by synced frm debian most likely [10:30] he did the update [10:30] kamstrup: thanks! [10:30] rodrigo_: yeah, so breaks: on older [10:31] didrocks, ok [10:31] rodrigo_: can you warn us on that for the future please? MacSlow was desperate yesterday evening :) [10:32] didrocks, rodrigo_, njpatel: sorry on the phone but the new gsettings-desktop-schemas can likely be synced from experimental, pochu did the update [10:32] someone should check they patch to change the default screensaver though [10:32] didrocks, I didn't know that branch had landed, we discussed it yesterday and we talked about doing the merge after the package was updated [10:32] but seems the branch was merged before [10:33] rodrigo_: yeah, the branch was merged yesterday [10:33] seb128, ah, already updated then? [10:33] didrocks, yes, I see it now [10:33] seb128: I won't have the time, in any case, I need unity to breaks: on it for avoid partial upgrades [10:34] didrocks, sweet... the fix works [10:34] didrocks, just sync-source g-d-s if you want [10:34] we can fix the default screensaver thing later on [10:34] seb128: ok, doing that then :) [10:34] from experimental? [10:34] yes [10:34] ok, doing, thanks! [10:35] you're welcome [10:35] seb128, default screensaver? [10:35] rodrigo_, the debian guy added a patch to change the default value of the screensaver key [10:35] seb128, we don't use that schema in natty, only in the gnome3 ppa, right? [10:35] ah ok [10:36] anyway, need to reboot, brb [10:36] njpatel, rodrigo_, didrocks: was the issue with unity r878 and r879 solved? [10:36] MacSlow: yeah, you need a newer g-d-s [10:36] MacSlow: I'm doing the sync now [10:36] didrocks, what?! [10:36] ok [10:36] gsettings-desktop-schemas [10:38] MacSlow, once I get an +1, I'll merge my branch that has a workaround that disables a11y [10:38] MacSlow, will ping you [10:38] njpatel: yeah, sorry doing the sync first :) [10:39] np :) [10:39] njpatel, cool... after that I'll merge-propose the superkey-label stuff [10:41] MacSlow, sweet [10:42] njpatel, I guess you've seen the screencasts [10:42] MacSlow, yep, very cool :D [10:42] the dynamic reassigning of reordered icons is very cool [10:42] njpatel, a bit over the top... but funky [10:42] yeah, /me likes [10:43] no, it's attention to detail, so it's nice to see :D [10:53] MacSlow: the good news is that it wasn't to complicated to get it from the model :) [10:54] didrocks, :) [10:54] yeah for effiency \o/ [10:54] MacSlow: so, basically, you'll need gsettings-desktop-schemas 0.1.7-2, sync done, but still need rebuild and publish === API is now known as Guest88340 === Guest88340 is now known as apinheiro [11:17] rodrigo_, we need to switch to gconf from gsettings for the a11y stuff, as natty is going to still be using gsettings [11:17] bah, still be using gconf* [11:17] seb128, didrocks ^ [11:18] rodrigo_ is back [11:18] njpatel, talk to apinheiro, I thought it was already using gsettings [11:18] apinheiro, ^ [11:18] njpatel, I don't understand [11:18] rodrigo_, right, it's using gsettings, it should not [11:18] we are using gsettings [11:18] ah [11:18] natty is GNOME 2.32 [11:18] well [11:18] it's using gconf [11:18] right, but we need to use gconf [11:18] " natty is going to still be using gsettings" [11:18] hmmm [11:18] apinheiro, I corrected myself afterwards [11:18] " bah, still be using gconf*" [11:18] on the next line [11:18] ups sorry [11:18] njpatel, ok [11:19] lets create two bugs about that [11:19] one for the service panel [11:19] and the other for unity [11:19] So, yeah, please switch to gconf, I'm about to land a branch that adds gconf as a dep, so if you wait ~20mins you can branch off trunk [11:19] apinheiro, but at-spi1 uses gsettings already? [11:19] rodrigo_, I think this is for the "should we enable a11y" check [11:19] rodrigo_, yes, but it was not a replacement [11:20] njpatel, yes [11:20] and it doesn't include the enable toolkit gconf [11:20] apinheiro, ah, so it supports both gconf and gsettings? [11:20] njpatel, there is just a problem [11:20] that the old gconf variables [11:20] doesn't include the bridge location [11:20] that was one of the reasons to move to gsettings [11:20] right, and we need it [11:20] so we can use both, right? Thats fine [11:20] both? [11:21] njpatel, as I said there isn't any gconf variable exposing the atk-bridge location [11:21] well another option is to patch the capplet to write in gsettings [11:21] connect to gconf to monitor whether we need to be enabled or not [11:21] and connect to gsettings to get the settings [11:21] ugh [11:21] njpatel, ah ok [11:21] everything we need is in gsettings, so why not just use that? [11:21] so you are saying that to check if a11y is enabled [11:21] seb128, but will other applications be listening to gsettings in natty? [11:21] we should use gconf [11:21] unity already uses gsettings for other stuff, right? [11:22] but to get the bridge location [11:22] use gsettings? [11:22] apinheiro, exactly, so we follow what the rest of the desktop is doing [11:22] but one question, as rodrigo_ says [11:22] why don't use [11:22] njpatel, oh, I meant to write in gconf and gsettings [11:22] rodrigo_, we need to use gconf too where we have to read settings from gnome that aren't in gsettings yet [11:22] gsettings for both [11:22] njpatel, i.e write both keys [11:22] ah ok [11:22] because the bridge location is already on at-spi1 [11:22] right? [11:22] seb128, oh, okay, that would work too, as long as we're sure we're not breaking scripts that relied on the old location (and didn't use the capplet) [11:23] we have a gconf->gsettings bridge in g-s-d 2.91., so we could port it to 2.32 [11:23] instead of having to patch apps to write to both gconf and gsettings [11:23] Instead of all of this, why not just connect to gconf to get the initial true/false, and monitor that for natty? [11:24] because we need to read gsettings for the atk bridge location [11:24] right apinheiro? [11:24] rodrigo_, isn't the bridge the other way around? [11:24] or make the ugly assumptions that firefox does [11:24] the other way around? [11:24] what do you mean? [11:25] rodrigo_, I don't understand, gconf and gsettings aren't mutually exclusive, you can use both [11:25] we *do* use both when we need to work with old GNOME stuff [11:25] i'm just about to land a branch that does that [11:25] njpatel, well, but my question is still here [11:25] why don't use gsettings to check in the a11y is enabled? [11:26] because the GNOME dialog doesn't write in gsettings [11:26] apinheiro, because the capplet isn't updating gsettings, it's just updating gconf [11:26] so the key will never be set [11:26] ok [11:26] we still have GNOME 2.32 [11:26] apinheiro, and because we don't know if other people's tools are also just updating gconf instead of gsettings [11:26] thanks, no I understand [11:26] so concluding: [11:26] so I'd like to just work with gnome as it is [11:26] a11 enabled: use gconf as the dialog is updating it [11:27] atk-bridge location: use gsettings as at-spi1 already has a patch with it [11:27] right? [11:27] right [11:27] ok, was hard, but in the end we conclude something ;) [11:27] ok [11:27] so lets create two bugs [11:27] one for the service [11:27] and one for unity [11:27] btw [11:28] njpatel, this is related with MacSlow mail about unity hanging on start? [11:28] apinheiro, i believe that is because we don't have the very latest gsetting schemas, didrocks has uploaded them [11:29] well, yes, I realized that by mistake, I update the accessibility check to "toolkit-accessibility" [11:29] as it is right now on upstream [11:29] my mistake [11:29] anyway, gsettings causing a crash [11:29] just because you are asking for a wrong setting name [11:29] is really bad [11:29] as we need to move it to gconf [11:30] I can make a sanity commit [11:30] in order to not check the gsettings for the accessibility [11:30] yeah, I can't believe gsettings does that [11:30] so people could start unity wihout problem [11:30] I'm waiting to merge something that adds a UNITY_A11Y_DISABLE option [11:30] well, there's a way to check for the schema before getting the key [11:30] then it would be solved when we integrated the gconf thing [11:30] so I think that shoudl be fine [11:31] well, our "unity_a11y_disable" was just disabling the gsettings [11:31] rodrigo_, that's the most annoying aspect, that it g_error's but there isn't a way to sanity check! :) [11:31] I didn't know that gsettings was so unstable === MacSlow is now known as MacSlow|lunch [11:31] it's by design it seems (to g_error) [11:31] rodrigo_, yes we are checking if the schema is there [11:31] but it seems [11:32] that if you ask for a setting on this schema [11:32] and this setting is not on the schema [11:32] it crashes [11:32] njpatel, but ok, I will make a sanity commit to avoid the unity crash [11:32] apinheiro, no, afair, we are calling g_settings_get directly, without calling g_settings_list_schemas, right? [11:33] no [11:33] we have a check [11:33] static gboolean [11:33] has_gsettings_schema [11:33] apinheiro, sweet [11:33] ah, right [11:33] /* we need to check if AT_SPI_SCHEMA is present as g_setting_new [11:33] could abort if the schema is not here*/ [11:33] so although we check it to avoid a crash is the schema is not there [11:34] it will crash if we ask for a wrong setting [11:34] wrong == wrong name [11:34] apinheiro, is there a way to check if a schema exists? [11:34] * njpatel should do the same sanity check where he uses gsettings [11:34] you dont' want your WM crashing ;) [11:35] njpatel, yes, we use that on the a11y initialization [11:35] unitya11y.cpp method has_gsettings_schema [11:35] * njpatel looks [11:36] njpatel, we ask all the schemas available [11:36] list_schemas = g_settings_list_schemas (); [11:36] and then we check if our schema is on this list [11:36] oh :/ [11:36] that seems slow [11:36] maybe better to desrt once here? [11:37] to do what to desrt? ! [11:37] ;) [11:37] argh, eating words :p [11:37] ask* [11:37] or hit if you are really angry about that crash :) [11:37] I let you choose guy! ;) [11:38] njpatel, well, there isn't a really big list of schemas installed [11:38] and it is just a comparison with the list [11:38] in practice, I didn't notice any slowdown [11:39] apinheiro, sure, sorry, I'm just thinking out alound [11:39] I guess gsettings has a cache anyway [11:39] so it won't be bad [12:01] njpatel, I have just made the sanity commit [12:01] thanks [12:02] MacSlow|lunch, trunk should be safe now === MindWarper_ is now known as MindWarper === MacSlow|lunch is now known as MacSlow [12:44] njpatel, thanks! === m_conley_away is now known as m_conley === joaopinto_ is now known as joaopinto [14:22] ronoc: hey, IIRC, you told me to reset something in gsettings that can explain why I have banshee twice in the soundmenu, I remember to do that, log out/log in, but I have still have two of them [14:25] didrocks: dbarth: any other branches pending? [14:25] from new people? [14:26] jcastro: not that I noticed [14:32] morning all [14:32] didrocks: lamlex: I had an idea yesterday [14:32] what do you guys think of lumping all the twinview/multimonitor stuff in a tag? [14:32] * lamlex claps [14:33] jcastro: do you think that it's a big enough section of bugs? [14:33] hooo boy, I absent-mindedly did apt-get upgrade, and Natty on my Virtualbox is broken. *sigh*. [14:33] cyphermox has a branch up now for better multi-monitor support [14:33] I counted at least 6 or 7 unscientifically yesterday [14:34] lamlex: isn't it only for changing resolution? it's really muti-monitor support? [14:34] jcastro: hum, that would be possible [14:35] didrocks: no it's also to relayout on monitor added (afaik) [14:36] ok :) [14:37] lamlex, better? [14:37] i haven't tested it [14:37] nvidia [14:37] is f'ing up my life [14:38] fwiw I got a review from smspillaz too, and he brought up a good point, hooking up to outputChangeNotify [14:38] didrocks, gsettings reset com.canonical.indicators.sound blacklisted-media-players [14:38] anyone running a daily or trunk of unity? [14:39] didrocks, whoops sorry it should be [14:39] didrocks, gsettings reset com.canonical.indicators.sound interested-media-players [14:39] ronoc: ok done, at next login, it should be changed, right? [14:39] jcastro: almost trunk there, why? [14:40] didrocks: I need a screenshot of the fixed trash can quicklist [14:40] didrocks, just restart the service [14:40] I have the broken one, I want to show a before and after [14:40] killall indicator-sound-service [14:41] jcastro: if you are not afraid of French, I can show you :) [14:41] didrocks: good enough [14:49] ronoc: excellent! I got two soundbars now (think it's a known issue, right?) but just one bansee [14:50] didrocks, if the service crashes its a side effect, will fix [14:50] jcastro: http://people.canonical.com/~didrocks/correct-tash-quicklist.png [14:50] ronoc: ok, thanks :) [14:52] didrocks: that's the correct one? It looks like mine, wrong. :) [14:52] jcastro: hum? no it's centered on the Trash now [14:53] jcastro: before it was above it [14:53] oh I see it now [14:53] thanks [14:53] yw :) [14:53] ok, there still appears to be too much space [14:54] in the quicklist itself, but whatevs [14:54] jcastro: the bug wasn't about that, just the placement :) [15:32] didrocks: https://bugs.launchpad.net/unity/+bug/604619 [15:32] I can mark invalid right [15:33] Anyone know what's up with: https://bugs.launchpad.net/unity/+bug/718886 [15:35] bug 718886 [15:35] Launchpad bug 718886 in unity (Ubuntu) "Maximized windows do not always undecorate properly on initial map" [Undecided,Confirmed] https://launchpad.net/bugs/718886 [15:35] weird bot! [15:35] iirc, usually bot would announce the bug even when link is pasted.. [15:39] lamlex: oh right, I think it's gone for a while :) [15:39] jcastro: I can't reproduce it [15:39] ah [15:57] didrocks: this one? https://bugs.launchpad.net/unity/+bug/604621 [16:00] lamlex: this one is still valid I guess as zg is empty (or you can replace with recent files) [16:01] lamlex: but I think in that case, we have now the home folder showing [16:08] didrocks: well this is for applications [16:11] lamlex: yeah, not sure about that one, we should check [17:29] dbarth, ping [17:49] "Don’t worry, these are from two different computers, we won’t turn your labels into French" [17:49] jcastro_: -> I can make this a reality ^ :-) [17:49] yeah! [17:52] jcastro_: I changed the "lock" state for the fading for next release [17:52] jcastro_: should be more obvious now [17:52] jcastro_: sorry, misread your post, that what you stated :) [17:54] (I like the (NEW!) tag, sounds like in a supermarket) [17:56] njpatel, btw, the gconf thing is finished [17:56] https://code.launchpad.net/~apinheiro/unity/Bug723699/+merge/50963 [17:57] just waiting for review [17:57] (although rodrigo already reviewed it) [18:12] apinheiro, sweet, thanks! [18:26] hello, can someone help me debug an issue i found in unity-place-applications? the problem is trying to launch the FBreader app from the dash; it doesn't seem to work because the .desktop file's path has capital letters in it, and i think u-p-a might be sending the wrong path [18:27] a clue on where to narrow my search would be much appreciated [18:36] ronoc: if you have time for review (can wait until tomorrow): https://code.launchpad.net/~kvalo/indicator-network/settings-tech-control/+merge/50972 [19:15] lamlex, bug 684361 -> the answer is "no" - i can't batch-change the status, could you do it? [19:15] Launchpad bug 684361 in unity (Ubuntu) "Closing an application crashes Compiz" [Undecided,Incomplete] https://launchpad.net/bugs/684361 [19:15] sure [19:15] thanks [19:15] thanks :) [19:28] lamlex: hey, any reason Bug #686133 has the ayatana design task open.. [19:28] ? [19:28] Error: Could not parse data returned by Launchpad: list.index(x): x not in list (https://launchpad.net/bugs/686133) [19:28] stupid ubot5 ! ;p [19:28] lamlex: btw, when closing a unity bug as opinion or invalid, do feel free to close the papercut task too ;) [19:29] Bug 686133 [19:29] Error: Could not parse data returned by Launchpad: list.index(x): x not in list (https://launchpad.net/bugs/686133) [19:29] meh, ubot5 is not a very good bot.. [19:29] hah [19:30] vish: can you just paste link? [19:30] lamlex: https://launchpad.net/bugs/686133 [19:30] oh, bugbot got that part right [19:30] why does that have a design task? [19:30] because that's a design issue [19:31] oh open [19:31] i dont know.. [19:31] well design has not made a decision I guess [19:31] sorry I misunderstood what you were asking me at first [19:31] lamlex: chris was in a phase where he opened a design task for a lot of bugs.. and this was one of them ;) [19:32] yah this should have a design task, that is good [19:32] lamlex: right, but since you closed the task as opinion it seemed like there was a decision.. [19:32] unity one. [19:32] vish: no, just updating based on unity bug policy [19:33] ah! [19:33] https://wiki.ubuntu.com/Unity/FilingBugs#Design%20Bugs [19:33] we mark the unity task opinion to get it out of our face until design makes a decision [19:33] hmm, thats not an ideal workflow.. [19:34] then design marks the unity task confirmed (or triaged-I forget which) or wontfix when theyve made a decision [19:34] vish: no it's pretty ideal [19:34] lamlex: for other Ubuntu packages, opinion should be used for something that the designer will not fix [19:34] lamlex: but lets people continue the discussion [19:35] vish: well the ayatana-design task doesn't got to opinion [19:35] there are some semantics here [19:35] the unity task is "we dont care but keep talking we are not dealing with this until we hear from design" [19:35] yea, but now unity workflow is different from *all* ubuntu pacakges [19:35] packages* [19:35] no it's not really it's just specialized [19:36] because the unity team is saying we can't look at this but you can keep discussing [19:36] lamlex: actually it will lead to confusions :), ex: see the comment there after you marked opinion [19:36] he thought you consider it case closed [19:37] it could have been an "incomplete", IMO [19:38] we talked about that but that's not ideal for us [19:38] incomplete means waiting for more user input [19:38] the UNITY team are not waiting for user input, that's why the design task stays open [19:38] well, its not necessarily always, incomplete can be waiting on some other task too.. [19:39] this is the workflow that is best for us, it's not that complex and people will need to get used to it [19:39] ok.. ;) [19:39] we need to get design bugs off of our radar until the design team tells us what to do [19:39] wontfix isn't right, incomplete doesn't get them out of the way [19:40] if the team wanted to differentiate, it could be incomplete status + a needs-design tag [19:40] thats another way design bugs are handled in other ubuntu packages [19:40] it stays in the bug list though [19:40] you can do lp searches with status and tags [19:41] to exclude on tags? [19:41] yup [19:42] well damn, someone should have told me that before we made this workflow and have already been using it a ton [19:42] ill talk to didrocks tomorrow I guess [19:42] thanks.. :) [19:44] lamlex: https://wiki.ubuntu.com/Bugs/Tags#Different%20ways%20you%20can%20help [19:44] those are some common tags. [19:44] rather, most of the common tags [19:45] thanks [19:48] lamlex: for excluding tags, the link should end in > +bugs?field.tag=-TAGNAME note the "-" before the tagname [19:48] yah [19:48] i found it in the lp help docs :\ === ivanka is now known as ivanka-train === Amaranth_ is now known as Amaranth === Artir is now known as Omega-lulz === Omega-lulz is now known as Artir === Artir is now known as Omega-lulz === Omega-lulz is now known as Artir === sladen is now known as 5EXAB7I4U === chaotic_ is now known as chaotic === mdeslaur_ is now known as mdeslaur === RAOF_ is now known as RAOF === achiang` is now known as achiang === m_conley is now known as m_conley_away === popey_ is now known as popey === Pici` is now known as Pici