[01:11] <Azure_Chaos> Hello would it be safe to install the 18.04 daily how stable is it? Also would i have to reinstal at release time? I currently use debian testing but i want to move back to ubuntu.
[02:32] <FurretUber> Grub2 has a strange graphical error after I upgraded to 18.04: https://youtu.be/wKUBOAx73k4
[02:32] <FurretUber> I am not able to reproduce this on virtual machines
[10:23] <alkisg> touch "/tmp/hi there"; ls -ld "/tmp/hi there"
[10:23] <alkisg> -rw-r--r-- 1 administrator administrator 0 \u03a6\u03b5\u03b2  20 12:21 '/tmp/hi there'
[10:23] <alkisg> ...is this a new feature in ls? Quoting the output?! 
[10:24] <alkisg> And it also includes a space in front of lines, e.g.: ls /tmp
[10:24] <alkisg>  file1 'hi there'
[10:24] <alkisg> A space before file1 there
[10:24] <alkisg> Does anyone else have that issue in 18.04?
[10:26] <alkisg> Heh, "it's a feature", ls -Q double-quotes
[10:30] <alkisg> Hmm, I think "ls" now defaults to "--quoting-style=shell" instead of "literal". I wonder how many scripts will now break with this undocumented change...
[10:31] <alkisg> There's a new -N option to disable quoting...
[10:31] <alkisg> http://changelogs.ubuntu.com/changelogs/pool/main/c/coreutils/coreutils_8.28-1ubuntu1/changelog ==> 
[10:31] <alkisg>   * Reenable default ls quoting
[10:32] <alkisg> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813164
[10:32] <ubottu> Debian bug 813164 in coreutils "coreutils: ls suddenly quotes output" [Wishlist,Fixed]
[15:36] <donofrio> last issue (for now) that I have on my 18.04 install is I'm getting these locale messages once and awhile like this when I just sshed into a host while I'm working and it said "/usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct" so I'm wondering what do I nbee" so I'm wondering what do I need to do to resolve that?
[15:43] <alkisg> And what is the value for those variables?
[15:43] <alkisg> env | grep ^L
[16:00] <FurretUber> Hi, the package intel-gpu-tools no longer has intel-gpu-overlay available on bionic
[16:01] <FurretUber> The program intel-gpu-overlay is available on xenial, zesty and artful
[16:08] <nacc> FurretUber: i'd file a bug?
[16:09] <nacc> i'll ask timo
[16:09] <FurretUber> I'm doing it now
[16:09] <FurretUber> I noticed intel-gpu-tools source built successfully without the overlay
[16:09] <nacc> FurretUber: thanks!
[16:10] <nacc> FurretUber: yeah, it seems like a removed functionality, possibly upstream?
[16:10] <FurretUber> Because it is a warning and not a error
[16:10] <FurretUber> But I could build the overlay after I investigated the warning. It's funny, as it shows the Intel HD Graphics 520 is using 40 GW of power
[16:12] <FurretUber> Done: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1750605
[16:12] <ubottu> Launchpad bug 1750605 in intel-gpu-tools (Ubuntu) "intel-gpu-tools no longer has intel-gpu-overlay application" [Undecided,New]
[16:17] <BLZbubba> hi guys, i just installed a bionic desktop, and systemd-resolvd is ignoring the DNS server IP -- though it keeps the search paths
[16:18] <BLZbubba> what should i do to debug this?  i did notice that the resolv.conf had (iirc) 127.1.0.1 as the ip, but systemd-resolvd is listening on 127.0.0.53:53
[16:20] <BLZbubba> ok i lied, it was 127.0.1.1
[16:24] <nacc> BLZbubba: where does /etc/resolv.conf point to (it's a sy mlink)
[16:24] <nacc> BLZbubba: if it is using 127.0.1.1, then your system is not using systemd-resolved currently
[16:25] <BLZbubba> not a symlink, it says the file was created by NetworkManager
[16:25] <nacc> oh hrm
[16:25] <nacc> i'm not sure then
[16:25] <nacc> on my bionic desktop it is a symlink (upgrade over the past several releases, not a fresh install)
[17:11] <nacc> FurretUber: thanks for your report, timo has pushed a new version (updated build-depends) to debian, which should come into bionic eventually
[18:14] <Jayflux> hi all, is it possible to install postgresql non-interactively (so without picking country and city?)
[18:14] <Jayflux> this is on ubuntu 18
[18:23] <lotuspsychje> phoenix_firebrd: welcome, how can we help you
[18:25] <phoenix_firebrd> lotuspsychje: I tested 18.04 daily image yesterday, I wanted to check for the condition of vaapi. It seems VAProfileVP9* was removed from intel vaapi driver. Is this a bug or a known action?
[18:26] <lotuspsychje> phoenix_firebrd: sorry dont know about vaapi myself
[18:26] <lotuspsychje> phoenix_firebrd: perhaps explain in this channel some more details of what you trying?
[18:26] <phoenix_firebrd> ya sure
[18:26] <lotuspsychje> !find vaapi
[18:27] <ubottu> Found: gstreamer1.0-vaapi, gstreamer1.0-vaapi-doc, W:, W:, W:, W:, W:, W:, W:, W: (and 214 others) http://packages.ubuntu.com/search?keywords=vaapi&searchon=names&suite=bionic&section=all
[18:28] <lotuspsychje> phoenix_firebrd: also perhaps compare the xorg vs wayland session?
[18:30] <phoenix_firebrd> My problem is, I want hardware accelerated video decoding for VP9 codec video files using intel onboard GPU, My processor is i5 7400 which has the intel HD 630 graphics. It is capable of native decoding/encoding of VP9 codec. The is a bug is in the intel vaapi driver version 1.8.. .........
[18:31] <lotuspsychje> phoenix_firebrd: did this work on other ubuntu versions for you?
[18:32] <lotuspsychje> !info intel-vaapi-driver
[18:32] <ubottu> Package intel-vaapi-driver does not exist in bionic
[18:36] <phoenix_firebrd> which causes image corruption in certain frames. I patched by driver by cherry picking a patch from the official developer git page. Now the media players work fine. The issue now is, since the release of vlc 3.0 the snap version is compiled for the intel vaapi driver with the bug and so when a vp9 codec video file is played, it is played with corrupt image in certain frames. So I was forced to use a vlc daily ppa(unstable version). So I wanted 
[18:36] <phoenix_firebrd> to check if this problem is sorted out with the libva1(va-api2) in 18.04, as I know since the patch was merged before the 2.0 tagging, bug was fixed and I can confirm that....... 
[18:37] <phoenix_firebrd> but to my surprise the VAProfileVP9Profile* was gone and VP9 hardware decode/encode support was gone all together.
[18:38] <phoenix_firebrd> lotuspsychje: Its a feature in vaapi driver that is missing, It is seperate from wayland.
[18:39] <phoenix_firebrd> lotuspsychje: the package name is i965-va-driver
[18:41] <lotuspsychje> !info i965-va-driver
[18:41] <ubottu> i965-va-driver (source: intel-vaapi-driver): VAAPI driver for Intel G45 & HD Graphics family. In component universe, is extra. Version 2.0.0+dfsg1-1 (bionic), package size 416 kB, installed size 2280 kB (Only available for any-amd64; any-i386)
[18:41] <lotuspsychje> phoenix_firebrd: you might wanna bug against that, see what the devs suggest to do
[18:42] <donofrio> say does anyone here use multiple monitors?
[18:43] <phoenix_firebrd> lotuspsychje: I think I saw a bug report in launchpad, let me check
[18:43] <lotuspsychje> phoenix_firebrd: if you find an existing,sure i didnt see it right away
[18:44] <phoenix_firebrd> https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1591714
[18:44] <ubottu> Launchpad bug 1591714 in intel-vaapi-driver (Ubuntu) "Why no VAProfileVP9Profile* in libva" [Undecided,Invalid]
[18:44] <donofrio> not wsl question dell 8200 question with 18.04
[18:44] <lotuspsychje> phoenix_firebrd: lemme check
[18:45] <lotuspsychje> phoenix_firebrd: this bug is invalid as #2 describes
[18:47] <lotuspsychje> phoenix_firebrd: but that bug is also created for 16.04
[18:47] <phoenix_firebrd> lotuspsychje: ya, but mine is a kabylake processor and as said it fully supports hardware decoding/encoding. So I have to file a new one?
[18:47] <lotuspsychje> phoenix_firebrd: i would reccomend yes
[18:47] <phoenix_firebrd> ok
[18:47] <lotuspsychje> phoenix_firebrd: and describe your whole story, ubuntu version, kernel etc
[18:47] <phoenix_firebrd> sure
[18:47] <lotuspsychje> might be helpfull for the community
[18:48] <phoenix_firebrd> Do you know what version of intel vaapi driver they use in ubuntu snap core package?
[18:48] <donofrio> When you have four monitors like I do on one card/chip radeon I cannot get all the monitors to touch sides in the "Display" applet, when they are anything other than rotation of normal....
[18:48] <lotuspsychje> phoenix_firebrd: not sure sorry
[18:49] <lotuspsychje> phoenix_firebrd: perhaps the #snappy guys might know
[18:49] <phoenix_firebrd> lotuspsychje: Thanks for the support, I will file a bug report with all the details and I will contact the snappy channel too
[18:50] <lotuspsychje> phoenix_firebrd: some tips to more easy solving:µ
[18:50] <lotuspsychje> try to find more users that can add to your bug
[18:51] <lotuspsychje> and try steps yourself to add to the bug=more activity=more chance of solving
[18:51] <phoenix_firebrd> sure :)
[20:23] <donofrio> so no-one here runs more than one display output on 18.04?
[20:24] <alkisg> I do
[20:24] <alkisg> In ubuntu mate 18.04
[20:28] <hggdh> two displays, standard Ubuntu
[20:31] <donofrio> ok can you get them to touch or just overlap
[20:31] <Odd_Bloke> I'm running two displays with 18.04 also.
[20:31] <Odd_Bloke> Mine do not overlap.
[20:31] <donofrio> I'll have to get a screen2gif for ubuntu so I can show you all what madness moving these displays around is
[20:32] <donofrio> I have a visiontec radion quad head that just "works by default" all screens live out of the gate
[20:32] <Odd_Bloke> (FWIW, I have one of my monitors in portrait mode.)
[20:32] <donofrio> and fine when in normal rotation but the have North / South  magnet like repulsion to each other...
[20:33] <donofrio> but only in "Left"/portrait mode
[20:33] <donofrio> find in landscape/normal mode
[20:33] <Odd_Bloke> donofrio: I wonder if the problem is that something doesn't think you can drive that much vertical resolution?
[20:35] <donofrio> yah I dunno....felt like http://unity.grogansoft.com/wp-content/uploads/2017/05/rabbit.gif only with four displays and I'm tryingto get two to snap together
[20:35] <Odd_Bloke> donofrio: Can you pastebin xrandr output?
[20:36]  * Odd_Bloke doesn't really know much about the desktop side of things, so is kinda stabbing in the dark here.
[20:39] <donofrio> I'll be able to do that in four hours, I'm at work and it's at home...
[20:39] <Odd_Bloke> Ah, fair enough.
[21:00] <FurretUber> The bridge connection created by virt-manager is acting strange on 18.04: the virtual machine can ping to the host and can ping to the internet, but can't ping to other hosts and can't access internet (updating packages, for example)
[21:01] <donofrio> FurretUber, are you Natting or Bridgeing?
[21:01] <FurretUber> NAT
[21:02] <donofrio> Try Bridge, Not had much luck with Natting and VM's (just a thought)
[21:02] <FurretUber> It's strange, as the same configuration worked on 16.04 and 17.10
[21:03] <donofrio> well then my guess is probably incorrect
[22:14] <tfgbd_> How do I turn off the accererometer?
[22:15] <tfgbd_> Everything seems to work but bluetooth and the touchscreen
[22:15] <tfgbd_> The accererometer works in the opposite way it is supposed to
[22:19] <tfgbd_> When I hold it in poitrait it rotates to landscape and vice versa
[22:40] <FurretUber> Definitively, the libvirt network configuration that is working in Xenial doesn't work in Bionic