[11:38] <oSoMoN> hello release masters, I got informed by psivaa that « Failures in boottesting with oxide-qt is known and iirc, the release team does add hint for that to be forced », is that correct?
[11:41] <Laney> oSoMoN: I thought that was supposed to be fixed
[11:42] <oSoMoN> Laney, it apparently isn’t, see https://jenkins.qa.ubuntu.com/job/wily-boottest-oxide-qt/lastBuild/console
[11:43] <Laney> I can see that, but it is *supposed* to be
[11:43] <Laney> So we should first find out what is wrong
[11:44] <Laney> Oh. It's not that unity greeter thing. Man, this output is confusing.
[11:50] <oSoMoN> if I read correctly the output, the test that failed is getpkgsrc, but I’m not really sure what that does
[13:07] <Laney> Possibly fixed the test instead (#ubuntu-ci-eng) if any other release team members come along and get tempted to skip it.
[13:07] <Laney> Waiting for review then we can retry this.
[15:44] <quadrispro> tjaalton, hi there! do you have time for this? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1449892
[16:32] <tjaalton> quadrispro: not before monday
[16:34] <quadrispro> alright thx
[16:36] <tjaalton> i'll upload it then
[16:50] <quadrispro> tjaalton, I've uploaded it already to vivid-proposed, AFAIK needs review
[18:56] <tjaalton> quadrispro: hm ok, i need to import it to git then
[20:12] <barry> infinity: i'm looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html  -- esp. python-pip and python-pluggy.  are these blocked because of the recent infrastructure outage or something else?
[20:14] <infinity> barry: pluggy is in NEW.
[20:14] <barry> infinity: oh of course
[20:14] <infinity> barry: pip looks like it's blocked on the python DEP-8 tests sucking.
[20:15] <barry> infinity: i'm looking at the amd64 console output.  looks to me like an infrastructure failure
[20:15] <barry> https://jenkins.qa.ubuntu.com/job/wily-adt-python3.4/lastBuild/ARCH=amd64,label=adt/console
[20:16] <infinity> barry: For amd64 yeah, for i386, not so much.
[20:16] <barry> infinity: ack
[20:17] <infinity> barry: In fact, on i386, the failures look very much related to pip...
[20:17] <infinity> ImportError: No module named 'ensurepip'
[20:17] <barry> yay
[20:17] <infinity> Well, some of the failures anyway.
[20:17] <infinity> That testsuite looks to be a mess.
[20:18] <barry> infinity: indeed.  ok, thanks, i'll stare at doko
[20:19]  * barry hugs infinity
[20:31] <doko> infinity, barry: how's that? these are all networking failures
[20:31] <barry> doko: and now network is cut off in dep-8 tests :(
[20:31] <infinity> The importerror is a network failure?
[20:31] <doko> barry, is this a final decision?
[20:32] <doko> infinity, which one?
[20:32] <barry> doko: i think it already happened, but i'm not positive, and i don't know whether it will be reversed.  i already disabled some network tests in the system-image dep-8 tests
[20:32] <doko> adt-run [16:32:38]: test failing-tests:  - - - - - - - - - - results - - - - - - - - - -
[20:32] <doko> failing-tests        PASS
[20:33] <doko> infinity, known failing tests are run, but ignored
[20:33] <infinity> That's not confusing.  Kay.
[20:34] <infinity> Right, so it's just the connectivity stuff.
[20:34] <infinity> That conversation is still ongoing.


[06:40] <pitti> Good morning
[07:50] <pitti> jibel: ah, so when I install lightdm-gtk-greeter, the greeter starts in the container with the dummy driver
[07:50] <pitti> jibel: unity-greeter crashes
[07:51]  * pitti tries to find something less intrusive, that greeter is in universe
[07:54] <pitti> hah
[08:05] <pitti> jibel: so I want to test this: http://paste.ubuntu.com/6918740/
[08:08] <pitti> oh, this already callsl dpkg-divert, I'll do that as well then (with _runInImage)
[08:11] <pitti> http://paste.ubuntu.com/6918768/ then
[08:18] <pitti> jibel: hm, it does the upgrade test on the original container, without an ephemeral overlay?
[08:19] <pitti> jibel: I had a bug in my code; how do I restore the original saucy container image now?
[08:19] <jibel> pitti, no, the overlay is created and mounted in the backend
[08:19] <pitti> sorry, I had assumed that would happen in overlays
[08:19] <pitti> jibel: ah, so I can just kill the job?
[08:19] <pitti> I lxc-attached to upgrader-ubuntu-saucy-trusty-desktop-amd64 and it showed me the in-progress upgrade
[08:20] <jibel> pitti, yes, did it not use an overlay?
[08:20] <pitti> jibel: it's currently running, so I can't tell yet
[08:20]  * pitti kills the job
[08:21] <pitti> jibel: ah, it did
[08:22] <jibel> pitti, phew :) it's in UpgradeTestBackendLXC, it creates a mount hook script called mount.sh and set it as mount hook
[08:22] <pitti> ah, I see
[08:22] <jibel> then the overlay is used when the container is started
[08:24] <pitti> yay, X is running now
[08:30] <jibel> Yay
[08:30] <jibel> pitti, thanks for fixing all this
[08:41] <pitti> jibel: c'est vert !
[08:42] <jibel> pitti, Cool
[08:42] <pitti> jibel: so I'd commit http://paste.ubuntu.com/6918860/ and roll it out, if it's ok for you
[08:43] <jibel> pitti, LGTM
[08:50] <pitti> jibel: done and rolled out
[08:50] <pitti> AutoUpgradeTester/UpgradeTestBackendQemu.py
[08:50] <pitti> +                                   "--addpkg", "linux-image-generic",
[08:50] <pitti> jibel: ^ is that something which we should commit to bzr? (that's a local diff on wazn)
[08:50] <pitti> I actually had expected that this is already installed by default
[08:52] <jibel> pitti, IIRC, it was not installed by vmbuilder
[08:52] <jibel> so, yes should be in bzr
[08:53] <pitti> jibel: oh, do we still use vmbuilder to create the VMs?
[08:53] <pitti> I'd actually say we should fail a test if linux-image-generic is missing
[08:53] <jibel> pitti, it is still there, hallyn is porting it to use uvtools instead of deboostrap
[08:56]  * pitti filed a bug report as a reminder
[08:57]  * pitti looks into that weird "old kernel" thing in the VMs
[08:58] <pitti> jibel: so perhaps vmbuilder still installs grub 1 into those?
[08:59] <jibel> pitti, yes, but I installs grub-pc and is supposed to migrate from grub-legacy
[09:00] <pitti> jibel: ah, so if the base image doesn't exist, it calls ubuntu-vm-builder to generate it; so I could do that locally to recreate that VM and see where things go haywire?
[09:02] <pitti> so grub 1 is "rc" (i. e. removed, but not purged)
[09:07] <pitti> jibel: so, calling "grub-install /dev/sda" works
[09:18] <pitti> jibel: just to understand this, ubuntu-vm-builder just gets you a bare-minimum VM; where does it install ubuntu-desktop?
[09:18]  * pitti doesn't see it in UpgradeTestBackendQemu.py
[09:28] <jibel> pitti, it is in the profile, DistUpgrade.cfg has an entry that point to a file with additional files to install during boostrap
[09:28] <jibel> bootstrap
[09:29] <pitti> ah, thanks
[09:29] <jibel> for example in upgrade-tester@aldebaran:~/auto-upgrade-tester/profiles/trusty/ubuntu-saucy-trusty-desktop-i386/DistUpgrade.cfg
[09:29] <jibel> there is
[09:29] <jibel> BasePkg = ubuntu-desktop
[09:29] <jibel> AdditionalPkgs = pkgs.cfg
[09:30] <jibel> BasePkg is a list of packages
[09:30] <jibel> AdditionalPkgs is yet another list of packages but in a external file
[09:34] <pitti> jibel: sheesh, ubuntu-vm-builder failed on my host, grep: /proc/cpuinfo: No such file or directory
[09:35] <pitti> forgets to mount /proc into the chroot or so
[09:36] <pitti> jibel: would it be ok if I modify the original VMs (run grub-install in those), and if that works, adjust vm-builder or UpgradeTestBackendQemu.py to do that?
[09:36] <jibel> pitti, it is okay, it is usually what i do
[10:36] <pitti> jibel: http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-saucy-trusty-desktop-i386_vm/24/console \o/
[10:38] <jibel> pitti, world is becoming greener \o/
[10:38] <pitti> jibel: so I wonder, should I just add the grub-install command to UpgradeTestBackendQemu.py?
[10:39] <pitti> jibel: yeah, and I just sponsored/NEWed xorg-lts-transitional, which should hopefully make the 12.04.{1234} upgrades much better
[10:40] <jibel> pitti, I saw that, it's great. You can update the qemu backend with the grub-install command and we'll reprovision VMs
[10:41] <pitti> jibel: so for testing, I'd add that to the code, remove/rename the amd64 VM, and re-start the test; that should rebuild the VM, right?
[10:42] <jibel> pitti, right, remove the disk image and it will be bootstrapped again
[11:15] <davmor2> Morning all
[11:17] <slickymaster-job> morning davmor2
[11:26] <pitti> jibel: yay, upgrade tests also find actual bugs
[11:27] <pitti> aside from the backported X stack ones, bug 1270597
[12:56] <pitti> jibel: hm, why do we have ubuntu-desktop in a server upgrade test? (http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-precise-trusty-server-lts-saucy-amd64/26/artifact/results/bootstrap.log)
[12:59] <jibel> pitti, interesting, it was not part of the original bootstrap.
[12:59] <jibel> pitti, and was not in yesterday's upgrade
[14:12] <pitti> jibel: hm, I don't remember logging into those containers, did I mess up anything?
[14:13] <jibel> pitti, there is no risk of messing up anything. I've been sidetracked by a HO, I'll have a look, maybe the original config is wrong
[14:13] <pitti> jibel: no worries, please don't interrupt anything
[14:14] <pitti> jibel: I'm still investigating the grub issue in VM, my initial fix didn't work
[14:24] <jibel> pitti, so from history.log the initial provisioning is wrong, but the profiles are correct
[14:24] <jibel> pitti, I'll recreate this container
[14:26] <jibel> and amd64 too
[14:29] <pitti> jibel: can you please poke me when these are done? my postgresql fix landed in trusty, I'd like to restart precise-trusty-server-tasks*
[14:29] <pitti> and the xorg fix is in as well, I'd like to run those too
[14:29] <jibel> you can restart *tasks* only p>t+lts-s had this problem
[14:29] <jibel> lts-s-server
[14:31] <jibel> pitti, I restart upgrade-ubuntu-precise-trusty-server-lts-saucy-(amd64|i386) you can restart tasks too
[14:31] <pitti> jibel: yes, done; thanks!
[14:32] <jibel> pitti, lxc being lighter than VMs maybe we could increase the number of executors to 4?
[14:32] <pitti> ah, http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-saucy-trusty-desktop-amd64_vm/24/artifact/results/bootstrap.log grub-install was *still* grub 1
[14:33] <pitti> jibel: not sure, it's still rather heavy; I managed to kill wazn with a dist-upgrade in a container twice already
[14:33] <pitti> but you have a better gut feeling about what these machines can do
[14:34] <jibel> hm, the run queue is pretty low and there is not bottleneck on IOs
[14:36]  * pitti wonders why he doesn't see any of the print() statements of AutoUpgradeTester/UpgradeTestBackendQemu.py in bootstrap.log
[14:36] <pitti> oh, they are in the console log
[14:38] <pitti> grub VM fix, take 2 running
[14:39] <pitti> jibel: so ATM we have 1 slot on aldebaran apparently?
[14:39] <pitti> and two on wazn?
[14:41] <pitti> precise-trusty-server-lts-saucy-{i386,amd64} pass again
[14:42] <jibel> there are 2 slots on each hosts, so 1 free slot on aldebaran, 0 free on wazn and 2 free on alderamin
[14:44] <jibel> pitti, but these tests use a lot of disk so we cannot balance the load between all the hosts, it would duplicate the base images. So LXC are done on wazn, S->T in VMs on aldebaran and P->T in VMs on alderamin
[14:44] <pitti> *nod*
[14:45] <jibel> ideally we'd have 1 shared disk with all the base images and distribute the jobs on a pool of slaves
[14:45] <pitti> in this brave new future world of CI machinery we probably will
[14:46] <jibel> :)
[14:46] <pitti> jibel: btw, what is saucy-{i386,amd64}.qcow2 on aldebaran?
[14:47]  * pitti is a bit confused about all those images, bak/, etc.
[14:47] <pitti> or the 5 checkouts of auto-upgrade-testing
[14:47] <pitti> well, let's clean up next week
[14:49] <jibel> pitti, <release>-<arch>.qcow2 are the original images created by vmbuilder
[14:49] <jibel> pitti, we'll cleanup next week, remember this upgrader was not supposed to exist anymore and being replaced by utah :)
[14:56] <pitti> darn, upgrade-ubuntu-precise-trusty-server-tasks-* caught the previous postgresql-common still
[14:57] <pitti> will probably need some time for whichever mirror to catch up
[14:57] <pitti> err, http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-precise-trusty-desktop-lts-saucy-i386/13/? -- quois ?
[14:57] <pitti> "quoi"
[14:58] <pitti> that's installing xserver-xorg-video-dummy
[15:17] <pitti> jibel: http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-saucy-trusty-desktop-amd64_vm//25 ☺
[15:18]  * pitti cleans up the other VMs and restarts those
[15:20] <pitti> jibel: http://paste.ubuntu.com/6920445/
[15:20] <pitti> jibel: the first hunk was already there; I'll commit those as two commits to bzr, ok?
[15:21] <jibel> pitti, suonds good
[15:21] <jibel> ou
[15:24] <pitti> done, and rolled out
[15:33] <pitti> more green!
[15:56] <pitti> jibel: nice, http://d-jenkins.ubuntu-ci:8080/job/upgrade-ubuntu-precise-trusty-server-tasks-amd64/27/ survives the upgrade now, and detects a conffile prompt
[15:57] <pitti> although I can't actually see any prompt in the log
[15:58] <pitti> jibel: oh, I have an idea about http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu-precise-trusty-desktop-lts-saucy-i386/13/console
[15:58] <pitti> jibel: you can't actually install xserver-xorg-video-dummy in that precise, it would need to be *-lts-whatever
[15:59] <pitti> and apparently it's already installed anyway
[16:13] <jibel> I don't see where it got this bind9.dpkg-dist from, there is nothing in the logs
[16:18] <pitti> c'est une chose pour demain
[16:18] <pitti> I hope the two running jobs that I kicked off will succeed as well now
[16:27] <pitti> green!
[16:28]  * pitti starts the other precise.lts*->trusty desktop tests
[16:36] <pitti> jibel: as for bind, we kill the LXC overlay as soon as the test is finished, right? (for post-upgrade investigation)
[16:37] <jibel> pitti, right, and it's in tmpfs, I'll add an option to keep it and upgrade on a persistent directory
[16:38] <pitti> jibel: no worries, I'll try it manually tomorrow morning
[16:38] <jibel> pitti, okay
[16:56] <pitti> jibel: I pushed two new tests, FYI
[16:57] <pitti> this is fun!
[16:57] <pitti> ok, some red -> yellow, more on this front tomorrow
[16:57] <pitti> good night!
[17:02] <jibel> Good night pitti
[19:25] <balloons> evening dkessel
[19:25] <balloons> and moring to you Noskcaj .. how are you gents?
[19:26] <Noskcaj> morning balloons. Pretty good, still waiting for MOTU and my new pc(s).
[19:27] <dkessel> hey, good evening balloons :) i'm fine. how are you? how's the dog?
[19:28] <balloons> I'm doing well. The dog is up and moving about happily. He's all to happy to overdue it. My wife tells me I have to be careful; I like running, hiking, etc and the dog is always coming along :-)
[19:41] <dkessel> hehe :)
[19:42] <dkessel> mh. can't find the official instructions for ubuntu touch installation on the 2013 nexus 7.... i thought it has become the officially supported tablet now...
[19:45] <balloons> dkessel, it's "flo" right?
[19:46] <dkessel> balloons, "razor", I believe: http://en.wikipedia.org/wiki/Nexus_7_(2013_version)
[19:47] <balloons> regardless, the image is still wip.. however if you are feeling brave
[19:47] <dkessel> ...if somebody tells me that at least it won't render the nice new tablet broken.... ;)
[19:48] <dkessel> i chose the 32 gb variant and hope to get dual boot...
[19:48] <balloons> dkessel, https://lists.launchpad.net/ubuntu-phone/msg06352.html
[19:48] <balloons> rsalveti would know more
[19:49] <balloons> and, https://lists.launchpad.net/ubuntu-phone/msg06378.html
[19:49] <balloons> dkessel, ^^ that's probably better to use actually
[19:50] <balloons> I guess the tldr is if you wait a week or so, it'll be much easier
[19:50] <balloons> buonasera Letozaf_
[19:50] <Letozaf_> balloons, hello
[19:50] <Letozaf_> balloons, howzit?
[19:51] <balloons> Letozaf_, craving a cheese sandwich and some tea :-)
[19:51] <dkessel> hehe many thanks balloons :)
[19:51] <Letozaf_> balloons, lol I finished dinner about an hour ago
[19:52] <dkessel> balloons, I guess I can cope with stock android for some weeks at least ;)
[19:53] <dkessel> rsalveti, I will be glad to test any never installation instructions ;)
[19:54] <balloons> dkessel, no worries.. You'll be able to consume ubuntu touch soon enough
[19:56] <balloons> Letozaf_, do you have a favorite cheese?
[19:56]  * balloons is still stuck on cheese
[19:57] <Letozaf_> balloons, well not really I like a lot of types of cheese
[19:57] <Letozaf_> balloons, maybe I prefer Asiago it's an Italian cheese
[19:57] <balloons> mm yes, quite good..
[19:59] <Letozaf_> balloons, what kind do you prefer ?
[20:00] <balloons> last night I had some gouda with a bit of fruit..
[20:00] <Letozaf_> balloons, sounds delicious
[20:01] <Letozaf_> balloons, sometimes it's also nice to have  cheese with jam too
[20:01] <balloons> we must stop.. lol.. hunger
[20:01] <balloons> anyways, is AP working for you now Letozaf_ ?
[20:02] <dkessel> guys... i am getting hungry again :)
[20:03] <Letozaf_> balloons, haven't tired, but I will now, I was working on bug 1238902
[20:05] <Letozaf_> balloons, looks like I'm getting good at compiling kernels :P (without configuration, just compiling :P)
[20:06] <balloons> Letozaf_, :-)(
[20:16] <rsalveti> dkessel: http://paste.ubuntu.com/6915695/
[20:16] <rsalveti> just make sure to boot the device at least once after doing oem unlock
[20:18] <dkessel> rsalveti, thanks. is setting up dual boot possible yet?
[20:18]  * Letozaf_ is updating autopilot
[20:18] <rsalveti> dkessel: yup, ondra knows how to do it
[20:19] <dkessel> ondra?
[20:20] <dkessel> rsalveti, ondra?
[20:21] <rsalveti> dkessel: he's in #ubuntu-touch
[20:21] <dkessel> ok thanks
[20:22] <Letozaf_> balloons, yeah! autopilot launch is working again :D
[20:24] <balloons> Letozaf_, excellent, so might we be able to finish reminders?
[20:24] <balloons> if I remember right, the issue was the app having changed
[20:25] <Letozaf_> balloons, yeah! think so, I am trying to remember
[20:26] <Letozaf_> balloons, maybe it's just better I update the one on my PC and run it to see what it's like now
[20:30] <Letozaf_> balloons, one thing I do not remember, now reminders app enters my Evernote account directly
[20:31] <balloons> Letozaf_, yes I think that's ok. We did work that would allow us to get around that.. my oauth-branches I believe use my account. We have a test account now.
[20:31] <balloons> anyways, first things first, let's make them work again ;-)
[20:32] <Letozaf_> balloons, but do I have to test using your test account or is it ok to use mine ?
[20:32] <balloons> Letozaf_, right.. test using your own
[20:32] <balloons> we'll do the work again to migrate to the special test account.. david set one up
[20:34] <Letozaf_> balloons, ok
[20:35] <Letozaf_> balloons, just one thing: reminders-app will enter the evernote account right away right? so I will have to fix the test that selects the account and then enters it
[20:38] <balloons> Letozaf_, umm.. I think if only one account is defined they might do that. But even if you have it all setup, you still need to select the account at the moment
[20:38] <balloons> not a bad idea to make that piece a little utility function you can remove later if needed
[20:39] <Letozaf_> balloons, I launched reminders-app with autopilot launch and it entered my account without me having to select it
[20:40] <balloons> Letozaf_, ahh then they already made the change :-)
[20:40] <Letozaf_> balloons, I will try to add a second evernote account to see what happens
[20:43] <Letozaf_> balloons, cool, yes if you have two accounts you have to select one, it you only got one it enters directly
[20:43] <Letozaf_> balloons, I will have to fix the test
[20:43] <Letozaf_> balloons, I will have to check if there are two accounts
[20:43] <balloons> Letozaf_, gotcha. Yea, I remember them wanting to change that, didn't realize it was done already. For the test then, yes assume we have 1 account already authenticated
[20:45] <Letozaf_> balloons, oh! ok, so I won't have to check if there are more than one, suppose we will always test with only one account
[20:45] <balloons> Letozaf_, yes.. We should develop a test for when there is a second account, but let's start simple :-)
[20:46] <Letozaf_> balloons, ok
[20:48]  * Letozaf_ need to reboot
[20:54] <Letozaf_> balloons, argh! I removed the second evernote account, but now reminders-app doesn't enter my account directly but requires me to select it so now I am not quite sure what is the right behavior
[20:54] <Letozaf_> balloons, maybe adding and removing the second account "broke" something
[20:54] <balloons> mmm.. tea.. the second cup is always better.. more steeping
[20:55] <balloons> Letozaf_, wild.. that might just be a bug actually
[20:55] <balloons> if you wipe the cache for the app, I assume it will fix itself
[20:55] <balloons> ?
[20:55] <Letozaf_> balloons, let me try
[20:55] <dkessel> balloons, nice to see you guys have got the google calendar with QA events online... that will make it easier for me to participate
[20:56] <balloons> dkessel, yes, It's been handy..  That sounds really odd
[21:00] <balloons> although honestly it should matter
[21:00] <balloons> one account should go straight in
[21:00] <balloons> I guess keep poking around till you figure out what's goin gon
[21:01] <Letozaf_> balloons, ok
[21:13] <Letozaf_> balloons, if I launch the reminders app installed on my PC fom touch coreapps ppa it doesn't enter directly the one and only account, is there a directory to remove so I can clear it's settings ? I do not think it's the ~/.local/share/com.reminders-app one as I have already tried removing it and nothing changed
[21:16] <balloons> Letozaf_, I suspect you are launching different versions of the codebase. What's in trunk should be what's in the ppa though
[21:17] <balloons> I wouldn't worry about removing the settings constantly.. It was just worth a try.. it should work, no matter what
[21:17] <Letozaf_> balloons, could be should I remove the ppa ?
[21:17] <balloons> Letozaf_, well you don't need to worry about the ppa version. Work using what's in the source
[21:37] <dkessel> good night. see you :)
[21:38]  * Letozaf_ is rebooting


[08:20] <Odd_Bloke> smoser: ;.; Forgive me.
[13:56] <smoser> Odd_Bloke, thank you for fixing
[13:57] <Odd_Bloke> smoser: Phil fixed it. :)
[14:17] <smoser> Odd_Bloke, what do you think about https://code.launchpad.net/~harlowja/cloud-init/cloud-init-fix-up-cli/+merge/297409
[14:23] <Odd_Bloke> smoser: I'm strongly +1 on the idea; I haven't reviewed the code.
[14:23] <Odd_Bloke> smoser: I think the reason I didn't do anything more invasive before is that I was fixing a trusty bug, but I can't remember exactly.
[17:09] <harlowja_> https://code.launchpad.net/~harlowja/cloud-init/cloud-init-fix-up-cli/+merge/297409 also fixes flake8 issues (so thats why some changes in that aren't just cli related)
[17:09] <harlowja_> cause the code moved under cloudinit so now it got flake tested
[17:10] <harlowja_> (if u were wondering)
[17:10] <harlowja_> lol
[18:06] <smoser> harlowja_, yeah, i like it
[18:06] <smoser> does the packaging still work i woner.
[18:10] <smoser> harlowja_, my pep8 cries now
[18:10] <smoser> http://paste.ubuntu.com/17373169/
[18:31] <smoser> http://paste.ubuntu.com/17374020/ seems needed for fixing that branch
[18:32] <smoser> all output in output/
[18:52] <harlowja_> hmmmm, will fix that, wonder why flake8 not find that
[19:12] <harlowja_> smoser what pep8 is that
[19:12] <harlowja_> *(what version)
[19:12] <smoser> 1.7.0-2
[19:13] <harlowja_> mine doesn't show anything, let's try that version, lol
[19:14] <harlowja_> ok, got same issues, its because of patcher.pathc
[19:14] <harlowja_> *patch
[19:14] <smoser> well, i did this: http://paste.ubuntu.com/17374020/
[19:15] <harlowja_> hmmm, or u can just do
[19:15] <harlowja_> patcher.patch()  # noqa
[19:15] <harlowja_> :-P
[19:19] <harlowja_> ok, https://code.launchpad.net/~harlowja/cloud-init/cloud-init-fix-up-cli/+merge/297409 updated with those
[19:33] <smoser> harlowja_, the patcher.patch....
[19:33] <harlowja_> ya
[19:33] <smoser> do you think its necessary that early ?
[19:33] <smoser> why not just move it down
[19:33] <smoser> assuming we dont stack trace in an 'import' that early, it should be ok, no ?
[19:34] <harlowja_> it patches logging, which if we do it after we import cloud.log then i think it might not be working as we want
[19:35] <smoser> oh. ok.
[19:35] <smoser> well, short term, your solution with a comment is fine.
[19:35] <smoser>  (# noqa)
[19:35] <harlowja_> ya, long-term kill patching
[19:37] <harlowja_> if we get git i can figure out the kill patching :-P
[20:10] <smoser> harlowja_, https://code.launchpad.net/~harlowja/cloud-init/cloud-init-net-sysconfig/+merge/297115
[20:10] <smoser> comented tehre.
[20:11] <smoser> and yea, lets get to git
[20:11] <smoser> and /me is out
[20:25] <harlowja_> lol


 https://www.youtube.com/watch?v=hTH3wPjWzQk
[03:20] <ronnoc> ahoneybun: Nice video :)
[03:23] <ronnoc> sand the panel crashes lol
[03:23] <ronnoc> *sans
[04:22] <valorie> nice vid, but dang, all those crashes
[04:22] <valorie> I never get any
[04:22] <valorie> knock on wood
 Good morning
 mornin'
[07:51] <lordievader> Good morning.
[10:32] <sitter> Mirv: hey, packaging for this is in ubuntu+1 branch I presume? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-011
[11:01] <Mirv> sitter: yes for qtbase, qtdeclarative and qtmultimedia. they've ubuntu+1 branches. hmm, some others have 5.6 changes in the normal ubuntu branch (qtwebkit, qt3d), that could be changed if it hurts.
[11:02] <sitter> Mirv: should be fine thanks
[11:03] <vip> any news on beta 3?
[11:03] <Mirv> ok
[11:34] <soee> vip: there will be next beta ?
[11:34] <soee> i think RC now and than final
[11:34] <soee> !schedule
[11:41] <vip> soee: who knows
[11:42] <vip> I'd like t upgrade from wily, but I don't know if I should wait (and vbox test it) or not
[11:43] <soee> vip: most of us here ar eon Xenial for a long time already :-)
[11:43] <soee> i use it at my laptop and work machine
[11:50] <vip> soee: two monitors?
[11:56] <soee> vip: yes
[11:57] <vip> soee: great, You've convinced me ;)
[11:57] <soee> :D
[11:58] <soee> though i am using nvidia driver here where 2 i have monitors setup
[11:58] <soee> *where i have 2 monitors setup
[12:14] <BluesKaj> Howdy folks
[13:07] <soee> chakra is based on arch ?
[13:07] <soee> hiho BluesKaj
[13:08] <lordievader> soee: I believe it was.
[13:08] <BluesKaj> soee, hi.. yes it is
[13:10] <BluesKaj> it also has plasma 5.6 available...assume that's why you're asking
[13:11] <soee> yeah :) it has all latest stuff i though i might test it but since it is not debian based i might skip
[13:12] <BluesKaj> arch's  package management system is a bit clunky iirc
[13:13] <soee> well i tried it a long time ago: arch + kde and it is not so hard
[13:13] <soee> but i prefere apt
[13:13] <soee> there is yast i think
[13:14] <BluesKaj> same here, about 5 yrs ago, it's ok ,but a lot of work for a pretty ordinary linux
[13:15] <soee> yup, and since i'm using Debian on my VPS-es i want to stick with it :)
[13:18] <soee> btw i switch ed from Chromium Browser to Vivaldi 1.0 :)
[13:18] <soee> dark theme rox :)
[13:19] <BluesKaj> sticking with FF for bow..too much invested in it atm
[13:19] <BluesKaj> now
[13:21] <soee> this thursday 16.04 RC will be released and we still don't have Plasma 5.5.5 in archive :/
[13:23] <BluesKaj> think the OS is sticking with 5.4 for now
[13:24] <soee> 5.5.4 should be in archive no ?
[13:25] <marco-parillo> Default 16.04 is 5.5.4
[13:26] <marco-parillo> IIRC, you can get 5.5.5 with sudo add-apt-repository ppa:kubuntu-ppa/ppa-landing
[13:27] <soee> yes yes i have it installed
[13:30] <BluesKaj> marco-parillo, odd that I have the landing ppa , but plasmashell -v shows 5.5.4
[13:32] <marco-parillo> I could be wrong. Maybe I had tried (successfully) ppa:kubuntu-ppa/staging-plasma
[13:33] <marco-parillo> All I knew, somebody asked me to test, and it seemed to work for me.
[16:10] <mhall119> yofel: are you around for the snappy flavor call?
[16:10] <sgclark> yofel: ping? meeting today
[16:10] <mhall119> yofel: https://appear.in/snaps-flavours
[16:11] <yofel> IRC-only, sorry
[18:47]  * sick_rimmit waves
[18:47] <sick_rimmit> Hi friends
[18:49] <ahoneybun> hey sick_rimmit
[19:01] <soee> \o
[19:02] <soee> hey tomorrow is chocolate day :D
[19:02] <sick_rimmit> Chocolate day, that sounds good :-D
[19:03] <sick_rimmit> Hi ahoneybun
[19:03] <sick_rimmit> I see you've been playing with xenial
[19:03] <ahoneybun> mm?
[19:04] <ahoneybun> I've been running it for a few weeks sick_rimmit
[19:04] <sick_rimmit> Ah yes, but I saw the short video of you on YouTube yesterday
[19:04] <sick_rimmit> with desktop, and your cam in the bottom right corner
[19:04] <ahoneybun> the gaming video?
[19:05] <sick_rimmit> Nah, dunno it was posted to the Kubuntu Podcast
[19:05] <ahoneybun> no it was posted to mine
[19:05] <ahoneybun> it is on my channel
 nope
 it's on the KP channel
[19:06] <ahoneybun> lies
 https://www.youtube.com/watch?v=xyRIk9zTylU
[19:07] <ahoneybun> the heck
[19:07] <ahoneybun> ohhh'
[19:07] <ahoneybun> I was wondering where it was going
 and that's windows!!!!!!!!!!
[19:07] <ahoneybun> I was using the KP streaming key
[19:07] <ahoneybun> opps
 remove it please
[19:08] <sick_rimmit> ha ha, you posted it to wrong channel
[19:08] <sick_rimmit> no worries.
[19:08] <ahoneybun> well the second time it was to mine
[19:08] <ahoneybun> ovidiu-florin, is so serious about it
[19:08] <sick_rimmit> it would be good idea to take it down,
[19:09] <ahoneybun> https://www.youtube.com/watch?v=o5LARzUrHZg
[19:09] <ahoneybun> though now I know I was not recording sound
[19:09] <ahoneybun> ovidiu-florin, some people like to game
[19:09] <sick_rimmit> Anyways, let's not take over devel channel on an off topic
[19:09] <sick_rimmit> ;-)
[19:09] <ahoneybun> I think the kubuntu-ci does that fine lol
[19:10] <sick_rimmit> I'm just setting up a packaging build server
 I'm still at work...
[19:11] <sgclark> ovidiu-florin: do you have that packaging docker up somewhere?
 yeah, but it's not in any kind of usefull shape
 it was just a test to replace pbuilder
[19:13] <sgclark> right, I was going to make it useful. I can start from scratch.
 sgclark https://hub.docker.com/r/ovidiub13/kubuntu-packaging-devel/
[19:14] <sgclark> thanks
 github source link is in there
[19:14] <sick_rimmit> Did you guys know about the Debian Packaging plugin for Jenkins ?
 nooooo....??
 tell us more
[19:15] <sick_rimmit> I was reading about it over the weekend
[19:16] <sick_rimmit> https://wiki.jenkins-ci.org/display/JENKINS/Debian+Package+Builder+Plugin
[19:18] <sgclark> ovidiu-florin: I see nothing in regards to github source
 on the right side
 bellow the owner field
[19:20] <sick_rimmit> Oooo look
[19:20] <sick_rimmit> New Shinnies
[19:20] <sick_rimmit> Jenkins 2.0
[19:20] <sick_rimmit> https://jenkins.io/2.0/
[19:21] <sgclark> ah found it thanks
[19:21]  * sick_rimmit Thinks... "if only I had a clue how that stuff works"
 it's Java
 it doesn't
[19:22] <sick_rimmit> lol
[20:11] <vip> soee: do-release-upgrade -d?
[20:12] <soee> i never remember this command :D probably yes
[20:12] <vip> Nie odnaleziono nowego wydania
[20:13] <vip> oh, now it found something
[20:13] <vip> strange
[20:15] <vip> "error during upgrade"
[20:16] <vip> Hash Sum mismatch
[20:17] <soee> ~.~
[20:50] <BluesKaj> had to install upstart, the plymouth screen takes forever, almost 2 mis, and sddm doesn't load the login page , I have to login via vt/tty and startx to get to the desktop
[20:51] <BluesKaj> something is definitely missing here
[20:57] <valorie> hmmm, hash sum mismatch is supposedly a thing of the past
[20:58] <valorie> BluesKaj: is that an install from a daily image, or upgrade, or?
[21:01] <BluesKaj> valorie, , it's an upgraded daily, it's been a while since I installed it, probly 6 weeks at least
[21:02] <valorie> wow, sounds like a regression then
[21:02] <valorie> leaves me not wanting to upgrade today
[21:02] <valorie> yesterday
[21:03] <valorie> 's upgrade was flawless, afai can tell
[21:04] <BluesKaj> valorie, I might reinstall tomorow , it only takes 20 mins but setting up the vpn and other extar packages will be a pita, that's why I'm procrastinating
[21:06] <BluesKaj> hoping there's a fix in the pipe
[21:06] <soee> https://launchpad.net/ubuntu/xenial/+source/systemd/+changelog
[21:06] <soee> latest systemd chnages, maybe something was not right
[21:08] <mamarley> Hmm, I have had that installed for several days and no issues booting up.
[21:11] <valorie> BluesKaj: why do you need a vpn?
[21:12] <BluesKaj> valorie, shhhhh
[21:12] <valorie> lol
[21:14] <valorie> some Debian-based project had an April Fools screen that popped up saying Your Computer has Been Locked because of US Code blah blah of 2017
[21:14] <valorie> based on the ransomware screens now infesting Win installs
[21:15] <valorie> seemed extreme to me, but then I read about the crap my Congress is proposing
[21:15] <valorie> I think it doesn't have a snowball's chance to pass, because they are mostly known now for Doing Nothing and Getting Paid for It
[21:16] <BluesKaj> this old pc is my HTPC , nothing real fancy , just vlc for watching movies thru hdmi and spdif into an audio system ... experimenting with Kodi atm to see if it's worth cutting the cord
[21:17] <BluesKaj> and this TV is also my monitor
[21:57] <snele> clivejo: about muon. I think muon from your ppa is enought for now (because nobody else cares for pushing it to main archive)
[21:57] <snele> clivejo: i will share your ppa on kubuntu forums
[21:57] <clivejo> snele: I deleted it
[21:57] <snele> clivejo: could you maybe make xenial ppa only for muon?
[21:58] <clivejo> I cant see what the problem is
[21:58] <snele> clivejo: muon from your ppa works great for me. no problems at all
[21:58] <clivejo> muon is broken, we have a fix
[22:00] <clivejo> if I need to open another FFE for qapt, then thats fine, just tell me what to do and Ill try and do it
[22:01] <snele> clivejo: please add it back at least to your xenial ppa, many kubuntu users will really appreciate it
[22:01] <valorie> libqapt actually changed recently?
[22:01] <valorie> I remember us talking about this, but not the details
[22:02] <clivejo> yes, and the new Muon needs that change otherwise it crashes when you refresh the list
[22:02]  * valorie is still reading the debian policy manual, and is to the part about libraries and symbols
[22:02] <clivejo> but I grabbed git snapshot for both
[22:02] <valorie> they don't have a release?
[22:02] <valorie> ugh
[22:03] <valorie> that is probably why the FFE is being ignored
[22:03] <valorie> they really don't like git snapshots for an LTS
[22:04] <valorie> perhaps ask yofel if old release plus cherry-picked patches are a better bet to be accepted?
[22:04] <clivejo> then tell me, Im not a mind reader!
[22:04] <valorie> imo libqapt will have to be FFE'd too
[22:04] <valorie> probably late for yofel
[22:04] <valorie> :(
[22:05] <ahoneybun> clivejo, I sent an email about Muon
[22:05] <valorie> sitter, Riddell, have any input?
[22:05] <valorie> ahoneybun: where did you send your email?
[22:05] <clivejo> ahoneybun: did mhall get back to you?
[22:05] <clivejo> he said he was going to call in some favours
[22:05] <ahoneybun> I've not heard, I asked if you wanted him CCed into it
[22:05] <ahoneybun> I'll see if I can ping him
[22:07] <ahoneybun> valorie, to the dev list?
[22:07] <ahoneybun> I hope
[22:07] <valorie> ok, I should read email
[22:08] <valorie> gave up last night when comcast crapped out AGAIN
[22:08] <ahoneybun> valorie, https://lists.ubuntu.com/archives/kubuntu-devel/2016-April/010355.html
[22:08] <valorie> every night for over a week
[22:08] <ahoneybun> there is the thread
[22:08] <valorie> grrrr
[22:08]  * ahoneybun finally bookmarked that url
[22:10] <valorie> thank you, ahoneybun
[22:10] <valorie> I think that the release-team list is where we should be writing, however
[22:11] <valorie> that is where the people are with the power to help us get it into the archive
[22:11] <valorie> and someone should release muon and libqapt!
[22:11] <ahoneybun> I prefer to use apt but I can for sure understand its use
[22:11] <valorie> I agree
[22:12] <ahoneybun> for an LTS it is pretty important to have
[22:12] <valorie> it's lovely to check out packages for latest changes, etc.
[22:12]  * ahoneybun will have to write new docs about it
[22:12] <valorie> search works well, etc
[22:13] <ahoneybun> what timezone is yofel in?
[22:15] <valorie> he lives in Poland IMO
[22:16]  * valorie replied to ML
[22:19] <clivejo> why is a git snapshot questionable?
[22:19] <ahoneybun> where is the bug report about Muon clivejo
[22:19] <ahoneybun> snapshots are sometimes seen as unstable
[22:19] <clivejo> ahoneybun: its a FFE Bug 1562406
[22:21] <valorie> clivejo: I assume because it is assumed that there is a reason for "no release" status
[22:21] <valorie> like, no testing
[22:21] <clivejo> the diff to libqapt is very little
[22:21] <clivejo> https://quickgit.kde.org/?p=libqapt.git&a=commitdiff&h=e63d3239a7846eb968151ebdd4f12e0921e0f13a
[22:21] <clivejo> its just adding a signal
[22:22] <ahoneybun> there are buildable and working debs somewhere clivejo ?
[22:22] <ahoneybun> like a PPA
[22:22] <clivejo> well two signals cacheReloadFinished(); and cacheReloadStarted();
[22:22] <clivejo> there arent not
[22:22] <clivejo> I had them in my PPA
[22:23] <valorie> I think it would be good to help ovidiu-florin and sick_rimmit do a release
[22:24] <sick_rimmit> What!!!
[22:24] <ahoneybun> getting a working build in PPA or deb that works
[22:24] <valorie> I believe it isn't that difficult: tag, and roll a tarball, then upload it to the kde depot for distribution
[22:24] <ahoneybun> would be a good step I think
[22:24] <valorie> sitter made a script called releaseme that many application devels use
[22:25] <clivejo> valorie: shouldnt be that hard, this is sitters last bump https://quickgit.kde.org/?p=libqapt.git&a=commitdiff&h=726defa3188a1449312e212085f914e97e29f76f
[22:25] <valorie> and the people in #kde-devel are helpful
[22:25] <sick_rimmit> snele: I'm working on Muon
[22:25] <valorie> who maintains libqapt?
[22:25] <sick_rimmit> snele: Tonight I've neem configuring my build server
[22:26] <clivejo> but I cant see why a release and a git snapshot would make any difference
[22:26] <sick_rimmit> snele: I hope to have new PPA's in about a weekish
[22:27] <valorie> clivejo: it expresses the confidence of the maintainer
[22:29] <clivejo> maybe Carlo Vanini can do that for us?
[22:29] <valorie> clivejo: I believe we've done it before, but that was when Riddell was release manager
[22:30] <clivejo> do sick_rimmit or ovidiu-florin have commit access yet?
[22:30] <valorie> certainly worth asking him
[22:30] <sick_rimmit> I don't believe so
[22:30] <sick_rimmit> We've got a dialogue going with Carlo though
[22:30] <sick_rimmit> so good start
[22:30] <valorie> the Kubuntu Developers are the ones who vet new Kubutu Devels
[22:31] <valorie> the KC doesn't do that, and doesn't have a say
[22:31] <valorie> I surely do want more Kub Devels
[22:31] <clivejo> but libqapt is on KDE, surely they need to be KDE devels?
[22:32] <valorie> so you are talking about two different commit accesses
[22:32] <clivejo> Im confused
[22:32] <valorie> KDE devels can commit to any repo
[22:32] <valorie> but maintainers or release managers do releases in KDE
[22:33] <valorie> kubuntu devels I believe are the ones with commit access to our own repos
[22:33] <clivejo> if we had someone to bump the version of libqapt, grab that source code and package it
[22:33] <sick_rimmit> Buildserver ready, so I'll try building my version now
[22:33] <valorie> and MOTUs are the ones who commit to Universe
[22:33] <clivejo> then the release team might allow it in?
[22:34] <valorie> I very much wish we had a senior person like yofel, sitter or riddell speaking up
[22:34]  * sick_rimmit is permanently confused... just keep typing and pressing ok
[22:34] <valorie> sgclark: are you here, or in the air?
[22:34] <sgclark> fly back in a few hours
[22:34] <valorie> sick_rimmit: yes, I hope you all and carlo can get something going
[22:35] <valorie> sgclark: have I said anything untrue above?
[22:35] <clivejo> rick would you ask Carlo if there is any way he could bump the version of libqapt then?
[22:35] <valorie> I don't want to confuse anybody with wrong info
[22:36] <sgclark> I confused
[22:36] <sgclark> not sure what above is about sorry
[22:37] <valorie> sgclark: the attempt to get Muon and libqapt updated and into the archive
[22:37] <valorie> via FFE
[22:37] <sgclark> ah good luck with that
[22:38] <sgclark> highly doubt unreleased software post all feature freezes will get in
[22:38] <sgclark> color me impressed if you do
[22:38] <clivejo> I opened an FFE for Muon - Bug 1562406
[22:39] <clivejo> to try and get a git snapshot of libqapt and muon into the archive
[22:39] <clivejo> but the release team have totally ignored it
[22:39] <clivejo> Id like to know why?
[22:39] <sgclark> likely cause: past all freezes and the software is unreleased.
[22:39] <clivejo> is it because they are git snapshots?
[22:40] <sick_rimmit> clivejo: Bump on libqapt, sure I will ask him
[22:40] <clivejo> so Im wasting my time?
[22:40] <valorie> if the software builds and runs, it should be released IMO
[22:40] <valorie> then you can update your FFE
[22:41] <sgclark> well then tell them to release, ,I highly doubt it will get into xenial unreleasef
[22:41] <valorie> with a link to the released tarball or so
[22:43] <clivejo> sick_rimmit: well looks like we'll need a bump on Muon too *rolls eyes*
[22:44] <sick_rimmit> I think we can't release while we still have crash on package list
[22:44] <clivejo> otherwise we'll have those two bugs wide open
[22:44] <valorie> I thought that was recently fixed?
[22:44] <clivejo> the crashing on the package list is fixed by updating libqapt
[22:44] <clivejo> we need both libqapt and muon to make this work again
[22:44] <sick_rimmit> Ah right, OK
[22:45] <sick_rimmit> do you have a quickgit link for libqapt to hand ?
[22:46] <clivejo> https://quickgit.kde.org/?p=libqapt.git
[22:46] <valorie> release release release
[22:47] <sick_rimmit> Doh!
[22:47]  * sick_rimmit its in the history
[22:49] <clivejo> sick_rimmit: for handyness you could install the latest libqapt from KCI
[22:49] <clivejo> that would stop your local build crashing
[22:50] <sick_rimmit> OK
[22:51] <sick_rimmit> Well Muon package is in mid build with pbuilder
[22:51] <sick_rimmit> TBH, it'll probably be Weds evening that I can get it into PPA upload shape
[22:52] <sick_rimmit> I have no clue how to get it FFE'd or stuff like that
[22:52] <sick_rimmit> I can probably get as far as my PPA on launchpad
[22:53] <sick_rimmit> I'm confused about release tarball, is that with KDE ?
[22:53] <valorie> yes, with KDE
[22:53] <valorie> it is released for everyone, not just us
[22:53] <valorie> same with libqapt
[22:54] <valorie> sick_rimmit: once they are released, I think the original FFE can be changed to include the new release info
[22:55] <sick_rimmit> OK so we need a version bump tagged as Release on both, yes ?
[22:55] <valorie> sick_rimmit: please ask someone who knows how to release!
[22:55] <valorie> and look up the releaseme script by apachelogger/sitter
[22:56] <valorie> ximion's input on that ML thread sounds important as well
[22:56] <valorie> since it just involves syncing with Debian
[22:58]  * sick_rimmit scratches head, as heart sinks with sense of utter frustration.
[22:59]  * sick_rimmit can get as far as build to PPA, then its beyond his skills
[22:59] <sick_rimmit> https://github.com/KDE/releaseme
[23:00] <ximion> valorie: in my mind Ubuntu already had 5.6, so this was suprising to me
[23:00] <ximion> and you really, really don't want to run on ancient app-install-data
[23:01] <ximion> problem is that the new release will include some behavior changes and will use new technology (AppStream), so it might also add new issues
[23:01] <ximion> but IMHO this (small) risk is outweight by the benefit of updating it
[23:05] <valorie> "ubuntu already had 5.6" -- Qt 5.6 or what?
[23:05] <valorie> plasma 5.6?
[23:05] <valorie> the release dates made that impossible
[23:06] <valorie> for both, actually
[23:06] <valorie> we'll have to backport them
[23:06] <valorie> after release
[23:11] <valorie> sick_rimmit:
[23:11] <valorie> General Release Workflow
[23:11] <valorie> Decide on a release date (duh)
[23:11] <valorie> gotta do that first, and than one week later you can do the release
[23:15] <valorie> ok, must go outside to work, at least a bit
[23:20] <sick_rimmit> Thanks valorie I'm gonna wrap it up too
[23:22] <sick_rimmit> OK so Muon builds with one minor Lintian warning, version number
[23:23] <sick_rimmit> I'll be back Weds night try finish it and upload to PPA
[23:23]  * sick_rimmit Out!


[20:02] <Alsyia> Hi, would this be place to ask a question about why an upstream kernel patch is not included in the corresponding Ubuntu kernel?
[20:22] <sarnold> yes, that'd be on-topic here
[20:27] <Alsyia> So the patch is this one, Jul 2021: https://lkml.org/lkml/2021/7/12/1687
[20:27] <Alsyia> My understanding is that it was included in upstream kernel 5.12 (but I'm starting to think I'm wrong about that? I'm not familiar with kernel dev conventions!) but I checked the source for my 5.13 kernel and it's not included in it. The related bug I'm interested about is this one: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1929591
[20:29] <Alsyia> *for my Ubuntu 5.13 kernel, sorry
[20:32] <sarnold> https://kernel.dance/#ad3fc798800fb7ca04c1dfc439dba946818048d8 -- it looks like it did land in the 5.12 stable series, yeah
[20:34] <Alsyia> Thanks! Is is normal that there is no 5.12 tags in the list here? https://github.com/torvalds/linux/commit/ad3fc798800fb7ca04c1dfc439dba946818048d8
[20:39] <sarnold> I'm not entirely sure how all that works.. you can see the backport on eg https://github.com/gregkh/linux/commit/27f9d646b165cb0f1d64989b19b50498dff93379
[20:59] <Alsyia> Ah, thanks
[21:00] <Alsyia> I'm not sure either ^^ But thanks for the help, this gives some pointers to continue looking


[13:20] <bluesabre> ochosi: the screen off code for the greeter in utopic (1.8.5) seems to cause a new black screen issue
[13:23] <bluesabre> If I walk away from my computer for an extended amount of time, coming back, I can move my mouse but the screen stays dark (on the login screen)
[13:23] <bluesabre> If I type my password, the screen is restorted when logging back in
[13:23] <bluesabre> Still investigating, but good to know
[14:33] <bluesabre> xchat dropped from seed
[15:29] <brainwash> bluesabre: NOOOOOOO
[15:29] <brainwash> :P
[15:29] <bluesabre> haha
[15:30] <brainwash> so it looks like 14.10 will be a very boring release
[15:30] <elfy> when you adding hexchat and removing pidgin, abiword, gnumeric and light locker :p
[15:31] <brainwash> you can't just remove pidgin o.o
[15:31] <brainwash> how should people communicate over the internet? :)
[15:32] <bluesabre> send pings at spaced intervals to represent morse code
[15:32] <elfy> tincans and string
[15:33] <bluesabre> nope
[15:33] <bluesabre> $ tincans
[15:33] <bluesabre> tincans: command not found
[15:33] <elfy> :)
[16:39] <ochosi> bluesabre: hm, strange. i guess we can try the XActivateScreenSaver instead of XForceScreenSaver
[16:40] <ochosi> but either way, this is a standard xlib call, not sure what could be wrong with that
[16:40] <ochosi> also, that issue seems to have been reported in trusty already (going away for a longer period of time)
[16:40] <ochosi> is the screen really off or just black but with backlight?
[16:41] <ochosi> if it's off, then it's DPMS, not the stuff we added in the greeter
[16:41] <ochosi> (i guess nobody previously tested sessions sitting at the greeter for longer)
[17:06] <bluesabre> oh, this definitely was not a problem for me with trusty
[17:14] <bluesabre> I'll try a different video driver to see if that makes a difference