=== Guest52427 is now known as RAOF
[01:35] <duflu> RAOF: Interesting question(?): If someone has a significantly nonlinear colour curve, could that distort some non-white colours very near #ffffff ?
[01:36] <RAOF> duflu: I don't quite get the question.
[01:36] <RAOF> The gamma tables can do approximately arbitrary things to the output.
[01:37] <RAOF> You can do any of the palletised animation if you want!
[01:37] <duflu> RAOF: I think I already answered it for myself. But yeah. I think if you need a particularly bendy curve then high values could go to unexpected places (when they actually want to go beyond white etc)
[01:37] <RAOF> Oh, no. The LUT won't ever go out of bounds.
[01:37] <RAOF> It's not actually a curve.
[01:37] <RAOF> It's a lookup-table.
[01:38] <RAOF> Approximately :)
[01:38] <duflu> RAOF: Yes I know, but if you're accounting for a particularly off display then I guess values near the edge of the gamut might stand out more than they should
[01:39] <jamesh> if you've got a gamma value of infinity, every value greater than 0 should map to 1
[01:41] <jamesh> or is that negative infinity?
[01:45] <RAOF> You're not actually programming gamma curves into the hardware, though.
[01:46] <RAOF> You're just sending 256 uint16_t values.
[01:46] <RAOF> (Also, you'd better be using the projective reals if you're talking about infinities ☺)
[02:06] <duflu> RAOF: Yes I understand how it works. Turns out I didn't need to ask the question at all though.
[02:07]  * RAOF wonders what the prompt for the question was
[02:08] <duflu> RAOF: Apparently #fefffc on one particular laptop looks very green/yellow. More than it should
[02:08] <RAOF> Maybe they should get a colorhug and calibrate the monitor :)
[02:08] <RAOF> But, yeah, laptop panels are often not excellent at colour reproduction!
[02:30] <duflu> RAOF: Apparently ColorHug2 also measure latency :)
[02:30] <RAOF> It can indeed :)
[06:11] <oSoMoN> good morning desktoppers!
[06:19] <duflu> Morning oSoMoN
[06:27] <Trevinho> Morning
[07:08] <didrocks> good morning!
[07:28] <duflu> Morning Trevinho, didrocks
[08:07] <willcooke> morning all
[08:10] <seb128> good morning desktopers
[08:10] <seb128> hey duflu Trevinho willcooke
[08:10] <willcooke> morning seb128, back home again?
[08:11] <oSoMoN> hey seb128, willcooke
[08:11] <willcooke> morning oSoMoN!  Trust you had a great holiday?
[08:11] <oSoMoN> I did :)
[08:12] <willcooke> Got my new laptop set up last night
[08:13] <willcooke> Think I've copied everything over
[08:13] <willcooke> But this one has a 1080 screen on the laptop, and the fonts are too small for me to read now :)
[08:13] <oSoMoN> which brand/model did you go for?
[08:13] <willcooke> Thinkpad X270
[08:14] <willcooke> it's pretty much the same as my X220
[08:14] <willcooke> which is perfect :D
[08:14] <oSoMoN> yeah, don't change something that just works
[08:14] <duflu> willcooke, oh I have been curious what the X270 is like
[08:14] <oSoMoN> I've got an X230 and I'm very happy with it
[08:15] <seb128> willcooke, yes, arrived around 9:30pm yesterday without issue
[08:15] <seb128> lut oSoMoN , bonnes vacances ?
[08:15] <willcooke> duflu, so far so good.  I went for the middle of the road i5 with a 1080p screen.  Space bar is a bit hit and miss, but everything else is fine.  Everything seems to work
[08:16] <willcooke> And most importantly, it was a real docking station
[08:16] <duflu> willcooke, backlit keyboard or not? I found on the X250 that backlit means smoother keys, and non-backlit better textured
[08:16] <willcooke> *has
[08:16] <willcooke> duflu, backlit yeah
[08:18] <oSoMoN> seb128, salut! excellentes vacances, ça fait du bien!
[08:19] <jamesh> I'm still waiting for the 1440p ThinkPad X1 Carbons that seem to be perpetually coming soon
[08:19] <willcooke> jamesh, :D
[08:19] <willcooke> I read about the "retro thinkpad" which was coming soon, but decided not to wait
[08:20] <duflu> jamesh, I think I saw they appeared recently...?
[08:20] <jamesh> If they were available, the choice between the X1 Carbon and X270 would be a lot easier
[08:20] <jamesh> duflu: oh. Let's see.
[08:20] <oSoMoN> seb128 et al.: how was GUADEC ?
[08:20] <duflu> jamesh, yep +$300
[08:25] <jamesh> duflu: thanks for pointing that out.  I guess I should go ahead and order one
[08:25] <duflu> jamesh, *shrug* sounds like a rather high premium to pay for a bit more resolution. Is the colour gamut wider?
[08:26] <seb128> oSoMoN, it was great
[08:26] <jamesh> Higher res screen, thunderbolt, and USB-C charging look nice
[08:26] <tjaalton> duflu: t470s review suggests it's brighter and has wider gamut
[08:27] <tjaalton> if they share the same panel..
[08:28] <jamesh> duflu: I'm happy to pay a bit extra if I think it'll last me a bit longer
[08:28] <jamesh> duflu: I've been on 768 line screens since my first laptop, so I guess I thought I'd skip 1080p if there was the option
[08:37] <ricotz> hello desktopers
[08:37] <oSoMoN> hey ricotz
[08:38] <ricotz> could someone change "linux (ubuntu)" to confirmed instead of released?
[08:38] <ricotz> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772
[08:38] <ubot5> Ubuntu bug 1699772 in scilab (Ubuntu) "linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing" [Undecided,Confirmed]
[08:39] <ricotz> the upstreamed patches are available since over month and included in 4.4.74 which still hasnt got into a 4.4 package release
[08:40] <ricotz> (this still breaks the i386 tests suite of libreoffice and the currently included patches for CVE-2017-1000364 are not sufficient)
[08:45] <oSoMoN> done
[08:47] <didrocks> Internet is fine on the train, IRC is flaky though
[11:48] <willcooke> cyphermox, did you have any problems with audio out on your dock?
[12:21] <willcooke> hey tseliot - do you know who might be a good person to sponsor a patch for the intel va driver?  https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1708091
[12:21] <ubot5> Ubuntu bug 1708091 in intel-vaapi-driver (Ubuntu) "External buffers of factually correct size get rejected by vaCreateSurfaces" [High,In progress]
[12:21] <willcooke> cc seb128 ^
[12:35] <seb128> willcooke, that patch is commited upstream so it's going to be part of the new version and we are in sync with Debian os are going to get it by sync, but I'm fine uploading it to Ubuntu meanwhile if we think we need it
[12:36] <willcooke> seb128, ah right.  Any ideas how long that would take?  If it's < a few weeks, safe to just wait I think
[12:37] <sergiusens> sil2100: are you working on ubuntu-image these days? I have some triggered adt tests due to my snapcraft  upload to zesty but it seems the failures are in ubuntu-image itself at runtime (or potentially snapd) -> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/u/ubuntu-image/20170801_183907_33a7d@/log.gz
[12:37] <sergiusens> can you confirm that?
[12:38] <sergiusens> ah, I see ubuntu-image already in the queue to SRU and also failing there
[12:39] <tseliot> willcooke: I think tjaalton might want to have a look at it
[12:58] <didrocks> ok, setting XDG_CURRENT_DESKTOP=ubuntu:GNOME works well apparently
[12:58] <didrocks> (not sure if I should capitalize "ubuntu", what do you think?)
[13:17] <sil2100> sergiusens: hey! Let me take a look
[13:18] <sil2100> sergiusens: but anyway, the ubuntu-image currently in -proposed for all stable releases is busted, there's a newer on in the unapproved queue but no one reviewed it yet
[13:19] <sil2100> sergiusens: eh, I see what the problem is
[13:20] <sergiusens> sil2100: something about fakeroot and what not, but I haven't dived into the code base
[13:20] <sil2100> sergiusens: so once someone other than me from the SRU team reviews the ubuntu-image that's in the queue it should be good
[13:21] <sergiusens> sil2100: ah, great, let me take it to #ubuntu-release, I can nudge ;-)
[13:21] <sil2100> sergiusens: since the current ubuntu-image that's in the -security/-updates pocket has the CVE fix that added the fakeroot dependency, but apparently we all missed adding it as a test dep then ;p
[13:21] <ricotz> seb128, hi, I had a look a poppler 0.57, but of course it is hit by a regression of glib-mkenums rewrite
[13:21] <oSoMoN> willcooke, the PPA we use to stage chromium updates before publication to the archive is configured to use only -security, not -updates, but I need -updates to build chromium with clang 4.0 that has recently been SRU’d to xenial
[13:21] <oSoMoN> willcooke, do you see potential issues with changing the PPA config to use -updates?
[13:22] <sil2100> sergiusens: the 1.1 in the queue has that fixed
[13:22] <ricotz> oSoMoN, rustc will eventually need llvm 4.0 too, so an update for trusty too would be great
[13:22] <mdeslaur> oSoMoN: you can't build security updates if -updates is enabled
[13:24] <oSoMoN> mmm, that's annoying, I was really counting on being able to use clang 4.0 in xenial
[13:24] <mdeslaur> oSoMoN: do a no-change rebuild of clang 4.0 in your ppa as xenial-security
[13:25] <mdeslaur> oSoMoN: and remember to tell chris to release it at the same time chromium is released
[13:25] <oSoMoN> that’s a neat trick
[13:25] <mdeslaur> oSoMoN: ie: "No change rebuild in the -security pocket." as the changelog
[13:26] <oSoMoN> mdeslaur, does it need to be released though? it’s a build dep only, so keeping it in the PPA should be fine, no?
[13:26] <mdeslaur> well, we release no change updates to the -security pocket all the time, it makes subsequent updates a lot easier
[13:26] <ricotz> oSoMoN, mdeslaur, meaning firefox 56/57 will need llvm 4.0 too
[13:26] <oSoMoN> mdeslaur, ok, I'll do that then
[13:27] <ricotz> a no-change rebuild will of course not work for trusty/14.04
[13:27] <oSoMoN> ricotz, can you file an SRU? I'm not sure who would handle it and how much work that would represent, but that should be the first thing to do
[13:28] <ricotz> it is basically the same a done to llvm 3.9, I would assume chris will do it
[13:28] <cyphermox> willcooke: not that I noticed, but I use some good USB speakers
[13:29] <mdeslaur> ricotz: llvm-toolchain-4.0 is already in xenial-updates
[13:29] <mdeslaur> ricotz: is that what you need?
[13:29] <ricotz> mdeslaur, I am talking about trusty
[13:29] <cyphermox> willcooke: how should I test? plug in something in the audio jack on the dock?
[13:29] <willcooke> cyphermox, yeah, audio jack in the dock.  I've done some more googling - looks like a common problem
[13:30] <mdeslaur> ricotz: oh! sorry, right, someone needs to port it...perhaps ask chris what the plans are and/or what needs to be done when he's back from vacation
[13:31] <ricotz> mdeslaur, he is hard to catch though
[13:31] <mdeslaur> ricotz: have you tried beer?
[13:31] <ricotz> heh
[13:31] <mdeslaur> :)
[13:33] <cyphermox> willcooke: https://www.amazon.co.uk/Logitech-OEM-S150-Speaker-System/dp/B000XUQ2LI/ref=sr_1_8?ie=UTF8&qid=1501680751&sr=8-8&keywords=logitech+speakers
[13:34] <ricotz> mdeslaur, would be great to get some response on https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1701556 with some further plans on https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/rust-updates/+packages
[13:34] <ubot5> Ubuntu bug 1701556 in rustc (Ubuntu) "Backport rustc 1.17 and cargo 0.18 to 14.04/16.04 and 17.04" [Undecided,New]
[13:34] <cyphermox> they're inexpensive and work quite well :)
[13:36] <oSoMoN> mdeslaur, do you know when chris gets back from vacation?
[13:38] <seb128> oSoMoN, he's not on VAC but at GUADEC to discuss mozjs/gjs maintainance
[13:38] <seb128> oSoMoN, he's back from that tonight iirc
[13:38] <mdeslaur> ah, that's why I couldn't find it in the calendar
[13:38] <ricotz> oSoMoN, mdeslaur, regarding llvm 4.0, of course 4.0.1 is wanted :)
[13:38] <mdeslaur> seb128: thanks
[13:39] <seb128> mdeslaur, yw
[13:41] <oSoMoN> seb128, right, thanks!
[13:45] <oSoMoN> davmor2_, congrats on the new job man!
[13:46] <didrocks> what is davmor2_ going to break nowdays?
[14:11] <popey> hello! I had a 16.04 basic install, not much changed. Just booted an artful USB key and tried to 'upgrade' it. It seems to have hung during "Removing conflicting operating system files", and isn't doing anything
[14:11] <popey> anything i can do to debug what it's doing?
[14:13] <popey> http://paste.ubuntu.com/25226720/ - copy and pasted that out of the ubiquity window
[14:14] <seb128> popey, you want cyphermox  or xnox, maybe #ubuntu-devel is better
[14:14] <popey> ok, thanks
[14:15] <seb128> yw
[14:15] <didrocks> popey: do you know why you have snapd info in your logs?
[14:19] <popey> eh?
[14:19] <ouroumov> Guys, sorry for polluting the channel, can anyone help me test gtk+2.0 from zesty-proposed for the SRU check? When I try to install it with apt-get it tries to do regexp matching, so I'm not sure how to install the package from proposed.
[14:20] <didrocks> popey: a lot of usr/lib/snapd/snapd[1361]: daemon.go:176: DEBUG: uid=999;@ GET /v2/find?q=ter
[14:20] <didrocks> popey: I think it's may be the features app? Not sure why they are fetched
[14:20] <popey> no idea
[14:20] <didrocks> ouroumov: did you add the proposed pocket to your source.list?
[14:21] <ouroumov> Yes. Also put a hold to avoid upgrading all packages as per instructions from https://wiki.ubuntu.com/Testing/EnableProposed
[14:22] <didrocks> good, then, your fix is really in the gtk+2.0 source?
[14:22] <didrocks> if so, sudo apt install libgtk2.0-0/zesty-proposed
[14:22] <didrocks> (you need to list binary package name, not source package names)
[14:22] <ouroumov> Okay, trying that, thanks
[14:22] <didrocks> this should pull the packages you need
[14:22] <didrocks> yw!
[14:23] <oSoMoN> mdeslaur, Rejected. PPA uploads must be for the RELEASE pocket.
[14:23] <oSoMoN> This upload queue does not permit SECURITY uploads.
[14:23] <mdeslaur> oSoMoN: oh, well, just use xenial then
[14:23] <oSoMoN> llvm-toolchain-4.0 (1:4.0-1ubuntu1~16.04.1ubuntu1) xenial-security; urgency=medium
[14:24] <mdeslaur> oSoMoN: or wait, and I'll rebuild it after lunch and push it to the archive
[14:24] <oSoMoN> mdeslaur, I’ll do that if you don't mind, please ping me when it's there
[14:24] <mdeslaur> oSoMoN: ok
[14:24] <ouroumov> Holly Jesus, hey didrocks is it normal it wants to remove ubuntu-mate-core, ubuntu-mate-desktop and some other packages?
[14:25] <didrocks> ouroumov: hum, were any of those only in proposed by any chance and your apt pinning did that?
[14:26] <didrocks> ouroumov: I would say, you can remove your apt pinning (the wiki mentioned one)
[14:26] <seb128> brb
[14:26] <didrocks> keep proposed enabled
[14:26] <didrocks> do the apt install …
[14:26] <didrocks> remove proposed so that next apt update/upgrades takes anything from proposed
[14:27] <ouroumov> Alright, trying that
[14:28] <ouroumov> didrocks, thanks this time it didn't try to remove stuff
[14:31] <didrocks> ouroumov: great, that was things you had from proposed I guess :)
[14:32] <willcooke> I've got dnsmasq and resolved using 100% CPU again.  cyphermox - any thoughts on what I can do to work out why?
[14:41] <cyphermox> why are you using both?
[14:42] <cyphermox> it depends on the config used, I suppose
[14:42] <cyphermox> willcooke: could you please file a bug, include /etc/NetworkManager/NetworkManager.conf and /var/log/syslog (but as I recall ubuntu-bug will do that for you)
[14:43] <cyphermox> maybe gdb each and include a backtrace too
[14:43] <willcooke> cyphermox, we needed dnsmasq for wifi hotspot support
[14:43] <willcooke> I might have installed the full dnsmasq
[14:43] <cyphermox> sure, but dnsmasq for hotspot doesn't do DNS resolution and wouldn't fight with resolved
[14:44] <cyphermox> even if you installed dnsmasq instead of dnsmasq-base, it's a bug
[14:44] <willcooke> I'm going to reinstall my test machine, if I can still reproduce the issue I'll log a bug
[14:44] <willcooke> oki
[14:44] <cyphermox> ok
[14:44] <cyphermox> maybe just check if dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf quickly first
[14:45] <cyphermox> if that's in there, then yeah NM will still try to use dnsmasq to do DNS caching
[14:45] <cyphermox> s/caching/resolution/
[14:45] <willcooke> no mention of dnsmasq in that conf file
[14:56] <seb128> to those using hexchat, is there any way to configure it in a way its indicates properly what channels get some activity?
[14:57] <seb128> it displays a conversation icon all the time, which is useless :-/
[14:57] <seb128> xchat-gnome was displaying nothing and adding an icon when there was unread content in the channel
[15:01] <willcooke> seb128, I configured it to show red text when I get a mention and green text when there is activity and grey when nothing, is that what you want?
[15:04] <didrocks> I guess seb128 is mentioned when the window isn't focused
[15:04] <didrocks> like you alt-tab to something else
[15:29] <seb128> willcooke, oh, let me look at that
[15:30] <seb128> didrocks, both, but having already different colors/signs on the main UI would be nice
[15:30] <seb128> atm I need to visit all the channels to see if there is an ongoing discussion somewhere, that's ridiculous
[15:31] <willcooke> seb128, http://imgur.com/a/MxxyV
[15:31] <seb128> willcooke, thanks, that did it, I was focussed on the icons thing and it didn't come to my mind that the color tab could have a solution to my problem
[15:32] <willcooke> \o/
[15:32] <willcooke> hmm, I'm not seeing snaps in the dash on gnome shell on a new 17.10 install
[15:33] <willcooke> it did this before, and then went away by itself
[15:33] <willcooke> but this is a new install, so dunno what I did
[15:35] <seb128> what sort of snaps?
[15:36] <seb128> you mean if you install a snap which has a .desktop?
[15:36] <willcooke> e.g. ohmygiraffe
[15:36] <seb128> like libreoffice?
[15:36] <seb128> let me try that one
[15:36] <seb128> did you install it and the icon is missing?
[15:36] <seb128> or did you try to look for uninstalled thing and to get the dash to guide you to gnome-software to install?
=== Guest63459 is now known as fredp
[15:37] <willcooke> seb128, I installed it via cli
=== fredp is now known as Guest43051
[15:37] <willcooke> software knows it's installed no
[15:37] <willcooke> w
[15:37] <willcooke> and it runs fine
[15:53] <seb128> shrug
[15:54] <seb128> willcooke, sorry, gnome-software froze eating cpu at the end of the installation, had to stop it after 10 min
[15:55] <willcooke> reboot, brb
[15:56] <seb128> jbicha, do you know where is GNOME supposed to put screenshots taken using the area keybinding?
[15:56] <willcooke> seb128, Photos
[15:56] <willcooke> *Pictures
[15:56] <seb128> right
[15:56] <seb128> it's not working :-/
[15:56] <seb128> every bug I try to debug I hit another one of the way
[15:56] <willcooke> oh
[15:56] <willcooke> well
[15:56] <seb128> thanks anyway :-)
[15:56] <willcooke> :)
[15:57] <willcooke> Interesting,
[15:57] <willcooke> I don't have a Pictures dir here on a fresh install
[15:57] <seb128> it works if I take screen screenshots
[15:57] <seb128> not area ones
[15:57] <willcooke> ahh
[15:57] <willcooke> on Waylnad?
[15:57] <seb128> no, X
[15:57] <seb128> ctrl-shift-print
[15:58] <willcooke> works here on Wayland, but because I dont have a Pictures dir it's putting them in ~
[15:58] <willcooke> seb128, try shift printscr
[15:58] <seb128> that seems another bug :-/
[15:58] <didrocks> confirmed area one not working on X
[15:58] <seb128> didrocks, thanks
[15:58] <didrocks> ah Shift + printscrn works
[15:58] <mdeslaur> oh, I hope we're not reverting to putting your confidential info into your shared pictures photo when you hit prtscrn by mistake
[15:58] <seb128> right
[15:59] <seb128> maybe I got my keybindings wrong
[15:59] <didrocks> seb128: well…:)
[15:59] <didrocks> you still have the cross
[15:59] <seb128> I bet the one with ctrl is for the clipboard
[15:59] <didrocks> ahhhh
[15:59] <willcooke> +1
[15:59] <didrocks> yep
[15:59] <willcooke> mdeslaur, interesting, it seems to have been that way for ever
[15:59] <didrocks> ctrl+Shift+printscreen is the clipboard
[15:59] <seb128> right
[16:00] <seb128> sorry for the confusion
[16:00] <didrocks> no worry, I learnt a new keybinding :)
[16:00] <mdeslaur> willcooke: we always reverted that
[16:00] <mdeslaur> we may have made it unity specific though
[16:00] <didrocks> mdeslaur: have you talked about it to the GNOME design team? (or have a bug/logs we can refer to?)
[16:01] <willcooke> brb
[16:01] <mdeslaur> I think there's an ancient WONTFIX bug somewhere
[16:01] <didrocks> would be great to find it so that we can reopen the discussion
[16:01] <jbicha> https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html or
[16:01] <jbicha> https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.fr :)
[16:02] <didrocks> jbicha: looking for the help on screenshot tool? Crazy ;)
[16:02] <mdeslaur> didrocks: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/927952
[16:02] <ubot5> Ubuntu bug 927952 in gnome-screenshot (Ubuntu) "When I press the Print Screen button, it will not appear in "Save Screenshot" window." [Medium,Fix released]
[16:03] <seb128> brb, moving location
[16:21] <xclaesse> Hm, just noticed that a recent install of ubuntu 16.04 has kernel 4.10 while my old upgraded system has kernel 4.4, that's weird
[16:21] <xclaesse> new systems gets linux-generic-hwe-16.04 installed by default but not upgraded systems it seems
[16:54] <seb128> willcooke, weird, selecting the wayland session here gave me an xorg one :-/
[16:54] <seb128> I wonder if the selector is buggy atm
[16:54] <willcooke> seb128, ah, I didnt test that
[16:56] <willcooke> seb128, they both give me wayland :)
[16:57] <willcooke> But the wayland one is realllly buggy
[16:58] <willcooke> e.g. crtl-alt-t for a terminal is super slow to respond, so I now have 10 terminals open
[16:58] <willcooke> log out does nothing
[16:58] <willcooke> cpu is not pegged
[16:58] <willcooke> oh, there we go
[16:58] <willcooke> it caught up
[17:00] <willcooke> and now I've logged in and out of a few sessions I get Xorg on the Ubuntu session and Wayland on the wayland one
[17:00] <willcooke> and on X my snaps appear again
[17:09] <seb128> willcooke, right, I know what the issue is, I add it to my list to deal with
[17:11] <willcooke> seb128, re: snaps or session?
[17:12] <jbicha> seb128 is going to fix all the issues :)
[17:16] <willcooke> \o/
[17:28] <ricotz> chrisccoulson, ping
[17:28] <chrisccoulson> hi ricotz
[17:28] <ricotz> chrisccoulson, hi, see PM
[18:39] <willcooke> night
[18:39] <willcooke> !"
=== JanC is now known as Guest87139
=== JanC_ is now known as JanC