 Does anybody know how to check if my network connection is following the ntp server on my router?
 timedatectl show-timesync will show the current server you are synced to. (re @heysoundude: Does anybody know how to check if my network connection is following the ntp server on my router?)
[13:07] <dsc_> Hello, what does lubuntu use for networking, netplan or systemd-networking?
[13:07] <dsc_> version 20.04
[13:12] <dsc_> I'm asking because my networkig is wrecked, can't get anymore interwebs
[13:12] <dsc_> god knows I love my interwebs
[14:13] <dsc_> So seems like (kernel?) upgrade I recently destroyed my networking
[14:14] <dsc_> With kernel 5.8.0-38 I can't see any drivers under my ethernet controller: Realtek RTL8111/8168/8411 (lspci -k)
[14:15] <dsc_> I downgraded to `5.4.0-60` and now I it actually lists drivers for my ethernet controller:
[14:15] <dsc_> 	Kernel driver in use: r8169
[14:15] <dsc_> 	Kernel modules: r8169
[14:15] <dsc_> and I have networking again
[14:15] <dsc_> :(
[18:19] <david__> hello
[18:20] <david__> do you speak german?
[18:20] <teward> !de
[18:20] <teward> wow you left too quickly xD
[18:27] <Arrow88> hi
[18:28] <Arrow88> I'm burning Gallium to a usb
[18:28] <Arrow88> I tend to prefer debian or lubuntu
[18:29] <Arrow88> I once had a very good setup with lubuntu
[18:29] <Arrow88> Ubuntu too
[18:29] <Arrow88> ...on different machines
[18:29] <Arrow88> This time it's a Chromebook
[18:31] <Arrow88> It will be at work tomorrow
[21:01] <Arrow88> Is anyone used to both Debian and Lubuntu?
[21:04] <Arrow88> Join #debian
 Arrow88: Debian and Lubuntu aren't that much different, but we usually don't ask for people to join other channels
 Debian's support is on OFTC by the way ;)
 not here on Freenode
[21:12] <genii> ..I was going to point this out LOL
[21:13] <Arrow88> I am trying to find the difference between the light running components in Debian versus lubuntu
 genii: where's my coffee
 Arrow88: That's a much more in-depth comparison than you will get on IRC
 because the fundamental components on LXQt Debian and Lubuntu LXQT are different in what is default-installed
[21:13] <Arrow88>  know Ubuntu is derived from Debian
 so you can't compare Apples and Oranges in this case
[21:14]  * Arrow88 googles lxqt
[21:15] <Arrow88> I think I had lxde
 since a while ago, Lubuntu has switched to LXQt
 at least t=he last handful of Lubuntu releases including 20.04 are LXQt now
[21:16] <Arrow88> I see
 not LXDE
 hence the comparison of Apples and Oranges I mentioned
 the lightest Debian desktop install I've had is with their netinst ISO, base Debian utilities (system tools, wget, curl, vim, etc.), and LXQt
 has a similar footprint to Ubuntu Server + Only LXQt, but is fundamentally different under the hood by what network utiltlies are preinstalled, etc.
 (I have a customization script too that minimizes my installs for my VMs and embedded devices, which the Lubuntu Team doesn't endorse)
 but in terms of a direct comparison between the two environments, there's no full documentation/writeup
 because Debian and Ubuntu are at their core fundamentally different
[21:19] <Arrow88> I thought Ubuntu devs was sent update packages directly from debian monthly or weeklyl
[21:19] <Arrow88> it used to be like that
[21:19] <Arrow88> Eitehr way, I guess I just have to try
[21:20] <Arrow88> I shall probably not get that into kernels and under the hood stuff right now
 Arrow88: you're thinking only during the development cycles and ONLY when we have autosync on - there's freezes, etc. that halt syncs
 unlike Debian Unstable, it's *not* a rolling release type situation
 as i said
 fundamental differences
 I was just talking to @kc2bez  in another room and I think there needs to be an option in either OPENBOX or LXQT SETTINGS to where we can turn off that blue outline around active windows. Its really annoying when you're coming from SUSE or Fedora where that is not offered
 PS dont use LXQT SUSE...  It went bonkers on me....
[22:24] <lynorian> I am not quite sure how that is implemented to be honest so not sure where the setting should be
 Dan said its was a featured requested. But there should be a way to turn it on and off in the settings or in OpenBox settings. I think it should go under appearance (re @lubuntu_bot: (irc) <lynorian> I am not quite sure how that is implemented to be honest so not sure where the setting should be)
[22:26] <lynorian> it does make it easier to resize by adding to the edges
 yeah
 See I came from SUSE... and neither it or Fedora ( I was on fedora for like 2 hours Lol) and it was just regular screen edges
[23:12] <wxl> there's no accounting for taste, admittedly
[23:12] <wxl> luckily it's super simple to resize windows without ever even needing to drag
[23:13] <wxl> er, drag screen edges
[23:13] <wxl> same with moving: the window doesn't even need to be on screen
[23:15] <dsc_> Now that there are people around .. `apt upgrade -y` killed my networking, more specifically I cannot see a driver loaded for my ethernet controller under `lspci -k`
[23:15] <dsc_> so I downgraded kernel version grub to get networking working
[23:16] <dsc_> in grub*
[23:16] <dsc_> My question is, what should I do
[23:17] <dsc_> keep using the older kernel? :D
[23:17] <wxl> that's certainly a possible solution
[23:17] <dsc_> then we will do just that
[23:18] <wxl> otherwise i'd investigate the driver itself
[23:18] <wxl> don't you have a realtek chip?
[23:18] <dsc_> I do indeed
[23:18] <dsc_> Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
[23:18] <wxl> yeah they are a never ending source of problems
[23:18] <wxl> i used to think broadcom was bad until i've had to deal with them
[23:18] <dsc_> I cheaped out by buying the most affordable mobo I could find
[23:18] <wxl> at least with broadcom it's pretty straight forward once you get it set up
[23:19] <wxl> what's the pci id? (`lspci -nnk` should give you that at the end of that same line in the form [xxxx:xxxx] where x is an alphanumeric)
[23:19] <wxl> also that should give you not only kernel modules loaded but kernel modules AVAILABLE
[23:20] <wxl> it may simply be an issue of needing to switch over to a new driver
[23:20] <dsc_> [10ec:8168] (rev 15)
[23:20] <wxl> and you're on 20.04?
[23:20] <dsc_> Currently on older kernel:
[23:20] <dsc_>         Kernel driver in use: r8169
[23:20] <dsc_>         Kernel modules: r8169
[23:20] <dsc_> yes, 20.04
[23:20] <wxl> oh oh
[23:21] <dsc_> at least, that's what my desktop wallpaper says ... 20.04
[23:21] <dsc_> :D
[23:21] <wxl> might be worthwhile to flip to the new kernel and see if you get another available module
[23:21] <wxl> lsb_release -a will do the trick
[23:21] <dsc_> 20.04.1 LTS
[23:21] <wxl> k 1s
[23:21] <dsc_> kernel 5.4.0-60
[23:21] <wxl> i'm surprised ethernet is the issue too
[23:22] <wxl> but again, freaking realtek
[23:22] <dsc_> 5.8.0-38 <== causing problems
[23:23] <dsc_> Well, I think it's driver because on this newer kernel, `lspci` does not show me any drivers loaded/listed
[23:23] <dsc_> That's as far as my detective skills goes
[23:24] <wxl> harumph
[23:24] <wxl> searching…
[23:26] <wxl> can you pastebin `lsmod`?
[23:27] <wxl> i'm confused as to how you got 5.8 at all
[23:27] <dsc_> sure
[23:27] <wxl> !info src:linux focal
[23:27]  * wxl kicks the bot
 Everyopne is getting it in 20.04 it seems wxl
[23:28] <wxl> i… don't understand
[23:28] <wxl> https://packages.ubuntu.com/source/focal-updates/linux
[23:28] <wxl> that is clearly not 5.8
[23:28] <dsc_> lsmod: https://paste.centos.org/view/raw/d0f9ccab
 hmm, many are getting the HWE kernel
[23:29] <dsc_> I just ... upgraded my distro ... like a good citizen :D
[23:30] <wxl> i'm kind of at a loss
[23:30] <wxl> there's probably some github repo somewhere with a good driver
[23:30] <wxl> that will then shortly be deprecated
[23:30] <dsc_> [user@box ~ ]$ dpkg -l | grep linux-image | grep "5.8"
[23:30] <dsc_> ii  linux-image-5.8.0-38-generic                  5.8.0-38.43~20.04.1                   amd64        Signed kernel image generic
[23:30] <wxl> i've seen a number of similar issues along those lines lately
[23:31] <wxl> hey i believe you, i just don't understand how
 Exactly, there have been a bunch.
[23:31] <dsc_> https://paste.centos.org/view/raw/1319022b
[23:31] <wxl> either way, it's a *buntu problem not a lubuntu one
[23:31] <dsc_> ah ok
[23:31] <dsc_> fair enough
[23:31] <wxl> meaning it should affect every flavor
[23:31] <dsc_> cool cool
 I think it is.
 I have seen some issues in Ask Ubuntu too I think.
[23:32] <dsc_> Nobody has reported about it here because they can't connect to IRC
[23:32] <dsc_> (joke)
 I think someone did have this issue here over the weekend maybe.
[23:33] <wxl> ok so here's looking at your #1 repo, the nl mirror
[23:34] <wxl> here's 5.4 in the focal repo https://nl.archive.ubuntu.com/ubuntu/dists/focal/main/signed/
[23:34] <dsc_> wtf?
[23:34] <wxl> ah but the 5.8 hwe in updates https://nl.archive.ubuntu.com/ubuntu/dists/focal-updates/main/signed/
 I was just going to say, I think HWE is on for desktop by default.
[23:35] <wxl> and yet that's not what appears to be on packages.u.c
[23:35] <wxl> i never really pay attention but are HWEs always or even often new versions?
[23:36] <wxl> @teward001 oh core dev you have any thoughts on this mess?
 He was griping about it the other day, so yes.
[23:36] <wxl> i see :(
 HWE kernels are usually newer kernels, yes.
[23:37] <wxl> sorry i don't have better news for you, dsc_. i'd stick with the older kernel for now
[23:37] <dsc_> no problem at all
[23:37] <dsc_> thanks for the help
[23:37] <wxl> it may be worth filing a bug against the kernel
 Absolutely, if there already is one you can add some heat.
[23:38] <wxl> yeppers
[23:38] <wxl> in fact let's see what the hot bugs are…
[23:38] <dsc_> where does one partake in such blackmailing?
[23:39] <wxl> hm that's not very telling
[23:39] <dsc_> bugzilla.kernel.org?
[23:39] <wxl> but hold onnnnn
[23:40] <wxl> nope just do `ubuntu-bug linux`
[23:40] <dsc_> ah
[23:40] <wxl> aren't these the hwe bugs??? https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=kernel-stable-tracking-bug&orderby=-id&start=0
[23:41] <wxl> that last one for the focal (20.04) 5.4.90 update is 2 hours old!
[23:41] <wxl> i'm really confused about how 5.8 is there
[23:42] <wxl> in fact that's kind of driving me batty
[23:42] <wxl> https://launchpad.net/ubuntu/+source/linux
[23:42] <dsc_> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655
[23:42] <wxl> 5.8 exists in groovy and hippo
[23:43] <wxl> dsc_: you have that same dmsg error?
[23:44] <wxl> also baffled at that one as it's supposedly focal and 5.8
[23:44] <wxl> OH interesting https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655/comments/5
[23:44] <dsc_> I do not have that same message in /var/log/dmesg or /var/log/kern.l .... wait I'm on the old kernel right now :P
[23:44] <dsc_> ah, right
[23:45] <wxl> dsc_: don't worry, i understand your confusion. sometimes i think i'm drowning in vms. XD
[23:45] <dsc_> yeah happens :P
[23:46] <dsc_> Well, this report sounds like my problem
[23:46] <wxl> if you've got the dmesg bit, it probably is
[23:46] <dsc_> same ethernet controller, same symptons
[23:47] <dsc_> ill reboot and check
[23:53] <wxl> ah HA so i'm not crazy after all. hwe is a separate package https://packages.ubuntu.com/source/focal/linux-hwe-5.8
[23:56] <wxl> and HWE's are installed by default with LTSs (like focal) so they keep rolling over
[23:56] <wxl> i think i discovered this at one time but forgot XD
[23:57] <wxl> server defaults to the standard kernel, tho
[23:57] <dsc_> ic
[23:57] <dsc_> Well, I could not find "the message"
[23:58] <wxl> then you may have a different issue
[23:58] <wxl> like similar but different
[23:58] <dsc_> right
 I think I knew it was separate but it hasn't always been enabled by default. I think this is the first LTS where it is. (re @lubuntu_bot: (irc) <wxl> and HWE's are installed by default with LTSs (like focal) so they keep rolling over)
[23:58] <wxl> it looks to me in that case the card is detected and a driver is used, but it's problematic
[23:59] <dsc_> Ah yes, that output does show a driver loaded
[23:59] <dsc_> I don't have that
[23:59] <dsc_> Anyway, older kernel is fine