[01:26] <apb1963> QNativeImage: Unable to attach to shared memory segment. 
[01:27] <ohsix> nice try
[01:27] <apb1963> I get this error using Okular.  It shows a problem with the screen... essentially you can't see portions of the page.  However, the problem is not limited to Okular...
[01:28] <apb1963> Not sure where to from here, but I figured you guys would be a good starting point.
[01:28] <apb1963> ^go
[01:30] <apb1963> There are numerous errors produced by X after that error, but I get the feeling the X errs are a side effect of not having the mem segment.
[01:31] <apb1963> Well, the cause being the missing segment rather than a side effect... but you know what I mean.
[01:32] <apb1963> Errors like this:
[01:33] <apb1963> X Error: BadPixmap (invalid Pixmap parameter) 4
[01:33] <apb1963>   Major opcode: 56 (X_ChangeGC)
[01:33] <apb1963>   Resource id:  0x0
[01:34] <apb1963> At this point, even right clicking and trying to copy or paste is a chore, because the menu is obscured or blank, however you want to picture it.
[02:03] <apb1963> Oh and... the rightclicking problem is system wide... not limited to any program.  Once it starts, I have to reboot to fix it.  I've rebooted twice now and it's starting to become a little more frequent, and is starting to become a major issue.
[02:05] <apb1963> If anyone wants to use something like teamviewer or whatever to see it in action, I'm open to that.
[02:06] <apb1963> 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[02:07] <apb1963> Ubuntu 14.04.3 LTS
[02:11] <ohsix> you're using kde though? what is using the most memory in xrestop
[02:20] <apb1963> bash: xrestop: command not found
[02:20] <apb1963> ohsix: ^^
[02:22] <apb1963> E: Unable to locate package xrestop
[02:41] <apb1963> ohsix: kwin followed by libreoffice/writer and then firefox
[03:14] <apb1963> ohsix: #kde-devel helped me track it down.  java memory leak.   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799587  Thanks for pointing me in the right direction :)
[03:14] <apb1963> Any idea when it will make it into ubuntu 14.04 ?
[03:15] <apb1963> or will it be 14.05 at that point? :)
[03:16] <apb1963>  https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1512760
[03:16] <ohsix> i like the comments on the bug, kde/plasma isn't very usable without bugs ;D
[03:16] <apb1963> haha
[03:22] <apb1963> ohsix: by the way... PovAddict in #kde-devel was the person that tracked it down.... and then found the bug had already been reported.  Just in case you want to talk to him about it.
[13:30] <marga> infinity, 3.13.0-68 was released to trusty-updates on Nov 10th, but the installer has had no updates since Nov. 4th.  I'm getting an install failure because of this (mismatch between running kernel and installed kernel, when doing update-initramfs after dkms installation). Is there a bug about this?
[13:34] <apw> marga, not sure there is a bug about it, no.  i think he will be aware now tho
[13:35] <marga> now that I mentioned it? Or already before that?
[13:37] <apw> well it got mentioned on #u-d as well, so i suspect he'll get the message, and indeed i'll be chatting to him about it too as i got highlighted about it on #u-d
[13:37] <marga> ah, ok.
[13:37] <marga> What's the normal process for updating the installer when a new kernel comes around?
[13:44] <apw> in part i am unsure, which is why i am going to be talking about it
[15:39] <cmagina> The stable release pull for the current trusty proposed kernel carries a patch that breaks arm64. The issue was seen on wily as well and was worked around by disabling the new config option added by the patch. I added a comment to the stable release bug, bug #1514853
[15:39] <ubot5`> bug 1514853 in linux (Ubuntu Trusty) "Trusty update to 3.13.11-ckt29 stable release" [Undecided,Fix committed] https://launchpad.net/bugs/1514853
[15:53] <tseliot> apw: I can't reproduce the failure with bcmwl
[15:53] <tseliot> apw: and linux 4.3
[15:54] <apw> tseliot, hrm
[15:54] <apw> tseliot, i386 right ?
[15:56] <apw> tseliot, http://paste.ubuntu.com/13299698/ is what ADT gets
[15:59] <tseliot> apw: that should help. Thanks
[16:34] <dsmythies> Just passing along something: I observe that http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc1-wily/ is having the same problem as I was. Kernel 4.4-rc1 would not compile until I applied this patch: https://lkml.org/lkml/2015/11/6/987 
[16:39] <apw> dsmythies, yep, those are raw builds done from the tip of the tree, if the tree is broken they don't build
[17:04] <henrix> cmagina: hi! re. bug #1502946 (CONFIG_ARM64_ERRATUM_843419), have you actually tried to boot that trusty kernel and reproduced that bug?
[17:04] <ubot5`> bug 1502946 in linux (Ubuntu Wily) "kernel crash on m400 arm64 server cartridge" [Critical,Fix released] https://launchpad.net/bugs/1502946
[17:05] <henrix> cmagina: because wily actually contains CONFIG_ARM64_ERRATUM_843419=y (the same as trusty)
[17:05] <cmagina> henrix: yes, i have a log, just need to attach it
[17:05] <henrix> cmagina: no need, i just wanted to understand exactly what i should do because trusty seems to have the same config 
[17:07] <cmagina> henrix: really? hmm...this is the bug where it was supposedly set to 'n' https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946
[17:07] <ubot5`> Ubuntu bug 1502946 in linux (Ubuntu Wily) "kernel crash on m400 arm64 server cartridge" [Critical,Fix released]
[17:07] <cmagina> [Config] CONFIG_ARM64_ERRATUM_843419=n
[17:08] <cmagina> 4.2.0-16.19) wily
[17:08] <henrix> cmagina: right, but the wily kernel in -proposed seems to be closing that bug by reverting that patch
[17:08] <cmagina> henrix: maybe dannf's upstream fix was accepted and pulled into wily after 16.19
[17:09] <henrix> cmagina: ah, wily also contains this: b6dd8e0719c0 ("arm64: errata: use KBUILD_CFLAGS_MODULE for erratum #843419"
[17:09] <cmagina> henrix: yeah, that's dannf's fix
[17:10] <henrix> cmagina: ok, cool.  so... i guess we need that in trusty as well
[17:10] <cmagina> henrix: yeah, that would be perfect
[17:10] <henrix> cmagina: and in lts-utopic too.  (we're building arm64 in utopic, right?)
[17:11] <cmagina> henrix: yes
[17:11] <henrix> cmagina: ok, thanks
[17:11] <cmagina> henrix: i hadn't gotten to check the other releases yet. are we still supporting utopic? thought it ended and we're now on vivid
[17:12] <henrix> cmagina: right, utopic has EOL'ed, but we're still doing lts-utopic for a couple more cycles
[17:12] <cmagina> henrix: ah, ok
[17:13] <henrix> cmagina: grr... looks like we have the same thing on vivid.
[17:14] <cmagina> henrix: so, everything up to wily then. arm64 seems prone to these kinds of regressions where a stable release patch breaks it, but there is already a fix, just not in that stable release
[17:15] <henrix> cmagina: correct.  i'll start working on that.  thanks for reporting. 
[17:16] <henrix> cmagina: btw, do you have another bug i could you for SRU'ing this?
[17:16] <henrix> s/you/use
[17:16] <cmagina> henrix: np, thanks for fixing. yes, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516682
[17:16] <ubot5`> Ubuntu bug 1516682 in linux (Ubuntu) "a trusty stable release patch breaks module loading on arm64" [Undecided,Incomplete]
[17:17] <henrix> cmagina: awesome, thanks!
[17:18] <cmagina> henrix: welcome :)