[00:29] <pcd> Hey, I have 18.04 installed and wanted to try playing around with SystemTap. Unfortunately, it looks like kernel versions > 4.14 require systemtap 3.2 (released 18/10/18, bug in question is 22158), and the ubuntu package for systemtap is at 3.1. Is the systemtap package going to be updated to 3.2 in the final release? Is this even the right place to be asking about this, or should I take my question 
[00:29] <pcd> elsewhere? Thanks in advance.
[00:30] <SlidingHorn> bug 22158
[00:30] <SlidingHorn> oh, must be a different tracker...
[00:30] <pcd> Sorry, systemtap's tracker
[00:30] <pcd> https://sourceware.org/bugzilla/show_bug.cgi?id=22158
[01:00] <pcd> Should I file a bug on launchpad? I know it's pretty soon before the release ships
[01:05] <SlidingHorn> pcd: looking at the changelog, it looks like they may have patched 3.1 to fix that...
[01:05] <SlidingHorn> bug 876337
[01:05] <SlidingHorn> that's not it either...hmm...
[01:07] <pcd> Looks like they know about it in the debian package https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892995
[01:08] <SlidingHorn> this is the one the last ubuntu changelog update fixes: bugs.debian.org/cgi-bin/bugreport.cgi?bug=876337
[01:10] <SlidingHorn> pcd: so I think that's patched and all set :)
[01:11] <pcd> SlidingHorn: that looks like a different issue? The bug I linked is significantly newer than that, and still open
[01:13] <pcd> like 876337 is closed in 3.1-3, and 892995 is an issue in 3.1-3.
[05:33] <Volkodav> after recent partial upgrade I get no login screen startx from tty1 gets me into gnome. How do I start xfce session insyead?
[05:37] <flocculant> vo
[05:39] <lotuspsychje> Volkodav: try ubuntu recoverymode/fix broken packages
[05:39] <lotuspsychje> Volkodav: startx is not the right way anymore
[05:39] <lotuspsychje> !recovery
[05:40] <Volkodav> lotuspsychje: thanks - will do
[06:28] <kab0m> Hi together
[06:30] <kab0m> Does anyone has the bug "error while loading shared libraries: libzstd.so.1" while running "apt-get upgrade" with the 18.04 Beta? Any ideas how to fix this?
[07:08] <lotuspsychje> kab0m: did you add external ppa's to your system?
[07:09] <kab0m> lotuspsychje: No i didnt. But i am running kubuntu 18.04 beta 2...if this is relevant
[07:10] <lotuspsychje> kab0m: did you clean install or upgrade?
[07:10] <kab0m> lotuspsychje: clean install
[07:11] <lotuspsychje> kab0m: ok good, could you hastebin the output of: sudo apt update && sudo apt full-upgrade please
[07:11] <kab0m> Ok
[07:13] <kab0m> lotuspsychje: here you go https://paste.ubuntu.com/p/xfVHmYy7Gt/
[07:18] <lotuspsychje> bug #1766046
[07:19] <lotuspsychje> kab0m: if relevant, can you add yourself affected to this bug?
[07:21] <kab0m> lotuspsychje: ok i will. i just have to setup an account on launchpad. thanks for your help so far
[07:22] <Norux> Wow, I just read the release notes for bionic beaver and can say, I'm hyped!
[07:22] <lotuspsychje> kab0m: no problem, try to do some steps from that bug too, to see if you can reproduce
[07:22] <lotuspsychje> Norux: yeah they rock
[07:23] <Norux> lotuspsychje: So many things that really annoyed me about ubuntu that are fixed this update. E.g. now having a minimal installation
[07:23] <lotuspsychje> Norux: yeah thats gonna be so good
[07:23] <kab0m> ok guys. Im out, have a nice day
[07:23] <lotuspsychje> laterz
[07:23] <Norux> bye :)
[07:25] <lotuspsychje> Norux: you got that new welcome screen?
[07:28] <Norux> lotuspsychje: didn't try it yet! But I'm installing a VM right now.
[07:28] <lotuspsychje> cool, first desktop use should give you welcome screen
[07:44] <Norux> Hmm. Reeeeaally laggy for me. Might be because of the VM, but it has 16GB RAM and 8 cores...
[07:45] <lotuspsychje> gnome is much more lag then unity
[07:50] <Norux> I dislike gnome. I just don't like the look & feel of it. However, I still like the decision to use gnome once again
[07:50] <Norux> The number of bugs I encountered, caused by unity interfering with gnome, it was just ridiculous
[07:51] <lotuspsychje> same feeling
[07:51] <lotuspsychje> i wish they made gnome lightweight again
[07:52] <erle-> is the release on schedule or are there any known blockers?
[07:52] <Norux> lotuspsychje: yeah, I'd like that too
[07:53] <lotuspsychje> erle-: should be tomorrow during day
[07:54] <lotuspsychje> !party
[08:28] <forester> Hi. Why my Ubuntu-mate-beta2 uses ip 95.172.71.41 (or ...42)?
[08:28] <forester> Ubuntu downloads something from that ip-adress.
[08:29] <forester> without my permission.
[09:22] <MrM1st> If I install 18.04 now, do I have to update it again after friday? Is it enough just doing a aptitude update && aptitude upgrade? Or should I wait with installing it as my main OS until the final release?
[09:23] <erle-> upgrade should be enough
[09:27] <MrM1st> A bit concerned about the new version as the last kernels froze my laptop :(
[09:27] <MrM1st> The last kernels in 17.10
[09:38] <brainwash> MrM1st: you could download the daily iso and then test it by booting into live mode
[09:51] <Raytar> Hi, could someone else take a look at this bug? https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304
[09:51] <Raytar> It breaks some password management extensions like bitwarden and lastpass in firefox
[09:59] <brainwash> Raytar: someone? plenty people/devs already looked at it
[10:00] <Raytar> Ok, it just seems to me that this bug needs more attention.
[10:02] <brainwash> from whom?
[10:04] <Raytar> I don't know, I would hope that someone could triage it
[10:04] <Volkodav> I have no broken packages and still it boots in tty1 and only startx invokes gnome session and I can not get to login screen or start xfce that I usually use
[10:10] <brainwash> Raytar: did you rebuild ibus without the ubuntu patches yet?
[10:10] <brainwash> Raytar: one could maybe test ibus 1.5.18 from debian also https://packages.debian.org/sid/ibus
[10:11] <Raytar> Thanks, I will try
[10:15] <brainwash> Volkodav: did you share the output of "systemctl status gdm" yet?
[10:15] <brainwash> or lightdm
[10:18] <Volkodav> brainwash:not yet but I'll get it out 
[10:23] <Volkodav> https://pastebin.com/dTfcuZXD
[10:25] <Volkodav> brainwash: I just pasted it
[10:31] <brainwash> Volkodav: it says that lightdm was started successfully, but you cannot confirm that, right?
[10:32] <brainwash> I find it odd that lightdm does not come with its own .service file
[10:35] <brainwash> Volkodav: more logs can be found in /var/log/lightdm/
[10:37] <Volkodav> brainwash: not really - it shows a few colorful screens where login manager would normally pop up but then goes into tty1
[10:38] <Volkodav> let me pull the logs
[10:38] <brainwash> Volkodav: you use the nvidia driver?
[10:38] <Volkodav> yes
[10:38] <brainwash> that one could be the cause
[10:38] <Raytar> brainwash: I use "quilt" to delete the ubuntu patches right? After deleting the "ubuntu-*.patch" files and building the packages, the issue persists.
[10:39] <luna_> 18.04 release tommorow evening o/
[10:40] <Volkodav> brainwash: I'm pretty sure since it happened at least once before
[10:40] <brainwash> Raytar: so, next is to test the ibus 1.5.18 release from debian
[10:40] <brainwash> Volkodav: let's see what the lightdm log(s) say
[10:43] <Volkodav> brainwash: no such file lol
[10:44] <Volkodav> https://pastebin.com/C2tQARkg
[10:47] <brainwash> Volkodav: mmh. maybe try with gdm instead. "sudo systemctl disable lightdm" and "sudo systemctl enable gdm"
[10:48] <brainwash> not sure if simply reinstalling lightdm would help
[10:49] <Volkodav> brainwash: hardly ever reinstall helped me with anything
[10:50] <brainwash> not having /var/log/lightdm/ is pretty odd
[10:50] <Volkodav> brainwash: https://pastebin.com/5FWuHU9G
[10:50] <Raytar> brainwash: just built 1.5.18 from debian and the issue persists
[10:52] <brainwash> Volkodav: can you do "sudo systemctl start gdm" from tty?
[10:53] <brainwash> Raytar: mmh. running out of ideas then
[10:54] <brainwash> Raytar: at least that info can be added to the bug report
[10:55] <Volkodav> brainwash: sure I'll kill X and be right back with an output
[11:00] <Volkodav> brainwash: it started OK thanks for your help - how do I permanently set it up? Or is it going to be fixed soon? I doubt that given the time left until the release
[11:01] <brainwash> Volkodav: I'd think that it should automatically start on boot then (after disabling lightdm)
[11:02] <Volkodav> but lightdm is disabled isn't it? Or it may respawn ?
[11:08] <Raytar> brainwash: I have added the info. I will see if I can reproduce the issue on debian itself.
[11:28] <erle-> please note that default-jre being Java 11 breaks some things
[11:34] <brainwash> Volkodav: I assumed that disabling lightdm will allow gdm to start up instead
[12:05] <micw> Hi. I'm testing 18.04 in virtualbox. I installed the guest utils, dkms and x11 driver. When I switch to fullscreen, the screen gets messed up and does not respond until I switch back to window. I remember that I had similar in 17.10 (so stayed with 16.04)
[12:21] <MrM1st> micw: I've run 17.10 in virtualbox multiple times without problems
[12:22] <MrM1st> Trying 18.04 now
[12:23] <micw> i installed virtualbox today on the host (5.2.10), drivers are the same version
[12:23] <micw> the problem with 17.10 was on my workmate's laptop (windows 10)
[12:23] <micw> i'm running it on macos x currently
[12:24] <MrM1st> Hmm
[12:24] <MrM1st> I'm on a linux host as well
[12:24] <MrM1st> Is this the place to ask about livepatch? What is it?
[12:28] <guardian> so, if Bionic is released tomorrow, it means tonight's build ?
[12:30] <donofrio> guardian, but it's already tomorrow in "Suva"
[12:33] <lapaga> mine no longer says development branch so think it is the final
[12:37] <stickyboy> nacc: Hey, I have another question about something Java related. Are you around?
[12:42] <stickyboy> nacc: Seems tomcat8 in bionic does not work with openjdk-8. I found a Debian bug report about it from mid April: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895866
[12:46] <zteam> Hi all! I just upgraded from Ubuntu 17.10 to Ubuntu 18.04, most things appear to work as expected, but I'm unable to start synaptic from the desktop launcher starting it from a terminal with gksu synaptic however works fine, is this a known bug?
[12:47] <brainwash> zteam: mostly like it's due to running the wayland session
[12:49] <brainwash> there is bug 1713313
[12:49] <zteam> brainwash, well, I don't think so, because my Nvidia drivers doesn't support wayland yet (unless something changed very recently) so I'm still in Xorg-land
[12:50] <brainwash> ok
[12:51] <brainwash> so, what error do you get when simply running "synaptic" in a terminal window?
[12:52] <brainwash> or "synaptic-pkexec" in case that one exists
[12:52] <zteam> brainwash, no error at all, it's starting fine, however it does print this warning: Gtk-Message: 14:51:19.955: GtkDialog mapped without a transient parent. This is discouraged.
[12:53] <brainwash> and "synaptic-pkexec"?
[12:54] <zteam> brainwash, synaptic-pkexec doesn't work at all, no error either
[12:54] <brainwash> just checked it. the desktop launcher contains "Exec=synaptic-pkexec"
[12:57] <zteam> brainwash, okey :-)
[12:58] <zteam> brainwash, not a huge issue for me anyway, i just thought about if needed to report the error
[12:58] <brainwash> just to make sure, what is the output of "echo $DESKTOP_SESSION"?
[12:58] <zteam> ubuntu
[12:59] <brainwash> mmh
[12:59] <brainwash> then "echo $XDG_SESSION_TYPE"
[12:59] <zteam> X11
[12:59] <brainwash> ok
[13:00] <brainwash> so, I guess it should be report worthy
[13:02] <zteam> brainwash, I should add, that I recieved several errors from dpkg then I attempted to upgrade, the system even told me that it would revert to Ubuntu 17.10 again, but apparently it still works okey, and claims to be Bionic :P
[13:04] <brainwash> you could run "strace synaptic-pkexec" which will you give a rather large log output of system calls
[13:04] <brainwash> maybe the last couple of lines contain some hint
[13:05] <brainwash> other than that, you could test other applications which utilize pkexec for authorization
[13:06] <brainwash> like gparted-pkexec
[13:06] <brainwash> oh. and also try "pkexec synaptic"
[13:10] <stickyboy> How can I check when a package was last synced from Debian into Ubuntu?
[13:10] <stickyboy> s/How/Where/
[13:11] <stickyboy> tomcat8 stopped working for me this week in bionic, but it was working two weeks ago.
[13:11] <zteam> brainwash, https://paste.ubuntu.com/p/Yk44WVc8pk/
[13:12] <zteam> stickyboy, are you using bionic on a server you say?
[13:14] <stickyboy> zteam: Testing bionic server, yes. Not running in production of course.
[13:14] <brainwash> maybe this bug 1717998
[13:15] <stickyboy> brainwash: Nah, I'm explicitly using tomcat8 (aka 8.5.x) not tomcat8.0.
[13:15] <brainwash> ok
[13:16] <stickyboy> I found this Debian bug from a few weeks ago, seems to be similar to my problem.
[13:16] <stickyboy> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895866
[13:16] <brainwash> https://launchpad.net/ubuntu/+source/tomcat8/+publishinghistory
[13:16] <stickyboy> That's why I'm wondering if it's maybe something related to a Debian→Ubuntu sync.
[13:16] <stickyboy> brainwash: Ok, let me have a look.
[13:17] <stickyboy> (gist of the Debian bug is that tomcat8 was compiled with Java 9, so won't run properly with Java 8)
[13:19] <stickyboy> Ah, so it looks like Ubuntu bionic did indeed sync tomcat8 from sid on April 20 (so it inherited this bug).
[13:19] <stickyboy> Err, 2018-04-19 rather.
[13:19] <brainwash> zteam: not sure about the output, but it may be helpful in case you file a bug report
[13:20] <brainwash> stickyboy: right
[13:21] <stickyboy> brainwash: Exciting! The resolution of the Debian bug was the maintainer saying he'd rebuild tomcat8 with Java 8 in the next release.
[13:21] <stickyboy> Now to find out if Debian fixed it...
[13:30] <nostrora> Hello everybody, I can read this : "Canonical is also working to speed up the boot-time of Ubuntu by using systemd’s features." Do you know which systemd's features are talking about ? source : https://fossbytes.com/ubuntu-18-04-bionic-beaver-release-date-features/
[13:37] <stickyboy> nostrora: Starting system services in parallel? Starting things only when they are needed (dependencies)? Using systemd-analyze to see the graph of service dependencies and times taken.
[13:38] <stickyboy> nostrora: systemd can also wait to mount filesystems until they are accessed.
[13:38] <stickyboy> etc
[13:58] <nostrora> stickyboy: ok !
[14:00] <stickyboy> brainwash: Ok, I filed a bug for tomcat8 on Launchpad and linked it to the Debian bug: https://bugs.launchpad.net/debian/+source/tomcat8/+bug/1766882
[14:02] <stickyboy> Err, this one: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1766882
[14:02] <stickyboy> Launchpad is confusing. :D
[14:15] <strang3quark> hi, any of you knows how to install anbox on Bionic?
[14:15] <strang3quark> I cannot load the kernel modules
[14:16] <wlan2> I never really got anbox to work ever.
[14:17] <wlan2> But, what method did you use for installing?
[14:18] <Volkodav> brainwash: I've just rebooted and it's the same story - had to manually start gdm
[14:20] <donofrio> whoa think I just figured out ubuntu numbering (it's year then month released?)
[14:23]  * stickyboy hands donofrio a cookie.
[14:24]  * donofrio chewing
[14:26] <wlan2> donofrio: Precisely.
[14:27] <strang3quark> wlan2: i followed the instructions on the anbox site, I also tried to download and run the installer script
[14:27] <strang3q1> wlan2: I followed the instructions on the Anbox website (install the snap package)
[14:28] <wlan2> strang3quark: What kind of error would you get?
[14:28]  * donofrio thinks anbox now there is a name I've not heard of in awhile.
[14:28] <wlan2> donofrio: android runtime in containers
[14:29]  * wlan2 typed that before finished reading your reply...
[14:29] <strang3q1> their anbox-support ppa does not have packages for bionic, I tried to use the xenial packages but the modules aren't working
[14:32] <wlan2> I'd bet you'd have to build the modules yourself for bionic... But did dkms succeed in building them?
[14:34] <strang3q1> wlan2: yes, the modules are built but I cannot load them
[14:34] <wlan2> Any particular error?
[14:37] <strang3q1> http://pastebin.ubuntu.com/p/rv27qkzP67/
[14:39] <wlan2> What does dmesg say?
[14:40] <strang3q1> ashmem_linux: Unknown symbol __vfs_read (err 0)
[14:45] <wlan2> That sounds to me like those modules won't work for your current kernel without some coding. I've never coded kernel modules, so I'm just guessing.
[14:46] <Volkodav> has anybody noticed that panel-xkb is a cpu hog? Has been eating up to 40% of CPU since early alpha
[14:47] <strang3q1> Me neighter, I guess I'll just use a VM until there's an update. thanks for your help
[14:49] <brainwash> Volkodav: what is panel-xkb?
[14:50] <Volkodav> brainwash: Keyboard layout plugin for xfce panel
[14:53] <brainwash> Volkodav: does it constantly use that much cpu?
[14:53] <Volkodav> brainwash: yes it does
[14:53] <Volkodav> 35-40%
[14:54] <brainwash> maybe you should have filed a bug report for this earlier
[14:55] <enyc> hrrm
[14:55] <enyc> will ubuntu-18.04 (updated from 16.04) boot ok with an older 4.8.0 kernel  (yes, i know, i will need to sort out newer kernel / custom drivers etc in time)?
[14:55] <wlan2> I would recommend using ibus instead of th0se layout switchers.
[14:57] <wlan2> enyc: I see no reason why it would not,4.8 is not THAAAAT old.
[14:57] <enyc> last i checked gcc had a minimum of 2.6.32 =)
[14:57] <enyc> but that may have changed
[14:57] <brainwash> Volkodav: I suggest asking in #xubuntu-devel, maybe someone there can confirm this issue and help with debugging the it
[14:57] <brainwash> -the
[14:58] <wlan2> Bye.
[14:59] <Volkodav> brainwash: I will ask them guys
[15:00] <odez> hi, after upgrading to ubuntu 18.04 i got a minute delay in showing the login screen. anyone heard of this issue?   (X, gdm3, nvidia)
[15:00] <vlt> odez: Might be a "resume from" device the initramfs is waiting for.
[15:02] <brainwash> odez: I would check the output of "systemd-analyze blame"
[15:04] <Volkodav> brainwash: I should have filed it long ago - agree , just was hoping that some bugs are ironed out in the process - but this one has obviously been not
[15:05] <brainwash> it's possible that it only affects a specific driver/panel setup
[15:05] <brainwash> therefore, not affecting everyone
[15:07] <Volkodav> brainwash: xfce is rather straightforward in testing that 
[15:07] <Volkodav> I'll ask them anyway
[15:07] <brainwash> please do
[15:07] <Volkodav> already did actually
[15:10] <odez> brainwash:  732ms fwupd.service is my no 1.  i guess the delay is in X?
[15:11] <brainwash> odez: and "systemd-analyze critical-chain"?
[15:12] <brainwash> also, check "journalctl -u gdm"
[15:18] <odez> brainwash: journalctl  -u gdm says this 3 times:  Unable to kill session worker process -   Child process -xx was already dead   
[15:21] <brainwash> odez: ideally, you should pastebin the whole terminal output
[15:23] <odez> brainwash: https://pastebin.com/3W0Ttjjw
[15:29] <brainwash> odez: searching the web for info about those lines does give helpful results
[15:30] <brainwash> odez: I guess the last place to check is /var/log/xorg/
[15:30] <brainwash> and general system log of course
[15:30] <brainwash> journalctl
[15:40] <odez> brainwash: thanks for helping
[15:49] <kiroma> I've performed a do-release-upgrade on my kubuntu 17.10 and I noticed a lot of oddities
[15:49] <kiroma> i.e. update-grub was run at least 5 times, and update-initramfs only once near the end like it should be
[15:50] <kiroma> Before changing the kernel all DKMS modules have been reinstalled.
[15:50] <kiroma> And then removed.
[17:16] <ChmEarl>  cat /etc/issue.net -> Ubuntu 18.04 LTS
[17:16] <ChmEarl> maiden voyage ^^
[17:16] <ads20000> nice! Have fun and report bugs! :)
[17:18] <pcd> What's the turnaround time on package bugs when the packages are nominally maintained by Ubuntu Developers?
[17:19] <nacc> pcd: it depends
[17:19] <pcd> nacc: alright, what's the turnaround time for a bug where systemtap simply doesn't work on 18.04? :P
[17:20] <nacc> pcd: is the bug filed?
[17:20] <pcd> https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/1766754
[17:21] <nacc> pcd: i'd ask in #ubuntu-kernel
[17:21] <pcd> nacc: Alright, thanks
[17:21] <nacc> pcd: np
[18:41] <arun007> :)
[19:10] <guardian> curious whether current daily build is the final one :)
[19:12] <acheronuk> guardian: no, it's not
[19:16] <guardian> acheronuk: how do you know? (honest question, is there a task list somewhere?)
[19:19] <acheronuk> guardian: because I'm a Kubuntu and Ubuntu developer, keeping an eye on the current state of things in #ubuntu-release and other dev channel. hence I know that there is to be a respin of iso images to fix an installer bug at the very least
[19:20] <guardian> acheronuk: oh I see, thanks for sharing
[19:47] <freehUgsz> first ubuntu release i'm interested in
[21:40] <Seveas> freehUgsz: welcome to the dark side!
[22:34] <freehUgsz> Seveas, well thank you :)
[23:07] <Moc> I was told to join here to talk about issue in trying to boot the daily build of bionic beaver
[23:08] <Moc> The beta 2 iso does work correctly (Im on it right now), but I tried both 20180425 daily build and installer wont start
[23:09] <Moc> I
[23:09] <Moc> I'm going to try yesterday daily in 2 minutes
[23:10] <Moc> My machine is a Dell Latitude E5540
[23:12] <Moc> Rebooting now to 20180424 daily build.  brb
[23:16] <Moc> Daily 20180424 installer started normally
[23:43] <katnip> are most new releases released on UTC time?
[23:56] <silox> Hello, I wanted to see if anyone could verify that both Landscape (on premises install) and MAAS will both function on Ubuntu 18.04 LTS that's scheduled to be released tomorrow.  Any help would be appreciated as I'd like to use 18.04 for a Landscape/MAAS deployment for an entire datacenter.