=== marcc is now known as kub
=== brainwash_ is now known as brainwash
[09:49] <oaky> This is my ouput when running "systemd-analyze time", "Startup finished in 3.446s (kernel) + 2.761s (userspace) = 6.207s". I'm wondering how to interpret this correctly, is it correct to say that given that it says 6.2 seconds, that after my Thinkpad BIOS screen has passed and the OS has begun loading, it should take 6.2 seconds to get to the login screen? Or am I missing something?
[09:50] <brainwash> kinda
[09:51] <brainwash> "Note that these measurements simply measure the time passed up to the point where all system services have been spawned, but not necessarily until they fully finished initialization or the disk is idle."
[09:52] <oaky> Ok, because there is quite a wide gap between my boot time and 6.2 seconds.
[09:53] <brainwash> by how much?
[09:54] <brainwash> kernel takes over until you can login
[09:54] <oaky> Is it normal for it to deviate almost 20 seconds? I'd guess my boot time is around 25-30 seconds. Though I realize now I've measured from when I hit the start button but maybe I should measure from when the BIOS screen goes away instead.
[09:54] <oaky> I'm running on an SSD.
[09:54] <brainwash> yes, you have to measure after the bios/uefi is done
[09:54] <oaky> (25-30) seconds is my estimate if I cut out the BIOS screen
[09:55] <oaky> it's 40-44 seconds when measured from start-click
[09:56] <brainwash> you could check the output of "systemd-analyze blame", "systemd-analyze critical-chain" and even create a boot graph with "systemd-analyze plot >bootup.svg"
[09:56] <oaky> Ye I've done that
[09:56] <brainwash> no useful info?
[09:57] <oaky> Well I had the something "Wait for network service" at about 7.7 seconds and I disabled that because what I read I don't really need it
[09:58] <oaky> And with that disabled the most consuming thing when running blame is "1.061s keyboard-setup.service"
[09:59] <brainwash> did you try to boot into command line instead of the graphical login screen (lightdm)?
[10:00] <oaky> Nope I haven't tried that
[10:01] <brainwash> in case there is something strange going on with the graphical initialization
[10:01] <oaky> Ye
[10:01] <oaky> So I guess I'll have to change something now, and then reboot
[10:01] <oaky> as long as I know how to get back into the GUI :p
[10:02] <brainwash> sudo systemctl set-default multi-user.target
[10:02] <brainwash> sudo systemctl set-default graphical.target
[10:02] <brainwash> second command to revert it
[10:02] <oaky> so if I run first command, then restart, I boot into cli?
[10:03] <brainwash> yes
[10:03] <oaky> Alright, I'll give it a try and measure time aswell. back in a bit
[10:08] <oaky> So, it took 24 seconds to get to the cli login prompt (exl. bios time). And systemd-analyze time shows 7.047s
[10:08] <oaky> so 17 seconds is "unaccounted" for
[10:09] <brainwash> mmh yeah
[10:09] <oaky> "Startup finished in 3.447s (kernel) + 3.599s (userspace) = 7.047s" when booting with the multi-user.target enabled. and I just entered "lightdm" afterwards to get into the GUI
[10:10] <brainwash> can you share the critical-chain output via https://paste.ubuntu.com ?
[10:11] <brainwash> other than that, you'll have to check if there is some hint in the "dmesg" output (or journalctl)
[10:12] <oaky> https://paste.ubuntu.com/p/sG7B2KXh4j/
[10:13] <brainwash> oh well
[10:15] <brainwash> which xubuntu release is that?
[10:15] <oaky> 18.04
[10:16] <oaky> Any keywords I can grep frolook form "dmesg", since I don't really know what to
[10:16] <oaky> to look for*
[10:17] <oaky> That sentence got messed up, any keywords I can grep from the dmesg output?
[10:17] <brainwash> you scroll to the end while keeping an eye on the timestamp
[10:19] <brainwash> maybe a timeout is mentioned there
[10:19] <brainwash> or error
[10:19] <oaky> Hmm ye. I'll look through it and paste the parts that might be of interest
[10:20] <brainwash> going afk for a bit
[10:20] <oaky> parts of interest, I assume is parts where there are large time gaps
[10:20] <oaky> ok
[10:21] <tomreyn> oaky: dmesg -T if you prefer wall clock time over milliseconds since boot.  or use journalctl -b
[10:21] <tomreyn> *  journalctl -kb
[10:25] <oaky> Ok
[10:25] <oaky> The output from journalctl seems to include less info though
[10:26] <oaky> On this paste, you can see some major time gaps
[10:26] <oaky> https://paste.ubuntu.com/p/rVwRZjPtdf/
[10:27] <oaky> Biggest gap seems to be here: "[   10.145855] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[10:27] <oaky> [   72.413203] random: crng init done"
[10:27] <oaky> 10.....72
[10:27] <tomreyn> is this a VM then?
[10:28] <tomreyn> hmm no you have wireless devices, can't be a VM then
[10:28] <oaky> Nope, running xubuntu on real hardware. Though I did just install virtualbox and win10 on a VM
[10:29] <oaky> should mention aswell that this is a fresh install of xubuntu, installed yesterday
[10:29] <tomreyn> anyways, there's a lack of entropy, causing the cryptographics random number generator initialization to be delayed. which itself causes the delayed boot to desktop.
[10:30] <tomreyn> is this system fully updated, yet?
[10:30] <tomreyn> sudo apt update && sudo apt full-upgrade
[10:31] <oaky> Yep, everything is up-to-date
[10:31] <tomreyn> which hardware is this?  journalctl -b | grep 'DMI:'
[10:32] <oaky> "DMI: LENOVO 4174W2X/4174W2X, BIOS 8CET63WW (1.43 ) 10/12/2016"
[10:33] <tomreyn> is there an option to enable the IOMMU in the BIOS (UEFI) setup?
[10:33] <oaky> I read something online about similar things as what you mentioned with randomness, someone said when moving their mouse/pressing keys during boot it decreased boot-time, but I tried it and it didn't seem to improve.
[10:34] <tomreyn> look for the iommu option, if there is none you can install a software which will increase available entropy by adding new entropy sources.
[10:35] <tomreyn> but it'd be a little better to enable the kernel to do it the 'nmormal' way, so let's look for that first
[10:35] <tomreyn> that software is called haveged
[10:36] <oaky> Ok
[10:36] <oaky> I'll reboot into bios and look for IOMMU and set it to enabled if I find it
[10:36] <oaky> back in a bit
[10:41] <PoolShark_> Morning... does the video driver in 18.04 support 4k at 60Hz? All of my hardware should be good but I can't get more than 30Hz out of it
[10:44] <Spass[m]> PoolShark_: hello, what monitor do you have exactly? did you check on other cables? sometimes they are the culprit
[10:45] <Spass[m]> also, what graphics card do you have?
[10:45] <PoolShark_> Spass[m]: it's a Toshiba 4K 60Hz TV... just bought new cables that support HDMI 2.2 just in case it was that.. it's a GTX1060 card that is 2.0b, which should also do 4K at 60Hz. I can get 60Hz out of the TV up to 2880x1620 but if I go the next step to 3840x2160, 60Hz is not available as an options
[10:46] <oaky> Could not find anything related to IOMMU unfortunately
[10:48] <Spass[m]> PoolShark_: 18.04 should have the 430 branch of NVIDIA drivers already (maybe they're still in the "bionic-proposed" repo), which version do you have installed currently?
[10:48] <PoolShark_> Spass[m]: good question, let me take a look
[10:48] <PoolShark_> It appears to be using nouveau
[10:48] <Spass[m]> you can check that in the NVIDIA config GUI app dor example
[10:49] <Spass[m]> well, you should try do change it to proprietary and check, 418 or 430
[10:49] <tomreyn> oaky: ok, so do the haveged then. also see this newer bios update available for your system (you're on 1.43 currenty): https://pcsupport.lenovo.com/gb/en/products/LAPTOPS-AND-NETBOOKS/THINKPAD-T-SERIES-LAPTOPS/THINKPAD-T420S/4174/4174W2X/downloads/DS014963
[10:49] <Spass[m]> unless you don't want anything proprietary on you system
[10:49] <PoolShark_> It lists 390 as my nvidia option
[10:50] <PoolShark_> so I guess I need to add the bionic-proposed repo to sources.list and install something newer huh?
[10:50] <Spass[m]> you could try with that 390 first
[10:51] <Spass[m]> if that wouldn't work you can then 1) add PPA or 2) enable proposed
[10:51] <PoolShark_> alright let me give it a go.. I tried to do this before I reinstalled the system but the nvidia driver would only drive one of my screens and at 1024x768 heh.. that is kinda what prompted me to nuke from orbit and start over hehe
[10:51] <oaky> tomreyn: Ok, I'll have a look. But what do you make of "for Windows 8,Win 7Vista,Xp"
[10:52] <tomreyn> oaky: i notice that it's an .iso and a .txt file and realize that those are universal.
[10:52] <Spass[m]> oh, and if you won't be able to boot to your system just go to Ctrl+Alt+F2, log in and "sudo apt purge nvidia-driver-390"
[10:53] <PoolShark_> Spass[m]: roger
[10:53] <PoolShark_> will take a while to download the new driver... DSL
[10:53] <PoolShark_> lol
[10:53] <Spass[m]> but I guess your card really needs the newer driver than 390...
[10:53] <oaky> tomreyn: Ok. I'll first try updating the bios to 1.46 and then if nothing changed I'll look into haveged. Thanks for the help so far
[10:53] <PoolShark_> Spass[m]: that sounds reasonable... I think all the hardware is okay
[10:54] <Spass[m]> PoolShark_: so maybe go with the PPA route?
[10:54] <PoolShark_> well it's downloading 390 now... we'll try that
[10:54] <tomreyn> oaky: you're welcome, good luck.
[10:54] <Spass[m]> and one more thing, someone mentioned that there could be problem with gtx1650 and proprietary drivers when you have secure boot anabled
[10:55] <Spass[m]> *enabled
[10:55] <Spass[m]> something with the signatures...
[10:55] <Spass[m]> oh, you have 1060
[10:55] <Spass[m]> so maybe 390 drivers will be sufficient after all
[10:56] <PoolShark_> no secure boot for me
[10:56] <PoolShark_> ok it's done... gonna restart and cross my fingers that I still have all 3 monitors
[10:56] <PoolShark_> brb
[10:57] <tomreyn> nvidia drivers are proprietary, source code is not available to canonical. so they can't sign them with their secure boot accredited signing key.
[10:58] <Spass[m]> <insert_Linus_T_showing_one_of_his_fingers_here>
[10:58] <PoolShark_> back
[10:59] <Spass[m]> how bad is it? ;)
[10:59] <PoolShark_> Spass[m]: It almost worked
[10:59] <PoolShark_> I did get all three monitors back, which was good.. but I can only get 59.9Hz out of the TV
[10:59] <PoolShark_> (hahahahahaha)
[10:59] <PoolShark_> so yeah I think it's fine now
[11:00] <Spass[m]> 59.9 is good enough I would say :P great
[11:00] <PoolShark_> I think some of my desktop icons went off screen though
[11:00] <PoolShark_> some of them have gone missing
[11:01] <Spass[m]> can you somehow sort them?
[11:01] <PoolShark_> yeah I did a right click / arrange
[11:01] <PoolShark_> but nada
[11:01] <Spass[m]> or, go to your ~/Desktop folder in Thunar, cut them, paste somewhere else temporarly, and then move again on the desktop
[11:02] <PoolShark_> ohhh I see what's happening
[11:03] <PoolShark_> so you know that screen panel where you can position multiple monitors?
[11:03] <Spass[m]> you mean "xfce4-display-settings"?
[11:04] <PoolShark_> left to right I have my 24inch, 24inch, and 43inch screen, 1080, 1080, and 2160 respectively.. I'm centering up the 4K monitor on a horizontal axis through the center of each monitor, so when I slide the 4K monitor up, it is aligning the icons on my first monitor but putting them at the resolution that would have them at the top of the 4K monitor, which is higher than the top of the 24" monitor.. if that makes any sense
[11:04] <Spass[m]> (btw, my monitor has 59,9 Hz too, just checked)
[11:06] <Spass[m]> yeah... Xfce, desktop icons and the multi-monitor setup, that is a recipe for some strange things ;)
[11:06] <Spass[m]> at least that's what I see on Xfce forums many times
[11:06] <PoolShark_> yeah it seems so
[11:07] <PoolShark_> one last question... my mouse pointer is huge.. where's the thing to make it normal size?
[11:08] <Spass[m]> you should be able to change its size here - https://docs.xfce.org/xfce/xfce4-settings/mouse#cursor
[11:09] <PoolShark_> ahh yes that did the trick
[11:09] <PoolShark_> thanks!
[11:09] <PoolShark_> okay time to go for a bike ride. thanks for your help!
[11:09] <Spass[m]> glad I could help, have a fun ride
=== xerox123_ is now known as xerox123
=== sorinello1 is now known as sorinello
=== Israphel is now known as Guest34818
=== Israphel_ is now known as Israphel
=== GridCube_ is now known as GridCube
[18:44] <sorinello> Hello. I am trying to install pulseaudio-equalizer on Xubuntu 19.04 64bit, but I get the following error
[18:45] <sorinello> The following packages have unmet dependencies:
[18:45] <sorinello>  pulseaudio-equalizer : Depends: libpulse0 (= 1:12.2-2ubuntu3) but 1:12.2-9~disco1 is to be installed
[18:45] <sorinello>                         Depends: pulseaudio (= 1:12.2-2ubuntu3)
[18:45] <sorinello> E: Unable to correct problems, you have held broken packages.
[18:45] <sorinello> and idea what am I doing wrong ?
[18:58] <brainwash> !ppa
[18:58] <ubottu> A Personal Package Archive (PPA) can provide alternate software not normally available in the offical Ubuntu repositories - Looking for a PPA? See https://launchpad.net/ubuntu/+ppas - WARNING: PPAs are unsupported third-party packages, and you use them at your own risk. See also !addppa and !ppa-purge
[18:58] <brainwash> sorinello: what gives "apt policy libpulse0"?
[18:59] <sorinello> brainwash, https://pastebin.com/aT5ZxJ7Y
[19:03] <brainwash> sorinello: try to downgrade the package via "sudo apt install libpulse0=1:12.2-2ubuntu3"
[19:25] <tomreyn> sorinello: you seem to have had a PPA installed which you since removed, keeping packages from there installed. or you just installed single foreign .deb packages in versions not available in your ubuntu release.
[19:26] <tomreyn> this script can help identify such leftover foreign packages which are 'getting in the way' of the apt dependency resolver: https://github.com/tomreyn/scripts#foreign_packages
[19:27] <sorinello> tomreyn, I have downgraded as brainwash suggested. I will reboot and be back in 3 minutes
[19:28] <usney> <usney> usney> I have an issue with screen lock. When I lock my screen it doesn't respond to commands to wake it up and unlock it.
[19:28] <usney> <usney> <usney> So I have to restart the system
[19:28] <usney> <usney> sorry i forgot not to lock the screen so had to restart again
[19:29] <sorinello> ok, seems that I have lost sound completely now
[19:34] <brainwash> usney: try another screen locker
[19:34] <usney> how?
[19:34] <brainwash> is that xubuntu 19.04?
[19:34] <usney> no
[19:34] <usney> lts
[19:35] <brainwash> so the new xfce4-screensaver is not in the repo yet
[19:35] <Spass[m]> usney: gnome-screensaver or xscreensaver
[19:36] <usney> I'll try the lighter one
[19:36] <Spass[m]> I had some issues with light-locker on LTS on my machines
[19:36] <usney> how do I change it to the default?
[19:37] <brainwash> remove light-locker and install gnome-screensaver/xscreensaver
[19:37] <brainwash> that should set the default
[19:37] <usney> cool
[19:37] <brainwash> after a relog that is
[19:37] <usney> thank you so much
[19:37] <brainwash> or rebbot
[19:39] <Spass[m]> xscreensaver is probably lighter, but... definitely not prettier ;) but it works
[19:43] <usney> yes I guessed so
[19:43] <usney> so I installed that instead