[11:43] <tay> como fazer para formatar  o xubuntu??
[11:47] <gnrp> Hmmmm.
[11:47] <gnrp> !es
[11:47] <gnrp> ?
[11:47] <gnrp> !pt
[11:47] <gnrp> or rather that?
[11:54] <jphilips> if there are any german speaking individuals here, please contribute to completing xubuntu's user-docs - https://translations.launchpad.net/xubuntu-docs/cosmic/+lang/de
[12:06] <gnrp> oh, there is stuff to do?
[12:06] <gnrp> last time I looked for translations German seemed to be over-translated^^
[12:33] <jphilips> there are quite a number of languages that are missing or incomplete translations - https://translations.launchpad.net/xubuntu-docs/
[12:34] <jphilips> there is only 7 untranslated for brazilian portuguese if anyone knows that - https://translations.launchpad.net/xubuntu-docs/cosmic/+lang/pt_BR
[12:35] <jphilips> 7 as well for finnish - https://translations.launchpad.net/xubuntu-docs/cosmic/+lang/fi
[12:36] <jphilips> 3 for russian - https://translations.launchpad.net/xubuntu-docs/cosmic/+lang/ru
[16:52] <Giuliqq> Hello everyone! New and unaware user of Xubuntu here. I've just installed Xubuntu on a late 2008 MacBook, in order to inject new life into it
[16:54] <Giuliqq> As of know everything works smooth, except from some problems related to the suspension status and closing the lid of the Mac. It is impossibile to exit the suspension mode, only thing I get is a black screen. Any suggestion, useful links or something? Thank you in advance!
[16:55] <gnrp> Giuliqq: When you reboot, do you see anything in the logs, or is the notebook jus tfrozen?
[16:57] <Giuliqq> Thank you for your answer, first of all, very kind of you. I really can't tell if the notebook is really just frozen or just unable to load a proper interface, only thing to do is rebooting by a long press of the power button
[16:57] <Giuliqq> Did not check the log, honestly, I'll try now.
[16:58] <gnrp> so once you re-open it, wait a bit, and then reboot the computer
[16:58] <diogenes_> Giuliqq, suspend in general is Achilles' heel for both linux and windows, on linux it works worse and there is little to nothing you can do about that.
[16:58] <gnrp> and note the time
[16:58] <gnrp> when you look into /var/log/syslog, you can check it out
[16:58] <gnrp> ah, and what diogenes_ says. Suspend is a bitch
[16:59] <Giuliqq> Thanks to the both of you, I've heard that suspend was one big itchy problem
[16:59] <Giuliqq> but everything else works so smooth that I really want to try and solve this issue
[16:59] <Giuliqq> I'll try with the log
[17:02] <Giuliqq> Curios thing is that the notebook has a little led on one side, meant (originally) to indicate if the hdd was in function or not. Usually (while using OS x ) the led would turn off with the lid closed. In this case it appears to be the contrary: once I close the lid, the led stays active and then, once the lid is re-opened, the led rose flashing
[17:13] <Giuliqq> Hemm, having some troubles with finding the log. Sorry for the silly question, really new user. Should I just use the command you wrote in the Ubuntu terminal?
[17:17] <gnrp> no, but use the file explorer to navigate to /var/log
[17:17] <gnrp> and then there is a file syslog
[17:17] <gnrp> but as diogenes_ said, I highly doubt you will be able to fix your problem, esp. if you are new to Linux :/
[17:19] <Giuliqq> Oh right, sorry, that was a route. you're probably right, was just willing to try
[17:27] <jphilips> i've had some issues like that and had to Ctrl + Alt + F2, login, and kill the screensaver or screen locker
[17:28] <jphilips> then Ctrl + Alt + F7 to get back
[17:29] <Giuliqq> could it maybe me something related to graphic card drivers?
[17:30] <jphilips> for me it was definitely a bug in the screen saver or locker, so had to kill it as it was malfunctioning
[17:31] <Giuliqq> Thanks jphilips, I've read that and I've tried ctrl+alt+f2 but nothing happened
[17:31] <Giuliqq> But I'll try again later
[17:32] <jphilips> Giuliqq: if you press that key combination, the screen should go black and you should see a login prompt
[17:32] <jphilips> ctrl + alt + f1 also works
[17:33] <Giuliqq> I've read that in the past days, but once the lid is opened the screen is black and remains black whatsoever
[17:42] <Giuliqq> Ok, thank you alla for your kindness and patience, I will try again sometimes in future. In case I'll avoid closing the lid with the notebook on. Thanks, bye!
[22:25] <Allemand> Looking for help with my Toshiba Satellite laptop L15W. Xubuntu 18.04 is installed. The wireless chip is a Realtek RTL8723Be.
[22:25] <Allemand> It doesn't see any wireless networks
[22:34] <lighterowl> boy, are you unlucky.
[22:35] <lighterowl> Allemand: is the adapter detected? are you sure that any hardware switches for turning wireless connectivity on/off on the laptop are set to enabled?
[22:36] <lighterowl> generally, the driver is now part of the kernel, so it should at least be detected without having to install any external drivers.
[22:39] <Allemand> Yes it is. I ran lshw -c network and the adapter is seen. If I toggle the hardware status with FN+F12, 'Enable Wi-Fi in the system will gray out. Hitting it again, enables it again.
[22:39] <Allemand> Could it be the Network Manager? Where can I find it?
[22:41] <lighterowl> okay. well, "Enable Wi-Fi" should stay enabled.
[22:45] <lighterowl> ugh. the only thing that comes to mind is missing firmware. are there any messages related to the adapter in dmesg?
[22:48] <Allemand> dmsg shows the adapter from when I toggled it off and on
[22:48] <Allemand> Where can I find Network Manager to (re) install it?
[22:50] <lighterowl> I don't see why you would want to do that. if you're sure that's what you need, apt purge network-manager will do the trick. but I'd advise against it.
[22:52] <lighterowl> what's the output of "rfkill list"?
[23:09] <Allemand> "sudo rfkill list: shows Toshiba Bluetooth, soft blocked: yes , hard blocked: no , Wireless Lan, soft blocked: no, hard blocked: no
[23:17] <lighterowl> ohuh
[23:18] <Allemand> can you elaborate?
[23:18] <lighterowl> well, everything seems fine.
[23:19] <lighterowl> though the arch wiki mentions that some devices have "only one physical antenna connected, and antenna autoselection is broken".
[23:19] <lighterowl> you could try putting "options rtl8723be ant_sel=1" and rebooting. if it still doesn't work, change that to "ant_sel=2" and reboot again. if that still doesn't work, I'm out of ideas.
[23:20] <Allemand> where do I put those options?
[23:20] <lighterowl> oh, right, I forgot. create a file called /etc/modprobe.d/rtl8723be.conf as root.
[23:31] <Allemand> "options rtl8723be ant_sel=1" worked!!!  Thank you very much!
[23:31] <lighterowl> yay! :)
[23:32] <Allemand> This had been working a year of so ago and then I haven't used it in about a year so it is strange that this is needed but whatever
[23:33] <lighterowl> huh. perhaps you updated your system in the meantime, and the new drivers don't default to antenna number one anymore - but that's just conjecture.