[01:06] <Joel9> When can I upgrade to 19.04 from 18.10 i386?
 @Joel9 [<Joel9> When can I upgrade to 19.04 from 18.10 i386?], 19.04 is not released for 18.10
 * i386
 I mean 19.04 is not released for i386.
[05:06] <guiverc> The_Loudspeaker ISO's are not produced for i386 (really i686), but you should be able to `do-release-upgrade` from 18.10 to 19.04  (19.04 ISOs were produced until dec-2018; i tested with it & have 19.04 running on a 686/non x86_64 test box)
[05:08] <uncle_ben> i'm doing a fresh install on a laptop, but there's no networking software on the install medium. how do i connect my wifi to complete the installation?
 @uncle_ben [<uncle_ben> i'm doing a fresh install on a laptop, but there's no networking sof …], Which version of lubuntu?
[05:08] <guiverc> uncle_ben, what install media are you using?  did you verify the download & media burn were valid?
[05:12] <uncle_ben> i'm using the lubuntu-19.04-desktop-amd64.iso
[05:13] <uncle_ben> it booted fine, it doesn't include net-tools, apparently
[05:14] <uncle_ben> it also doesn't seem to include network-manager-gnome
[05:16] <uncle_ben> why wouldn't that be included? seems like a basic and necessary utility
[05:17] <krytarik> uncle_ben: Well, the first has been deprecated all the way from the Debian base, and the latter would pull in GTK while Lubuntu is based on Qt now.
[05:17] <uncle_ben> krytarik ok so how does one connect to wifi then? is there any utility included on the installation medium that will accomplish this?
[05:18] <krytarik> The Lubuntu team are aware that there isn't really a suitable replacement for the latter available yet though.
[05:19] <uncle_ben> krytarik: i'm doing this install for a friend. so are you saying lubuntu doesn't support wifi? what should i do?
[05:27] <uncle_ben> and when i say "support" i mean the software include on the install media
[05:29] <krytarik> uncle_ben: https://manual.lubuntu.me/3/3.1/3.1.5/nm-tray.html - it'd seem you should be able to configure your wireless with nm-tray too, unless iirc its ID is hidden.
[05:40] <uncle_ben> krytarik: i'm reading the documentation, but i'm confused about the "connect the wifi name applet and then enter the password for the wifi." how do i connect the wifi name applet? when i left click the nm-tray applet, there's only an option for "enable wifi" but i don't see how to access the applet.
[05:41] <uncle_ben> is there a way to autodetect wifi networks or do i need to enter all the info manually?
[05:41] <krytarik> Well, I noticed that wording too and believe it's simply off.
[05:41] <krytarik> Yeah, like I said, if the wireless network is hidden, you are out of luck with this tool.
[05:43] <uncle_ben> ok well i'll just try doing it manually, since there seems to be no simpler option, but i hope the team fixes this for future releases, since it would be very helpful. even systemrescuecd has a very simple utility for connecting to wifi when you boot into graphical mode.
[05:43] <uncle_ben> thanks for your help
[05:57] <uncle_ben> krytarik: i'm up and running. thanks again
[06:00] <krytarik> uncle_ben: You are welcome.  But how did you manage it exactly?
[06:07] <uncle_ben> krytarik: i had to select "edit connections" on the applet and enter all the info manually. but now i have another problem. i wiped the disk for a clean install, then used gdisk to create a gpt parition table with three partitions: sda1 (bios boot partition) sda2 (swap) sda3 (btrfs) and i want to install lubuntu on sda3, but the installer won't let me do that from the partitions set up screen, apparently. is there any kind of "advanced user mode" i can u
[06:12] <uncle_ben> nevermind, i think i figured it out
[06:14] <krytarik> Good, but this might affect you too: https://github.com/calamares/calamares/issues/1014
[06:17] <uncle_ben> krytarik: i haven't read your link yet, but the installer is telling me that i need to create an efi system partition to start lubuntu. i set up my partition table from past memory of grub2 needing a bios boot partition on gpt tables to boot properly. maybe it's not relevant anymore or maybe lubuntu doesn't use grub as the boot manager?
[06:23] <krytarik> uncle_ben: Yes, it'd seem that info is outdated by now - all Ubuntu flavors still use Grub as the bootloader though.
[06:31] <guiverc> sorry; i had to step away & forgot to return..
[06:53] <uncle_ben> that link says i need the first partition 8MB unformatted and with ' bios_grub ' flag set, but on another system using arch i set the bio boot partition as 1007.0 kb before the 2048 sector, but come to think of it, i think this laptop is uefi enabled, so i probably should just wipe the partition table and use the installer to create the table
[11:41] <sagat> Bom dia , sou novo por aqui , onde posso ver como devo me portar na sala ?
[11:41] <sagat> Portugues ?
[19:05] <Mat____> Hi, does anyone know where to report a possible bug in Lubuntu 19.04?
 Mat____ => https://phab.lubuntu.me/w/bugs/
[19:09] <Mat____> Ok I see, I was searching somewhere in tasks page... Thank you!
 No problem. If you need further help, just ask
[19:13] <Mat____> I just installed Lubuntu 19.04 in a virtual machine to try it. On of the first thing I tried was to open a file with vim. I created an empty file on the desktop, went in properties>open with>vim>ok. When I double-click on the file icon nothing happen. If I right-click open with...>vim, then it opens. Is it a know bug?
[19:15] <Mat____> Also, if I chose featherpad as a default application for this type of file, I can double-click on the file and it will open. It looks like it is only with vim than it does not open on double-click.
[19:15] <wxl> hm that is interesting
[19:15] <wxl> my guess is that if you used gvim you'd have no such issue
 ^ i was about to say this
 `vim` is a CLI program heh.  `gvim` is GUI Vim
[19:16] <wxl> i bet the properties dialog somehow doesn't handle a non-graphical application
[19:16] <wxl> why the open with works is bizarre, though
[19:16] <Mat____> I will try Gvim by curiosity. But I prefer terminal vim.
[19:17] <Mat____> Yes it is working properly with gVim.
 the problem is probably because of terminal applications being weird.
[19:18] <wxl> doubtful
[19:18] <wxl> if it works one way it should work another
[19:18] <Mat____> Should I report it?
[19:18] <wxl> yes
[19:18] <wxl> against pcmanfm-qt
[19:18] <wxl> so `ubuntu-bug pcmanfm-qt`
[19:18] <Mat____> Ok
[19:18] <wxl> i bet if you added nano it would have the same problem
[19:19] <Mat____> I will try.
 lxqt-config-file-associations
[19:20] <wxl> hm the custom command isn't even playing right
[19:21] <wxl> this is not necessarily about a permanent association, @aptghetto
[19:21] <Mat____> Yes, I have to switch tab to be able to click on Ok in the custom command tab.
[19:21] <wxl> even then, it doesn't seem to save
[19:21] <wxl> seems like you have several bugs to report :)
[19:22] <Mat____> I also wanted to report the fact that if I use the Win button (is it Meta?) I have to press Up key twice to go up in the menu.
[19:23] <wxl> it's true if you click on it, too
[19:23] <wxl> report away
[19:23] <wxl> i count 4 bugs :)
[19:23] <Mat____> I did not know what to do tonight. Now I know...
[19:24] <kc2bez> In the menu for me, the first up stops in the search box.
[19:25] <Mat____> Yes but the cursor was already in the search field, isn't it?
[19:26] <wxl> la la la making 17000 10MiB files full of /dev/urandom
[19:26] <kc2bez> Not when I used the meta key.
[19:27] <Mat____> Interesting. For me if I use the meta key, the cursor is already blinking in the search field.
[19:28] <kc2bez> Interesting, a bug for sure.
 *makes 50000 17000MiB files full of `/dev/urandom` output on wxl's computer*
 :P
[19:28] <kc2bez> Interesting, down always moves it to the top of the list.
[19:29] <kc2bez> with one press
[19:29] <Mat____> Yes, same here for down.
 For me, as an Emacs user, the Meta key is the key "ALT", whereas the "Windows" key is called Super key.
[19:40] <Mat____> Ok, I so meant Super key in my previous messages, not Meta key.
[19:40] <wxl> we all know what you meant :/
[19:41] <wxl> never trust an emacs user XD
[19:42] <Mat____> I am a bit corrupted, I tried emacs + evil. But I went back to vim!
[19:43] <wxl> yeah well you're not REALLY an emacs user if you use evil
 You don't have to trust me. It's just easier to understand bug reports, that use clear definitions.
[19:45] <Mat____> Yes sure. I prefer to know my mistakes.
[20:20] <Mat____> Do you have an idea of the name of the package related to the menu bug? (in which we have to press twice the Up key to go up in the menu)
[20:20] <wxl> everything on the panel is the panel
[20:21] <wxl> so lxqt-panel
[20:21] <Mat____> ok
[20:21] <Mat____> Thanks
[20:21] <wxl> oooh well played Mat____
[20:22] <wxl> jeez a bug report i might not have to spend all night editing or trying to make sense of.. it's like a dream come true
[20:22] <Mat____> I just tried to followed the link you gave me.
[20:22] <Mat____> follow*
[20:23] <wxl> well, you did good
[20:23] <wxl> please make more bugs. i like your work. :)
[20:24] <Mat____> It will maybe happen. I am liking this new Lubuntu so there is a chance I will use it more :)
[20:24] <wxl> yay!
[22:45] <joe657> i'm trying to schedule a job in cron to disable my touchpad, but it's not working either as a root or user crobtab job. i'm using cron because i can't seem to get it to work using autostart within the user desktop environment. i'm using 18.04 LTS and here is the command: 'xinput set-prop 12 "Device Enabled" 0'. i hope someone can help
[22:46] <wxl> why don't you make a script that you call instead of using the command itself, just to avoid any parsing weirdness
[22:47] <wxl> i do know cron is particularly poopy because it's sh by default and often doesn't have the environment variables you expect
[22:47] <wxl> that's why calling everything out explicitly often helps
[22:47] <joe657> sorry, actually it's: @reboot xinput set-prop 12 "Device Enabled" 0
[22:47] <joe657> but that's what i had in there
[22:48] <joe657> wxl: is there a recommended autostart method using the default DE in lubuntu?
[22:49] <joe657> but yeah, i guess i can go the script route, if all else fails
[22:49] <wxl> yeah, the autostart
[22:50] <wxl> but i'd still use the script
[22:50] <joe657> autostart didn't work for me
[22:50] <wxl> https://wiki.lxde.org/en/LXSession#autostart
[22:50] <joe657> but i probably will just use a script
[22:50] <wxl> https://wiki.lxde.org/en/Autostart
[22:50] <joe657> thanks for the link, i'll check it out
[22:51] <wxl> there's also preferences » default applications for lxsession » autostart
[23:48] <joe657> wxl: even a bash script didn't execute the command at startup. i had assumed that creating the script as root, saving it at /, chmod u+x and using the @reboot sh /startup.sh would affect all users, but maybe i need to create the script as a user and call it from the user crontab? i'm confused.
[23:50] <wxl> joe657: i'm not sure that's going to do what you want, actually. you want it to run when you run the desktop environment, as your user. in other words, use autostart. crontab *might* work, but my guess is that it will run before x starts, which will mean it won't exactly work right. did you setup mail so you get feedback?