[00:48] <clivejo> grrrr I hate firefox
[00:54] <clivejo> I cant load a buildlog without it crashing!
[00:58] <valorie> I've given up FF for just about everything
[00:58]  * mamarley too, sadly.
[00:59] <clivejo> its was fine until the last update
[00:59] <clivejo> now its useless
[01:00] <mamarley> For me I pretty much gave it up a while back because it doesn't have good performance on my 4K monitor.
[01:00] <clivejo> crashes so often 
[01:00] <valorie> for me, it just got more and more annoying until chromium became my browser of choice
[01:00] <valorie> how I miss good old konq
[01:01] <mamarley> One nice thing that Chrom{e|ium} has is high-resolution scrolling support on Synaptics touchpads.
[01:23] <ximion> valorie: nice mail RE Flames_in_Paradise
[01:23] <ximion> that guy is on fire
[01:24] <ximion> I am mostly working on AppStream stuff at time and constantly see him running by fixing metainfo files or triaging arbitrary other KDE related bugs ^^
[03:19] <DarinMiller> FYI: Noticed a comment awhile back about print screen button pectacle install . Before restart, no spetacle shortcuts were defined, after restart, shift-print and meta-print are assigned to fullsceen and active window under Custom shortcuts. Reconfiguring the print button complains of another assignment but works just fine.
[04:27] <valorie> thanks, ximion
[04:29] <sgclark> DarinMiller: good to know, thanks. And it arrived thanks!!!!!!
[04:30] <DarinMiller> Excellent!!  SSD also?
[04:32] <sgclark> not yet. hopefully tomorrow :)
[05:43] <Mirv> have you noticed the plasma-workspace autopkgtest problems eg at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#kwin ?
[05:43] <Mirv> they're blocking my qtdeclarative silo too at the moment (also CI Train executes autopkgtests, already before publishing to proposed)
 We have noticed. It is trying to build old plasma with new kwin which is a recipe for failure. yofel is trying to sort out how to make them stop that.
[06:20] <Mirv> thanks!
[08:49] <mparillo> DarinMiller: You are correct. Both meta- and shift- prt scr work after a re-boot (perhaps they did before the reboot, but I did not try) and prt scr with no modifier key does not work. Funny, though. It simply saves to Pictures. Didn't ksnapshot bring up the image where you could choose where to save it?
[08:50] <valorie> mparillo: it did
[08:50] <mparillo> valorie: TY, but aren't you on the west coast?
[08:51] <mparillo> I am up obscenely early, you are up obscenely late.
 Morning friends
 Yes Prt Scr would launch Ksnapshot, and leave you with a UI, you could then Save or Send to an application.
 Very handy tool, which I miss
[08:53] <valorie> 'tis almost 2am, yeah
[08:56] <soee_> hiho :)
[09:02] <yofel> mgraesslin: I tried Xenial on a machine with an ATi GPU in my office, which looked like http://people.ubuntu.com/~yofel/pics/Screenshot_20160318_095855.png
[09:02] <yofel> against what should I be filing a bug?
[09:04] <mgraesslin> I don't know
[09:04] <soee_> i accidently updated apps to 15.12.3 because of having this ppa enabled
[09:04] <mgraesslin> it doesn't look like a KWin bug
[09:04] <yofel> looks to me like all QML components render black.. well, thanks anyway
[09:04] <mgraesslin> it's not only QML Components
[09:05] <mgraesslin> you have the white areas in the background selection
[09:05] <mgraesslin> which means that some parts of QML components render still correctly
[09:05] <mgraesslin> but yeah overall it looks like a problem with OpenGL
[09:21] <mparillo> Thanks to the great folks at KFN, I solved my prt scr behavior (and it brings up the dialogue I missed): delete ~/.config/khotkeysrc and re-login. https://www.kubuntuforums.net/showthread.php?69815-Screenshoot&p=385279#post385279
[09:26] <soee_> now find solution for my bug ... :D
[09:49] <soee_> do you also have since yesterday all extra repositories returning warnings about The repository is insufficiently signed by key ... ?
[09:49] <soee_> something about weak digest - does Ubuntu changed omething with those keys and repository mainteiners have to update them ?
[10:05] <totof-at-work> hi all I've read somewhere that since 1.2.7 version of APT SHA1 is considerd as obsolete
[10:05] <totof-at-work> results with this error message
[10:08] <jmux> yofel: also my dual-screen KDE setup in Xenial broke with one of the updates this week. ATI GPU too.
[10:09] <yofel> define "broke"? we had a lot of kscreen breakage in 5.5, with "most" of that fixed in 5.5.4 and 5.5.5
[10:09] <jmux> Basically external screen stays blank after wakeup; dmesg has "[drm:radeon_dp_link_train [radeon]] *ERROR* displayport link status failed"
[10:09] <yofel> urgh
[10:10] <yofel> #ubuntu-x might have pointers, but that's probably kernel or driver
[10:11] <jmux> yofel: after finding those in all the kernel output, I think so too
[10:12] <jmux> And there is also still https://bugs.kde.org/show_bug.cgi?id=357007 for me. And I'm seeing graphical glitches and have crashing apps now
[10:12] <mamarley> totof-at-work: https://bugs.launchpad.net/launchpad/+bug/1556666
[10:13] <yofel> soee_: ^
[10:14] <jmux> yofel: and "helping error messages like http://snag.gy/q7Wx2.jpg
[10:14] <totof-at-work> mamarley: thks for the bug ref :D
[10:14] <yofel> lolwhat o.O?
[10:15] <mamarley> Note that the warning messages do not mean that packages won't be installed from the PPA.  It only looks like they won't.
[10:16] <mamarley> However, there are some third-party repositories (such as the Chrome repository and Bintray) that are completely broken by this change, so I have APT held at 1.2.6.
[10:16] <yofel> yeah, chrome was "acceptable colleteral damage"
[10:16] <mamarley> Someone already complained to Google.  Considering they are leading the charge to deprecate SHA1, it shouldn't be long.
[10:17] <yofel> true
[10:17] <mamarley> I also let the Bintray people know, but their response was much less encouraging: "Thank you for your input. We will discuss this issue internally with our Product Manager."
[10:17] <jmux> And somehow the task bar changed to this: http://snag.gy/68gLm.jpg - couldn't find a way to restore the old look and the reconq highlight looks broken
[10:25] <jmux> Last week after the update I thought "Some glitches, but that's expected from a beta". I'll ask on #ubuntu-x and otherwise will open a bug report.
[10:40] <jmux> yofel: BTW linux 4.4.0-12.27 had a "Pull in upstream AMD code (amdgpu) in Xenial (LP: #1546572)"
 @Yofel rebased calligra 2.9.10 is uploaded to misc staging and packaging pushed to bzr. Will you take a wee look when you get a chance?
[10:57] <yofel> in the evening, thanks
[11:08] <clivejo> soee_: how are apps 15.12.3 looking?
[11:09] <soee_> clivejo: all available installed fine
[11:09] <clivejo> would you mind testing calligra 2.9.10 in the misc staging for me?
[11:10] <soee_> sure
[11:12] <clivejo> and anyone else who wants to test :) add "sudo add-apt-repository ppa:kubuntu-ppa/staging-misc" and install calligra
[11:19] <soee_> clivejo: installed fines, all apps start fine
[11:20] <clivejo> glad to hear that!
[11:24] <mparillo> clivejo: I added your ppa, and installed calligra. It was added to the Dolphin Open with menu, but did not take over from Libre Office.
[11:24] <mparillo> Is that working as designed?
[11:25] <BluesKaj> Hi folks
[11:25] <jmux> yofel: Just rebooted 4.4.0-13-generic with the radeon module compiled from the 11.26 source - no more graphical glitches, Displayport works again
[11:25] <mparillo> I successfully opened an .ods and and .odt in the Calligra spreadsheet and word processor that I had originally created with LO.
[11:26] <clivejo> mparillo: that I dont know
[11:26] <yofel> telegram: hm, -13 didn't help me personally, guess I'll go to building the driver then... thanks for the update
[11:26] <yofel> jmux: ^
[11:27]  * clivejo wonders if yofel knows hes talking to a bot
[11:27] <yofel> ubottu: how are you today my fair lady?
[11:27] <yofel> what a shame
[11:30] <jmux> yofel: and the diff is just 500 lines. The -13 is broken. But I just copied the radeon source from 4.4.0-11(.26) and build the module against the -13 kernel and that works.
[11:30] <jmux> works for me (TM)
[11:31] <clivejo> hi BluesKaj
[11:32] <jmux> And most of the lines in the patch change the display port handling.
[11:32] <BluesKaj> Hey clivejo
[11:33] <clivejo> hummm plasma is picking up icons again
[11:34] <soee_> clivejo: can you take a look in a free time at this 2 red http://qa.kubuntu.co.uk/ppa-status/applications/build_status_15.12.3_xenial.html ?
[11:35] <clivejo> they are "problem" packages moved into the manual folder by the staging script
[11:35] <clivejo> dont want to step on sgclark's toes
[12:06] <clivejo> yofel: anything on your to-do list, that I can do?
[12:12] <yofel> look at why the kwin and kopete autopkgtests are failing?
[12:12] <yofel> kopete failed on all archs IIRC, so that you should be able to reproduce
[12:12] <clivejo> the key to my question is "I can do"
[12:14] <yofel> well, you won't know that before you look at it. 
[12:14] <yofel> but otherwise...
[12:15] <yofel> clivejo: do you think you can do some basic python scripting by now?
[12:15] <clivejo> doubt it!
[12:15] <yofel> ruby? :D
[12:16] <clivejo> basic
[12:16] <yofel> hm
[12:16] <sgclark> morning
[12:16] <yofel> oh hey
[12:17] <sgclark> clivejo: te stepping is allowed and encouraged as long as you document what you are working on here: https://notes.kde.org/p/kubuntu-ninjas
[12:17] <sgclark> s/te/toe/
[12:18] <sgclark> just woke up but will do those apps here in a few. 
[12:57] <soee_> yofel: will you upload calligra from staging-misc to archive ?
[12:59] <yofel> I'll upload it from bzr, which is what clive pointed me to (IIRC)
[12:59] <yofel> but yes, we should update calligra
[12:59] <soee_> nice, thank you
[13:00] <sgclark> yofel: did kdevelop get uploaded?
[13:00] <yofel> no
[13:00] <yofel> can't you just upload it yourself?
[13:00] <yofel> it's just bugfixes anyway, right?
[13:01] <sgclark> it is, not sure I have perms on that, will try
[13:01] <yofel> do you know how to look at our packageset?
[13:02] <sgclark> yofel: seed?
[13:03] <yofel> no, that's the definition, not the ACL
[13:03] <yofel> bzr co lp:ubuntu-archive-tools; cd ubuntu-archive-tools; ./edit-acl -P kubuntu -S xenial query
[13:03] <yofel> that's the full list of sources that you may upload
[13:03] <sgclark> oh
[13:03] <sgclark> then no
[13:43] <melodie> hi
[13:45] <melodie> a message to yofel and mitya57 : we have installed Kubuntu Trusty on a beautiful new computer yesterday, no windows inside at all, and added the HWE 4.4 kernel on it as you advised me! Thanks a lot! That worked as a charm! :D
[13:46] <melodie> The fonts were really really too tiny also, in the very large high resolution screen, but we managed to do the install as is from the live usb stick and fixed the size of the fonts after, once the install done (using a second computer where I had formerly done the install as a test, which helped find more easily with normal size fonts where to look in order to configure the fonts)
[13:48] <mamarley> yofel: It actually looks like Google has already started using the SHA256 package signatures.  I don't get an error anymore; just a warning.
[13:49] <yofel> oh, nice
[13:49] <mamarley> So now I can upgrade to APT 1.2.7 on all my boxes except the one running tvheadend (which comes from bintray).
[13:50] <melodie> yofel mitya57 the main components for this tower, so you get the idea, a silent tower, http://www.ldlc-pro.com/fiche/PB00147836.html a good mobo, http://www.ldlc-pro.com/fiche/PB00192574.html a CPU Intel Skylake 6th generation, 8 GB RAM, and this screen : http://www.ldlc-pro.com/fiche/PB00181462.html
[13:50] <melodie> I wanted to bring this feedback for your good advice. :)
[13:50] <yofel> interesting, thanks for the feedback :)
[13:50] <melodie> my client is happy, thanks to your help!
[13:52] <melodie> well, before I installed the 4.4 13 kernel, the screen was starting to act weird, flicker from "screen/no image/screen no image", so I just did the normal update, then added the 4.4 kernel the way you told me to, rebooted, unticked the additional source for updates : problem solved.
[13:53] <melodie> so all good, and keep on the good work! :D
[13:53] <melodie> I have to quit now, wishing you all a nice day.
[13:59] <clivejo> !info digikam xenial
[14:02] <clivejo> digikam could do with a archive sync too?
[14:02] <clivejo> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/digikam/changes
[14:06] <yofel> right, although it's uninsallable anyway
[14:06] <yofel> *uninstallable
[14:07] <yofel> oh right, there was that
[14:07] <yofel> clivejo: you could figure out if the 2 libkipi's can be made coinstallable
[14:07] <clivejo> 4.14 is current stable?
[14:07] <yofel> yes
[14:08] <yofel> (the alternative would be to remove digikam and later try to get a working digikam 5 into the official backports)
[14:08] <clivejo> one is KDE4 other is kf5, why wouldnt they be co-installable?
[14:08] <yofel> the -data packages conflict
[14:08] <clivejo> ah
[14:13] <clivejo> they seem to share 4 files
[14:13] <clivejo> /usr/share/icons/hicolor/16x16/apps/kipi.png, /usr/share/icons/hicolor/22x22/apps/kipi.png, /usr/share/icons/hicolor/32x32/apps/kipi.png, /usr/share/icons/hicolor/48x48/apps/kipi.png
[14:14] <clivejo> sorry 5
[14:14] <clivejo> all icons
[14:35] <yofel> if it's really just that, then removing those from the 4 -data, and making depend on 5 -data would be an idea
[14:35] <yofel> *making that depend
[14:42] <clivejo> Im comparing http://packages.ubuntu.com/xenial/all/libkipi-data/filelist to http://packages.ubuntu.com/xenial/all/libkf5kipi-data/filelist
[14:47] <yofel> looks about right... maybe make the changes, throw them into a ppa and fix the versioned breaks in kf5kipi. Then we can test that
[14:47] <yofel> if that works it would be great
[14:47] <clivejo> Ill have to try it later
[14:47] <clivejo> need to go do a few things
[14:47] <yofel> then we would still not have any kipi plugins for spectacle and gwenview, but *shrug*, that's backports material
[14:49] <clivejo> why dont they factor out the plugins from digikam into a frameworks package or something?
[14:50] <clivejo> or apps like libkf5kipi
[14:50] <yofel> they didn't want to bother with all the release maintenance overhead. So they took the formerly separate kipi-plugins, digikam and a couple other libs and bundled everything in one digikam SC
[14:50] <clivejo> :/
[14:51] <clivejo> doesn’t seem sensible to me!
[14:51] <yofel> I mean, we just need to package digikam 5, beta 3 or so was released a while ago, have fun
[14:51] <clivejo> LOL
[14:51] <clivejo> not my idea of fun!
[14:51] <yofel> why not? Digikam is the biggest consumer of the plugins and the developers are the same. That way they at least have a tested software bundle
[14:51] <sgclark> lol a few ports I am not looking forward to, that , kdevelop, and calligra
[14:52] <yofel> yeah, that needs some talking to debian. I don't want us to do that twice
[14:53] <sgclark> agree
[14:57] <genii-testing> Seems something with gpgv doesn't like the Kubuntu PPA keys anymore. I'm getting a bunch of warnings like this: "W: gpgv:/var/lib/apt/lists/ppa.launchpad.net_kubuntu-ppa_staging-kdeapplications_ubuntu_dists_xenial_InRelease: The repository is insufficiently signed by key E4DFEC907DEDA4B8A670E8042836CB0A8AC93F7A (weak digest)"
[14:58] <mamarley> genii-testing: https://bugs.launchpad.net/launchpad/+bug/1556666
[15:00] <genii-testing> OK
[15:19] <BluesKaj> getting tired of krunner crashing at the slightest mouse movement
[16:29] <ejat> mamarley: W: gpgv:/var/lib/apt/lists/ppa.launchpad.net_juju_stable_ubuntu_dists_xenial_InRelease: The repository is insufficiently signed by key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 (weak digest)
[16:29] <ejat> W: gpgv:/var/lib/apt/lists/ppa.launchpad.net_mamarley_quassel_ubuntu_dists_xenial_InRelease: The repository is insufficiently signed by key A0D47AB4E99FF9F9C0EA949A26F4EF8440618B66 (weak digest)
[16:33] <mamarley> ejat:  https://bugs.launchpad.net/launchpad/+bug/1556666
[16:36] <ejat> mamarley: ok thanks 
[19:21]  * clivejo yawns
[20:27]  * soee wrrrr..............
[21:24] <yofel> clivejo: did you make progress with kipi?
[21:25] <clivejo> I didnt, been looking at the kde wiki
[21:25] <yofel> ok
[21:30] <yofel> clivejo:   4     - Removed upstream patch (upstream_qmax.diff)
[21:30] <yofel> why?
[21:30] <yofel> wrt. calligra
[21:59] <clivejo> yofel: because those changes are already in the source
[21:59] <yofel> ok
[22:00] <clivejo> I cant find the git
[22:00] <yofel> nah, if that's it then it's fine
[22:00] <clivejo> but I check the source code and the changes are actually in the tar ball
[22:00] <clivejo> is that not the right thing to do?
[22:01] <yofel> it is, the changelog just wasn't clear about why the patch was removed
[22:01] <clivejo> I thought upstream meant that it was cherry picked from upstream git to fix a problem
[22:02] <clivejo> and in next release the issue will be fixed so patch can be removed
[22:02] <clivejo> how do I explain that?
[22:02] <yofel> except that "next" release can also mean next major release. So that's not necessarily an automatism
[22:03] <clivejo> in the changelog?
[22:03] <yofel> I changed it to "- Remove upstream_qmax.diff - applied upstream"
[22:03] <yofel> that's what we usually write 
[22:04] <clivejo> you pushing that to bzr?
[22:04] <yofel> yes
[22:05] <clivejo> ok, I also uploaded it to misc
[22:06] <clivejo> I had a problem merging in bzr
[22:06] <clivejo> seemed to totally mess up the changelog
[22:07] <clivejo> so have to edit it manually
[23:12] <yofel> The signer of this package is lacking the upload rights for the source package, component or package set in question.
[23:12] <yofel> uhm.. how did that happen..
[23:13] <yofel> I don't have the energy for this right now
[23:13] <yofel> nini
[23:13] <sgclark> night yofel!