[05:47] <Mirv> bregma: regarding the unity7 AP tests, just another reference point from two successive test runs, the '+':s of which prevented the automatic release this time http://pastebin.ubuntu.com/5979939/
[05:48] <Mirv> in case there'd be something that could be made more solidly succeeding
[08:03] <sil2100> jamesh: hi!
[08:03] <sil2100> jamesh: did you get my e-mail?
[08:03] <jamesh> sil2100: hi.  I saw your comment on the MP.  Was there some other email?
[08:04] <jamesh> Thanks for your work on lucene++ though: we're deciding what to do about the test failures now
[08:05] <jamesh> Looks like we'll disable them for now, since they appear to be broken in trunk too and pass locally
[08:08] <sil2100> jamesh: sounds good for me! NP, and once this gets in let's deal with releasing media-scanner to the world
[08:08] <jamesh> sil2100: yep.
[08:12] <Cimi> Saviq, ping
[08:12] <Saviq> Cimi, pong
[08:13] <Cimi> Saviq, ciao
[08:13] <Cimi> Saviq, so can you test the last rev with autopilot?
[08:13] <Saviq> Cimi, sure, will do
[08:14] <Saviq> Cimi, and well, CI can, too ;)
[08:14] <Cimi> there's just one minor thing I belive
[08:14] <Cimi> background property of root, not sure it will have to be an alias or not
[08:15] <Cimi> readonly alias might be good
[08:21] <mzanetti> Cimi: just ran the autopilot tests with the background branch... all passed
[08:21] <Cimi> mzanetti, and you confirm is failing without?
[08:21] <Cimi> mzanetti, a previous rev...
[08:21] <mzanetti> Cimi: no... I never saw it failing
[08:22] <mzanetti> Cimi: ah... hmm... there is one thing:
[08:22] <mzanetti> Cimi: if there is no image set because of a wrong url. then the greeter has some weird behavior. i.e. it doesn't fully slide away etc
[08:23] <mzanetti> Cimi: I could see how that might has broken the tests in environments where no background is set
[08:23] <Cimi> mzanetti, rev 167 should fail
[08:23] <Cimi> mzanetti, mmm the branch is supposed to fix those
[08:24] <Cimi> mzanetti, it should revert to default bg in case
[08:24] <mzanetti> Cimi: yep... let me just try without my fix if I can reproduce the issue
[08:24] <Saviq> mzanetti, set your background to an invalid one
[08:24] <Saviq> mzanetti, or to an empty string
[08:24] <Saviq> mzanetti, that's when they failed
[08:24] <Saviq> mzanetti, 'cause greeter was never "ready"
[08:24] <mzanetti> Saviq: yeah... I've fixed that one now... but let me verify
[08:28] <Cimi> mzanetti, thought was fixed in the branch...
[08:28] <mzanetti> Cimi: Saviq: yep. confirmed. with an empty background it failed with revision 174, but works with 175
[08:28] <mzanetti> of this branch lp:~unity-team/unity/background-ugly
[08:29] <Saviq> mzanetti, k cool
[08:29] <Cimi> I'll clean up and push to unity8 :P
[08:29] <mzanetti> :D
[08:41] <dednick> larsu: good morning!
[08:42] <larsu> dednick: morning :)
[08:42] <dednick> larsu: would you mind taking a look? https://code.launchpad.net/~nick-dedekind/qmenumodel/remove.unitymenuaction/+merge/179800
[08:42] <dednick> larsu: we're leaking :(
[08:43] <dednick> larsu: had to remove UnityMenuAction
[08:44] <larsu> dednick: hm, activate() does magic now...
[08:44] <larsu> dednick: fine by me if it's fine by you
[08:45] <larsu> and I guess it is, since you wrote it :)
[08:46] <tsdgeos> dednick: when using https://code.launchpad.net/~nick-dedekind/unity8/indicator.positions/+merge/179505 clock is not on the right anymore, is this ok?
[08:47] <dednick> larsu: well, i wasnt really sure about the activate. could do activateWithData if you prefer
[08:47] <dednick> but then magic will just be shifted to unity8
[08:47] <dednick> tsdgeos: er. let me check that out. doesnt sound right
[08:48] <tsdgeos> dednick: on the device, on the pc is on the right
[08:48] <dednick> tsdgeos: pc?
[08:49] <tsdgeos> dednick: Personal computer, laptop
[08:49] <dednick> tsdgeos: hm. i havent seen that. what indicator is that?
[08:49] <tsdgeos> :D
[08:49] <tsdgeos> ok
[08:49] <tsdgeos> let me start again
[08:50] <larsu> dednick: fair enough. I'm approving.
[08:50] <tsdgeos> dednick: if i run unity8 on my laptop, the clock is correctly on the right, but if run unity8 on the phone it is not on the right
[08:50] <tsdgeos> dednick: clearer now?
[08:50] <dednick> tsdgeos: ahha. yes
[08:51] <Saviq> tsdgeos, pushed fixes to app-preview-data
[08:51] <tsdgeos> oka
[08:51] <Saviq> tsdgeos, will talk with the online guys later to see if it should work already
[08:51] <Saviq> tsdgeos, so don't top-approve yet
[08:51] <dednick> tsdgeos: it's possibly because the files are still being read from install folder. let me check it out
[08:51] <Saviq> tsdgeos, thanks
[08:54] <Saviq> dednick, looking at lp:~nick-dedekind/unity8/indicators-behaviour.tabs - MainView is kinda scary to use there, it's meant to *be* the main view...
[08:55] <sil2100> Trevinho, andyrock, bregma: ping
[08:55] <andyrock> sil2100, pong
[08:55] <dednick> Saviq: indeed it is scary. unfortunately it's the only thing that tabs work on at the moment. I spoke to SDK, but it's not really on their priority list.
[08:55] <Saviq> dednick, mhm :/
[08:55] <andyrock> sil2100, what's up?
[08:55] <sil2100> andyrock: hi! Poor you! You always respond to my pings ;) And you know what my pings are usually about!
[08:55] <sil2100> andyrock: failing AP tests, oh noes!
[08:56] <tsdgeos> Saviq: dednick: yeah i remember looking at that and then running away :D
[08:56] <tsdgeos> Saviq: dednick: also i guess you have that "let's override this internal property" for that reason, right?
[08:56] <dednick> Saviq: PageStacks are the same. i have no idea why they seem relucant to do something about it.
[08:56] <dednick> tsdgeos: yep
[08:56] <Saviq> dednick, mhm
[08:56] <andyrock> sil2100,  :D do you have a list of need-fixing tests right?
[08:57] <sil2100> andyrock: so, I actually have two lists, let me bring those in
[08:57] <dednick> tabs seem like a fairly normal thing to have in a view...
[08:58] <tsdgeos> +1
[08:59] <dednick> larsu: any idea why the version format of qmenumodel has suddenly changed?
[09:01] <larsu> dednick: no. Do you mean the version of the package?
[09:01] <tsdgeos> dednick: wait, i may not be running the correct code on the phone
[09:02] <dednick> larsu: yeah, it was 0.2.6daily13.06.07-0ubuntu1  , now  0.2.6+13.10.20130812-0ubuntu1
[09:02] <larsu> dednick: no clue - maybe they changed the format of the daily builds and qmenumodel didn't have a release in a while...
[09:03] <dednick> larsu: yeah, i guess so
[09:04] <dednick> larsu: i think we should bump it up to 0.2.7
[09:05] <larsu> dednick: sure, feel free to do so (I'm a bit preoccupied with i-messages right now -- I'll by on vacation from tomorrow)
[09:05] <dednick> larsu: ok :) i'll stop bugging you in that cas
[09:06] <larsu> dednick: heh, didn't mean it like that. Just wanted to let you know I don't have time for changing the version ;)
[09:06] <dednick> larsu: sure. i meant it in hurry up and finish messaging ;)
[09:06] <larsu> ha :)
[09:09] <dednick> Saviq: how do you actually go about bumping package version up? is all you need to to is add new section to debian/changelog?
[09:09] <Saviq> dednick, yes
[09:09] <Saviq> dednick, just add a *released* version entry
[09:09] <Saviq> dednick, just the upstream version (i.e. 7.83.1 in the case of unity8)
[09:10] <Saviq> dednick, daily release takes care of the rest
[09:10] <dednick> Saviq: ok, thanks
[09:10] <didrocks> we do all the heavy work ;)
[09:11] <didrocks> prefer still -0ubuntu1 though if you want to easily rebuild locally the package
[09:11] <didrocks> (but that's just for your own ease)
[09:17] <tsdgeos> Saviq: what's your opinion on https://code.launchpad.net/~aacid/unity8/less_repeated_stuff_cmake/+merge/179875 ?
[09:17] <tsdgeos> ok or ko?
[09:17] <dednick> quite interesting that unity8 is version 7... ;)
[09:18] <mzanetti> dednick: I think its common to have 7.80 for 8-alpha, 7.90 for 8-beta etc
[09:18] <dednick> mzanetti: ahh i see. like v0.X
[09:18] <Saviq> dednick, yup
[09:19] <Saviq> tsdgeos, I'm torn, on the one hand I agree it's spurious, on the other I like the plugins self-contained, so that you can effectively take 'em out and the build should work ~without intervention
[09:20] <Saviq> tsdgeos, but it's not really the case anyway, probably
[09:20] <tsdgeos> Saviq: probably you'd need stuff from the toplevel cmakelists too
[09:20] <tsdgeos> as the project() call and whatnot
[09:21] <Saviq> tsdgeos, yeah, exactly
[09:21] <Saviq> tsdgeos, so yeah - ok
[09:21] <tsdgeos> okidoki
[09:23]  * mzanetti agrees
[09:24] <dednick> Saviq: this right? https://code.launchpad.net/~nick-dedekind/qmenumodel/bump-0.2.7/+merge/179879
[09:24] <Saviq> dednick, +1, maybe a slightly more descriptive changelog entry would be useful, though
[09:24] <dednick> :) yeah, i was just thinking that
[09:25] <Saviq> dednick, commented on lp:~nick-dedekind/unity8/indicators-behaviour.tabs
[09:26]  * mzanetti loves this ^^
[09:26] <Saviq> mzanetti, +1
[09:27] <mzanetti> looks like a simple change (design-wise) but improves usability in so many ways
[09:27] <Saviq> mzanetti, we're actually supposed to get the same for the dash
[09:27] <Saviq> mzanetti, to replace the bottom bar
[09:28] <mzanetti> hmm... not sure how that will look. but lets see.
[09:29] <dednick> Saviq: thanks
[09:30] <Saviq> mzanetti, like the video you're getting in your email, more or less
[09:30] <Saviq> tsdgeos, you got it, too, but don't worry about it for now
[09:30] <Saviq> mzanetti, tsdgeos, dednick you might be interested in the fallout from IoM, though
[09:30] <Saviq> https://docs.google.com/a/canonical.com/document/d/1ypEDFzqRcYXKNcEVzAEG5KgdCWfgwiUHlmP5NledYzo/edit
[09:31] <Saviq> not huge, but good to keep in mind
[09:31] <dednick> i dont like the sound of "fallout"
[09:31] <mzanetti> hehe
[09:31] <Cimi> mzanetti, I think background property should be readonly alias of backgroundImage.source
[09:32] <mzanetti> Cimi: we write it in line 448
[09:32] <dednick> is a self approval of a version bump ok? :)
[09:33] <Saviq> dednick, approved
[09:33] <Cimi> mzanetti, that's bad
[09:33] <dednick> Saviq: thanks
[09:33] <mzanetti> Cimi: I don't see why
[09:33] <Cimi> mzanetti, because it's not in sync with the shell
[09:33] <Saviq> dednick, btw, it might make sense next time to explain why the release is needed (if there is such a reason ;))
[09:33] <Cimi> mzanetti, so my branch breaks it
[09:33] <Cimi> mzanetti, I am using source independently
[09:33] <Cimi> source of crossfadeimage btw
[09:34] <mzanetti> Cimi: have to go to a meeting now. I'll ping you in 20 mins for this
[09:34] <dednick> Saviq: "I like to give myself work"
[09:35] <dednick> and annoy people with useless MPs
[09:35] <Saviq> dednick, ;)
[09:35] <Cimi> mzanetti, what's background property?
[09:35] <Cimi> who needs it?
[09:38] <dednick> how many edges do we have on this phone? i could swear we only have 4 to play with...
[09:38] <Saviq> rotfl
[09:38] <Saviq> dednick, it's *the* edge
[09:38] <mzanetti> :D
[09:38] <Saviq> there can be only one
[09:38] <Saviq> dednick, but there's 4 on the back, too!
[09:39] <mzanetti> there's at least 2 on the left side :D
[09:39] <Saviq> dednick, and with the Edge's design, there's like 24 total!
[09:39] <dednick> we going to have underhand touch detect? stroke with right index finger opens the calculator.
[10:14] <Cimi> mzanetti, you back
[10:14] <Cimi> mzanetti, I think it's used by the lockscreen
[10:14] <mzanetti> Cimi: yes, now I am
[10:14] <Cimi> mzanetti, the real shell background don't need it
[10:14] <mzanetti> Cimi: what exactly is the issue?
[10:15] <Cimi> mzanetti, I was wondering if we could have dropped the background property of shekk
[10:15] <Cimi> shell
[10:16] <mzanetti> Cimi: right... there seems to be some issue indeed
[10:17]  * Saviq biab
[10:17] <mzanetti> Cimi: I'd vote for making it an alias
[10:17] <Cimi> mzanetti, why does the greeter change the property?
[10:17] <Cimi> mzanetti, I believe only for the lockscreen
[10:17] <mzanetti> Cimi: the background changes if you select another user
[10:17] <Cimi> actually I don't know what we should do for multi user
[10:18] <Cimi> mzanetti, but what happens when it loads gsettings?
[10:18] <Cimi> it shouldn't change the bg of the shell
[10:18] <Cimi> I'm confused
[10:18] <Cimi> do you have a tablet to test?
[10:18] <mzanetti> Cimi: you can test on the desktop
[10:18] <Cimi> ok
[10:19] <Cimi> but how about multiple users with multiple gsettings?
[10:19] <mzanetti> Cimi: good question :/
[10:19] <seb128> the greeter background is stored in accountsservice, not gsettings
[10:19] <seb128> well accountsservice has a list of users with properties
[10:19] <seb128> keyboard layout, background image
[10:19] <mzanetti> Cimi:  I think this issue will go away once the greeter is split out of the shell
[10:19] <seb128> the greeter read it from there
[10:19] <seb128> the desktop greeter
[10:20] <mzanetti> Cimi: as the greeter just updates its own image with the stuff from accountservice as seb128 said.
[10:20] <seb128> that's the plan for the new greeter as well afaik
[10:20] <mzanetti> Cimi: and once you log in, the shell can load the background from gsetting and that won't change through the greeter any more
[10:22] <mzanetti> Cimi: so I think we can just drop line 446-449
[10:23] <sil2100> andyrock: btw! I looked at raring right now, and I see you made a fix to compiz that disables the default show desktop shortcut
[10:33] <Cimi> mzanetti, but that way it won't change when you change user?
[10:35] <sil2100> andyrock: I'm not entirely sure this is SRUable though
[10:36] <sil2100> andyrock: I know that the shortcut works only for the first time, but still it would probably be best to simply fix showdesktop
[10:36] <mzanetti> Cimi: yes, because in a real multi user environment, ever user runs his own instance of the shell
[10:36] <sil2100> andyrock: or is it broken fundamentally beyond fixing ;) ?
[10:37] <Cimi> mzanetti, so when you change user it changes gsettings?
[10:37] <mzanetti> Cimi: no... ever user runs his own instance of the shell
[10:37] <mzanetti> so if you change user, a second shell will be launched
[10:37] <Cimi> mzanetti, I mean in the greeter
[10:38] <Cimi> mzanetti, how can the greeter change bg when you scroll users?
[10:38] <mzanetti> Cimi: no... the greeter just reads the stuff from logind or whatever which in turn reads if from the gsettings for the selected user
[10:39] <mzanetti> Cimi: then when you log in with a user, a new shell gets started which just reads the setting from gsettings.
[10:39] <mzanetti> Cimi: makes sense?
[10:40] <Cimi> mzanetti, the lock screen seems to read shell.background
[10:40] <mzanetti> Cimi: yeah, that's fine...
[10:40] <Cimi> lockscreen != greeter?
[10:40] <mzanetti> Cimi: yep
[10:40] <Cimi> ah ok
[10:40] <mzanetti> Cimi: the lockscreen's background will go away eventually once we can do blur
[10:42] <Cimi> mzanetti, ok pushed
[10:42] <mzanetti> to unity8? :P
[10:42] <Cimi> https://code.launchpad.net/~unity-team/unity8/unity8.background-gsettings-fix/+merge/179884
[10:45] <mzanetti> small comment added
[10:47] <sil2100> jamesh: hm, we probably need to create a project for media-scanner, right?
[10:47] <sil2100> jamesh: since I doubt hollywood is the right name
[10:53] <Cimi> mzanetti, done
[10:53] <Cimi> mzanetti, I merged the two tests
[10:54] <mzanetti> Cimi: good
[10:54] <Cimi> mzanetti, nope
[10:54] <mzanetti> ?
[10:54] <Cimi> mzanetti, wrong code hold on :)
[10:54] <mzanetti> right :)
[10:55] <Cimi> mzanetti, ok now done
[10:55] <Cimi> mzanetti, had to check for expectedUrl not just url
[10:55] <mzanetti> Cimi: ok. giving it a last spin before approving. code looks good
[10:56] <mzanetti> Cimi: one note: In general its more safe to use removeAll() instead of removeOne() in such unregisterObject() methods
[10:56] <mzanetti> Cimi: won't do any harm here, but if that api is used by someone else you get nasty effects if someone calls register() twice and unregister() only once
[10:56] <Cimi> ok
[10:56] <Cimi> good to know
[10:57] <mzanetti> Cimi: removeAll() might be a bit slower tho... of in case you're doing performance critical stuff its again a tradeoff
[11:00] <andyrock> sil2100, sorry was afk
[11:00] <andyrock> let me check
[11:01] <andyrock> sil2100, i proposed a fix for 0.9.9
[11:01] <andyrock> sil2100, because 0.9.9 is still saucy ;)
[11:02] <sil2100> hmmm
[11:02] <Cimi> Saviq, https://code.launchpad.net/ubuntu-settings-components has packaginf
[11:02] <Saviq> Cimi, k
[11:03] <sil2100> andyrock: sadly, 0.9.9 is for raring ;)
[11:03] <sil2100> andyrock: target_branch: lp:compiz/0.9.9
[11:03] <mzanetti> tsdgeos: any news on the ListView positioning with snapping in the center?
[11:03] <andyrock> sil2100, but it's saucy too right?
[11:04] <sil2100> andyrock: well... for saucy we're using no branch right now, maybe it was based on 0.9.9 but we're not doing any releases
[11:04] <andyrock> *for saucy
[11:04] <tsdgeos> mzanetti: ah no, didn't do anything, i was about to start wokring on it last week but then i realized i wasn't sure what would be "good enough" for us
[11:04] <sil2100> andyrock: we'll be using 0.9.10 for saucy
[11:04] <sil2100> andyrock: so every commit now that goes into 0.9.9 is for raring only
[11:04] <mzanetti> tsdgeos: do you need anything from me in that regard?
[11:04] <sil2100> andyrock: since that's the branch that's targetted for daily release for raring ;)
[11:04] <andyrock> sil2100, cool... so just revert that rev
[11:04] <sil2100> andyrock: sooo, I think we need to consult this with the SRU guys if it's ok or not
[11:05] <tsdgeos> mzanetti: i think i do, that's why i stopped, but don't remember now, i'll try to have a second look again today and ask you something if needed
[11:05] <andyrock> in that case I need to propose a branch for unity 7.0 too
[11:05] <andyrock> unity raring branch
[11:05] <mzanetti> tsdgeos: thanks
[11:08] <andyrock> sil2100, in that case we should backport http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3443
[11:09] <andyrock> we are not disabling the show_desktop
[11:09] <andyrock> we just moved the option
[11:09] <Cimi> Saviq, can we chat on the backend for welcome wizard?
[11:09] <andyrock> sil2100, we have good reasons :D
[11:09] <sil2100> andyrock: ah, so we moved it out of compiz to unity?
[11:09] <Saviq> Cimi, sure, should have seb with us, though, and he doesn't seem around
[11:10] <Cimi> lunch time in france
[11:10] <sil2100> andyrock: if so, it would be nice to have the disable-shortcut-for-compiz and unity-add-showdesktop-to-unity in raring ;)
[11:10] <Saviq> Cimi, probably, can you throw something in our calendars?
[11:10] <andyrock> sil2100, do you want me to propose a branch for unity 7.0?
[11:10] <Cimi> Saviq, ok
[11:10] <sil2100> andyrock: would be awesome
[11:10] <andyrock> sil2100, can I do it after lunch?
[11:11] <sil2100> andyrock: of course! I'll be going out for lunch pretty soon as well
[11:13] <tsdgeos> Saviq: greyback: i am going to put some time on the category expansion animation, am i right that we agreed that we'd only animate the delegate height when no contentY position was needed?
[11:23] <greyback> tsdgeos: just thinking out loud: if the bottom of the contracted category is off-screen, there's no need to animate the height, just expand it immediately and animate contentY (if needed).
[11:24] <greyback> tsdgeos: if bottom of contacted category on screen, I think animating both height & contentY would be visually ok.
[11:25] <greyback> you see something similar on iOS, when viewing a folder of apps.
[11:26] <Saviq> greyback, I think it's more or less simple: if you can see the animation - animate, otherwise - don't
[11:26] <Saviq> tsdgeos, ↑ rather
[11:26] <tsdgeos> :D
[11:26] <tsdgeos> ok
[11:43] <mzanetti> Cimi: there is still another issue :/
[11:44] <mzanetti> Cimi: dunno why, but if the gSetting has an invalid picture url at startup the background doesn't work :/
[11:44] <mzanetti> Cimi: weird thing is, the Greeter works, it's just the background that doesn't
[11:44] <mzanetti> Cimi: I gave up now and added the dummy picture back to determine if the url is valid or not
[11:51] <didrocks> Saviq: one flacky test: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/960/
[11:52] <Saviq> didrocks, yeah, we saw that before, need to add some debugging there
[11:52] <didrocks> Saviq: we'll maybe wait for next daily run then
[11:53] <didrocks> (2h from now)
[11:53] <Saviq> didrocks, it's just typing "password\n", no idea how it fails :/
[11:53] <didrocks> Saviq: the video doesn't help?
[11:53] <didrocks> don't you think it's just timing out?
[11:53] <Saviq> didrocks, yeah it does - it shows that the password was wrong
[11:53] <Saviq> didrocks, which is *weird*
[11:53] <didrocks> interesting
[11:53] <Saviq> didrocks, that's why I'm saying we need more debugging in there
[11:54] <Saviq> didrocks, but obviously it'll just work on the next run
[11:54] <didrocks> ok, let's wait for now
[11:56] <didrocks> sil2100: FYI ^
[12:16] <sil2100> Looking!
[12:19] <andyrock> sil2100, didrocks in autopilot-saucy-daily_release job 956 bamfdaemon crashed (that's why all those failures)
[12:20] <andyrock> do you know how can I get the .crash file?
[12:20] <andyrock> should be easy to debug the issue
[12:20] <andyrock> and fix it
[12:27] <didrocks> andyrock: I don't find it, but you think that we everytime have high level of failures because of bamf?
[12:27] <Saviq> didrocks, sil2100 https://code.launchpad.net/~saviq/unity8/autopilot-debug-passphrase-entry/+merge/179915
[12:27] <didrocks> (for the previous runs)
[12:27] <didrocks> andyrock: I would then look at https://errors.ubuntu.com/?release=Ubuntu%2013.10&package=bamf&period=month
[12:27] <didrocks> seems there is a popular crash
[12:27] <didrocks> Saviq: are .debug() showed by the default level execution during AP?
[12:28] <Saviq> didrocks, are you not running with -v ?
[12:28] <didrocks> Saviq: it's not me, it's autopilot
[12:28] <didrocks> so not sure how it's running you :)
[12:28] <Saviq> didrocks, are you not running autopilot with -v?
[12:28] <didrocks> we do
[12:28] <Saviq> didrocks, then that's it - it's autopilot debugging
[12:29] <Saviq> didrocks, not "our" debugging
[12:29] <didrocks> Saviq: sorry, I read too quickly, I thought the process part was in unity8
[12:29] <didrocks> ok, approving then
[12:29] <Saviq> didrocks, I expect that enter is pressed (and authentication requested) before the key was processed properly
[12:29] <Saviq> didrocks, so a simple Eventually(Equals()) should fix that
[12:30] <Saviq> didrocks, but let's see what (if anything) we get from the debug logging
[12:30] <didrocks> Saviq: probably yeah
[12:30] <didrocks> right
[12:33] <sil2100> didrocks: still, a pretty nice outcome - just one red light ;p
[12:34] <didrocks> right ;)
[12:34]  * didrocks stare at Saviq!
[12:34] <didrocks> almost 2 runs green in a row
[12:34]  * Saviq hides
[12:34] <didrocks> :)
[13:04] <Saviq> tsdgeos, ok, the app preview seems to be fine, it's the backends that are still not up to par
[13:04] <Saviq> tsdgeos, I think we can land it
[13:06] <Saviq> tsdgeos, it will at least make  the guys fix it then :)
[13:06] <jamesh> sil2100: hi.  About the name for the mediascanner, currently the "hollywood" name is exposed in the name of the grilo plugin
[13:07] <jamesh> sil2100: the packaging in the branch uses ubuntutv-mediascanner for the source package name, and just "mediascanner" in the binary package names
[13:07] <tsdgeos> Saviq: ok for me
[13:07]  * tsdgeos approves
[13:14] <Cimi> mzanetti, I just read the MR
[13:16] <mzanetti> Cimi: ok... what do you think?
[13:16] <mzanetti> Cimi: I kinda hate the fact that we need that dummy Image...
[13:17] <mzanetti> Cimi: but I've found another issue and spend quite a lot of time trying to fix it... haven't been able to do so without the dummy image
[13:18] <Cimi> mzanetti, first of all, why not gsettingscontroller?
[13:18] <mzanetti> ?
[13:18] <mzanetti> Cimi: ah, you mean the failed test?
[13:18] <Cimi> the one you put the log
[13:19] <mzanetti> Cimi: didn't investigate why it happens, but tests fail if I run them locally
[13:19] <mzanetti> Cimi: most likely the mock plugin isn't installed, or it is installed, but the real one has preference or something like this
[13:19] <Cimi> mzanetti, you might need the import?
[13:20] <mzanetti> Cimi: does it work for you if you do this:
[13:20] <mzanetti> cd builddir && make testShell
[13:20] <mzanetti> ?
[13:20] <Cimi> yes
[13:20] <Cimi> let me branch again
[13:20] <mzanetti> I get this error in that case
[13:26] <Cimi> mzanetti, might be wrong import sequence
[13:26] <Cimi> order
[13:27] <Cimi> still compiling though
[13:27] <Cimi> mzanetti, works here on a branch new branch
[13:28] <Cimi> *brand new
[13:32] <Saviq> Cimi, mzanetti, tsdgeos, dednick_, nic-doffay standu
[13:32] <Saviq> p
[13:33] <Cimi> Saviq, mistake, I thought today was wednesday :P
[13:33] <tsdgeos> i was there
[13:33] <tsdgeos> what happend?
[13:33] <Cimi> Saviq, can we have today the meeting for the backend?
[13:33] <Saviq> Cimi, sure, it's you who put it in for tomorrow :)
[13:33] <Cimi> Saviq, lol saw the wrong day :)
[13:38] <Cimi> someone knows where web is?
[13:38] <Cimi> seb
[13:41] <didrocks> Cimi: travelling to Berlin
[13:41] <didrocks> he will be back on IRC in ~1h I guess
[13:41] <Cimi> didrocks, ah ok… you know when will he be online/available?
[13:42] <Cimi> didrocks, and working?
[13:42] <didrocks> yeah
[13:42] <Cimi> didrocks, or holiday?
[13:42] <Cimi> ok
[13:42] <didrocks> if seb is on IRC, he's working ;)
[13:42] <Cimi> Saviq, let's move the meeting later then ^
[13:50] <dednick_> eh. sorry.
[13:50] <Cimi> didrocks, pretty much like sms pillaz
[13:50] <Cimi> hah
[14:12] <mzanetti> Cimi: I fixed the comment
[14:13] <mzanetti> Cimi: where is the whitespace issue? the whitespace test passes here
[14:18] <Cimi> mzanetti, new line
[14:19] <Cimi> mzanetti, empty line in gsettings
[14:20] <mzanetti> Cimi: ok. fixed... I've no clue why the tests don't pass here...
[14:20] <Cimi> who can test?
[14:20] <mzanetti> tsdgeos: can you?
[14:21] <tsdgeos> mzanetti: what?
[14:21] <mzanetti> https://code.launchpad.net/~unity-team/unity8/unity8.background-gsettings-fix/+merge/179884
[14:21] <mzanetti> tsdgeos: does "make testShell" work for you?
[14:21] <tsdgeos> in general or with that branch?
[14:21] <mzanetti> this branch
[14:22]  * tsdgeos tests
[14:23] <sil2100> jamesh: ping
[14:24] <jamesh> sil2100: pong
[14:24] <sil2100> jamesh: quick question - media-scanner will be named media-scanner, right? Not hollywood?
[14:25] <sil2100> jamesh: since I saw unity-scope-hollywood
[14:26] <sil2100> jamesh: also, do we intend to daily-release hollywood/media-scanner ?
[14:27] <tsdgeos> mzanetti: fails
[14:27] <tsdgeos> FAIL!  : qmltestrunner::Shell::test_wallpaper(red) Uncaught exception: GSettingsController is not defined
[14:27] <jamesh> sil2100: I don't really know about the naming.  The "hollywood" naming is exposed in the Grilo plugin name, which does make up part of the public API
[14:27] <jamesh> sil2100: all the packaging currently says mediascanner though
[14:27] <jamesh> daily builds seem like a good idea
[14:28] <Cimi> dammit why works here?
[14:28] <jamesh> I haven't asked anyone to set them up yet
[14:28] <Cimi> tsdgeos, mzanetti works here :-\
[14:30] <mzanetti> Cimi: did you install the mocked GSettings plugin system wide ?
[14:30] <Cimi> mzanetti, mmm nope
[14:31] <mzanetti> tsdgeos: it is indeed a bit weird that it passes in jenkins too
[14:32] <sil2100> jamesh: I can do that, but would have to do a packaging review - and the name thing would have to be resolved, so that we can have a public LP project page available (we need that for releasing the package to universe as well)
[14:34] <jamesh> sil2100: if we want to get rid of the "hollywood" name, we can certainly rename the LP project.
[14:34] <tsdgeos> mzanetti: ^_^
[14:35] <jamesh> sil2100: renaming the plugin would also require small changes to related software.  For example, I needed to reference the plugin name in the media scanner scope: http://bazaar.launchpad.net/~unity-team/unity-scope-hollywood/trunk/view/head:/src/main.c#L16
[14:38] <mzanetti> Cimi: it works if I uninstall qtdeclarative5-gsettings1.0
[14:39] <mzanetti> Cimi: which means that one has higher preference over the mocked one
[14:39] <mzanetti> anyways, I need to leave now. will be back later
[14:42] <Cimi> mzanetti, ok failing for me now
[14:45] <jamesh> sil2100: I was just talking to thostr_, and he seems happy to switch away from the hollywood name.  If "mediascanner" is too generic, ubuntu-mediascanner or unity-mediascanner might be appropriate
[14:46] <sil2100> jamesh: ok, one of the *-mediascanner ones would be nice, let me see what's the more appropriate convention
[14:46] <sil2100> Saviq: unity8 check went fine this time
[14:46] <Saviq> sil2100, yeah, expected
[14:47] <Saviq> sil2100, next time it fails we'll have some debug output
[14:47] <Saviq> sil2100, or! the debug logging itself might create enough delay that we'll not encounter that issue again ;d
[14:47] <sil2100> didrocks: Apps stack is still running, but so far all is green again :O Shocking, I think something's broken
[14:47] <didrocks> I have hope in Saviq :)
[14:47] <sil2100> Saviq: heh ;)
[14:57] <Cimi> mzanetti, tsdgeos how weird!
[14:57] <Cimi> mzanetti, tsdgeos I realised the difference now from before is that I did dist-upgrade
[14:57] <tsdgeos> greyback: Saviq: i added animations to the dash category expansion, can you have a look and see how it feels for you?
[14:57] <Saviq> tsdgeos, awesome, thanks
[14:57] <Cimi> even my old branch doesn't work with the test anymore
[14:58] <greyback> tsdgeos: ok.
[14:59] <tsdgeos> Cimi: weird
[15:00] <tsdgeos> Cimi: is qtdeclarative5-gsettings1.0 interferring with you?
[15:01] <tsdgeos> should the mock "win" over that?
[15:01] <Cimi> tsdgeos, it should
[15:01] <Cimi> it was before
[15:03] <tsdgeos> Cimi: well, it's not
[15:03] <tsdgeos> if i uninstall the package the test passes
[15:04] <Cimi> tsdgeos, clearly it isn't
[15:04] <Cimi> tsdgeos, GSettingsCOntroller is only defined in the mock
[15:05] <tsdgeos> so if the real one is loaded
[15:05] <tsdgeos> you don't get GSettingsCOntroller
[15:07] <Cimi> tsdgeos, yes, because it doesn't win
[15:07] <Cimi> tsdgeos, but why?
[15:08] <greyback> tsdgeos: that's a big improvement IMO, I now follow what's happening much better. The animations are 2-stage, though: first height, then contentY. Is simultaneous possible, to see how it looks?
[15:09] <tsdgeos> greyback: simultaneous is a bit harder
[15:09] <tsdgeos> since i need to "lie" to LVWPH about how much the item is in height
[15:09] <tsdgeos> so when calling maximizeVisibleArea it has the final height and not the currently animated one
[15:10] <tsdgeos> Cimi: because the plugin loader prefers the versioned folders it seems
[15:10] <tsdgeos> doing
[15:10] <tsdgeos> mv tests/mocks/GSettings/ tests/mocks/GSettings.1.0/
[15:10] <tsdgeos> in the builddir makes the test pass again
[15:10] <tsdgeos> Cimi: mzanetti: ↑↑↑
[15:10] <greyback> tsdgeos: I see the dilemma. If that's a lot of work, I think this is good enough
[15:10] <tsdgeos> greyback: let me see if i can pull it off before eod
[15:11] <greyback> tsdgeos: you have 49 minutes, do it! :D
[15:20] <Cimi> tsdgeos, it's weird
[15:20] <Cimi> tsdgeos, will we have to change this everywhere?
[15:20] <tsdgeos> Cimi: everywhere where the "real" one uses versioned folders i guess
[15:21] <Cimi> ok
[15:21] <tsdgeos> greyback: seems the lying was easier than i thought
[15:21]  * tsdgeos hates how lieing is lying
[15:22] <tsdgeos> greyback: pushed, can you give a try, i think it looks better this way
[15:22] <greyback> tsdgeos: cool, trying
[15:22] <Cimi> tsdgeos, ok thx, fixed and pushed
[15:25] <tsdgeos> greyback: the "catch" is that it works cool becuse both animations happen to be 200ms
[15:25] <tsdgeos> but they are not necessarily linked
[15:25] <greyback> tsdgeos: understood. I agree it looks better too
[15:26] <greyback> tho sometimes I think 200ms is too much
[15:26] <greyback> too little
[15:26] <greyback> I mean
[15:26] <tsdgeos> :D
[15:26] <tsdgeos> E_NO_UNDERSTAND_GERRY
[15:26] <tsdgeos> greyback: you mean things move too fast?
[15:27] <greyback> tsdgeos: sometimes yes, I loose track of what's going on
[15:28] <greyback> but I think it's more due to the lack of visual differentiation between the section headers and the content. They have the same background, which I don't like so much
[15:28] <greyback> but that's just me
[15:28] <sil2100> jhodapp: ping
[15:29] <tsdgeos> greyback: ok, so what's next?
[15:30] <greyback> tsdgeos: do we have a designer to give it the ok? If not, I guess it's good enough to land anyway, in which case I'll review
[15:30] <sil2100> jhodapp: unping
[15:30] <jhodapp> lol
[15:31] <tsdgeos> greyback: tbh i'd prefer we land it, it gets to designer hands and if they don't like it they can complain and not stall on them. It does what Oren wants in the big picture, if they don't like the animations we can fine tune them later since now we know it's not hard to switch from simultaneous to sequential
[15:32] <tsdgeos> Cimi: sure you pushed? still can see nothing at https://code.launchpad.net/~unity-team/unity8/unity8.background-gsettings-fix/+merge/179884
[15:32] <tsdgeos> Cimi: or am i looking at the wrong place?
[15:33] <greyback> tsdgeos: ok, I'll do code review so
[15:33] <tsdgeos> awesome
[15:42] <Cimi> tsdgeos, pushed
[15:44] <tsdgeos> ok
[16:02] <Saviq> sil2100, we're now doing multiple releases a day, right?
[16:02] <sil2100> Saviq: yes, every 4 hours basically
[16:03] <Saviq> sil2100, ok, so if I can see "cu2d-unity8-head-3.0publish	1 hr 19 min" we should effectively expect a new release in ~2:40
[16:07] <sil2100> Saviq: more or less, since the check job takes some time as well, and sometimes there might be some delays with other depending stacks etc.
[16:07] <Saviq> sil2100, yeah, that's why I'm looking at the publish one
[16:07] <Saviq> sil2100, but yeah, I get it that's tentative
[16:12] <Cimi> seb128, you EOD?
[16:12] <seb128> Cimi, not really, still busy trying to finish some stuff, why?
[16:13] <sil2100> seb128: btw. you doing work today ;)?
[16:13] <Cimi> seb128, I'd like to have a chat with Saviq on the backend for settings
[16:13] <seb128> sil2100, sure, I've been working offline a part of the day while travelling though
[16:13] <seb128> Cimi, tomorrow is better if that works for you guys
[16:13] <Cimi> seb128, tomorrow morning?
[16:14] <seb128> I'm at dholbach's and I want to finish some stuff before we go out
[16:14] <seb128> that should work, what time do you have in mind?
[16:14] <sil2100> seb128: I'll poke you about g-c-c-u for raring tomorrow as well then ;)
[16:14] <Cimi> seb128, something around your 10:30-11 might be right
[16:14] <seb128> sil2100, ok
[16:15] <seb128> sil2100, I'm working normal hours for the rest of the week, I was just travelling today
[16:17] <sil2100> seb128: cool!
[16:19] <sil2100> olli_: hi! You around?
[16:19] <seb128> Cimi, that works for me
[16:19] <olli_> sil2100, what's up
[16:19] <seb128> sil2100, did you want to see about g-c-c-u now or tomorrow?
[16:22] <sil2100> olli_: just want to give you a heads up about unity related SRU for raring - we're currently blocked with releasing the unity stack, there was a compiz change that's pending, but it needs an additional unity change to get in before we can SRU it
[16:22] <sil2100> seb128: I'm on a hangout right now, but a quick thing about that if you have a moment:
[16:22] <olli_> bregma, are you aware of that?
[16:23] <sil2100> seb128: https://bugs.launchpad.net/bugs/1173818 <- this is blocking g-c-c-u for raring in -proposed, not sure if we should push it forward or block it until the other issue is fixed?
[16:23] <olli_> sil2100, what needs doing?
[16:23] <sil2100> seb128: since I agree with Doug that it's a different issue, but it appeared with this fix and makes things broken anyway
[16:24] <sil2100> seb128: should we mark it as verification-done and just leave it for a separate release?
[16:25] <seb128> sil2100, I can have a look
[16:26] <sil2100> olli_: unity needs to have a change in that adds the showdesktop code into unity instead of compiz, that's a really small change and I think andyrock was backporting it already (or already prepared a merge even)
[16:29] <olli_> sil2100, so it's really just a heads up, no action required?
[16:29] <sil2100> olli_: yes ;)
[16:29] <olli_> sil2100, thx!
[16:29] <olli_> sil2100, bregma is your man in case something needs doing
[16:35] <Cimi> tsdgeos, what's happening here? https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1055/console
[16:40] <tsdgeos> Cimi: test_rightEdgeDrag fails "randomly"
[16:40] <tsdgeos> Cimi: just retrigger the build
[16:40] <Cimi> why it does?
[16:40] <tsdgeos> no idea
[16:40] <Cimi> tsdgeos, who approved? :)
[16:41] <tsdgeos> no idea
[16:41] <tedg> dednick, So what other uses of libupstart are you imaging?
[16:41] <tedg> imagining?
[16:41] <tsdgeos> Cimi: was it me?
[16:41] <Cimi> tsdgeos, no was just asking
[16:41] <Cimi> tsdgeos, advantage of working remotely is that we can't kick each other asses for those things :P
[16:42] <dednick> tedg: we're going to start apps with upstart
[16:42] <tedg> dednick, Yeah, but that's using libupstart-app-launch which hides libupstart
[16:42] <Cimi> tsdgeos, no big deal was just joking
[16:42] <Cimi> tsdgeos, but would be great to have reliable tests
[16:42] <tsdgeos> agreed
[16:43] <dednick> Saviq: any other use cases for upstart other than indicators (that arent using libupstart-app-launch)?
[16:45] <sil2100> seb128: thanks!
[16:51] <seb128> sil2100, yes, let's verification-done that one, I'm going to have a look to the other issue another day, but no need to block 90% of the fix on 10% missing
[16:53] <sil2100> seb128: awesome, doing that and let's get this released
[16:53] <sil2100> Ah, done already
[16:53] <seb128> sil2100, I changed the tag, and yes, agreed, let's get that in ;-)
[16:53] <sil2100> Cool! :)
[16:54] <sil2100> Thanks again
[17:11] <bregma> sil2100, could you please email me with what's going on with compiz/unity etc -- I'm trying to handle a water emergency right now
[17:29] <sil2100> bregma: will do!
[17:29] <sil2100> bregma: I'll include all the info for things saucy and raring related
[17:34] <bregma> great, thanks
[17:46] <tvoss> Saviq, getting to the mail now
[18:02] <dednick> Saviq: ping
[18:50] <Saviq> dednick pong
[18:51] <dednick> Saviq: hey. been trying to get that diff branch for you working, but unsucessfully. I managed to get it to Indicators vs IndicatorsLegacy, but doing it with replacement rather than renames end in a branch over about 6k.
[18:57] <Saviq> dednick, weird, it should effectively be a case of renaming (not bzr mv) Indicators2 to Indicators and adding IndicatorsLegacy
[18:57] <Saviq> dednick, but don't worry much, I'll have a try of that tomorrow morning
[18:57] <Saviq> dednick, it's just sugar, really
[20:02] <Luzbelito> Hello, i'm running ubuntu 13.04, and do not know why ive lost any interaction with the windows. compiz crashed, and dont have dash or upper panel
[20:02] <Luzbelito> 	i've googled and tried several suggestions, but nothing yet
[20:06] <Luzbelito> now logged in enlightenment. but I really want my unity back
[20:06] <Luzbelito> Any idea_
[20:06] <Luzbelito> ?\
[20:07] <bschaefer> Luzbelito, hello, so are you able to press ctrl+alt+t to open a terminal?
[20:08] <bschaefer> if so try entering "unity" to try and start unity back up, if it fails it should hopefully say a bit more info on why it fail :)
[20:15] <Luzbelito> gives me this:  unity
[20:15] <Luzbelito> compiz (core) - Info: Loading plugin: core
[20:15] <Luzbelito> compiz (core) - Info: Starting plugin: core
[20:15] <Luzbelito> compiz (core) - Error: Another window manager is already running on screen: 0
[20:16] <Luzbelito> compiz (core) - Info: Stopping plugin: core
[20:16] <Luzbelito> compiz (core) - Info: Unloading plugin: core
[20:16] <Luzbelito> luzbelito@LAGATA-NV59C:~$ unity-panel-service: proceso no encontrado
[20:16] <bschaefer> Luzbelito, hmm so unity is already running? Try going into ccsm and seeing if all the plugins have stopped them selfs
[20:17] <bschaefer> Luzbelito, so "ccsm" in the command line and look for Unity Plugin
[20:17] <bschaefer> and see if its enabled or not
[20:17] <Luzbelito> could be because I'm logged now in enlightenment environment?
[20:17]  * bschaefer isn't sure what enlightenment env is :)
[20:17] <bschaefer> Luzbelito, but that could be
[20:17]  * bschaefer sees its a different WM
[20:18] <bschaefer> Luzbelito, yes that would cause some problems, if you try to go back to the version where compiz has crashed
[20:18] <bschaefer> and try to restart unity, if you can't restart unity, try going to a tty and doing a "DISPLAY=:0 unity --advanced-debug" which will start it in gdb, which will hopefully help figure out whats
[20:18] <bschaefer> causing the crash
[20:19] <Luzbelito> too much info! sorry, but what a tty is?
[20:19] <bschaefer> Luzbelito, sorry, tty is Ctrl+Alt+F1
[20:20] <bschaefer> Luzbelito, but first try to start unity after compiz has crashed
[20:20] <Luzbelito> a terminal
[20:22] <Luzbelito> well. So i must log out from here and log in the crashed unity, open a tty, call the irc for continue following steps, and in another tab DISPLAY=:0 unity --advanced-debug
[20:22] <Luzbelito> that's correct?
[20:23] <Luzbelito> going for it
[20:23] <bschaefer> Luzbelito, hmm well first you want to try and start unity outside of a tty
[20:23] <bschaefer> well... good luck!
[20:28] <Luzbelito> how can I ask for make a .txt from the info of a tty?
[20:28] <bschaefer> Luzbelito, soo you should be able to do this:
[20:29] <bschaefer> unity --advanced-debug 2>&1 | tee unity-gdb.log
[20:29] <bschaefer> Luzbelito, but you should try to start unity again from the crashed desktop first
[20:29] <bschaefer> Luzbelito, if you are able to do Ctrl+alt+t to bring up a terminal on the desktop
[20:29] <bschaefer> try just starting unity from there
[20:30] <Luzbelito> ok
[20:31] <Luzbelito> did it. the screen flashed, but no changes
[20:32] <bschaefer> Luzbelito, did the terminal say anything interesting?
[20:33] <bschaefer> Luzbelito, also, lets double check the unity plugin is enabled, try typing "ccsm" in the terminal
[20:33] <bschaefer> also find the "Ubuntu Unity Plugin"
[20:33] <bschaefer> err "and find the"*
[20:33] <Luzbelito> there could be! a line says no unity-panel-service no process found
[20:36] <bschaefer> Luzbelito, hmm possibly, but the command "unity" should restart that process...but if you get a chance to pastebin the output of attempting to restart unity that could possibly help :)
[20:36] <Luzbelito> it is no more installed. I did purge compiz* few hours ago
[20:37] <Luzbelito> looking for help with this same issue they said purge compiz then install ubuntu-desktop
[20:37] <bschaefer> Luzbelito, well reinstalling compiz/unity again could help
[20:37] <bschaefer> hmm it should have been installed again, if you can't find ccsm try install compiz-config-setting-manager
[20:38] <Luzbelito> installing now
[20:39] <bschaefer> also make sure compiz unity are installed as well
[20:42] <Luzbelito> opened ccsm hard to manage, not having any interaction with the windows, but yes. unity plugin checked
[20:42] <Luzbelito> nothing changed
[20:42] <Luzbelito> should I relog or something?
[20:43] <bschaefer> Luzbelito, alright, hmm interesting would you be able to pastebin what attempting to start unity says?
[20:43] <bschaefer> ie. what plugins its failing on?
[20:44] <Luzbelito> it says that not found unity-panel-service process
[20:44] <Luzbelito> sorry my english is poor
[20:45] <bschaefer> Luzbelito, well I mean anything else?
[20:45] <bschaefer> Luzbelito, no worries! Lets try this then
[20:45] <Luzbelito> ok
[20:45] <Luzbelito> shot it
[20:45] <bschaefer> Luzbelito, /usr/lib/unity/unity-panel-service
[20:45] <bschaefer> is where that service is
[20:45] <bschaefer> soo try going there and doing:
[20:46] <bschaefer> /usr/lib/unity/unity-panel-service; unity
[20:46] <bschaefer> or just doing that :)
[20:46] <bschaefer> as im guessing u-p-s is crashing causing unity to crash :(
[20:47] <Luzbelito> so I type in the terminal /usr/lib/unity/unity-panel-service?
[20:47] <bschaefer> Luzbelito, yup copy/type this whole line in:
[20:47] <bschaefer> /usr/lib/unity/unity-panel-service; unity
[20:49] <Luzbelito> this is the return:
[20:49] <Luzbelito> (unity-panel-service:10502): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
[20:49] <Luzbelito> (unity-panel-service:10502): libindicator-WARNING **: Unable to load icon from file 'audio-output-none' because: No se ha podido abrir el archivo «audio-output-none»: No existe el archivo o el directorio
[20:49] <Luzbelito> (unity-panel-service:10502): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
[20:49] <Luzbelito> (unity-panel-service:10502): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
[20:49] <Luzbelito> (unity-panel-service:10502): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_client_get_root: assertion `DBUSMENU_IS_CLIENT(client)' failed
[20:49] <Luzbelito> (unity-panel-service:10502): LIBDBUSMENU-GLIB-CRITICAL **: dbusmenu_menuitem_get_children: assertion `DBUSMENU_IS_MENUITEM(mi)' failed
[20:49] <Luzbelito> ** (unity-panel-service:10502): WARNING **: unable to open indicator service file directory: Falló al abrir el directorio «/usr/share/unity/indicators»: No existe el archivo o el directorio
[20:49] <Luzbelito> (unity-panel-service:10502): IDO-CRITICAL **: ido_calendar_menu_item_get_calendar: assertion `IDO_IS_CALENDAR_MENU_ITEM (menuitem)' failed
[20:49] <Luzbelito> (unity-panel-service:10502): Gtk-CRITICAL **: gtk_calendar_get_date: assertion `GTK_IS_CALENDAR (calendar)' failed
[20:50] <Luzbelito> (unity-panel-service:10502): Gtk-CRITICAL **: gtk_calendar_select_month: assertion `GTK_IS_CALENDAR (calendar)' failed
[20:50] <Luzbelito> (unity-panel-service:10502): Gtk-CRITICAL **: gtk_calendar_select_day: assertion `GTK_IS_CALENDAR (calendar)' failed
[20:50] <Luzbelito> (unity-panel-service:10502): Gtk-CRITICAL **: gtk_widget_realize: assertion `widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed
[20:50] <Luzbelito> (unity-panel-service:10502): Gtk-CRITICAL **: gtk_widget_realize: assertion `widget->priv->anchored || GTK_IS_INVISIBLE (widget)' failed
[20:50] <Luzbelito> (unity-panel-service:10502): Indicator-Session-WARNING **: Couldn't load the image "/home/javo/.face": No se ha podido abrir el archivo «/home/javo/.face»: No existe el archivo o el directorio
[20:50] <bschaefer> hmm
[20:51] <bschaefer> Luzbelito, are you able to start eog?
[20:51] <Luzbelito> looks like I've deleted those files or something
[20:51] <Luzbelito> I don't know. Can try
[20:51] <Luzbelito> what's eog
[20:51] <Luzbelito> ?
[20:51] <bschaefer> eye of gnome
[20:51]  * bschaefer thinks
[20:52] <Luzbelito> never did it before. Can try
[20:52] <bschaefer> Luzbelito, I don't think thats the problem...but if u-p-s isn't starting something ins't right on your system hmm
[20:53] <Luzbelito> is there a way to reinstall the whole distribution without affect the /home?
[20:53] <bschaefer> Luzbelito, also if you could tell me any more information that comes up when you type "unity" as after it says unity-panel-service can't start it has to be trying to load plugins
[20:54] <bschaefer> Luzbelito, well you could really just re-install 13.04 and all should be good...
[20:54] <Luzbelito> mmmm
[20:54] <bschaefer> but you'll lose all information, unless you save stuff to a HD
[20:54] <Luzbelito> but where would be the spirit?
[20:55] <Luzbelito> ill paste my returns from calling unity
[20:55] <bschaefer> Luzbelito, hmm, so could copy what type "unity" says and paste it here?
[20:55] <bschaefer> http://paste.ubuntu.com/
[20:55] <bschaefer> copy what "unity" says
[21:52] <mterry> Is it possible to run unity8 as your desktop session?  Are there instructions anywhere for that?  (All I find is ./run suggestions)
[22:37] <Luzbelito> hello, bschaefer
[22:37] <bschaefer> Luzbelito, hey, any luck?
[22:38] <Luzbelito> sorry i left suddenly. Im a teacher and had the kids at the door
[22:38] <Luzbelito> now at home.
[22:45] <Luzbelito> this is the return of mi terminal when call unity:
[22:45] <Luzbelito> luzbelito@LAGATA-NV59C:~$ unity
[22:45] <Luzbelito> compiz (core) - Info: Loading plugin: core
[22:45] <Luzbelito> compiz (core) - Info: Starting plugin: core
[22:45] <Luzbelito> unity-panel-service: proceso no encontrado
[22:45] <Luzbelito> compiz (core) - Info: Loading plugin: ccp
[22:45] <Luzbelito> compiz (core) - Info: Starting plugin: ccp
[22:45] <Luzbelito> compizconfig - Info: Backend     : gsettings
[22:45] <Luzbelito> compizconfig - Info: Integration : true
[22:45] <Luzbelito> compizconfig - Info: Profile     : unity
[22:45] <Luzbelito> compiz (core) - Info: Loading plugin: composite
[22:45] <Luzbelito> compiz (core) - Info: Starting plugin: composite
[22:45] <Luzbelito> compiz (core) - Info: Loading plugin: opengl
[22:45] <Luzbelito> compiz (core) - Info: Unity is fully supported by your hardware.
[22:46] <Luzbelito> compiz (core) - Info: Unity is fully supported by your hardware.
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: opengl
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: compiztoolbox
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: compiztoolbox
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: decor
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: decor
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: vpswitch
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: vpswitch
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: snap
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: snap
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: mousepoll
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: mousepoll
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: resize
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: resize
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: place
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: place
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: move
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: move
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: wall
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: wall
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: grid
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: grid
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: regex
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: regex
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: imgpng
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: imgpng
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: session
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: session
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: gnomecompat
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: gnomecompat
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: animation
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: animation
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: fade
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: fade
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: unitymtgrabhandles
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: unitymtgrabhandles
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: workarounds
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: workarounds
[22:46] <Luzbelito> compiz (core) - Info: Loading plugin: scale
[22:46] <Luzbelito> compiz (core) - Info: Starting plugin: scale
[22:47] <Luzbelito> compiz (core) - Info: Loading plugin: expo
[22:47] <Luzbelito> compiz (core) - Info: Starting plugin: expo
[22:47] <Luzbelito> compiz (core) - Info: Loading plugin: ezoom
[22:47] <Luzbelito> compiz (core) - Info: Starting plugin: ezoom
[22:47] <Luzbelito> compiz (core) - Info: Loading plugin: unityshell
[22:47] <Luzbelito> Segmentation fault (core dumped)
[22:47] <bschaefer> Luzbelito, hmm also next time could you please paste it to: http://paste.ubuntu.com/
[22:47] <bschaefer> Luzbelito, soo unity is seg faulting fun, now let run unity --advanced-debug in the TTY (Ctrl+Alt+F1)
[22:48] <bschaefer> unity --advanced-debug 2>&1 | tee unity-gdb.log
[22:50] <Luzbelito> ok
[22:54] <Luzbelito> can't tipe this character  > on tty with spanish keyboard
[22:55] <Luzbelito> is there any way to change the setting in terminal
[22:55] <Luzbelito> ?
[22:56] <bschaefer> Luzbelito, o umm
[22:56] <bschaefer> it should be on the spanish keyboard somewhere
[22:57] <bschaefer> annnd it doesn't appear to be hmm
[22:57] <bschaefer> Luzbelito, can you change the keyboard layout?
[22:58] <Luzbelito> is there a way to call the settings from terminal?
[22:58] <bschaefer> yeah, one sec have to look it up
[22:59] <Luzbelito> thsnk you very much, bschaefer, you are taking so much work
[23:02] <bschaefer> Luzbelito, np, and the only problem im having to how to get you back to spanish after changing the layout :)
[23:03] <bschaefer> to get to english you can do "setxkbmap en_US"
[23:03] <Luzbelito> no problem
[23:03] <Luzbelito> ok
[23:04] <Luzbelito> done
[23:04] <Luzbelito> now, im going to tty
[23:04] <bschaefer> alright
[23:05] <Luzbelito> no way. in tty the setting remains sapnish
[23:05] <bschaefer> Luzbelito, hmm try setxbmap us in the tty
[23:05] <bschaefer> Luzbelito, if that fails we can just have you copy paste this into a file and you can run it from the tty
[23:06]  * bschaefer also thinks "es" will take you back to spanish
[23:13] <bschaefer> Luzbelito, also to pastebin from the command line install: pastebinit
[23:13] <bschaefer> then onces you get that gdb log, type:
[23:13] <bschaefer> pastebinit unity-gdb.log
[23:14] <bschaefer> o yeah, after you tun unity --advanced-debug type "r" to run unity
[23:14] <bschaefer> well to run gdb, which will run unity :)
[23:14] <Luzbelito> how can I run this from a file?
[23:15] <bschaefer> Luzbelito, alright you can copy and paste in a terminal right?
[23:15] <Luzbelito> yes
[23:15] <Luzbelito> but not in the tty
[23:16] <bschaefer> echo "unity --advanced-debug 2>&1 | tee unity-gdb.log" > ~/command
[23:16] <bschaefer> Luzbelito, run that, which will make a file command in your home directory
[23:16] <bschaefer> int he TTY run:
[23:16] <bschaefer> `cat ~/command`
[23:18] <Luzbelito> you won't believe it, but now the problem, is the character 	`
[23:19] <bschaefer> :), that should be the right of your letter P
[23:19] <bschaefer> if Im looking at the right keyboard layout...
[23:20] <bschaefer> yeah, just hit it twice, as its a dead key I think at first
[23:20] <Luzbelito> but goes the otheer way
[23:20] <bschaefer> `
[23:20] <bschaefer> when I set my keyboard layout to es
[23:20] <bschaefer> hmm
[23:21] <bschaefer> Luzbelito, well the other one I see is 2 keys to the right of the letter L
[23:21] <bschaefer> ´
[23:21] <bschaefer> but thats the wrong way for me...
[23:22] <bschaefer> Luzbelito, alright, well lets just skip the log file and just try this from the TTY
[23:22] <bschaefer> unity --advanced-debug
[23:22] <bschaefer> after that hit r to run it, and go back to ctrl+alt+f7
[23:22] <Luzbelito> {**ok
[23:26] <bschaefer> Luzbelito, and once you see everything crash go back to ctrl+alt+f1 and let me know what the error was
[23:26] <bschaefer> there should be a gaint seg fault, and line that is guilty
[23:39] <Luzbelito> fail
[23:39] <Luzbelito> it returned me a lot of lines, then I put r
[23:39] <Luzbelito> then another lot of lines
[23:40] <Luzbelito> then ctr+alt f7 took me to a black screen. just the mouse remained
[23:40] <Luzbelito> so i had to reboot
[23:40] <Luzbelito> and here am i
[23:41] <bschaefer> Luzbelito, hmm this is where putting that into a log would have helped :) hmm
[23:47] <bschaefer> Luzbelito, do you see any message that pop up about a compiz crashing? the app would be apport?
[23:47] <Luzbelito> bschaefer, even if i stop trying by now, given your experience, whats your diagnostic? do you think the situation is recoverable?
[23:48] <bschaefer> Luzbelito, well...usually yes, if unity is crashing im assuming something is missing, or put together wrong
[23:48] <Luzbelito> yes, bschaeffer, when i start up there is the typical ubuntu13.04 has experimented an inner error
[23:48] <bschaefer> Luzbelito, could you try to follow through with that and try and report a bug? As it could take you somewhere people have already reported
[23:49] <Luzbelito> opening it an waiting, gives informationa refering  compiz crash
[23:49] <bschaefer> sounds good
[23:49] <Luzbelito> and hplip dont-know-what other error too
[23:49] <Luzbelito> but i couldn't copy that text
[23:50] <Luzbelito> mmm
[23:50] <bschaefer> Luzbelito, if you continue it should attempt to file a bug report
[23:51] <Luzbelito> ah, the other curious thing, i wanted to comment with you is that when initing the system, before login
[23:51] <bschaefer> if so, the it'll have all the stack traces I would need to actually see whats the problem
[23:51] <Luzbelito> ther IS the upper panel there, in fact ive connected the internet using that panel
[23:51] <Luzbelito> that disssappears whe login in any user
[23:52] <bschaefer> Luzbelito, before you loging, the panel is no longer there? Or after?
[23:52] <Luzbelito> bfore login the panel is there
[23:53] <Luzbelito> after login not
[23:56] <bschaefer> Luzbelito, yeah, without compiz you wont get it...
[23:56] <bschaefer> Luzbelito, well without more information about the cause of the crash its hard for me to help much more :(
[23:59] <Luzbelito> well
[23:59] <Luzbelito> i wnat to thank you very much for your help
[23:59] <bschaefer> Luzbelito, well one more thing...