[16:55] <David_Hedlund> apt-get update is working fine. But I'm curious to learn why I cannot install transitional snap packages. Please see http://rafb.ath.cx/pastes/pdwlB657.html JanC
[16:55] <David_Hedlund> This is for Ubuntu Server, not Ubuntu
[16:57] <leftyfb> David_Hedlund: sudo snap install firefox   # and: sudo snap install chromium-browser
[16:57] <leftyfb> David_Hedlund: also, looks like you have a broken dpkg somewhere with the instructions on how to resolve it right in your paste
[17:04] <David_Hedlund> leftyfb: I didn't have any broken dpkg packages before I executed this (verified with a VM).
[17:05] <leftyfb> David_Hedlund: fix the broken package and install firefox and chromium using the commands I posted above
[17:27] <David_Hedlund> leftyfb: Solved with `sudo apt --fix-missing update`  -- Thanks
[17:28] <leftyfb> David_Hedlund: just curious why you didn't follow the instructions in your pastebin?   sudo dpkg --configure -a
[17:31] <David_Hedlund> leftyfb: I added that text, it's relevant if you cancel the apt-install by shutting down in the middle of the process for example
[20:58] <webchat2> Hi there. I'm having an issue with my MS Bluetooth mouse, it disconnects after a while and will not connect, only rebooting will take care of it.
[20:59] <webchat2> With that being said, I have no idea on what is causing it to be honest. Has anyone ever dealt with this issue before?
[21:12] <webchat2> jeremy31: Aight, will reboot now.
[21:17] <webchat2> Just rebooted, after like 1 minute it disconnected again.
[21:17] <tomreyn> webchat2: some background info on what you just did: "btusb" is a kernel module, not a command you can run. kernel modules do have parameters you can pass to them, though, to make them work differently. the "modinfo -p btusb" command would list those of the "btusb" module, for your current kernel. kernel module options are applied while the module is loaded (called "module probing", i.e. "modprobe"), and placing them in /etc/modprobe.d is a way
[21:17] <tomreyn> to do so. passing them on the kernel command line is another (type "!kernelparm" here for more info on that).
[21:18] <webchat2> !kernelparm
[21:18] <jeremy31> webchat2: using wifi too?
[21:19] <webchat2> Yes, I happen to be using Wi-Fi as well.
[21:19] <jeremy31> Might need to change Bluetooth coexistence parameter of the wifi module
[21:21] <jeremy31> webchat2: post URL from terminal for>  lsmod|grep cfg|nc termbin.com 9999
[21:24] <webchat2> jeremy31: https://pastebin.com/t6kAHM8D
[21:24] <webchat2> That's from lsmod.
[21:27] <jeremy31> webchat2: try> echo "options options iwlwifi bt_coex_active=0"| sudo tee /etc/modprobe.d/iwl.conf
[21:28] <webchat2> Aight. Rebooting again.
[21:28] <tomreyn> you have "options" twice there
[21:29] <jeremy31> I hate doing things on my phone
[21:31] <tomreyn> you need nokia 9000 communicator
[21:32] <webchat2> jeremy31: Now the mouse doesn't even work.
[21:33] <jeremy31> 4:27 PM <jeremy31> webchat2: try> echo "options iwlwifi bt_coex_active=0"| sudo tee /etc/modprobe.d/iwl.conf
[21:33] <webchat2> Aight.
[21:34] <tomreyn> webchat2: there was a typo in the command jeremy last provided, it said "options options". this ^ fixed command will correct it.
[21:34] <webchat2> Rebooting.
[21:37] <webchat2> jeremy31: It's working now, but oddly enough the mouse pointer is more sensitive now.
[21:37] <webchat2> Just made a few adjustments, now to see if it will disconnect.
[21:38] <jeremy31> webchat2: if anything goes wrong just delete the iwl.conf and reboot
[21:38] <webchat2> Alright.
[21:38] <webchat2> Btw, I've been getting some odd error messages, but not sure if they are related.
[21:39] <webchat2> It's usually right when I log in.
[21:41] <jeremy31> webchat2: if you find them paste them to paste.ubuntu.com and just post URL here
[21:41] <webchat2> Is there any folder where they are saved to?
[21:42] <jeremy31> webchat2: likely /var/log/syslog
[21:45] <tomreyn> likely /var/log/journal nowadays - use the "journalctl" command to view them
[21:45] <webchat2> Jeremy31 Found it, but it's... a lot of information. Too much in fact.
[21:45] <tomreyn> or just "dmesg" for only kernel messages
[21:48] <webchat2> Odd, it shows some logs, but from 12th May.
[21:48] <tomreyn> journalctl -b -p3    should list errors logged since boot
[21:48] <tomreyn> journalctl -b -p4    should list warnings and errors logged since boot
[21:50] <webchat2> https://pastebin.com/3BZF3fYB
[21:50] <webchat2> Used p4
[21:54] <tomreyn> if you want to share the output, use    journalctl -b -p4 | nc termbin.com 9999
[21:54] <ravage> i see that there is a missing firmware file
[21:54] <ravage> could that be a problem?
[21:54] <webchat2> I have no idea on what is missing.
[21:55] <oerheks> MDS CPU bug present and SMT on, data leak possible. This vulnerability was fixed by 20190514 update of microcode
[21:55] <ravage> if yes then here somoneone built a .deb with them https://github.com/winterheart/broadcom-bt-firmware/releases
[21:55] <webchat2> That would be a chipset firmware update, right?
[21:55] <oerheks> no, intel microcode
[21:56] <ravage> i dont think that affects his BT but could be a good idea to get that latest update too
[21:56] <webchat2> Where would I get that? I doubt Dell has Linux drivers.
[21:56] <tomreyn> "kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)"
[21:56] <ravage> webchat2: sudo apt -y install intel-microcode
[21:57] <ravage> but that should be installed
[21:57] <webchat2> ravage: Correct, it is.
[21:57] <ravage> maybe install that .deb on github. it includes the file that is missing
[21:58] <ravage> for your BT firmware
[21:59] <jeremy31> webchat2: in terminal> cd /lib/firmware/brcm && sudo wget https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM20702A1-413c-8197.hcd
[22:00] <ravage> ok. the single file is a good idea too of course :)
[22:01] <webchat2> jeremy31: Is that all I have to do to install the update=
[22:01] <webchat2> ?
[22:01] <ravage> yes
[22:01] <webchat2> Rebooting, brb.
[22:01] <jeremy31> That will get the firmware but you will need to reboot
[22:02] <ravage> ^^
[22:02] <jeremy31> Strange having Intel wifi and Broadcom Bluetooth unless it is a dongle
[22:03] <tomreyn> driver was "btusb"
[22:03] <tomreyn> so i assume that's a dongle, probably
[22:13] <webchat2> Uh, this is awkward. The error messages disappeared alright. But now the Bluetooth Manager won't open.
[22:16] <jeremy31> webchat2: URL from terminal for>  sudo dmesg | egrep -i 'blue|firm' | nc termbin.com 9999
[22:17] <webchat2> https://termbin.com/bdvgl
[22:18] <ravage> it somehow does not like that firmware patch
[22:18] <jeremy31> webchat2: Lets get rid of it> sudo rm /lib/firmware/brcm/BCM20702A1-413c-8197.hcd
[22:18] <jeremy31> then reboot
[22:19] <webchat2> Rebooting.
[22:19] <ravage> do we have a lsbusb output somewhere?
[22:21] <jeremy31> ravage: I bet it shows ID 413c:8197
[22:22] <webchat2> Back. Now it opened, but couldn't interact with the window, and an error messaged showed up that BlueZ failed.
[22:23] <jeremy31> webchat2: Is it a Bluetooth dongle?  If it is, unplug for a couple seconds, then put it back in
[22:23] <webchat2> No, it is a module.
[22:23] <jeremy31> Internal then?
[22:24] <jeremy31> Must be an older HP
[22:24] <ravage> on what kernel version are you? maybe it was somewhere mentioned
[22:24] <ravage> i think its a dell
[22:25] <Miles8of9> i'm running command "sudo modprobe i2c-dev"... i'm getting a new prompt below, no error, nothing... Running "lsmod | grep i2c" shows no i2c-dev loaded
[22:25] <Miles8of9> why?????
[22:27] <jeremy31> Miles8of9: That is because i2c-dev is built into the kernel and not as a module
[22:28] <Miles8of9> ah ok
[22:28] <Miles8of9> OpenRgb complains no i2c-dev module is loaded
[22:29] <jeremy31> Miles8of9: Check in terminal>  modinfo i2c-dev
[22:29] <Miles8of9> builtin...
[22:44] <ottosch> I have a PC which was working fine until a couple days ago, but now has network issues. I can't ping the router or 8.8.8.8 for example ("Destination Host Unreachable")
[22:44] <ottosch> how can I fix it?
[22:45] <jeremy31> ottosch: Start with a router reboot
[22:45] <webchat2> ravage: Correct.
[22:45] <webchat2> A Dell Latitude E6330 to be more precise.
[22:46] <ottosch> jeremy31: I can't do that at this specific moment (maybe in half an hour). Is it possible it's a router issue with this specific pc?
[22:47] <jeremy31> ottosch: The pc may have received bad info from the router
[22:47] <ottosch> jeremy31: ok, I'll try that soon
[22:52] <webchat2> ravage: Correct
[22:53] <webchat2> ravage: Err, the kernel is 5.19.0-41-generic
[22:57] <webchat2> Well, my shift is about to end. Thanks for the help anyways, I'll see how it goes from here.
[23:49] <ottosch> jeremy31: hey man, I restarted the router and still can't ping anything. Got any other suggestion?
[23:52] <ottosch> Ubuntu server can't ping router, 8.8.8.8, nothing
[23:53] <sarnold> what error message do you get?
[23:53] <oerheks> is this bare metal install, or vm?
[23:53] <sarnold> does ip r  output look right? ip a ?  unexpected messages in dmesg? do you have link light on both ends?
[23:56] <ottosch> sarnold: oerheks: Destination Host Unreachable.
[23:57] <ottosch> bare meta install (mini pc)