 I just ran 'stress --cpu 4 --io 4 --vm 2 --vm-bytes 2G --timeout 16s' the screen flickered once or twice during the run.
 Not in every run tho. Once in a 4-5 runs. You need to stress it on some specific parameters?
[00:13] <xpkill23> failed run completed in 2087s
[05:22] <gmichel3> Hello, fresh install of Lubuntu 18.10, I installed Netbeans and when I run it after the loading screen it just quits, I get no error code on the terminal.
[05:22] <gmichel3> Any ideas?
[05:23] <wxl> you run it in the terminal and nothing is output?
[05:23] <gmichel3> That's right wxl
[05:25] <gmichel3> Googling around all I found was something related to Netbeans (on Ubuntu 18.04) trying to use jdk11 when it should use jdk8. My installation seems to use jdk8 (it was one of the dependencies).
[05:26] <wxl> yeah i don't know but it's likely not a *l*ubuntu issue. you might want to ask over at #ubuntu and see if they have ideas
[05:26] <gmichel3> Alright, I will do that. Thanks!
[05:26] <wxl> good luck
[05:38] <wxl> https://phab.lubuntu.me/P5
[05:38] <wxl> oops wrong channel XD
 @wxl [<wxl> oops wrong channel XD], Ack
 It's okay. We won't hate you for that. XD
[09:24] <xpkill23> 3
[13:25] <cheburnet> hi, I'm going to try 19.04, where can I look up known issues?
[13:41] <cheburnet> what's the purpose of verifying md5sum if you get it over plain http which may be tempered
[13:45] <teward> cheburnet: you have to verify the ISO is downloaded fully, the hash sums will identify that, and if you get the ISOs from an official mirror you can be fairly certain those aren't 'tampered with'
[13:45] <teward> cheburnet: there's a slew of known issues fir 19.04 though, but I don't know if there's one all inclusive list of known issues
[13:45] <cheburnet> teward: but if my router is hacked because the firmware is old and my provider uses simple standard passwords
[13:45] <cheburnet> and dns is hijacked...
[13:46] <teward> then get a new router.
[13:46] <cheburnet> I'm a bum :-)
[13:46] <teward> if you think *that* paranoid then you either need to
[13:46] <teward> (a) fix the problem
[13:46] <teward> (b) not download anything
[13:46] <teward> and if B is your choice, then I can't help you nor can anyone else
[13:47] <cheburnet> I may download via torrent or https, should help
[13:47] <teward> HTTPS won't help you :P
[13:47] <teward> torrent might
[13:47] <teward> but last I heard there was no 19.04 torrents yet
[13:47] <cheburnet> teward: but certificate is hard to hijack even if you control dns I think
[13:47] <teward> cheburnet: keep telling yourself that.
[13:48]  * teward is an IT Security guy and knows a few mechanisms that could be used to 'hijack' a site with DNS MITM and expoliting a vuln to drop a new trusted root CA into your browser and then 'appear' as a valid site
[13:48] <cheburnet> teward: thank you, will dnssec help if it is provided by ubuntu dns servers?
[13:48] <teward> and if your router is seriously that old that you're afraid of hijacking and such like this you're SOL
[13:48] <teward> because there's a billion ways to circumvent the 'protections' that exist
[13:49] <teward> DNSSEC only helps if it's enabled
[13:49] <teward> and it's not for ubuntu.com
[13:49] <teward> or its subdomains
[13:50] <teward> *most* domains in the world don't have DNSSEC enabled
[13:50] <teward> (L)Ubuntu's included it seems
[13:51] <cheburnet> I tried to enable it for the domain I own, but subtomains that don't have it enabled got broken if using 1.1.1.1, 8.8.8.8 works fine with unprotected subdomains
[13:51] <teward> and now we're drifting into the world of offtopic chatter
[13:51] <cheburnet> teward: thank you for your help
[14:04] <teward> cheburnet: the only OTHER thing you could do possibly
[14:04] <teward> is to check the cryptosigs on the ISOs against the known good keys
[14:04] <teward> but again you'd have to trust you're getting the proper keys from Ubuntu to test against for verification
[14:04] <teward> (I say Ubuntu, i just use that as an umbrella term in this case for all the variants0
[14:05] <teward> but if you don't trust *that* either then you're out of luck.
[14:06] <player1> hi guys, yesterday I installed lubuntu 18.10 and I boot with nomodeset, it boots ok but my screen resolution is stuck in 1024x768, I have WXGA screen with resolution 1280x800 but I cannot find this in monitor settings
 nomodeset is more or less a "solution of last resort"
[14:07] <player1> whenever I click monitor settings has 1024x768, how to change this in 1280x800?
[14:08] <teward> by getting proper drivers rather than using nomodeset.  nomodeset is a "solution of last resort" when all other solutions ahve failed.
[14:09] <player1> whenever I login with live dvd my resolution seems to be ok
 what shows `lspci -nnk | grep -A3 "\[03..\]:"`?
[14:09] <player1> wait to check this
[14:09] <player1> I must go to other room
[14:18] <player1> it says ATI MOBILITY RADEON RS300M
[14:23] <player1> aptghetto it says AMD/ATI RS300M [Mobility Radeon 9100 IGP[103c:006b]
[14:23] <player1> aptghetto it says kernel modules;radeonfb,radeon
[14:24] <player1> aptghetto did you see my message?
 probably has, but you need patience
[14:25] <player1> ok
 I see *the* message
 :P
[14:28] <player1> so is any way to set screen resolution in 1280x800
 Your graphic card should run with the normal radeon driver
[14:31] <player1> it runs ok with live dvd
 Make first `sudo apt update && sudo apt full-upgrade`, check also, that radeon is installed with `dpkg -l xserver-xorg-video-ati`
[14:36] <player1> I go to check this and I come back later
[14:43] <player1> aptghetto it says xserver-xorg-v 1:18.1.0-1 i386
 beginning with `ii`?
[14:43] <player1> yes
[14:44] <player1> ii
 reboot your system, edit your grub entry, pressing key "E" and delete the word "nomodeset", then boot the system
[14:45] <player1> if I do this it shows white screen
 That may be, but then we can check the logs
[14:46] <player1> ok wait to do this
[14:51] <player1> aptghetto I did it and booted in white screen
 Press CTRL+ALT+F5 and login
[14:52] <player1> aptghetto I pressed control alt f2 and I am logged in in terminal
[14:52] <player1> what should I type
 then execute `grep EE /var/log/Xorg.0.log`
 Maybe there is some error in your display server
[14:54] <cheburnet> I had lubuntu 18.10 and after I installed nvidia drivers and did an apt upgrade it won't boot. I flashed 19.04 on a pendrive but it doesn't boot in safe graphics mode too. It prints "Booting in blind mode" as usual but nothing else is printed.
 Otherwise `sudo apt install mesa-utils && glxinfo | grep "OpenGL version"`
[14:55] <cheburnet> it seems to not be hanging but blind typing commands like systemctl start display-manager doesn't help
[14:56] <player1> aptghetto wait to do this
[14:58] <cheburnet> if I edit grub loader it says "file=/cdrom/preseed/lubuntu.seed" <- shouldn't cdrom be something else on my pendrive?
[14:59] <cheburnet> I tried burning with both dd and etcher
[15:02] <cheburnet> pressting ctrl + alt + del flashes the light on the pendrive but doesn't reboot the system
[15:02] <player1> aptghetto first command with Xorg.0.log shows error
 I hope, you will tell us more details about the xorg errors
[15:04] <cheburnet> also I get "file "/boot/" not found" before grub menu appears, I use rEFInd on the HDD and boot from it into pendrive grub
[15:08] <cheburnet> I doubt I have any physicall tty, but how else can I troubleshoot the boot process? I have anothe machine and a phone -- may I use them to debug the booting process?
[15:10] <player1> aptghetto wait to do this
[15:16] <player1> aptghetto WW warning EE error NI not implemented (??) unknown[62.128](II) Initializing extension MIT-SCREEN-SAVER
 This are normal messages
[15:17] <player1> aptghetto now I must reboot with nomodeset to connect to internet and install mesa-utils?
 Not yet
[15:18] <player1> if I boot without nomodeset I cannot connect to internet
[15:18] <player1> I am offline
 Yes, I understand
 But first I like to see your log files of sddm
[15:19] <player1> ok how to create this log
 Go back, and type `cd` to be sure, that you are in your home directory, then type `journalctl -b -u sddm > sddm.log`
 This should create a file in your home directory and then you can reboot your system
[15:22] <player1> wait I go to do this
 Then please upload the file to pastebin and share the link, so we can have a look at it … And post also your OpenGL version
[15:26] <player1> aptghetto it says -bash: sddm.log Permission Denied
 Then you are not in your home directory or you have your home directory messed up
[15:28] <player1> in prompt it says blahblah.../home$
 `cd ~`
[15:28] <player1> wait I will do this
[15:32] <player1> aptghetto ok I did it I opened this file with nano
[15:32] <player1> what line should I post from this log
 Post the whole log file to a pastebin site and share the link, check also that there are no sensitive data before posting
 I will be offline soon
[15:35] <player1> aptghetto I need sometime to do this
[15:35] <player1> how to paste bin this
 Like this morning: `pastebinit -i ~/sddm.log`
[15:39] <player1> wait
 No, I go now
 But I will see it later
[15:54] <player1> aptghetto my url is /p/X4vbzsQYvG
[16:15] <cheburnet> How to apport to submit booting information about a hanging boot of 19.04?
[16:15] <cheburnet> *use apport
[16:16] <cheburnet> I see "Started Set console scheme." on tty1 and no serious errors in the logs
[16:56] <player1> why lubuntu 19.04 does not have 32bit version?
 you mean why does it not have a 32-bit *installer* ISO.
 there is still a 32-bit version but you have to install from the last release that had a 32bit ISO which IIRC was 18.04 and then incrementally upgrade to still get 32-bit packages
 the reason there's no 32-bit installer ISO is that there was more or less a global decision to discontinue 32bit ISOs amongst all the variants.
 but 32bit packages still exist.
 if you still want a reason why though I'm sure that @tsimonq2, the Lubuntu Release Manager and a member of the Lubuntu Council, can give you a more specific answer.
 *hides*
[17:02] <teward> player1: see those ^ messages to answer your question
[17:02] <teward> or wait
[19:15] <player1> can I type after  nomodeset  video=radeonfb:1280x800  ? will this fix my resolution?
 @player1 I had a look at the sddm logs, but unfortunately I didn't found anything useful
 Then I had a look on the full log files from http://paste.ubuntu.com/p/rBJwhqHHXG/ and there it seems to be a problem of sddm
 It might be this known bug => http://paste.ubuntu.com/p/rBJwhqHHXG/
[20:33] <player1> aptghetto if I put after nomodeset
[20:34] <player1> aptghetto video=radeonfb:1280x800
[20:34] <player1> will it work?
[20:36] <player1> aptghetto did you find any bug?
[20:38] <player1> how can i add to nomodeset the  video command?
[20:39] <player1> I want to edit grub from command line in terminal
[21:31] <player1> I added this line but nothing happened
[21:31] <player1> is there a way to add voice commands in lubuntu?
[22:00] <heysoundude> tomorrow's the big day, right?  Or can I start looking for the upgrade around 00:00Z?
[22:01] <wxl> !isitout
[22:01] <wxl> XD
[22:02] <heysoundude> 18.04.19...midnight Zulu tomorrow, I guess
[22:05] <wxl> to be clear the INTENTION is to release it on the 19th
[22:05] <wxl> but sometimes things get messed up
[22:05] <wxl> that's rare
[22:05] <wxl> the time is never specified, either, so assume EoD
[22:23] <heysoundude> alrighty...sometime thursday, then.