[02:05] <lotuspsychje> good morning
[09:38] <lotuspsychje> !next
[09:40] <luna_> 23.10 development has not started yet for another couple of weeks
[09:41] <lotuspsychje> wont be long luna_ 
[09:42] <lotuspsychje> toolchain follows up pretty quickly these days
[09:42] <luna_> yeah about 1,5-2 weeks
[09:42] <ice9> if I want to use ubuntu-bug to report an issue with bluetooth, which package to provide?
[09:43] <lotuspsychje> ice9: bluez maybe
[09:44] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/bluez/+bugs?orderby=importance&start=0
[15:12] <ice9> I'm confused, what's the difference between the driver and the linux-firmware?
[15:43] <leftyfb> ice9: my understanding is that linux-firmware loads firmware for devices into memory as opposed to firmware that gets flashed to the device. I might be oversimplifying or even wrong
[21:03] <Jeremy31> leftyfb: some firmware gets loaded into hardware
[21:03] <Jeremy31> ice9: What is the issue with Bluetooth?
[21:04] <daftykins> oy it's like softmodems all over again
[21:05] <daftykins> :)
[21:05] <Jeremy31> Power off the device and the firmware clears
[21:07] <daftykins> not really firmware anymore, then
[21:10] <Jeremy31> Not a permanent thing like flashing a BIOS update
[21:11] <daftykins> ugh i was improving some silly Dell all-in-one computers at a client today, dust clearing and thermal paste reapplication... ahead of a RAM upgrade... and saw my predecessor had installed the OS as legacy with secure boot off and TPM off
[21:11] <daftykins> what amateurs
[21:30] <ice9> Jeremy31, can't enable bluetooth in gnome settings nor in blueman-manager
[21:30] <ice9> blueman-manager 23.30.04 ERROR    Manager:147 on_dbus_name_appeared: Default adapter not found, trying first available.
[21:30] <ice9> blueman-manager 23.30.04 ERROR    Manager:151 on_dbus_name_appeared: No adapter(s) found, exiting
[21:30] <ice9> this happened right after upgrade from 23.04
[21:30] <Jeremy31> ice9: post URL from terminal for>  (lsusb; dmesg | egrep -i 'blue|firm')|nc termbin.com 9999
[21:31] <ice9> Jeremy31, https://termbin.com/jpyo
[21:33] <Jeremy31> ice9: What kernel?
[21:33] <ice9> Jeremy31, 6.2.0
[21:35]  * daftykins walks outside the channel and checks the name above the door
[21:36] <Jeremy31> ice9: File a bug against package linux as it is a kernel issue
[21:36] <ice9> Jeremy31, how are sure it's the kernel not the driver or the firmware?
[21:38] <Jeremy31> ice9: Because the kernel is responsible for loading correct firmware, that chipset might need a flag in btusb because of this error "Failed to read MSFT supported features (-110)"
[21:50] <Jeremy31> ice9: you could try copying https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel/ibt-19-0-4.sfi into /lib/firmware/intel/ and do a reboot as that is the newest version
[21:52] <ice9> Jeremy31, I already installed this https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git but didn't help
[21:52] <ice9> I mean I installed all firmware there
[21:53] <Jeremy31> So you have the latest/greatest firmware that Intel has made available
[21:54] <daftykins> maybe TJ's old ACPI OSI trickery could be worth a go?
[21:54] <daftykins> for fun if nothing else
[21:55] <ice9> Jeremy31, maybe I install the old firmware that was on 22.10?
[21:55] <daftykins> although perhaps support should be pursued in support channels y'know, just saying...
[21:55] <Jeremy31> ice9: Did you try it on 22.04?
[21:55] <ice9> Jeremy31, 22.04 and 22.10 was working fine
[21:56] <Jeremy31> So it must be the kernel