=== Phothrism is now known as Optiprism [00:58] hi all. can somebody please point me in the right direction for nic bonding in 16.04. i read that it's using systemd networking now, but i'm referring to my old work docs and not clear on how much of the process is different [02:18] Good evening +1. I was wondering if booting from zfs is supported in 16.04, or just using zfs after boot? I can't seem to find an answer on the googles. === littlebunnyfufu is now known as SonikkuAmerica === Guest0 is now known as thisguy [03:53] wjlafrance: There are guides for doing it. You can boot ZFS root. It won't do it with either installer though. [03:54] It gets tricky if you include LUKS, but still possible. [03:55] I found one of the guides on Github and it was exciting to say the least. I had a difficult time getting grub to find my zfs root, and then I could boot but couldn't install grub onto the actual drive (it was on my old system disk still) [03:55] Something about the disk not having an MBR [03:57] wjlafrance: My favourite guide so far: https://github.com/rlaager/zfs/wiki/HOWTO-Install-Ubuntu-to-a-Native-ZFS-Root-Filesystem [03:58] wjlafrance: My own notes, which are scattershot as the last I worked on them I was starting to integrate UEFI stuff: https://bpaste.net/show/665551712361 [03:59] ChibaPet: Much appreciated, I'll give it another shot [04:00] I cheat and use an EXT4 boot. I'd love a pure ZFS solution, but I don't think it'll be possible outside of initramfs-and-UEFI, and that will require a slight deviation from how Ubuntu likes to do thigns. [04:00] things [04:01] So for the moment my default install is EXT root, and just ZFS for /home and /usr/src and similar. [04:03] !info wine [04:03] wine (source: wine1.6): Microsoft Windows Compatibility Layer (meta-package). In component universe, is extra. Version 1:1.6.2-0ubuntu13 (xenial), package size 0 kB, installed size 6 kB (Only available for i386; amd64) [04:03] I thought I'd seen something about 1.8 in Xenial itself, but I guess not. [06:18] !find 364.12 [06:18] Package/file 364.12 does not exist in xenial === Logan is now known as Guest92038 [09:12] Good morning. [09:51] hey, this bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1560356 makes all test to be marked as failed for beta images [09:51] Launchpad bug 1560356 in ubiquity (Ubuntu) "ubiquity will not start on Xenial liveUSB" [Undecided,Confirmed] [09:52] shall we wait for a fix before further testing ? [09:54] soee_: if this is your situation, you can test things yourself too [09:58] hi - seeing as Nvidia released a new driver http://www.nvidia.com/download/driverResults.aspx/100577/en-us - will this make it into 16.04 ? [09:58] yossarianuk: 16.04 will have good driver support, so we hear [09:58] I really hope so as it brings Vulkan support as well as Wayland/Mir support [09:59] yossarianuk: newer driver versions will make it to all ubuntu versions not only xenial [09:59] yossarianuk: so little patience till this driver hits the repos :p [10:00] Cool- I was fearing in 5-6+ months when a raft of Vulkan games comes out trying to explain to people that the driver in 16.04 can run them... So glad to hear it. [10:00] Will it just be in the PPA or in default repos ? [10:01] yossarianuk: follow phoronix website for latest news, or #gamingonlinux also know the latest changes [10:01] iok cheers [10:01] yossarianuk: we dont support external ppa's on ubuntu, so recommended to try ubuntu default drivers first [10:02] stop the press.. minecraft segfaults on start [10:02] snadge: fresh install or upgrade? [10:03] fresh install [10:03] snadge: got the right graphics drivers active? [10:03] hmm.. looks like im using openjre 9 [10:03] woops [10:03] i installed 8.. but need to select default [10:05] ok.. now im getting a different error ;) [10:07] snadge: make sure you test all options before you file a bug ok :p [10:09] lotuspsychje: actually just realised the driver is beta at the min... [10:10] yossarianuk: with a little patience, everything will come in place for sure :p [10:10] lotuspsychje: my point however is that unless Ubuntu does end up supporting the Nvidia driver with Mir/Vulkan support its not exactly going to be useful from 2017+ (and its meant to last for up to 5 years) [10:11] I mean the nvidia support being useful (not the rest of teh distro) [10:11] but thanks, and its really good progress to see Nvidia support. [10:12] err wow.. okay i just got it to work.. and 60fps in minecraft on the open source drivers!?!? thats amazing [10:12] thats with vsync enabled too [10:12] !yay | snadge [10:12] snadge: Glad you made it! :-) [10:13] http://news.softpedia.com/news/ubuntu-16-04-lts-xenial-xerus-final-beta-now-in-feature-freeze-lands-march-24-502020.shtml [10:13] only reason im trying xenial is because i have amd graphics.. and traditionally speaking, the open source driver sucked.. so there's hope yet ;) [10:14] also of random note.. the minecraft seed "Ubuntu 16.04" starts out in this cool jungle environment ;) [10:15] snadge, yossarianuk join #gamingonlinux also, those guys have latest news about graphics/gaming on linux [10:17] i dont think an lts is particularly relevant to gaming on linux.. most "gamers" are going to use an lts for 6 months, before upgrading to the next release ;) [10:18] unless all you want to play is supertux [10:18] snadge: what are you talking about, xenial benchmarking already great on phoronix news [10:18] yeah dont get me wrong.. i was just skeptical about dropping fglrx [10:18] xenial will rocknroll for gaming [10:18] which is more amd than anything else [10:19] on 15.10.. i use catalyst.. even with a mainline kernel and oibafs ppa.. it doesn't appear to be as good as xenial [10:19] so its exciting to see mesa, radeon, kernel updates etc [10:20] yep [10:21] I hope nvidia take note of the AMD open driver.... [10:22] i think the sad fact of the matter is that amd needed to do this.. nvidia's proprietary driver isn't in as bad shape [10:23] but i agree.. perhaps they can utilise a similar model.. ie.. the drm and framebuffer parts open.. and proprietary opengl / shaders etc [10:23] ie, a hybrid model [10:23] even with the new improvments if you want to get good performance (i.e on par with Windows or better) you need nvidia at the minute [10:23] but amd's improvements are promosing . [10:23] *promising* [10:35] snadge: I wouldn't assume gamers upgrade to non LTS's - I know of lost of developers who run Ubuntu and stil to the LTS but still dualboot Windows because they say graphics drivers are slow [10:35] However if they had just updated their Nvidia driver it would have boosted their fps on certain steam, etc games./ [10:36] i cant stand lts.. i like ubuntu too much.. i consider them to be more for a) lazy people b) people who don't care and c) boring business type people ;) [10:36] snadge: personally I just use them for server based things [10:36] you can upgrade the nvidia driver after the fact.. you dont have to use the one that comes with it [10:36] however others don;t [10:37] snadge: but it can be hard to (unless you use the PPA) [10:37] i haven't had nvidia in years.. but there you go, you said it yourself.. just use the ppa [10:37] I know ubuntu isn't rolling release, but certain packages should be for a desktop [10:37] i.e nvidia/amd drivers... [10:38] thats fine for me (I actually use the .RUN file from nvidia.com) but newbies wouldn't even know about them. [12:48] !info unison xenial [12:48] unison (source: unison): file-synchronization tool for Unix and Windows. In component universe, is optional. Version 2.48.3-1ubuntu1 (xenial), package size 648 kB, installed size 2018 kB [12:48] omfe: this is the version recommended for 16.04 [12:49] what is the issue with the "too new" version? [12:49] Hello! How can I install unison-2.40.x inside lubuntu-16.04 beta1? There is only unison-2.48.x available. Which source can I use? [12:50] omfe: please dont mix package versions, if you need 2.40.x you can try installing 14.04 or 15.10 [12:54] I need syncronisation between pc1 (16.04) and pc2 (14.04 with unison 2.40). [12:57] omfe: https://help.ubuntu.com/community/Unison [12:59] omfe: if you find 2 different unison versions wont sync, you could contact: https://launchpad.net/unison or make a new bug? [13:00] omfe: what is the error when you use the regular unison? [13:01] i am not aware of unison beeing not compatible with older version [13:02] "Received unexpected header from the server: expected "Unison 2.48\n" but received "Unison 2.40\n\000\000\000\000\017", which differs at "Unison 2.40". ... [13:04] Is it not possible or not a good idea to install unison-2.40 inside lubuntu-16.04? Why not? [13:04] The versions of unison running on the server and the client must match. (Specifically, the first two components of the version number must match exactly: versions 2.24.6 and 2.24.10 will happily talk to each other, but 2.17.3 and 2.24.10 will not). If all you need is the textual user interface, compiling binaries for most distributions is straighforward. [13:04] grabbed from: https://alliance.seas.upenn.edu/~bcpierce/wiki/?n=Main.UnisonFAQTroubleshooting [13:05] omfe: no, dont mix up package versions mate [13:05] lotuspsychje: that is good to know [13:06] oh damn. [13:06] omfe: its recommended to use package versions, meant for your ubuntu version [13:07] needs to file bugs to unison to get all old installs updated :/ [13:07] omfe: can you make it 2 similar boxes? [13:09] ok, there seems to be no solution except copying unisons binary around [13:09] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807019 [13:09] Debian bug 807019 in unison2.40.102 "unison2.40.102: Segmentation fault" [Grave,Fixed] [13:09] lotuspsychje: o.k., i will do so and use unison-2.48.x on my system! But how can I synchronize against the other pc using unison-2.40.x? [13:10] omfe: cant you setup another 14.04 box with 2.40.x to sync? [13:10] omfe: or make both boxes 16.04? [13:11] Howdy all [13:12] hey TJ- [13:13] lotuspsychje: switching all machines to 16.04 will come in the next future. But i need synchronisation during this time. [13:13] omfe: copy the binary from one system to the next one [13:13] omfe: well there is a pinning method, but not sure this really recommended [13:14] omfe: perhaps go for k1l_ solution rather [13:14] that is what the debian maintainers say: we dont have a solution so far, copy the binary [13:16] k1l_: I will test this really simple solution and report! Thanks a lot! [13:38] lotuspsychje & k1l_: I performed the copy and set 2 links and then: all was fine! I can synchronize and be happy! ;-) Thanks a lot for this solution! [13:38] !cookie | k1l_ [13:38] k1l_: Wow! You're such a great helper, you deserve a cookie! [14:07] hi genii [14:19] * genii waves to lotuspsychje [16:22] how do I reset the unity desktop, its missing the panels again. [16:24] even in guest-account? [16:24] if so its a driver issue. if guest account is fine rename the .config folder [16:24] (i dont recall what exact setting in .config it was) [16:26] I forgot to check guest account again, usually that one is fine [16:26] the entire .config folder? [16:29] mv .config .config_backup [16:29] like i said, i dont know what exact stuff in there was a common issue [16:30] I think we narrowed it down to the monitor.xml [16:30] or monitors.xml; can't recall the filename fully now [16:31] i think there was some qt stuff too [16:45] salamanderrake: did you fresh install or upgrade? [18:19] Does anyone else have an issue with the unified menus not showing up properly in some apps on the first time logging in from a boot? Terminal and Nautilus both won't show menus (Thunderbird and Chrome will though) unless I log out and back in. [18:51] ZenHarbinger for some apps, there's no menu in the title bar, that is correct... i guess it will be solved when 16.04 is released [19:27] Hi all. I am trying to make the vfio-pci kernel module claim my Radeon R9 290 gpu before the radeon kernel driver/module claims it. [19:28] OK, I just wanted to make sure it wasn't just me. I can work around it, but I hope it goes away. :) [19:28] I've added "options vfio-pci ids=1002:67b1,1002:aac8" to /etc/modprobe.d/vfio.conf, and in /etc/modules I've added vfio-pci on a new line. [19:29] But when I boot and do "lspci -nnk" it reports that "kernel driver in use: radeon" for my Radeon gpu ... [19:30] Even blacklisting the radeon module 'echo "blacklist radeon" > /etc/modprobe.d/blacklist.conf' does not change the output of "lspci -nnk", it still shows the radeon module as being used for the radeon gpu. [19:31] lsmod also still list the radeon module being used by 1, and the vfio-pci module loaded, but used by 0. Any ideas? === nhandler_ is now known as nhandler === vladimir-sn is now known as not_jbatdk === not_jbatdk is now known as vladimir-sn === Warrigal is now known as tswett [22:12] lordievader: I did an upgrade and it broke, now its fixed [22:12] again [23:12] salamanderrake: Sorry, what broke? [23:22] lordievader: unity [23:22] * lordievader is confused