[00:21] <rtpg> The previous issue I mentioned above is still happening (where Terminal windows just pop out of existence after a split second), I also saw an issue with like... the desktop icons kinda spawning in and out of existence a bunch sometimes. 
[00:21] <rtpg> Thinking this is a Gnome issue, gonna try building gnome-terminal from source with .... debug stuff up to see what's up
[05:07] <atari2600a> I still say you assholes should fix the framebuffer_depth=24 glitch in weston/mesa20.3
[05:07] <atari2600a> *on the pi
[05:07] <atari2600a> & FFS, make it the default
[05:07] <atari2600a> this isn't raspbian
[05:08] <atari2600a> this isn't a browse wikipedia & run scratch operating system, this is UBUNTU
[05:08] <atari2600a> it's been 24 hours & I'm already tired of looking at 16-bit text anti-aliasing.  It's like I installed windows vista on a pentium III.
[05:09] <atari2600a> hell not even that because a pentium III would have a TNT2 or VIA, & the CRT would anti-alias itself
[05:36] <tomreyn> atari2600a: your language seems broken
[06:01] <linuxuser95> Hello I have two bad problems on Hirsute Hippo beta.
[06:03] <linuxuser95> 1. Bluetooth won't work on Ice Lake U with wifi 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30)
[06:03] <linuxuser95> and 2. USB-C DisplayPort monitor won't accept set refresh rate in GNOME WAYLAND. It shows 99hz, but when I set it: it flashes and then doesn't change the refresh rate. Then gnome erases the refresh rate selection menu from the display in display settings.
[06:07] <linuxuser95> How do I submit a bug report?
[06:08] <linuxuser95> I had the display problem on Fedora 34 beta but they patched it unlike in Ubuntu.
[06:22] <atari2600a> just saying, not the only one here with a weston issue
[06:24] <atari2600a> don't get me wrong I'm not anti-weston
[06:24] <atari2600a> I love wayland
[06:24] <rtpg> maybe you could pipe this energy into writing out bug reports, patches etc
[06:24] <atari2600a> x was the final crux that kept linux from the gamersphere.  you can't have 60fps if you can't 'have' 60fps
[06:24] <atari2600a> bruh
[06:24] <atari2600a> I tried
[06:24] <atari2600a> your shit is locked down worse than MS
[06:25] <atari2600a> they're trying to kill you off don't you see!?
[06:25] <atari2600a> & when I finally do get in contact with a ubuntu dev, you know what they told me?
[06:25] <linuxuser95> I dunno, it works fine in fedora
[06:25] <atari2600a> they told me to fuck off because they won't fix an issue without cash
[06:25] <atari2600a> *EXACTLY*
[06:26] <rtpg> like you sent in a patch and they're like "we won't merge without money"?
[06:26] <linuxuser95> that seems fair tbh
[06:26] <atari2600a> bruh, I can't even access launchpad anymore
[06:26] <atari2600a> the shit's locked down
[06:26] <atari2600a> otherwise I'd issue a weston bug report
[06:26] <linuxuser95> weston sounds like a cool guy
[06:27] <atari2600a> they expect you to use this in-OS ubuntu-bug shit & fucking scour it's man page for the right options to manually specify what you're trying to report
[06:27] <atari2600a> yeah weston doesnt afraid of anything
[06:27] <linuxuser95> I dunno even how to report this bug tho
[06:27] <linuxuser95> lsusb, lspci wont show bluetooth
[06:27] <linuxuser95> but like, its an intel wifi
[06:28] <linuxuser95> there is 100% a driver
[06:28] <atari2600a> it might be on another bus
[06:28] <atari2600a> can wifi interface through spi or some weird shit?
[06:28] <linuxuser95> that sounds freaky
[06:28] <linuxuser95> what else should I try lol
[06:28] <linuxuser95> Bluetooth is handled by Pipewire now right?
[06:29] <atari2600a> bluetooth should show up as it's own block device, even if it's on the sort of GMS-lasered-out-baseband
[06:29] <atari2600a> wait you said intel
[06:29] <linuxuser95> Yeah
[06:29] <atari2600a> yeah no they were forced to take that GMS shit off die due to litigation
[06:30] <atari2600a> just out of curiosity
[06:30] <atari2600a> you didn't reset the cmos did you?
[06:30] <linuxuser95> 00:00.0 Host bridge: Intel Corporation Ice Lake-LP Processor Host Bridge/DRAM Registers (rev 03)
[06:30] <linuxuser95> 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07)
[06:30] <linuxuser95> 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
[06:30] <linuxuser95> 00:07.0 PCI bridge: Intel Corporation Ice Lake Thunderbolt 3 PCI Express Root Port #0 (rev 03)
[06:30] <linuxuser95> 00:07.1 PCI bridge: Intel Corporation Ice Lake Thunderbolt 3 PCI Express Root Port #1 (rev 03)
[06:30] <linuxuser95> 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03)
[06:30] <linuxuser95> 00:0d.2 System peripheral: Intel Corporation Ice Lake Thunderbolt 3 NHI #0 (rev 03)
[06:30] <atari2600a> it's entirely possible it could be disabled in firmware
[06:31] <atari2600a> lol you're muted
[06:31] <atari2600a> anyways, you sure it's not device 00:04.0?
[06:32] <atari2600a> thur you go
[06:33] <atari2600a> use pastebin next time jeez
[06:33] <linuxuser95> I saw that in the corner of my eye
[06:33] <linuxuser95> hmm
[06:34] <linuxuser95> oh wait
[06:34] <atari2600a> too late leaving for drinking byeee
[06:35] <linuxuser95> k bye
[06:35] <linuxuser95> maybe I ought to check bios
[06:40] <linuxuser95> its enabled
[06:41] <linuxuser95> it shows up in lshw under 4:usb
[06:41] <linuxuser95> https://paste.ubuntu.com/p/3Z9jwBdyVt/
[06:42] <linuxuser95> so then the question is why tf doesn't it work
[06:43] <linuxuser95> if I go into gnome-settings
[06:43] <linuxuser95> it just says "BlueTooth Turned Off"
[06:43] <linuxuser95> but then if I toggle the on/off button nothing happens
[06:55] <rtpg> you seeing anything in logs/journalctl?
[07:03] <linuxuser95> Apr 04 21:34:54 linux1 bluetoothd[737]: Failed to set mode: Blocked through rfkill (0x12)
[07:03] <linuxuser95> Apr 04 21:34:54 linux1 bluetoothd[737]: Failed to set mode: Blocked through rfkill (0x12)
[07:08] <linuxuser95> https://paste.ubuntu.com/p/F8n72kCbJJ/
[07:08] <linuxuser95> I've used rfkill before but I can't remember that much
[07:09] <linuxuser95> but like why is it blocked, or is that even an issue :S
[07:10] <linuxuser95> They're not blocked..
[07:10] <linuxuser95>  1 bluetooth ideapad_bluetooth unblocked unblocked
[07:10] <linuxuser95>  2 bluetooth hci0              unblocked unblocked
[07:10] <rtpg> I mean.... I don't know anything about rfkill but that error message + 30 seconds with google makes me think that there's something set up
[07:10] <linuxuser95> rfkill basically hard or soft blocks radio stuff
[07:10] <linuxuser95> iirc
[07:11] <linuxuser95> so like you can turn off  wifi
[07:12] <rtpg> maybe it was set up at boot but not anymore? like if you restart the bluetooth service now maybe you can get through
[07:12] <linuxuser95> that did it
[07:13] <rtpg> might be an ordering thing or ... something. I imagine other people might end up getting issues here tho
[07:13] <linuxuser95> I restarted the service lol and my bluetooth window that I had side to side in gnome started looking for signals
[07:13] <linuxuser95> my next best option was going to be manually connecting but eugheugheugh thats a pain
[07:14] <rtpg> I mean I imagine you wouldn't actually be able to connect manually
[07:14] <linuxuser95> Not sure, I know with wifi you can
[07:14] <linuxuser95> Yeah lol it works fine
[07:15] <linuxuser95> thats so weird
[07:15] <linuxuser95> That must be a bug for sure
[07:15] <linuxuser95> okay I take that back
[07:16] <linuxuser95> it doesn't work once you try and pair
[07:16] <linuxuser95> and its dead
[07:20] <linuxuser95> journalctl has lots of errors
[07:20] <linuxuser95> https://paste.ubuntu.com/p/gMbk2ntQyz/
[07:20] <linuxuser95> Apr 05 00:16:11 linux1 gnome-control-c[6379]: Setting up /org/bluez/hci0/dev_F4_05_8B_61_72_1C failed: GDBus.Error:org.bluez.Error.InProgress: In Progress
[07:20] <linuxuser95> Apr 05 00:16:13 linux1 kernel: Bluetooth: hci0: setting interface failed (71)
[07:47] <linuxuser95> I managed to pair my earbuds lol, even so I had to restart the service for it to work
[20:03] <KOLANICH> https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src-gles/+bug/1922587
[20:03] <KOLANICH> https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1922589
[20:10] <MikeRL> I created a custom session and now there's no option besides yaru-light and default for a GNOME shell theme. What can I do to get the orange on black back in a custom session?
[20:10] <MikeRL> Also with the custom session appearance is missing under Settings.