=== guiverc2 is now known as guiverc
[10:22] <Iamthehuman1> Hey. Got an urgent problem. In US, for the 2nd time now, when I start an OS in VirtualBox I cannot see the opened OS anywhere, except the thumbnail when hovering over the running VirtualBox-icon
[10:22] <Iamthehuman1> So the window containing the started OS, cannot be accessed at all
[10:23] <Iamthehuman1> I would appreciate info if this is (likely) an US, Kubuntu, Xorg or VirtualBox bug
[11:09] <Iamthehuman1> found a workaround: virtualbox will start one OS ok after a reboot, but the 2nd time one tries to start an OS it just fails in the way I described
[11:14] <Iamthehuman1> and ok, sorry for the channel noise, it autoenabled my HDMI-connected TV, when I removed a broken monitor, so cancel all the above lines
[11:14] <Iamthehuman1> another thing: is this bluetooth-devices autoconnect Kubuntu people's idea or US idea? It is annoying, can I unset it somewhere?
[14:23] <Eickmeyer[m]> Iamthehuman1: Per the channel topic, you're unlikely to get help here prior to 1500 UTC since that's when most people here are awake. That said, the bluetooth autoconnect thing? I don't know of a single OS that doesn't autoconnect, so I think it's just part of the bluetooth spec. 
[14:26] <Eickmeyer[m]> Just keep in mind, Ubuntu Studio isn't based on Kubuntu. Both ARE alternate configurations of Ubuntu, not separate distributions in and of themselves.
[14:28] <Eickmeyer[m]> !morehelp | Iamthehuman1: If you need such urgent help in the future:
[14:28] <ubottu> Iamthehuman1: If you need such urgent help in the future:: #ubuntustudio sometimes cannot answer your questions in a timely matter, or simply lacks the capacity. For additional sources of help, try #ubuntu if your issue is of a technical nature, or #lau (Linux Audio Users) or #opensourcemusicians if it has to do with the audio stack.
[15:47] <Iamthehuman1> Eickmeyer[m]: I have had Kubuntu for a decade that did not automatically connect every bluetooth that gets powered on too close to the computer
[15:47] <Iamthehuman1> The autoconnect just makes me need to do more manual work to undo the autoconnects
[15:49] <Iamthehuman1> If I want to listen on my headphones from my phone and I power them up I need to go all the way to the computer to undo the autoconnect or no audio at all
[15:57] <Eickmeyer[m]> Iamthehuman: Then maybe it was even further upstream with KDE, but even GNOME and other DEs do this.
[15:58] <Eickmeyer[m]> And you're not the only one that has used Kubuntu for a decade. :)
[15:58] <Eickmeyer[m]> You can, of course, just switch your audio device using the applet.
[16:05] <Eickmeyer[m]> Iamthehuman1: My point is, it was nobody's decision, at least in the scope of Ubuntu. And you're not going to find anyone in this chat that knows how to change it unless someone speaks up. Hence I gave you other options for help.
[16:09] <Iamthehuman1> You're not making much sense, maybe you should eat something
[16:11] <Iamthehuman1> If someone decided that every bluetooth that is powered on is autoconnected without asking if this is cool or not, and this did not show up in Kubuntu from 2011 to 2020 at all, nor in KDE Neon, so I do think this is a choice by someone, how much ever you are being confusing and hostile
[16:14] <oerheks> i use commandline,  bluetoothctl, scan, pair and most important ' trust' ..
[16:14] <oerheks> or install bluez, a gui to do so. standard tool gave me no options
[16:14] <Iamthehuman1> oerheks: thanks, but I think an OS should have some settings which could for example set. if I want to fix everything myself, then I'd want Arch and not US, but I guess that is the only way
[16:15] <Iamthehuman1> So I need to write a script to block some script that does not exist according to the head developer, niiiiiice
[16:15] <oerheks> oh oke, you are not using ubuntu studio?
[16:16] <Iamthehuman1> I am, that is why I am asking here, but the boss already said that nothing is a design choice and no implemented solution is hackable at all
[16:17] <oerheks> ? 
[16:18] <Iamthehuman1> Arch is probably more work, but there people actually help each other and not just tell the users to shut up and switch to another distro if they want anything
[16:19] <oerheks> oh rant away, i have more important things to do, good luck!
[16:21] <Iamthehuman1> oerheks: I would just like a setting to _not_ autoconnect the Bluetooth devices, but that cannot be done on US according to the head developer
[16:29] <Eickmeyer> Iamthehuman1: Literally not what I said. Ubuntu Studio is *not* a distribution. It's a preconfiguration. Remember that. We simply release a pre-made .iso image of software from the Ubuntu repositories that is configured differently than regular Ubuntu.
[16:29] <Eickmeyer> Therefore, the Bluetooth stack is *outside* of the Ubuntu Studio scope.
[16:30] <Eickmeyer> We have *nothing* to do with developing it.
[16:30] <Eickmeyer> Do you understand, Iamthehuman1?
[16:32] <Eickmeyer> Anything beyond what we have beyond the installation is up to you to configure to your liking. That's not our job at all.
[16:33] <Eickmeyer> Besides that, we are UNPAID VOLUNTEERS.
[16:33] <Eickmeyer> so you do NOT get to treat us like we work for you.
[16:34] <Eickmeyer> Please see the following:
[16:34] <Eickmeyer> !guidelines
[16:34] <ubottu> The guidelines for using the Ubuntu channels can be found at https://wiki.ubuntu.com/IRC/Guidelines
[16:34] <Eickmeyer> !CoC
[16:34] <ubottu> The Ubuntu Code of Conduct is the document that spells out etiquette in the Ubuntu community | http://www.ubuntu.com/project/about-ubuntu/conduct | For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct | Watch http://static.screencasts.ubuntu.com/videos/2010/12/22/004-SigningCoC.ogv