[08:10] <acheron_uk> clivejo: krita seems to start now
[09:33] <IrcsomeBot> <Clifford> Its about time!
[09:43] <acheron_uk> clivejo: not that I have any digital art skills to use it!
[09:52] <IrcsomeBot> <Clifford> Neither do I !
[10:04] <acheron_uk> this is what I get in commandline startup in a VM http://paste.ubuntu.com/16981517/
[10:04] <acheron_uk> not sure if any errors there are significant or just expected noise
[10:22] <IrcsomeBot> <Clifford> No idea!
[10:35] <mamarley> http://blog.qt.io/blog/2016/06/03/qt-5-7-0-release-candidate-available/  Hah, 5.7 is going to be out before we even have 5.6…
[10:37] <clivejo> mamarley: debian are working on 5.6.1 I believe
[10:38] <acheron_uk> I saw a 5.6.x in their git I think, and maybe a package in experimental?
[10:39] <clivejo> from the chat in the IRC channel they are working on it
[10:39] <mamarley> And there are 5.6 packages in the landing-011 PPA too, but my point still stands.  5.7 will probably be out before 5.6 goes into Yakkety.
[10:40] <clivejo> acheron_uk: would you mind purge my PPA and installing krita via the archive and then upgrading via my PPA?
[10:40] <acheron_uk> clivejo: yep, I'll give that a go
[10:41] <clivejo> krita has part of the calligra source but has now been split, so Im wondering how an upgrade is handled
[10:41] <acheron_uk> mamarley: I would not be surprised one bit
[10:42] <acheron_uk> clivejo: didn't handle the ppa purge well for a start!
[10:43] <clivejo> oh?
[10:43] <clivejo> only krita in that PPA!
[10:43] <acheron_uk> oh, moaning about aptitude actually
[10:44] <acheron_uk> let me try again
[10:44] <clivejo> oh it probably wants to roll back to the archive version
[10:44] <clivejo> and will need to pull in calligra-libs and all that rubbish :/
[10:46] <acheron_uk> http://paste.ubuntu.com/16982835/
[10:48] <acheron_uk> have purged krita and krita-data manually and disbaled your ppa, so shall try from that 
[10:52] <acheron_uk> well, krita doesn't even want to install on this VM without your ppa
[10:55] <acheron_uk> following the dep problem through gives http://paste.ubuntu.com/16983034/
[10:56] <clivejo> LOL
[10:56]  * clivejo shakes head
[10:56] <clivejo> cant believe that bug is still in xenial
[10:57] <clivejo> I guess noone uploaded my updated version
[10:58] <clivejo> acheron_uk: thats a typo in the control file fonst-lyx => fonts-lyx
[10:58] <acheron_uk> that is yy, but probably the same
[10:58] <acheron_uk> lol
[11:01] <clivejo> LP: 1538098
[11:01] <ubottu> Launchpad bug 1538098 in calligra (Ubuntu) "Please update Calligra to 2.9.10" [Wishlist,Triaged] https://launchpad.net/bugs/1538098
[11:02] <clivejo> !info krita
[11:02] <ubottu> krita (source: calligra): pixel-based image manipulation program for the Calligra Suite. In component universe, is optional. Version 1:2.9.7-0ubuntu13 (yakkety), package size 7959 kB, installed size 32002 kB
[11:02] <clivejo> that be why!
[11:07] <acheron_uk> oh dear
[11:08]  * acheron_uk sees it's time for lunch
[11:08] <clivejo> will you be about later?
[11:09] <acheron_uk> in a couple of hours I would imagine
[11:09] <clivejo> Ive uploaded krita for xenial
[11:09] <clivejo> would you find someone to test it for me?
[11:10] <clivejo> also if you see jimarvan, could you ask him reload OSM and check the location of his workplace?
[11:11] <acheron_uk> OK. If I get back without being diverted, I will
[11:11] <clivejo> I probably wont be at the computer over the next few days
[11:11] <clivejo> but Ill have telegram, you can ping me with @Clifford
[11:12] <acheron_uk> ok
[11:17] <BluesKaj> Hi folks
[11:17] <clivejo> hi BluesKaj
[11:18] <BluesKaj> hi clivejo
=== acheron_uk is now known as acheron
=== acheron is now known as acheron_uk
[13:25] <clivejo> can someone on Xenial, please test trita for me - https://launchpad.net/~clivejo/+archive/ubuntu/krita/
[13:25] <clivejo> oooo
[13:26] <clivejo> KDE Android client now supports reply to messages
[13:28] <acheron_uk> it runs
[13:28] <clivejo> *NOTE for Ubuntu users: The Ubuntu folks are not updating their repos as fast as this app gets updated. Some features will not work if the KDE Connect version in you desktop doesn't match the one in your phone. To make sure you always have the latest version on your desktop, use this PPA repository: https://code.launchpad.net/~vikoadi/+archive/ubuntu/ppa/
[13:28] <clivejo> naughty Ubuntu folk
[13:31] <acheron_uk> do you want me to purge and reinstall on XX?
[13:31] <clivejo> nah, no point
[13:31] <clivejo> its the same version in xenial
[13:31] <clivejo> un-installable
[13:32] <acheron_uk> I beg to differ, as it just installed fine
[13:32] <clivejo> is did?
[13:32] <clivejo> !info krita xenial
[13:32] <ubottu> krita (source: calligra): pixel-based image manipulation program for the Calligra Suite. In component universe, is optional. Version 1:2.9.7-0ubuntu12 (xenial), package size 7975 kB, installed size 31997 kB
[13:33] <acheron_uk> http://paste.ubuntu.com/16988025/
[13:34] <clivejo> strange
[13:38] <acheron_uk> and upgrade once ppa enabled again http://paste.ubuntu.com/16988174/
[13:39] <clivejo> does it run?
[13:39] <acheron_uk> ppa v3? yes
[13:40]  * clivejo cheers
[13:43] <acheron_uk> that's a nice bit of software to have packaged up in the newest version
[13:49] <clivejo> acheron_uk: agreed
[13:49] <clivejo> soee_: ping
[13:49] <clivejo> can you arrange for testing and maybe get this into backports
[17:49] <mamarley> So I finally opened a bug for getting Quassel updated to 0.12.4: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1589128.  I have already packaged it; I just need someone to do the upload.
[17:49] <ubottu> Launchpad bug 1589128 in quassel (Ubuntu) "Please update Quassel to 0.12.4" [Undecided,Confirmed]
[18:05] <mparillo> Is anybody trying to install on YY and getting this? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1577540 It has been maybe a month or so that I have been unable to install YY.
[18:05] <ubottu> Launchpad bug 1577540 in ubiquity (Ubuntu Yakkety) "ubi-console-setup failing on yakkety images" [Undecided,Confirmed]
[18:21] <acheron_uk> I was a couple of weeks ago. not tried latest images though
[20:00] <IrcsomeBot> <marcinsagol> Uhm Xenial died
[20:01] <clivejo> died, how?
[20:01] <IrcsomeBot> <marcinsagol> Sddm does not start now after some updates
[20:01] <clivejo> eak
[20:04] <clivejo> what updates did you make that might have killed it?
[20:05] <IrcsomeBot> <marcinsagol> No idea
[20:05] <IrcsomeBot> <marcinsagol> Some nvidia drivers for examllr
[20:06] <clivejo> nvidia driver do indeed like to kill SDDM
[20:07] <IrcsomeBot> <marcinsagol> mamarley said there was some change related to opengl and it might be it that breaks system
[20:07] <clivejo> I noticed a new nvidia driver for my yakkety install
[20:07] <IrcsomeBot> <marcinsagol> But it was for snappy packages
[20:11] <IrcsomeBot> <marcinsagol> This driver is broken
[20:11] <IrcsomeBot> <marcinsagol> Gives me some errors when trying to reinstall
[20:13] <IrcsomeBot> <marcinsagol> http://paste.ubuntu.com/17005687/
[20:14] <IrcsomeBot> <marcinsagol> Clivejo can you ping mamarley?
[20:15] <IrcsomeBot> <marcinsagol> Uhm i can't purge the driver either
[20:15] <clivejo> mamarley: ping
[20:18] <mamarley> marcinsagol: I doubt your sddm issue was caused by the driver; I have tested it on 3 PCs with Kubuntu Xenial now and have not had that issue on any of them.  As for the install failure issue, I would recommend reproducing it with the 361 driver from the regular archive and then filing a bug report on it.
[20:19] <mamarley> The patch i applied was just a backport of what they applied to 361.
[20:20] <mamarley> I can see where it complains that there were no instances of the nvidia-367 module in the tree though.  That might explain your sddm brokenness.
[20:21] <IrcsomeBot> <marcinsagol> Hmm
[20:21] <IrcsomeBot> <marcinsagol> Same will be with 361 from the ppa?
[20:22] <mamarley> I think the 361 in the main archive is actually newer than the 361 in the PPA.  But the idea is to test the driver from the main archive so you can file a bug report that the Ubuntu developers will handle.
[20:26] <IrcsomeBot> <marcinsagol> I can't install any driver
[20:26] <IrcsomeBot> <marcinsagol> Errors
[20:35] <acheron_uk> 364.19-0ubuntu0~gpu16.04.5 installed ok here earlier, or at least didn't have errors 
[20:35] <IrcsomeBot> <marcinsagol> Rebooted?
[20:39] <mamarley> It looks like the error occurs when attempting to remove the driver.  Could you please execute the journalctl command that the error recommends so I can see why it fails?
[20:41] <IrcsomeBot> <marcinsagol> http://paste.ubuntu.com/17006991/
[20:41] <IrcsomeBot> <marcinsagol> Is it it?
[20:42] <acheron_uk> ok. just rebooted and sddm and login are ok
[20:42]  * mamarley nie mówi po polsku.
[20:43] <IrcsomeBot> <marcinsagol> http://paste.ubuntu.com/17007055/
[20:43] <mamarley> Oh, I see, "target is busy".  Hmm.
[20:45] <mamarley> marcinsagol: Try running sudo lsof | grep -i "\/var\/lib\/snapd\/gl"
[20:46] <IrcsomeBot> <marcinsagol> Empty result
[20:47] <mamarley> marcinsagol: How about sudo lsof | grep -i "\/var\/lib\/snapd"
[20:47] <IrcsomeBot> <marcinsagol> http://paste.ubuntu.com/17007239/
[20:48] <mamarley> marcinsagol: Shut down Xorg (stop sddm) and then attempt to uninstall the driver again.
[20:49] <mamarley> And definitely report this bug on Launchpad.  It looks like someone didn't do enough QA before they uploaded that patch.
[20:51] <soee> back on system :)
[20:51] <acheron_uk> LP: #1589006
[20:51] <ubottu> Launchpad bug 1589006 in snapd (Ubuntu) "Failed unmounting Mount unit for nvidia support in snappy" [Critical,Confirmed] https://launchpad.net/bugs/1589006
[20:51] <soee> mamarley: ^ is it this one ?
[20:52] <mamarley> Looks like it.  I will subscribe to that so that I can update the graphics-drivers PPA packages as soon as it is fixed.
[20:53] <acheron_uk> I obviously dodged that so far in some way
[20:53] <mamarley> It didn't affect my systems because I don't have snappy installed.
[20:53] <mamarley> acheron_uk: It would only affect you if you tried to remove/reinstall the NVIDIA driver since yesterday when the snappy patch was uploaded.
[20:54] <mamarley> Ooh, this is actually worse, it seems that it is preventing some people from logging in...
[20:55] <soee> me :D
[20:56] <acheron_uk> I updated to 364.19-0ubuntu0~gpu16.04.5 earier today from the ppa
[20:56] <mamarley> acheron_uk: Do you have "snapd" installed?
[20:56] <acheron_uk> yes
[20:57] <acheron_uk> odd. not that I'm complaining
[20:57] <mamarley> Yeah, I don't get that...
[20:58] <ahoneybun> what's up with nvidia soee?
[20:58] <soee> grr i posted in comment that i use 16.10 while im on 16.04, can i edit comment?
[20:58] <soee> ahoneybun: breaks sddm 
[20:58] <ahoneybun> again?
[20:59] <soee> they patched driver and make it a bit broken
[20:59] <soee> not enough tests i think :)
[20:59] <ahoneybun> I've not updated the laptop in a bit
[20:59] <ahoneybun> I did the desktop but no issue
[20:59] <ahoneybun> might be on a older version
[20:59] <mamarley> They uploaded it to proposed, which technically isn't supposed to be used.
[21:00] <soee> um, i see :)
[21:00] <mamarley> soee's problem was caused by the fact that I went ahead and patched the graphics-drivers PPA packages with it too.
[21:00] <ahoneybun> I was having some weird kwin issues but that was after I played Shadow of Mordor
[21:00] <soee> mamarley: not a problem for me :D i like to break my system
[21:01]  * acheron_uk is afraid to change anything now in case of breakage
[21:01] <mamarley> And I tested it, but it didn't happen on my system.
[21:01] <ahoneybun> mm I wish my preset for my keyboard would stick
[21:01] <ahoneybun> turns off every reboot
[21:02] <soee> throw the keyboard through the window :D
[21:02] <ahoneybun> not a 160 dollar one
[21:02] <ahoneybun> XD
[21:03]  * ahoneybun works on new blog post
[21:08] <ahoneybun> HEY a green light!
[21:10] <mamarley> soee: It looks like all the problems are caused by failure to unmount that directory, but I haven't a clue why it is even trying to unmount it at that point.  I don't know much about Snappy and I generally try not to fool around with stuff I don't understand, because that could cause even more brokenness.
[21:12] <mamarley> For the moment I am not going to try to do anything with it.  But like I said, I am subscribed on both of those bugs so I will know as soon as anything changes.
[21:15] <soee> mamarley: thank you for your help
[21:17] <mamarley> Sorry for the trouble.  When I uploaded that patch into graphics-drivers, I didn't realize it was only in proposed and not actually released yet.
[21:17] <mamarley> I wonder if I should disable that unit and reupload.  Or just back it out completely.
[21:18] <mamarley> I would love to ask ricotz or tseliot about this, but neither is around.
[23:31] <mamarley> soee: I reverted the patch in graphics-drivers.  The new packages are compiling now.
[23:31] <soee> mamarley: ok, thank you :)
[23:32] <mamarley> There was also another bug where the "start" or "stop" command was apparently getting run from a different package than from which the unit was installed, causing a race condition and giving even more trouble.
[23:35] <clivejo> wacky races