[05:22] <maslen> I'm trying to set up the aflize docker image (https://github.com/d33tah/aflize) , but when I run docker with "docker run -ti d33tah/afl-sid bash", I get an error: "System error: exec format error" . I'm on Ubuntu 16.04. This is my first time using docker, so I apologize for any noob mistakes.
[05:30] <ngaio> I'm seeing severe graphical corruption with Qt programs in xenial
[06:00] <ngaio> for example, bring up the About window in VLC
[09:23] <lordievader> Good morning.
[11:15] <ngaio> would anyone like to assist me in possibly filing a bug about severe graphics corruption with Qt programs in Xenial (assuming no one did already, which would be surprising)?
[12:04] <enyc> ngaio: look up if its' already there in  https://bugs.launchpad.net/  ?? -- i'm not an expert on ubuntu bug reporting tbh
[12:26] <BluesKaj> Hey all
[12:26] <ngaio> BluesKaj, you're a KDE user right?
[12:27] <BluesKaj> ngaio, yes
[12:27] <ngaio> and/or packager
[12:27] <BluesKaj> tester
[12:27] <ngaio> have you seen or heard of severe graphical corruption with Qt programs in xenial?
[12:28] <BluesKaj> no, just the odd freeze
[12:28] <ngaio> e.g. About screen in VLC
[12:28] <ngaio> I get only the title bar of the About window, which is the full screen width, and no content
[12:29] <ngaio> do you see that?
[12:31] <BluesKaj> no, I the about  popout
[12:31] <BluesKaj> get
[12:33] <BluesKaj> http://ibin.co/2WwBqlvq6MYH
[12:33] <BluesKaj> that's what I'm getting
[12:34] <ngaio> hmm okay. I wonder why I'm not. I'm running the standard Unity theme
[12:35] <ngaio> my own PyQt program is severely corrupted and in fact doesn't even display
[12:35] <BluesKaj> I'm on plasma 5.5.4
[12:40] <BluesKaj> ngaio, got python3 ?
[12:40] <lordievader> ngaio: Qt4 or Qt5?
[12:41] <ngaio> python 3.5, Qt 5
[12:42] <lordievader> Does it throw errors in the terminal?
[12:42] <ngaio> yes, I don't recall exactly, but something about gtk widget
[12:43] <ngaio> (i'm dual booting, in 15.10 at the moment)
[12:43] <ngaio> the gtk widget error is surprising considering they're Qt programs
[12:43] <lordievader> Yeah, that is quite odd.
[12:43] <lordievader> Is it possible to pastebin your code?
[12:43] <ngaio> I did a search on the specific error, and found bugs from 2011 relating to Qt 4
[12:44] <ngaio> it's not just my code though - VLC shows the same problem
[12:44] <ngaio> it gives the same error
[12:45] <BluesKaj> how about 15.10 are you on unity there too? ot kde?
[12:45] <BluesKaj> or
[12:45] <ngaio> Unity & KDE on 15.10.... won't install KDE on 16.04 unless / until the bug with SSO is fixed
[12:45] <ngaio> the telepathy bug
[12:46] <BluesKaj> oh, telepathy, ,never use it
[12:48] <lordievader> Wait, you have the problem on both 15.10 and 16.04?
[12:49] <ngaio> lordievader, no, it only shows up in 16.04
[12:50] <ngaio> in 15.10 it works as expected
[12:51] <ngaio> I'll reboot into 16.04 now to get the exact error message on the terminal
[12:53] <ngaio> to answer your question about my code, it's on launchpad as lp:rapid. You can get it with bzr. Don't run the setup.py though, I'm still coding that and in any case some dependencies can only be installed with pip :-D
[12:53] <ngaio> screenshot is here: http://damonlynch.net/rapid/screenshots/beta/20160128rpd.png
[12:54] <ngaio> brb
[12:59] <ngaio> this the the VLC about window I'm seeing: http://ibin.co/2WwJn8jsja84
[13:00] <ngaio> that shows the error messages on the console too
[13:00] <lordievader> Hmm, at first I thought it was a problem with your application, specifically. But if more applications suffer the same fate it would make you think a library is the culprit.
[13:01] <lordievader> !info vlc xenial
[13:01] <ngaio> many Qt applications are totally unusable
[13:02] <lordievader> Haven't run (Kubuntu) Xenial for a while myself, but last time I ran it I didn't notice any problems.
[13:02] <ngaio> what's odd is that VirtualBox seems to work okay
[13:03] <ngaio> at least the main windows and the preferences
[13:03] <ngaio> I dont' dare start an actual VM
[13:04] <lordievader> Why not?
[13:06] <BluesKaj> one thing I did notice is thay 16.04 is much slower to load tje desktop after boot and packages than 14.04, and I'm dual booting both OSs on the same ssd
[13:07]  * BluesKaj opens the blinds to get more light
[13:09] <ngaio> lordievader, because I don't want VirtualBox breaking at the moment when it tries to load another O/S.
[13:11] <maslen> Does docker require an x64 host ?
[13:12] <ngaio> aha! when I run my app with Motif style, it works
[13:12] <ngaio> so it's a Qt theme problem
[13:14] <lordievader> Oehh, would you mind submitting a bug report for that?
[13:14] <ngaio> yes I'm just trying to figure out what the default theme is
[13:15] <BluesKaj> maslen, not to worry 16.04 is multiarch by default
[13:15] <ngaio> lordievader, do you know what package I should file it against?
[13:15] <ngaio> I have no idea what the default Qt theme under Unity is called
[13:16] <BluesKaj> orange and purple :-)
[13:17] <maslen> BluesKaj: What does that mean?
[13:17] <BluesKaj> oh and brown
[13:18] <ngaio> maslen, we're talking about the default theme for Qt programs that are run under the Unity desktop
[13:18] <lordievader> ngaio: I think the theme is called breeze, but I am not sure if that is a seperate package and/or if Unity uses that by default.
[13:18] <maslen> ngaio: And I was asking about docker :)
[13:18] <BluesKaj> docker can run on both 32 and 64bit
[13:19] <BluesKaj> it's been around since kde3
[13:19] <BluesKaj> and gnome
[13:29] <BluesKaj> maslen, are you talking about the container app or the graphical panel ?...there seems to be a duplicate name for 2 differnt applications
[13:31] <BluesKaj> !docker
[13:31] <maslen> the container app. docker.io
[13:32] <k1l> who runs 32bit hosts anyway
[13:33] <BluesKaj> because when I refernced docker in muon this what I got: "Docker is a docking application (WindowMaker dock app) which acts as a system tray for any desktop environment"
[13:35] <BluesKaj> Think the packagers better come up with a new name for the docking app in the DE
[13:38] <maslen> k1l: I've been using x86 because of ASAN : https://github.com/mirrorer/afl/blob/master/docs/notes_for_asan.txt
[13:40] <k1l> maslen: you are aware that this is not a real issue on todays ram sizes? 32bit is going to die slowly. faster than flash, but still slowly. chrome dropped 32bit support. first linux distributions dropping 32bit isos.
[13:40] <ngaio> bug #1545450 is filed
[13:47] <maslen> k1l: I can only allocate so much RAM to my VMs
[14:13] <k1l> https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule  doesnt have the schedule for the pointreleases so far
[16:12] <TheOnlyBouncer> good day
[16:12] <TheOnlyBouncer> i have a Lenovo yoga 2-11 which is running the current alpha for 16.04 but i am getting occasional total system freezes. Since i can not do anything, is there a way to debug this to commit a bug report?
[16:12] <TheOnlyBouncer> its running a Intel Pentium N3520 processor
[16:13] <TheOnlyBouncer> and it seem to happen mostly during gpu access
[16:16] <TheOnlyBouncer> i must admit that i did not try another distro or version of ubuntu yet (since i really wanted a 4.4 kernel or newer), but i rather figure out how to debug this :)
[17:23] <penguin42> TheOnlyBouncer: Do you have it connected to a network and can you log in when it fails?
[17:25] <penguin42> TheOnlyBouncer: Also, how dead is it - e.g. does the capslock key still change the state of the capslock LED ?
[18:24] <TheOnlyBouncer> penguin42, nothing reacts anymore, at all, total system freeze (ie. keyboard not reacting etc)
[18:24] <TheOnlyBouncer> otherwise i would have switched to a terminal and did some debugging
[18:25] <TheOnlyBouncer> did not try if i could ssh in it when crashed though
[18:27] <penguin42> TheOnlyBouncer: Worth a try, otherwise, file a bug anyway - probably   ubuntu-bug linux     just after you reboot
[18:33] <TheOnlyBouncer> penguin42, are there any automated logs for crashes that get fetched this way?
[18:33] <TheOnlyBouncer> to be honest, i would rather find out what actually goes wrong so i can hotpatch it
[18:33] <TheOnlyBouncer> i kind of need that system running
[18:34] <penguin42> TheOnlyBouncer: Yeh that can be tricky depending what broke
[18:34] <penguin42> TheOnlyBouncer: I'd start by seeing if you can ssh in, if you can then that makes it a LOT easier to see what's going on
[18:35] <penguin42> TheOnlyBouncer: But check /var/log/syslog and syslog.1 or kernel.log and kern.log.1  to  see if they have anything from the crash, but if it crashes hard it often can't write the logs
[18:36] <TheOnlyBouncer> hmm ok will try, thanks
[18:36] <TheOnlyBouncer> i don't think it is a kernel panic, which makes me happy :P since that would definitely shown anything
[18:37] <penguin42> TheOnlyBouncer: There are some other tricks as well - e.g. if you can get it to fail while it's in text mode console then you might be able to see a crash message - but it's quite hard if it just stops
[20:57] <alkisg_away> Has anyone experienced problems in xenial with services not starting on boot _some_ times?
[20:58] <alkisg> E.g. network-manager, dnsmasq, even lightdm...
[20:58] <alkisg> Maybe one out of 20 boots or so
[20:58]  * alkisg has seen that in 3 different installations so far
[21:11] <lordievader> Haven't noticed it yet. Is this a recent trend?
[21:13] <alkisg> I'm not sure, I've been using xenial on one pc since months, but I only rebooted it once per month or so... the other 3 installations are recent, from 2 to 20 days old, and they all have the issue
[21:13] <lordievader> Hmm, haven't booted my Xenial install in a while. But I can't remember such as issue happening.
[21:15] <alkisg> Thanks, I'll check more and file a bug report on that then :)