 @saptech [<saptech> after updating to 18.10, when I boot I'm taking to this virtual keyboa …], After one update of Lubuntu 18.10 i also got this keyboard at login screen but some updates after it is gone
[11:17] <onla> what program to open .rtf files?
[11:18] <onla> hmm abiword ok
[11:22] <leszek> onla: you could also install libreoffice writer for it
[11:22] <onla> I have 2gb .rtf file
[11:22] <onla> how can I examine it? Soon I am gonna plug it in here.. oh except that I forgot this is arch linux and not lubuntu sorry
[11:40] <leszek> 2gb rtf?? WTF
[11:54] <alish> Hi, I have lubuntu 18.04. recently I had fresh install (i needed to use windows for a while then I return back). I'm using openconnect for vpn. after using it for several hours, everything (especially things that interact with terminal) get freeze. when I try to restart system, it show trying to stop "avahi" but it can't. I've searched but hadn't find anything useful.
[17:52] <jdx_> diogenes_ are the same person that visits #mageia ?
[17:53] <diogenes_> jdx_, i've never visited #mageis
[17:53] <diogenes_> mageia*
[17:57] <jdx_> ok, thanks diogenes_
[17:57] <diogenes_> no problem
 @wxl [<wxl> i'd try it enabled first, but not sure], Hi! Enabling secure boot on bios will not block any kernel upgrade of my Lubuntu 18.10?
 @JyotiGomes it can if the underlying drivers aren't signed.
 unless you're installing drivers from random sources on, say, Windows, you probably don't *need* Secure Boot...
 but it could cause kernel update problems if you have Secure Boot enabled and things go sideways
[18:15] <wxl> @JyotiGomes why would it?
 @wxl because someone forgets to sign a driver :P
[18:16] <wxl> but that would be a bug
[18:17] <teward> yet it does happen sometimes lol
[18:17]  * wxl shrugs
[18:18] <apt-ghetto> are we speaking about upgrading from 18.10 to 19.04 or installing a newer kernel on the same major version?
 @apt-ghetto [<apt-ghetto> are we speaking about upgrading from 18.10 to 19.04 or installing a …], I am speaking about installing a newer kernel on the same major version, the Lubuntu 18.10. Today i had a upgrade to the 4.18.0-12 kernel and i did not know if was better to have the secure boot on bios enabled or not...
 I havo not dual boot, only Lubuntu 18.10
[18:57] <apt-ghetto> do you have an UEFI installation?
 @apt-ghetto [<apt-ghetto> do you have an UEFI installation?], Yes, UEFI
[18:58] <apt-ghetto> check it with `sudo efibootmgr -v`
 @apt-ghetto [<apt-ghetto> check it with `sudo efibootmgr -v`], ok
[19:01] <apt-ghetto> do you have installed a proprietary driver, say NVidia?
 sudo efibootmgr -v ... BootCurrent: 0000 ... Timeout: 0 seconds ... ... ... Boot2001* EFI USB Device        RC ... Boot3000* Internal Hard Disk or Solid State Disk        RC
 not nvidea in my laptop, but my wife has a nvidia drive in her laptop (where is also installed Lubuntu 18.10...
[19:07] <apt-ghetto> installing a newer kernel does not break your secure boot, because it is signed
[19:08] <apt-ghetto> and installing a newer kernel does not change the driver, so in my opinion, you should not have problems with secure boot
 @apt-ghetto [<apt-ghetto> and installing a newer kernel does not change the driver, so in my …], ok, thank you
[19:09] <apt-ghetto> if you have problems, they are very likely not related to secure boot
[19:09] <wxl> that's what i was trying to say in response to @teward001 .. if a driver isn't signed, that's a bug in the driver, not a problem with secure boot
[19:10] <apt-ghetto> the only signed driver that i know is from nvidia
[19:10] <apt-ghetto> and nvidia is, ehhhm nvidia
 This appeared during the upgrade (sorry for being in Portuguese):
 (Photo, 1280x591) https://i.imgur.com/3M6IvDX.jpg
[19:12] <apt-ghetto> that is totally unrelated to secure boot
[19:12] <wxl> i assume you can read it and understand what it means XD
[19:12] <wxl> if not, i can tell you (and i don't speak portugese)
 I can not choose between the two options, I do not know if I should keep the existing package or replace it with the creator package
[19:15] <wxl> then look at them
 i'd view the idfferences, make a note about them yourself, then accept the package's version
[19:15] <wxl> that's one of the options
 then apply changes as you need to later
 yep ^ that
[19:15] <wxl> ^^ in general, that, because most often they're commends
[19:15] <wxl> s/commends/comments/
 ok, i can not make an informed decision but i will replace the package 😊
 my knowledge is very poor :-P
[19:18] <wxl> just post it up here if you want us to help you
 @wxl [<wxl> just post it up here if you want us to help you], Thanks a lot, you are the user's guardian angels.
 😊
[19:20] <wxl> we try XD