[05:42] <pitti> Good morning
[07:18] <seb128> good morning desktopers
[08:04] <TheMuso> Hey willcooke.
[08:07] <seb128> hey TheMuso, willcooke
[08:07] <seb128> how are you?
[08:14] <davmor2> seb128: in deja dupe there is a drop down option which shows what is happening, that used to take most of the rest of the window however now in 16.10 it uses a single line instead any clue as to what would cause that, I think it is the same with the updater where you can open the terminal to see what it is doing but let me double check on that
[08:16] <seb128> davmor2, likely a side effect of the new GTK but it's the individual components that need to be updated to specify a min height or something, so please open a bug against deja-dup (and same for updater if needed)
[08:17] <seb128> davmor2, willcooke, did we speak about tagging those bugs? rls-y-incoming would make sense?
[08:18] <davmor2> seb128: yes so if you open software updater and and click on details on the installing updates page you can see the issue too so I think it is an element rather than deja dupe itself
[08:18] <seb128> no
[08:18] <seb128> it's new gtk forcing you to specify the height you want for that widget when yo use it
[08:19] <seb128> they use the same widget
[08:19] <seb128> but needs to be fixed in each codebase
[08:19] <davmor2> seb128: oh okay so do I file one bug and update it with new projects when I hit them then?
[08:20] <seb128> no please don't do that
[08:20] <seb128> just open a bug on deja dup describing the issue
[08:20] <seb128> then one on update-manager
[08:20] <davmor2> seb128: right no worries
[08:20] <seb128> the "use one bugs and collect for similar things that have nothing to do" just creates spam
[08:21] <seb128> like the update-manager maintainer fix his code and then keep receiving emails about similar bugs in other projects he doesn't care about
[08:21] <seb128> fixes
[08:23] <happyaron> seb128: hey, mind to have a look at n-m? the 1.2.4 thing
[08:24] <seb128> happyaron, sure, it's in git? let me check, but you should probably go through normal sponsoring for those so more people can review and it's visible that something is waiting
[08:24] <happyaron> ic
[08:24] <seb128> you might also get some people vouching for you over time to give you ppu for it ;-)
[08:24] <happyaron> yep
[08:26] <seb128> happyaron, what's the difference between patches "dropped" and "merged"?
[08:27] <happyaron> dropped is not needed (due to design change upstream), merged is for those are almost directly merged upstream
[08:27] <seb128> k
[08:28] <seb128> would probably nice in the dropped case to have a small explanation of why they are not needed anymore
[08:28] <happyaron> ok
[08:31] <duflu> pitti, Saviq: Can we increase the unity8.log.* files that apport attaches? Seems like that log is always so big it's already rotated so the useful info is missing
[08:31] <duflu> Never goes back as far as Unity8 starting up
[08:32] <pitti> you mean attach the first rotated log too? sure, the apport hook can do this
[08:32] <seb128> happyaron, systemd-Don-t-enable-NetworkManager-wait-online.serv.patch seems new and no documented in the changelog?
[08:33] <duflu> pitti: Yes I think the first one will do thanks
[08:33] <duflu> tjaalton: Hey found a second regression from Mesa 12.0.2:  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1620994
[08:33] <ubot5> Ubuntu bug 1620994 in mesa (Ubuntu) "EGL clients with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate)" [Undecided,New]
[08:33] <duflu> Seems 12.0.2 is very bad for Unity8
[08:33] <pitti> seb128, happyaron: that's an old Debian patch which we dropped (deliberately); please keep it dropped
[08:33] <happyaron> seb128: lemme have a look of it
[08:34] <happyaron> pitti: ok
[08:34] <pitti> happyaron: i. e. we do want to enable NM-wait-online
[08:34] <seb128> happyaron, there are 3 other new patches added to the serie, those at least need to be documented in the changelog
[08:35] <happyaron> others should be renamed ones, I'll make a list later in changelog
[08:35] <seb128> pitti, hey, "we" and "when"? it's still in the current archive version and the change is undocumented in the debian/changelog
[08:35] <seb128> happyaron, can you please stop renaming patches?
[08:35] <seb128> that just makes reviews difficult for no good reasons
[08:36] <seb128> pitti, sorry, I read what you said in reverse
[08:36] <seb128> so yeah, shouldn't be added back?
[08:36] <seb128> happyaron, ^
[08:36] <pitti> seb128: https://launchpad.net/ubuntu/+source/network-manager/1.1.93-0ubuntu4 was the last  time it was brought back
[08:37] <seb128> happyaron, but bottom line is that every change in the patches set (so basically in the series) should be documented in the changelog
[08:37] <seb128> either it's a rename or a patch added/removed there is always a reason
[08:38] <seb128> seems it was added back in https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=38a52be23a88226fc255332d6d1bd2b440bc8b5b
[08:38] <happyaron> I see
[08:39] <seb128> happyaron, did you talk to cyphermox about removing Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch
[08:39] <seb128> or debian/patches/Order-IPv6-nameservers-before-IPv4-for-dns-plugins-d.patch
[08:39] <seb128> it's a bit annoying
[08:39] <seb128> those have no bug reference neither upstream or downstream
[08:40] <seb128> no cookie for c_yphermox
[08:40] <pitti> seb128, happyaron: oh, sorry; debian/patches/systemd-Don-t-enable-NetworkManager-wait-online.serv.patch actually looks intended, *if* we still actually enable it via WantedBy; well, the net result is: we want NM-wait-online.service, and with as little delta to Debian as possible (dropping the dh_installinit override  was easiest)
[08:41] <seb128> pitti, it looks like the patch might not be new, just that this git gbp workflow keeps renaming patching
[08:41] <seb128> which is really annoying for reviews
[08:41] <pitti> hm, how's that?
[08:41] <seb128> I don't know, I don't use it
[08:41] <pitti> I see how they would get renamed *once* after moving from plain quilt to gbp
[08:41] <seb128> but patches keep getting renamed and according to happyaron it's because of the tools
[08:41] <pitti> but there is zero reason that they would randomly get renamed again
[08:41] <happyaron> seb128: I have different view on the debian/patches/Order-IPv6-nameservers-before-IPv4-for-dns-plugins-d.patch to him, since that behaviour isn't performing good because of the DNS thing
[08:42] <pitti> unless you acually change the commit messages
[08:42] <happyaron> seb128: I'll make sure they don't get renamed from 1.2.4
[08:42] <seb128> thanks
[08:42] <seb128> happyaron, why did they got renamed in that update?
[08:42] <seb128> can we just revert that rename?
[08:42] <pitti> well, do a clean import/export so that there is no "git diff" or renames, and from then on keep  it clean
[08:43] <seb128> pitti, https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=38a52be23a88226fc255332d6d1bd2b440bc8b5b is typically what happyaron get at every new version update
[08:44] <seb128> unsure how/why
[08:44]  * seb128 is not familiar with git gbp
[08:44] <seb128> but e.g Don-t-block-network.target-on-NetworkManager-wait-on.patch got renamed to systemd-Don-t-enable-NetworkManager-wait-online.serv.patch for whatever reason
[08:44] <pitti> seb128: hm, where's the rename?
[08:44] <pitti> ah
[08:45] <pitti> hm, looks like that got done on the Debian side?
[08:45] <seb128> but that's not a merge on debian or anything like that
[08:45] <seb128> the commit is "Update patches for new upstream release"
[08:46] <seb128> see https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu
[08:46] <pitti> -Subject: Don't block network.target on NetworkManager-wait-online.service
[08:46] <pitti> +Subject: systemd: Don't enable NetworkManager-wait-online.service statically
[08:46] <pitti> well, someone changed the commit message
[08:46] <seb128> k, maybe it's a undocumented rebase
[08:46] <pitti> no
[08:47] <pitti> rebases don't change commit messages
[08:47] <seb128> I think the bottom line is that changelog is underdocumenting what is being done
[08:47] <pitti> some*one*, not some*thing*
[08:47] <seb128> well maybe debian did change the commit message
[08:47] <seb128> and happyaron is basing is work on their branch
[08:47] <pitti> isn't debian on 1.4 already?
[08:47] <seb128> so is getting those changes
[08:47] <seb128> yes
[08:48] <pitti> (which would really be nice to get, FWIW -- upstream merged our huge ofono patches, it drops the dependency to isc-dhcp-client, etc.)
[08:48] <seb128> we are not going to do an "update n-m the week before release" this cycle again, are we? ;-)
[08:48] <happyaron> I talked with willcook_e earlier and he sugguested me to keep 1.2 this cycle..
[08:48] <seb128> yeah, we should have updated to 1.3 mid-cycle
[08:49] <seb128> but that didn't get done
[08:49] <seb128> so now is late imho
[08:49] <pitti> seb128: you are right, we still need to wait a month before we upgrade :)
[08:49] <seb128> :-)
[08:49] <happyaron> well, /me is talking with him again atm guys
[08:49] <seb128> keep 1.2 for this cycle
[08:49] <seb128> we have enough things that are behind and need to land we fixed
[08:49] <seb128> including fallout from new gtk
[08:49] <seb128> systemd user session not done yet
[08:49] <seb128> unity8 to get on the iso still
[08:50] <seb128> yakkety has an edgy feeling
[08:50] <seb128> ;-)
[08:50] <pitti> eft eft eft!
[08:50] <seb128> hehe
[09:32] <seb128> using linux is depressing some days
[09:32] <seb128> that laptop worked so nicely in trusty
[09:33] <seb128> now can't vt switch without getting the intel to the gpu lock of the xorg session to close or something
[10:15] <willcooke> errrrr
[10:15] <willcooke> suddenly I can't resize windows
[10:15] <willcooke> brb
[10:16] <davmor2> seb128, willcooke: can either of you boot from todays iso on kvm?
[10:16] <willcooke> fixed by restarting session
[10:16] <willcooke> meh
[10:16] <willcooke> davmor2, haven't tried today yet
[10:17] <davmor2> I just get a text cursor in the middle of a black screen, seems to be fine on hardware though
[10:18] <willcooke> davmor2, that's at the point it tries to start the live session or the installer bit?
[10:18] <davmor2> willcooke: it's the point in uefi that shows you the uefi menu
[10:19] <davmor2> I'll try without uefi
[10:19] <willcooke> plan
[10:20] <davmor2> so it works without uefi hmmm
[10:31] <davmor2> So I'm now using the newer OVFM from 16.10 same thing blank screen text cursor so there is a problem there for kvm
[11:27] <seb128> davmor2, I'm using virtualbox and it works fine for me (but no uefi on this machine)
[11:28] <davmor2> seb128: yeah kvm with -boot d work kvm with -pflash OVMF_CODE.fd doesn't
[12:40] <cyphermox> good morning!
[12:49] <seb128> hey cyphermox, how are you?
[12:51] <cyphermox> good, you?
[12:51] <seb128> good, waiting for days to get a bit cooler again though, over 30°C is not nice to work
[12:52] <ogra_> dont you already have the thunderstorms down there in france ?
[12:52] <ogra_> (they are announced for tomorrow in germany and come from the south)
[12:54] <cyphermox> seb128: I know what you mean, the weather is just starting to be a little cooler, and every day after work I'm neck deep in renovations
[12:54] <cyphermox> to say that it's hot to work is an understatement
[12:57] <seb128> bit of patience, winter is coming, then we can complain it's too cold ;-)
[12:57] <ogra_> \o/
[12:58]  * ogra_ imagines seb128 in a black fur coat with large sword with wolf handle ... 
[12:58] <seb128> ogra_, but yeah, most of france got rain&co so it's getting better
[12:58] <seb128> but most of the week was hot summer like
[12:59] <ogra_> yeah, same here
[12:59] <ogra_> 30+ ....
[13:17] <andyrock> morning
[13:17] <seb128> andyrock, evening!
[13:18] <seb128> how are you?
[13:18] <andyrock> :D
[13:18] <andyrock> where there is still sun
[13:18] <seb128> is sun still going up? ;-)
[13:22] <andyrock> well not
[13:22] <andyrock> so good evenging
[13:51] <seb128> andyrock, joke aside, how are you? is it hot summer still for you as well?
[13:52] <andyrock> not anymore
[13:53] <seb128> lucky you ;-)
[14:10] <seb128> going for some exercice
[14:10] <seb128> bbl
=== dpm is now known as dpm-afk
=== dpm-afk is now known as dpm
=== PaulW2U_ is now known as PaulW2U
[17:45] <davmor2> willcooke, seb128: hmmm I think we might have issues with bluetooth between unity 7/8 I can't get a simple speaker to show up in either but it does on tablet and phone
[17:46] <seb128> was it working in u7 before you installed extra things?
[17:46] <willcooke> davmor2, could it be related to airplane mode from U8 having switched off BT?
[17:47] <willcooke> just testing on a vanilla Y
[17:47] <davmor2> willcooke: it's turned back on but I can test via cli
[17:47] <davmor2> one second
[17:50] <willcooke> ok, with the u8-desktop-session-mir meta package from universe installed
[17:50] <willcooke> I can see a BT speaker and connect to it  in U7
[17:51] <willcooke> however, playing back audio from it fails
[17:51] <willcooke> and if I try and play a video it hangs until I switch back the audio to the internal soundcard
[17:51] <willcooke> so yes, we have a problem, but I think it's a different one
[17:51] <davmor2> willcooke: koza has some work ahead of him then :D
[17:52] <willcooke> heh, poor chap
[17:59] <willcooke> davmor2, I'm not sure where to log this one, against BlueZ or pulse.  Start with Bluez you think?
[18:01] <davmor2> willcooke: always start at the top of the stack and then let koza blame jhodapp :)
[18:35] <flocculant> jbicha: not sure how involved with Ubuntu Gnome you are, but it's affected by bug 1617711 - makes it hard to read the resize screen for the older people amongst us ;)
[18:35] <ubot5> bug 1617711 in ubiquity (Ubuntu) "Resize screen hard to read" [Undecided,New] https://launchpad.net/bugs/1617711
[18:56] <jhodapp> willcooke: I'm always the catch-all bucket for davmor2's woes ;)
[18:56] <willcooke> jhodapp, thanks!  It's on TheMuso's list, so will catch up with him about it first.
[18:57] <jhodapp> davmor2, willcooke: bring your device with you to the next sprint
[18:57] <willcooke> jhodapp, :) need it fixing before release really
[18:57] <jhodapp> koza will be doing a BT hackathon after hours and he promises Polish beer
[18:58]  * willcooke gathers his devices
[18:58] <willcooke> :)
[18:58] <jhodapp> willcooke, what's the issue exactly?
[18:58] <willcooke> jhodapp, https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1608820
[18:58] <ubot5> Ubuntu bug 1608820 in pulseaudio (Ubuntu) "Cannot use BT speaker - sink is suspended" [Undecided,In progress]
[18:59] <jhodapp> willcooke, does it work with the phone?
[18:59] <willcooke> jhodapp, probably.  this is for desktop 16.10
[19:00] <jhodapp> willcooke, right, I am curious as I've seen some issues from watching koza where it's been a difference sometimes between bluez versions and kernel drivers between desktop and phone
[19:00] <jhodapp> willcooke, so if it works on one, that actually makes it a lot easier to fix for the other
[19:01] <willcooke> jhodapp, oki, good to kow
[19:01] <willcooke> know
[19:01] <willcooke> thanks
[19:01] <jhodapp> np
[19:45] <seb128> k, calling it a week (I've a vac day tomorrow), have a nice w.e desktopers
[19:45] <flocculant> seb128: have a good one :)
[19:45] <seb128> thanks!
[20:57] <a1fa> whats the easiest way to wipe gnome from system (16.10) apt-get remove --auto-remove ubuntu-gnome-desktop just removes two packages, gnome-shell is still there
[21:18] <dobey> a1fa: you'd want autoremove --purge ubuntu-gnome-desktop and then probably need to do another apt-get autoremove --purge after to catch some additional packages
[21:19] <a1fa> dobey: it didnt do it for me
[21:19] <a1fa> dobey: i ended up doing apt-get purge *gnome*
[21:20] <dobey> well unity7 requires some gnome packages, so that won't be good either
[21:20] <a1fa> i purged unity7 at the moment
[21:20] <a1fa> trying to see how much i can purge before reinstalling a desktop enviroment
[21:21] <a1fa> wish there was a command to strip everything down to base
[21:26] <sarnold> gtk? gdk?
[21:29] <jbicha> a1fa: honestly, a reinstall of the desktop you like is probably the easiest
[21:30] <jbicha> Ubuntu differs from Debian in that we don't want users who remove a metapackage to also get most of their desktop autoremoved
[21:32] <a1fa> i see that ;)
[21:32] <jbicha> or you can look in your apt logs to see what packages were installed when you installed ubuntu-gnome-desktop and remove those
[21:32] <a1fa> well, i am using ubuntu-desktop-16.10 test isos
[21:32] <a1fa> so it came pre-bundled with gnome
[21:32] <jbicha> ?
[21:33] <a1fa> not sure why that was
[21:33] <jbicha> I think you downloaded the wrong iso, try http://cdimage.ubuntu.com/daily-live/current/
[21:33] <a1fa> yakkety-desktop-amd64.iso d01dda0162bb572c21f2827dd3e0c01c
[21:34] <jbicha> yeah, that's Ubuntu GNOME 16.10 Beta 1 http://cdimage.ubuntu.com/ubuntu-gnome/releases/yakkety/beta-1/MD5SUMS
[21:35] <a1fa> odd - well, i think i got everything purged, and stuff reinstalled
[21:35] <a1fa> now its a matter of finding out if its fixed. if not, i'll reinstall with new iso
[21:36] <jbicha> I really recommend you just reinstall; I don't recommend trying to turn Ubuntu GNOME into Ubuntu (Unity)
[21:37] <a1fa> yeah, compiz keeps crashing ;(
[21:37] <a1fa> i wanted to try unity8
=== alecu_ is now known as alecu