[02:51] <hallyn> pitti: thanks.  no my use case isn't onfailure, just need to fix lxc vs lxc-net.
[02:52] <hallyn> pitti: switching to ExecPreStart or whatever in lxc-net seems like the way to go
[16:42] <LocutusOfBorg1> xnox, hi, quick question, do you know why ubuntu-dev-tools doesnt depend at runtime to pbuilder?
[16:42] <LocutusOfBorg1> I mean, I can't pbuilder-dist sid login without pbuilder, and the former is part of ubuntu-dev-tools
[16:47] <ScottK> LocutusOfBorg1: udt doesn't depend on every single the every script needs.  It'd be very heavy to install otherwise. Devscripts is similar in this regard.
[16:49] <LocutusOfBorg1> ScottK, I was wondering that was the reason, of course pbuilder-dist armhf login needs qemu and it is heavy
[16:49] <LocutusOfBorg1> I was wondering how much of ubuntu-dev-tools can run without pbuilder, and I guess the answer is "a lot"
[16:50] <LocutusOfBorg1> well, I won't ask to split anything :P thanks!
[17:42] <zequence> I'm still very new to uploading packages. I can't seem to find any other information on the subject, than here http://packaging.ubuntu.com/html/udd-uploading.html.
[17:43] <zequence> I'm about to upload lp:ubuntustudio-menu, but not sure which steps to take
[17:44] <zequence> I'm not supposed to upload the bzr branch to ubuntu:ubuntustudio-menu, right?
[17:45] <zequence> In the log for ubuntu:ubuntustudio-menu, it says committer is Package Import Robot
[17:45] <zequence> So, I'm guessing it gets updated from a package that was uploaded to the archive with dput?
[17:57] <zequence> Ok, I uploded to the archive, with: dput ../<changes_file>.
[18:03] <Laney> zequence: https://wiki.ubuntu.com/MOTU/New might be useful
[18:05] <zequence> Laney: Thanks!
[18:11] <Laney> please edit it with any missing knowledge that you would have liked to know
[19:49] <micahg> LocutusOfBorg1: regarding the virtualbox backport, did you intend to test a backport from wily to trusty, utopic, and vivid?
[19:49] <micahg> I'm just trying to clean up some of the backports bugs and there are at least 2 open for virtualbox at present
[19:53] <infinity> LocutusOfBorg1: Given that the majority of ubuntu-dev-tools users don't even use pbuilder (and will, generally, actively recommend against it), I'd be pretty miffed if it depended on it. :P


[13:34] <penguin42> Hi, I can see a file in /etc/init.d/ssh but it doesn't get listed in initctl list - why?
[13:39] <Younder> How does upstart deal with the syslogd? I just installed psad (apt-get) and want to make sure kern is set to the /var/lib/psad/psadfifo named pipe.
[17:54] <JanC> Younder: if you are using Ubuntu 9.10 then have a look at the config files in /etc/init/
[23:17] <Younder> yeah, psad is set up now (and reports back to DShield)


[08:01]  * smb hails cking
[08:01]  * cking requires more coffee
[08:05]  * apw yawns
[08:26] <ppisati_> diwic: so, the pulseaudio in the ppa:audio-dev fixed the cracking noise i head wrt skype
[08:26] <ppisati_> diwic: but i had to rip it off this morning cause after a bit
[08:27] <ppisati_> diwic: i got a loud 'beeeeepp' coming out of my speakers
[08:27] <ppisati_> diwic: and the noise didn't stop until some other audio samples was played
[08:31] <diwic> ppisati_, hmm, that sounds strange
[08:31]  * ppisati_ prepares some more coffee
[08:31] <ppisati_> diwic: if you want i can reinstall everything
[08:32] <diwic> ppisati_, nah, but I wonder what that beeeepp came from, really
[08:32] <ppisati_> diwic: and do some more debugging for you
[08:32] <ppisati_> diwic: is there a way i can find it out?
[08:32] <diwic> ppisati_, hard to tell without a verbose log, and examining the state when it's present
[08:33] <ppisati_> diwic: pulseaudio log?
[08:33] <diwic> ppisati_, https://wiki.ubuntu.com/PulseAudio/Log
[08:33] <diwic> ppisati_, but you need to reproduce the beep while the logging is active
[08:34] <ppisati_> diwic: yep, no prob
[08:34] <ppisati_> diwic: it happened two times in a row
[08:34] <diwic> ppisati_, do you know how to reproduce it?
[08:35] <ppisati_> diwic: login, play a couple of songs on you tune and that's it :)
[08:35] <ppisati_> *youtube
[08:36] <diwic> ppisati_, ok, while the beep is present also take a "pacmd list"
[08:37] <ppisati_> diwic: cool, will do
[08:54] <smb> infinity, Am I right in assuming you have not looked at any of the Xen packages, yet?
[09:06]  * apw bets on good old flash for pp's issue
[11:30] <alexbligh1> Is there a reason why module-init-tools is built with --disable-zlib? I've tried rebuilding with --enable-zlib, it adds no library dependencies, and allows for modules to be compressed with gzip. The saving of even one module's compression will outweigh the extra size of a static zlib I'd have thought. And compressing all the modules in Ubuntu running from RAM saves 100MB (150MB down to 50MB). I think cjwatson added the --disable-zl
[11:30] <alexbligh1> ib stuff (or just did the packaging). Any reason not to change this? (will supply patches)
[11:32] <cjwatson> module-init-tools is removed as of raring
[11:32] <cjwatson> And I have made one change to module-init-tools ever, according to the changelog, and it wasn't that
[11:33] <alexbligh1> cjwatson, ah I'm looking at Precise. Where do they live now?
[11:33] <cjwatson> For current releases, please look at kmod, not module-init-tools; for stable releases, I suspect such a change wouldn't be appropriate
[11:34] <alexbligh1> cjwatson, I have no idea where I got your name from :-)
[11:34] <alexbligh1> would it be appropriate to use zlib in kmod?
[11:35] <alexbligh1> For Precise I'll just build a custom package. I was just checking there was nothing deathly about module compression.
[11:35] <cjwatson> No idea
[11:36] <cjwatson> Would probably need benchmarking to make sure it doesn't regress boot performance for some reason (yes, intuitively the I/O gain should outweigh that, but it still needs benchmarking)
[11:36] <alexbligh1> thanks
[13:00]  * ppisati goes out for a bit, brb
[13:38]  * henrix -> back in 15
[13:45]  * rtg pushes v3.10-rc3 rebase to Saucy unstable
[13:46] <ogra_> vs Saucy stable ?
[13:48] <rtg> ogra_, vs Saucy master-next (which is likely to be much more stable then -rc3)
[13:48] <ogra_> ah :)
[13:48] <rtg> ogra_, I'm gonna do some testing on -rc3 today. if it looks OK, then perhaps I'll make it the new stable.
[13:49] <rtg> or master-next I mean
[14:09] <smb> Hm... seems today's netboot saucy images go straight into a panic (at least on Xen)
[14:13] <rtg> smb, I don't think the kernel has changed in awhile.
[14:15] <rtg> yeah, uploaded on the 20th
[14:15] <smb> rtg, I thought that did work last week but who know. Dumping now to see the more useful parts of dmesg... At least with today I seem to run into a bit of lvm trouble, too. Only some LVs of my 30 or so get their symlinks created in /dev/<vgname> or /dev/mapper/...
[14:16] <rtg> smb, wouldn't that be a udev problem ?
[14:17] <smb> rtg, Right, those are likely unrelated. Just an indication that it might just be one of those days
[14:30] <bjf> apw, i think bug 1098378 should be on your radar
[14:30] <ubot2> Launchpad bug 1098378 in linux (Ubuntu Raring) "chroot+overlayfs seems to cause umount mis-behavior" [High,Confirmed] https://launchpad.net/bugs/1098378
[14:30] <smb> Oh, maybe the failure inside the guest actually is related to udev, too... "cannot open /dev/null" (twice) and "mounting none on /dev/pts failed"...
[14:48] <apw> bjf, ta
[14:52] <jsalisbury> **
[14:52] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:52] <jsalisbury> **
[14:53] <bjf> apw, you are most welcome
[15:25] <rtg> apw, rtg@gomeisa:~/r/kern$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-raring.git
[15:25] <rtg> Cloning into 'ubuntu-raring'...
[15:25] <rtg> remote: error: Could not read bce134d73d6d2bc23aeea1d32e559f11e61b8958
[15:25] <rtg> remote: fatal: bad tree object bce134d73d6d2bc23aeea1d32e559f11e61b8958
[15:25] <rtg> remote: aborting due to possible repository corruption on the remote side.
[15:25] <rtg> fatal: early EOF
[15:25] <rtg> fatal: index-pack failed
[15:27] <apw> rtg, eep
[15:27] <rtg> apw, yeah. I think my local repo is up to date.
[15:38] <smb> have we recently moved some other repo to archive?
[15:39] <smb> (iow could it be that weird --reference badness again)
[16:07] <apw> smb, no i think this is actually because we started using linux.git on there as a rewind tree, a nono with this setup
[16:08] <apw> rtg, i think i have it repaired, you might want to try recloning, i am letting fsck finish again, if it is clean then i will repack the repo without an alternative
[16:08] <rtg> apw, ack
[16:08] <apw> bjf, sconklin, henrix, your raring master repo is unhappy, i am working on it
[16:08] <sconklin> apw: ack
[16:08] <bjf> ack
[16:09] <smb> apw, Hm, and I thought Linus repo as alternative would always be safe
[16:10] <apw> smb, it would be _if_ we weren't putting stable in it, which has 'pending' branches which are rebased; bad
[16:10] <smb> apw, eew
[16:11] <apw> smb, yeah, and that expalins the objects which have gone, they are blobs and trees which would have been common on patches in another branch
[16:12] <smb> Sounds like we should give up --reference as long as git allows us
[16:27] <bjf> apw, i'm totaly confused why we would be using the "stable" tree (linux.git) as a reference to _any_ of our repos
[16:27] <bjf> apw, that just seems so wrong
[16:30] <rtg> bjf, I don't think it started out being the stable tree
[16:31] <bjf> rtg, ack
[16:32] <rtg> hmm, 'Failed to execute /init' is a real problem. v3.10-rc3 is kind of a fail.
[16:47] <rtg> apw, is your git fsync done ?
[16:51] <jsalisbury> ##
[16:51] <jsalisbury> ## Kernel team meeting in 10 minutes
[16:51] <jsalisbury> ##
[16:52] <infinity> smb: You might be right.
[16:54] <smb> infinity, Looking at the changelog, Daviey thinks I need to get TechBoarded anyway
[17:07] <apw> rtg, bjf,  sconklin, ubuntu-raring looks to be in good shape now; i have separated it from the linux.git repo now so we should be safe going forward
[17:07] <apw> rtg, i am just checking saucy which has the same linkage
[17:07] <sconklin> ack, thanks
[17:07] <rtg> apw, yep, cloned it a bit ago with no problems
[17:07] <bjf> apw, ack, thanks
[17:08] <apw> smb, did i see that the issue with devtmpfs was a systemd/udevd issue?
[17:09] <smb> apw, for the installer part yes
[17:09] <rtg> apw, ok to push saucy master-next ?
[17:09] <smb> some script from debian rather using tmpfs not devtmpfs
[17:23] <sconklin> apw:  do I need to clone raring fresh?
[17:23]  * rtg -> lunch
[17:40] <apw> sconklin, nope, it should be fine if you have a copy
[17:40] <sconklin> ok, too late :-)
[17:40] <apw> sconklin, it was the central copy which was missing an object or two; now restored
[20:30]  * rtg -> EOD


[08:09] <tsdgeos> mzanetti: can you do when you have some free time? https://code.launchpad.net/~aacid/unity8/fix-xvfbtest-dashview-plugin
[08:09] <tsdgeos> https://code.launchpad.net/~aacid/unity8/fix-xvfbtest-dashview-plugin/+merge/215181
[08:12] <Cimi> Saviq, what do I do though with the cmake file since my patch didn't work?
[08:13] <mhr3> Mirv, if you're preparing a qt pkg for the carousel issue, feel free to add it to silo 015
[08:15] <Saviq> Cimi, let me check something
[08:19] <Mirv> mhr3: I'm not (yet), since it's in a non-touch seed so I was thinking of having it for the beginning of u-series with a bunch of other patches
[08:19] <Saviq> Cimi, http://paste.ubuntu.com/7260172/
[08:19] <Saviq> Cimi, that works
[08:20] <Saviq> Cimi, set_tests_properties only affects things when you run `make test`, not when you use `make testfoo`, 'cause testfoo is not a test, it's just a custom target
[08:21] <Saviq> Cimi, might want to wrap the second LC_ALL= in quotes
[08:21] <Cimi> Saviq, makes sense
[08:21] <Saviq> Cimi, so http://paste.ubuntu.com/7260175/
[08:21] <Cimi> Saviq, so we don't need make test here, or we do?
[08:21] <Cimi> sorry, set test properties
[08:21] <Saviq> Cimi, we do
[08:21] <Saviq> Cimi, 'cause if you run `make test`
[08:21] <tsdgeos> Mirv: understand this is not specifically against you but more against "stable distros concept". So we have a bug, we have a fix for the bug, but since it's "stable" the bug is not applied <- never understood this rationale
[08:22] <Saviq> Cimi, it would fail
[08:22] <Cimi> Saviq, but can't we set it for all tests?
[08:22] <Cimi> set it once for all?
[08:22] <Saviq> Cimi, no, it has to be per-test
[08:22] <Cimi> ok
[08:22] <Saviq> or per-custom-command
[08:23] <mhr3> Saviq, have you tried turning on the perf overlay for the shell?
[08:23] <mhr3> it's quite interesting
[08:23] <Saviq> mhr3, no I haven't
[08:23] <mhr3> Saviq, http://paste.ubuntu.com/7260184/
[08:24] <Saviq> mhr3, great, MP!
[08:24] <Saviq> :P
[08:25] <Mirv> tsdgeos: well it's more like it cannot enter right now since it's final freeze and it's seeded. it could go in as SRU, but so far we've always just moved to the next development version instead for touch.
[08:25] <mhr3> Saviq, observation #1, rendering in both the apps scope and scopes scope are much slower compared to the rest
[08:25] <Mirv> tsdgeos: but I do get your point, the burden of how to do stable updates more often that not leads to not having updates
[08:27] <Mirv> tsdgeos: the history behind it is that usages of distro and libs are large and abound, and there have been numerous examples of minor, 100% rock solid 1-liner patches that ended up causing grievance. so that's why it's more like "no changes, unless provenly regression-free for all reverse depedencies" for stable update
[08:28] <Mirv> but it's cultural, too
[08:29] <tsdgeos> Mirv: which is understandable from some pov, but is still against "progress", since if you delay the patch you'll face that grievance anyway in "the next release", so it's better if you face it now since it also means it'll be fixed sooner (if you delay the patch 6 months the guy that did it may not even be around anymore and you have to decide which of the two bugs is worse)
[08:29] <tsdgeos> but as said, it's not against you and i'm not trying to change ubuntu's stance on it
[08:30] <tsdgeos> i'm just explaining the reason of open handed bug fixing i apply to the projects i'm maitainer/release manager
[08:38] <Saviq> dednick, hey, can you please have a look at bug #1306499 - I've a feeling it's a feedback loop of some sort :|
[08:40] <dednick> Saviq: I've already commented on it. It's not unity8. the issue exists on desktop as well. although not sure why unity8 stops responding...
[08:41] <dednick> Saviq: i can look into the problem on a deeper level if you wish
[08:41] <Saviq> dednick, well, if it updates the slider repeatedly..
[08:41] <Saviq> dednick, but you're right, it's there on desktop, too
[08:43] <dednick> Saviq: but there are other issues.: i guess if the user is currently interacting with the slider, the server probably shouldn't update it (jerky) . Also, should maybe put an update throttle in there (i think the desktop has one). We're posting a massive number of updates with the live slider.
[08:44] <Saviq> dednick, yeah, I know
[08:45] <tsdgeos> but it's really a regression on the desktop too
[08:45] <tsdgeos> it used to work afair
[08:45] <Saviq> indeed
[08:45] <Saviq> dednick, that's something the bidirectional binding component could deal with, when we get to write it...
[08:45] <dednick> tsdgeos: yeah. i think it's something to do with the account services
[08:46] <Saviq> tsdgeos, re: launcher-dbus, I think the problem is QtDBus doesn't handle subscribing to a path and all its children
[08:46] <Saviq> tsdgeos, we need /unity/launcher/$app_id
[08:47] <Saviq> tsdgeos, so that we can confine it
[08:47] <Saviq> tsdgeos, but apparently QtDBus can't do it...
[08:47] <Saviq> so you get into low level dbus message handling
[08:47] <dednick> Saviq. tsdgeos: i think it is this: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-sound/trunk.14.04/revision/431
[08:48] <Saviq> dednick, yeah, another feedback loop...
[08:48] <dednick> i'll revert and see if it fixes the prob
[08:55] <tsdgeos> Saviq: mhhhhok
[08:56] <tsdgeos> just wanted to make sure it was not ted just going the way it resembles more what glib does
[08:57] <Saviq> tsdgeos, yeah, he asked around, but didn't get anywhere
[08:57] <Saviq> tsdgeos, would be nice to get it on QtDBus indeed (especially since I think we might need it more often in the future)
[08:58] <tsdgeos> well, contribution upstream is welcome i'm pretty sure
[09:05] <mhr3> dpm, what did you do to my name? :P
[09:05] <mhr3> dpm, i don't have that weird l thing in Michal :P
[09:08] <Cimi> Saviq, shall I do for all the other tests or just for this?
[09:10] <Saviq> :PPPPPP
[09:11] <dpm> mhr3, lol, other Michal's have it, so I thought you deserve to have a special letter too!
[09:12] <dpm> Saviq, so is the ł only used in Polish?
[09:13] <Saviq> dpm, yes ;)
[09:13] <Saviq> dpm, ąęółśżźćń
[09:14] <Saviq> of those I've only seen ó used anywhere else, TBH
[09:14] <dpm> wow, you like your accents in consonants :)
[09:14] <dpm> we use ó quite often in Catalan too
[09:15] <mhr3> we have ó too
[09:16] <mhr3> but still no weird l :)
[09:16] <Cimi> Saviq, shall I add only this cmakefile modification for now?
[09:16] <Cimi> or all tests?
[09:20] <Saviq> Cimi, to qmltests/CMakeLists.txt as well
[09:21] <Cimi> Saviq, but there are other tests apart that
[09:21] <Cimi> Saviq, I don't think all with require though
[09:21] <Cimi> generally is text and dimes
[09:22] <Cimi> }times
[09:23] <tsdgeos> interesting so ń and ñ are the same sound
[09:41] <Cimi> Saviq, this should be enough http://paste.ubuntu.com/7260511/ ?
[09:41] <Saviq> Cimi, you can't have two ENVIRONMENT properties
[09:42] <Cimi> Saviq, so how do I set two?
[09:42] <Saviq> Cimi, space separated
[09:42] <Cimi> I tried and complained
[09:42] <Saviq> Cimi, space separated in the same quotes
[09:42] <Cimi> oh maybe in the same " "
[09:42] <Saviq> Cimi, not separate string
[09:42] <Cimi> yep
[09:43] <Cimi> Saviq, well cmake was passing with that anyway :)
[09:43] <Cimi> committing
[09:43] <Saviq> Cimi, sure, but probably not the tests :P
[09:44] <Cimi> Saviq, do we have a function that is called after the autopilot test ends?
[09:45] <Saviq> Cimi, addCleanup is used for that
[09:45] <Cimi> Saviq, all test suite?
[09:46] <Saviq> Cimi, http://unity.ubuntu.com/autopilot/tutorial/advanced_autopilot.html
[09:48] <dednick> Saviq: um, can't really think of a solid solution for volume issue
[09:48] <dednick> It's feedback from asynchronous account service property changes . we change the valume 10 times internally (and send off update to account services), then get a slow trickle volume property changes from account services... ever needed to deal with that before?
[09:48] <Saviq> dednick, right, that's what I was afraid of...
[09:49] <dednick> there doesnt seem to be a way which we can tell if it was a locally updated value or someone else that updated the service.
[09:50] <tsdgeos> dednick: can you tell the service thing "you this is the new value but don't tell me, i already know about it"?
[09:50] <dednick> tsdgeos: um. dont think so. it's just a dbus property update
[09:50] <Saviq> tsdgeos, yeah, it's just like QML props...
[09:50] <tsdgeos> right
[09:51] <Saviq> dednick, other than making it sync, or adding some timeout logic...
[09:52] <dednick> Saviq: hm. dont think sync will work, since the prop update is still async.
[09:53] <mhr3> or a "i'm about to receive these notifications, ignore them"
[09:54] <Saviq> mhr3, yeah, but would you just maintain a list of those you didn't receive yet?
[09:54] <mhr3> indeed
[09:55] <mhr3> i'd call the class implementing it "NotificationPremonition" :)
[09:55] <dednick> thought about that. but operations the operations can fail. dont think it's guaranteed to get the prop update for the one you sent.
[09:55] <Saviq> tsdgeos, I wonder... if we increased the cache buffer (i.e. moved delegatecreationbegin/end), we wouldn't be blocking as much would we
[09:56] <Saviq> hmm or wait, not
[09:56] <Saviq> it doesn't know about cacheBuffer vs. on screen
[09:56] <tsdgeos> Saviq: it doesn't guarantee it, but yes if you have enough buffer zone for async creation of stuff it'd be doing less blocking
[09:56] <tsdgeos> but otoh everything is inside an async card now
[09:56] <tsdgeos> so i don't know why is still blocking at all
[09:57] <tsdgeos> in the optim branch i mean
[09:57] <tsdgeos> it should just give us blank spots
[09:57] <Saviq> tsdgeos, well, Loaders are not async by default are they?
[09:58] <tsdgeos> but this one is
[09:58] <tsdgeos>         delegate: Loader {
[09:58] <tsdgeos>             asynchronous: true
[09:58] <tsdgeos> CardFilterGrid.qml
[09:58] <Saviq> mhm
[09:59] <mhr3> dednick, hm, then the only safe way is to add a timestamp?
[09:59] <Saviq> yikes :|
[10:00] <dednick> mhr3: uh?
[10:02] <mhr3> dednick, when changing the volume, the requester passes current timestamp, and then the service exposes it
[10:03] <dednick> mhr3: would require changes to service. dont think that's possible.
[10:03] <mhr3> oh well... heuristics then
[10:04] <dednick> yeah. i think we're just going to have to have a timeout
[10:07] <mhr3> fwiw yesterday on android the volume overlay wasn't updating for me properly either :)
[10:10] <dednick> :)
[10:16] <Cimi> Saviq, http://paste.ubuntu.com/7260650/
[10:17] <Cimi> Saviq, this works...
[10:17] <Saviq> Cimi, can't see how it would
[10:18] <Saviq> Cimi, indicators are already started before
[10:18] <Saviq> Cimi, you can probably see it working because LC_ALL got exported as C already
[10:18] <Cimi> Saviq, maybe they can change locale on the fly?
[10:18] <Cimi> like the settings?
[10:18] <Saviq> Cimi, or maybe you should think about how environment variables work :P
[10:18] <Cimi> ahah
[10:19] <Cimi> Saviq, so upstart kills the indicators somehow
[10:19] <Saviq> Cimi, unity8 does (not for long)
[10:19] <Cimi> Saviq, thing is, with this code, indicators and shell are english while testing, then spanish when tests end
[10:20] <Saviq> Cimi, unity8 on exit stops them, but that won't be the case after upcoming unity8 release
[10:20] <Cimi> Saviq, so you can see how it would work now
[10:20] <Saviq> Cimi, well, not without --global I don't, TBH
[10:21] <Cimi> I can add global, but works
[10:21] <Cimi> proof http://paste.ubuntu.com/7260669/
[10:23] <Cimi> Saviq, -g is implied
[10:23] <Cimi>               -g, --global
[10:23] <Cimi>                      Operate  on  the  global  job  environment  table and all
[10:23] <Cimi>                      existing running job environment tables. This  option  is
[10:23] <Cimi>                      implied when not run from within a job.
[10:24] <Saviq> Cimi, ah right
[10:24] <Saviq> Cimi, so yeah, that actually leaves your environment broken, 'cause LC_ALL is unset, instead of being reset to the original value
[10:26] <tsdgeos> Saviq: when do you get teh file:///home/phablet/shell/qml/Dash/Card.qml:140: TypeError: Cannot read property 'height' of null
[10:26] <tsdgeos> file:///home/phablet/shell/qml/Dash/Card.qml:141: TypeError: Cannot read property 'opacity' of null
[10:26] <tsdgeos> warnings on the optim branch?
[10:27] <Saviq> tsdgeos, scrolling carousel in music, I think
[10:28] <Cimi> Saviq, so I can save a variable with initctl storing LC_ALL and then using it inside the cleanup?
[10:28] <Saviq> Cimi, sure, but that still won't make it work with the release that will be merged in an hour or so
[10:29] <Saviq> Cimi, since indicators won't be stopped on unity8 stop
[10:29] <mhr3> Saviq, crashes from whoopsie still aren't sent automatically?
[10:29] <Saviq> mhr3, they should be
[10:29] <mhr3> Saviq, https://errors.ubuntu.com/?package=unity8&period=month
[10:30] <mhr3> ~40 crashes... doesn't seem right :P
[10:30] <Saviq> of course it does!
[10:30] <mhr3> period=month!
[10:30] <Saviq> :P
[10:30] <Saviq> Cimi, so let's wait until then, I can't wrap my head around this atm, it really feels like we'll end up having to restart the whole session for this...
[10:31] <mhr3> Saviq, do you know who would know more about it?
[10:31] <mhr3> pitti?
[10:31] <Saviq> mhr3, ev, to start with
[10:31] <Saviq> Cimi, otherwise we'll just be hunting services that need to be restarted...
[10:32] <Saviq> Cimi, so it feels like we shouldn't be doing this for ap tests
[10:33] <Saviq> tsdgeos, yeah, scrolling in carousel - can be reproduced in tryGenericScopeView
[10:33] <Cimi> Saviq, ok
[10:33] <tsdgeos> Saviq: ok, tx
[10:34] <Cimi> Saviq, I'll attach the patch to the bugreport but not push it to the branch
[10:34] <Cimi> so we don't lose the trick
[10:34] <Saviq> Cimi, it's not really a trick ;)
[10:36] <Cimi> Saviq, well, you know always where to put hands, but not everyone is handy in python or upstart... so unless you'll be the one fixing this but, a quick note helps
[10:37] <tsdgeos> Saviq: i don't get it with tryGenericScopeView :S
[10:37] <tsdgeos> Saviq: which branches do you have merged in?
[10:38] <tsdgeos> if any
[10:38] <Saviq> tsdgeos, trunk + your branch (+ && windowShown)
[10:38] <tsdgeos> weird
[10:38] <tsdgeos> i've the same
[10:38] <Saviq> lemme try again
[10:38] <tsdgeos> Saviq: so you do the tryGSV and just flick the carousel horizontally?
[10:39] <Saviq> tsdgeos, yes, and then Alt+F4 to actually see output
[10:39] <Saviq> h wait
[10:39] <Saviq> I'm only getting binding loops there
[10:39] <Saviq> tsdgeos, so no, I can only see that through run_on_device in the music scope
[10:40] <tsdgeos> ok
[10:40] <tsdgeos> i need to add music there again
[10:40] <tsdgeos> soomehow it disappeared
[10:40] <tsdgeos> i guess i bootstrapped
[10:40] <Saviq> tsdgeos, prolly
[10:41] <Cimi> Saviq, ideally, indicator services might restart when locale changes
[10:41] <Saviq> Cimi, and scopes... and foo... and bar... and baz...
[10:42] <Cimi> yes
[10:42] <Saviq> Cimi, truth is the whole session needs to restart
[10:42] <Saviq> tsdgeos, looking through Card.qml, there's plenty of things that could be offloaded to CardTool, anything that only queries template and components...
[10:42] <Cimi> well, if doesn't affect UX
[10:42] <Saviq> tsdgeos, but when I did a quick try, it didn't really help :P
[10:42] <Saviq> Cimi, if it doesn't, it shouldn't run in the session ;)
[10:42] <Cimi> on my phone when I change locale I don't have to reboot it :)
[10:43] <Cimi> Saviq, if from the settings we change locale
[10:43] <Cimi> Saviq, indicators can easily restart because we don't have them opened
[10:43] <Cimi> Saviq, ssame for the dash and scopes (we're in the system settings app)
[10:44] <Saviq> Cimi, that's a band-aid, not a solution
[10:44] <tsdgeos> Saviq: yeah there's lots of things one thinks can be "optimized" but then the benchmark says "not really"
[10:44] <Saviq> Cimi, anyway, people know about it, you can stop thinking on it ;)
[10:44] <Saviq> tsdgeos, yeah, exactly...
[10:44] <tsdgeos> Saviq: i think i even put the art in a loader at some stage and didn't help
[10:44] <tsdgeos> but i'll try again
[10:45] <Saviq> tsdgeos, yeah, ignore me if it doesn't
[10:45] <Saviq> tsdgeos, it looked like it's more expensive to bind than to do the calculation in each card... which feels insane
[10:57] <Saviq> tsdgeos, please let me know when you're done with that branch, there's pressure to get it in...
[10:57] <tsdgeos> Saviq: sure
[10:58] <tsdgeos> Saviq: i mean we can probably get it in already, is not magic, but helps a bit already
[10:58] <tsdgeos> there's stuff i want to check
[10:58] <tsdgeos> but we don't need to land everything together
[10:58] <Saviq> tsdgeos, no, I mean like adding : '{}' to reduce warnings
[10:58] <tsdgeos> but sure, i need to reduce the warnings
[10:58] <Saviq> tx
[10:58] <Saviq> /food
[11:30] <Cimi> mzanetti, how do I see errors from make test?
[11:30] <mzanetti> Cimi: where?
[11:30] <mzanetti> ah
[11:30] <Cimi> make test
[11:30] <mzanetti> Cimi: use ctest -V
[12:01] <mhr3> Saviq, any idea what this is? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1297197/+attachment/4085366/+files/unlock_screen.mp4
[12:01] <Saviq> mhr3, I *think* it might be the screenshot
[12:01] <Saviq> mhr3, in the apps list
[12:02] <mhr3> i've never seen it *that* slow
[12:02] <Saviq> mhr3, I've encountered that on and off
[12:02] <Saviq> mhr3, after an autopilot run, for example
[12:02] <mhr3> Saviq, actually, just happened :)
[12:03] <mhr3> Saviq, but it unlocked to an empty scopes scope, so unless the screenshots are refresh even when not visible, it's not them
[12:03] <mhr3> (it was empty cause i killed it half an hour ago)
[12:04] <Saviq> mhr3, the screenshots get updated more often than the scope results, yes
[12:04] <Saviq> mhr3, can you kill the app and try again?
[12:05] <mhr3> Saviq, oh, i don't have any running :P
[12:05] <Saviq> mhr3, was that after the phone was off for a while?
[12:06] <mhr3> Saviq, yes, but i'm aware of the render thread blocking, waited a bit
[12:06] <Saviq> mhr3, mhm
[12:07] <mhr3> Saviq, cpu on 100% when swiping the greeter away
[12:07] <didrocks> Saviq: mhr3: I didn't have any app running and it was a fresh boot
[12:08] <Saviq> didrocks, the first video is expected
[12:08] <Saviq> didrocks, that's scopes loading its results for the first time
[12:08] <Saviq> didrocks, the latter I haven't seen ever :|
[12:08] <didrocks> Saviq: I get it really frequently
[12:08] <didrocks> I guess popey told it as well
[12:08] <didrocks> Saviq: we really just have the default (I wiped it yesterday)
[12:08] <didrocks> the only thing, as told, my network is quite effective…
[12:09] <didrocks> (and it's worse sometimes, really noticeable)
[12:09] <Saviq> mhr3, you're not blocking the UI any more are you?
[12:10] <mhr3> Saviq, when sending a query i might
[12:10] <mhr3> Saviq, but there are no queries sent in this case
[12:11] <Saviq> grr
[12:14] <Saviq> mhr3, in didrocks's example there might have been a query - he's going to the apps scope, and there can be a screenshot made, 'cause there's an app in the scope
[12:16] <mhr3> let me record what i see
[12:21] <mhr3> Saviq, https://drive.google.com/file/d/0BxxLngWtDRLjbmZMNHZpUDNYdG8/edit?usp=sharing
[12:22] <mhr3> smaller jerk, but still a jerk
[12:22] <didrocks> mhr3: got something similar sometimes
[12:23] <MacSlow> Saviq, regarding the needed version-bump for unity-api (unity-notifications and unity8 for modal-snap-decision)... going from 0.1.2 to 0.1.3 should be sufficient... no need to touch the minor part?!
[12:25] <Saviq> MacSlow, it's not about that
[12:25] <Saviq> MacSlow, it's about the Provides: unity-notification-impl-$foo
[12:25] <Saviq> MacSlow, and Version: in unity-notifications.pc
[12:26] <Saviq> MacSlow, and Depends: unity-notifications-impl-$foo in unity8
[12:26] <MacSlow> Saviq, sure... but it needs to start there
[12:26] <Saviq> that's unity-api, unity-notifications, unity8, respectively
[12:27] <MacSlow> Saviq, it should be based on the unity-api-version number and not on the package-version
[12:29] <Saviq> MacSlow, yes, the two are somewhat unrelated
[12:29] <Saviq> mhr3, I'm not getting this here at all, can you see any output in unity8.log? are you sure there's no query fired (a failed query or something)?
[12:29] <Saviq> mhr3, I killed my scopes scope, and it just goes fluently to the dash...
[12:30] <mhr3> Saviq, the only thing i see is
[12:30] <mhr3> file:///usr/share/unity8/Dash/CardFilterGrid.qml:36:5: QML FilterGrid: Binding loop detected for property "height"
[12:30] <mhr3> lots of it though
[12:30] <mhr3> but probably not during the unlock
[12:30] <Saviq> mhr3, yeah, only interesting part is during the unlock
[12:30] <mhr3> hmmm
[12:30] <mhr3> QIODevice::write: device not open
[12:31] <Saviq> nah
[12:32] <mhr3> Saviq, just an unlock - http://paste.ubuntu.com/7261216/
[12:32] <Saviq> mhr3, ok that's interesting...
[12:32] <mhr3> Saviq, and plus displaying empty scopes scope
[12:32] <mhr3> so... ehm?
[12:33] <Saviq> well, still shouldn't cause that
[12:33] <Saviq> but shouldn't be there in the first place
[12:33] <Saviq> (not to mention the binding loop doesn't make sense)
[12:33] <mhr3> Saviq, aren't you running tsdgeos's opti branch?
[12:33] <Saviq> mhr3, no
[12:33] <mhr3> hm, ok no idea then
[12:35] <Saviq> ah, well, the binding loop is "kind of" there
[12:36] <Saviq> mhr3, ok, nothing else I can get from you without profiling it... do you know if it persists across unity8 restarts?
[12:36] <didrocks> I have the same binding loop detection
[12:36] <didrocks> (across reboots)
[12:37] <Saviq> didrocks, and the jerky unlock, too?
[12:37] <didrocks> Saviq: yeah, I get that really regularly
[12:37] <didrocks> across reboots/versions
[12:38] <didrocks> (and not always on the first unlock)
[12:38]  * Saviq must try with broken 3G or something
[12:38] <Saviq> mhr3, does scopes scope use network for surfacing?
[12:39] <Saviq> (other than icons)
[12:39] <mhr3> Saviq, does that matter?
[12:39] <Saviq> mhr3, it might, that's what I'm trying to find out
[12:39] <mhr3> even if it does it's outside of unity process
[12:40] <Saviq> mhr3, yeah but if you're blocking on query, it might still affect unity8, no?
[12:40] <Saviq> or is the place you're blocking at only pinging scope-registry
[12:41] <mhr3> no, the blocking happens only between the time a client requests a query creation and the query object being created
[12:41] <mhr3> anything else is fully async
[12:41] <mhr3> and the network query == anything else
[12:41] <Saviq> mhm
[12:42] <Saviq> mhr3, can you consistently reproduce across unity8 restarts?
[12:42]  * mhr3 tries
[12:43] <Saviq> Cimi, you broke something https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-trusty-armhf/4456/console
[12:44] <Saviq> Cimi, QT_QPA_PLATFORM is no longer in the environment
[12:44] <Saviq> Cimi, for three of the tests
[12:45] <mhr3> Saviq, not really, first unlock was jerky but now it's ok
[12:45] <mhr3> fwiw the binding loops are still there
[12:45] <Saviq> mhr3, yeah
[12:46] <Saviq> those are spurious warnings
[12:46] <Saviq> well, still need to get rid of them
[12:46] <MacSlow> Saviq, unity-notifications will bump its "Provides" from unity-notifications-impl-2 to unity-notifications-impl-3, but how can I make sure it'll build-depend on unity-api 0.1.3 ... I only know how to make it depend on package-versions
[12:47] <Saviq> MacSlow, well, that's standard
[12:47] <Saviq> MacSlow, you need to bump unity-api indeed, and bump the B-D in unity-notifications
[12:47] <mhr3> Saviq, even the greeter itself refreshes much faster, i no longer need to wait 3 seconds for it to settle
[12:49] <Saviq> mhr3, right, so, you wanna add "-qmljsdebugger=port:3768" to unity8.conf's exec args...
[12:49] <Saviq> MacSlow, so, all in all, build-depends are handled as usual, only runtime deps are special
[12:49] <Saviq> mhr3, and the next time you encounter that - connect to it and do some profiling
[12:49] <Saviq> didrocks, ↑
[12:51]  * didrocks notes
[12:51] <didrocks> Saviq: can't really do testing atm, firedrills on firedrills…
[12:51] <Saviq> didrocks, I understand, just letting you know, I'll be trying to repro it, too
[12:52] <didrocks> yep ;)
[13:03] <MacSlow> Saviq, still not sure how to proceed... should I check for the unity-api version only in unity-notification headers (checking defined UNITY_API_VERSION_STRING from <unity/api/Version.h>) or predict the upcoming package-version number of libunity-api-dev (7.80.7) in unity-notifications build-deps?
[13:03] <mhr3> Saviq, with that do i connect to it and what do i do once i am connected?
[13:03] <mhr3> s/that/what/
[13:03] <MacSlow> Saviq, I haven't done that type of thing in ages
[13:03] <Saviq> MacSlow, don't "predict", bump it in unity-api
[13:04] <MacSlow> Saviq, so just the check in the header... ok
[13:04] <Saviq> MacSlow, you just need an UNRELEASED changelog entry in unity-api's debian/changelog
[13:05] <Saviq> MacSlow, the train machinery only deals with the part after +
[13:06] <Saviq> MacSlow, so just add an UNRELEASED at 7.80.7-0ubuntu1 or whatever the scheme is there
[13:06] <mterry> kgunn, Saviq: I don't have urgent work, if you folks have bugs or reviews you'd like to me to look at
[13:06] <MacSlow> Saviq, ok
[13:06] <Saviq> mterry, hey
[13:06] <Saviq> mterry, https://code.launchpad.net/~mterry/unity8/greeter-ux-fixes/+merge/210042
[13:06] <Saviq> mterry, three issues found during testing
[13:07] <mterry> Saviq, ask and I shall receive.  looking into it
[13:07] <mterry> Saviq, I did strip tags from all my remote and local branches!  How'd they sneak in
[13:08] <Saviq> mterry, that's an old comment
[13:08] <Saviq> mterry, you're clean
[13:08] <Saviq> mterry, last two comments are relevant
[13:08] <mterry> ah I see
[13:08] <kgunn> MacSlow: curious if you're working one similar to this ?
[13:08] <kgunn> https://bugs.launchpad.net/unity-mir/+bug/1308368
[13:09] <kgunn> sounds maybe more like unity-mir in general...
[13:09] <MacSlow> kgunn: no
[13:09] <Saviq> kgunn, we'll have to split notifications out of dash to fix that - post - QtComp work
[13:09] <MacSlow> kgunn: after the unity-api version thing I wanted to jump on bug https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1308011
[13:10] <Saviq> kgunn, or well composite OSK on the correct layer - so yah, QtComp work
[13:11] <kgunn> yeah, might be better to "leave it" until Qt comp
[13:12] <MacSlow> kgunn: but I can tackle (or at least look closer at it) that after 1308011
[13:15] <MacSlow> kgunn: on the topic of that bug 1308368, I've yet to see any design how notifications are meant to be presented on the phone in landscape orientation
[13:16] <tsdgeos> Saviq: i think we could try to review and land what is in https://code.launchpad.net/~aacid/unity8/card_optimizations/+merge/213660 right now
[13:16] <tsdgeos> not saying there's more things to be investigated/improved
[13:16] <Saviq> tsdgeos, sure
[13:17] <tsdgeos> but what we have is defenitely an improvement i'd say
[13:17] <tsdgeos> so worth going in to make people a bit happier
[13:17] <kgunn> MacSlow: sure, but landscape is a bit irrelevant to the stacking order...
[13:18] <Saviq> tsdgeos, slightly unrelated: FilterGrid.qml:69 - we're getting binding loop warnings off that all the time
[13:18] <Saviq> tsdgeos, and I can't say I disagree...
[13:18] <tsdgeos> yep
[13:18] <tsdgeos> that's the next one i want to tackle
[13:18] <Saviq> tsdgeos, ok
[13:18] <Saviq> tsdgeos, I think we talked about this
[13:18] <tsdgeos> it even happens at times hickups happen
[13:19] <MacSlow> kgunn: well... there's the case of the password-entry snap-decisions... if hte osk would be overlapped by the notification (and swallowing input) that would make entering password "hard"
[13:19] <tsdgeos> so it may or may not be related
[13:19] <tsdgeos> but killing them is a good thing for sure
[13:19] <kgunn> MacSlow: ah... true, would need a autoscroll to have text entry in view, for sure...
[13:20] <MacSlow> kgunn: I just wish this whole "stuff a dialog into a notification" would be solved in a better way... but we don't have that yet.
[13:21] <Saviq> tsdgeos, yeah, what's interesting, too, is that they show up when unlocking... when nothing should change at all re:dash, unless results are being refreshsed
[13:21] <Saviq> -s
[13:21] <dandrader> greyback, so, is it time to create a proper home (lp project) for qpamirserver?
[13:21] <MacSlow> kgunn: then such problems could be avoided
[13:21] <greyback> dandrader: ah yes, that reminds me
[13:22] <greyback> Saviq: have you had chance to think over https://docs.google.com/a/canonical.com/document/d/163nyfh_G90nzQnRdI7IYgrMH_0VdmesBju5jpb4wse0/edit
[13:23] <Saviq> greyback, not yet, probably not today, either
[13:23] <greyback> Saviq: no rush
[13:23] <greyback> dandrader: your answer: not yet :D
[13:24] <greyback> dandrader: if you're idling, I've plenty of ideas still :)
[13:24] <dandrader> greyback, shoot
[13:24] <kgunn> guys...might want to tackle that trusty-touch releast day+1
[13:25] <kgunn> knowing Saviq might be close to melting
[13:25] <greyback> true
[13:27] <kgunn> hey speaking of trusty touch, i thot media hub was gonna land, and that would decouple music from this qt/egl block bug ?
[13:27] <Cimi> Saviq, I did set(qmltest_DEFAULT_PROPERTIES ENVIRONMENT "'QT_QPA_PLATFORM=minimal' 'LC_ALL=C'")
[13:27] <kgunn> ah waiting for QA signoff...
[13:28] <Saviq> Cimi, why did you put them in quotes?
[13:28] <Saviq> Cimi, in single quotes I mean
[13:28] <Cimi> Saviq, because otherwise QT_QPA_PLATFORM is "minimal lc_all=c"
[13:28] <Saviq> Cimi, but apparently I was wrong
[13:28] <Saviq> Cimi, they need to be semicolon-separated :|
[13:29] <Cimi> so "QT_QPA_PLATFORM=minimal;LC_ALL=C"
[13:29] <Cimi> i'll try
[13:29] <asac> kgunn: in the last two landing meetings rsalveti said that media is not ready; might be that we are now readyu and could take a shot
[13:30] <kgunn> asac: yep...was more curious than anything
[13:32] <Cimi> Saviq, I'm ready for a new bug
[13:32] <Cimi> had lunch... feeling fine
[13:34] <rsalveti> kgunn: asac: the qt thing would still be an issue afaik
[13:34] <rsalveti> it is at least when testing the silo
[13:34] <kgunn> rsalveti: absolutely...
[13:34] <rsalveti> I still need to unblank the screen to go to the next song
[13:35] <kgunn> rsalveti: oh...really...ok
[13:35] <kgunn> rsalveti: i meant i know it'd still be a global issue (e.g. alarms and such)...but thot the song advance would be fixed
[13:35] <asac> rsalveti: feels like a bug thogh, no?
[13:35] <asac> i mean the idea is that it continues playing through playlist
[13:35] <asac> even if the app is dead
[13:35] <kgunn> asac: apps not dead
[13:36] <kgunn> just screen off
[13:36] <asac> kgunn: no just sayuing that the lifecycle thing would in tehorry kill the app alltogether
[13:36] <asac> and media hub continues working
[13:36] <kgunn> thot is was whitelisted
[13:36] <asac> sure sure
[13:36] <asac> just saying that its a bug if mediahub requires application to do anything to continue playing next song
[13:37] <kgunn> oh i see
[13:37] <asac> so if the event loop bug that causes the app to stop causes mediahub to not forward to next song, there is something fishy in mediahub still
[13:37] <asac> but maybe i am missing something
[13:37] <rsalveti> oh, right, because ricmm still needs to finish the backgroundplaylist implementation
[13:37] <asac> right. so no playlist support yet
[13:37] <rsalveti> and then change music-app to use that
[13:37] <asac> makes sense then
[13:38] <rsalveti> not sure where we stand with that, will try to ping him
[14:01] <paulliu> Have anyone tried to run unity-mir on Desktop already? I got black screen. After one minute, it goes back to lightdm and system halts.
[14:08] <dandrader> should I see anything on the dash when I ./run unity8 on my desktop?
[14:10] <dandrader> damn. closed the unity8 window instead of ctrl+c. so, should I see anything on the dash when I ./run unity8 on my desktop?
[14:12] <mterry> Saviq, so launcher in tablet-greeter -- I don't recall offhand why the current code disallows it.  But it is rather explicit in code.  Do you remember?
[14:13] <Saviq> mterry, I think the binding there is broken then, it was only meant to be disallowed when account had pin/pwd
[14:13] <Saviq> mterry, if open, launcher should just work, as on phone
[14:14] <Saviq> mterry, now you mention it I remember I saw that some time before indeed
[14:14] <mterry> Saviq, why would we disable when locked?  I thought the interaction then would be show login prompt?
[14:14] <Saviq> mterry, yeah, that wasn't the plan before I think
[14:14] <Saviq> mterry, so yeah, rather legacy
[14:15] <mterry> Saviq, although now that I think about it...  The interaction was that we launch app in background while we show the prompt.  But that seems odd from a security perspective -- maybe we should wait to launch until authenticated.  But anyway
[14:16] <mterry> Saviq, OK, well I'll re-enable launcher in my branch then
[14:17] <mterry> Saviq, I think  it's ready for landing again, unless we want to hold off of Jouni's comments regarding the tease
[14:17] <Saviq> mterry, I kicked another landing already, so not before yesterday
[14:18] <mterry> yesterday?
[14:19] <Saviq> mterry, tomorrow ;)
[14:19] <Saviq> mterry, sorry, OnAir now, brain not working well ;)
[14:20] <mterry> Saviq, oh hah.  I'll let you alone then so you can devote all your grey cells  ;)
[14:26] <MacSlow> Saviq, ok... all needed changes (MRs) for the required version-bump are in place now. I hope I didn't overlook anything. Packages do build, if added depedencies are satisfied
[14:26] <Saviq> MacSlow, cool, thanks, will look at those tomorrow
[14:26] <MacSlow> Saviq, ok
[14:37] <Saviq> mhr3, good call on the qt event loop, I didn't notice the time there :)
[14:44] <greyback> dednick: that was an issue with mir around 0.1.7
[14:44] <greyback> dednick: or maybe 0.1.8. A fix landed definitely in mir/devel for it.
[14:45] <greyback> dednick: a workaround was to use LD_PRELOAD=/path/to/libmirserver.so
[14:57] <Saviq> paulliu, please let me know when you have the log out branches up for review, I think we can do without the prompt in unity8 for now, so make shortcuts if possible
[14:59] <paulliu> Saviq: ok.
[15:03] <tsdgeos> Saviq: any clue about this one? https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-trusty/1696/testReport/junit/%28root%29/qmltestrunner/tst_listviewwithpageheaderqml__compile/
[15:03] <dednick> mterry: is this it? lp:~mterry/mir/missing-links
[15:03] <Saviq> tsdgeos, huh
[15:03] <mterry> dednick, yes, sorry.  Got distracted in an IRC convo
[15:04] <dednick> mterry: no worries. it just missed 0.1.8 . which is why mine is not working :)
[15:04] <tsdgeos> Saviq: yeah that :D
[15:05] <mterry> dednick, I thought we backported it
[15:05] <paulliu> Saviq: I think I got problems testing my unity-mir code.
[15:05] <paulliu> Saviq: In what case that part of code will be executed?
[15:05] <mterry> dednick, I think it was backported in lp:mir, but maybe not lp:mir/devel
[15:05] <dednick> mterry: backported to lp:mir most likely
[15:05] <paulliu> Saviq: Running unity on mir?
[15:06] <Saviq> paulliu, yes, only on mir
[15:06] <mhr3> Saviq, i see de... things :)
[15:06] <Saviq> mhr3, devel?
[15:07] <Saviq> mhr3, that's mir :P
[15:07] <paulliu> Saviq: Strange things happened on my desktop. If I login by unity-mir from lightdm, I got black screen. It doesn't work. And strange things also happened if I switch to console and found that com.canonical.Unity.WindowStack is provided by window-stack-bridge in hud. Not the lib itself?
[15:07] <mhr3> Saviq, too late for 6th sense references? :)
[15:07] <Saviq> mhr3, yes, probably
[15:07] <Saviq> mhr3, dead where?
[15:07] <kiko> mhr3, ping?
[15:07] <mhr3> damn, i'm old :)
[15:08] <mhr3> kiko, pong
[15:08] <kiko> mhr3, an install from a freshly downloaded trusty iso has applications not showing up in the dash search
[15:08] <paulliu> And window-stack-bridge is bringed up by upstart sessions.
[15:08] <kiko> mhr3, so for instance, looking for "terminal" returns nothing in the applications category
[15:08] <Saviq> paulliu, on desktop window-stack-bridge talks to X11
[15:08] <kiko> though I do helpfully get offered the terminator movie
[15:08] <Saviq> paulliu, on phone unity-mir exposes them
[15:08] <kiko> mhr3, also, looking for gimp gives me a BSDM result in the top row
[15:08] <Saviq> tsdgeos, I get the same locally
[15:08] <kiko> which I found pretty avant-garde
[15:09] <mhr3> kiko, bsdm?
[15:09] <mhr3> kiko, also nothing changed there for the past 6months
[15:09] <Saviq> tsdgeos, "make -C builddir testlistviewwithpageheaderqml"
[15:09] <tsdgeos> Saviq: that is weird, i didn't change anything there, did I?
[15:09] <Saviq> tsdgeos, maybe the iterations thing?
[15:09] <kiko> mhr3, yeah, I take you are not into that sort of thing?
[15:09] <kiko> anyway
[15:09] <tsdgeos> Saviq: ok, i'll check
[15:09] <kiko> my point is that there is something weird
[15:09] <kiko> mhr3, what should I do to try and understand where the problem might come from?
[15:10] <paulliu> Saviq: for logout. Isn't that for X11 things?
[15:10] <Saviq> tsdgeos, actually no, the QmlTest.cmake changes
[15:10] <paulliu> Saviq: I think we want to fix Desktop versions?
[15:10] <mhr3> kiko, take a look if the scope processes are running
[15:10] <Saviq> paulliu, no, that's for a Unity8 on Mir session, desktop, not X11
[15:10] <tsdgeos> Saviq: they looked pretty safe to me :/
[15:10] <paulliu> Saviq: ok.
[15:10] <mhr3> kiko, then bustle log might show something
[15:10] <paulliu> Saviq: got it.
[15:10] <paulliu> Saviq: So my problem is shrinked. unity-mir doesn't run on my computer and I have to figure that out.
[15:11] <paulliu> Saviq: And window-stack-bridge shouldn't be there.
[15:12] <Saviq> paulliu, the latter probably doesn't matter
[15:12] <kiko> mhr3, there are 6 processes running with unity-scopes in their names, but I don't know if there is a special scope that needs to run for the application scope to function
[15:12] <Saviq> paulliu, but yeah, you need to have a unity8 on mir running somewhere
[15:12] <kiko> mhr3, what is the bustle log?
[15:12] <Saviq> paulliu, phone/tablet would be good enough, you'd just have to either call the dbus methods manually
[15:13] <paulliu> Saviq: ok
[15:13] <Saviq> paulliu, or change the indicator profiles to desktop, but yeah, ideally you'd test on desktop unity8+mir session
[15:13] <mhr3> kiko, app that records dbus traffic
[15:13] <kiko> mhr3, where do I look
[15:14] <mhr3> apt-get install bustle
[15:14] <kiko> mhr3, aha
[15:14] <mhr3> logout, login, ctrl+alt+t to run terminal, run `bustle`, start logging, press the super key
[15:16] <Saviq> tsdgeos, you need to pass "leftover" arguments down
[15:17] <Saviq> tsdgeos, ${ARGN} should work
[15:17] <tsdgeos> Saviq: yep, works, was doing just that
[15:17] <Saviq> tsdgeos, we'll land that fix separately, don't want to rebuild again
[15:18] <tsdgeos> Saviq: so you want a different branch?
[15:18] <Saviq> tsdgeos, same branch is fine
[15:18] <Saviq> tsdgeos, just that last revision will get in in the next landing
[15:18] <tsdgeos> if nothing breaks
[15:18] <tsdgeos> sure :)
[15:18] <tsdgeos> pushed
[15:18] <Saviq> yeah exactly
[15:25] <mterry> dednick, thanks for the indicator-sound fix for my stupid feedback loop.  Will test
[15:27] <dednick> mterry: :) no worries
[15:27] <dednick> bit of a tricky one that. the solution is a bit crap
[15:28] <mterry> dednick, could we send less updates?
[15:29] <dednick> mterry: yeah. i'm not sure why the desktop does so many. the slider only updates every second or so, but we still get a flood of changes in one batch. As for unity8, we need to put a throttle in for the slider. It throws them out in excess.
[15:30] <dednick> for the desktop, it seems to be queuing the events up, and then emitting events every second or so
[15:30] <mterry> dednick, I guess you do want live updates...  since the icon in the bar should match where the slider is
[15:30] <mterry> low-volume or high-volume icon at least
[15:30] <dednick> mterry: yeah, but maybe only every few hundred ms or so. we get dozens every time you change.
[15:31] <mterry> dednick, hmm so your branch listens less, but how hard is it to send less?
[15:31] <mterry> could still use the same timer thinking
[15:31] <dednick> mterry: it sends less as well.
[15:32] <mterry> oh ok
[15:32] <dednick> mterry: it sends to account services less, but keeps the local volume correct
[15:33] <mterry> dednick, I see.  So we only listen to AS after a second of changing our own
[15:34] <dednick> mterry: ya. all the receives are processed, but only in one update 1 second after the last receive
[15:34] <dednick> well, not all of them i mean. they're merged into a single update 1 second after the last receive
[15:35] <mterry> OK, well I have to eat lunch, but will test with it
[15:35] <dednick> mterry: ta
[15:41] <mhr3> kiko, will you attach the bustle log to the bug?
[15:45] <kiko> mhr3, one log out and back in and it's working unfortunately
[15:46] <mhr3> sucks
[15:56] <kiko> you said it
[15:59] <Cimi> Saviq, what's the right syntax for  set(qmltest_DEFAULT_PROPERTIES ENVIRONMENT "QT_QPA_PLATFORM=minimal" "LC_ALL=C") ?
[16:04] <tsdgeos> Saviq: so no, the binding loop was not causing the performance slow down, but at least it's gone now :D
[16:04] <tsdgeos> Cimi: what's wrong with that?
[16:04] <Cimi> tsdgeos, doesn't work here
[16:06] <mhr3> Cimi, "FOO=bar;QOO=baz"
[16:07] <Cimi> didn't work too
[16:07] <mhr3> we're using it
[16:07] <mhr3> so i'm pretty sure it does
[16:07] <tsdgeos> mhr3: that and the first is the same
[16:07] <tsdgeos> so "doesn't work" is probably "doesn't work somewhere else or doesn't do what i'd like it to do"
[16:08] <Cimi> cmake complains
[16:08] <Cimi> CMake Error at cmake/modules/QmlTest.cmake:154 (set_target_properties):
[16:08] <Cimi>   set_target_properties called with incorrect number of arguments.
[16:08] <Cimi> Call Stack (most recent call first):
[16:08] <Cimi>   cmake/modules/QmlTest.cmake:115 (add_qmltest_target)
[16:08] <Cimi>   tests/qmltests/CMakeLists.txt:16 (add_qml_test)
[16:08] <tsdgeos> right,so it's not the "set" that fails is just that set_target_properties doesn't like being called with a stringlist instead of a string it seems
[16:09]  * tsdgeos needs to go
[16:09] <tsdgeos> tty tomorrow
[16:09] <mhr3> Cimi, we're using
[16:09] <mhr3>         set_tests_properties(test${CLASSNAME}${_test}
[16:09] <mhr3>                 PROPERTIES ENVIRONMENT "QT_QPA_PLATFORM=minimal;LD_LIBRARY_PATH=${CMAKE_BINARY_DIR}/plugins/Unity:${LIBUNITYPROTO_LIBRARY_DIRS};UNITY_SCOPES_RUNTIME_PATH=${SCOPES_TEST_RUNTIME};UNITY_SCOPES_LIST_DELAY=5")
[16:09] <Cimi> mhr3, that's a different command
[16:10] <Cimi> set(qmltest_DEFAULT_PROPERTIES ENVIRONMENT ..
[16:10] <Cimi> not set_tests_properties
[16:10] <mhr3> ah, didn't notice that
[16:10] <mhr3> so perhaps use that :)
[16:12] <tsdgeos> whatthe
[16:12] <tsdgeos> search people stopped working in launchpad?
[16:12] <tsdgeos> mzanetti: that's yours
[16:12] <tsdgeos> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1308631
[16:12] <tsdgeos> mzanetti: search fails so can't assign it to you
[16:12] <tsdgeos> mzanetti: can you assign it to yourself?
[16:12] <mzanetti> tsdgeos: yes
[16:13] <dednick> hm. i used it a couple of hours ago
[16:13] <tsdgeos> same here
[16:13] <tsdgeos> but for some reason
[16:13] <tsdgeos> now it says "search team"
[16:13] <tsdgeos> instead of search people
[16:14] <tsdgeos> "Select a team of which you are a member"
[16:14] <tsdgeos> anyway
[16:14] <tsdgeos> tomorrow more
[16:49] <asac> kgunn: what is the unity8 thing fixing that we are landing?
[16:50] <asac> kgunn: is this worth risking not being able to get our browser fixed?
[16:50] <asac> we will not have time to do anything if anything is broken with this
[16:50] <kgunn> asac: which line ?
[16:50] <kgunn> silo ?
[16:51] <asac> kgunn: "Unity8 updates
[16:51] <asac> - test fixes
[16:51] <asac> - carousel last item fix
[16:51] <asac> - fix preview widgets
[16:51] <asac> - improve indicator startup
[16:51] <asac> - improve dev scripts
[16:51] <asac> - new default backgrounds
[16:51] <asac> - cleanup
[16:51] <asac> - first go at scope optimizations"
[16:51] <asac> kgunn: so just heard we can back it out in theory
[16:51] <asac> so lets do it
[16:51] <asac> will be super stressful, but can still be kicked out if we get someone testing the image coming out tonight
[16:51] <asac> so lets do it. worry
[16:51] <asac> soryy
[17:01]  * greyback_ gone out
[17:57] <mterry> dednick, commented on sound MP
[18:05] <dandrader> mterry, on the phone, what's the Lockscreen and what's the Greeter?
[18:05] <mterry> dandrader, greeter is what you're used to
[18:06] <dandrader> mterry, so Greeter is the thing showing that circular graph?
[18:06] <mterry> dandrader, Lockscreen is the bit that shows the pin/password entry (after swiping away greeter)  -- those bits aren't enabled on the image yet -- they need the split greeter
[18:06] <mterry> dandrader, yeah
[18:06] <mterry> dandrader, (the infographic)
[18:06] <dandrader> ok, thanks
[18:23] <dednick> mterry: thanks. i'll take a look tomorrow morning


[19:31] <lubot1> Juan Carlos was added by: Juan Carlos
 Welcome!
[19:33] <lubot1> <Juan Carlos> Thanks !!
[19:36] <lubot1> <Juan Carlos> Hello everyone !! I have a laptop and I do not know whether to install Lubuntu or Xubuntu
[19:37] <wxl> @Juan Carlos #lubuntu is generally the right place for support, but the difference is that Lubuntu is meant to have the smallest possible footprint
[19:37] <lubot1> <Juan Carlos> Which one do you recommend?
[19:38] <lubot1> <Juan Carlos> The laptop has 1Gb of RAM and 150 GB of hard disk
[19:39] <lubot1> <Juan Carlos> Windows 10 is installed, but not official
 This channel is for development not support.
[19:39] <lubot1> But both are great Lubuntu just needs less resources I flip flop between the two
[19:40] <lubot1> <Juan Carlos> Ok, thanks
[19:41] <lubot1> <Juan Carlos> Do you know if there is a specific Telegram channel of Linux?
[19:41] <wxl> well if you get on Freenode IRC, you can go to ##linux
 No there is not they usually do it in IRC and message groups
[19:42] <wxl> the open source world, in general, uses IRC. Telegram, Matrix, Slack, etc. is secondary at best
[19:42] <wxl> for example, here we have Telegram bridged to our IRC channel but THE place for chat is the IRC
 hundreds of non-geek users are panicking because of the repos shutting down
[20:52] <wxl> huh?
 a more "human readable" message would be fine, instead of "network error updating" when they have internet
 17.04 users, I mean
[20:53] <wxl> oh yeah
 all my "guinea pigs" around here (friends with Ubuntu) are giving me that feedback
[20:54] <agaida> life can be hard
 indeed
 specially dealing with git+lp!!! O___O
[20:56] <agaida> solution: uses salsa.debian.org ...
[20:58] <agaida> hmm - the latest changes in the packages was great - ok, settings are still not found, but a lot less crap
 which ones?
[20:59] <agaida> just a second
 º__º
[21:02] <agaida> last changelog entry for lubuntu-meta 0.88
[21:02] <agaida> or so
 mhm
[21:03] <agaida> or what it was - no lightdm on bionic anymore (lubuntu-next) - sddm is used
[21:03] <agaida> ok, unconfigured aka sddm-theme-maui
 yayy!
 wait. what theme is sddm using?
[21:04] <agaida> simple soulution would be to rename the release - but please not paintitblack - we use it at siduction
[21:04] <redwolf> yes
[21:04] <agaida> back in black would be a good choice :P
[21:05] <redwolf> but does it have any theme / visual configuration?
[21:05] <redwolf> file? I mean
[21:05] <agaida> i will have a look
[21:06] <redwolf> I think I experimented with this one: https://en.wikipedia.org/wiki/Simple_Desktop_Display_Manager#/media/File:Simple-desktop-display-manager.jpg
[21:06] <redwolf> but it has changed since that
[21:06] <agaida> that is maui
[21:07] <agaida> but yes, it has changed a lot
[21:07] <redwolf> showing all the users is nice
[21:07] <redwolf> but not that way
[21:07] <redwolf> this is lively: https://i.imgur.com/UY8yOwm.png
[21:08] <redwolf> *lovely
[21:09] <agaida> i would use it - only one reason - i don't like userlists displayed and also don't like if DMs remember the last user
[21:09] <agaida> but - for anyone who like it - nice
[21:09] <redwolf> but end-users usually like that
[21:10] <redwolf> I admit it's handy, just typing the password+enter and it logs in
[21:10] <agaida> end users also use luks encrypt and place their decryption pass in some scripts ...
[21:10] <redwolf> XD
[21:11] <redwolf> I wonder if I can change the average avatar picture
[21:12] <agaida> create a faces dir iirc
[21:13] <redwolf> I need to study. I want to make some Lennys as available avatars
[21:14] <redwolf> I want to do a lot of things for this release and I'm not sure if we're in time
[21:15] <agaida> http://paste.debian.net/1007401/ - so the list of installed packages is cleaner now
[21:16] <redwolf> :)
[21:16] <agaida> maybe one should add the l10n packages - all non english speaking users would be grateful
[21:16]  * agaida think - only a wild guess
[21:16] <redwolf> yes, I like my OS in Swedish :D
[21:17] <agaida> ah - btw
[21:17] <agaida> System:    Host lubuntu-next Kernel 4.13.0-25-generic i686 bits 32 Desktop LXQt
[21:17] <agaida>            Distro Ubuntu Bionic Beaver (development branch)
[21:17] <agaida> Machine:   Device oracle System innotek product VirtualBox v 1.2 serial N/A
[21:17] <agaida>            Mobo Oracle model VirtualBox v 1.2 serial N/A BIOS innotek v VirtualBox date 12/01/2006
[21:17] <agaida> CPU:       Quad core AMD FX-8350 Eight-Core (-MCP-) speed 4294 MHz (max)
[21:17] <agaida> Graphics:  Card InnoTek Systemberatung VirtualBox Graphics Adapter
[21:17] <agaida>            Display Server x11 (X.Org 1.19.5 ) drivers (unloaded: fbdev,vesa) FAILED modesetting
[21:17] <agaida>            Resolution<EMAIL_ADDRESS>[21:17] <agaida>            OpenGL renderer llvmpipe (LLVM 5.0, 128 bits) version 3.3 Mesa 17.2.4
[21:17] <agaida> Network:   Card Intel 82540EM Gigabit Ethernet Controller driver e1000
[21:17] <agaida> Drives:    HDD Total Size 10.7GB (37.7% used)
[21:17] <agaida>            ID-1 model VBOX_HARDDISK
[21:17] <agaida> Info:      Processes 142 Uptime 22 min Memory 494.3/8091.0MB Client Quassel v0.12.4 inxi 2.3.56
[21:17] <agaida> only a "little" backtrace at start - but no kernel panic
[21:18]  * krytarik slow-claps..
[21:19] <redwolf> oh, krytarik! you still alive after your "Lubuntu support shift" yesterday  XDDD
[21:20] <agaida> redwolf: do i need any additional packages - i have lubuntu-default-settings and lubuntu-live-settings
[21:20]  * redwolf sips tea
[21:20]  * redwolf wonders if there're already separated settings for Qt and gtk desktops
[21:20] <agaida> no - and i found lxqt in /etc/xdg
[21:21] <redwolf> :'(
[21:21] <agaida> so let's dig a little bit deeper
[21:21] <agaida> hmm - in xdg/lxqt are only the globalkeyshortcuts.conf - and thats fine
[21:22] <agaida> the only configuration i don't have moved right now
[21:22] <redwolf> agaida, is "lxqt-config-appearance" in "lxqt-config" ?
[21:22] <agaida> it is
[21:22] <redwolf> nice then
[21:23] <agaida> no, not nice
[21:23] <redwolf> you also included lxappearance
[21:23] <agaida> no - but it should be for the time being
[21:23] <redwolf> aye
[21:24] <agaida> or obconf-qt
[21:24] <agaida> dunno if lxappearance do things that obconf and obconf-qt can't do
[21:24] <redwolf> gtk
[21:24] <redwolf> ergo icons, toolbar buttons, text...
[21:26] <redwolf> themes should be qt+gtk always, and not even listing those imcomplete. and like Budgie, when you apply a theme, it applies for everything. at once.
[21:27] <redwolf> so, only one tool to configure appearance. but that's my personal trauma.
[21:27] <agaida> at least four tools
[21:27] <agaida> or five
[21:28] <redwolf> too many :(
[21:28] <agaida> echo, cat, vi, nano :P
[21:28] <redwolf> -___-
[21:28] <agaida> not to forget sed
[21:28] <redwolf> I kinda like nano, but I always tend to press f10 to show menus :|
[21:29] <wxl> ugh nano
[21:29] <redwolf> :)
[21:31] <wxl> i have a co-worker that's expressed interest in better making use out of the shell
[21:31] <wxl> i mean, like, he's new.
[21:31] <wxl> he still couldn't figure out how to get out of nano though :)
[21:31] <redwolf> XD
[21:31]  * agaida miss zsh as standard shell
[21:31] <wxl> it's not exactly intuitive
[21:31] <agaida> strg x is intuitive
[21:32] <agaida> better then <esc>q
[21:32] <agaida> upps
[21:32] <redwolf> never do that in nano :D
[21:32] <redwolf> it's like vim. you have to fire a missile to the computer to exit
[21:32] <redwolf> it's the only way XD
[21:33] <wxl> i've done some remapping in vim so to escape insert mode, save and quit, all i do is ,,
[21:33] <agaida> esc :q!
[21:33] <agaida> erm - ok intuitive
[21:34] <redwolf> I'm still looking for some visual-basic / msedit editor clone for linux
[21:34] <wxl> the reality is there *IS* no intuitive editor
[21:34] <redwolf> console, but with menus and all
[21:34] <wxl> including nano
[21:34] <redwolf> no, nano is alien
[21:34] <wxl> ummm
[21:34] <redwolf> remember that default editor for ms-dos 5/6?
[21:34] <wxl> isn't there a midnight commander for cli that has an editor built in?
 remember that default editor for ms-dos 5/6?
[21:35] <redwolf> damn
[21:35] <redwolf> https://i.stack.imgur.com/dJQOG.png
[21:36] <redwolf> fp, it seems
[21:36] <redwolf> https://askubuntu.com/questions/42453/equivalent-text-editor-to-ms-dos-editor
[21:36] <agaida> mcedit
[21:36] <agaida> yes
[21:37] <agaida> wxl - belive it or not - we had a short term user that want us to make a "native",  "original" Xfce
[21:37] <redwolf> huh?
[21:37] <agaida> without mc mcedit "and such crap" installed
[21:38] <agaida> so - not a solution :D
[21:38] <wxl> https://en.wikipedia.org/wiki/Midnight_Commander
[21:38] <wxl> that's what i was thinking of
[21:38] <wxl> but it uses $EDITOR
[21:39] <wxl> at least in ubuntu
[21:39] <wxl> upstream appears to have an actual editor https://www.gnu.org/software/mc/images/mc-edit-perl.png
[21:39] <wxl> oh
[21:39] <wxl> and that's mcedit
[21:39] <wxl> derp
[21:39] <wxl> but that's not the same as what redwolf was talking about
[21:40] <agaida> apt-file list mc
[21:40] <wxl> fp-ide looks pretty nice
[21:51] <agaida> ok - regarding the settings - look fine for the beginning - but someone should change some install pathes
[21:51] <agaida> redwolf: as i said - no problem
[21:54] <redwolf> :)    :*
[21:55] <agaida> i will file a bug with patch
[21:55] <agaida> not really a problem
[21:55]  * redwolf licks agaida
[21:55] <agaida> hihihi
[21:57] <agaida> and btw
[21:57] <agaida> 2018-01-26  14:00:35 <BTS> featherpad (NEW) 0.7-1 uploaded by Alf Gaida<EMAIL_ADDRESS>(Closes: #869730) https://tracker.debian.org/featherpad
[21:58] <agaida> 2018-01-26  14:03:30 <BTS> Closed #869730 in wnpp by Alf Gaida<EMAIL_ADDRESS>«ITP: featherpad -- FeatherPad is a lightweight Qt5 plain-text editor for Linux». https://bugs.debian.org/869730
[21:58] <redwolf> I like it: https://github.com/tsujan/FeatherPad
[21:59] <agaida> still a lot to do
[21:59] <redwolf> there it is: kvantum working :)
[21:59] <redwolf> oh and it has hamburger menu too!
[21:59] <agaida> my only problem with quantum - i don't like dark themes that much
[21:59] <agaida> kvantum
[22:00] <redwolf> then don't use them
[22:00] <redwolf> ;)
[22:00] <agaida> right
[22:00] <redwolf> kvantum has lots of sets preinstalled
[22:01] <agaida> if i find the time i should make a package
[22:01] <redwolf> for kvantum?
[22:01] <agaida> why not
[22:01] <redwolf> https://github.com/tsujan/Kvantum/releases
[22:02] <agaida> first rule- never ever let programmers do packaging
[22:02] <redwolf> :D why? poor things
[22:02] <agaida> second rule - never ever let programmers do packaging
[22:02] <redwolf> aren't both the same rule?
[22:03] <agaida> no, not really
[22:03] <agaida> the second rule is far more important
[22:03] <redwolf> mhm
[22:03] <redwolf> well, if you did a kvantum package for the seed, it'd be ok for me :) and you're a coder
[22:03] <agaida> oh - i forget the ". Really - never!"
[22:04] <redwolf> omg, sfte is soooo nice! it's like the good old wordstar
[22:05] <agaida> nope - i'm only an old grumpy guy - and our devs panic if i try to be a programmer
[22:05] <redwolf> not so old ;)
[22:05] <agaida> nearly 49
[22:06] <redwolf> perfect :)
[22:06] <agaida> hihihi
[22:06] <redwolf> still sexy!
[22:11] <agaida> yeah, my wife say this too - from time to time :P
[22:13] <agaida> is there a pull requst workflow on launchpad with git?
[22:15] <agaida> cool, the installer fails
[22:15] <redwolf> :)
[22:16] <agaida> or better: apt fails with a script bug in initramfs-tools
[22:18] <agaida> and the installed system paniced with the usual kernel panic for i386 - damn, i should download a sane amd64 iso
[22:20] <agaida> done
[22:22] <redwolf> O.O
[22:23] <agaida> the mirror was fast today- 25M
[22:25] <agaida> and i should mount my vbox dir to ssd
[22:25] <agaida> damn slow
[22:31] <agaida> ok - the initramfs bug isn't exactly nice- the amd64 segfaults too
[22:31] <agaida> installation - and i hate chrooting in just installed systems
[22:38] <agaida> bug found - whoever thought that it would be a good idea not to install ttf-dejavu - no, it wasn't
[22:40] <agaida> plymouth hook in initramfs-tools fails with dejavu not found - no created initramfs, not nice system start
[22:54] <redwolf> why not just jumping to another font?
[22:58] <agaida> erm - if the initramfs is not created, the system don't start
[22:58] <agaida> and my most hated program need dejavu in it's hoolk
[22:59] <agaida> but with a little bit good will - the installed system finally give up and start into an nice black screen
[22:59] <agaida> CPU~Quad core AMD FX-8350 Eight-Core (-MCP-) speed~4294 MHz (max) Kernel~4.13.0-25-generic x86_64 Up~5 min Mem~360.7/7974.8MB HDD~10.7GB(44.8% used) Procs~145 Client~Quassel v0.12.4 inxi~2.3.56
[22:59] <agaida> System:    Host lnext Kernel 4.13.0-25-generic x86_64 bits 64 Desktop LXQt
[22:59] <agaida>            Distro Ubuntu Bionic Beaver (development branch)
[22:59] <agaida> so what
[23:00] <agaida> but it should be fixed
[23:00] <redwolf> oh right
[23:02] <agaida> but hey - after a bit chrooting and a bit normal magic the system runs fine
[23:02] <agaida> just installing git, devscripts and debhelpers
[23:02] <agaida> -s


[06:51] <dholbach> good morning
[06:53] <jose> hello, dholbach!
[06:54] <bkerensa> dholbach: good morning
[06:56] <dholbach> hi jose, hi bkerensa
[06:56] <jose> all going good?
[06:56] <MooDoo> hello all
[06:56] <dholbach> yep - how about you?
[06:58] <elfy> morning all
[07:00] <bkerensa> elfy: morning
[07:07] <jose> I'm good, long day
[07:07] <jose> hey elfy, long time no see
[07:07] <elfy> hi bkerensa jose
[07:08] <elfy> jose: heh - I'm always somewhere :)
[07:08] <jose> true
[07:14] <dpm> morning all
[07:16] <elfy> dpm: hi
[07:17] <dpm> hey elfy
[07:19] <silverlion> o/
[07:20]  * jose goes to bed
[07:26] <elfy> night night :)
[07:43] <davidcalle> Morning all
[07:44]  * dholbach relocates to the office, brb
[08:22] <dholbach> popey, dpm, balloons, mhall119, davidcalle: any reason why the Q&A was moved to 17 UTC?
[08:22] <dholbach> now it stops at 20:00 my time
[08:22] <dholbach> which would be the second time in the week where I work until 20:00 which I'm really not looking forward to :-/
[08:23] <dpm> dholbach, no idea, I'd rather move it to 15:00UTC as it was when we originally scheduled it the first time
[08:23] <dholbach> <3
[08:23] <dholbach> I guess that'd conflict with our standup
[08:23] <dholbach> maybe that's why it was moved(?)
[08:24] <dpm> I don't know
[08:25] <dpm> happy to move it
[09:07] <silverlion> gosh. can somebody tell that guy on the mailing list to stop wasting our time?
[09:11] <dholbach> if you want to make yourself heard, write to the list
[09:18] <silverlion> dholbach: I would love to but I think I'd better not because my fear is that those words which are in my mind right now - would act as an insult
[14:21] <balloons> wow, where did may go?
[14:22] <knome> balloons, home
[14:26] <knome> and if you didn't notice, there's still almost a week of it left :P
[14:51] <balloons> knome, I didn't!
[14:51] <balloons> weeee!
[14:52] <elfy> there is ALWAYS a bonus - regardless of what other people might see or think
[15:12] <davidcalle> balloons, not sure if you know about it, but there is an incoming scopes branch with a python-harness tutorial inside, could be interesting for you https://code.launchpad.net/~stolowski/unity-scopes-shell/sphinx-docs
[15:13] <balloons> davidcalle, awesome.. that's what I was waiting for from Pawel
[15:13] <balloons> with docs <3
[15:13] <davidcalle> balloons, don't tell him I'm spying on his branches! :p
[15:13] <balloons> davidcalle, hehe.. nice to have an insider!
[15:16] <cprofitt> 8/names
[15:31] <jose> hey guys, anyone around here knows how to make an rt ticket urgent? I'm not able to send emails to ANY mailing list, and kinda need that...
[15:32] <knome> jose, i guess poke #canonical-sysadmin
[15:32] <jose> knome: no one on vanguard, already checked :(
[15:32] <knome> call mr. shuttleworth then
[15:32] <knome> :P
[15:32] <jose> phone's busy :(
[15:33]  * jose scratches head
[15:33] <knome> then you got no other chance than to retry aforementioned options
[15:33] <mhall119> jose: what's going on?
[15:36] <jose> mhall119: I can't send emails to any mailing list, reasons unknown
[15:36] <jose> I don't get any error messages or anything, but my emails don't go through
[15:37] <mhall119> jose: do you have an RT#?
[15:37] <jose> no, was thinking there was maybe a way to mark it as urgent, but I can file one noe
[15:40] <popey> jose: how do you know they aren't getting through, and can you give an example of a list this happened on?
[15:41] <jose> popey:
[15:41] <jose> Yesterday I was sending emails to ubuntu-news, loco-contacts and ubuntu-news-team as usual, but none of my emails went through (I had someone on the other side of the list check) or were archived. Same happened with ubuntu-pe, there are some emails are sent that are not on the archives.
[15:42] <jose> mhall119: rt.u.c#26584
[15:43] <jose> on ubuntu-news my email didn't go to the moderation queue and I checked with Lyz and she didn't get any emails, then I tried with the other two but same happened, no emails were sent out even though I contacted the list
[15:45] <popey> jose: has anything changed? I mean, you sending from a different address?
[15:45] <jose> popey: nope, still<EMAIL_ADDRESS>[15:45] <jose> same PC, same email cline
[15:45] <jose> client*
[15:46] <popey> does that address receive mail?
[15:46] <jose> it does
[15:46] <popey> i just sent you a test mail, can you reply?
[15:47] <jose> reply sent
[16:19]  * balloons waves to jono
[16:20] <jono> howdy balloons!
[16:31] <mhall119> jose: FYI, I'm trying to find someone to look into this for you
[16:32] <jose> mhall119: cool, thanks a bunch!
[16:33] <mhall119> jono: FYI, kubuntu-council as an entity has existed for a very long time, it's not a new thing
[16:33] <jono> mhall119, that's what I thought
[16:35] <mhall119> shadeslayer was proposing a change to it's constitution
[16:37] <jono> ahh
[16:41] <balloons> and indeed the proposed changes were adopted
[17:17] <balloons> jcastro, nice comment on http://www.reddit.com/r/Ubuntu/comments/37bedk/can_we_please_get_an_easier_way_to_submit_bugs/
[17:21] <jcastro> hah
[17:21] <jcastro> it would be nice if we could just get apport to stfu though
[17:21] <jcastro> I've only ever seen it hang up on junk in /var/crash
[17:22] <jcastro> someone needs to ttl that stuff
[17:22] <balloons> jcastro, bdmurray landed stuff to apport that should have shut it off for lts
[17:22] <balloons> that's been a bit, so I'm sad to see this post again
[17:24] <jcastro> I would just like it never to show up
[17:24] <jcastro> just do the background thing
[17:25] <balloons> right exactly. Unless you experienced something needing attention it really isn't supposed to appear
[17:26] <balloons> but I agree with your statement about how to "solve" the problem. Automated reporting and better testing
[17:31] <jcastro> I don't think I've had to manually file a bug in years
[17:31] <jcastro> well, for a defect anyway
[17:31] <jcastro> wishlist and others, then sure. :D
[20:40] <jose> mhall119: did you get anyone available on IS?
[22:37] <mhall119> jose: not yet, there doesn't seem to have been a vanguard all day
[22:37] <jose> weird
[22:37] <mhall119> jose: there's one there now, let me see if I can get some action on your rt
[22:38] <jose> woot woot, thanks
[22:39] <mhall119> np
[23:10] <mhall119> jose: all good now?
[23:10] <jose> mhall119: yup, looks like it was an unnoticed error on my side. thank you!
[23:10] <mhall119> np


[00:01] <Unit193> knome: Please to check listadmin.
[00:01] <knome> which one? :P
[00:02] <Unit193> floppies on -users, other crap on -devel.
[00:02] <knome> yeah...
[00:02] <knome> i've been watching those.
[00:02] <Unit193> !info listadmin
[00:11] <knome> nah.
[00:28] <knome> ok, sleepytime
[00:28] <knome> nighty!
[02:30] <bluesabre> evening all
[02:44] <bluesabre> menulibre 2.0.7 released https://launchpad.net/menulibre/+milestone/2.0.7
[03:40] <Unit193> Logan: Not alive right?
[03:41] <Logan> hi
[03:41] <Unit193> \o/
[03:41] <Unit193> Care to sync virtualbox-ext-pack from exp?
[03:42] <Logan> sure
[03:42] <Unit193> Yey!
[03:42] <Unit193> Danke.
[03:43] <Logan> bitte'
[03:56] <bluesabre> oh hey Unit193
[03:57] <bluesabre> safe to assume pinentry-gtk2 needs to be in core?
[04:27] <Unit193> bluesabre: pinentry-gnome3 is pulled in now.
[04:27] <Unit193> Are we switching to -gtk2?
[04:27] <bluesabre> it seemed like that might be preferable, or do we care?
[04:28] <Unit193>   * Temporarily (until Debian bug #791411 is fixed) allow other pinentry
[04:28] <Unit193>     methods to satisfy our dependency.
[04:29] <Unit193> If we can, I'd say -gtk2 yeah.
[04:30] <bluesabre> I'll go ahead and swap that in tomorrow.  While xfce is predominantly gtk2, I think we'd be better with that
[04:31] <Unit193> I love the GNOME response: No, we want pinentry-gnome3 for GNOME, since only that provides a proper
[04:31] <Unit193> UI/replacement for the builtin prompter.
[04:32] <bluesabre> :)
[04:33] <Unit193> bluesabre: If you want -gnome3, then do nothing.  If you want gtk2, then add that.
[04:34] <bluesabre> right
[04:34] <bluesabre> I got that
[04:34] <bluesabre> :D
[04:36] <Unit193> (Recommends of course, if you do. :P )
[04:36] <Unit193> OK, great.
[04:36] <bluesabre> mhm
[04:37] <bluesabre> ochosi: xfpanel-switch in -staging, experimental panel building in my ppa https://launchpad.net/~bluesabre/+archive/ubuntu/experimental
[04:37] <bluesabre> going to test it in the morning with a vm
[04:37] <bluesabre> installing the panel from today messed all sorts of things up
[04:37] <bluesabre> :)
[04:37] <bluesabre> tired
[04:38] <bluesabre> night all
[04:38] <Unit193> G'night.
[06:27] <Logan> Unit193: it's now in the new queue
[08:25] <knome> pleia2, feel free to drop sqlite stuff from the server, it's not needed any more
[08:27] <knome> now i just need to figure out why the new cron stuff isn't running :D
[08:28] <knome> oh, right...
[08:28]  * knome facepalms
[08:28] <Unit193> chronic is handy.
[08:28] <knome> no, it's a fail in includes
[08:31] <knome> i'm trying to include a file that doesn't exist...
[08:31] <knome> now it works nicely again
[12:10] <bluesabre> ochosi: did you send the latest version of the patch after your "aha" moment?
[12:12] <bluesabre> (doesn't seem to be working for me)
[12:14] <bluesabre> also of note... http://i.imgur.com/xgt0QWk.png
[12:18] <bluesabre> probably related, http://paste.ubuntu.com/12038986/
[12:21] <knome> heh, there's something fishy going on
[12:22] <knome> i export the flyers as pdf
[12:22] <knome> and the a4 with text rendered as paths is 1.7MB while all the other exports are 650kBish
[12:23] <knome> yes, i also checked the partial exports, they are all "in line", no weird things there
[12:23] <bluesabre> sounds fun
[12:28] <knome> yep
[12:38] <knome> hah
[12:38] <knome> changing the pdf compiling lib doesn't help
[12:39]  * knome shrugs
[12:41] <bluesabre> pffffffff
[12:41] <bluesabre> er
[12:41] <bluesabre> pdfffffffff
[12:42] <knome> hah
[12:42] <knome> i guess i could dump raw pdf output to files
[12:42] <knome> but meh
[12:42] <knome> really...
[12:51] <flocculant> afternoon
[12:52] <knome> hello flocculant
[12:52] <flocculant> hi knome
[12:57] <bluesabre> hey flocculant
[12:58] <flocculant> hi bluesabre :) just looking at ppa:bluesabre/experimental for panel
[12:58] <bluesabre> flocculant: don't use that one
[12:58] <bluesabre> it seems to be dead in the water
[12:58] <flocculant> ok :D
[12:58] <bluesabre> ochosi: poke
[12:59] <bluesabre> :D
[12:59] <flocculant> tried again this morning with the backup dooby - still get errors about things that aren't there - but which are
[13:00] <flocculant> also the close/save etc dialogues appear a bit dodgy here
[13:01] <bluesabre> those are "normal" gtk3 dialogs
[13:01] <knome> aka dodgy
[13:01] <bluesabre> can you paste the errors you're getting?
[13:01] <flocculant> well
[13:01] <flocculant> when I say dodgy I mean - they don't appear to work :p
[13:01] <bluesabre> oh
[13:02] <bluesabre> normal gtk3 to some degree ;)
[13:02] <flocculant> ha ha ha
[13:03] <flocculant> http://pastebin.com/uga4BfUT
[13:03] <flocculant> see FIleNotFoundErrror - then see it in the last command
[13:04] <knome> if you people just keep adding new work items, we'll never "get there"!
[13:04] <bluesabre> I'm trying to not add new ones
[13:05] <bluesabre> aha
[13:05] <bluesabre> flocculant: I see the issue
[13:05] <bluesabre> /.config/xfce4/panel/launcher-2/14391034521.desktop
[13:05] <bluesabre> that does not exist
[13:05] <bluesabre> ~/.config/xfce4/panel/launcher-2/14391034521.desktop
[13:05] <bluesabre> does
[13:05] <bluesabre> right?
[13:07] <flocculant> ... didn't see the missing ~
[13:08] <bluesabre> :)
[13:08] <bluesabre> I'll look into fixing that shortly
[13:08] <flocculant> ok
[13:08] <bluesabre> trying to kill off tasks today
[13:08] <flocculant> seems to be working - more or less now too
[13:09] <bluesabre> knome: is there anything particularly "wrong" about rearranging the work items on the blueprint?
[13:10] <bluesabre> like, into TODO, INPROGRESS, BLOCKED, DONE, POSTPONED
[13:10] <flocculant> small point - Save config button - dialogue - save config button for new panel - once you're finished - there's not a way to close that - other than X
[13:10] <flocculant> also Cancel - and I would expect that dialogue to close for me
[13:14] <bluesabre> yeah, there's probably tons more usability issues with that app
[13:14] <bluesabre> pushed it out quickly
[13:14] <flocculant> bluesabre: I'll pay about with it a make a list of what I see that seems odd
[13:14] <flocculant> a/pay/play
[13:14] <flocculant> s even
[13:14] <bluesabre> flocculant: thanks!
[13:15] <bluesabre> not going to get to xfce4-keyboard-overlay this cycle... if ever
[13:18] <flocculant> uninstalled the panel switch from yesterday - installed the one from staging
[13:20] <flocculant> bluesabre: is that better to use than the bzr method ochosi pointed at?
[13:21] <knome> bluesabre, no, that would likely be a better order anyway
[13:25] <knome> bluesabre, would you like the email reminders?
[13:26] <bluesabre> knome: yes please
[13:26] <knome> daily or weekly?
[13:26] <bluesabre> flocculant: yeah, I just hadn't packaged it until last night
[13:26] <bluesabre> knome: daily please
[13:27] <knome> bluesabre, ok, you're set up!
[13:28] <knome> bluesabre, and the status order should now be what you proposed
[13:29] <bluesabre> knome, cool, thanks
[13:30] <flocculant> bluesabre: ok - just sorting a mail for testers
[13:30] <knome> flocculant, you fancy reminder emails?
[13:30] <flocculant> not currently - I'm on top of blueprint
[13:30] <knome> ok ;)
[13:30] <flocculant> or at least know what's there :D
[13:30] <knome> just poke me if you need them later
[13:31] <flocculant> knome: does the mail just go for things not started?
[13:31] <knome> it sends a list of all your (not your teams') work items that are TODO, INPROGRESS or BLOCKED
[13:32] <flocculant> mmk
[13:33] <knome> how i see it, it's not just a nag about "get these done", it's also a reminder to close the open work items
[13:33] <flocculant> :)
[13:33] <bluesabre> knome: thanks for the new order, I was actually suggesting rearranging the blueprint itself around (for dev), that won't break anything, right?
[13:34] <knome> ahhh
[13:34] <knome> no, not at all
[13:34] <bluesabre> cool
[13:34] <knome> fwiw, it's just a blob of text that is parsed by the tracker
[13:34] <knome> fortunately, LP does the nagging about wrong syntax
[13:35] <knome> so i can just take it, split it into lines and then to db columns
[13:35] <bluesabre> cool
[13:35] <knome> (yeah, since it's a blob, every time i'm pulling it, i'm removing the old rows and adding the new ones...)
[13:35] <bluesabre> much cleaner, https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-w-development
[13:36]  * knome shrugs
[13:36] <knome> tbh, with the new tracker, i barely even look at the LP work item boxes
[13:36] <knome> i just go edit it there
[13:36] <bluesabre> yeah
[13:36] <bluesabre> the new tracker is super nice
[13:36]  * knome bows
[13:36] <knome> i'm happy it's useful for other people too
[13:36] <bluesabre> I've been motivated by it and been trying to get things done
[13:37] <knome> haha, yes, that's what the rationale for the burndown is ;)
[13:38] <flocculant> knome: reminder to reply to https://lists.ubuntu.com/archives/xubuntu-devel/2015-August/010843.html
[13:38] <knome> flocculant, thanks
[13:38] <knome> i'll go do that now
[13:41] <bluesabre> bbiab, gotta go get groceries
[13:42] <flocculant> bluesabre: cya another day if I've wandered off
[13:44] <knome> flocculant, ok, replied
[13:44] <knome> now, lunch-dinner
[13:44] <flocculant> good reminder - I'm ravenous
[13:45] <flocculant> knome: thanks for reply
[13:47] <flocculant> knome pleia2 - if I could have the daily image mail sociall mediaed that'd be good :)
[13:57] <knome> tweeted
[14:08] <knome> hmph, the status for the bug entries isn't shown
[14:11] <knome> i'll look at that later today or tomorrow
[14:12] <knome> i'm off
[14:12] <knome> hf and ttyl
[14:38] <bluesabre> seeya knome
[14:58] <bluesabre> Unit193: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1473952 :)
[15:00] <bluesabre> knome: and yeah, the tracker will look even nicer when fixed bugs are crossed off :)
[15:45] <bluesabre> almost there... today's image has elementary and human libreoffice themes
[15:45] <bluesabre> yesterday we also had galaxy
[15:47] <bluesabre> elementary is default, so we're doing pretty well there
[15:50] <bluesabre> suppose the next step is getting to be an alternative on the libreoffice packages
[15:51] <pleia2> knome: that was quick :) removing sqlite3 stuff now
[15:52] <pleia2> woo, and tracker still works
[15:55] <bluesabre> :D
[15:57] <pleia2> flocculant: fb and g+ done
[15:58] <pleia2> knome: I'm going to remove the linkedin link from the website
[16:55] <Unit193> bluesabre: \o/
[17:47] <flocculant> pleia2: much obliged
[18:50] <ochosi> bluesabre: that looks like fun. actually i sent you the last version, after my a-ha moment, the one that worked for me.
[18:51] <ochosi> bluesabre: also, i built my patch on xfce4-panel git master, maybe that's part of the problem
[18:56] <ochosi> bbl
[19:28] <pleia2> tracker site makes me happy :)
[20:17] <knome> pleia2, yep, go ahead
[20:25] <ochosi> pleia2: +1
[20:31] <knome> hhheeey, now bugs can be WIP/DONE in tracker
[20:31]  * knome went and fixed a minor bug
[20:44] <ochosi> burndown is looking better again
[20:44] <knome> yep
[20:45] <ochosi> bluesabre: maybe you can re-try my patch with git master in your wily vbox
[20:45] <ochosi> otherwise i can also look at the panel patches we ship
[20:45] <ochosi> knome: i'm not sure how to make sense of that yet or how to present it, but linking up workitems to deadlines would be nice
[20:46] <ochosi> like everything in -artwork > UIF
[20:46] <ochosi> and some things in -dev > FF
[20:46] <knome> right...
[20:48] <ochosi> maybe in terms of email reminders
[20:48] <knome> but if it's just for the email reminders, then i'm not sure if it's worth it to figure that out
[20:50] <ochosi> yeah
[20:50] <ochosi> true that
[20:50] <ochosi> bbabl
[21:37] <knome> ok, there's a bit wiser algorithm for bug status assignment
[21:37] <knome> 1) if statuses for all bugs are 'Fix Released', the status is 'DONE'
[21:38] <knome> 2) if status for *any* bug is 'Fix Released', 'Fix Committed', or 'In Progress', the status is 'INPROGRESS'
[21:38] <knome> 3) if neither of the above statements are true, the status is 'TODO'
[21:39] <knome> (eg. triaged bugs do not count...)
[21:39] <ochosi> sounds good to me
[21:40] <knome> the rationale for requiring 'Fix Released' for all tasks/linked items is that we care about upstream too
[21:40] <knome> though i think bug watches aren't in this task list
[21:41] <knome> and i don't think it still works completely
[21:41] <knome> but i'll look into it, and that's my goal anyway
[21:43] <knome> hmm right, there was some weird glitch
[21:43] <knome> it works now without code changes, as i expected
[21:43] <knome> so, for posterity
[21:43] <knome> https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1313682
[21:43] <knome> is "INPROGRESS"
[21:44] <knome> another one:
[21:44] <knome> https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1437180
[21:44] <knome> is "TODO"
[21:46] <knome> ochosi, how should we handle "Opinion", "Invalid", and "Won't Fix"?
[21:46] <knome> to me it would make sense to ignore those, eg. if there's a bug with 2 tasks; one is fix released and another is any of those, then it should be 'DONE', right?
[21:47]  * ochosi is a little distracted by having to kill mosquitos
[21:47] <ochosi> invalid/wontfix > done imo
[21:47] <ochosi> opinion feels more open
[21:47] <knome> really?
[21:48] <knome> "Doesn't fit with the project, but can be discussed."
[21:48] <knome> and yeah
[21:48] <knome> if there are only invalid/wontfix statuses, should the bug just not be listed at all?
[21:48] <ochosi> well invalid and wontfix don't sound like "can be discussed"
[21:48] <knome> (i don't exactly know why we would link bugs like that, but...)
[21:48] <ochosi> we can also just unlink those
[21:49] <knome> heh
[21:49] <knome> now they show up as "TODO"
[21:49] <ochosi> but yeah, you could take them out of the equation
[21:49] <knome> it's easy enough
[21:49] <ochosi> to some extent, keeping them linked let's us remember what we tackled / touched per cycle
[21:49] <ochosi> so that's not totally useless
[21:50] <ochosi> but showing up as TODO is
[21:50] <knome> ok, those are handled now
[21:50] <knome> not that we have any...
[21:50] <knome> i'll keep "opinion" handling as "new" then
[21:50] <knome> eg. no difference
[21:51] <ochosi> k
[21:51] <knome> isn't that what you wanted?
[21:51] <ochosi> i'm ok with that
[21:52] <knome> well, i thought that was what you wanted
[21:52] <knome> you didn't want them to be not visible
[21:52] <knome> what else would they be?
[21:52] <ochosi> it's a bit too hot here to really *know* what i *want* ;)
[21:52] <knome> if there are only opinion statuses (considering wontfix and invalid aren't counted here any more), should be 'BLOCKED' ?
[21:53] <knome> i don't know, this starts going very meta
[21:53] <ochosi> heh, indeed
[21:53] <ochosi> i'm not even sure "opinion" is a very useful status as it is
[21:53] <knome> me neither
[21:54] <knome> maybe it's a consolation status when you want to say "wontfix", but want to be nice
[21:55] <ochosi> heh
[21:55] <ochosi> yeah
[22:31] <knome> off to bed, nighty
[22:32] <ochosi> night knome


[20:46] <nhandler> On my cr-48, I get a big scary banner at the top when I try to login on uds.ubuntu.com using Launchpad. It says an insecure script has been blocked. I'm not sure about the specific script causing it (or if it is on the uds.u.c or LP side), but it is most likely openid related
[20:47] <nhandler> Hmm..uds.u.c then proceeds to give me a 500 error when I try to login
[21:04] <daker> nhandler, i am not sure uds.u.c has a login system
[21:04] <daker> can you explain ?
[21:04] <daker> uds.u.c is a wordpress instance
[21:10] <nhandler> daker: It is the wordpress login feature. It uses Launchpad for authentication rather than a username/password. The 500 error might be due to me not having an actual WP account there, but the scary warning should not be there regardless
[21:10] <daker> yep i think you don't have access to it
[21:11] <daker> are you using the /wp-admin ?
[21:12] <daker> nhandler, i think i know what's the problem
[21:14] <nhandler> daker: I probably was (I think something was messed up with the site when I tried, as the homepage didn't load properly either)
[21:14] <daker> the Launchpad SSO have been updated, and i think the wordpress lib should be updated too
[21:15] <daker> nhandler, the second thing LP doesn't provide any information to wordpress
[21:15] <mhall119> nhandler: it could be that you do have an account on the WP instance, but it's not associated with your openid
[21:16] <mhall119> nhandler: the wordpress openid plugin fails spectacularly if it tries to create a new user with an email that matches an existing user


[15:25] <Eickmeyer[m]> OvenWerks: any ideas on bug 1898369?
[17:09] <Eickmeyer[m]> If anybody wants to try to duplicate that, be my guest. ^
[17:18] <OvenWerks> Eickmeyer[m]: I suspect a lack of "apply" but will look closer as I go.
[17:20] <OvenWerks> I have started working on 2.2.0 (of course). I may add a save config to as many callbacks as I can. I don't like the idea of an auto "Apply" though.
[18:34] <OvenWerks> Though the part about edited the file by hand and it works (autojack accepts it) but the field shows up blank in studio-controls sounds odd.
[19:06] <Eickmeyer[m]> OvenWerks: Well, they really shouldn't be editing the config by hand.
[19:15] <Eickmeyer[m]> OvenWerks: Was armhf support dropped from Ardour?
[19:23] <Eickmeyer[m]> nfm, it was an internal error in the compiler.
[19:23] <Eickmeyer[m]> *nvm
[21:07] <OvenWerks> Eickmeyer[m]: editting by hand was a good trouble shooting step.
[21:07] <Eickmeyer[m]> True.
[21:08] <OvenWerks> good info for me anyway.
[21:08] <OvenWerks> I have dumped my current work into a branch so I can look at it. (was adding channel count to pulse bridge)


[08:24] <mup> Bug #1845458 opened: VMWare power fails to get IP from hostname <MAAS:New> <https://launchpad.net/bugs/1845458>
[08:24] <mup> Bug #1845459 opened: Failure creating KVM pod in CI <MAAS:Triaged> <MAAS 2.6:Triaged> <https://launchpad.net/bugs/1845459>
[08:39] <mup> Bug #1845461 opened: CentOS 7 fails to deploy in CI <MAAS:Triaged> <https://launchpad.net/bugs/1845461>
[08:48] <mup> Bug #1845461 changed: CentOS 7 fails to deploy in CI <MAAS:Triaged> <https://launchpad.net/bugs/1845461>
[08:54] <mup> Bug #1845461 opened: CentOS 7 fails to deploy in CI <MAAS:Triaged> <https://launchpad.net/bugs/1845461>
[09:32] <danboid> Does MAAS have the ability to image its machines? I realise machines are supposed to be configured with cloud-init and juju but it would be handy to be able to image machines and restore machines from images
[09:33] <danboid> Maybe I'll have to use something like fog for this?
[11:57] <mup> Bug #1821574 changed: [doc] Docs website defaults to showing 2.4 docs <doc> <MAAS:Fix Released> <https://launchpad.net/bugs/1821574>
[12:00] <mup> Bug #1821574 opened: [doc] Docs website defaults to showing 2.4 docs <doc> <MAAS:Fix Released> <https://launchpad.net/bugs/1821574>
[12:04] <mup> Bug #1821574 changed: [doc] Docs website defaults to showing 2.4 docs <doc> <MAAS:Fix Released> <https://launchpad.net/bugs/1821574>
[21:16] <mup> Bug #1845558 opened: UI sending websocket interface tags in a dictionary <ui> <MAAS:New> <https://launchpad.net/bugs/1845558>
[21:19] <mup> Bug #1845558 changed: UI sending websocket interface tags in a dictionary <ui> <MAAS:New> <https://launchpad.net/bugs/1845558>
[21:25] <mup> Bug #1845558 opened: UI sending websocket interface tags in a dictionary <ui> <MAAS:New> <https://launchpad.net/bugs/1845558>