[00:00] <Guest72> TJ- I'll admit this sounds pretty risky for me, all things considered. I know my chances of solving this issue might be diminished if I don't do this, but can I forego this step for now?
[00:01] <TJ-> Guest72: of course!
[00:01] <TJ-> Guest72: just keep it in mind that it may be having knock-on effects
[00:02] <Guest72> TJ- I'll be sure to keep this in mind. Thanks!
[00:03] <TJ-> check that bluetooth.service log
[00:03] <Guest72> TJ- I have the pastebin for the Bluetooth related pastebin, if it serves anything: https://paste.ubuntu.com/p/3b23dRtjCB/
[00:05] <TJ-> Guest72: hmmm, rather ... empty!
[00:05] <TJ-> Guest72: but it looks OK - no errors!
[00:06] <TJ-> Guest72: so now instead of using GUI tools lets use the command-line tooling to check for BT devices
[00:06] <TJ-> Guest72: do "bluetoothctl" and you'll be inside a Bluetooth-specific command-line tool
[00:07] <Guest72> TJ- Will it work for finding my bluetooth mouse? I'm mostly asking since I think I read that bluetoothctl requires a certain kind of parameter to pair it.
[00:07] <Guest72> TJ- Regardless, I typed bluetoothctl, now.
[00:07] <TJ-> now type "help" to see the range of commands
[00:07] <TJ-> that's so you get a feel for what is available
[00:08] <Guest72> TJ- Alright, I'm checking the commands.
[00:08] <TJ-> then type "list" and you should see a message about the current controller(s)
[00:08] <TJ-> E.g. I see "Controller E8:6F:38:D4:32:8A elloe000 [default]"
[00:10] <Guest72> I see "Controller 60:6D:C7:E5:61:84 comodoro64-HP-Pavilion-Notebook [default]" myself.
[00:10] <TJ-> Good!
[00:11] <TJ-> now "devices" will list any devices already known
[00:11] <Guest72> As in previously paired?
[00:11] <TJ-> not necessarily paired, but known/connected
[00:12] <TJ-> "paired-devices" will list those
[00:12] <Guest72> I see. So I should just type "devices" if I want to pair my Bluetooth mouse for the first time?
[00:13] <TJ-> no
[00:14] <TJ-> "agent on"  then "default-agent" then "scan on"
[00:14] <TJ-> put your other device into pairing mode
[00:14] <Guest72> Alright, then. I'm going to do that, now.
[00:14] <TJ-> you should see it reported by its MAC address
[00:15] <TJ-> then you can do "pair AA;BB:CC..." where those are the actual MAC address. Luckily you only need to type the first couple of characters because it will tab-complete if you press Tab key
[00:15] <Guest72> That's great! I'll see if I have any luck.
[00:17] <TJ-> if pairing works, then do "trust AA:BB:CC..." and finally "connect AA:BB:CC..."
[00:18] <Guest72> I think I'm definitely having no luck at all.
[00:21] <TJ-> are you seeing your device after doing "scan on"
[00:23] <Guest72> None at all, unfortunately.
[00:23] <TJ-> OK, do "quit" to return to the shell
[00:24] <TJ-> then lets see if that has caused any errors " journalctl -k -n 50 | nc termbin.com 9999 "
[00:26] <Guest72> Here's the requested pastebin: https://termbin.com/44ar
[00:26] <Guest72> I have the feeling I should probably do the process again. I admittedly had to do other things on my laptop during this troubleshooting process.
[00:27] <TJ-> no indications of BT errors there
[00:33] <Guest72> That's strange... Although I did try to go to bluetoothctl again to do the whole process of enabling the default agent and scanning then quitting and generating the log again, and the same text appears.
[00:35] <TJ-> yes, the log hasn't changed - read the timestamps :)
[00:36] <TJ-> Guest72: so as the 'scan on' doesn't see any devices (assuming you've put them into pairing mode and they're close to the PC) it looks like there's a fault.
[00:36] <Guest72> @TJ
[00:36] <Guest72> TJ- Indeed, it seems. It's unfortunate.
[00:36] <TJ-> one such that I have seen before is the bluetooth antenna detached internally, but these days its usually the same antenna as the wifi, so if wifi is good you can usually rule that out
[00:37] <TJ-> but its worth testing that by putting the to-be-paired device right up against the top of the laptop screen which is where the antennas usually are placed (either side of the webcam lens)
[00:38] <Guest72> TJ- I'll try that. Thanks!
[00:39] <TJ-> combined with your 1-6 usb device failure I do think there is an internal fault of some sort though
[00:41] <Guest72> TJ- Indeed. I'll have to assess whether it's worth to disassemble the laptop and test detaching those components. Nevertheless, I appreciate your given help!
[00:44] <TJ-> Guest72: before doing that a good idea would be to do some web searches with the exact model number of your laptop for anyone else using Linux and experiencing similar USB device failures/BT issues. One thing to bear in mind is the BT chipset is broadcom and they have a poor reputation. It could be a wrong/bad firmware file is being loaded into that BT device also oso lookupt for mentions of
[00:44] <TJ-> alternate bluetooth firmware files
[00:45] <TJ->  usb 1-7: Product: BCM43142A0
[00:45] <TJ-> Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[00:45] <TJ-> Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd'
[00:45] <TJ-> Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd'
[00:47] <TJ-> Actually, that's it! I cannot find either of those listed by "apt-file search"
[00:48] <TJ-> Guest72: I think we have it !
[00:48] <TJ-> Guest72: are you there?
[00:49] <Guest72> TJ- Wait, really?!
[00:49] <Guest72> Yeah, I'm here!
[00:49] <TJ-> OK, try this:
[00:49] <TJ-> "sudo -i"   then "cd /lib/firmware/brcm"
[00:50] <TJ-> then download this firmware file with "wget https://raw.githubusercontent.com/winterheart/broadcom-bt-firmware/master/brcm/BCM43142A0-0a5c-216d.hcd "
[00:50] <TJ-> This is https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-0a5c-216d.hcd
[00:51] <Guest72> Alright, I applied the wget command for that link as root.
[00:51] <TJ-> once that is in place we'll unload and reload the BT module(s)
[00:52] <TJ-> but first show me which are loaded with "lsmod | grep btusb | nc termbin.com 9999"
[00:52] <Guest72> Alright! On it!
[00:52] <Guest72> Here's the pastebin: https://termbin.com/wq40
[00:54] <TJ-> good, it's got nothing holding in memory. "modprobe -r btusb" then reload it with "modprobe btusb" then show me the kernel log with "journalctl -k -n 50 | nc termbin.com 9999"
[00:55] <Guest72> Alright! Here's the next pastebin: https://termbin.com/6y3nv
[00:55] <TJ-> Looks great! use your GUI tooling to search for devices!!
[00:55] <TJ-> I've pretty sure now it'll work
[00:56] <Guest72> Fingers crossed! 🤞
[00:56] <Guest72> Oh, wow!
[00:56] <Guest72> It works, now!
[00:56] <TJ-> :)
[00:57] <Guest72> TJ- Huuuuuge thanks! You saved me from lamenting the need to fill the few USB ports of my laptop! 😁
[00:57] <TJ-> always a problem with Broadcom devices because their firmware is not licenced for distribution so often can't be in the archives, as here
[00:57] <Guest72> Actually, not only that! I've noticed that the bluetooth adapter no longer disconnects my mouse for a weird few seconds, too!
[00:58] <Guest72> TJ- Yeah, I can imagine. That's unfortunate, though I also guess my laptop model wasn't that popular to begin with.
[00:58] <TJ-> kernel now reports "Bluetooth: hci0: BCM43142A0 'brcm/BCM43142A0-0a5c-216d.hcd' Patch"
[00:58] <Guest72> Oh! Great! So that'll be ready for future Kubuntu updates for other users?
[00:58] <TJ-> Bluetooth: hci0: BCM43142A0 Generic USB Class 2 NonUHE @ 20 MHz
[00:58] <Guest72> I was about to ask if I needed to fill in a report myself ^^;
[00:59] <TJ-> unfortunately that firmware can't be distributed - which is why we have to find it individually
[00:59] <Guest72> I see. Well, it's definitely something to keep in mind, I think.
[01:00] <TJ-> keep a note of where it came from, and how to reinstall it, in case you ever need that info again!!
[01:00] <Guest72> I apologize if I'm a beginner to this libera chat thing, but may I ask if there's a way to export this chat log from the web version of this site?
[01:03] <TJ-> I'm not sure if this channel gets logged
[01:03] <TJ-> oh, topic says it is
[01:04] <Guest72> I see. I'm mostly asking since, as my username suggests, I'm inside this chat as a guest.
[01:04] <TJ-> Guest72: https://irclogs.ubuntu.com/latest/%23kubuntu.txt
[01:04] <Guest72> Great! Thank you very much!
[01:04] <TJ-> Guest72: better link https://irclogs.ubuntu.com/2021/09/13/%23kubuntu.txt
[01:04] <Guest72> Next time I have an issue, I'll try to better learn to operate Libera Chat, regardless.
[01:05] <TJ-> latter link is for this date, the first was a rolling 'latest'
[01:05] <Guest72> TJ- Good!
[01:06] <Guest72> For now, I once again express my gratitude for this help! I'll be sure to tell others I might know who might share my issue with this exact BCM43142 module of this solution, too.
[01:08] <TJ-> I'd best get some sleep; 02:06 here!
[01:08] <Guest72> TJ- Oof! Pretty late, indeed!
[01:08] <Guest72> Have a nice sleep and a nice new week!
[01:20] <guiverc> thanks too TJ- ; I didn't know there was a 'latest' irclog
[01:40] <druid> wowzie
[01:40] <druid> no one here
[01:40] <druid>  :3
 Does anyone use portmaster? How to disable filtering for an app (kdeconnectd). Sorry if it is OT.
[11:56] <thelounge38> hi
[12:49] <BluesKaj> Hi folks
[15:57] <Mekaneck> thelounge38: as a told you before:  if you have a Kubuntu supportquestion just ask. Offtopic chat is in #kubuntu-offtopic.
[15:58] <Mekaneck> and if you don't want to listen just drop it and move on
[16:37] <kubuntu> Hello, could somebody help me to get my encrypted intel raid1 at / booting again? when booting  I get "waiting for encrypted device". I come not to the prompt where I can enter my passphrase. What Ive allready tried was chroot into from live session, where iam currently on and update-initramfs had runned without any errors, but the problem not to find the encrypted volume still resist.
[17:05] <TJ-> kubuntu: is that MD RAID1 + LUKS on top ?
[17:22] <kubuntu> TJ yes
[17:23] <kubuntu> from live session, encryption works fine.
[17:25] <kubuntu> thing problem is, that after changing HDD2 and rebuild raid in windows, the raid got new name in linux it seems.
[17:27] <kubuntu> the windows is as dual boot on none encrypted hdd separately
[17:29] <kubuntu> could be ignored in that context. The dual boot works properly as long the raid was not rebuilt
[17:36] <kubuntu> TJ I think its md raid1. an intel rst controller onboard. Have read thats similar to software raids
[18:08] <kubuntu> TJ-