[07:56] <KOLANICH> Hi everyone. Where can I change dkms flags? IDK why but it seems someone has combined incompatible flags (-mindirect-branch and -fcf-protection) breaking build of essential modules like bcmwl.
[07:56] <KOLANICH> 1. I have accidentially nuked /usr/lib/x86_64-linux-gnu. 2. I have decided that if I have to reinstall all the packages I should update to eoan simultaneously. 3. I have managed get apt working (I had an iso) so I have reinstalled the most of packages. But some essential ones are broken, like systemd, systemd-networkd. So now I have no network on pc and am writing from a phone. 
[07:57] <lotuspsychje> KOLANICH: the broadcom drivers are offline on the .iso too in /lib/pool soemwhere
[07:57] <lotuspsychje> KOLANICH: maybe you can re fix from there?
[07:58] <KOLANICH> lotuspsychje: on the iso the drivers are for another kernel, the iso is for cosmic
[07:59] <KOLANICH> lotuspsychje: though thenew kernel is not yet loaded
[07:59] <KOLANICH> the network is already broken
[07:59] <lotuspsychje> you didnt use daily 19.10 iso?
[07:59] <KOLANICH> lotuspsychje: no, it was the release iso
[08:00] <lotuspsychje> release iso?
[08:01] <KOLANICH> lotuspsychje: I have upgraded the system from cosmic to eoan. but when cosmic was released I had downloaded the iso and stored it on hdd fkr emergency cases
[08:03] <lotuspsychje> KOLANICH: for devel releases we reccomend to use daily instead of upgrades, until final release
[08:03] <lotuspsychje> brb lunch first
[08:03] <KOLANICH> so when I have nuked /usr/lib/x86_64 I have just mounted that iso and copied the deleted dir. that was enough to make apt work. after that I have edited sources.list and started the upgrade
[08:05] <KOLANICH> lotuspsychje: so I wonder if I can manually remove one of the flags breaking the dkms build
[08:08] <immu> hi
[08:08] <immu> i am running 19.10 beta
[08:10] <immu> i was playing bubble game yeah and after something happened and it went full screen and whole screen frozee...
[08:11] <immu> i can hear the music but can't get out of it, switched terminal logged out and logged in again but nope had to reboot
[09:01] <KOLANICH> figured out. the flags hardcoded into gcc and usednimplicitly are incompatible to the ones used for building
[11:53] <tomreyn> beta release https://lists.ubuntu.com/archives/ubuntu-release/2019-September/004828.html
[12:12] <lotuspsychje> !info linux-image-generic
[12:12] <lotuspsychje> lovely
[12:15] <tomreyn> also in 18.04 via linux-image-generic-hwe-18.04-edge/bionic-proposed
[12:15] <lotuspsychje> ah tnx tomreyn 
[12:15] <lotuspsychje> tomreyn: next clevo, i might test that edge one
[12:16] <lotuspsychje> 19.10 daily on 5.2 didnt have that flicker bug neither
[12:16] <tomreyn> good. :)
[13:37] <KOLANICH> Hi
[13:37] <KOLANICH> Can anyone help me?
[13:38] <KOLANICH> deb packages don't install the file to /etc/OpenCl/vendors/
[13:38] <KOLANICH> The file is present and dpkg even probes that dir
[13:38] <KOLANICH> but it is not written ther
[13:38] <KOLANICH> ther
[13:38] <KOLANICH> *there
[13:52] <immu> 5.3.0-12-generic was pushed out?
[13:54] <lotuspsychje> !info linux-image-generic
[13:58] <immu> system now seems to be stable before it use to free with nvida gpu
[14:00] <immu> lotuspsychje, hiu
[14:04] <immu> got hold of the change log
[14:04] <immu> thnx
[14:41] <immu> why isn't the new theme active? 
[16:15] <immu> hi....
[16:17] <oer> h!....
[16:31] <immu> its quiet in here
[16:33] <immu> has anybody installed steam on 19.10 i am getting glx extension not supported error
[16:37] <Faux> Didn't work for me until I installed libnvidia-gl-435:i386, but is now fine.
[16:37] <Faux> Mine was segfaulting trying to tell me about the glx error, though, which wasn't super helpful.
[16:38] <immu> its related to 32bit support in UBuntu 19.10
[16:38] <immu> OpenGl GLX extension not supported by Display
[16:40] <immu> brb
[16:53] <immu> any one having issues with steam? 
[16:59] <Faux> Not since the fix I recommended.
[17:00] <immu> how do i install that libary
[17:00] <Faux> sudo apt install libnvidia-gl-435:i386
[17:05] <immu> but i am on driver 390
[17:06] <immu> wont it hose my system?
[17:07] <immu> well Faux ?
[17:08] <Faux> No idea. A clean install gives you that driver, so you must be on some kind of exciting hybrid, which I can't possibly know anything about. Good luck.
[17:09] <immu> i have both intel and nvidia
[17:10] <tomreyn> that doesn't explain why you'd have nvidia 390 on eoan
[17:10] <immu> you know that hybrid config? kind of ting
[17:10] <Faux> It is available, at least.
[17:11] <immu> its always available to me , i got alienware14
[17:11] <tomreyn> oh it's in eoan, sorry, my fault there
[17:12] <immu> it will either use the intel driver or the nvidia if i enable it
[17:12] <immu> brb rebooting and prayinbg
[17:12] <Faux> immu: Well, try installing theversion for your driver. Or, if you want to know who's the problem, try a cleaner installer.
[17:18] <tomreyn> hmm it appears that the installer attempts to access the dvd after the prompt to eject the disc
[17:19] <tomreyn> ...resulting in "SQUASHFS error: Unable to read data" console spam
[17:48] <tomreyn> hmm the installer still prompts for primary / logical partition with a gpt partition table.
[18:15] <karlthane> Ok just downloaded the beta, still not offering zfs in ubiquity. What am I doing wrong?
[18:17] <lordcirth> karlthane, https://github.com/orgs/ubuntu/projects/1#card-22118218
[18:18] <lordcirth> Ubiquity supports it if experimental features are enabled, but isolinux does not yet have the option to turn them on.
[18:21] <karlthane> So no way to test, or if I do an update/full-upgrade will that give me the version of ubiquity needed?
[18:22] <lordcirth> ubiquity is an installer, how would full-upgrading an installation help?
[18:23] <karlthane> Full-upgrading from the live enviroment before starting the installer.
[18:24] <lordcirth> Ah. No, the work hasn't been done yet, that's why it's not checked off.
[18:26] <karlthane> Ah, ok.
[18:45] <tomreyn> karlthane: https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity/+merge/373087
[18:46] <tomreyn> and bug 1843768
[18:46] <tomreyn> FFe -> feature freeze exemption, i think, so this should still make it into the october release.
[19:10] <wonko> trying to upgrade from 19.04 to 19.10 and it got stuck. Killed it and trying to get it going again it looks like this is what got it stuck maybe:
[19:10] <wonko> wonko@deepthought:~/.config $ sudo dpkg --configure -a
[19:10] <wonko> Setting up grub-pc (2.04-1ubuntu6) ...
[19:27] <tomreyn> wonko: you'll need to post the full output on a pastebin if you're hoping to get someone to help out (but even then, still a beta)
[19:28] <tomreyn> 2 beta bugs reported so far, who got more?
[19:33] <tomreyn> can anyone confirm bug 1845703 ?
[20:36] <wonko> tomreyn: which output/logs would he most useful?
[20:45] <tomreyn> wonko: "sudo dpkg --configure -a" if there is more output. or run it with any verbose or debug options. and check journalctl -f   as well
[20:50] <trilead> Hi, was in the wrong channel before. Is there a syslinux switch to enable ZFS root support on the 19.10 beta live image?
[20:51] <tomreyn> not yet, trilead, but see bug 1843768 and the linked merge request there
[21:03] <trilead> Thanks, from reading the bug and looking at the commits I gather this didn't make it into the current image.
[21:04] <wonko> tomyren: the output I pasted above is the only output I get. I don't see a verbose flag for dpkg unless I'm missing something. I'll check jounalctl when I get home it seems sshd is currently down.
[21:27] <tomreyn> does this get past the directory check for anyone?  nautilus --check
[21:28] <tomreyn> ah, same issue on 18.04, so it'll be generic.
[21:28] <archetech> 19.10  nope
[21:29] <tomreyn> thanks for trying
[21:29] <archetech> w
[21:39] <tomreyn> archetech: if you have a launchpad account, please consider flagging 'affects me' (no need to comment) on bug 1845732 - thanks!
[21:39] <hggdh> tomreyn: you mean it hangs?
[21:40] <tomreyn> hggdh: yes
[21:40] <hggdh> tomreyn: metoo-ed it
[21:40] <tomreyn> thank you
[22:39] <tomreyn> wohoo, my first 'bluescreen'
[22:41] <tomreyn> apparently a newer gnome feature? https://static.spiceworks.com/shared/post/0014/5857/Screen%20Shot%202016-01-26%20at%207.14.04%20AM.png
[22:44] <hggdh> tomreyn: this is actually a black-and-white screen of death...
[22:45] <tomreyn> thus the ticks around bluescreen ;)
[23:21] <wonko> So I don't know if it's related or not but zfs is in a weird state as I'm trying to reboot. I'll test some upgrades with and without zfs in VMs after I get stable again to see if there is a correlation.
[23:22] <wonko> The upgrade did throw an error about trying to update the zfsutils package so there is a good chance that's it. Maybe. 😁
[23:24] <Bashing-om> wonko: Any hints here: https://discourse.ubuntu.com/t/enhancing-our-zfs-support-on-ubuntu-19-10-an-introduction/12130/37 ?
[23:28] <wonko> Ah, I'm not doing zfs root. Just have a non-root pool
[23:29] <wonko> Hmm, kernel panic. Unable to mount root. Bah.
[23:30] <wonko> But considering grub-rc had issues maybe I'm not surprised.