=== lotuspsychje_ is now known as lotuspsychje
[09:14] <lotuspsychje> confirmed bug #1866000 feel free to doublecheck aswell
[09:14] <ubottu> bug 1866000 in gnome-control-center (Ubuntu) "incorrect default apps for calendar and photos" [Undecided,Confirmed] https://launchpad.net/bugs/1866000
[09:16] <lotuspsychje> mcphail, popey previous authentication window disform is now fixxed
[12:01] <krauser> Having a problem with not only 19.10 but also 20.04 daily build on my computer. It doesn't boot, with or without splash screen, with or without modeset option. Specs are here: https://paste.ubuntu.com/p/xrSxwjxST7/ And message errors here: https://imgur.com/WOjj8JI. Debian and Arch installed fine, just to point it out/hopefully help in someway
[12:02] <lotuspsychje> krauser: uefi or legacy?
[12:03] <krauser> uefi(also have legacy option)
[12:04] <lotuspsychje> krauser: bit cards like GTX and RTX usually need !nomodeset workaround, but uefi settings can also influence this
[12:05] <krauser> yeah I tried nomodeset, all it did was change the resolution of the letters/splash screen
[12:06] <lotuspsychje> krauser: is this you? https://www.reddit.com/r/Ubuntu/comments/fcme81/cant_boot_ubuntu_1910_nor_2004_daily_build/
[12:07] <krauser> Yes
[12:08] <krauser> Also tried with and without CSM mode, but the same applies
[12:08] <lotuspsychje> krauser: did you try with other ubuntu releases iso's?
[12:08] <lotuspsychje> like 18.04 LTS
[12:09] <lotuspsychje> cant find a related bug on segfault right away for 20.04
[12:12] <krauser> i'll try 18.04 after lunch
[12:17] <lotuspsychje> krauser: wich brand is your system plz?
[12:28] <krauser> If i'm understanding correctly that's the motherboard info you want right? ASUS PRIME Z390M-PLUS
[12:28] <lotuspsychje> thank you krauser 
[17:36] <lotuspsychje> wb krauser 
[17:36] <lotuspsychje> did you test bionic on your issue?
[17:37] <krauser> hey, yes I did, and couldn't boot, but got a different message
[17:37] <krauser> https://imgur.com/a/Q7O3Zgv
[17:38] <lotuspsychje> hmm
[17:38] <lotuspsychje> krauser: do you dualboot currently?
[17:41] <krauser> well, my /boot/efi, looking at lsblk is on nvme0n1p2(this is the sdd drive with windows on it) while the sda has my debian install. When I boot the system, i'm prompted to Debian's grub, which contains a line for windows
[17:41] <lotuspsychje> krauser: this smells like a double problem to me
[17:42] <lotuspsychje> uefi bootable nvme + your nvidia card not recognized, needing its proper nvidia driver
[17:42] <lotuspsychje> if i was you, id try legacy boot + nomodeset
[17:42] <krauser> how do I do that, go on boot in my bios and set legacy only?
[17:45] <krauser> this might help too https://askubuntu.com/questions/1074098/booting-a-nvme-drive i'll try everything from what you said and this
[18:10] <krauser> tried some things, disabling fast boot removes part of the errors but the one consistant is that the "ntfs-3g" problem remains
[18:13] <krauser> it's that sdd hardrive that is the problem most likely, not sure how to go around it
[20:49] <krauser> Well, didn't exactly fixed the issue but using a mini.iso I finally got past boot and installed Ubuntu. I hope there will be one for 20.04 too
[20:55] <ducasse> anyone else having trouble generating initrds since mkinitramfs hangs on the plymouth hook?
[20:56] <ducasse> purged plymouth, and now it's working again, but it meant also losing lightdm
[22:17] <mcphail> ducasse: just updated a minute ago. There were some plymouth packages updated but no issues regenerating the initramdisk
[22:19] <ducasse> i'll try reinstalling plymouth tomorrow and try again, too late to mess with it today