[00:01] <CarlFK> FurretUber: my guess xserver-xorg-core  based on:  https://packages.ubuntu.com/focal/amd64/xserver-xorg-core/filelist /usr/lib/xorg/modules/drivers/modesetting_drv.so
[02:01] <lotuspsychje> good morning
[02:54] <Ben64> just installed 20.04 on my laptop
[03:45] <Smedles> hi all.... focal is running fine on a clean install, but if I mount my 18.04 /home partition; I get an 'Oh No! Something has gone wrong/' error immediately after logging in
[03:46] <Smedles> any suggestions on working out what it doesn't like?
[03:55] <Bashing-om> Smedles: How and where is the 18.04 /home partition mounted ?
[04:05] <Smedles> Bashing-om: I selected the partition during install, and mounted it as /home - I'll assume it added an entry in fstab
[04:05] <Smedles> (my current focal install is *not* using the 18.04 /home partition - as I wanted to confirm that was the source of the issue)
[04:06] <Bashing-om> Smedles: we then need to look at it = pastenin ' cat /etc/fstab ; sudo blkid -c /dev/null ' .
[04:07] <Smedles> from a command prompt in focal?
[04:08] <Bashing-om> Smedles: Affirmed from focal terminal interface.
[04:08] <Smedles> ok - rebooting now
[04:28] <Smedles> Bashing-om: https://pastebin.com/cDtSyigm
[04:31] <Smedles> Bashing-om: the other point of note, is that focal was working with the 18.04 /home up until a few weeks ago. After some package updates it broke
[04:32] <Smedles> a fresh install with this partition as /home fails in the same way
[04:33] <lotuspsychje> nice Ben64 did you pick -desktop?
[04:37] <Bashing-om> Smedles: with the /home on another drive - out f my experience range - the hard drive not up when /nvme0n1p1 comes up ?
[04:41] <Smedles> Bashing-om: /dev/sda is also an ssd - so pretty unlikely (imho)
[04:43] <Smedles> nothing stood out in syslog
[04:43] <Smedles> (to me)
[05:02] <Ben64> lotuspsychje: yeah
[05:02] <Ben64> installed flashback, trying to set things up how I like
[05:02] <Ben64> theming is still wonky
[05:05] <Bashing-om> Smedles: where is focus' /home ? and what is on nvme0n1p5 nvme0n1p6 ?
[05:31] <jphilips> The #UbuntuTestingWeek has begun today, so all those interested to help improve the stability of Ubuntu 20.04 LTS, please read this - https://discourse.ubuntu.com/t/testing-ubuntu-20-04-lts-official-ubuntu-flavors/14053
[05:44] <Smedles> Bashing-om: nvme0n1p5  is ubuntu 18.04; nvme0n1p56 is the focal install
[05:45] <Smedles> the shared /home is on a separate ssd
[05:46] <Bashing-om> Smedles: Sorry out of time here . Must leave.
[05:46] <Smedles> no probs
[08:12] <lotuspsychje> Ben64: cool flashback, been a while since ive tested that
[10:47] <mind_sage> Hi everyone, will the new ubuntu 20.04 solve some of the previous issues it had? What will be new?
[10:47] <lotuspsychje> mind_sage: what kind of issues did you had?
[10:49] <mind_sage> mostly with drivers, but the file search didn't work either, as well as many basic features (in-built mic and cam, touchpad gestures)
[10:50] <pmjdebruijn> mind_sage: presumably you are referring to a specific laptop?
[10:50] <pmjdebruijn> mind_sage: what's the last version you tested 19.10? or 18.04 (without or without HWE)?
[10:51] <pmjdebruijn> btw, presumaing it's a laptop, having the camera not working is odd, you'd think it would be a UVC device?
[10:53] <mind_sage> yes, a laptop, sorry
[10:53] <mind_sage> lenovo legion gaming laptop
[10:53] <mind_sage> and I used 18.04 LTS 
[10:54] <mind_sage> (kubuntu though)
[10:58] <lotuspsychje> mind_sage: did you update your bios to latest?
[10:59] <mind_sage> yes
[11:00] <lotuspsychje> mind_sage: using 20.04 the LTS way also means waiting till 20.04.1 comes out, to upgrade from 18.04
[11:00] <lotuspsychje> mind_sage: this way many more bus will be solved and you will get a smoother LTS experience
[11:00] <lotuspsychje> *bugs
[11:01] <mind_sage> I really hope so
[11:01] <pmjdebruijn> mind_sage: keep in mind the "Gaming" laptop often tend to have more issues than regular ones, companies tend to do weird stuff in those
[11:01] <mind_sage> since now I'm back on windows
[11:01] <pmjdebruijn> (it's a bit an a generalisation, but often true)
[11:10] <pmjdebruijn> mind_sage: did you buy the laptop with the intent to run linux on it? or is that something that's just come up later?
[11:10] <mind_sage> came up later
[11:11] <pmjdebruijn> ok, then it makes more sense
[11:11] <pmjdebruijn> btw, you can easily test by start a 20.04 live desktop
[11:11] <pmjdebruijn> from a usb drive
[11:11] <pmjdebruijn> you don't need to install to test the cam/mic ad touchpad
[15:24] <howarth> After dist-upgrading from 19.10 to 20.04, I found that the ubuntu software manager package appeared to no longer be part of 20.04 but the ubuntu-desktop virtual package didn't install an obvious replacement. What is the deal with that?
[15:25] <howarth> Never mind. Found it. Odd that the dist-upgrade stripped it out of the dock.
[15:32] <masteroman> Hey all. I've noticed some issues with Root-on-ZFS installer on daily Focal image. Is this the right place to report such issue with more details?
[15:43] <psymin> I guess if you don't get much input here, this path could work https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Reporting_bugs
[15:48] <masteroman> Apparently I'm just now noticing answers.launchpad.net. Will ask question there. Thank you!
[15:49] <psymin> good luck and thanks for helping!
[15:52] <masteroman> Thanks. Posted question under https://answers.launchpad.net/ubuntu/+question/689661 , we'll see if I provided all the required info or not :-) 
[16:38] <halvors> Will the beta be released to day? Or is it just a state of the development branch?
[16:39] <oerheks> yes, it will be released today, halvors 
[16:39] <oerheks> i read from the team; Looks like ubuntu, xubuntu, ubuntu-mate, ubuntu-budgie, ubuntustudio will get respun beta candidate images in a bit, to get a zfs fix in
[16:39] <oerheks> .. and you want that fix :-P
[17:02] <lotuspsychje> welcome thebiffman_ 
[17:03] <lotuspsychje> welcome tugapower 
[17:03] <tugapower> whats this here ?
[17:03] <lotuspsychje> the support channel for 20.04
[17:03] <tugapower> lotuspsychje: hi
[17:03] <wr> lotuspsychje, alt+f2 xfce4-terminal will do it, but any shortcut key? plus i need to start ssh, what would be command
[17:04] <tugapower> anyone here on 20.04 that use Filezilla ?
[17:04] <wr> sudo systemctl enable ssh?
[17:04] <lotuspsychje> ask your specific question to the channel tugapower and see if volunteers can help
[17:05] <lotuspsychje> wr: this channel is not for 14.04, as i said, its eol
[17:05] <tugapower> prior behabiour on 18.04 when open server over filezilla, it would prompt me password to unlock the ssh keys, and then connecte to the server
[17:05] <wr> lotuspsychje, i know, but commands work, no? i need to do an update on it but ssh has to be working ;)
[17:05] <tugapower> on 20.04 it does not happen and it fails straigh forward the connection to server
[17:06] <tugapower> but if type ssh-add ~/.ssh/id_rsa over terminal, type the password, then filezilla will be hable to conect xitout issues
[17:08] <tugapower> witout this filezilla will not even prompt for the password, it trows error on connection
[17:08] <wr> lotuspsychje, http://ubuntuhandbook.org/index.php/2014/09/enable-ssh-in-ubuntu-14-10-server-desktop/ ok?
[17:09] <lotuspsychje> wr: 14.04 is end of life, means no support anymore
[17:09] <wr> nevermind
[17:09] <lotuspsychje> wr: download a supported version from the topic in #ubuntu please
[17:10] <tugapower> lotuspsychje: anytip to my issue ?
[17:10] <wr> big news
[17:20] <oerheks> https://help.ubuntu.com/lts/serverguide/openssh-server.html good start
[17:25] <halvors> oerheks: What do i need ZFS for?
[17:26] <halvors> oerheks: Is that the only reason for creating new images? Should i use that or just switch with my current development branch install?
[17:26] <oerheks> it is pretty important, zfs and servers
[17:27] <halvors> But for my desktop?
[17:27] <oerheks> just wait and see, there is progress
[17:27] <halvors> I would rather use btrfs anyway
[17:28] <halvors> I have a problem with wine-development package from Ubuntu 20.04 LTS, i get this error: https://paste.ubuntu.com/p/2SRc7GnkVw/ 
[17:28] <halvors> Is the wine-development package missing dependencies?
[17:29] <lotuspsychje> halvors: pastebin your errors if you find something please, volunteers might help you
[17:29] <halvors> lotuspsychje: Um, i did?...
[17:30] <halvors> lotuspsychje: In case you missed it:
[17:30] <halvors> I have a problem with wine-development package from Ubuntu 20.04 LTS, i get this error: https://paste.ubuntu.com/p/2SRc7GnkVw/
[17:30] <lotuspsychje> oh sorry missed that
[17:49] <tugapower> halvors: do you have libcrypt-2.30.so ?
[17:50] <tugapower> forget
[17:51] <tugapower> wich glibc you have ?
[17:51] <halvors> https://paste.ubuntu.com/p/2cgq3bnFcg/
[17:52] <halvors> tugapower: how to check?
[17:53] <tugapower> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867423
[17:53] <oerheks> missing lib32-libldap?
[17:53] <oerheks> reinstall, or fix missing..
[17:54] <halvors> oerheks: don't think this bug is the problem, login and sudo works just fine and no packages failed to install.
[17:55] <tugapower> not that
[17:55] <tugapower> read the all bug from coments
[17:55] <tugapower> its not too much to read
[17:55] <tugapower> but people talk about that lib missing
[17:56] <halvors> think it was fixed after i did install my system.
[17:56] <halvors> lrwxrwxrwx 1 root root 16 mars  15 00:21 /lib32/libcrypt.so.1 -> libcrypt-2.31.so
[17:56] <halvors> also not in the /lib64 folder
[17:58] <tugapower> https://packages.ubuntu.com/search?suite=eoan&section=all&arch=any&keywords=libkrb5.so.26&searchon=contents
[17:58] <tugapower> maybe reinstall that package may fix your issue
[18:01] <halvors> tugapower: Did, apt install --reinstall libkrb5-26-heimdal, no difference.
[18:02] <halvors> both /lib32/libcrypt.so.1 and /lib/i386-linux-gnu/libkrb5.so.26 exists, maybe libcrypt.so.1 does not support XCRYPT_2.0?
[18:03] <halvors> Hmm, what is this? https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867432
[18:03] <halvors> fix is already in apt repositories? i have updated my system from main server
[18:04] <halvors> libc6-amd64:i386 is not installed on my system
[18:13] <halvors> oerheks: why would i need lib32-libldap?
[18:15] <tugapower> halvors: that fix is only deployed trough debian, ubuntu does not have the fix yet
[18:16] <halvors> tugapower: ok, when will those changes be pulled downstream?
[18:16] <tugapower> have no idea mate
[18:16] <tugapower> just a regular user like you
[18:16] <halvors> tugapower: It seems to only affect i386 :-S
[18:23] <halvors> Trying to use LD_PRELOAD i get this: ERROR: ld.so: object '/lib32/libcrypt.so.1' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
[18:24] <halvors> is wine supposed to load the 64 bit libcrypt library?
[19:12] <halvors> Is it ok to update this bug report or should i create a new one? 
[19:12] <halvors> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867432
[19:13] <halvors> So the problem here is that /lib32/libcrypt.so.1 is found first by the linker, similar to what's happening in Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951880) but in my case for lib32.
[19:13] <halvors> Seems the library in /usr/lib/i386-linux-gnu/libcrypt.so.1 works just fine, my dirty workaround for this was to create a link: ln -s /lib32/libcrypt.so.1 /usr/lib/i386-linux-gnu/libcrypt.so.1
[21:02] <donofrio> is this still for 20.04 or 20.10 now that we are in april?
[21:04] <dax> 20.04 until 20.04 comes out
[21:04] <dax> then pretty much useless until the 20.10 toolchain happens
[21:05] <donofrio> k tnx
[21:05] <dax> 20.04 comes out on the 23rd
[21:05] <donofrio> awesome news
[22:26] <Bashing-om> Smedles: Got the /home directories functional ?
[22:57] <Smedles> Bashing-om: nope :(
[22:58] <Bashing-om> Smedles: refresh my memory for the end goal here and we have another fo at it :D
[23:02] <Smedles> Bashing-om: main reason for sharing /home is due to a large virtualbox image ...
[23:03] <Smedles> my thoughts are to copy over my 18.04 /home excluding some large directories and confirm it breaks with focal; then try removing/deleting folders til I confirm what's causing it
[23:03] <Bashing-om> Smedles: A shared home is not a good idea due to differing config files . Do you not just want to mount that external /home partition ?
[23:04] <Smedles> Bashing-om: i'm slowly learning that
[23:05] <Smedles> it always seemed to work ok with 18.04 + 19.10
[23:05] <Smedles> but I'll re-engineer things :)
[23:08] <Bashing-om> Smedles: This help: https://help.ubuntu.com/community/Partitioning/Home/Moving ? 
[23:14] <valorie> what works for me is having a small $HOME and a large /media/Data
[23:15] <valorie> Data can easily live on a HD, while lil home is on the SSD with /
[23:20] <Smedles> Bashing-om: I'm also wondering what will happen when I eventually uprade the 18.04 partition to 20.04
[23:20] <Smedles> valorie: I'll look at doing something similar
[23:21] <valorie> an advantage for me was that I created it by rsyncing from my backups
[23:21] <valorie> so I know that my backups were good
[23:22] <valorie> I've lost a lot a few times from bad backups
[23:22] <Bashing-om> Smedles: As it is an external partition an upgrade will not affect it. But ! I do not recall where that external /home is located.
[23:45] <Smedles> Bashing-om: / is on an nvme drive, /home on a ssd