[05:44] <ian8254> Does anyone know why global menus aren't working with firefox on a new kubuntu 20.04 installation? I had it working previously on the same machine with KDE installed on mint 19.3.
[05:46] <user|62084> how to disable default startup applications like python3
[06:23] <linux_> Hi, does anyone know how to fix wine crashing everytime I install an application?
[06:31] <diogenes_> linux_, what app?
[06:53] <linux_> diogenes, I am trying to install an exe app of an organisation and wine seems to crash everytime while creating a virtual space and this is not just for a specific app, it happens for exe applications
[06:54] <diogenes_> linux_, try it in terminal and see what error it shows.
[06:56] <linux_> https://paste.ubuntu.com/p/k9xDt4ZCRh/
[06:56] <linux_> here is the terminal paste
[06:56] <lordievader> Good morning
[07:00] <gnoob> does this help https://forum.winehq.org/viewtopic.php?t=30818
[07:01] <gnoob> seem to be some sort of incompatibility between 64 and 32 bit.
[07:04] <gnoob> my guess would be something wrong with your install of wine.  https://linuxconfig.org/install-wine-on-ubuntu-20-04-focal-fossa-linux    might help too.
[07:05] <linux_> gnoob, yea seems like I am not able to create a x64 virtual drive for some reason. I just looked at your link and tried creating a x86 virtual drive and it worked.
[07:05] <linux_> wine was installed as part of playonlinux package from discover store.
[07:10] <gnoob> probably can't hut to also follow that 2nd guide
[07:11] <gnoob> but I am not a guru or anything.
[07:11] <linux_> gnoob, thank you so much. The link  https://linuxconfig.org/install-wine-on-ubuntu-20-04-focal-fossa-linux shows I also need to install wine64 for x64 virtual drive which doesn't come by default with playonlinux
[07:12] <linux_> Installed wine64 and it just works now
[07:12] <gnoob> :), I just searched what was on your pastebin
[07:12] <gnoob> the error at the bottom.
[07:12] <gnoob> linux_: glad I could help however.
[07:13] <linux_> Yeah I tried the same before and couldn't find a solution. Thank you for taking the time to help me out :)
 Gnoob :')
 Funny nick
[11:44] <BluesKaj> Howdy all
[12:17] <manjaro-web|51> hello, I couldn't turn off my nvidia gpu in kubuntu even by installing nvidia driver
[12:20] <BluesKaj> is the nvidia gpu a dedicated pci card?
[12:22] <BluesKaj> if so you should be able to choose which gpu you want to use in the uefi/bios
[13:12] <Gamertoc> Hey guys, got a weird issue lately. (btw I'm running Ubuntu 20.04 with KDE Plasma) So I sent my PC to sleep once with a few applications open so I could come back to them later, obviously. Since then, every time I start/restart my PC, those same applications are opened again, which is quite annoying. I have no idea on where this comes from or how
[13:12] <Gamertoc> to fix it
[13:19] <ksyd> Gamertoc: I'm far from an expert but maybe it's because in your settings Restore previous session is enabled?
[13:19] <Gamertoc> I'll check
[13:20] <Gamertoc> Indeed, that one was enabled. I'll try again to see if it works now :D
[13:21] <ksyd> In my case I set it to "Start with an empty session" and for Deafult Leave Option: "Turn off computer"
[13:22] <Gamertoc> ksyd it worked, thank you! :D
[13:23] <ksyd> Wow, I'm glad it worked. :)
[13:23] <deww> Gamertoc: \o/
[14:52] <jimmyorrea> Hey guys, just got a quick question... im running an old laptop, and im using ubuntu gnome on it.... was thinking of switching to kubuntu so it would get faster but wanted to tweak plasma to a more macos look, will that still make my laptop slow and is switching from gnome to plasma gonna make it faster? thanx guys
[14:54] <jimmyorrea> i know that lubuntu and xubuntu are actually what i need, but i was hoping maybe kde didnt slow my laptop down
 What are your specs?
[14:55] <jimmyorrea> well its a ideapad s205 with 1.5 gb ram and an AMD e450 apu processor
[14:56] <jimmyorrea> its got 500gb storage
[14:59] <BluesKaj> kde/plasma on 1.5 gb ram will be rather slow, lubuntu and xubuntu are better choices for that laptop
[15:00] <BluesKaj> jimmyorrea,^
[15:01] <jimmyorrea> yeah, i was aware, i was just in denial hehehe, i appreciate the help, thankx
[15:02] <BluesKaj> jimmyorrea, the recommended minimum for kde/plasma is 4GB RAM, and most likely a faster cpu
[15:02] <jimmyorrea> damn
[15:02] <jimmyorrea> yeah, thanks i was just thinking since ive gotten used to gnome being so slow, maybe kde was gonna be a bit faster
[15:03] <jimmyorrea> thanx anyways guys, think imma switch to lubuntu instead
 Mm lubuntu is a great choice. I would definitely try it. You could also have tried kubuntu with all the desktop effects off to see if that's better
[15:04] <BluesKaj> jimmyorrea, I haven't used gnome for many yrs, but according to reports kde/plasma needs a bit more firepower than gnome since it's so flexible with a lot of default apps
 But that would be a painful experience anyway on that cpu
 Gnome it's much slower than kde.. At least talkin about graphics and desktop experience. I tried that on my core2duo and it was slow. Kde was so much better but I did not try ubuntu 20.. Talking about 19.10
 Maybe it has improved
[15:08] <jimmyorrea> hey cool to know, ive decided to go ith lubuntu and look for a macos feel to it, im sure ill find one, thanx guys
 Maybe you can also install kde plasma on lubuntu someday
 If you get tired of your de
 Good luck with lubuntu :)
 @DarinMiller
 @DarinMiller, This doesn't help
[16:08] <analogical> in k3b how do I save the project as an ISO instead of burning it??
 Hi, is it possible to install the ISO groovy-desktop-amd64.iso from usb?
 because i can't get it to start normally from usb
 probably, you just need to make a bootable USB stick from that
 unfortunately with this ISO the pendrive boot doesn't work, it switches directly to the system boot. I tried with Fedora image writer and with balenaEtcher
 With any other distro it works properly
 With Rufus, boot correctly 😍
 Okay that's weird. Although i don't create boot able usb sticks anymore when i have isos as i have an isoloader hdd-case
[18:14] <fcanela2> Hello. I suppose tons of people have already asked today but I am unable to find information elsewhere
[18:14] <fcanela2> When can be Kubuntu 20.04.1 expected?
 It’s already out
[18:15] <fcanela2> Weird. The official download page (https://kubuntu.org/getkubuntu/) mentions Kubuntu 20.04 LTS, without any details regarding the Point Release
[18:15] <fcanela2> and it states the point release clearly for the Kubuntu 18.04.4 LTS version
[18:15] <fcanela2> Thanks, @ItzSwirlz
[18:16] <fcanela2> Humf. The image I am downloading have no .1 in the filename. Where can the point release be found?
[18:17] <RikMills> fcanela2: it is expected when the Ubutnu release team announce it for all flavours
[18:17] <fcanela2> Nevermind, I found it :)  http://cdimage.ubuntu.com/kubuntu/releases/20.04.1/
[18:18] <RikMills> ISO obviously need to sync to all mirrors before that announcement goes out ;)
[18:18] <fcanela2> Should I wait then, RikMills? Thanks for the info, btw
[18:18] <fcanela2> Then I will wait to avoid taking bandwidth from servers
[18:18] <RikMills> that would be appreciated...
[18:19] <fcanela2> I will download the torrent and let it seeding instead. Thanks a lot for the info!
[18:19] <RikMills> np :)
[20:01] <Roey> hi
[20:01] <Roey> anyone hre know about Zoom?
[20:05] <diogenes_> Roey, ask.
[20:05] <Roey> yeah, I'm trying to figure out why it is stalling on me.
[20:05] <Roey> I open it, I clicked on New Meeting, and I just see a window saying "Connecting:"
[20:05] <Roey> n othing past that
[20:06] <diogenes_> Roey, maybe you have a firewall?
[20:06] <Roey> it's not that
[20:07] <Roey> I changed nohting from having used Zoom yesterday, and yet today it refuses to run correctly.
[20:08] <diogenes_> any system updates?
[20:08] <Roey> I rebooted since then
[20:08] <Roey> hmm i wish zoom devs were online and accesible somwhere
[20:11] <Roey> and also
[20:11] <Roey> for some reason Youtube is stuck waiting when I hit Play.. I htink it may be connected to my audio somehow
[20:14] <diogenes_> Roey, you could try a different DNS.
[20:18] <Roey> why dns, diogenes_? like, what gives you the impression that it's timing out waiting for dns, maybe?
[20:20] <diogenes_> Roey, because i had a similar problem of slow loading videos and i change the DNS so no more issues.
[20:21] <Roey> diogenes_: ahhhhh
[20:22] <Roey> hrmmm how can I check what my current DNS is? in /etc/resolv.conf it just points to "nameserver <IP_ADDRESS>"
[20:22] <Roey> diogenes_: ok, I re-wrote resolv.conf with a backup of it I keep that is configured to openDNS
[20:23] <diogenes_> Roey, re-writing resolv.conf won't help.
[20:24] <Roey> then wha twill/
[20:24] <Roey> I mean yeah it'll get overwritten at some point automatically
[20:24] <diogenes_> it's not even applied.
[20:25] <diogenes_> https://www.addictivetips.com/ubuntu-linux-tips/change-dns-settings-on-linux/
[20:26] <diogenes_> scroll down to KDE.
[20:27] <diogenes_> i suggest <IP_ADDRESS>,<IP_ADDRESS>
[20:27] <Roey> ok
[20:27] <Roey> I mean I use openDNS specifically
[20:27] <Roey> and not google, if that's what you were suggesting
[20:28] <diogenes_> no, i suggested cloudflare.
[20:29] <Roey> oh, ok.
[21:40] <Roey> hello
[21:40] <Roey> why is it that when I do "pavucontrol", it just tells me "establishing connection to PulseAudio; please wait"?
[21:46] <Roey> and why can't my system connect to my Bluetooth BOSE SoundlinkIII speaker?


[00:22] <OvenWerks> zequence: which version does the about box say?
[00:54] <zequence> OvenWerks: I forget the version. It's on 15.10, which I haven't updated for a while, but I doubt there's been new uploads for ardour on that release
[00:54] <zequence> Ah, let me check with rmadison
[00:55] <zequence> 4.1~dfsg-1build2
[00:55] <zequence> I'll be upgrading to xenial soon
[00:55] <zequence> 4.6 already
[01:22] <OvenWerks> zequence: I do seem to remember a memory leak that was fixed within the past 3 or 4 months.
[11:36] <zequence> OvenWerks: Ok, cool. There are a few other bugs, which don't cause me too much problems, like when adding tracks, they don't always end up where they are supposed and I have to move them down usually
[11:37] <zequence> I've started to do some sidechaining, and though it works, I have a feeling there is something goofy going on with connections, but again, earlier ardour version
[11:37] <zequence> Should upgrade and have a look
[15:38] <zequence> I've set up the stagin site at http://ubuntustudio.zequence.net.
[15:39] <cfhowlett> ???
[15:39] <zequence> cfhowlett: It's for the theme that knome has been working on
[15:39] <zequence> We'll look at if we can use it for Ubuntu Studio
[15:40] <cfhowlett> OK.  but! !!
[15:40] <zequence> I'm going to switch to it just in a moment
[15:40] <cfhowlett> Officially, is it Ubuntu Studio or Ubuntustudio?
[15:40] <zequence> cfhowlett: Nothing decided yet. We just want to check it out
[15:40] <zequence> It's Ubuntu Studio. But, the terminal version would be ubuntustudio
[15:41] <cfhowlett> color me confused ...
[15:41] <cfhowlett> cause the wordmarks contradict that
[15:41] <zequence> How is that?
[15:41] <cfhowlett> ubuntustudio
[15:42] <zequence> There have been several variants of the wordmark over the years, and that's jsut playing with graphics
[15:43] <cfhowlett> zequence, agreed, but I thought the whole purpose of the recent redesign was to establish a definitive brand
[15:45] <zequence> Well, it's our latest definitive brand. And it looks good IMO
[15:45] <cfhowlett> agreed.  so then ... Ubuntu Studio ?? not to nitpick but am I missing something here?
[15:46] <zequence> The word Studio is clearly apart from Ubuntu in the graphics where Studio is fatter
[15:46] <zequence> So, I don't read it as ubuntustudio
[15:46] <zequence> I read it as ubuntu STUDIO
[15:46] <cfhowlett> ... ok
[15:46] <zequence> Similar to Ubuntu Gnome https://ubuntugnome.org/
[15:47] <zequence> Zak reduced the distance between the letters to make it look better
[15:53] <zequence> I switched themes, and adapted the theme to use our official blue instead of the Ubuntu orange
[15:53] <zequence> Now, what would be cool is to make it dark
[15:53] <zequence> knome: Nice work on the theme!
[22:16] <cub> I made some updates to the test site http://ubuntustudio.zequence.net/ Next step should be to set up a child theme and try out some colouring
[23:02] <knome> zequence, for all of you dark theme loving folks (including cub who quit very fast), i have pushed a new revision of the theme to github with a dark theme variant - this can be enabled from the customizer
[23:05] <OvenWerks> knome: I think cub reads the back scroll from the archives anyway.


[06:13] <tvoss> Saviq, ping
[07:03] <Saviq> tvoss_, pong
[07:12] <mzanetti> o/
[07:20] <Saviq> mzanetti, \o
[07:20] <Saviq> tsdgeos, \o
[07:25] <mzanetti> Saviq: how are things?
[07:25] <mzanetti> Saviq: any news I should know of?
[07:25] <Saviq> mzanetti, we're not releasing until we got integration tests in a better state
[07:26] <Saviq> mzanetti, which https://code.launchpad.net/~autopilot/unity8/autopilot-test-refactoring/+merge/175452 is aiming at
[07:26] <mzanetti> Saviq: right... just checked out the autopilot-refactor branch
[07:26] <mzanetti> Saviq: doesn't really work at all here
[07:27] <Saviq> mzanetti, but it still fails in Nexus10 scenario on Jenkins
[07:27] <Saviq> I'm about to test on maguro
[07:27] <mzanetti> Saviq: it completely fails here on my desktop
[07:27] <tsdgeos> Saviq: o/
[07:27] <mzanetti> but I guess that's subject for the meeting now anyways
[07:29] <Saviq> indeed
[07:30] <Saviq> mzanetti, you're joining, right?
[07:31] <Saviq> mzanetti, ooh, bad network?
[07:43] <tsdgeos> oh man, gmail marked kgunn's mail as spam
[07:48] <mzanetti> Wellark: ping
[07:49] <Saviq> veebers, I wonder if you should try the timeout thing in a VM detached from Jenkins
[07:49] <Saviq> veebers, rather than wait for the whole job to finish
[07:49] <tsdgeos> meh calum left :-/
[07:50] <Cimi> Saviq, forgot what I promised being on my plate for today...
[07:50] <Cimi> Saviq, apart of the scrollbars check
[07:50] <Saviq> tsdgeos, yeah :|
[07:50] <Cimi> the holiday worked :D
[07:50] <Cimi> brain cleared
[07:50] <Cimi> haha
[07:51] <Saviq> veebers, here are the failures I get on the VM http://pastebin.ubuntu.com/5899725/
[07:51] <Saviq> veebers, feel ap-internal
[07:51] <Cimi> there's a branch to fix
[07:51] <veebers> Saviq: I understand the pastebin, but not your second comment?
[07:52] <Saviq> veebers, that failure seems autopilot-internal
[07:52] <Cimi> Saviq, https://code.launchpad.net/~unity-team/unity8/unity8.background_gsettings/+merge/174958
[07:52] <veebers> Saviq: ah gotcha, yeah it's interesting
[07:52] <Saviq> veebers, http://pastebin.ubuntu.com/5899727/ here's one more
[07:52] <Cimi> Saviq, with 'gsettings mock' you mean I need a fake gsettings panel that sets that?
[07:52] <Saviq> Cimi, they're random
[07:52] <Cimi> *plugin
[07:53] <Saviq> Cimi, yeah, should be doable in QML
[07:53] <Cimi> Saviq, I'll create a GSettings component then
[07:53] <Saviq> Cimi, yeah it feels like it's enough for it to just be a QtObject, really
[07:53] <Cimi> Saviq, but how will it override the import GSettings 1.0?
[07:53] <Saviq> with some props
[07:54] <Saviq> Cimi, like everything else does?
[07:54] <Saviq> Cimi, we have mock/fake plugins for almost all the interfaces we use already
[07:54] <Cimi> it's monday morning and brain it currently empty
[07:54] <Cimi> as well as my stomach
[07:55] <veebers> hmm Saviq, with those logs  you didn't see any evidence that Unity8 crashed (or anything else for that matter)?
[07:55] <Saviq> veebers, nothing that autopilot reported back for me
[07:56] <Saviq> veebers, it seemed like it was just killed by autopilot
[07:56] <Saviq> veebers, but anyway - that's low prio
[07:56] <veebers> Saviq: hmm, alright understood
[07:56] <Saviq> veebers, shall we detach a VM for you to debug the timeout?
[07:56] <veebers> Saviq: not right now, but soon would be a good idea
[07:58] <Saviq> veebers, ok cheers
[07:58] <Saviq> mzanetti, tsdgeos will you guys write a trip report for QtCS?
[07:58] <tsdgeos> that's the plan
[08:00] <mzanetti> Saviq: yep
[08:00] <Saviq> cool
[08:00] <veebers> Saviq: odd, I'm not seeing the grid px unit issue on my galaxy nexus
[08:01] <mzanetti> Saviq: is there any template we need to use or is it just a free form text?
[08:01] <Saviq> mzanetti, free-form I'd say
[08:01]  * mzanetti gets started before today's afternoon beer wipes memories
[08:02] <Saviq> veebers, hum, so when you run the tests everything looks fine?
[08:02] <veebers> Saviq: yes
[08:02] <Saviq> veebers, can you send me your unity8-autopilot .deb?
[08:02] <Saviq> dednick, indicators-client doesn't work on device (no input), any idea?
[08:02] <mzanetti> Saviq: a btw. today is a sort of town-wide public holiday where everyone living here in Ulm takes a self-build boat, a huge amount of beer and swims down the river Danube. Can't miss that one, so I'll be awayas of 3pm
[08:02] <veebers> Saviq: hmm, that could be interesting, I was just running the tests from source. Building now to test
[08:03] <dednick> Saviq: i was using it on friday :/
[08:03] <Saviq> dednick, hmm let me check some things out
[08:03] <dednick> Saviq: I needed to kill unity8 though
[08:03] <Saviq> dednick, a --desktop_file_hint to any .desktop file would've sufficed
[08:04] <dednick> Saviq: ah. i tried, but couldnt get it working. didnt know about that command line.
[08:04] <Saviq> mzanetti, don't drown! (unless it's beer)
[08:04] <Saviq> dednick, but anyway, I'm trying with unity8 stopped, too
[08:05] <Saviq> dednick, hmm completely no input...
[08:05] <dednick> Saviq: let me give it another go
[08:06] <tsdgeos> oh noes
[08:06] <tsdgeos> someone dumbed down the unity sound indicator :-/
[08:06]  * Saviq reflashes
[08:06] <tsdgeos> can't use the mouse wheel on it anymore
[08:06]  * tsdgeos shakes fist
[08:07] <mzanetti> Saviq: http://tinyurl.com/jw33wwn :D
[08:07] <dednick> Saviq: device out of juice. give me a few minutes :)
[08:07] <Saviq> mzanetti, ok, no drowning there ;)
[08:07] <mzanetti> hehe
[08:07] <Saviq> dednick, k, I'll reflash in the mean time
[08:10] <Saviq> Cimi, moving to CrossFadeImage from SDK was the only task for you I could find in my logs
[08:12] <veebers> Saviq: who would I talk to about detaching a VM so I can have a poke around without interrupting people? (and not having to wait for the whole CI process)
[08:12] <Saviq> mzanetti, can you ↑?
[08:13] <mzanetti> Saviq: sure
[08:13] <mzanetti> veebers: I think you can do that yourself too actually
[08:13] <mzanetti> veebers: go to Manage Jenkins -> Nodes -> pick the node you want and click "Mark this node temporary offline"
[08:13] <veebers> mzanetti: ah ok, err do you mind pointing me in the right direction?
[08:13] <mzanetti> veebers: leave a short comment on why you detached it
[08:14] <mzanetti> veebers: once you have that, log in to naartjie via ssh
[08:14] <mhr3> Saviq, tiny fix https://code.launchpad.net/~mhr3/unity8/scopes-real-category-ids/+merge/176139
[08:14] <veebers> mzanetti: alright, am I able to ssh into the machine as per normal?
[08:14] <veebers> mzanetti: ah ok and then from there into the vm?
[08:14] <mzanetti> veebers: from there you can ssh to the vm's using their hostnames
[08:14] <mzanetti> veebers: if the vm is not running use "virsh start ps-saucy-server-<arch>-<id>"
[08:14] <veebers> mzanetti: would I duplicate what I see in the job config for starting X etc. so i can launch things (namely unity8) to test?
[08:15] <mzanetti> veebers: use "virsh list" to see if its running or not
[08:15] <veebers> mzanetti: awesome cheers
[08:15] <Saviq> mhr3, thanks
[08:15] <mzanetti> veebers: yeah, copy/paste the whole job script into the shell and you're set up
[08:15] <veebers> mzanetti: awesome, thanks
[08:15] <Saviq> tsdgeos, btw http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/122
[08:16] <mzanetti> veebers: you need to copy/paste parts of it as the paste buffer might get cleared during long-lasting things like apt-get update
[08:16] <veebers> mzanetti: sure, thanks for the heads up
[08:17] <veebers> Saviq: ugh, I'm getting this error trying to build the package: http://pastebin.ubuntu.com/5899765/
[08:17] <tsdgeos> Saviq: yep seen it
[08:17] <mhr3> jibel, ping? could you run http://paste.ubuntu.com/5899763/ on the memusage.log files when testing finishes?
[08:17] <Saviq> veebers, looks like some apt failure
[08:17] <Saviq> veebers, those are distro packages
[08:17] <mhr3> jibel, will produce a nice graph ;)
[08:18] <tsdgeos> Saviq: not really sure it's a correct fix though
[08:18] <Saviq> tsdgeos, we weren't sure whether that was the correct fix :)
[08:18] <Saviq> tsdgeos, right
[08:18] <Saviq> ;)
[08:18] <Cimi> Saviq, indeed will work on that
[08:18] <tsdgeos> i had thought that m_firstVisibleIndex would had been -1 when nothing is in the view
[08:19] <Cimi> tummy is satisfied now, had to grab a sandwich
[08:19] <Saviq> Cimi, too many details ;)
[08:19] <Cimi> lol
[08:19] <jibel> mhr3, sure, could you file a bug against otto, (https://bugs.launchpad.net/otto) ?
[08:20] <veebers> Saviq: bah, why's it failing on those packges all of a sudden. Will investigate
[08:22] <sil2100> mhr3: hello!
[08:22] <mhr3> jibel, https://bugs.launchpad.net/otto/+bug/1203650
[08:22] <mhr3> sil2100, hey
[08:23] <sil2100> mhr3: so, we have some unity results - on one machine we got a timeout and the test run failed (due to dbus issues?), but the second one looks pretty ok
[08:23] <sil2100> mhr3: since the other one has only 17 failures
[08:24] <mhr3> mardy_, do you do dbus-test-runner reviews? if you do - https://code.launchpad.net/~mhr3/dbus-test-runner/watch-pipes-for-hup/+merge/176092 pls ;)
[08:24] <tsdgeos> what provides unity-shell-launcher=2 ?
[08:24] <Saviq> Wellark, HUD stuck here again
[08:24] <mhr3> sil2100, there shouldn't be any dbus issues anymore
[08:25] <sil2100> mhr3: so I wonder why we had that timeout on one machine
[08:25] <Saviq> tsdgeos, unity-api-dev
[08:25] <Saviq> tsdgeos, from ppa:ubuntu-unity/next
[08:25] <Saviq> tsdgeos, ./build -s; ./build -c
[08:25] <mhr3> sil2100, maybe compiz crashed?
[08:25] <Saviq> Wellark, http://pastebin.ubuntu.com/5899782/
[08:25] <tsdgeos> Saviq: ah, forgot about the -s
[08:25] <tsdgeos> had done -c only
[08:25] <didrocks> Saviq: if people are not going to hack on it, better that they install the package :)
[08:26] <didrocks> Saviq: or even run bzr bd directly
[08:26] <Saviq> didrocks, not sure what you mean?
[08:26] <mhr3> sil2100, are we talking about this? http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/554/label=autopilot-ati/console
[08:26] <Saviq> didrocks, ./build in unity8 goes mk-build-deps
[08:26] <Saviq> didrocks, we're not building nothing locally anymore
[08:26] <didrocks> Saviq: ah ok, I thought you meant from unity-api-dev
[08:27] <sil2100> mhr3: yes, I see that suddenly unity.tests.test_dash.PreviewInvocationTests.test_home_scope_lmb_app started and did not finish
[08:27] <Saviq> didrocks, nah
[08:27] <didrocks> Saviq: great! the unity 7 team got bitten by that a lot :)
[08:27] <sil2100> (no video of that)
[08:27] <didrocks> (like stuff stil in usr/local :p)
[08:28] <veebers> Saviq: what process do you use to produce unity8 debs on your machine?
[08:29]  * mhr3 looks at what the test does
[08:29] <Saviq> veebers, bzr bd
[08:29] <Saviq> veebers, for armhf pbuilder or on device itself
[08:30] <Saviq> veebers, locally sbuild, too
[08:30] <veebers> Saviq: cool thanks, my pdebuilder is giving me that apt issues, so I may build on the device
[08:30] <Saviq> veebers, here's one more interesting one... http://pastebin.ubuntu.com/5899803/
[08:31] <sil2100> mhr3: so I've been wondering if that's a real regression causing this problem, or maybe some temporary failure that we can ignore
[08:31] <veebers> Saviq: hmm, I'm certain I've seen/heard of something similar before. I believe a workaround is to do: export LANG=C
[08:32] <Saviq> veebers, yeah, I did that
[08:33] <Saviq> veebers, and yeah, it helps
[08:33] <mhr3> sil2100, the whole ati testing is weird, ap started 5:20 and still wasn't finished at 6:53
[08:33] <mhr3> sil2100, i suspect compiz crashes
[08:33] <Saviq> dednick, hmm works on the current image, /me tries on pending
[08:34] <mhr3> sil2100, ie it's not one mishaving test that blocked everything, the whole collection of them took too long
[08:34] <dednick> Saviq: do the menus show any content? I get input, but no content in menus. showing "empty"
[08:34] <sil2100> mhr3: there also seems to be much much more failing tests there than in the intel machine
[08:35] <Saviq> dednick, yeah
[08:35] <Saviq> dednick, but that's probably unity8 conflicting
[08:35] <dednick> Saviq: probably.
[08:37] <Saviq> dednick, hmm or not
[08:38] <Saviq> dednick, I « chmod -x `which unity8`; pkill unity8 », as session upstart is b0rked in current
[08:38] <dednick> Saviq: definately had it working before i flashed with upstart image.
[08:38] <mhr3> sil2100, they're probably real failures then
[08:38] <Saviq> dednick, and still empty
[08:38]  * Saviq flashes current now
[08:38] <Saviq> s/current/pending/
[08:38] <sil2100> mhr3: let's maybe re-run the tests then to see how it goes
[08:38] <mhr3> sil2100, i don't think anything will change really
[08:39] <sil2100> mhr3: it's strange though that intel was fine
[08:39] <mardy_> mhr3: I don't, but I could try :-)
[08:40] <sil2100> mhr3: in any case, we need someone assigned to deal with this issue, if it's a real regression as you say it is - Trevinho?
[08:40] <dednick> sigh. really need to add a back button to that indicator-client app.
[08:41] <mardy_> mhr3: oh! "Lastly, don't print empty line after each received line from the process tasks. :)" this alone is a reason to approve your MR! :-D
[08:41] <Cimi> guys I think since we removed android
[08:41] <Cimi> my phone power button doesn't seem to work well
[08:42] <Cimi> I have to remove battery to turn it on
[08:42] <Cimi> or it doesn't power off
[08:43] <dednick> Saviq: i think the indicators are stopped when unity stops :(
[08:43] <dednick> mine aren't running anyway
[08:44] <Saviq> dednick, ugh, right, upstart?
[08:44] <dednick> Saviq: i wouldnt have thought so because most of them run from dbus service i think. unless we stop dbus as well.
[08:45] <Saviq> dednick, yeah but we're walking away from dbus activation, afaik
[08:45] <dednick> Saviq: new indicators are.
[08:46] <dednick> Saviq: phone still on old system i think.
[08:46] <Saviq> dednick, mhm
[08:46] <pete-woods1> Saviq: just remembered, I made the libusermetrics initialisation asynchronous now - version 1.0.9 has it
[08:46] <Saviq> pete-woods, cool!
[08:47] <Saviq> dednick, hmm, I `stop unity8`'d on pending
[08:47] <Saviq> dednick, all the services seem to be running still
[08:48] <dednick> Saviq: i restarted phone with -x unity8.
[08:48] <Saviq> dednick, right, so they never got started in your case
[08:49] <Saviq> dednick, yeah, but on current they don't get input at all
[08:49] <dednick> Saviq: as in no touch?
[08:49] <Saviq> dednick, yeah
[08:50] <dednick> Saviq: weird
[08:50] <Saviq> I wonder if the fix to ubuntuappmanager caused that...
[08:50] <dednick> Saviq: presumably other apps ok started from command line --desktop_file_hint ?
[08:51] <Saviq> dednick, actually not
[08:52] <dednick> Saviq: good news for me. bad for app manager
[08:52] <Saviq> yeah
[08:54] <Saviq> dednick, hrmpf.... I seem to have no input at all...
[08:54] <Saviq> dednick, in apps, that is
[08:56] <Saviq> dednick, seems my maguro is b0rked (I wonder if image-based upgrades did that to me)
[08:58] <mhr3> mardy_, ;)
[08:58] <mhr3> sil2100, maybe there's something with x and ati in s?
[08:59] <mhr3> sil2100, i did see in the last couple of runs in the videos that compiz crashed there from time to time
[08:59] <dednick> Saviq: ok, i'll try pending now and see if i can confirm
[09:00] <sil2100> mhr3: do you know who's responsible for compiz maintainance right now?
[09:01] <mhr3> sil2100, stephen's team
[09:01] <mhr3> it didn't change
[09:02] <mhr3> sil2100, do you have time for a quick chat?
[09:03] <sil2100> mhr3: what's up?
[09:04] <mhr3> sil2100, i mean with audio&video :)
[09:04] <Saviq> dednick, seems restarting unity8 makes input fail for apps...
[09:04] <sil2100> mhr3: can we hang out in 30 minutes? ;)
[09:04] <dednick> Saviq: oops
[09:04] <mhr3> sil2100, ok
[09:07] <Saviq> dednick, hrmpf, now it's working fine...
[09:07] <mhr3> mardy_, pushed btw
[09:08] <dednick> Saviq: hm. damn inconsistent bugs. just waiting for mine to finish flashing.
[09:12] <Saviq> dednick, the slider test needs fixing anyway, gets stuck at the slider going back and forth indefinitely
[09:24] <Saviq> tsdgeos, thanks for answering on the ML ;)
[09:25] <tsdgeos> sure, that's why we have ML, no? :D
[09:26] <Saviq> tsdgeos, yeah, we've taken care of it over IRC, but good to have a response there anyway
[09:28] <Saviq> veebers, btw, on manta I get four failures like so http://pastebin.ubuntu.com/5899914/
[09:28] <Saviq> veebers, but grid unit seems to be fine somehow...
[09:29] <veebers> Saviq: did it swipe too far or similar?
[09:29] <Saviq> veebers, running again
[09:29] <Saviq> veebers, I think it was grid units' fault
[09:29] <veebers> Saviq: perhaps I missed something subtle with that when moving the calculation wrong
[09:30] <Saviq> veebers, because it was at bad gu before
[09:30] <Saviq> veebers, yeah, now it completed OK
[09:30] <Saviq> veebers, ah, I *think* the indicators client fook up the grid unit
[09:31] <veebers> Saviq: ah ok
[09:31] <Saviq> veebers, if I only run the unity8 ones it's fine
[09:31] <veebers> Saviq: oh fyi I've had to bump up the timeout to 40sec to get the Nexus 10 desktop tests to pass (just running more now)
[09:31] <Saviq> veebers, yeah, so you need to have a look at the indicator_client ones to not set gu if !Desktop
[09:32] <Saviq> veebers, ugh
[09:32] <Saviq> veebers, at least it's fine on devices
[09:32] <veebers> Saviq: perhaps we need to update the indicator tests to use the refactored code
[09:32] <Saviq> veebers, yeah, exactly
[09:32] <veebers> Saviq: yep, I'll look into getting the ci running on the device tomorrow too
[09:33] <Saviq> veebers, yeah, they'll be run in image smoke testing anyway
[09:33] <Cimi> do you guys have the problem above ^^
[09:33] <Saviq> veebers, please just let us know when should we take over, then
[09:34] <veebers> Saviq: I'll have a look at the indicators stuff now, will me changing it screw things up for dednick ? or perhaps cause merge conflicts in trunk (or vise versa)
[09:34] <Cimi> power button not really working as before, sometimes the phone doesn't turn on or off?
[09:34] <Saviq> veebers, not that I know of
[09:34] <veebers> Saviq, dednick: is dednick actively working on those tests in trunk?
[09:34] <Cimi> it gets stuck into charging mode
[09:34] <Saviq> veebers, I don't think that he is
[09:38] <veebers> Saviq: cool thanks
[09:38] <Saviq> veebers, confirmed - "autopilot run unity8.shell" completes on both maguro and manta
[09:39] <veebers> Saviq: cool, so no grid px issue. I'm just running the tests on the VM with the new timeout to see how the run, while that's running I'm just looking at what needs to happen w/ the indicators test
[09:39] <Saviq> veebers, awesome!
[09:43] <veebers> Saviq: just read backlog (and email) if, for the nexus 10 desktop scenarios, it's still not loading the Home dash screen, then we will have failures there
[09:43] <Saviq> veebers, it is
[09:43] <Saviq> veebers, the fix is in trunk
[09:43] <Saviq> s/fix/workaround/
[09:43] <veebers> Saviq: ah cool, I'll make sure that's merged in
[09:52] <mzanetti> Saviq: trip report written in case you're interested
[09:52] <Saviq> mzanetti, cheers!
[09:55] <Saviq> dednick, whoa, tricky - input in ubuntuappmanager gets stuck if no app was launched in the shell prior to killing it
[09:56] <Saviq> dednick, if you launch an app *before* starting shell, or start one *in* shell, everything will be fine
[09:56] <Saviq> dednick, but if unity8 starts, stops, and *then* an app is launched - input is lost for them
[09:56] <Saviq> forever in a ubuntuappmanager run, that is
[09:58] <dednick> Saviq: hm. dodgey
[10:00] <Saviq> dednick, indeed
[10:04] <Saviq> dednick, can you confirm bug  #203698
[10:04] <Saviq> argh
[10:04] <Saviq> dednick, can you confirm bug  #1203698
[10:05] <dednick> Saviq: sure. give me a sec to reproduce.
[10:05] <Saviq> dednick, yup, that's what I meant :)
[10:10] <Cimi> Saviq, shall I create a tst_Shell then?
[10:10] <dednick> Saviq: hm. my device just got wiped with last update.
[10:10] <dednick> pending i mean
[10:10] <Saviq> Cimi, there is one by dandrader already
[10:11] <Saviq> Cimi, https://code.launchpad.net/~dandrader/unity8/runningApps_lp1193419/+merge/175955
[10:12] <Cimi> Saviq, ok I'll merge this
[10:15] <dednick> Saviq: confirmed
[10:15] <Saviq> dednick, thanks
[10:20] <veebers> Saviq: is this correct, I'm seeing for the test 'test_can_unlock_passphrase_screen' the unity8 log output: responding "PASSWORD" false (and the test fails)
[10:21] <Saviq> veebers, caps lock?
[10:21] <Saviq> veebers, should be lowercase
[10:21] <veebers> Saviq: hmm, interesting
[10:26] <veebers> Saviq: ah, I think it had to do with me kvm-ed in and hitting caps (which is actually my control)
[10:27] <mzanetti> Saviq: is the problem with touch input in autopilot resolved?
[10:27] <Saviq> mzanetti, not all of it
[10:27] <Saviq> mzanetti, just discovered bug #1203698
[10:27] <Saviq> mzanetti, but yeah, the other one is fixed
[10:28] <mzanetti> Saviq: do we know what was/is the issue?
[10:28] <Saviq> mzanetti, which actually probably introduced that one ↑ :/
[10:28] <Saviq> mzanetti, https://code.launchpad.net/~ricmm/platform-api/fix-crasher-on-last-app-dead/+merge/175667
[10:29] <mzanetti> heh...
[11:05] <mhr3> sil2100, https://code.launchpad.net/~mhr3/unity-scope-home/revert-r133/+merge/176157
[11:05] <mhr3> sil2100, and https://code.launchpad.net/~mhr3/unity-lens-applications/revert-351/+merge/176158
[11:08] <mhr3> pete-woods, ping?
[11:09] <pete-woods> mhr3: hi
[11:09] <mhr3> pete-woods, hey, re https://code.launchpad.net/~pete-woods/unity-scope-soundcloud/native-rewrite/+merge/174535/comments/393645 you tested that on unity8, right?
[11:09] <mhr3> (the preview thing)
[11:09] <sil2100> mhr3: reviewing in a sec
[11:09] <pete-woods> mhr3: no, just with unity7 and the scope debug tool thing
[11:10] <mhr3> pete-woods, oh? hmm, then i'll have to take a look, i thought you used unity8, cause it doesn't support music previews yet and uses generic one instead
[11:11] <pete-woods> mhr3: it's probably just something stupid I've done in the preview method, I wasn't totally clear on what I was supposed to do in there
[11:11] <mhr3> pete-woods, the code looks fine
[11:13] <Saviq> veebers, if you're still here, you should not, just give us what you have and we'll take over? unless you really want to pull it through, of course ;)
[11:13] <veebers> Saviq: heh, yeah I'm still here
[11:14] <veebers> Saviq: it appears there is an issue with the indicator tests and autopilot re: the grid unit px
[11:14] <veebers> Saviq: I've just done some debugging and about to put a MP against autopilot too (after running the test suite)
[11:15] <Saviq> veebers, ah, we seem to be hitting all kinds of bugs *everywhere* ;)
[11:15] <Saviq> and here we thought our tests were simply that bad :D
[11:15] <sil2100> jibel: hi, can I bother you for a moment? I noticed something strange in one of the otto runs
[11:15] <veebers> Saviq: I'll push both the timeout update and the indicators fix, but until that autopilot one is merged, if the indicators tests are run it will change it for those in the same run
[11:15] <veebers> Saviq: :-)
[11:18] <Saviq> veebers, cheers, will try and harass someone into merging it today
[11:22] <nic-doffay> Anyone here familiar with the Popover API component?
[11:25] <greyback> thank $DEITY for ppa-purge
[11:26] <mlankhorst> Sarvatt^ :P
[11:29] <sil2100> mhr3: ok, I'm poking jibel right now about it, but it seems that the ati run wasn't even properly archived ;/ So we can't really even check if the compiz crash log was in the ati machine
[11:29] <sil2100> mhr3: but I'll check if intel has it
[11:29] <sil2100> mhr3: since you said it crashed once ;)
[11:29] <mhr3> sil2100, (at least) ;)
[11:29] <sil2100> mhr3: it's taking a while, as it seems it's strangely big, having over 4GB
[11:30] <sil2100> Normally it's much smaller
[11:30] <mhr3> sil2100, what has 4gb?
[11:33] <sil2100> mhr3: the otto FS snapshot diff ;p
[11:33] <mhr3> ah
[11:33] <mhr3> maybe there's lots of crashes :)
[11:45] <lakhan> my menu bar goes on missing how could i resolve this issue.
[11:46] <lakhan> please answer
[12:09] <Saviq> Wellark, ping
[12:32] <Saviq> kgunn, ping
[12:32] <kgunn> Saviq: pong
[12:40] <greyback> kgunn: ping
[12:42] <kgunn> greyback: pong
[12:53] <Saviq> dednick, the indicator battery slider test needs fixing, could you look at it?
[12:53] <Saviq> dednick, starting from branch lp:~autopilot/unity8/autopilot-test-refactoring
[12:53] <Saviq> dednick, we need it to work at a different geometry - it fails on manta
[13:03] <dednick> Saviq: ok
[13:06] <Saviq> dednick, actually it might be enough to just run it with --side_stage_hint=SideStage
[13:07] <Saviq> --stage_hint=SideStage, I meant
[13:07] <Saviq> nvm then
[13:29] <seb128> Saviq, hey, do you know if the touch image is using the standard xdg directories (e.g ~/Photos for gallery), and if there is a qml/qt api to get those?
[13:29] <seb128> Saviq, or who is the person to ask for those infos ;-)
[13:29] <Saviq> seb128, I'm afraid Pictures is hardcoded
[13:29] <Saviq> seb128, gusch will know more
[13:30] <Saviq> seb128, but http://qt-project.org/doc/qt-5.0/qtcore/qstandardpaths.html
[13:31] <Saviq> paulliu, start without me, I'll be right there
[13:31] <seb128> Saviq, excellent, thanks ;-) (I was google for variants around "xdg" and didn't find that one)
[13:45] <Saviq> seb128, cheers
[13:46] <Saviq> dednick, the slider test seems unstable on maguro as well (at least prior to the refactoring branch, which I got fed up with now and backporting only the fixes)
[13:47] <dednick> Saviq: hm. you testing on actual devices?
[13:47] <Saviq> dednick, yes
[13:47] <Saviq> dednick, but you should be able to reproduce with different geometry
[13:47] <dednick> Saviq: but it's not fullscreen.
[13:47] <Saviq> dednick, on devices it is
[13:47] <Saviq> dednick, they don't do anything else
[13:47] <dednick> Saviq: i see.
[13:48] <dednick> Saviq: I've never tested on device.
[13:48] <Saviq> dednick, yeah, that needs to change ;)
[13:50] <Saviq> dednick, but anyway it should be reproducable on desktop, just use the same geometry
[13:54] <dednick> Saviq: unfortunately i dont have a 2560 wide screen :)
[13:55] <dednick> Saviq: but i will give changing geo a try
[13:58] <Saviq> dednick, it should be the same with half the GRID_UNIT_PX
[13:58] <Saviq> unless it's a rounding issue
[14:09] <Cimi> Saviq, how do i create a property with a rule?
[14:09] <Cimi> Saviq, in my case, schema.id
[14:09] <Cimi> was doing with a list model but it's kinda stupid :p
[14:11] <dednick> Saviq: what is the error? i can't get it to fail on desktop
[14:12] <Saviq> Cimi, http://pastebin.ubuntu.com/5900718/
[14:12] <Saviq> dednick, it gets stuck
[14:12] <Saviq> dednick, as in it drags back and forth
[14:12] <Cimi> Saviq, always awesome you are
[14:13] <dednick> Saviq: i c.
[14:13] <Saviq> Cimi, never did that before and there might be a better way, but then again there might not be
[14:13] <Saviq> dednick, let me get you a video
[14:15] <dednick> Saviq: how do you actually run ap on the phone with indicators_client?
[14:15] <didrocks> mzanetti: hey, mind merging https://code.launchpad.net/~mzanetti/cupstream2distro-config/drop-phablet-team-ppa/+merge/169373?
[14:15] <didrocks> (top approving)
[14:15] <didrocks> if things are ready
[14:17] <didrocks> fginther: do you mind looking at merges that are on your side for cu2d-config?
[14:17]  * didrocks tries to clean stuff ;)
[14:18] <didrocks> fginther: there are 4, from you, mmrazik and alesage
[14:18] <fginther> didrocks, no problem, I'll add it to the days list
[14:18] <didrocks> fginther: thanks!
[14:20] <nic-doffay> paulliu, ping
[14:20] <nic-doffay> If you're still around!
[14:22] <paulliu> nic-doffay: hhi
[14:24] <nic-doffay> paulliu, since Pawel's on holiday, do you have any info regarding the filters for me?
[14:24] <nic-doffay> paulliu, see this picture: http://design.ubuntu.com/apps/building-blocks/option-selector
[14:26] <Saviq> dednick, http://pastebin.ubuntu.com/5900759/ should show you the failure
[14:27] <paulliu> nic-doffay: I have no idea right now. But are you based on his filter branch?
[14:28] <nic-doffay> paulliu, yeah
[14:29] <Saviq> dednick, http://ubuntuone.com/7AIixqURu1p5JqPALK7iPm
[14:30] <dednick> Saviq: reproduced already :) thanks
[14:30] <dednick> just needed the ap deps installed
[14:30] <Saviq> dednick, cool
[14:34] <Cimi> Saviq, so I only need a small qml file
[14:35] <Cimi> Saviq, GSettings.qml
[14:35] <Saviq> Cimi, yup
[14:35] <Cimi> Saviq, was wondering how I make it with version
[14:35] <Cimi> so import GSettings 1.0 will get it
[14:35] <Cimi> qmldir?
[14:35] <Cimi> GSettings 1.0 GSettings.qml?
[14:36] <Saviq> module GSettings
[14:36] <Saviq> Cimi, but yup
[14:36] <Saviq> Cimi, very simple
[14:36] <Cimi> ok
[14:37]  * kgunn read mzanetti & tsdgeos reports....and really really really wishes he had more time to play on qt/qml
[14:37] <kgunn> excellent write ups
[14:41] <tsdgeos> kgunn: thanks for the writing compliment :-)
[14:45] <dednick> Saviq: it's the touch device
[14:45] <dednick> *touch input
[14:46] <dednick> Saviq: same thing happens when you switch to touch input on desktop
[14:46] <Saviq> dednick, ah!
[14:47] <Saviq> dednick, wonder if we could get away with mouse for now
[14:48] <dednick> it's really wierd. cursor goes in opposite direction to slider :/
[14:49] <dednick> i'll try mouse on device
[14:49] <Cimi> forgot the command to run just one test?
[14:49] <Cimi> thought it was testCompoennt
[14:50] <Cimi> make testShell doesn't work
[14:50] <Saviq> Cimi, it should
[14:50] <Saviq> Cimi, but you need to build first
[14:50] <Cimi> mmm weird
[14:50] <Cimi> Saviq, I did
[14:50] <Saviq> Cimi, to update the targets
[14:50] <Cimi> oh right
[14:50] <Cimi> I merged daniel branch
[14:50] <Cimi> but didn't rebuild
[14:54] <Saviq> dednick, right, Mouse doesn't work on device...
[14:54] <dednick> Saviq: should probably figure out why it's not working in the first place.
[14:54] <Saviq> dednick, yeah
[14:55] <Saviq> dednick, well, it imports Xlib
[14:55] <Saviq> dednick, so that's why ;)
[14:55] <Saviq> dednick, and we're only doing touch on devices, so it kinda makes sense
[14:55] <dednick> heh
[15:02] <dednick> Saviq: Pointer doesnt suppose drag for Touch device :(
[15:02] <dednick> not properly anyway.
[15:08] <Cimi> dandrader, what's the command to run test for shell?
[15:11] <Saviq> dednick, ok, so whatever we're using for the Hud is working
[15:11] <dednick> Saviq: hud not dragging ;)
[15:18] <Saviq> dednick, what's it do?
[15:19] <Saviq> dednick, "self.touch.drag"...
[15:19] <Saviq> yeah, but _finger_move, too
[15:22] <Saviq> spread the word! http://www.indiegogo.com/projects/ubuntu-edge
[15:30] <dednick> 600. tempting
[15:31] <dednick> Saviq: yeah. the pointer position doesnt update. we rely on it having last location.
[15:32] <dandrader> Cimi, make tryFoo
[15:32] <dandrader> Cimi, and "make testFoo"
[15:33] <dandrader> where "Foo" is the name of the component (e.g. Stage, Launcher, etc
[15:34] <Saviq> dandrader, yeah, he just didn't rebuild so his targets weren't ready
[15:34] <Saviq> nice, $42k done, $31,958k to go
[15:35] <Saviq> lol
[15:35] <kgunn> Saviq: your good for the balance right?
[15:35] <Saviq> kgunn, let me call my bank, k?
[15:35] <Saviq> kgunn, 5 mins
[15:36]  * kgunn folds wallet, places back in hip pocket
[15:36] <Cimi> dandrader, make testShell doesn't seem to work
[15:36] <Cimi> dandrader, no works, sorry was in the wrong dir
[16:01] <Saviq> dednick, will you please file a bug with autopilot
[16:02] <Saviq> dednick, ideally with a small test?
[16:11] <mhr3> sil2100, news on testing?
[16:12] <sil2100> mhr3: was still testing when I last checked, one moment
[16:13] <sil2100> mhr3: ouch, red
[16:13] <sil2100> mhr3: both timeouts... damn
[16:13] <sil2100> mhr3: I'm filling in a bug then
[16:14] <mhr3> sil2100, why is there no autopilot artifacts?
[16:15] <sil2100> mhr3: the logs are strange
[16:16] <sil2100> mhr3: it's as if compiz didn't even start
[16:16] <mhr3> great...
[16:16] <sil2100> So hmmm
[16:16] <dednick> Saviq: yup
[16:16] <sil2100> mhr3: if the tests didn't even run, why did it take 2 hours?
[16:17] <sil2100> Timeout, yes?
[16:17] <sil2100> geh
[16:18] <sil2100> Trevinho, bschaefer, bregma: ping
[16:18] <bschaefer> o a large ping.... sounds bad :(
[16:18] <bschaefer> sil2100, pong!
[16:18] <mhr3> sil2100, i see lightdm segfault in syslog
[16:18] <pete-woods> is anyone able to review this trivial MR to the camera-app for me? https://code.launchpad.net/~pete-woods/camera-app/change-infographic-text/+merge/176238
[16:19] <pete-woods> (the label change is per design-team request)
[16:19] <sil2100> bschaefer: one moment then
[16:19] <sil2100> (since mhr3 noticed something)
[16:19]  * bschaefer sits close to the edge of his chair
[16:19] <sil2100> lightdm segfault... but why on both machines?
[16:19] <sil2100> bschaefer: since we can't get unity released for a looong time :(
[16:19] <bschaefer> :(
[16:20] <dednick> Saviq: https://bugs.launchpad.net/autopilot/+bug/1203808
[16:21] <Saviq> dednick, awesome, thanks
[16:22] <mhr3> sil2100, can you just restart the test machines and try again?
[16:23] <sil2100> jibel: hi! Are the machines restarted on every run? Or do those have to be restarted manually?
[16:23] <sil2100> didrocks: ^ ?
[16:23] <dednick> Saviq: we could fix it our side by making the test less presumptuous.
[16:23] <Saviq> dednick, https://code.launchpad.net/~saviq/unity8/fix-ap-on-device/+merge/176236
[16:23] <Saviq> dednick, I want to just have it working ASAP
[16:24] <Saviq> dednick, so I skipped the broken tests
[16:24] <dednick> lol. ok
[16:24] <didrocks> sil2100: they are daily restarted, after refreshing the image
[16:24] <dednick> they're pretty useless tests anyway
[16:24] <sil2100> didrocks: can we somehow restart them manually?
[16:24] <sil2100> mhr3: I can check if it's badly broken by running it manually with any test
[16:24] <didrocks> sil2100: ssh and reboot it :)
[16:25] <bregma> sil2100, are you alluding to https://bugs.launchpad.net/unity/+bug/1202976 above?
[16:25] <mhr3> sil2100, i'm running the daily ppa, guess i'll just try restarting my machine
[16:25] <sil2100> bregma: hi! I think sadly no... since right now we seem to be encountering compiz (and lightdm) crashes that make tests fail
[16:26] <sil2100> bregma: we didn't yet find what exactly is going on, but we're guessing something might be wrong causing compiz to crash
[16:26] <sil2100> didrocks: will try!
[16:27] <didrocks> sil2100: thanks!
[16:27] <Saviq> dednick, when it builds, I'll ask you to put it on your device and run the whole unity8 suite, ok?
[16:27] <mhr3> bregma, most of the preview stuff was fixed, the bug could use updating
[16:27] <mhr3> sil2100, ^
[16:28] <mhr3> yea, if i don't come back, something is *reall* broken :)
[16:28] <dednick> Saviq: ok
[16:29] <dednick> Cimi: ping
[16:32] <mhr3> sil2100, looks like my system survived
[16:32] <sil2100> mhr3: phew
[16:32] <sil2100> mhr3: I'm trying to log in but having some key problems
[16:33] <sil2100> mhr3: in the meantime, I checked the FS snapshot from the previous run and couldn't see /var/crash ;/
[16:33] <Saviq> yikes we're at $240k
[16:33] <nic-doffay> Saviq, just wanted to check something with you before I code something. There isn't a general purpose bool on a Component or Item or some other child class which checks if it's animating? You have to check on the actual animation itself, correct?
[16:33] <mhr3> great, so we are where we  were in the morning
[16:33] <sil2100> mhr3: didrocks says the machines seem ok
[16:33] <nic-doffay> Saviq, I haven't been able to find one as of yet.
[16:34] <Saviq> nic-doffay, yup
[16:35] <nic-doffay> Saviq, cool beans
[16:36] <Saviq> $255k
[16:42] <sil2100> mhr3: ouch
[16:43] <sil2100> mhr3: when did you upgrade? Do you have -proposed enabled?
[16:43] <sil2100> mhr3: siiiince!
[16:43] <mhr3> sil2100, no proposed
[16:43] <sil2100> mhr3: there has been an lightdm upload 10 hours ago to main which has this https://bugs.launchpad.net/lightdm/+bug/1203711
[16:43] <sil2100> mhr3: it seems a critical bug, but the bug says that it's 'rarely triggered'
[16:44] <sil2100> (I think our jenkins is the case where the bug appears)
[16:44] <sil2100> mhr3: there's a new upload in -proposed fixing that bug
[16:44] <sil2100> mhr3: upload made 1 hour ago
[16:44] <mhr3> sil2100, but doesn't that mean that the bug has been there for quite a while?
[16:45] <mhr3> it run "fine" today morning
[16:45] <sil2100> mhr3: not sure! It might be something introduced in the recent version, who knows?
[16:45] <sil2100> mhr3: maybe it doesn't happen every time
[16:46] <sil2100> mhr3: and we're just unlucky
[16:46] <mhr3> sil2100, hmm, i guess a re-run will tell
[16:47] <sil2100> mhr3: re running, let's see what's happening... btw. unity is failing on powerpc right now ;p
[16:47] <sil2100> Because of unit tests
[16:47] <sil2100> Trevinho, bschaefer: could you guys take a look?
[16:47] <mhr3> Trevinho, ^
[16:47] <sil2100> https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/4815026
[16:48]  * bschaefer reads backlog
[16:48] <sil2100> bschaefer: the backlog is about something else, I mean the failing powerpc unit test for unity
[16:48] <bschaefer> o
[16:48] <sil2100> bschaefer: in the log I pasted ;)
[16:48] <bschaefer> sil2100, sweet, I just got to that bit
[16:48]  * bschaefer looks at log
[16:49] <mhr3> sil2100, is it going to re-build everything or just run the tests?
[16:49] <mhr3> sil2100, ie will it take an hour or three? :)
[16:49] <sil2100> mhr3: just re-run the tests ;)
[16:49] <sil2100> bschaefer: thanks!
[16:49] <sil2100> :)
[16:50] <bschaefer> sil2100, strange failure, Im hoping I can reproduce it!
[16:50] <mhr3> bschaefer, unlikely :)
[16:50] <mhr3> bschaefer, unless you have powerpc ;)
[16:50] <sil2100> mhr3: well, last time it was JUST running the tests for 2 hours (and by 'running' I mean 'timing out' for 2 hours)
[16:50] <bschaefer> mhr3, thanks for the hope man, i suppose well have to figure out why its failing due to that log then
[16:50] <sil2100> ;p
[16:50]  * bschaefer looks harder at the log
[16:50] <mhr3> sil2100, yea, but if someone looked at the output it'd be clear after 5minutes that it's not going anywhere
[16:51] <mhr3> bschaefer, you're welcome, i'm super-positive today
[16:51] <bschaefer> mhr3, :), it sounded that way!
[16:51] <dednick> BE the log
[16:51] <mhr3> lol
[16:52] <bschaefer> haha
[16:52] <Trevinho> mhr3: oh, sorry...
[16:52] <bschaefer> sil2100, also on a different thing im working on, you know the new ibus 1.5 stuff? Well its always on, which is making these tests fun to fix
[16:52] <mhr3> Trevinho, your double tests, when are you going to learn? :P
[16:53] <Trevinho> mhr3: I didn't made them double... They already were
[16:53] <bschaefer> ie. enable/disable signals are no longer emited
[16:53] <Trevinho> :P
[16:54] <sil2100> bschaefer: the new ibus is always on in the end?
[16:54] <sil2100> bschaefer: I remember a discussion on the ML but don't remember the end result
[16:55] <bschaefer> sil2100, right, or so it seems, its kind of cool, but kind of annoying as we can longer detect when we are about to be entering preedit or not
[16:55] <sil2100> bschaefer: shiiit...
[16:55] <bschaefer> sil2100, also it uses gsettings now, which the xml file is just one huge string
[16:56] <bschaefer> ish, its just not formatted very well, but hopefully I can read that stuff in and get the hot key...
[16:56] <sil2100> But that's just mean
[16:56] <sil2100> ;/
[16:56] <bschaefer> sil2100, but I might have to go back to asserting the results by hand :(
[16:56] <Saviq> $323k
[16:56] <sil2100> ;|
[16:56] <bschaefer> sil2100, which in doing so I get 32 tests to pass
[16:56] <Saviq> *crazy*
[16:56] <bschaefer> Saviq, thats going up fast!
[16:57] <sil2100> bschaefer: ok, let's do that, since I started the automated mess, I'll maybe try to work around it some other way in my free time ;p
[16:57] <Saviq> bschaefer, it is
[16:57] <sil2100> bschaefer: since I remember 1.5 opened up some new possibilities
[16:57] <bschaefer> sil2100, right, theres 1 other regression I see in the dash hint, but I should just get the tests passing, then we can go back and fix it up
[16:58] <bschaefer> sil2100, as we can no longer assert we have enabled ibus or not :( which is really bad, but we might have to assert which engine is active or not now
[16:58] <bschaefer> sil2100, ie. <Hot key triggered> assert pinyin is active
[16:58] <bschaefer> vs asserting we are enabled
[16:58] <bschaefer> sil2100, but overall unity still works well with ibus :)
[16:59] <sil2100> bschaefer: at least that!
[16:59] <bschaefer> sil2100, yup :), well Ill take  alook at this test and see how powerpc could be failing
[16:59] <sil2100> bschaefer: I talked with the SRU team about the XIM things btw. - they answered and poked me for more info, which I am providing slowly bits by bits
[16:59] <sil2100> bschaefer: since they want to know a bit more about the risk factors
[17:00] <bschaefer> sil2100, if you have any questions, let me know
[17:00] <sil2100> Will do!
[17:00] <sil2100> For now, I think I need to pop out for now
[17:00] <sil2100> So see you tomorrow!
[17:00] <bschaefer> sil2100, thats always a tough thing to answer, but we've been using it since 13.04
[17:00] <bschaefer> sil2100, alright!
[17:00] <bschaefer> cheers
[17:00] <sil2100> See you
[17:00] <Trevinho> mhr3: do you know if using EXPECT_FLOAT_{GE,LE} can help there?
[17:01] <mhr3> Trevinho, i dont think such function exists
[17:01] <mhr3> er, template
[17:01] <mhr3> whatever
[17:01] <Trevinho> mhr3: EQ exists...
[17:01] <Trevinho> I wanted to try :D
[17:01] <mhr3> yea
[17:01] <mhr3> but EQ is special :)
[17:02] <mhr3> Trevinho, it's likely that it needs to be clamped in the real thing
[17:02] <Trevinho> mhr3: we have a fast way to test other a launchpad build?
[17:03] <mhr3> don't think so
[17:03] <Saviq> dednick, http://s-jenkins:8080/job/unity8-saucy-armhf-ci/358/
[17:03] <mhr3> you can do a vm :)
[17:03] <Trevinho> mhr3: would sooo fast
[17:03] <Trevinho> be ^
[17:04] <bschaefer> well it would be nice to see what the value of rem is :)
[17:04] <mhr3> Trevinho, you don't need to compile the entire unity, just create a test method that uses the fpu the same way
[17:04] <mhr3> but yea, definitely, change the assert to two EXPECT_LE and EXPECT_GE
[17:04] <mhr3> that won't fix it, but it will produce better output next time :)
[17:05] <bschaefer> very much so :)
[17:05] <bschaefer> mhr3, should we just merge in a branch now, and see what happens or get a VM set up?
[17:07] <mhr3> bschaefer, well there's two things the failure will say either than expected value was supposed to be <= 1.0 and is 1.00001 or that it was supposed to be >= -1 and is -1.00001
[17:07] <mhr3> there i just saved us a 3 hour build :P
[17:07] <bschaefer> mhr3, haha, well I know that much...
[17:08] <bschaefer> mhr3, but ... if its those values vs say 2.0? (i don't htink it can get that high though...)
[17:08] <bschaefer> we'll just need to clamp it...
[17:08]  * bschaefer starts getting a VM set up
[17:12] <Saviq> :|
[17:15] <dednick> Saviq: it's still broken
[17:15] <dednick> Saviq: in ci i mean
[17:15] <Saviq> dednick, yeah, bad skips
[17:15] <Saviq> dednick, pushed a fix already
[17:16] <dednick> Saviq: yeah, i see that now
[17:16] <Saviq> dednick, I'll have a fixed unity8-autopilot package in 5
[17:16] <Saviq> dednick, so you can still grab the output (binaries aren't changed in that branch anyway)
[17:17] <dednick> Saviq: ok
[17:17] <Saviq> $400k
[17:17] <mhr3> ehm, so the testing is hanging again afaict, who has the powers to kill it?
[17:17] <mhr3> Trevinho, ^?
[17:18] <Trevinho> mhr3: ok
[17:18] <Trevinho> mhr3: which job is?
[17:18] <mhr3> Trevinho, http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/559/
[17:19] <dandrader> racarr, ping
[17:20] <Trevinho> mhr3: oh, no... I can't login there mhmh
[17:21] <Trevinho> mhr3: no, no way.. ask fginther ^
[17:21] <bschaefer> mhr3, i've cancelled it...
[17:21] <mhr3> fginther, AP machines are broken :(
[17:21] <bschaefer> it looks like at lease
[17:21] <bschaefer> and building again
[17:22] <mhr3> i see [27209.760444] lightdm[10208]: segfault at 3f7 ip b74cba42 sp bfae2d9c error 4 in libglib-2.0.so.0.3703.0[b7489000+102000]
[17:22] <mhr3>  in dmesg
[17:22] <mhr3> again
[17:24] <mhr3> hmm, can i just update lightdm and start the testing manually?
[17:25] <mhr3> anyone know how to run them manually?
[17:25] <racarr> dandrader: POng
[17:26] <dandrader> racarr, that server api for getting notified when a client changes the type of one of its surfaces
[17:26] <dandrader> racarr, did you have time to make it?
[17:27] <dandrader> I should probably join #ubuntu-mir...
[17:27] <dednick> omg. these test run even slower than on the desktop :( sleeep time
[17:28] <racarr> dandrader: Agh, no sorry.
[17:29] <dandrader> racarr, it's blocking the work of "osk on unity8-mir"
[17:29] <racarr> dandrader: Ok. I made a note and will try and make sure it happens today
[17:29] <racarr> I did a bunch of other stuff last week and got kind of in to it
[17:29] <racarr> anything else blocking?
[17:30] <dandrader> racarr,  that mp on the input-method surface type. although I could work around it by using the overlay type as a substitute for the time being
[17:31] <racarr> Ok.
[17:33] <mhr3> bschaefer, can you now re-run the test again?
[17:33] <bschaefer> mhr3, thought I did that...
[17:33] <mhr3> i upgraded lightdm there
[17:33] <bschaefer> mhr3, o cool, alright just re-did it
[17:33] <mhr3> not sure if it's going to survive the re-run, but let's hope it does
[17:33]  * bschaefer crosses fingers and toes
[17:34] <bschaefer> mhr3, I don't think im entering the correct info in ...
[17:34] <fginther> Trevinho, mhr3, what's going onnow?
[17:34] <bschaefer> as normally the params stay around...
[17:34] <bschaefer> fginther, could you make sure the tests are re-running at this point :)
[17:35]  * bschaefer does not think so
[17:35] <mhr3> fginther, some weirdness with the AP testing, lightdm is crashing and therefore nothing gets tested
[17:35] <mhr3> fginther, there's probably a fix for that in proposed
[17:35] <fginther> mterry, cyphermox, can one of lend a hand? AP test in dailyrelease is failing due to lightdm
[17:35] <Saviq> dednick, http://ubuntuone.com/216F6FhOBIhiHTitoJOqa8
[17:36] <bschaefer> mhr3, alright, I just copied over the info from that last build
[17:36] <Saviq> dednick, reboot phone, start an app, close the app
[17:36] <Saviq> dednick, phablet-test-run -i -n -p unity8-autopilot -c indicators-client_*deb -c unity8_*.deb -c unity8-autopilot_*.deb -c unity8-fake-env_*.deb -c unity8-private_*.deb unity8
[17:36] <mhr3> bschaefer, cool, seems to be doing something now :)
[17:37] <cyphermox> fginther: sure
[17:37] <mhr3> bschaefer, lovely [29901.858938] lightdm[17098]: segfault at 3f7 ip b7479a42 sp bfc4caac error 4 in libglib-2.0.so.0.3703.0[b7437000+102000]
[17:37] <cyphermox> fginther: where is the failure?
[17:37] <fginther> cyphermox, i think bschaefer restarted it # 562
[17:37] <bschaefer> mhr3, yup, last time it was just empty, pointing to raring... ops :)
[17:37] <bschaefer> :(
[17:37] <mterry> fginther, I'm a tad busy, but if something needs lightdm specific knowledge, maybe I can help
[17:37] <bschaefer> mhr3, that was quick
[17:37] <mhr3> i can upgrade it again, but dunno how to manually kick start it
[17:38] <bschaefer> mhr3, I can start it up again it seem, but you have to get an account from QA I think
[17:38]  * bschaefer got it from thomi
[17:38] <mhr3> i can connect to the lxc containers using ssh
[17:38] <bschaefer> oo
[17:38] <fginther> mterry, cyphermox, the problem was reported by mh3
[17:38] <fginther> mterry, cyphermox, the problem was reported by mhr3
[17:38] <bschaefer> you mean sshing :)
[17:38] <cyphermox> ok
[17:39] <cyphermox> well it's going to be hard to reproduce as-is
[17:39] <cyphermox> I'll see if I can get in the container to get a crash dump or something
[17:39] <mhr3> cyphermox, basically we just need to upgrade lightdm from proposed
[17:39] <mhr3> that should fix it
[17:39] <cyphermox> what's blocking lightdm in proposed?
[17:39] <mhr3> proposed is already enabled, but it seems it doesn't pull it
[17:39] <mhr3> cyphermox, no idea
[17:40] <mhr3> cyphermox, or perhaps you just the right command to manually starting the testing from within the lxc container?
[17:40] <Saviq> dednick, ok, don't - there's something wrong there still :|
[17:40] <Saviq> ah right, stupid .pyc
[17:40] <cyphermox> mhr3: i'll take a look
[17:41] <bschaefer> mhr3, that would be awesome if it fixed that crash....
[17:41] <bschaefer> mhr3, do the lightdm logs offer any other info?
[17:41]  * bschaefer is guessing you've covered those bits already
[17:42] <dednick> Saviq: ok, got past the indicators tests and running uniyt8
[17:43] <Saviq> dednick, so you're better than me
[17:43] <Saviq> dednick, but seems I got some dependency issues
[17:45] <mhr3> bschaefer, cyphermox, yea, ok lightdm from proposed does fix it
[17:45] <cyphermox> ok
[17:45] <bschaefer> mhr3, yay
[17:45] <mhr3> i upgraded and did "reboot" and it seemed to to start up compiz then
[17:45] <mhr3> although then otto reported a timeout :)
[17:46] <mhr3> guess it doesn't like reboots
[17:46] <Saviq> ok yeah, it's looking better now
[17:47] <cyphermox> mhr3: proposed is not enabled there
[17:47] <mhr3> cyphermox, i saw it in one of the otto dirs
[17:47] <mhr3> plus it offered my lightdm...ubuntu2
[17:47] <mhr3> me*
[17:48] <cyphermox> ok
[17:48] <cyphermox> well, I can't see it in the directories there http://<IP_ADDRESS>/otto/saucy-i386-20130722-0916/
[17:49] <cyphermox> but it seems like you know better how this is done than I do, it was my first time seeing this URL at all
[17:49] <mhr3> ..hm unless it was coming from main
[17:50] <cyphermox> I don't know
[17:50] <cyphermox> seems like lightdm should land in the archive anytime too
[17:50] <mhr3> nope, just check, it's not in main yet
[17:50] <mhr3> checked*
[17:51] <mhr3> well if it's going to land, then we just need to run the tests again once it lands
[17:52] <mhr3> seems like only didrocks and jibel really know how this works :)
[17:57] <dednick> Saviq: hm. unity8 tests didnt appear to actually start :(
[17:58] <Saviq> dednick, yeah, it's all still not good
[17:58] <dednick> just hung waiting for pid
[17:58] <Saviq> dednick, go have a life ;)
[17:58] <dednick> Saviq: woooh!
[18:02] <mhr3> tedg, eh http://bazaar.launchpad.net/~mhr3/dbus-test-runner/watch-pipes-for-hup/revision/75
[18:02] <mhr3> this is embarrassing :P
[18:04] <tedg> Heh
[18:04] <tedg> Wonder why the test didn't get that...
[18:07] <mhr3> the tokens weren't split properly so it considered them all invalid
[18:08] <mhr3> and the last test... probably different scheduling that made it succeed :)
[18:48] <dandrader> If I run unity8 manually on the device it doesn't get any content (all dbus connections fail) such as indicators and scopes
[18:48] <dandrader> what I am missing?
[19:00] <Saviq> dandrader|afk, tried logging out and back in?
[19:01] <Saviq> dandrader|afk, sounds like your session isn't set up?
[19:04] <Saviq> $844k
[19:18] <dandrader> Saviq, so my DBUS_SESSION_BUS_ADDRESS was different than the one used to launch the session bus daemon (dbus-daemon --session --address=...)
[19:18] <Saviq> dandrader, must've gotten out of sync
[19:18] <Taek|Work> Why does unity exists?
[19:19] <hio> Hi, does anyone here like Unity?
[19:19] <dandrader> Saviq, btw, should run_on_device work at the moment? (with this new upstart setup)
[19:19] <Saviq> dandrader, yes
[19:19] <Saviq> dandrader, but not on "current"
[19:19] <Saviq> dandrader, flash with --pending
[19:20] <Taek|Work> No one knows why Unity exists?
[19:20] <hio> I think nobody actually loves Unity. People tolerate it
[19:21] <hio> nature - it's amazing
[19:21] <dandrader> Saviq, so "pending" is the next "current"?
[19:22] <Saviq> dandrader, yeah, pending is the latest and greatest
[19:22] <Saviq> dandrader, current is the latest that passed QA
[19:22] <dandrader> Saviq, hmm, ok. thanks
[19:22] <Saviq> hmm how do I use CalDAV on Google with SSO...
[19:22] <Taek|Work> don't use google
[19:22] <Taek|Work> they want all your base!
[19:23] <Taek|Work> to give it to the Fbi