[00:37] <wagle> how do i tell which beta I am rnning now?
[01:02] <wagle> .. "running" ..
[01:39] <tomreyn> wagle: if anywhere i guess it would say in lsb_release -sd. but i think it just says "18.04 development version" or something. this probably makes more sense, too, since it gets constant updates.
[01:41] <wagle> tomreyn: yeah, it doesnt say much, but suppposedly beta2 was released today, and I'm curious if it upgraded
[01:46] <TJ-> wagle: beta is just all the packages on a certain date. if the system is up to date then it's there
[01:46] <wagle> TJ-: oki
[01:46] <wagle> thanks
[02:56] <CMEE_fie> Hello, I'm having a little trouble testing lubuntu 18.04 beta2, i thought asking here since there's more people and the issue doesn't seem to be specific of lubuntu
[02:57] <CMEE_fie> basically i have two HDDs, a toshiba formated with GPT and a WB formated with MBR
[02:58] <CMEE_fie> and lubuntu 18.04 beta2 running from a usb stick isn't mounting the WB drive formatted with MBR
[02:58] <CMEE_fie> the computer motherboard is from 2009 and bios only tho
[02:59] <CMEE_fie> btw when i say it isn't mounting the wb drive at all i mean i can't see it anywhere, not even on gparted
[03:00] <Bashing-om> CMEE_fie: From the USB stick what results ' sudo fdisk -lu ' is the hard drive seen ?
[03:00] <CMEE_fie> but the drive is working, i just restarted a moment ago again into my installed lubuntu 16.04 and i can see there both of my drives
[03:00] <CMEE_fie> Bashing-om: one sec
[03:02] <CMEE_fie> i see the toshiba drive on /dev/sda: 1,8 TiB, i see the usb stick on /dev/sdb: 7,5 GiB, then there's something on /dev/sdc: 3,7 GiB. not sure what that 3,7 drive is
[03:02] <CMEE_fie> and then three /dev/zram
[03:03] <CMEE_fie> no sight of my western digital 500GB
[03:03] <CMEE_fie> on dmesg i see "ata4: reset failed, giving up"
[03:03] <CMEE_fie> i've never seen that before
[03:04] <CMEE_fie> i also see "ata4: link is slow to respond, please be patient (ready=0)" and "ata4: COMRESET failed (errno=-16)". but i've had those messages since i bought the western digital
[03:04] <CMEE_fie> the western digital seem slow to turn on
[03:06] <CMEE_fie> kernel seem to still be trying to mount ata4 but failing. ill upload the relevant log on pastebin
[03:07] <CMEE_fie> http://pasteall.org/911310
[03:07] <CMEE_fie> went for pasteall tho :P
[03:07] <Bashing-om> CMEE_fie: reading . back soonest .
[03:09] <CMEE_fie> you might notice some of the message repeat again and again, they are still repeating with more recent timestamps, meaning the kernel is still* trying to mount the drive
[03:11] <CMEE_fie> btw, the WB drive had never taken this* long to be mounted before, usually takes 2 minutes and then is mounted before* the desktop show up
[03:12] <Bashing-om> CMEE_fie: Right off hand I would say the drive is dieing/dead . What does SMART relate about the health of the drive ? Might also ask in the #hardware channel .
[03:13] <CMEE_fie> SMART hasn't given any warning or error so far, the firmware might be faulty tho
[03:14] <CMEE_fie> that's why i bought the toshiba, but i intended to keep using the Western Digital as a backup
[03:14] <Bashing-om> CMEE_fie: Could be a number of things else - like sata cable, connections or the port .. Alk we know presently is that the system can not bring the drive up .
[03:15] <CMEE_fie> Would you say i can discard systemd and the problem is most probably the kernel if not the hardware?
[03:15] <Bashing-om> CMEE_fie: No comsolation, but I have have 3 WD drives here recently with the same issues . I have replaced them .
[03:17] <CMEE_fie> with same issues you mean slow to turn on and messages of "COMRESET failed" or unable to be mounted at all?
[03:19] <Bashing-om> CMEE_fie: " COMRESET failed (errno=-16) " I have beem able to temporatily resurrect by repaiting the file system and sparing off the super block - in my case . You are advised to get other opinions .
[03:20] <CMEE_fie> In other words: move everything to the toshiba ASAP :P
[03:21] <Bashing-om> CMEE_fie: I sure would ! safty is no accident .
[03:23] <Bashing-om> CMEE_fie: In all fairness - I had issues with 2 drives *after* installing a SSD and enabling AHCI . I have not tested those drives in other systems .
[03:25] <CMEE_fie> maybe testing lubuntu 17.04 is worth doing
[03:25] <CMEE_fie> i mean 17.10
[03:27] <valorie> offtopic here, CMEE_fie
[03:28] <CMEE_fie> exactly, on the bright side if the issue happen there i can ask on the channels for already released versions, thanks for everything Bashing-om
[03:29] <Bashing-om> CMEE_fie: :)
[03:54] <BionicMac> Multitudes of upgrades today. The Beaver is running like a charm over here.
[04:01] <valorie> same here
[04:01] <valorie> haven't restarted yet though
[04:01] <valorie> after the upgrades
[04:13] <BionicMac> Same here. 
[04:16] <BionicMac> Installed Ubuntu Server 17.10 on an ancient machine today. No X. Samba/Dns/Gateway/dhcpd/ etc etc. Put some life back in that old box.
[04:48] <Bashing-om> flocculant: "want to check if the fontconfig update......." I got the update, what do you need for verification ?
[04:49] <flocculant> Bashing-om: I actually need to check the iso and first boot post install - thanks for offering though :)
[04:49] <lotuspsychje> morning flocculant 
[04:49] <flocculant> morning lotuspsychje :)
[04:51] <lotuspsychje> new systemd in updates im curious :p
[05:00] <lotuspsychje> loading to desktop still slow
[05:01] <lotuspsychje> lotuspsychje@R00TBOOK:~$ systemd-analyze blame
[05:01] <lotuspsychje>           8.966s dev-sda1.device
[05:01] <lotuspsychje>           8.098s NetworkManager-wait-online.service
[05:01] <lotuspsychje>           1.967s dev-loop2.device
[05:01] <lotuspsychje>           1.951s dev-loop1.device
[05:01] <lotuspsychje>           1.927s dev-loop0.device
[05:01] <lotuspsychje>           1.894s dev-loop3.device
[05:01] <lotuspsychje>           1.860s dev-loop4.device
[05:01] <lotuspsychje> seems like snaps also booting time
[05:02] <lotuspsychje> lets unstall a few
[05:02] <flocculant> good plan :p
[05:04] <flocculant> corresponding dev-x.device here is 281ms
[05:04] <lotuspsychje> whats that
[05:05] <flocculant> I assume you're installed on /dev/sda1 and 8.966s - installed on /dev/sdb5 here and 281ms
[05:06] <lotuspsychje> ah
[05:06] <lotuspsychje> flocculant: no ssd?
[05:06] <flocculant> though maybe hdd vs ssd
[05:06] <lotuspsychje> im on 850 pro of samsung, thats why i want it speed :p
[05:06] <flocculant> hah - that'd do it I guess
[05:07] <Bashing-om> lotuspsychje: 1.167s dev-sdb1.device
[05:07] <flocculant> oh - I'm on some samsung ssd - I assume you weren't
[05:07] <lotuspsychje> nono :p
[05:08] <lotuspsychje> i am :p
[05:08] <lotuspsychje> makes it even stranger...
[05:08] <lotuspsychje> why 8sec
[05:08] <flocculant> yea - but that blame thing never really seems to make much sense to me anyway lol
[05:11] <Bashing-om> sysop@x1804mini:~$ systemd-analyze >> Startup finished in 4.539s (kernel) + 3.596s (userspace) = 8.135s ; graphical.target reached after 3.571s in userspace .
[05:11] <lotuspsychje> Startup finished in 6.680s (kernel) + 12.731s (userspace) = 19.412s
[05:11] <lotuspsychje> graphical.target reached after 12.684s in userspace
[05:12] <lotuspsychje> but your on mini Bashing-om 
[05:12] <lotuspsychje> cheat :p
[05:12] <flocculant> lol
[05:13] <lotuspsychje> did you guys install preload?
[05:13] <flocculant> not that I'm aware of
[05:18] <flocculant> Bashing-om: well - boot to desktop on live looks a whole lot better now with that updated package \o/
[05:19] <lotuspsychje> ah this looks more usefull
[05:19] <lotuspsychje> systemd-analyze critical-chain
[05:20] <Bashing-om> flocculant: That " graphical.target reached after 3.571s in userspace" of mine irks me just a tad . Enter password and have to wait then for the DE to start  . I have not looked to this time to see what is going on .
[05:24] <lotuspsychje> ok new reboot
[05:24] <flocculant> well I have to wait - not long though
[05:24] <flocculant> Bashing-om: ^^
[05:26] <Bashing-om> flocculant: Not a big deal , just a wait in 18.04 that is not present on 16.04 boot .
[05:27] <flocculant> Bashing-om: in fact probably about a second
[05:28] <lotuspsychje>  21.115s plymouth-quit-wait.service
[05:28] <lotuspsychje> jesus
[05:28] <flocculant> that'll help
[06:11] <Bashing-om> rebooting the physical half - back in a few hours :)
[06:42] <CMEE_fie> hello i was here some hours ago, i was having trouble with the final beta of lubuntu 18.04, and i think it was BionicMac who mention that he started having issues when he enabled AHCI
[06:43] <CMEE_fie> a friend also suggested me changing the sata mode from AHCI to IDE, so i went to the bios but IDE was already the mode for SATA in the bios
[06:44] <CMEE_fie> so just for testing i changed the sata mode to AHCI, and for some reason the bios doesn't seem to recognize the Western Digital formated with MBR
[06:44] <CMEE_fie> i can boot with the WB, but i can with the toshiba
[06:45] <CMEE_fie> and once the lubuntu 17.10 i have on the toshiba loads i can actually use the WB drive
[06:45] <CMEE_fie> and BTW i dont have any drive issues on lubuntu 17.10 with either IDE or AHCI
[06:46] <CMEE_fie> so the issue is truly limited to lubuntu 18.04 beta2
[06:50] <CMEE_fie> i haven't tried lubuntu 18.04 + ahci tho, and i can't until tomorrow, dont ask why im an idiot
[07:34] <Ian_Corne> maxb: did you find a solution?
[07:34] <Ian_Corne> if not, to wich package would you log a bug? I'm having a touchpad issue as well
[08:29] <Exterminador> hello guys. I'm facing a weird issue. suddenly my volume buttons stopped working (even Fn + arrow up/down). any ideas where to gather more info or what the problem can be?
[08:57] <alkisg> Run xev and see if it gets the events; also try with an older kernel
[09:08] <Exterminador> alkisg: here's what I've got running xev: http://paste.ubuntu.com/p/m6s55hK4QD/
[09:09] <Exterminador> all the keys seems to be zeroed
[09:19] <Exterminador> weird. kernels 4.15.0-12-generic and 4.15.0-13-generic have this issue (on Xubuntu, btw)..
[09:34] <Exterminador> I'm updating the other install of Ubuntu main and I'll see if the problem persists. otherwise can be something related to xfce?
[09:58] <Exterminador> okay. this is weird. on main Ubuntu, volume buttons work with kernel 4.15.0-13-generic, but not in Xubuntu with the same kernel. thoughts?
[09:59] <flocculant> can you reproduce this will the daily? http://cdimage.ubuntu.com/xubuntu/daily-live/current/
[10:00] <flocculant> alternatively add a test user - login in there and see if you can reproduce it
[10:06] <Exterminador> it happens with all the users I've on the laptop. I just updated the OS today, in both distros
[10:06] <flocculant> and worked previously?
[10:09] <Exterminador> yep. it keeps working in the main distro but not in Xubuntu. sometimes you press volume buttons, it does nothing and after a while the volume decrease/increase without visual output. like, after a few minutes
[10:09] <flocculant> no
[10:10] <flocculant> did it work previously in xubuntu?
[10:10] <Exterminador> yes, it did
[10:11] <flocculant> and now after updates it doesn't? if that's the case check in /var/log/apt/history.log for what's been updated
[10:19] <Exterminador> flocculant: this is what i have in /var/log/apt/history.log - http://paste.ubuntu.com/p/ffNHBYVc9P/
[10:20] <flocculant> and it last worked when?
[10:21] <flocculant> ugh
[10:21] <flocculant> so you added most of kubuntu then?
[10:22] <flocculant> can we go back to checking it on a daily?
[10:22] <Exterminador> i can't try it now, as i have no usb/cd and no more partitions to install :x
[10:23] <lotuspsychje> welcome AlexMao 
[10:23] <AlexMao> lotuspsychje, Thanks
[10:23] <AlexMao> Anyone running into issues with the ubiquity/installer on the latest/final beta ? 
[10:23] <Exterminador> and i didnt explicitly added anything related to Kubuntu.. I've upgraded from Xubuntu 16.04.3 to 18.04
[10:24] <lotuspsychje> AlexMao: whats happening exactly mate?
[10:24] <lotuspsychje> Exterminador: its not reccomended yet to upgrade from xenial
[10:24] <flocculant> Exterminador: you added plasma desktop
[10:25] <Exterminador> flocculant: i guess i installled it to use with something else. but i can uninstall it
[10:25] <lotuspsychje> Exterminador: we reccomend if you help test daily, you install a daily live iso
[10:25] <flocculant> mmm
[10:25] <AlexMao> Well simply put the installer crashes each time I try to install lubuntu on a spare machine. I get passed the partition process, the initial installation process begins. At some point near the end the installer crashes. 
[10:26] <lotuspsychje> AlexMao: have you tryed another machine if you can reproduce this?
[10:26] <Exterminador> lotuspsychje: I know. but I like to live on the edge :)
[10:26] <AlexMao> I've gone through the launchpad reports and it appears to be a known issue, one post suggested updating the installer but that was a bit odd. 
[10:27] <lotuspsychje> Exterminador: i know, but the problem is we cant properly help you, if we dont know if its real bug or a leftover from a wrong upgrade
[10:27] <AlexMao> I can try another machine certainly, but to note I've tried different copies of the ISO as well in case I botched something during download and/or DD-ing it to a usb 
[10:28] <Exterminador> lotuspsychje: I've upgraded at almost one month. so, I assume isn't a leftover
[10:28] <lotuspsychje> flocculant: you know who to poke for lubuntu dailys?
[10:28] <flocculant> Exterminador: so when did it stop working?
[10:28] <flocculant> still don't know that ;)
[10:28] <flocculant> lotuspsychje: tsimonq2 or wxl wherever he's hiding
[10:29] <lotuspsychje> Exterminador: again, its not yet advisable for upgrading lts to lts
[10:29] <lotuspsychje> flocculant: tnx
[10:29] <Exterminador> flocculant: well, I've noticed it today. can't give you a correct date, because on Stremio I use the built-in volume control
[10:29] <lotuspsychje> tsimonq2: lubuntu= <AlexMao> Anyone running into issues with the ubiquity/installer on the latest/final beta ? 
[10:30] <flocculant> AlexMao: how does it actually fail? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754174
[10:30] <flocculant> that one?
[10:32] <AlexMao> not that one. 
[10:32] <flocculant> Exterminador: well - not sure then, assumign it worked post-upgrade then I now don't know how plasma would impact
[10:32] <flocculant> AlexMao: does the installer tell you anything at all or does it just crash?
[10:32] <Exterminador> will a sd card suffice to try those daily installs?
[10:33] <lotuspsychje> Exterminador: think ubuntu needs 8gig
[10:33] <flocculant> and xubuntu about the same 
[10:33] <flocculant> cos that's what we're talking about :D
[10:33] <Exterminador> oh damn. mine is just 4Gb
[10:33] <flocculant> oh hang on
[10:33] <AlexMao> let me set up the other machine and start the process. if/when it crashes I'll chime in here. 
[10:33] <flocculant> if you can get the iso on there it should boot
[10:34] <lotuspsychje> AlexMao: tnx for testing, perhaps add yourself to the bug?
[10:34] <flocculant> Exterminador: ^^ 
[10:34] <flocculant> AlexMao: this was normal lubuntu not the Next thing?
[10:35] <flocculant> Exterminador: so try it 
[10:35] <AlexMao> this is the beta that was released yesterday/day-before-yesterday. I had similar issues with previous version of the 18.04 release as well 
[10:36] <flocculant> AlexMao: ok - well I think they've had some issues - but hard to know until we've some idea of what the error actually is
[10:37] <flocculant> it should if it dies - start the desktop and report the bug - or I've seen that at least
[10:38] <lotuspsychje> AlexMao flocculant good idea choose 'try ubuntu' and let ubiquity debug from there, open a syslog:dmesg tail to see whats going on?
[10:38] <lotuspsychje> try lubuntu in your case
[10:38] <flocculant> :p
[10:41] <Exterminador> I'll download the daily build and see
[10:41] <lotuspsychje> Exterminador: tnx
[10:43] <lotuspsychje> !info firefox 
[10:43] <Exterminador> my internet is a pita. it downloads only at 1.6Mbps. so, after downloading, how do I make a bootable USB (I've found one)?
[10:43] <lotuspsychje> !usb | Exterminador 
[10:43] <Exterminador> tks
[10:44] <flocculant> lotuspsychje: I grabbed ff 59.0.2 from proposed this morning
[10:44] <lotuspsychje> Exterminador: i very like the ubuntu media usb creator
[10:44] <lotuspsychje> flocculant: cool!
[10:44] <flocculant> I use gnome-disk-utility or whatever it's called 
[10:44] <lotuspsychje> yeah thats the one
[10:44] <lotuspsychje> pretty fast and decent
[10:46] <lotuspsychje> flocculant: shows in my updates Instellen van firefox (59.0.2+build1-0ubuntu1) 
[10:46] <Exterminador> installing :D
[10:47] <AlexMao> Installer crashed: We're sorry. the installer crashed. After you close this window, we will aloow you to file a bug report using the integrated bug reporting tool. This will gather information about your systemand your installation process. The details will be sent to our bug tracker and a developer will attend to the problem as soon as possible.  
[10:48] <AlexMao> It occurred as the installation process was beginning. 
[10:48] <lotuspsychje> AlexMao: yeah see if you can grab the details of the bug it creates
[10:49] <Exterminador> is it named Disks after install? or isn't compatible with Xubuntu?
[10:49] <flocculant> well I assume that it would open ubuntu-bug - then web browser
[10:49] <flocculant> Exterminador: yea that's it
[10:50] <Exterminador> okay, i need to let it finish download the iso
[10:50] <Exterminador> then i must see how to create the usb using that tool
[10:50] <flocculant> select the CORRECT drive in the left pane - then from the menu use Restore Disk Image
[10:51] <Exterminador> aight.. ty
[10:51] <flocculant> Exterminador: https://i.imgur.com/x3WXumq.png
[10:53] <flocculant> AlexMao: did it do anything? 
[10:54] <lotuspsychje> flocculant: lol look at this guy :p https://www.deviantart.com/art/Unity-1-739160105
[10:55] <flocculant> heh
[10:55] <Exterminador> does it auto format the USB?
[10:55] <flocculant> Exterminador: yea it''ll do what's needed
[10:55] <Exterminador> all my life I've used Rufus to do the usb thingy
[10:56] <flocculant> all my life I've never heard of it :p
[10:56] <lotuspsychje> lol
[10:56] <Exterminador> never created a USB from within (X)Ubuntu itself
[10:57] <flocculant> probably done it about 200 times during this 6 month cycle :p
[10:57] <flocculant> I really should have more than 1 
[10:57] <Exterminador> :o that's a lot
[10:57] <lotuspsychje> :p
[10:58]  * lotuspsychje has a whole box of ubuntu usb's
[10:58]  * flocculant really should go back to just having iso's listed in grub menu
[10:59] <flocculant> as I mostly just want to boot them to test something
[10:59] <lotuspsychje> !info gnome-disk-utility | adviced by flocculant 
[10:59] <flocculant> :P
[10:59] <Exterminador> erm.. my USB is only 4Gb too. will that be enough?
[11:00] <lotuspsychje> Exterminador: yes that will work
[11:00] <lotuspsychje> Exterminador: ubuntu needs 8 gig+ install space on target
[11:01] <lotuspsychje> Exterminador: your not gonna install on your usb right?
[11:01] <flocculant> even if they were - xubuntu needs about the same ;)
[11:01] <lotuspsychje> bbl citywalk, sunny 22 degrees
[11:01] <lotuspsychje> laterz flocculant 
[11:02] <flocculant> lotuspsychje: cya - cloudy here in UK
[11:03] <Exterminador> in progress.. also, installing into removable devices isn't advised, right? :p
[11:04] <flocculant> well some people do it - I have rarely for specific reasons - but slow ... 
[11:08] <Exterminador> booting into the USB (was pretty fast to create the USB). Try Xubuntu?
[11:08] <flocculant> yea
[11:09] <flocculant> Exterminador: then check out the volume keys 
[11:09] <Exterminador> I've borked something on my main install. for sure.. it's working on the daily one
[11:10] <Exterminador> I assume I can't reinstall and keep the current data?
[11:10] <flocculant> ok
[11:10] <flocculant> right hang on and give me a moment to mull that over
[11:12] <Exterminador> while on that I'm going to eat something
[11:14] <Exterminador> it must have been one of those packages I've installed. I've removed plasma and no cigar (I don't remember why did I installed it :x)
[11:15] <flocculant> Exterminador: by current data - do you mean things you have in your /home folders?
[11:16] <flocculant> or things you've installed?
[11:17] <flocculant> you can keep your local data but not the latter
[11:17] <Exterminador> well, most of the things I can reinstall. the important is the /home
[11:18] <flocculant> yea you can keep that
[11:19] <Exterminador> still, I've installed xorg-server and nouveau-firmware (because that little issue with Nvidia drivers). can it be related?
[11:19] <flocculant> doubtful
[11:21] <flocculant> Exterminador: when you removed plasma did it remove all the things it installed?
[11:21] <Exterminador> it must have been something on the last 2 days. my son was watching YouTube videos in the middle of the week and volume was working.
[11:22] <Exterminador> flocculant: I've done "apt remove --purge plasma*"
[11:23] <AlexMao> This is a bit strange. I booted into the live environment, opened the terminal ran an apt update && apt dist-upgrade (as sudo), ran the installer and now it's installing the system. (so far). 
[11:24] <flocculant> right - hard to know if it removed everything from here :p check your paste http://paste.ubuntu.com/p/ffNHBYVc9P/plain/ did it remove all the things in the big list from Start-Date: 2018-04-06  20:51:16 ?
[11:24] <flocculant> Exterminador: ^^
[11:24] <flocculant> AlexMao: ok - good to know
[11:24] <Exterminador> I'll check it now
[11:24] <Exterminador> booting into the system
[11:24] <Exterminador> (and eating)
[11:24] <flocculant> AlexMao: did it do a bug report? 
[11:25] <flocculant> Exterminador: everytime you say that I remember I'm hungry :(
[11:25] <AlexMao> In the previous attempt yes. 
[11:26] <Exterminador> flocculant: just imagine I didn't said anything. :p
[11:26] <AlexMao> This time round no crashes after updating the live environment and running the installer 
[11:27] <flocculant> Exterminador: are you in the usb or on the installation?
[11:28] <Exterminador> flocculant: installation now.
[11:29] <Exterminador> flocculant: do you want to know? I've done again "apt remove --purge plasma*".. it uninstalled a ton of things.. and suprise!!!
[11:30] <Exterminador> volume keys works again!
[11:31] <flocculant> hah
[11:31] <flocculant> awesome
[11:32] <Exterminador> so, we've found the culprit :)
[11:32] <Exterminador> thanks for bearing with me ;)
[11:32] <flocculant> Exterminador: I'll tell you a useful thing, this was my next suggestion - open the file manager and make sure you can see hidden . files and folders
[11:33] <Exterminador> I can, when using Ctrl + h
[11:33] <flocculant> open .cache and you'll see an xfce4 folder in there (also in .config) that's where the most of the things 'you' do personally to xfce land - so removing those can prove issues
[11:33] <flocculant> pretty much sends you back to a default setup
[11:34] <flocculant> anyway - all that aside - you found the issue :)
[11:35] <Exterminador> next time I must remember "do not install plasma again".
[11:38] <HarkalyG> Hi, I'd like to know if I install Ubuntu 18.04 beta2 will it automatic upgrade to it's final version at the end of April?
[11:38] <alkisg> Yes
[11:39] <flocculant> as long as you update it 
[11:40] <flocculant> Exterminador: back in the past I did similar - I then found it much better to have different installations
[11:41] <flocculant> AlexMao: all sorted now then?
[11:41] <Exterminador> yeah. but my poor laptop is in EOL already (at least the HDD). 9y of constant rewrite
[11:42] <flocculant> :)
[11:43]  * flocculant goes to finally eat something now ;)
[11:43] <Exterminador> I've started to use *Ubuntu last year. I'm loving it!
[11:43] <Exterminador> enjoy the meal!
[11:43] <flocculant> cool - gald to hear it - better to see Xubuntu though ;)
[11:44] <Exterminador> I have both (Xubuntu and Ubuntu) along Windows 10 (for some games only)
[11:44] <HarkalyG> Thanks
[11:57] <AlexMao> flocculant, all sorted now 
[12:00] <flocculant> \o/
[12:02]  * tsimonq2 stretches
[12:02] <tsimonq2> What's up?
[12:10] <flocculant> nothing now - all dealt with :p
[12:24] <tsimonq2> Cool.
[14:06] <lotuspsychje> landspite: here you can try it already on daily image in beta stage
[14:06] <lotuspsychje> till final release
[14:11] <AlexMao> has there been any indication when ubuntu (canonical) or lubuntu will roll out lxqt as the default DE for lubuntu ? 
[14:16] <lapaga> ...but in the case of Lubuntu Next, which is based on the very much work-in-progress LXQt desktop, those daily builds will likely be quite buggy.
[14:21] <AlexMao> I suppose the silly question is what's taking so long for the transition to occur? LXQT is rather stable under Debian 8 + 9. 
[14:31] <alkisg> Maybe with the switch to wayland, desktop environments can't find enough programmers to keep up with all the changes...
[14:32] <alkisg> And maybe only the big ones (gnome/kde) will survive)
[14:32] <lotuspsychje> hey alkisg 
[14:32] <alkisg> Hey lotuspsychje, how's everything?
[14:32] <lotuspsychje> great, playing bionic hard here :p
[14:33] <alkisg> I've had deployments in schools since 3 months now
[14:33] <alkisg> Since february it's been mostly OK
[14:33] <lotuspsychje> neat
[14:33] <lotuspsychje> burning lubuntu 32 bit bionic right now
[14:33] <lotuspsychje> testing on customers laptop
[14:34] <lotuspsychje> i love normal/mini option at setup
[14:34] <alkisg> I think mate, if one removes snapd etc, is pretty much as light as lubuntu, and a LOT more mature
[14:34] <AlexMao> I noticed on the most recent version of Lubuntu there was a minimal install option browser + basic utils. I thought that was a nice touch 
[14:35] <alkisg> Lubuntu doesn't even implement inhibitors, one can just logout and lose all unsaved work...
[14:38] <lotuspsychje> flocculant tsimonq2 confirming lubuntu daily iso crashes ubiquity at the end of setup with squashfs errors spam
[14:39] <tsimonq2> lotuspsychje: And this is from Try Lubuntu?
[14:39] <lotuspsychje> tsimonq2: no, install lubuntu
[14:40] <tsimonq2> lotuspsychje: known bug
[14:40] <AlexMao> About the crashing, and forgive my ignorance, but how does updating the live environment correct everything to the point where I can install the beta? 
[14:40] <lotuspsychje> tsimonq2: got the url?
[14:40] <tsimonq2> lotuspsychje: flocculant linked it a few hours ago, otherwise I can try to find it...
[14:41] <lotuspsychje> tsimonq2: well i gues if its known already, nvm will it work from try lubuntu?
[14:41] <tsimonq2> lotuspsychje: yep
[14:41] <lotuspsychje> cool lets test
[14:41] <tsimonq2> alkisg: What do you mean by "inhibitors"?
[14:42] <lotuspsychje> AlexMao: what do you mean exactly?
[14:42] <tsimonq2> AlexMao: The LXQt transition is closer than one might think, I'll just say that.
[14:43] <AlexMao> this was referring to my previous issue with installing lubuntu final beta 
[14:43]  * tsimonq2 goes AFK for a bit.
[14:47] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754174
[15:14] <alkisg> tsimonq2: logout inhibitors is an API for applications to tell the system NOT to allow log out because they have unsaved data
[15:14] <tsimonq2> alkisg: Link?
[15:14] <alkisg> So for example when you try to logout from gnome, libreoffice blocks that, and prompts "do you want to save first"?
[15:14] <alkisg> tsimonq2: https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.Inhibitor
[15:15] <tsimonq2> alkisg: Any Qt links?
[15:15] <alkisg> tsimonq2: I don't know how they're called in KDE
[15:16] <tsimonq2> alkisg: ok
[15:16] <tsimonq2> Thank you, I'll look into it.
[15:16] <alkisg> np
[15:16] <alkisg> It was just an example, that lighter DEs are missing things
[15:16] <tsimonq2> Yeah.
[15:16] <alkisg> And that DEs that are more mature, of course also offer more
[15:17] <alkisg> Another could be "automatic printer installation"
[15:17] <tsimonq2> Does e.g. Ubuntu MATE have that?
[15:17] <alkisg> Yes, since gnome2 had that, mate has it as well
[15:17] <tsimonq2> OK.
[15:17] <alkisg> mate is mature just because gnome2 was mature, not so much because of its current developers
[15:18] <lapaga> right now i have sda1(win), sda2(win), sda3 (swap),sda4(extended),sda5(/),sda6(/home) I am going to wipe out 3,4,5,6 and install 18.04...can I not have swap partition ?
[15:18] <alkisg> AFAIK if you have a swap partition, it sees it and doesn't create a swap fie
[15:18] <alkisg> *file
[15:18] <tsimonq2> lapaga: Why do you need it?
[15:18] <tsimonq2> And, right.
[15:19] <lapaga> I have 12g ram so have never had it use it
[15:20] <alkisg> Ah, you want to have neither a swap partition nor a swap file; sure, you can do that, I'm not sure if the installer allows it or if you need to remove it after the installation...
[15:20] <alkisg> It doesn't hurt though
[15:20] <lapaga> and if no swap then would not have to make extended partition
[15:23] <alkisg> Well the default installation gives you a swap file
[15:23] <alkisg> So no swap partition, so no need for extended
[15:24] <lapaga> ok-just have always made one
[15:48] <lotuspsychje> tsimonq2: confirmed it installed thru try lubuntu, tnx alot
[16:57] <lotuspsychje> lubuntu 18.04 32bit working like a charm on that box
[16:58] <lotuspsychje> nice wallpaper too
[16:58] <tsimonq2> \o/
[16:59] <lotuspsychje> tsimonq2: great work mate :p
[17:00] <BenLubar> not sure if this is an Ubuntu question or a VirtualBox question, but is there any way I can have an Ubuntu VM release memory back to the host OS? Rebooting doesn't do it; I need to shut down the VM and start it back up to get memory back when the VM isn't using it.
[17:00] <tsimonq2> lotuspsychje: Thanks!
[17:00] <BenLubar> In this case, the VM is a build slave, but the host is my gaming machine, so I'd like to be able to reclaim the memory when I'm not using the VM to compile stuff
[17:01] <tsimonq2> BenLubar: I don't think Virtualbox will let you do that.
[17:41] <mifritscher> moin
[17:42] <mifritscher> how can I debug "Apr  7 19:21:33 server /usr/lib/gdm3/gdm-wayland-session[13642]: dbus-daemon[13644]: [session uid=108 pid=13644] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1" after a upgrade to ubuntu 18.04?
[17:42] <mifritscher> this message is produced by gdm3, thus no graphical login - but ssh is possible
[17:42] <lotuspsychje> mifritscher: we dont reccomend upgrading to bionic yet in this stage
[17:42] <lotuspsychje> mifritscher: bionic is still in beta stage atm
[17:42] <mifritscher> I know ;)
[17:43] <lotuspsychje> mifritscher: so best to help us, is installing daily live iso, and see if you can reproduce
[17:43] <mifritscher> I upgraded another machine yust today without problems ;-)
[17:44] <mifritscher> I assume it has something to do with the old installation
[17:44] <lotuspsychje> mifritscher: this is just why we dont reccomend, as we cant know if its a real bug, or a leftover from previous install
[17:46] <mifritscher> I had some problems with systemd-shim regarding a link (/usr/share/dbus-1/services/org.freedesktop.systemd1.service and usr/share/dbus-1/services/org.freedesktop.systemd1 I think)
[17:47] <mifritscher> lotuspsychje: I know it was a bit dangerous and so on, I yust need to have some help to get further (debug) infos ;)
[17:48] <mifritscher> I made a apt install --reinstall systemd, but didn't help
[17:48] <mifritscher> I think something is broken here
[17:48] <lotuspsychje> !info systemd
[17:49] <mifritscher> same version as mine
[17:49] <lotuspsychje> mifritscher: perhaps try this in a liveusb? see if you can reproduce?
[17:49] <mifritscher> systemctl --user says "Failed to connect to bus" while is working on other system (also a upgraded 18.04 installation)
[17:49] <mifritscher> lotuspsychje: another upgrade with exactly the same version is working
[17:50] <mifritscher> so something is different on this machine
[17:50] <mifritscher> big question: What? ;-)
[17:51] <lotuspsychje> mifritscher: you could try fix broken packages option from recoverymode
[17:51] <lotuspsychje> mifritscher: did your previous system have external ppa's?
[17:52] <mifritscher> yes, but removed & cleaned them (were only user mode applications, no drivers or system things)
[17:52] <mifritscher> I've no broken packages atm
[17:52] <lotuspsychje> kk
[17:53] <lotuspsychje> out of ideas myself then, i guess would affect different users too
[17:53] <mifritscher> all seems to be fine but something around systemd/dbus
[17:53] <lotuspsychje> (on your system)
[17:54] <mifritscher> problem: it happens before login
[17:54] <mifritscher> yust at the moment gdm is starting
[17:54] <mifritscher> I get this message right after restarting gdm3 as well
[17:55] <mifritscher> (in /var/log/syslog)
[17:56] <lotuspsychje> mifritscher: you got docker installed?
[17:56] <mifritscher> nope
[17:58] <lotuspsychje> mifritscher: related? https://answers.launchpad.net/ubuntu/+source/systemd/+question/287454
[18:00] <mifritscher> it is the right direction, yes
[18:04] <mifritscher1> ok, after reinstalling dbus and dbus-user-session it seems to work again :-)
[18:05] <lotuspsychje> !yay | mifritscher1 
[18:05] <lotuspsychje> did that bug help you?
[18:05] <mifritscher1> honestely no, it was more or less a wild guess *g*
[18:06] <mifritscher1> I knew that there is somewhere a problem between systemd and dbus (also because of the name "/usr/share/dbus-1/services/org.freedesktop.systemd1.service")
[18:06] <mifritscher1> so first I looked after reinstalling systemd
[18:06] <lotuspsychje> cool
[18:07] <mifritscher1> and after a while I thought "hmm, what packages with dbus in it are there?"
[18:08] <mifritscher1> and dbus-user-session has the description "simple interprocess messaging system (systemd --user integration)" - bingo :-D
[18:08] <mifritscher1> if that hadn't worked I had examined this package a bit further
[18:08] <mifritscher1> probably my "fix" regarding this link was not that right
[18:08] <mifritscher1> and broke things
[18:14] <mifritscher1> now a bit housekeeping - aka removeing orphaned packages^^
[18:15] <mifritscher1> hehe, firefox in 16.04 is a bit newer than in 18.04
[18:16] <lotuspsychje> !info firefox xenial
[18:16] <lotuspsychje> mifritscher1: you mean on your system?
[18:16] <mifritscher1> in the repos
[18:17] <lotuspsychje> !info firefox
[18:17] <lotuspsychje> same
[18:17] <mifritscher1> hmm, ok, then my mirror is old
[18:17] <mifritscher1> on xenial I've 59.0.2, on bionic 59.0.1
[18:17] <lotuspsychje> update bionic :p
[18:18] <mifritscher1> I made a apt update; apt dist-upgrade 30 seconds before *g*
[18:18] <lotuspsychje> then something is wrong
[18:19] <lotuspsychje> got the FF update this morning here
[18:19] <mifritscher1> perhaps my mirror updates bionic not so regular than xenial
[18:20] <lotuspsychje> try sudo apt update && sudo apt full-upgrade
[18:27] <mifritscher1> ohoh - Use of uninitialized value $buf in concatenation (.) or string at /usr/bin/debmirror line 2163, <RELEASE> line 1.
[18:28] <mifritscher1> I think I need to fix this before I get further updates *g*
[18:28] <lotuspsychje> :p
[18:28] <lotuspsychje> you might wanna choose daily iso next time
[18:29] <mifritscher1> hmm, it seems that there are pubic keys messing
[18:29] <mifritscher1> /me don't know when he used isos at home the last time
[18:30] <mifritscher1> I always install per pxe-boot and local mirror, which in turn is updated against one official mirror all few hours ;)
[18:32] <mifritscher1> but
[18:32] <mifritscher1> gpgv: Korrekte Signatur von "Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>"
[18:32] <mifritscher1> .temp/.tmp/dists/xenial/Release.gpg signature does not verify.
[18:32] <mifritscher1> indicates really that the mirror I use for debmirror has a problem
[18:32] <mifritscher1> interestingly only xenial, bionic is ok
[18:37] <mifritscher1> hmm, same happens with de.archive.ubuntu.com
[19:07] <mpb> Hello.  I am trying Ubuntu 18.04 beta2 on my Acer Aspire One laptop with AMD graphics.  Graphics is failing.  I get text/console login, but no graphical desktop.  I did get to a graphical desktop once, not sure how/why, but the keyboard and touchpad were frozen.  Is there somewhere I can report this problem and/or help diagnose the cause.
[19:09] <lotuspsychje> mpb: are you on the xorg or wayland session?
[19:09] <lotuspsychje> mpb: im running 18.04 fine on acer aspire one here
[19:09] <mpb> lotuspsychje:  I just booted the live ISO off of a usb stick.  So whatever the default is from live ISO.
[19:10] <lotuspsychje> Client: HexChat 2.14.1 • OS: Ubuntu "bionic" 18.04 • CPU: AMD C-60 APU with Radeon(tm) HD Graphics (1,03GHz) • Memory: Physical: 3,5 GiB Total (2,3 GiB Free) Swap: 2,0 GiB Total (2,0 GiB Free) • Storage: 72,3 GB / 129,5 GB (57,3 GB Free) • VGA: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] @ Advanced Micro Devices, Inc. [AMD] Family 12h/14h Processor Function 5 •
[19:10] <lotuspsychje>  Uptime: 5h 57m 23s
[19:10] <lotuspsychje> mpb: did you choose try or install ubuntu?
[19:12] <mpb> lotuspsychje: I chose "try".
[19:12] <lotuspsychje> mpb: nevermind, you might wanna install ubuntu
[19:12] <lotuspsychje> mpb: you did not change bios settings ahci or ide?
[19:14] <mpb> lotuspsychje: The live ISOs for 16.04 and 17.10 work fine on the same laptop.  I can try an install, if you think that will make a difference.  In the past, I have always done "try" and then installed from the live session.  I'm not sure about the bios settings at present, but 17.10 works fine.
[19:14] <lotuspsychje> mpb: ok tnx for details
[19:15] <lotuspsychje> mpb: at wich point does your system freeze exactly?
[19:17] <mpb> I can get to text consoles, so it is not a freeze, just no graphics.  If I turn of "quiet" and "splash", the last message that appears on console #1 is: "Started User Manager for UID 999."  I have the laptop running right now, and installed openssh-server, so I can look at any log files, if you want.  I also tried restarting GDM3.  GDM3 seems to go into a loop, writing lots of messages to syslog.
[19:18] <mpb> lotuspsychje:  did my previous message come through okay?  I can only see the end of it.
[19:20] <lotuspsychje> mpb: yeah got it
[19:21] <mpb> The model of my Acer Aspire One laptop is: 722-BZ454, manufactured Nov 2011, 2GB ram.
[19:21] <lotuspsychje> mpb: got also radeon card?
[19:21] <lotuspsychje> [AMD/ATI] Wrestler [Radeon HD 6290 is mine
[19:22] <mpb> from dmesg: fbcon: radeondrmfb (fb0) is primary device
[19:24] <mpb> lotuspsychje: I'm not sure where to look to see the model of the GPU.  I'm not sure if it is an APU (on the same chip as the CPU).
[19:24] <lotuspsychje> mpb: sudo lshw -C video shows driver active?
[19:25] <mpb> lotuspsychje: product: Wrestler [Radeon HD 6250]
[19:25] <Bashing-om> mpb: Set trust ? https://ubuntuforums.org/showthread.php?t=2333630 <- oldfred : Ubuntu on Acer Aspire new Laptop .
[19:31] <mpb> Bashing-om: why would the Acer "trust" setting prevent graphics from working?  The threads you linked to seem to be problems with dual boot, not with Live sessions via USB.
[19:33] <lotuspsychje> mpb: its weird, as my system works like a charm with same card
[19:36] <lotuspsychje> mpb: perhaps try 'install ubuntu'?
[19:36] <lotuspsychje> and enable 3rd party software & updates during setup
[19:37] <mpb> from syslog, perhaps when I tried to restart GDM3: Apr  7 18:40:01 ubuntu /usr/lib/gdm3/gdm-x-session[1196]: (EE) open /dev/fb0: Permission denied
[19:38] <lotuspsychje> mpb: what kind of hardisk in there?
[19:39] <mpb> also:  (WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted (EE) Fatal server error: (EE) xf86OpenConsole: Switching VT failed   (EE) Server terminated with error (1). Closing log file.
[19:40] <mpb> lotuspsychje: no hdd/sdd at present.  I pulled it out of the laptop to avoid potential data loss.
[19:40] <lotuspsychje> huh?
[19:41] <mpb> lotuspsychje: I'm running off of a USB disk.
[19:42] <mpb> lotuspsychje:  I'm happy to try an install, if that is what you recommend.
[19:42] <lotuspsychje> mpb: always backup before you try development versions
[19:57] <mpb> Update:  If I repeatedly stop and start GDM3, sometimse I get to the GDM3 login screen.  However, if I select "Live session user", the screen goes blank and comes back to the same GDM3 login screen.  So it seems like an intermittent graphics problem that happens most of the time.
[22:10] <Nycatelos> Hiya, I upgraded 17.10 -> 18.04 and my right click doesn't work
[22:10] <Nycatelos> I have a synaptics touchpad
[22:13] <lotuspsychje> Nycatelos: i think they have played with doublefinger mouseclick
[22:13] <Nycatelos> lotuspsychje: it seems to have affected my 'physical' right click in the corner of the pad, which confuses me a bit
[22:17] <lotuspsychje> Nycatelos: have you installed gnome-tweak-tool?
[22:17] <Nycatelos> uhh, yeah I have
[22:17] <lotuspsychje> Nycatelos: in mouse settings it says, right click simulation with 2 fingers
[22:18] <Nycatelos> lotuspsychje: the fingers mouse emulation, I had that enabled.
[22:25] <lotuspsychje> Nycatelos: fixxed now?
[22:25] <Nycatelos> lotuspsychje: nothing changed
[22:26] <Nycatelos> it was like that before, so no
[22:26] <lotuspsychje> hmm
[22:26] <lotuspsychje> not really sure then sorry
[22:26] <Nycatelos> I'm more confused than anything tbh
[22:36] <Nycatelos> lotuspsychje: it works on KDE, but not gnome
[22:36] <Nycatelos> so uhh, I have no idea what the problem is
[22:47] <lotuspsychje> Nycatelos: did you disabled completly, aka last option in mouse emulation?