[05:55] <lotuspsychje> good morning to all
[06:34] <lotuspsychje> http://news.softpedia.com/news/canonical-patches-multiple-kernel-vulnerabilities-in-all-supported-ubuntu-oses-510156.shtml
[06:35] <lotuspsychje> !info linux-image-generic xenial
[06:35] <ubot5`> linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 4.4.0.47.50 (xenial), package size 2 kB, installed size 12 kB
[07:20] <ducasse> hi all
[10:42] <BluesKaj> Hiyas all
[10:54] <daftykins> \o
[10:54] <daftykins> hrmm tried an up to date install of kodibuntu on my ancient atom+ion1 machine, sticking with nvidia-304 as the driver - but i'm getting broken VDPAU
[10:55] <BluesKaj> hey daftykins
[10:55] <daftykins> NOTICE: VDPAU::Open: required extension GL_NV_vdpau_interop not found <-- from Kodi's log
[10:57] <BluesKaj> I find kodi runs perfectly fine just as an app rather than an OS on my machines ...leaves a lot more options
[11:00] <daftykins> well, this is their outdated ISO so once you dist-upgrade it seems some things break
[11:07] <BluesKaj> jarvis ?
[11:13] <daftykins> yep
[11:13] <daftykins> kodibuntu is a trusty base
[11:32] <BluesKaj> k , that might be a bit old
[11:35] <daftykins> nah nothing wrong with it
[13:08] <daftykins> ah nevermind, i gave up and now have LibreELEC on there :D much better :D
[13:08] <daftykins> a wild TJ- ! hey there, how are you?
[13:09] <TJ-> Heya Mr D, how you doing?
[13:09] <daftykins> i'm very well thanks :D
[13:09] <daftykins> i think you'd be proud too, because i now have soldering capable hands!
[13:09] <TJ-> I'm great too; back to the online world (mostly) over winter after a busy summer
[13:10] <daftykins> ah yep :) is the dream house all complete now then?
[13:10] <TJ-> Woo-hoo!! party-time :) Did you invest in a multimeter too?
[13:10] <TJ-> No, there's still a lot of work to do but it is weather tight
[13:11] <TJ-> The larger problem is it is very isolated so getting materials to it is difficult when its wet and muddy
[13:11] <daftykins> ah i see, nah no multimeter just yet ;)
[13:11] <TJ-> I've hit a problem with basic lxc unprivileged containers that I can't fathom; very frustrating!
[13:12] <daftykins> ah har
[13:12] <BluesKaj> Hi pauljw, TJ-
[13:12] <daftykins> i was just beating my head against a brick wall of broken VDPAU on 14.04, but i've ditched that setup now
[13:12] <TJ-> BluesKaj ought to know how to solve my lxc issue by now :p
[13:13] <daftykins> :D
[13:13] <BluesKaj> TJ-,  lxc? my memory fails
[13:13] <daftykins> TJ-: would a dropbox link still be as useful as a chocolate teapot, to show you what i'd repaired last? :D
[13:14]  * BluesKaj has no clue about containers unless it's the coffee cans I save for screws etc
[13:14] <TJ-> LOL
[13:15] <TJ-> Why is it when *i* come in search of help everyone hides?
[13:15] <daftykins> that's my usual experience too ;)
[13:15] <daftykins> well, unless you're about!
[13:15] <BluesKaj>  not hiding TJ- , I'm just clueless :-)
[13:15] <TJ-> Grrrrr
[13:16] <TJ-> the lxcontainers channel is totally quiet so looks like i'm gonna spend several frustrating hours trying to figure it out, only to find that the instructions probably are missing some vital step
[13:24] <pauljw> hey BluesKaj , everyone
[13:37] <R13ose> Hi
[13:40] <R13ose> Oh, the problem has reappeared maybe because I restarted and didn't make the text added to grub permanent.  Should I do that and if so how? What text is this again?
[13:49] <daftykins> i didn't think it was solved to begin with
[13:50] <daftykins> "acpi_osi=Windows 2013" wasn't it? i forget
[13:50] <daftykins> or 2012 maybe
[13:55] <R13ose> It was "acpi_osi=Windows 2012"
[14:05] <TJ-> often good to clear out the existing OSI list first, using "acpi_osi=! "acpi_osi=Windows 2013" " - the ! clears the list
[14:06] <TJ-> ^^^ that's an example from this PC
[14:30] <daftykins> !info gnome-session-fallback
[14:30] <ubot5`> Package gnome-session-fallback does not exist in xenial
[15:04] <R13ose> daftykins: back.  How do I do that?  Go into grub again and put that in?
[15:09] <daftykins> you need to edit /etc/default/grub to enter it into one field yeah, i can't tell you which it is though
[15:11] <TJ-> GRUB_CMDLINE_LINUX="..."
[15:24] <R13ose> one sec  looking
[15:27] <R13ose> this is what I have now: http://pastebin.com/6rLSze0u the first line was there already and the second line was GRUB_CMDLINE_LINUX="" in which I added the text TJ- said above.
[15:27] <R13ose> If that is correct, I will save the file and then should I restart?
[15:27] <TJ-> R13ose: ok, you'll need to *escape* the embedded double quote marks so DO NOT reboot yet
[15:28] <R13ose> Do I need to run update-grub after I save the file?
[15:28] <R13ose> TJ-: can you explain what you mean?
[15:28] <TJ-> so for each embeded " you have to write \" ... here's mine as an example
[15:28] <TJ-> GRUB_CMDLINE_LINUX="no_console_suspend acpi_osi=! acpi_osi=\"Windows 2013\""
[15:29] <R13ose> okay
[15:29] <R13ose> do I need the first part of your line no_console_suspend?
[15:29] <TJ-> R13ose: otherwise the first " matches the second one rather than the second one being included inside the string
[15:30] <TJ-> R13ose: no, just the acpi_osi lines your system needs
[15:30] <TJ-> R13ose: if i recall correctly, earlier, you mention yours was "Windows_2012" not 2013 ?
[15:31] <R13ose> right 2012.
[15:32] <R13ose> Here is the line: GRUB_CMDLINE_LINUX="acpi_osi=! "acpi_osi=\"Windows 2012\"" but I see 5 double quotes and I believe I need even numbers right?
[15:33] <TJ-> R13ose: correct. lose the second "
[15:34] <R13ose> TJ-: Done.  Now I should use that command I talked about earlier and then restart?
[15:36] <TJ-> R13ose: "sudo update-grub" will take those options and write them to the /boot/grub/grub.cfg
[15:38] <R13ose> TJ-: right and now I can restart?
[15:38] <TJ-> R13ose: yes
[15:41] <daftykins> TJ-: as it happens that guys actual issue is one you might enjoy :> it's some annoying acer laptop if i remember rightly, intel graphics only, but some boots it'd come up with the 'modeset' driver and other times the 'intel' :)
[15:42] <daftykins> user first came in complaining of UI issues in browsers, such as updating the full screen when opening tabs etc, i think
[15:42] <TJ-> could it corollate to boots vs suspend cycles? many machines configure ACPI stuff less strictly on resume from sleep than they do at cold boot time
[15:43] <daftykins> mmm not sure
[15:44] <daftykins> i very quickly learnt that 16.10 handles Xorg's log location differently - and at that point i used a few expletives regarding FOSS always changing things for no good reason and walked away
[15:44] <daftykins> (wasn't my ticket)
[15:45] <TJ-> Huh? 16.10 has moved logs again?
[15:45] <R13ose> I am back, and will have to wait until the problem comes up again if this does.  There was a warning when I did the update that maybe I should fix, right?
[15:45] <TJ-> where to now?
[15:46] <daftykins> well it seems like it creates a different Xorg log per PID, so when you boot up it's a different X instance than once you log in
[15:46] <daftykins> i don't know very clearly as i don't run desktop or non-LTS :)
[15:46] <daftykins> R13ose: TJ's our resident deity on issues if you could describe the main problem from scratch :)
[15:47] <daftykins> iirc it was browser UI update quirks when opening tabs
[15:47] <TJ-> oh, that's been pretty standard for a few releases now. It's to do with separating the login X server from the user server. I forget what scenarios it kicks in from though
[15:47] <R13ose> daftykins: if the problem comes up again, I will let the channel know again.
[15:47] <daftykins> oh, i figured you'd recall
[15:48] <R13ose> daftykins: I know the problem exactly, but don't want to flood the channel with a problem that is not happening now.
[15:48] <R13ose> I am already testing TJ- approach and will see if this works.
[15:49] <daftykins> R13ose: write it in a paste and then link it...
[15:49] <R13ose> daftykins: my problem?
[15:49] <daftykins> it's not a new approach though, you were meant to have been using this since the first time we discussed it
[15:49] <daftykins> yeah
[15:50] <R13ose> daftykins: yes but I most likely restarted and didn't edit grub again as this was written into grub for good.
[15:52] <daftykins> yeah, you were meant to keep it handy to use every time and see if it had fixed it
[15:52] <daftykins> so essentially this entire process is still at the 'undetermined' stage
[15:53] <TJ-> what is the actual fault? missing hardware?
[15:53] <TJ-> I seem to recall with this PC it would have missing hardware if the mains power was not attached at boot
[15:56] <daftykins> i'm only going to be guessing from memory unless R13ose describes it again, so i'm gonna give up i'm afraid
[15:56] <R13ose> I am writing
[15:56] <R13ose> daftykins: the command, I forgot to do that each time sorry.
[15:56] <daftykins> eh no skin off my nose, my machines work :D
[15:57] <R13ose> Here is the pastebin that I setup to expire in 1 month: http://pastebin.com/9Up28Z60
[15:58] <daftykins> yeah so that's what led to trying to read the xorg log, then found out some boots would be using modeset, others would be using intel (or so it seemed)
[15:58] <daftykins> so Bashing-om went down the acpi_osi route
[16:00] <R13ose> yep
[16:00] <R13ose> I have to go in a few mins as family is over now.
[16:06] <R13ose> bbl
[16:07] <daftykins> \o
[17:46] <TJ-> Finally figured out my LXC issue! I'm using upstream kernels and it seems Ubuntu kernels carry CGROUP (control group) patches to allow relative bind mounts of the kernel file-system, and they haven't been sent upstream!
[17:47] <TJ-> fix is to edit the container's config file and add "lxc.aa_allow_incomplete = 1"
[17:48] <daftykins> :D
[17:51] <TJ-> wasted an afternoon on that, grrr
[21:21] <EriC^^> hey Bashing-om
[21:21] <EriC^^> how did the new bios chip go?
[21:24] <Bashing-om> EriC^^: From bad to worse in some respects ... gonna keep the latest version .. and try a new plan . ending up re-partitioning and re-installing a full desktop xubuntu . This has turned into a real learning experience :)
[21:25] <EriC^^> sounds good man