[08:11] <uvizachan> nigger
[08:12] <uvizachan> oh w8 i said it
[08:12] <uvizachan> sorry
[08:13] <uvizachan> Ehhh, anyways I was wondering if there's any impediment between this OS and me trying to use a VM to relay my Internet connections.
[08:17] <gnrp> uvizachan: Sneaky...
[08:17] <gnrp> uvizachan: Uhm, well, I don't know why you would do that, but yes, should work?
[08:19] <gnrp> you mean a VM hosted on the same machine? It doesn't make too much sense and you spend resources, but it is possible
[08:21] <uvizachan> Cool.
[15:12] <johanhelmuth> Hmm, I'm having some issues with my boot time. I've checked my fstab, and everything is in order there, pointing to the correct UUIDs etc. types, mount points, options everything looks good. I've checked "systemd-analyze critical-chain" and checked the "systemd-analyze time", basically the userspace takes 1,6 seconds to get going, wich is nice and fast. But the kernel startup is insanely slow - 33
[15:12] <johanhelmuth> seconds..
[15:13] <johanhelmuth> Been googling for a bit, and most solutions I can find tend to point towards slow startups because of graphical.target, which is part of the userspace boot time, which isn't the case for me.
[15:14] <johanhelmuth> Could this potentially be a grub issue?
[15:16] <diogenes_> johanhelmuth, adm graphics?
[15:17] <diogenes_> s/adm/amd
[15:17] <johanhelmuth> nvidia graphics
[15:18] <johanhelmuth> I tried adding nomodeset to grub, but nothing really changed.
[15:19] <johanhelmuth> I also checked the boot log, and the only thing failing is the AppArmor initialization.
[15:19] <diogenes_> is it a fresh install? upgrade? what kernel? has it always been this slow or it's a new situation?
[15:19] <johanhelmuth> It's a fresh install, xubuntu minimal install
[15:20] <johanhelmuth> kernel: 4.15.0-46-generic
[15:20] <diogenes_> and have you upgraded the kernel?
[15:20] <johanhelmuth> I have not
[15:20] <diogenes_> what is in: ls /boot
[15:21] <johanhelmuth> config-4.15.0-46-generic      memtest86+.bin            System.map-4.15.0-46-generic
[15:21] <johanhelmuth> grub                          memtest86+.elf            vmlinuz-4.15.0-46-generic
[15:21] <johanhelmuth> initrd.img-4.15.0-46-generic  memtest86+_multiboot.bin
[15:21] <johanhelmuth> That's in /boot
[15:21] <diogenes_> i see
[15:21] <diogenes_> patebin the: systemd-analyze blame
[15:22] <johanhelmuth> https://pastebin.com/UyXK17ez
[15:22] <johanhelmuth> That mostly displays the userspace boot, right?
[15:23] <johanhelmuth> systemd-analyze time shows:
[15:23] <johanhelmuth> Startup finished in 32.981s (kernel) + 1.669s (userspace) = 34.650s
[15:23] <johanhelmuth> graphical.target reached after 1.632s in userspace
[15:24] <diogenes_> yeah, nothing extraordinary in there
[15:24] <johanhelmuth> I did notice one thing that might be odd, not sure though.
[15:25] <johanhelmuth> checking "blkid", my boot partition doesn't have a UUID
[15:25] <johanhelmuth> Which I'm certain it always have had before
[15:25] <johanhelmuth> "/dev/sda1: PARTLABEL="boot" PARTUUID="8e502ceb-20c6-4e85-a82d-e4aa89841940"
[15:27] <johanhelmuth> Uhm, wait a second, fstab shouldn't contain boot, right?
[15:30] <diogenes_> johanhelmuth, i need to leave now, hopefully someone will help you fother on.
[15:31] <Spass> johanhelmuth, you could try upgrading the kernel to 4.18 with this command "sudo apt install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04"
[15:31] <Spass> but that's a pretty big step, should be safe tho
[15:32] <johanhelmuth> will definitely try that out if all else fail, for sure
[15:32] <johanhelmuth> I just have this feeling I messed my boot partition up somehow
[15:46] <johanhelmuth> Spass: Does your fstab include a line for the boot partition?
[15:46] <Spass> let me see
[15:49] <Spass> well, I have my ext4 there, mounted to "/" described with UUID with these options "errors=remount-ro 0 1"
[15:49] <Spass> I didn't make any changes to it, so it's a default entry
[15:49] <johanhelmuth> alright, that's pretty much what I was hoping to hear
[15:49] <johanhelmuth> alright, thanks
[15:50] <johanhelmuth> so my fstab is definitely not the issue then, hmm
[15:52] <johanhelmuth> I am almost certain I messed my boot partition up however, somehow. Because when I check the "blkid", everything is showing a UUID, TYPE etc. Except for my boot partition, it just shows the PARTLABEL and PARTUUID.
[15:54] <johanhelmuth> Gonna stop my spammy speculations in chat here, and look for a fix. Thanks for the help again, Spass.
[15:56] <Spass> no problem, stay for a while, maybe someone will have some hints for you
[16:00] <johanhelmuth> Yeah, I'm always online, I have my irc client running on my homeserver 24/7
[16:35] <johanhelmuth> Thank god, it's solved now
[16:35] <johanhelmuth> "Startup finished in 1.980s (kernel) + 1.667s (userspace) = 3.648s"
[16:35] <johanhelmuth> that shaved off 28 seconds
[16:36] <johanhelmuth> I had to remove the UUID from "RESUME=" in "/etc/initramfs-tools/conf.d/resume", and replace it with "none".
[16:37] <johanhelmuth> Apparently boot timed out waiting to resume a specific device, every time I boot.
[16:38] <Spass> thanks for the info, was that "/etc/initramfs-tools/conf.d/resume" your custom config?
[16:38] <johanhelmuth> Honestly, I didn't even know it existed. Must be something that generated itself when I mounted my media hard drive
[16:39] <johanhelmuth> Or wait.. now I get it, oh wow.
[16:40] <johanhelmuth> So during installation of Xubuntu, for some reason my ssd was named sdb, and my bootable installation usb was sda. But after installation, somehow, the system changed my ssd to sda.
[16:41] <johanhelmuth> Which screwed my fstab up, so I had to fix the fstab. So I'm guessing what the resume was pointing to, was the old swap.
[17:19] <xubuntu70w> hello everyone
[17:20] <xubuntu70w> I'm using xubuntu 18.04
[17:20] <GridCube> good?
[17:21] <xubuntu70w> i  don't understand why my laptop give me a blank/black screen when it wakes up from suspend
[17:21] <xubuntu70w> is it driver related or something ?
[17:22] <GridCube> it's because the screensaver is still enabled
[17:22] <GridCube> most probably
[17:22] <GridCube> it could be other things
[17:22] <xubuntu70w> still enabled but why ?
[17:22] <GridCube> disable your screen power saving settings and try again
[17:22] <xubuntu70w> ok thank you i'll try that
[17:23] <GridCube> i don't know https://askubuntu.com/questions/1094529/xubuntu-screen-does-not-wake-up-after-being-locked
[17:23] <GridCube> it's a very common problem
[17:24] <GridCube> sorry meant to paste this xubuntu70w https://bugs.launchpad.net/ubuntu/+bug/1804235
[17:25] <Vimar> Hi
[17:40] <xubuntu70w> Thank you GridCube i don't have a blak screenn anymore
[17:42] <GridCube> xubuntu70w: :)
[17:43] <GridCube> xubuntu70w: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1303736
[23:40] <johanhelmuth> Maybe a silly question, but do I need to remove nvidia drivers before installing new ones? Or will it automatically do everything for me? Suppose I have Nvidia 390 drivers, and I want to install the Nvidia 418 drivers. Will a "apt install nvidia-driver-418" suffice? Or do I have to remove stuff beforehand?
[23:40] <johanhelmuth> Googled it, and I see mixed responses.