[01:59] <electricityZZZZ> trying to do an install of ubuntu 20.04 onto an encrypted ZFS root partition. from scratch, i'm fine with wiping the drive. i followed some guide which involved editing what i think was a ubiquity installer script but i ended up with an unencrypted ext4 partition. can i get any help with this?
[02:11] <Eickmeyer> !support | electricityZZZZ
[02:12] <electricityZZZZ> i asked in #ubuntu and got crickets,... i guess i can try again
[02:12] <sarnold> electricityZZZZ did start there, it's just a pretty niche thing, not many have tried it yet..
[02:12] <electricityZZZZ> i was really looking forward to first class ZFS support on ubuntu 20
[02:12] <Eickmeyer> !patence | electricityZZZZ
[02:12]  * electricityZZZZ sits and stares at a wall
[02:13] <sarnold> hehe
[02:13] <Eickmeyer> Oof, that one was removed.
[02:13] <Eickmeyer> Basically, if someone doesn't know the answer, nobody will answer you.
[02:13] <Eickmeyer> That's kinda the rule there.
[02:13] <electricityZZZZ> right, so nobody knows
[02:13] <electricityZZZZ> this was the guide i used, fwiw: http://archive.is/w3K1E
[02:14] <Eickmeyer> electricityZZZZ: This channel is not for support, this is for development collaboration.
[02:14] <Eickmeyer> You won't get an answer here either.
[02:14] <sarnold> electricityZZZZ: oh wow, that actuallylooks pretty good
[02:15] <electricityZZZZ> eickmeyer: oh okay sorry to pollute. maybe you guys could add a "encrypted ZFS root" button to the installer tho, i would transfer lots of cosmic karma your way
[02:17] <Eickmeyer> electricityZZZZ: I'm not part of the desktop team. I recommend a bug report for "wishlist" style items like that.
[02:17] <Eickmeyer> electricityZZZZ: In this case, "ubuntu-bug ubiquity".
[02:18] <Eickmeyer> electricityZZZZ: (the people in this channel don't handle the installer either)
[02:18] <electricityZZZZ> ok
[02:31] <electricityZZZZ> ok i'll mention here that the issue is that if you use that guide (which so far seems to work, i'll provide final confirmation in a few min when the install finishes) then you can't use uh, certain characters in your password
[03:47] <callmepk> Good morning
[04:27] <jibel> good morning
[06:22] <didrocks> good morning
[06:41] <seb128> goood morning desktopers
[06:41] <callmepk> Hi jibel didrocks seb128 
[06:42] <didrocks> salut seb128, hey callmepk 
[06:43] <seb128> lut didrocks, jibel, hey callmepk, how are you?
[06:44] <didrocks> good, thanks! Disk swapping and reinstallation day on my main laptop to use ZFS by default! That will be interesting :)
[06:44] <didrocks> and you?
[06:48] <callmepk> seb128 I am good, thanks! right now looking into a bug reported for WSL version of Ubuntu
[06:49] <seb128> didrocks, good, still a bit tired but it's friday! bug triage day and probably some email/trello cleaning and maybe some scripts hacking
[06:52] <didrocks> hehe, sounds easy enough :)
[07:01] <ricotz> hey desktopers!
[07:01] <didrocks> hey ricotz 
[07:02] <ricotz> please get libreoffice accepted
[07:02] <ricotz> https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=
[07:03] <didrocks> I think there is no SRU team member reading actively this channel, should try rather #u-release?
[07:05]  * didrocks will try to enable secure boot with nvidia \o/
[07:41] <oSoMoN> good morning desktoppers, happy release party hangover!
[07:43] <didrocks> hello oSoMoN 
[07:47] <oSoMoN> salut didrocks 
[07:57] <marcustomlinson> good morning desktoppers
[07:57] <oSoMoN> mornin' marcustomlinson 
[07:57] <seb128> lut oSoMoN, hey marcustomlinson, how are you?
[07:58] <didrocks> hey marcustomlinson 
[07:59] <marcustomlinson> hey oSoMoN seb128 didrocks. I'm not too bad thanks :) you guys?
[07:59] <seb128> marcustomlinson, I'm good! a bit tired but release is over and W.E is arriving so plenty of opportunity to fix the situation :)
[08:00] <marcustomlinson> indeed!
[08:02] <Laney> morning
[08:03] <marcustomlinson> hey Laney
[08:04] <marcustomlinson> by the way brian reviewed my update-manager fix yesterday so you can cross that off your todo :)
[08:05] <Laney> marcustomlinson: yeah, I asked him if he wanted to take a look
[08:05] <didrocks> hey hey Laney 
[08:05] <Laney> good old brian!
[08:05] <marcustomlinson> Laney: ah ok thanks
[08:05] <Laney> oin didrocks 
[08:05] <Laney> m
[08:10] <oSoMoN> salut seb128, I'm good, thanks!
[08:10] <oSoMoN> good morning Laney 
[08:11] <oSoMoN> https://discourse.ubuntu.com/t/error-upgrading-to-development-version-of-20-04/15522 < known bug?
[08:12] <oSoMoN> (I suppose the -d flag doesn't hurt here, although it wasn't needed)
[08:12] <seb128> hey Laney, how are you?
[08:13] <Laney> what up oSoMoN seb128 
[08:13] <Laney> I'm doing alright
[08:14] <Laney> bit tired, looking forward to the weekend
[08:15] <oSoMoN> this will be well deserved
[08:15] <Laney> :>
[08:16] <seb128> oSoMoN, doesn't seem to be report, I wish people would stop using discourse to post bugs though :/
[08:17] <Laney> https://discourse.ubuntu.com/t/about-the-desktop-category/57 maybe that topic should say something about this
[08:17] <Laney> like links to what to do if you want to file a bug
[08:19] <oSoMoN> agreed, but better to get a report on discourse than no report at all, if it's a valid issue
[08:30] <seb128> oSoMoN, if it's hitting enough users to be import we will get a report on launchpad, if it's a valid issue impacting 1 user ... we just don't have the resources to deal with those
[08:30] <seb128> import->important
[08:31] <seb128> well, at least that's my opinion :)
[08:38] <Laney> Alright let's look at that accountsservice crash thing eh
[08:40] <Laney> btw if you have things in the queue that should go into focal, it would be worth SRUifying the bug description and probably asking the SRU vanguard for them to be reviewed
[08:55] <jibel> We should probably create a default bug report with instructions for people who are getting squashfs errors and skipped or ignored the integrity check and an apport hook that redirect this report. WDYT?
[08:55] <Laney> interesting!
[08:55] <Laney> does casper notify the live system when you skip it?
[08:56] <jibel> s/apport hook/an apport bug pattern/
[08:57] <Laney> well if not, I guess it could
[08:57] <Laney> that's a good idea
[08:57] <jibel> /var/log/installer/casper_md5check contains skip or fails
[08:58] <jibel> fail*
[08:58] <jibel> we could use that in the installer too
[08:58] <jibel> but for now, a bug pattern can be effective immediately
[09:00] <seb128> right
[09:00] <jibel> We could prevent the installer from starting if checksum failed, and display a message on the 'Prepare' page if the user skipped it
[09:01] <seb128> xnox mentioned making ubiquity read the status of the file and do something but I don't think he got to work on that yet
[09:01] <seb128> we should try to get something done for .1
[09:01] <seb128> right
[09:01] <jibel> I'll do the report + bug pattern
[09:01] <seb128> thx
[09:03] <didrocks> not my day in term of usb: one official ubuntu key doesn’t work anymore, another, after a long copy, 18 errors found in files (and then the screen is stuck). humf
[09:03] <didrocks> trying a 3rd usb key now
[09:03] <didrocks> but getting on slower and slower keys
[09:04] <Laney> I never got to give you one of those funny Ubuntu ones :(
[09:04] <Laney> if you like slow USB keys
[09:04] <didrocks> but maybe more reliable than the rest :p
 We should probably create a default bug report with instructions for people who are getting squashfs errors and skipped or ignored the integrity check and an apport hook that redirect this report. WDYT? -> Ahhhh that's why the disk check is ran by default now!!! :D
[09:07] <jibel> pieq, and still people are ignoring it
[09:07] <pieq> jibel, "well, it told me to press Ctrl+C!" :)
[09:07] <jibel> but we receive far less reports than without the dis kcheck
[09:08] <jibel> pieq, stop blindly doing what's written on the screen :P
[09:08] <seb128> jibel, 'ignoring', I'm not even sure they see it, that doesn't block the boot for confirmation does it? (I didn't hit the case where I had a buggy media recently)
[09:08] <pieq> Laney, I think I know what keys you're talking about, we still have a lot in the Taipei office :D
[09:08] <jibel> seb128, when it fails you have a message that tells you so
[09:08] <seb128> the result is displayed on screen some seconds when then start continue no?
[09:09] <seb128> well, the ISO takes 3 min to boot, I don't stare at the screen
[09:09] <seb128> I usually go back to do  something while it's booting
[09:09] <pieq> Laney, but with the new trendy laptops, the USB ports are getting closer and closer and this poor key is really thick by today's standards... (thick and *slow*)
[09:09] <seb128> and when I come back it's a the desktop
[09:09] <seb128> without clue of the check result
[09:09] <seb128> or at the maybe ubiquity
[09:09] <Laney> pieq: Yep! The *one* time I tried to use it, I had to unplug some other stuff
[09:10] <Laney> and then I discovered how slow it was, and well... not sure where it is now actually
[09:10] <Laney> ah I never actually saw the md5check failing, I thought it made you press enter to confirm
[09:11] <pieq> Actually, regarding these messages that are shown between the vendor Logo and the Ubuntu logo, I've noticed some of them are displayed like 1/10th of a second and disappear
[09:12] <pieq> on my laptop with encrypted partition. I think it's saying "partition decrypted successfully" or something along these lines, but I'm not sure
[09:13] <didrocks> seb128: depends on how bad your disk is, mine displayed the message for few seconds, then erased (spinner still there though) and froze
[09:15] <didrocks> I clearly didn’t have to press enter
[09:15] <seb128> didrocks, right, the issue is that I often comes back to the machine 10 min after it's done booting
[09:15] <seb128> but yeah, we have the bases so we can improve the UI part for .1
[09:16] <didrocks> I wonder if we could set something for ubiquity to pick it up
[09:17] <didrocks> display a big red alert and report in telemetry + apport if reported
[09:30] <seb128> didrocks, imho we should just display a screen explaining that the image is corrupted with instructions on download/write it again and exit and not let the option to do the install ... do we have any telemetry if we don't process with the installation?
[09:31] <didrocks> seb128: no, telemetry is only on first boot by design
[09:32] <seb128> right
[09:57] <didrocks> xnox: hey, so, I am a little bit puzzle about the enroll procedure with a nvidia card with secure boot enabled after selecting installing the nvidia device
[09:58] <xnox> Di
[09:58] <didrocks> the installer says that I will be guided by ubuntu but the reality isn’t as bright :p
[09:58] <didrocks> I have 4 options
[09:58] <didrocks> on Perform MOK management:
[09:58] <didrocks> Continue boot (seems this will disable signing the driver)
[09:58] <didrocks> Enroll MOK
[09:58] <didrocks> Enroll key from disk
[09:58] <didrocks> Enroll hash from disk
[09:59] <didrocks> which one should I use to sign my nvidia driver? :p
[09:59] <xnox> didrocks: funny thing, we latelinked Nvidia modules with canonical signatures and should not be doing mok enrollment
[09:59] <didrocks> (and argh, it just timed out, rebooted and Enroll MOK became Reset MOK now)
[09:59] <didrocks> ah, could be another driver than nvidia maybe?
[09:59] <xnox> Any dkms
[10:00] <Laney> There's a bug where we present that mok stuff even when it's not needed
[10:00] <Laney> Steve filed it, probably on ubiquity
[10:00] <xnox> And yes mok stuff is confusing.
[10:00] <xnox> I think you need second option (enroll)
[10:00] <didrocks> I’ll check if I have more dkms stuff
[10:00] <didrocks> ok, even now that it says reset?
[10:01] <xnox> And then it should ask you for characters from the password you set an hour ago at the ubiquity screen.
[10:01] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856410
[10:01] <xnox> didrocks: yes, because mok state is weird
[10:02] <xnox> Imho mok should be done on shutdown with plymouth
[10:02] <xnox> Such that it is right before reboot
[10:02] <didrocks> that would feel more guided indeed
[10:02] <didrocks> ah, I bet this is qwerty
[10:03] <didrocks> interesting, it did fail
[10:04] <didrocks> ok, let’s boot and see if I have any dkms driver other than nvidia
[10:05] <ricotz> seb128, the libreoffice package sitting in focal unapproved it meant to fix the upgrade issue https://bugs.launchpad.net/bugs/1874556
[10:05] <Wimpress> Morning desktoppers :-)
[10:05] <oSoMoN> good morning Wimpress 
[10:05] <didrocks> xnox: ok, confirming Laney, I don't have any dkms modules loaded, so the prompt is a lie :p
[10:05] <didrocks> thanks, and yeah, the experience needs to be enhanced IMHO
[10:06] <didrocks> hey Wimpress 
[10:07] <xnox> didrocks:  ergh.... you can't have any loaded if MOK is not enrolled
[10:07] <xnox> didrocks:  do you have any installed? $ dkms status
[10:08] <didrocks> xnox: I have no dkms installed
[10:08] <xnox> perfect
[10:09] <didrocks> (just confirmed thus Steve bug)
[10:14] <didrocks> Wimpress: what GUI apps you used to know if you were running with what card? nvidia-settings is set on Performance Mode (not on demand), but I still have the On demand option with right clicking on the dock (remember the bug we discussed at the Yaru sprint)
[10:21] <didrocks> using firefox or chrome, the driver change, but the nvidia one isn’t recognized
[10:25] <didrocks> Wimpress: FYI, I have to change to On demande for things to work as expected
[10:25] <didrocks> which isn’t the default
[10:26]  * didrocks will file a bug
[10:41] <jibel> seb128, are you ok with the wording https://bugs.launchpad.net/ubuntu/+bug/1874662 ?
[10:41] <jibel> I'll push the bug pattern
[11:04] <jibel> done, that should quieten lp a bit.
[11:29] <seb128> ricotz, hey, had nice for libreoffice, just need a SRU team member to review the queue now :)
[11:31] <seb128> jibel, the wording sounds fine to me
[13:36] <PaulePanter> Hi. Have you heard of PulseAudio user service not starting after updating to Ubuntu 20.04?
[13:44] <PaulePanter> For the user there are errors in the user journal.
[13:53] <jibel> seb128, xnox bug 1874809 is interesting, integrity check passed by installation failed with a squashfs error
[13:54] <jibel> s/by/but
[14:29] <xnox> jibel:  nice! responded
[14:29] <xnox> jibel:  i suspect bad usb stick, bad RAM, or bad target harddrive device.
[14:43] <seb128> PaulePanter, hey, no mention of this nor bug report so far
[15:44] <hellsworth> good morning desktopers
[15:45] <kenvandine> good morning hellsworth 
[15:46] <hellsworth> hi kenvandine 
[16:21] <marcustomlinson> have a great weekend desktoppers
[16:32] <oSoMoN> you too marcustomlinson, enjoy!