[03:36] <wonko> With aptX LL the ideal latency for bluetooth is 34ms. That's best case. It can even go up to over 100ms. It also depends a lot on the stack implementation. The latency to my headphones is good enough for movies. The latency to my truck is horrendous and makes watching anything video completely unacceptable.
[04:14] <OvenWerks> 34ms is bad enough that it is impossible to keep time. By the time I am 30ft away from the band (with a long cord), my timing is not acceptable as a bass player. probably less for drums.
[06:12] <zmagii> How can I increase font size in e.g. terminal and Emacs when I plug in an external monitor? (On #emacs the recommendation was to do it system wide, rather than in Emacs.)
[06:18] <corrinado[m]>  zmagii [Ctrl-Shift + / Ctrl -] ??  It has to be the window that is 'in focus'
[06:21] <zmagii> corrinado[m]: That seems to work only for terminal and not e.g. Thunderbird or Emacs.
[06:25] <corrinado[m]> Yeah. I thought your question was specifically about the terminal.
[06:25] <corrinado[m]> If this is about app display on only an external monitor, I'm not sure how to help. If you want to do it system wide, each app should have controls within their setting area for fonts used.
[06:26] <corrinado[m]> If you only want to effect that external monitor only .. perhaps simply changing the monitor resolution would help everything on that display more readable. At the cost of fewer pixels
[17:21]  * jouni65[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/HbiSqhEFNRifSnWoVbReDvpa/message.txt >
[17:41] <Voidnaut> Hello, I am quite new to linux. I'm having an issue with JACK. When I first launch Ubuntu Studio, 3 instances of JACK launch and all give an error about DBUS. All three fail to start the server. If I manually launch qjackctrl I am still unable to start the server. If I kill all instances and launch again, it still doesn't work. Everything worked
[17:41] <Voidnaut> previously, I haven't changed anything that I'm aware of. Possibly related; Everytime I restart Ubuntu Studio it launches in some kind of safe mode? (low resolution, only 1out of 3 monitors, no sound) I have to launch into repair mode and fix a package that always seems to be ubuntu-driver-common or something like that. Where do I even begin trying
[17:41] <Voidnaut> to troubleshoot this? :/
[17:44] <Voidnaut> I'm on 20.04 LTS and have windows 10 dual booted if that info helps
[18:18] <jouni65[m]> <Voidnaut "Hello, I am quite new to linux. "> Have you checked the /var/log/system ( system error log) says? What kind of error message you get? As a linux newbie, the exact error message and search engine of your choice  is one of your friends.  Based on the fact that only one of your monitors are visible, good starting point is to check know linux issues with your graphic card.
[18:19] <jouni65[m]> > <@freenode_Voidnaut:matrix.org> Hello, I am quite new to linux. I'm having an issue with JACK. When I first launch Ubuntu Studio, 3 instances of JACK launch and all give an error about DBUS. All three fail to start the server. If I manually launch qjackctrl I am still unable to start the server. If I kill all instances and launch again, it still doesn't work. Everything worked
[18:19] <jouni65[m]>  * Have you checked what  the /var/log/system ( system error log) says? What kind of error message you get? As a linux newbie, the exact error message and search engine of your choice  is one of your friends.  Based on the fact that only one of your monitors are visible, good starting point is to check know linux issues with your graphic card.
[18:55] <Voidnaut> Which log file am I looking for, sorry? in /var/log there is nothing called "system" I have syslog, syslog.1 and syslog.2.gz etc(.3.gz, .4.gz -> .7.gz). And what info should I be looking for in said file? Everything I see contains seemingly thousands of lines. It's not a hardware compatibility issue I don't think, because if I have the issue I can
[18:55] <Voidnaut> just restart into advanced boot options and check for broken packages; Upon doing so it finds/fixes the package 'ubuntu-drivers-common', then I can reboot and all monitors work fine, games work fine. But JACK audio still has 3 instances open and none of them are able to start the server
[19:58] <Voidnaut> The last important bit of info is that *everything* worked fine ~last week. The only thing I've actively changed is installing steam games. I'm not sure exactly when the JACK issue began as it only really effects my music production and I have been doing daw-less things for a few weeks
[20:15] <Voidnaut> I searched through syslog and it found that it was saying a device was missing. I traced some cables around the room and my audio interface had gotten unplugged at some point. So that fixed part of the issue, JACK can now launch a server but it still launches 3 instances on startup for some reason (only one starts the server, the other two give
[20:15] <Voidnaut> errors). In my startup programs there is only one instance of jack and one of pulse audio. The low resolution issue still persists; But this time when I ran dpkg(?) from recovery mode it didn't find anything wrong. But still somehow fixed the issue, and all monitors work at their intended resolutions :/
[20:20] <_puddle_> sounds like the wrong graphics driver is getting loaded