=== led_ir23 is now known as led_ir22
=== led_ir23 is now known as led_ir22
=== led_ir23 is now known as led_ir22
=== sergiusens_ is now known as sergiusens
=== mnepton is now known as mneptok
=== led_ir23 is now known as led_ir22
[06:08] <jibel> xnox, thanks for looking, it's a VM and capable of running gnome-shell.
[07:01] <acheronuk> openjdk-lts installs /usr/share/applications/openjdk-11-policytool.desktop which wants /usr/bin/policytool but no longer sets up an alternative for this?
[07:03] <acheronuk> doko: I see you much on changelogs. do you happen to know what happened there?
[07:04] <acheronuk> on an artful install I have for example /etc/alternatives/policytool -> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytoo
[07:17] <acheronuk> doko: so I guess that policytool was dropped after jdk8, but the desktop file for 11 was left being installed and dangling?
[07:40] <doko> acheronuk: please could you file a bug report?
[08:31] <forester> Hi. Why my Ubuntu-mate-beta2 uses ip 95.172.71.41 (or ...42)?
[08:31] <forester> Ubuntu downloads something from that ip-adress.
[08:31] <forester> without my permission.
[08:33] <Faux> Never heard of it. Try working out what's making the connection, or what data its sending? (netstat -anp, wireshark, etc.)
[08:35] <forester> I have take a look in internet. It is from GB. (England)
[08:36] <Unit193> Faux!  Wondered the other day if you'd be interested in poking at chary.
[08:36] <Unit193> ..This is the wrong net, but eh.
[08:39] <forester> I use wireshark. But for my level it does not say something important.
[08:39] <forester> I mean that I am not a specialist in this area.
[08:40] <forester> And all that wireshark's stuff do say me nothing.
[08:42] <Faux> Unit193: I don't even know what that is. :)
[08:42] <Faux> forester: Wireshark will tell you the protocol, port, and in most cases, a lot of details about the message in the bottom pane. Screenshot it, or work out how to read it then tell us!
[08:42] <Unit193> charybdis.
[08:42] <Faux> Oh!
[08:45] <Unit193> I'm still running charybdis-4.1
[08:51] <cjwatson> forester: That's the Internap CDN; the snap store sends snapd there for downloads of snaps.
[08:51] <cjwatson> forester: So you presumably have at least one snap installed which is being refreshed ("sudo snap list", "sudo snap changes" will say).
[08:52] <Unit193> IIRC, MATE ships one by default.
[08:53] <arunkumar413> Hi All, anybody familar with .config.sh files
[08:53] <cjwatson> A few, I believe: pulsemixer, ubuntu-mate-welcome, and software-boutique.
[08:53] <forester> core  pulsemixer   software-boutique   ubuntu-mate-welcome
[08:53] <cjwatson> And core as a result, yes.
[08:57] <forester> https://imgur.com/a/WsKfhHe
[08:57] <cjwatson> arunkumar413: That sounds like a very project-specific kind of thing, rather than a generic file type that somebody is going to be familiar with.  It would probably be better to say what your actual problem is.
[08:59] <arunkumar413> well it's related to ubuntu. it's related to adding a new mobile device to the config.sh file. T guide says we should add new device to the config.sh file for porting to a new device.
[08:59] <arunkumar413> sorry. It's not related to*
[09:00] <forester> Please take a look at snapshot, especially at system tray (goldendict popup submenu and 2 strips of Typing Monitor).
[09:01] <forester> Typing Monitor should be only one.
[09:01] <forester> And goldendict popup submenu should look different. In this case it looks like a sound volume.
[09:12] <forester> cjwatson: How to disable it? I have a slow internet and it is not possible to lister radio some times due to background downloading.
[09:12] <forester> listen radio*
[09:15] <cjwatson> forester: There's no supported way to disable snap refreshes entirely, but you can control the timing: https://forum.snapcraft.io/t/refresh-schedule-via-core-config/434
[09:16] <cjwatson> Actually it's refresh.timer now apparently.  https://forum.snapcraft.io/t/system-options/87
[09:20] <forester> cjwatson: Thank you. I am going to try it. Did you take a look on the screenshot I have sent?
[09:21] <forester> https://imgur.com/a/WsKfhHe
[09:21] <forester> where I told about issues in the system tray
[09:24] <cjwatson> forester: I'm not a MATE developer and cannot help with that.
[09:26] <forester> cjwatson: Is it the right place for me to tell about that issues? And is it possible to remove something with Synaptic to disable that updating? (refresh.timer I have already set).
[09:27] <forester> Or there is another channel for ubuntu-mate-dev/?
[09:27] <cjwatson> forester: Reporting bugs on IRC usually isn't very sensible, because they'll get lost unless somebody picks them up right away.  That's what the bug tracker on Launchpad is for.
[09:34] <forester> Ok. Thank you for help.
[09:41] <Mirv> I'm no longer in a group that can look up oops ids, but I got an ubiquity error with Ubuntu 18.04 LTS installation when clicking reboot after installation complete, maybe someone can click to create a bug report for oops 28c5e9ac-486c-11e8-a271-fa163e171d9b
[09:42] <Mirv> (the reboot didn't happen, as also indicated by the python backtrace)
[09:43] <cjwatson> Mirv: That isn't an OOPS ID.  Do you maybe mean the error tracker or something?
[09:44] <Mirv> yes well on error tracker I used to access those ids at https://errors.ubuntu.com/oops/[ID]
[09:44] <cjwatson> Oh, maybe it reused the name
=== simon_ is now known as Sibe39
[09:44] <Mirv> and I think syslog also uses oops for it, because I copy pasted it from there
[09:45] <cjwatson> But if I click the button for that then I'll be the bug reporter.
[09:45] <Mirv> right, whoopsie reported OOPS ID
[09:45] <cjwatson> Anyway, I think a fix for that one is already in progress.
[09:45] <cjwatson> Mirv: https://launchpad.net/bugs/1766811
[09:45] <ubottu> Launchpad bug 1766811 in ubiquity (Ubuntu Bionic) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.UnknownMethod: No such interface '(null)' on object at path /org/gnome/SessionManager" [Critical,New]
[09:45] <Mirv> right, just found it too now
[09:45] <cjwatson> is the same thing
[09:45] <Mirv> ok, no need then, thank you!
[09:46] <Mirv> a fix by didrocks updated 24 mins ago, thank you :)
[10:22] <acheronuk> doko: Thanks. I asked the person on our forums to file a bug, as it shows up in desktop menus and gives an error when they try to launch it. If they don't or have not soon, I will file myself
[10:47] <acheronuk> doko: LP: #1766843
[10:47] <ubottu> Launchpad bug 1766843 in openjdk-lts (Ubuntu) "obsolete openjdk-11-policytool.desktop file is still installed - gives error when users try to launch from menu" [Undecided,Confirmed] https://launchpad.net/bugs/1766843
=== sergiusens_ is now known as sergiusens
=== rmk` is now known as rmk
=== Whoopie_ is now known as Whoopie
[14:06] <Odd_Bloke> slangasek: infinity: sil2100: How are we looking for locking in the cloud images?  Any more packages we might care about expected to land?
[14:07] <Odd_Bloke> (Or have landed today, I guess, we might have triggered our daily before they landed.)
[14:09] <Odd_Bloke> (Oh, I fat-fingered when switching channels, pretend the above was in #ubuntu-release. >.<)
[14:09] <sil2100> Odd_Bloke: not sure if this will obviously affect cloud or not, but we might need to do some changes in dpkg/zstd for the dpkg-deb issues that have been reported
[14:10] <sil2100> But I guess it might be just an upgrade case, so maybe not really related to locking cloud
[14:22] <ogra_> slangasek, could we rename http://cdimage.ubuntu.com/ubuntu-core/16/current/ubuntu-core-16-arm64+snapdragon.img.xz ? this image solely runs on the dragonboard 410c, the new name causes some confusion (people in 96boards trying to install it to random snapdragon boards (which indeed fails)) ... it is unlikely we'll ever get a generic snapdragon image anyway due to the nature of the bootloader setups on these devices
[15:50] <slangasek> Odd_Bloke: the one thing that hasn't landed yet that's cloud-specific is linux-azure; I don't know why it hasn't been unblocked yet
[15:50] <Odd_Bloke> slangasek: (AU)rk.
[15:50] <slangasek> sforshee, apw: ^^ is linux-azure still blocked for a reason?
[15:51] <sforshee> slangasek: mhcerri wanted to wait for some of the sru tests that hadn't yet completed
[15:53] <slangasek> sforshee: have they completed now and can we unblock?
[15:57] <sforshee> slangasek: some have still not completed
[15:59] <slangasek> sforshee: can we track this progress somewhere?
[16:01] <sforshee> slangasek: hang on, was only looking at 1009, 1008 was for all practical purposes the same kernel and we have more results for that
[16:07] <sforshee> slangasek: still a few that are missing, am trying to see if mhcerri could run them maunually
[16:07] <sforshee> the results are at that same IP you couldn't get to the other day
[16:07] <slangasek> right, thought so ;)
=== FauxFaux is now known as Faux
[18:17] <rcj> slangasek: anything else we should wait for in cloud images?  The linux-azure dependency doesn't block everything for us to start cloud image builds.
[18:20] <slangasek> rcj: for final images you'll want to make sure db5.3 5.3.28-13.1ubuntu1 is published first, since that got accepted instead of being allowed to SRU
[18:20] <slangasek> rcj: if you see db5.3 published in release, I don't see anything else pending after that which impacts cloud images, except azure
[18:21] <rcj> slangasek: thanks!
[18:22] <rcj> and it looks like db5.3 is published.  So now it's just time for Odd_Bloke and I to have a mind meld and decide how early we can start without linux-azure in place.
[18:23] <slangasek> while you're melding I'll work on getting linux-azure out there
[18:49] <rcj> It's mostly harmless. https://i.chzbgr.com/full/2712406016/hB630F303/
[18:54] <slangasek> rcj, Odd_Bloke: linux-azure 4.15.0-1009.9 accepted into release; publishing cycles etc
[18:55] <rcj> slangasek: thanks.  it's possible I can let automation do its thing, but it was a fine exercise.
[20:23] <jbicha> yay, emoji in changelog entries: https://launchpad.net/ubuntu/+source/casper/1.394
[20:24] <Unit193> Ugh.
[20:28] <jbicha> Unit193: why doesn't Xubuntu install fonts-noto-color-emoji by default?
[20:28] <Unit193> Because we don't want it.
[20:28] <jbicha> could you use more words (or at least emoji!) to explain?
[20:29] <jbicha> if you don't install it, users will still be able to use emoji, they just won't look good
[20:30] <Unit193> I most certainly won't be doing that.  But from the earlier discussions Qt had issues with fonts-noto-color-emoji, so we went with the one that Qt doesn't have an issue with.
[20:30] <jbicha> because Xubuntu cares about Qt these days?
[20:30] <Unit193> They don't look good anyway, so using symbola isn't really a problem (and in fact, they look far better with symbola.)
[20:30] <Unit193> Xubuntu cares about Qt, because we realize our users might use something that's non-default...
[20:32] <Unit193> We don't ship anything Qt, but we'd still like it to work as best as possible for users that install some Qt application.  VLC is quite common, as are other Qt based applications.  It'd be silly to ignore them.
[20:34] <jbicha> if you include both fonts-symbola and fonts-noto-color-emoji, the Qt apps will use the Symbola black-and-white emoji
[20:34] <jbicha> so that's not an argument to not also offer color emoji for all the GTK+ apps you actually do ship
[20:35] <Unit193> If someone wants to install it, they can.  Again, no big deal..
[20:35] <jbicha> color emoji support is being advertised as an Ubuntu 18.04 feature
[20:36] <Unit193> That's fine for Ubuntu.
[20:36] <jbicha> it's a bit surprising that that feature works out of the box in every Ubuntu flavor except Xubuntu and Kubuntu. Kubuntu is understandable but …
[20:37] <jbicha> oh and Kylin
=== mochouinard is now known as Moc
[22:52] <Moc> I just tried to boot the latest daily build and the install wouldn't start.
[22:52] <Moc> I installed the beta2 normally
[22:54] <sarnold> how about previous dailies?
[22:54] <Moc> 20180425.1 just got made... ill try this one
[22:58] <Moc> I was on the latest 15min ago ;)
[22:59] <sarnold> ha :)
[23:00] <Moc> brb
[23:00] <Unit193> There was a world respin.
[23:02] <slangasek> not that anything we were respinning for would account for it not starting
[23:03] <Moc> :( Same issue
[23:04] <Unit193> slangasek: I wouldn't think so, but not been closely watching what the respins were for.
[23:04] <Moc> I'll try yesterday daily build.. (last one available on the daily build site)
[23:05] <slangasek> Moc: you might want #ubuntu+1 for support; and to give more detail on where it stops
[23:05] <Moc> I see the cursor, the screen is black and I hear the login prompt wav file
[23:05] <slangasek> so no video output
[23:06] <slangasek> I think you'll definitely want to try to work with #ubuntu+1 on that; sounds like a hardware-specific problem that we're not likely to be able to go deep on here
[23:06] <Moc> Only the cursor and a glimpt of audio.  CTRL-ALT-F2 does allow me to get out and I can CTRL-ALT-F1 again but I just see the cursor
[23:06] <sarnold> we have a wave file?
[23:06] <Unit193> sarnold: Does Ubuntu still use the drums?
[23:06] <Moc> I didn't hear the wave sound on the load of install using the beta 2 (as far as I can remember)
[23:06] <Unit193> I thought it'd stopped a while ago.
[23:07] <sarnold> Unit193: all I've got in my head is mac bootup sounds. I'm sure that says something.
[23:07] <Unit193> sarnold: The Ubuntu Bongos!
[23:12] <Moc> Rebooting now to 20180424 daily build.  brb
[23:16] <Moc> Daily 20180424 installer started normally
[23:17] <Moc> I
[23:18] <Moc> I'm new (again) to gnome... I just apparently put my terminal in 'full screen'... no idea how I did that.. lost my left navigator
[23:20] <Moc> urm, f11... not sure I did that... but could me... trying it on a new laptop and the keyboard is a bit shifted to the left (because it have a num pad to the right), making it hard to type on it so far