[09:07] <mzanetti> Guest74213, you want to wait an hour or two, update your system and try again
[09:08] <mzanetti> Guest74213, alternatively, check out lp:unity-api, build that yourself and install it
[09:22] <Guest74213> mzanetti, thanks :D i think i'll wait o/
[09:39] <Saviq> Guest74213, as I wrote on the bug, new libunity-api-dev is available in xenial for almost a day now
[09:40] <Saviq> it might be your mirror is behind, might want to use archive.ubuntu.com directly in that case
[09:41] <Guest74213> Saviq, i have libunity-api-dev 7.103+16.04.20151125-0ubuntu1 installed
[09:41] <Guest74213> and i still can build
[09:42] <Saviq> Guest74213, owait, the correct unity-shell-application version is 11, when did you last pull?
[09:43] <Guest74213> Saviq, yesterday :D omg i'm so dumb, i'll pull again now
[09:43] <Guest74213> <--- dumb
[09:44] <Saviq> Guest74213, and you really want to fix your IRC client to keep your nick :P
[09:44] <pixel_> done :D
[09:46] <Saviq> anyone else seeing a "diamond" character instead of "ff" in, say "affects" in Launchpad?
[09:46] <Saviq> /methinks saw it in Thunderbird, too
[09:46] <Saviq> that's Firefox, btw
[09:48] <Saviq> greyback, bug #1521106, might be unity8/qtmir, too, as we're not suspending music app and keeping the wakelock, thus?
[09:49] <davmor2> Saviq: might not be music app but might be media-hub as it had a partial update for background music playback that got complete recently iirc
[09:50] <Saviq> davmor2, right, pause != interrupt playback
[09:50] <Saviq> wonder if not ever starting playback has the same effect
[09:53] <davmor2> Saviq: so I just opened the music app and it now holds a queue of what was previously played so that is effectively media-hub queued ready to play
[09:53] <pixel_> Saviq, it's building now :D -- checking for module 'unity-shell-application=11'
[09:53] <pixel_> --   found unity-shell-application, version 11
[09:53] <pixel_> :D
[09:54] <Saviq> davmor2, right, but ready to play != pipeline all set up
[09:54] <Saviq> pixel_, glad
[09:55] <davmor2> Saviq: this is true
[09:56] <davmor2> Saviq: I'd bring it up with ahayzen and jhodapp too before you dig into it too far in case it is their end
[10:00] <Saviq> davmor2, ack, tx
[10:04] <cimi> tsdgeos, hola!
[10:04] <greyback> Saviq: hey, yeah, there was a similar bug that I investigated a bit & commented upon, lemme find it
[10:05] <tsdgeos> cimi: hi ho
[10:05] <greyback> Saviq: https://bugs.launchpad.net/music-app/+bug/1518764
[10:05]  * greyback marking duplicate
[10:05] <cimi> tsdgeos, I was wondering if there is a branch has priority to be tested/reviewed so I can jump on in
[10:05] <cimi> *it
[10:05] <Saviq> greyback, tx
[10:08] <tsdgeos> cimi: not really, the missing branches are either filters branches but still somehow blocked on the "can't open" bug
[10:17] <popey> I notice the ubuntu shape now has a shadow outside rather than inside in the app scope,  but still has the old internal shadow in the list of scopes pulled up from the bottom... http://people.canonical.com/~alan/screenshots/device-2015-11-30-100402.png
[10:17] <popey> is this known - and in progress - or a bug?
[10:17] <mzanetti> Saviq, why did you reopen this? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1510969
[10:17] <mzanetti> seems fixed to me
[10:18] <Saviq> mzanetti, tried when testing silo 5 and couldn't resize when 1-2px from the edge
[10:18] <mzanetti> Saviq, hmm... should work... kk, will test
[10:19] <mzanetti> popey, dunno. design instructed us to change it for the app icons, but no other shapes are affected
[10:19] <mzanetti> popey, you might want to file a bug to ubuntu-ux about it if you think it's wrong
[10:20] <popey> dunno if it's wrong but it's inconsistent
[10:20] <popey> all the scopes have the old one too
[10:20] <popey> so swipe side to side and the difference is obvious
[10:20] <mzanetti> yes. only the app icons have the new one
[10:20]  * popey files a bug
[10:24] <popey> https://bugs.launchpad.net/ubuntu-ux/+bug/1521130
[10:41] <tsdgeos> mzanetti: any reason https://code.launchpad.net/~aacid/unity8/cleanup_assets/+merge/278340 not top approved?
[10:42] <mzanetti> tsdgeos, hmm, not that I know of
[10:43] <mzanetti> I wonder if I forgot or if someone change it back
[10:54] <mzanetti> Saviq, is there a way to ignore ofono's "start" action in the postinstall stuff?
[10:54] <mzanetti> if I want to have unity8 installed, it pulls ofono
[10:54] <mzanetti> and that messes up whole dpkg
[10:56] <tsdgeos> mzanetti: just touch the init.d file it wants
[10:56] <tsdgeos> touch /etc/init.d/ofono
[10:56] <tsdgeos> yes, the packaging can be probably improved to not die because of that :D
[10:57] <mzanetti> tsdgeos, hmm.. doesn't seem to help
[10:57] <tsdgeos> hmmm
[10:57] <tsdgeos> it did help here
[10:57] <tsdgeos> what error do you get?
[10:58] <mzanetti> Nov 30 11:57:11 Shadow systemd[1]: ofono.service: main process exited, code=killed, status=11/SEGV
[10:58] <tsdgeos> ah, that's not what i was getting
[10:58] <tsdgeos> i was getting apt complain about /etc/init.d/ofono not existing and not being able to start the thing
[10:59] <mzanetti> also it seems wrong that we have a hard dependency on ofono
[11:00] <tsdgeos> yeah
[11:02] <tsdgeos> larsu: there?
[11:02] <Saviq> mzanetti, well, we should not be pulling in ofono, that's for sure... but we do through indicator-network
[11:03] <mzanetti> https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1521142
[11:03] <mzanetti> I know
[11:03] <Saviq> as well as some other things, /me never had that problem with ofono though
[11:03] <Saviq> might be because I had it installed before systemd or something
[11:04] <mzanetti> I think the only issue is that since a recent upgrade it fails to start with a SEGV
[11:04] <mzanetti> and the startup script wants it to work
[11:04] <mzanetti> so it exits with error now
[11:04] <mzanetti> leaving about 15 packages unconfigured here
[11:06] <mzanetti> interesting that it says this on my laptop:  ofonod[8671]: RILDEV detected modem type ril, 1 SIM slot(s)
[11:11] <mzanetti> Saviq, ok, about that bug from before with resizing. I have a suspicion that the new DDA on the right is eating the hower events
[11:12] <mzanetti> different bug... will clean up the reports
[11:13] <tsdgeos> larsu: if you have some time to have a look at https://code.launchpad.net/~aacid/gsettings-qt/disconnect_signal_handler/+merge/278947 it'd be great
[11:29] <Saviq> mzanetti, well, same bug, different cause ;)
[11:30] <mzanetti> Saviq, not really... the bug says: "resizing something next to the edges invokes the spread"
[11:30] <mzanetti> anyhow
[11:31] <mzanetti> i.e. you can now resize something *to* the edge, which wasn't really possible before
[11:31] <mzanetti> or well, would invoke the spread and cancel the drag operation
[11:31] <Saviq> mzanetti, ack
[11:32] <Saviq> mzanetti, I misinterpreted the bug title then
[11:33] <larsu> tsdgeos: done, thanks
[11:35] <tsdgeos> larsu: yeah i found it weird too, but i guess valgrind would not be lying there
[11:35] <larsu> tsdgeos: probably gsettings holding a ref to itself in an idle or so to clean stuff up
[11:35] <larsu> no, valgrind seems right to me
[11:46] <vitimiti> Hi
[11:46] <vitimiti> I'm trying to build and run the Unity 8 shell following this tutorial over here: https://unity.ubuntu.com/getinvolved/development/unity8/ but I get an initctl error saying the unity8 process is unknown: http://paste.ubuntu.com/13573548/ Somebody knows how to fix this problem?
[11:47] <mzanetti> vitimiti, try "stop unity8" first
[11:48] <vitimiti> mzanetti, it says "Impossible connecting to Upstar: Failed to connect to socket /com/ubuntu/upstart: Refused connection
[11:49] <mzanetti> hmpf
[11:49] <vitimiti> "
[11:49] <vitimiti> (I'm roughly translating from Spanish)
[11:49] <mzanetti> tsdgeos, this was working for you some weeks ago, right? ^
[11:50] <mzanetti> vitimiti, you can also do this "make -c builddir tryShell"
[11:50] <mzanetti> should give you the same result roughly as run.sh
[11:50] <vitimiti> Let me try that
[11:50] <tsdgeos> mzanetti: it may happen that you need to have unity8 installed for that to work
[11:50] <tsdgeos> not sure tbh
[11:51] <mzanetti> tsdgeos, in his case it says it would be running already
[11:51] <vitimiti> No rule to make target, it said :I
[11:51] <mzanetti> you did build it, did you?
[11:51] <vitimiti> I have unity8 installed in LXC
[11:51] <vitimiti> Yeah, it is built
[11:51] <mzanetti> cd builddir && make tryShell
[11:55] <vitimiti> I'm sorry, my laptop got disconnected from the A/C
[11:56] <vitimiti> I built the unity8 shell with the ./build.sh script
[11:56] <vitimiti> mzanetti, ^
[11:57] <mzanetti> cd builddir && make tryShell
[11:57] <Saviq> vitimiti, it looks as if your upstart user session is not running, what's your environment?
[11:57] <vitimiti> Saviq, I'm using Unity 7 in Ubuntu Xenial
[11:57] <Saviq> vitimiti, any chance your terminal has stale env vars? tried restarting it?
[11:58] <vitimiti> mzanetti, that target has no rules, it says
[11:58] <vitimiti> Saviq, no, I have never touched my terminal's variables, but just in case, how do I restart it?
[11:58] <mzanetti> something's wrong with your build
[11:59] <vitimiti> Should I try build --clean?
[12:00] <Saviq> vitimiti, just close the terminal and start again
[12:00] <vitimiti> Oh, then that's not the problem
[12:02] <vitimiti> I have installed unity8 natively and now it's asking for a reboot, just in case that's why initctl is failing
[12:02] <vitimiti> I will reboot
[12:02] <Saviq> vitimiti, how's `initctl --session list` look?
[12:02] <vitimiti> Saviq, that one does show unity8 stop/waiting
[12:03] <Saviq> vitimiti, try rebooting indeed, might be your upstart went awry
[12:03] <vitimiti> I will wait for the rebuild and then reboot and see what happens
[12:42] <vitimiti> Now it does work
[12:42] <vitimiti> Thank you guys
[13:24] <mzanetti> greyback, hey, are you running xenial?
[13:26] <greyback> mzanetti: not on the machine I have with me atm unfortunately
[13:26] <mzanetti> greyback, just upgraded my notebook, obviously wifi is gone
[13:26] <greyback> mzanetti: d'oh :(
[13:26] <mzanetti> and the bcmwl-kernel-source package seems not to exist any more at all now
[13:27] <mzanetti> b43 only gets me b/g
[13:43] <mzanetti> greyback, did you port that driver to 3.15 back then?
[13:46] <mzanetti> phew... works with 3.19 still
[13:47] <mzanetti> and I still had that kernel around
[13:47] <greyback> mzanetti: I guess our kernel guys will forward port the driver eventually
[13:48] <mzanetti> greyback, probably not, no
[13:48] <mzanetti> greyback, remember, bcm upstream dropped support for our chip
[13:49] <mzanetti> so all we will get is the broken version that can't do stable
[13:50] <mzanetti> anyhow... xenial + downgrade to kernel 3.19 + the patched bcmwl-kernel-source package seems to do...
[13:54] <greyback> mzanetti: did they? b*stards!
[14:01] <davmor2> greyback: is that only dawning on you now ;)
[14:02] <greyback> lol
[14:02] <davmor2> greyback: sorry /me gets hit by it too often testing iso images and seeing how broken they can be
[14:03] <greyback> davmor2: *nod* they caused me enough pain to forward port an older version of the driver, just to get something that mostly works
[14:22] <mzanetti> Trevinho, hey, just upgraded to vivid. great to see a normal sized mouse cursor :)
[14:22] <mzanetti> erm, xenial
[14:22] <mzanetti> Trevinho, the count emblem seems a bit off tho
[14:23] <Trevinho> mzanetti: yeah, cursors are now dynamic.. Finally. Also theme-side :-)
[14:23] <Trevinho> mzanetti: count emblem has not been changed, but it used to be in some cases in the past as well
[14:23] <Trevinho> it's a thing that should be fixed... It's just few px of offset I guess
[14:23] <mzanetti> http://i.imgur.com/zdKo4iE.png
[14:23] <Trevinho> ah, I was about to ask
[14:23] <Trevinho> oh... That
[14:23] <Trevinho> Mh, no never saw
[14:23] <Trevinho> ahhhhhhh
[14:23] <mzanetti> same in the launcher
[14:23] <Trevinho> that's with scaling
[14:24] <mzanetti> yes
[14:24] <Trevinho> so... Maybe I didn't take in consideration something
[14:24] <Trevinho> mzanetti: wasn't it before, right?
[14:24] <mzanetti> was fine on vivid, yes
[14:24] <mzanetti> I skipped wily
[14:24] <Trevinho> as that code hasn't changed since trusty I think
[14:24] <Trevinho> mh
[14:25] <mzanetti> Trevinho, the external screen is still unusable :( think that will be fixed at some point?
[14:25] <mzanetti> funny thing is, that the top panel actually has the correct size
[14:26] <mzanetti> but all the other stuff is huge
[14:35] <mzanetti> Saviq, hmpf... can you install unity8 on wily?
[14:35] <mzanetti> gna... xenial
[14:35] <davmor2> mzanetti: because it hates you
[14:36] <mzanetti> yes
[14:36] <mzanetti> wants libhybris
[14:36] <mzanetti> gah I hate that indicator-network
[14:36] <davmor2> mzanetti: also welcome to how the hell were people testing on xenial when they said they had ;)
[14:37] <mzanetti> I never said I tested on xenial
[14:37] <mzanetti> and well, flashing the phone to xenial might be easier
[14:38] <Saviq> mzanetti, I am on xenial and everything's fine, I did upgrade however, "new install" path might be different
[14:38] <mzanetti> I wonder if I can downgrade to vivid again...
[14:38] <mzanetti> I did upgrade too
[14:38] <mzanetti> Saviq, for me it wants to install libhybris
[14:38] <mzanetti> and that well, doesn't want to be installed on amd64
[14:38] <Saviq> not a problem I don't think
[14:39]  * Saviq has libhybris installed
[14:39] <mzanetti>  libhybris : Depends: libandroid-properties1 (= 0.1.0+git20131207+e452e83-0ubuntu40~gcc5.1) but 0.1.0+git20151016+6d424c9-0ubuntu2 is to be installed
[14:39] <Saviq> just means you have the *wrong* libhybris to install
[14:39] <mzanetti> ph...
[14:39] <mzanetti> oh
[14:39] <Saviq> just install libandroid-properties1=0.1.0...
[14:40] <Saviq> likely some PPA you have enabled
[14:40] <Saviq> or, had
[14:42] <Saviq> mzanetti, not sure where you have the older libandroid-properties1 from, but I'd say you also have some package pinning going on, check /etc/apt/preferences.d
[14:43] <mzanetti> yeah... making some progress now
[14:43] <Saviq> mzanetti, you probably didn't purge stable-phone-overlay before upgrading to xenial?
[14:43] <mzanetti> nope, I didn't
[14:44] <mzanetti> thought as we dual land all of it should be the same
[14:44] <mzanetti> but with higher version
[14:44] <mzanetti> anyhow... looking better now
[14:45] <mzanetti> wow, saw this for the first time: 502  Server Hangup
[14:45] <Saviq> mzanetti, "we" is the deciding factor here
[14:46] <mzanetti> Saviq, I thought it the second I typed it :D
[14:52] <Trevinho> mzanetti: I'm sorry, I missed your request :)
[14:52] <Trevinho> mzanetti: external screen... Well the shell should work fine per monitor
[14:52] <Trevinho> mzanetti: the problems are the apps, which don't support to be scaled per screen
[16:12] <mterry> @unity is anyone else running xenial seeing an "SSL connection error" message in chromium on google.com domains after updating your system?  -- also, if this is a real problem: beware of updating your system  :)
[16:13] <mzanetti> mterry, just updated today
[16:13] <mzanetti> have not seen this issue on our hangout before
[16:13] <mterry> mzanetti, so you can go to google.com just fine?
[16:14] <mzanetti> yes
[16:14] <mzanetti> seems you've got a man in the middle there ;)
[16:15] <mterry> mzanetti, :-/  well on the plus side it's only me.  On the down side, it's only me and I have to figure it out
[16:38] <tsdgeos> cimi: https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/focusPassesFromChildToParent/+merge/277962 seems to fix the bug
[16:39] <cimi> tsdgeos, great!
[16:39] <tsdgeos> you should be able to use http://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-vivid-armhf-ci/1276/artifact/work/output/*zip*/output.zip to test while we wait for it to land on the overlay