[02:52] <ubptgbot> Cloud was added by: Cloud
[06:58] <ubptgbot> Haywhy was added by: Haywhy
[07:45] <ubptgbot> ayidsudirman was added by: ayidsudirman
 @fredldotme Since today's update, my Xperia X is stuck on the "SONY" boot screen. It does not react to any key press and cannot be turned off. What should I do? Just let it sit there and drain the battery, or is there any magic I can try?
 Wow, fiddling around I found that pressing power and volume up/down together forces a reboot. I didn't know that. It needed two gos, but now it's booted into UT.
 @ruedigerkupper [Wow, fiddling around I found that pressing power and volume up/down together for …], Good thing you shared that. My gf's Xperia X is arriving today :)
[11:35] <ubptgbot> hafedh was added by: hafedh
[13:46] <ubptgbot> First was added by: First
[13:58] <ubptgbot> HoangJump was added by: HoangJump
 @matv1 [Good thing you shared that. My gf's Xperia X is arriving today :)], Enjoy! It's a good phone, UT runs great on it. All praise to Alfred! Be aure to follow his instructions for installing UBports on it.
 @matv1 [Good thing you shared that. My gf's Xperia X is arriving today :)], [Edit] Enjoy! It's a good phone, UT runs great on it. All praise to Alfred! Be sure to follow his instructions for installing UBports on it.
 I praise him every day :D
 👍
[17:25] <ubptgbot> Debura Peragine was added by: Debura Peragine
 Hi. Question for those who run UT on something other than the Pinephone: Does toggling bluetooth on/off in either the Settings app or the Lomiri pull-down menu work for you? I've been doing some research as to why that's not functional on Pinephone, but realized it's probably good to know what the situation is for the other devices.
[18:30] <ubptgbot> Thanks.
 yes, it works on android based devices
 also i think i works on x86 image when running on hardware
 As I unserstand, BT is a nasty subject.It is nothing to be resolved one for all, but must be resolved differently for each platform.
 pinephone root password???
 there is no root password
 you mean the password for sudo?
 yes
 it's whatever you set the pin/passphrase to
 or just blank for swipe to unlock
 ahhh ok
 now I set the passphrase
 tnks
 Anyone have any luck virtualizing the x86 image? Not sure if today's build is bugged or it's my setup, but seems to never get past "Starting virtual private network daemon".
 @YepYepperson [Anyone have any luck virtualizing the x86 image? Not sure if today's build is bu …], seems to do the same here
[20:10] <ubptgbot> <Debura Peragine> Binance Futures Will Launch BTC/USD Coin-Ⓜ Perpetual Contract With Up to 125x Leverage AND Binancе Giveaway for 10 000 BTC and 10 000 ETH!! Source - https://bit.ly/3fUXJ42
 I was hoping to see what dbus looked like on a system that had the bluetooth toggle working. Both ubuntu-system-settings and Lomiri send a session signal, which doesn't seem to be populated with any of the variables that something like bluetoothctl sends, and it also never sends a system message to org.bluez, which after looking at t
[20:18] <ubptgbot> he kernel bluez client code, I thiiiink that's how the power is supposed to be toggled. Just not sure what component is supposed to actually be in charge of telling the kernel to power on/off the device.
 @YepYepperson [I was hoping to see what dbus looked like on a system that had the bluetooth tog …], what does the log for `indicator-bluetooth` say when toggling the switch in the indicator?
 should be `~/.cache/upstart/indicator-bluetooth.log` i think
 it uses `/dev/rfkill` to turn off the radio
[20:31] <ubptgbot> Anish Khan was added by: Anish Khan
[20:33] <ubptgbot> C1A0BELLA was added by: C1A0BELLA
 Wow, that's helpful. From the name of it, I didn't think it was something worth looking at.
 "Could not write rfkill event: Bad file descriptor"
 bingo :)
 So, just changing the file permissions (or the ownership) of /dev/rfkill and then restarting indicator-bluetooth-service is all it took to get it working.
 interesting
 Not persistent after reboot, though. Gonna try a udev rule.
 Yep, udev rule did the trick