=== tmpRAOF is now known as RAOF [06:53] Hi all! I would like to fix https://bugs.launchpad.net/unity/+bug/1241972. Can someone here give some pointers? [06:53] Ubuntu bug 1241972 in Unity 7.2 "Drag and drop from Dash to Desktop doesn't work" [High,Triaged] [06:54] I have gone through https://unity.ubuntu.com/getinvolved/development/unity/ and successfully build unity. [09:42] tsdgeos: see the bug update, I'm not sure what to do - should it be seen if the autopilot issue could be fixed by adjusting how it uses DBus? [09:42] Mirv: it should yes [09:42] i don't think it's an autopilot issue per se [09:42] or may be [09:42] but my most probable guess without actually having read the code or the errors :D [09:43] is that stuff is now faster since more threads are used [09:43] so the uitk tests need a few more "wait for this to happen" [09:43] that they didn't need before because everything was slower [09:46] tsdgeos: it's not just UITK tests, it's basically all suites as quoted partially in the report === duflu_ is now known as duflu [09:46] Mirv: it's not uitk that is faster now, it's qt [09:46] D: [09:46] i can give you the same explanation [09:46] but as said, somebody needs to look at it [09:46] right. I think the fix should be on a global level instead of fixing each autopilot suite manually. [09:47] I guess QA then [09:47] Mirv: you can't fix "my test is bad" on a global level [09:47] if that's what it is [09:47] it's annoying that it's hard to validate whether the DBus patches were good or not, since the tests don't work... [09:48] tsdgeos: unless it's something autopilot does in some place of it, or the UITK provides to other suites or some such [09:51] yep [09:51] needs investigating [09:59] tsdgeos: ok, discussed in landing meeting and moving to #ubuntu-qa to try to get someone to help [10:00] cool, i'm busy digging some autopilot issue on unity8 [10:00] i'll try to see if i can find somet time too [10:01] #ubuntu-quality, that is! :D [10:01] Qatar LoCo would definitely use some manpower too, I visited there first [10:02] Saviq: tsdgeos: when you have time please also redo the reboot tests with the updated silo 018 that includes the two last DBus patches [10:04] :D === marcusto_ is now known as marcustomlinson [10:30] it seems like when you tap an item to go to a preview [10:30] the currentIndex property of PreviewListView jumps from [10:30] the right number to 0 [10:31] https://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Dash/PreviewListView.qml#L100 [10:31] if you put a onIsCurrentChanged: if (isCurrent) console.log("I'm current!", index) there [10:31] and then you tap on item 5, currentIndex goes to 5, and then to 0 [10:32] if you touch the list, then it goes back again to 5 [10:32] tsdgeos: ^ [10:32] any idea why that might happen [10:32] ? [10:32] I tested it with tryGenericScopeView, fwiw [10:33] faenil: let me read again, not sure i understand [10:33] ok [10:38] basically imagine you have a scope, with a category, with results [10:38] you tap on the result with index 5 [10:38] PreviewListView opens [10:38] currentIndex is set to 5, and then to 0 [10:39] but if you try scrolling the list, it is set to 5 again, which is the correct value [10:39] now, I don't understand the jump to 0 [10:40] listview is pretty crap all in all [10:40] yes i see what you mean [10:40] can't say anything else other than if you can have a look to see if you see something obvious which can be the problem [10:40] if not open a bug and i'll have a look when i can [10:41] that means I can't know the index of the currently shown item, unless I work it around by saving it before it's changed to 0 [10:41] otoh [10:41] ok, thank you, I'll keep poking [10:41] you should not try to know the indexes of things [10:42] mostly everything you want to know should come through models and stuff [10:42] but yes it's not an excuse for this not working [10:43] tsdgeos: how do you take an action on an item without its index? can I define functions in the models with implicit indexes? [10:43] (aside setting properties, I mean) [10:44] faenil: what do you mean "take an action on"? [10:45] whatever you want to do on that particular item which is not setting one of its properties [10:46] setting a property :D [10:46] or if you really really need to call a function [10:46] we usually have a proprety of the delegate that is an internal pointer [10:46] so we pass that internal pointer to the model [10:46] and then the model knows what you're talking about [10:46] no matter of the index [10:46] mmm sounds even hackier? :D [10:47] not really i mean i could be doing whatever i wanted on the ui [10:47] using an id is what makes more sense [10:47] i don't call it [10:47] scope 0 [10:47] but scope "appsscope" [10:47] ok.. [10:48] but that's just generic suggestions [10:48] obviously it may not apply to your use case [10:50] yeah, I'll see what I can do, thanks ;) [10:54] faenil, if it resets to 0, might be the model... [10:55] faenil, I saw when listview updating, sometimes resets to 0 [10:55] not something we control [10:55] Cimi: the problem isn't resetting to 0, it's not going back to 5 :D [10:55] ouch [10:56] it only goes back to 5 when I touch the list [10:56] faenil, maybe because we set to 5 before the model is loaded [10:56] ah... [11:03] tsdgeos: if you can join #ubuntu-quality so you'll too have a proper backlog.. [12:00] tsdgeos: onCountChanged is called twice with the same value...so something from cpp thinks the count has actually changed and emits.. [12:00] faenil: it's a mock, don't expect it to be awesome :D [12:01] not sure it's because it's a mock... [12:02] tsdgeos: anyway I can work it around by not resetting initialIndex [12:02] that way currentIndex does 5->0->5 as it is assigned on both onCountChanged [12:03] it seems after the first countChange something causes it to be reset to 0 (but not after the second) === dandrader is now known as dandrader|afk === marcusto_ is now known as marcustomlinson_ === dandrader|afk is now known as dandrader [14:11] mterry, ping [14:11] om26er, hi [14:11] mterry, got you a present :-) (bug 1436349) [14:11] bug 1436349 in unity8 (Ubuntu) "welcome wizard re-appears" [High,New] https://launchpad.net/bugs/1436349 [14:11] om26er, oh... you shouldn't have [14:12] mterry, I remember I showed you the video a few days ago, today I have exact steps. [14:12] om26er, ok, will look at it today. Thanks! [14:13] mterry, also another issue I saw was my Welcome wizard hanged at language selection screen. The 'next' button was partially greyed out, what could cause that ? [14:15] om26er, on the language selection? hmm... maybe if the shell (which is starting a PAM login for the user in the background) never heard back from PAM? But that would be unlikely [14:17] mterry, it never enabled the 'continue' icon, [14:18] om26er, right -- when the shell is logging in PAM, it disables everything as a security measure (it's not really thinking about wizard use case when it does this though). But if it got somehow stuck in that mode... [14:23] mzanetti: easy one for you https://code.launchpad.net/~aacid/unity8/autopilot3/+merge/254094 [14:53] Mirv: for those autopilot tests, are you using mako or krillin? [14:58] Mirv: and how much until a faiulre? it's been running for a long while here without failures [14:58] ha i think it just failed :D [14:58] that's timing [15:46] om26er, are you seeing that bug in rtm or vivid? [15:47] mterry, vivid [15:47] (the welcome wizard reappears) [15:47] ok [16:23] Mirv: please try https://code.launchpad.net/~aacid/autopilot/dbus_search_no_seen_connections/+merge/254109 === dandrader is now known as dandrader|afk === alan_g is now known as alan_g|EOD [19:16] Is there a fix for unity lockup when dragging app windows between work spaces? [19:19] Is there a fix for unity lockup when dragging app windows between work spaces? [19:20] guess everyone is out to lunch [20:59] om26er, so I reproduced your bug btw, but I see the edge tutorial on top of the dialer. And when I finish the tutorial, I don't see the wizard again [20:59] mterry, that;s strange, I'll record a video [21:00] om26er, I mean, there's definitely a bug in what I see -- edge tutorial should be stopped as well as the wizard [21:00] But it's a different bug [21:00] mterry, right, but for me the edge gesture hints start again and again [21:01] om26er, ah not the wizard? Just the tutorial? [21:01] OK, I thought you were saying wizard starts [21:01] mterry, yes, the tutorial [21:01] mterry, I always mix those two [21:01] om26er, (yeah understandable -- they appear to be one and the same sort of. But very different pieces of code underneath) [21:11] mterry, check email for video. [21:11] om26er, thanks! [21:13] om26er, ah... I wasn't swiping from left again to restart it