[07:21] <andyrock> msg MemoServ READ NEW
[07:21] <andyrock> sorry guys
[07:21] <Laney> retro
[07:25] <flocculant> :)
[07:32] <larsu> wow!
[07:32] <larsu> morning :)
[07:33] <Laney> laaaaaaaaaaaarrrrrrrrrssssssssssss
[07:33] <larsu> Laaaaaaaaaaneeeeeeey
[07:33] <seb128> oh, hey larsu
[07:33] <larsu> how are you? Enjoying the sprint?
[07:33] <seb128> we were just speaking about you
[07:33] <larsu> hi seb128!
[07:33] <larsu> oh really
[07:33] <seb128> and ice cream!
[07:33]  * larsu didn't do anything
[07:33] <seb128> how is Berlin?
[07:33] <larsu> oh. ice cream. where?
[07:33] <seb128> right, which is the issue :p
[07:34] <larsu> seb128: not warm
[07:34] <larsu> rainy
[07:34] <seb128> we are looking at somebody wanting to update gtk and fix the themes :p
[07:34]  * seb128 hides
[07:34] <seb128> joke aside we miss you here :-(
[07:34]  * larsu laughs and laughs and laughs and laughs and starts crying a little bit
[07:34] <Laney> seb128 will pay himself
[07:34] <Laney> €1000 per changed line
[07:34] <seb128> that better is a short diff
[07:34] <larsu> not sure it's worth it :)
[07:34] <seb128> wait
[07:34] <seb128> WAIT
[07:35] <larsu> haha
[07:35] <seb128> I've an idea
[07:35] <seb128> attente, if you update gtk I might get you out of the Vancouver sprint
[07:35] <Laney> D:
[07:35] <larsu> there's a Vancouver sprint?
[07:35] <seb128> snappy team one
[07:36] <attente> so tempting
[07:36] <larsu> that's just around the corner for attente. Same country!
[07:36] <larsu> hi attente!
[07:36] <seb128> yeah, he got invented
[07:36] <attente> hi larsu!
[07:36] <seb128> he's thrilled
[07:36] <seb128> invited even
[07:36] <larsu> I can imagine
[07:36] <larsu> vancouver is a nice city I hear
[07:36] <attente> i thought willcooke was our themes guy
[07:36] <seb128> somebody told me that it got more rain that London
[07:36] <willcooke> :D
[07:36] <seb128> google seems to back that statement up
[07:37] <seb128> oh, right!
[07:37] <larsu> seb128: is that possible?
[07:37] <larsu> that means it must be under water the whole time
[07:37] <seb128> apparently
[07:37] <seb128> it rains like 150 days a year
[07:37]  * larsu does some calculations and comes to the conclusion that that's a lot of days
[07:41] <Laney> larsu: how's cockpit?
[07:41] <larsu> Laney: loads of fun
[07:41] <larsu> tons of new stuff still
[07:41]  * larsu is having a blast
[07:42] <larsu> we publish to a debian repo and ubuntu ppa for every release now
[07:42] <Laney> \o/
[07:42] <larsu> and people seem to already be starting to use it
[07:42] <Laney> nice
[07:42] <larsu> ya, my first little project :)
[07:43] <larsu> Laney: how's gnome software?
[07:43] <larsu> did you guys settle on a name?
[07:44]  * larsu should download the release
[07:44] <Laney> getting there
[07:44] <Laney> it's a little bit rough in the release
[07:44] <Laney> but we fixed some stuff since and there is an sru waiting
[07:45] <larsu> nice
[07:45] <Laney> attente is rebasing on 3.20.2 now
[07:45] <larsu> congrats!
[07:45] <Laney> the name is Ubuntu Software
[07:45]  * Laney coughs
[07:45] <larsu> makes sense
[07:45] <larsu> Ubuntu Software Center was perfect
[07:46] <larsu> but changing the name made sense, since it's all new
[07:50] <Laney> http://people.canonical.com/~laney/weird-things/lifeisgood.png
[07:50] <larsu> awww
[07:53] <Laney> cool eh
[08:00] <larsu> indeed
[08:21] <willcooke> desktoppers:  please create yourself a board under this group:  https://trello.com/ubuntudesktop
[09:09] <Sweet5hark>  wakkety will!
[09:12] <Trevinho> xnox: hey... You remember https://code.launchpad.net/~xnox/upstart/lp1433013/+merge/259317 ?
[09:13] <Trevinho> xnox: since I've been just facing with a bug with gnome terminal missing the menu-bar... This is because it dbus-activates the gnome-terminal-server, and that instance was missing the proper GTK_MODULE env var
[09:13] <xnox> Trevinho, yeap, same bug
[09:13] <xnox> but that part of code never worked though =(
[09:13] <xnox> despite all that code, it fails to actually do anything =)
[09:13] <Trevinho> so... Ok, that bug can be even fixed in a different way, but... It's just an example how we should make upstart and dbus match the env
[09:13] <Trevinho> xnox: well, patching upstart with it, it does work
[09:14] <xnox> Trevinho, oh really, i must have done it wrong.
[09:14] <Trevinho> I've just taken the xenial src, patched with it... and voila!
[09:14] <xnox> Trevinho, maybe i should really land it, and SRU it?
[09:14] <Trevinho> xnox: yeah, it would be nice
[09:14] <xnox> Trevinho, do we need it on touch too, or not?
[09:15] <Trevinho> xnox: no, not that I know
[09:15] <xnox> ack
[09:15] <Trevinho> i still see some alt+f2  / super differences with that, but still better than nothgin
[09:15] <Trevinho> nothing*
[09:19] <Trevinho> xnox: it could be probably nice to do the other way around, so... Dbus vars to be set to upstart
[09:19] <duflu> willcooke: I'm struggling to remember... Why do we use Trello? Other than for cosmetic superiority over Launchpad?
[09:21] <xnox> Trevinho, yes
[09:21] <xnox> Trevinho, but patching dbus is not nice either =(
[09:21] <Trevinho> Yeah, I guess
[09:22] <Trevinho> xnox: then i had this for gnome-session, which could be sitll be worth http://pastebin.ubuntu.com/16092825/
[09:22] <xnox> if only there were hooks =)
[09:23] <pitti> Laney: FYI, I committed https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/commit/?id=eda12ffa to get some less spam; but it'll be a while until I can roll this out as upstart doesn't use the new job file as long as there's still any instance running
[09:23] <xnox> Trevinho, working out which environmental variables are missing from where, and what should be the environment variable flow would be a good thing.
[09:24] <Laney> pitti: nice --- do you have a way to monitor for stuck instances?
[09:30] <pitti> Laney: what do you mean with "stuck"? adt-run has timeouts for pretty much everything, so if an ssh command doesn't come back after a reasonable time it is aborted and counts as tmpfail
[09:30] <seb128> duflu, hey, do you think you can manage to have a look to that upower/usd issue?
[09:30] <Laney> pitti: quota exceeded is due to nova messing up usually right?
[09:31] <duflu> seb128: Only on weekends. It's my production server :(
[09:31] <duflu> Annoyingly its sister machine always runs the latest Ubuntu and has no problem
[09:32] <seb128> k, sorry to ask you to debug that, but nobody here seems able to reproduce
[09:32] <pitti> Laney: in a lot of cases, yes; over time, the quota DB gets out of sync, and it says that I use e. g. 5 instances, 4 CPUs, and 25 GB mem more than I actually do
[09:32] <pitti> Laney: so from time to time I need to prod IS to reset that
[09:32] <Laney> pitti: so if you're filtering out those mails then it might be that nobody knows about the quota errors for a while
[09:32] <duflu> seb128: Well, there are 30-something people subscribed to the bug (from the 4000 crash reports)
[09:32] <seb128> pitti, does the udisks issue duflu emailed us about ring any bell to you?
[09:33] <pitti> Laney: but also, if one more more "bigtests" run (which use m1.large instead of the autopkgtest flavor) these block more resources, and hten we can't run the full number of workers any more
[09:33] <seb128> duflu, right, I know, I would like to see it resolved as well
[09:33] <pitti> seb128: upower? no, not off the top of my head
[09:33] <duflu> seb128: I'm guessing it will be "query this DMI thing", which I can do right now in 14.04
[09:34] <seb128> pitti, right, wrong u, sorry ;-)
[09:35] <pitti> Laney: and while I'm at it, "No valid host was found. There are not enough hosts available." should also be blacklisted I guess
[09:36] <duflu> seb128: I'm guessing my desktop has no "lid" so the object is NULL for a reason
[09:36] <seb128> duflu, well, it shouldn't have a lid if it's a desktop right?
[09:36] <duflu> seb128: Not sure. There is a chassis switch
[09:37] <duflu> which may qualify
[09:39] <seb128> that might be what is specific to your config
[09:42] <duflu> seb128: I'm more curious about why the absence of a lid switch is a fatal error
[09:43] <duflu> That's what it sounds like
[09:43] <seb128> bug I guess
[09:45] <seb128> pitti, do you know offhand if there is a way to tell libc to read locales definition in another path than  /usr/lib/locale/locale-archive ?
[09:46] <pitti> seb128, duflu: https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/power/gsd-power-manager.c#n2589
[09:46] <pitti> this does an explicit check for the lid
[09:46] <pitti> which u-s-d doesn't according to https://launchpadlibrarian.net/241244694/StacktraceSource.txt
[09:46]  * pitti follows up to the bug, better place there
[09:46] <seb128> pitti, danke
[09:47]  * duflu grabs the xenial source to compare
[09:49] <duflu> pitti, seb128: Indeed the xenial source is missing the manager->priv->lid_is_present check
[09:50] <pitti> followed up to bug 1546641
[09:50] <pitti> seb128, duflu: more importantly, lid_is_present seems to be missing completely from u-s-d?
[09:51] <seb128> pitti, duflu, that was added in https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=d491ebf6325fd1883e5fa81ee0f5daa7eb281c3b
[09:51] <duflu> pitty: Horray
[09:51] <seb128> then we might need https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=dcf8dc956b050dc0e246d48ee7365d88a8f09357
[09:52] <pitti> wow, u-s-d hasn't been merged with g-s-d in a long time, has it
[09:53] <seb128> indeed not
[09:53] <seb128> well some of the plugins were
[09:53] <seb128> but not the power one
[09:53] <Trevinho> andyrock: https://code.launchpad.net/~3v1n0/bamf/safer-dbus-runner/+merge/293229
[09:53] <seb128> I started having a look some cycles back but it was quite some changes/not easy to review and we don't really have issues justifying it
[09:54] <seb128> well out of that one now
[09:56] <popey> seb128: where did you push that snapcraft yaml yesterday? I'd like to take a look
[09:56] <Laney> pitti: stress-ng seems to be stressful :P
[09:57] <seb128> popey, nowhere yet
[09:58] <popey> seb128: oh, i thought you put it somewhere for sergio to look at?
[09:58] <duflu> pitti: The NULL is not coming from u-s-d. It's originating from the upower logic
[09:58] <duflu> 'proxy' is NULL
[09:59] <duflu> So the absence of a lid may be fine. Just some UPower bug
[10:00] <popey> seb128: anyway, can I get a copy? :)
[10:00] <pitti> duflu: proxy? the only NULL thing in https://launchpadlibrarian.net/241244694/StacktraceSource.txt is the internal object= in the topmost frame
[10:00] <pitti> as there is no lid
[10:00] <seb128> popey, you need it now, I'm cleaning and was aiming at pushing before lunch
[10:01] <pitti> up_client_get_lid_is_closed() only returns a bool, there is no third value to say "there is no lid", you need to check it before
[10:01] <popey> seb128: ok, I can wait :)
[10:01] <duflu> pitti: Yeah I'm looking at the xenial source. It's not up_client that's NULL... it got past that
[10:01] <pitti> duflu: exactly
[10:01] <duflu> Admittedly I have no idea what proxy is
[10:01] <duflu> And now it's dark and dinner time
[10:03] <duflu> pitti: The NULL object appears unrelated to lids of any sort. It's just a context pointer
[10:03] <pitti> Laney: yeah, exit code 255, apparently it kills ssh :/
[10:03] <duflu> UPower client not initialized properly
[10:04] <pitti> I thought you just said that up_client was not NULL (and that's also what the stack trace says )
[10:04] <pitti> it does call the up_client_get_lid_is_closed() internal function, thus both the proxy and the up_client are fine
[10:05] <duflu> pitti: No, it crashes on the first attempt to dereference proxy
[10:06] <pitti> ok, then I don't know
[10:06] <duflu> It's in UPower I think
[10:06] <duflu> And not related to lids
[10:06] <pitti> and it seems you have some different bug than the one above
[10:06] <duflu> I'm just going on the stack trace in the bug
[10:06] <seb128> popey, try http://paste.ubuntu.com/16093118/ (sorry, having > 3 conversations ongoing)
[10:07] <popey> \o/
[10:07] <popey> thanks
[10:07] <seb128> popey, oh, change the +exec /bin/bash #$SNAP/usr/bin/gnome-calculator back :p
[10:07] <seb128> popey, I made it start bash for debug
[10:08] <popey> what is that a diff from?
[10:10] <seb128> popey, sorry, lp:~ubuntu-desktop/+junk/gnome-calculator-snap
[10:11] <popey> thanks
[10:13] <duflu> seb128, pitti: Any chance this is just GSD starting before UPower?
[10:13] <duflu> That's what it feels like
[10:13] <duflu> A race
[10:13] <seb128> could be
[10:13] <duflu> USD starting before UPower
[10:13] <seb128> what is weird is that usd didn't change for cycles
[10:13] <seb128> why would that start being an issue now?
[10:13] <duflu> Yeah but raciness can change with the rest of systemd
[10:14] <duflu> Should be easy to test. If only I still had a xenial install on this machine
[10:15] <seb128> so you basically say to try to start u-s-d without having upower
[10:15] <seb128> ?
[10:15] <duflu> seb128: Yep, try it
[10:15] <pitti> duflu, seb128: upower is dbus activated, that can't happen
[10:15] <pitti> connecting to o.f.UPower will block until it's running
[10:16] <duflu> Hmm.
[10:16] <duflu> pitti, seb128: OK too hard. EOD instead...
[10:16] <duflu> o/
[10:16] <pitti> duflu: I'd really recommend either adding that commit or replacing all _lid_is_closed() calls with "False" for a local test if it stops crashing
[10:16] <duflu> I'll need to reinstall xenial out of hours...
[10:16] <seb128> pitti, re. the previous comment, up_client_get_lid_is_closed() shouldn't segfault on a system without lid I would argue
[10:17] <seb128> duflu, have a good evening!
[10:17] <duflu> Later
[10:17] <pitti> seb128: yeah, an assertion failure would be more adequate
[10:17] <pitti> from a programmer's POV
[10:17] <seb128> or just returning FALSE
[10:17] <pitti> not that it would change much for the user
[10:17] <pitti> seb128: no, that'd be wrong
[10:17] <pitti> you'd need a third state
[10:17] <pitti> at most it could return True
[10:18] <seb128> right
[10:18] <pitti> you mustn't suspend a desktop without a lid, thinking that the lid is closed :)
[10:18] <Trevinho> Laney: https://code.launchpad.net/~3v1n0/gnome-session/upstart-export-variables/+merge/293236
[10:18] <pitti> so it could be changed to return an enum, but that'd be an API/ABI change and even more intrusive
[10:18] <seb128> let's see if duflu manage to debug a bit more tomorrow
[10:18] <pitti> making it an assert would make the error a bit clearer, though
[10:18] <seb128> if that's the issue
[10:18] <seb128> I wonder what old upower did/if that changed
[10:19] <seb128> because at said the client side code didn't change
[10:19] <seb128> I guess I can try on a porter box
[10:19] <seb128> those don't have lid
[10:20] <seb128> pitti, thanks for the input on that bug
[10:20] <seb128> pitti, unsure if you saw my other question but do you know if " /usr/lib/locale/locale-archive" is easily relocatable?
[10:20] <seb128> (I guess not)
[10:21] <pitti> seb128: hmm, $LOCPATH I think, but I'm not sure if that applies to the archive as well
[10:22] <seb128> pitti, let me try that
[10:22] <pitti> seb128: see man locale
[10:22] <pitti> seb128: but I only ever tried that with plain compiled locales, not the archive
[10:22] <seb128> that would work too
[10:22] <pitti> seb128: not sure what you want to do, but you don't necessarily need an archive format?
[10:23] <seb128> I want to do an hack you don't want to know about :p
[10:23] <seb128> basically trying to get a snap to load translations, and since there are no locale in the core trying to include those in the snap...
[10:23]  * seb128 ashamed
[10:34]  * dpm hugs seb128
[10:34]  * seb128 hugs dpm back
[10:35] <pitti> seb128: I thought snaps did all those magic bind mounts
[10:36] <pitti> we still can't build snaps with normal install locations?
[10:36] <seb128> dunno about the mounts but if they do that doesn't include locales
[10:36] <seb128> and no
[10:36] <pitti> seb128: no, you were right, I don't want to know :)
[10:36] <seb128> lol
[10:36]  * seb128 hugs pitti
[10:37]  * pitti mumbles something about "btrfs subvolumes", a solved problem for many years, and goes on :)
[10:38] <seb128> one day btrfs is going to be good enough to be default :-)
[10:38] <pitti> seb128: for this purpose it's been good enough for years
[10:38] <pitti> this is all read-only after all
[10:39] <seb128> righ
[10:39] <seb128> right
[10:39] <pitti> much bettern than overlayfs for sure
[11:12] <qengho> skip btrfs. straight to zfs.
[11:13]  * popey hugs btrfs tightly
[11:14] <pitti> has been chugging along happily on my laptop since I have it (~ 2 years), *shrug*; but I do realize that cking is able to break it
[11:14] <pitti> then again, show me a thing that cking cannot break :)
[11:14]  * cking likes testing stuff
[11:14] <pitti> cking: for example, stress-ng kills ppc64el instances in a loop (more precisely, it seems to kill sshd)
[11:16] <cking> pitti, stress-ng is quite good at finding issues like that, but killing sshd is a bit wrong
[11:16] <pitti> cking: http://paste.ubuntu.com/16093758/ is the logtail
[11:16] <pitti> cking: 255 is ssh's exit code for interrupted connections usually
[11:18] <popey> willcooke: https://bugs.launchpad.net/ubuntu/+source/glom/+bug/1573801
[11:18] <popey> looks like it needs a rebuild?
[11:19] <cking> pitti, what does the kernel log say, was the kernel killing the entire session because stress-ng was too stressy for it?
[11:20] <pitti> cking: I don't have it right now, I'll see to run this manually and grab it and file a proper bug
[11:20] <pitti> cking: doesn't seem to affect x86
[11:20] <pitti> but, lunch first :)
[11:20] <seb128> popey, looks like it, can you tell doko? ;-)
[11:20] <cking> pitti, indeed food is always best
[11:21] <pitti> popey: bug 1573801
[11:21] <pitti> Murray also G+'ed about it
[11:21] <pitti> glom is an orphan, nobody maintains it in Ubuntnu
[11:23] <seb128> he should snap it ;-)
[11:25] <Laney> el troll
[11:27]  * xnox ponders what is glom
[11:33] <popey> willcooke: un petit bug pour vous https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1576167
[11:52] <seb128> oh, popey filed another dup bug ;-)
[11:52]  * seb128 closes and collect free lp karma
[11:52] <popey> :(
[11:53] <seb128> popey, sorry man :-)
[11:53] <seb128> willcooke can still fix it!
[11:53] <popey> \o/
[11:53] <popey> fix it wiiiiilllll
[11:55] <davmor2> will'll fix it for you, and you, and you
[11:57] <willcooke> davmor2, let's have a look in Willy's magic chair...
[12:03] <seb128> pitti, the LOCPATH tips works, is there a similar one for the .mo to load? TEXTDOMAINDIR seems to work for the gettext command but only for that
[12:06] <pitti> seb128: hmm, bindtextdomain() doesn't say, but I thought there was some env variable, han gon
[12:06] <seb128> pitti, NLSPATH?
[12:07] <pitti> seb128: sounds plausible, yes
[12:07] <seb128> pitti, thanks
[12:08] <pitti> seb128: indeed, in man catopen
[12:12] <willcooke> popey, seb128 - looks like a very similar bug to the calendar white corners.  If I remove the view class it works.
[12:18] <seb128> willcooke, https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1052936/comments/5 might be useful?
[12:18] <seb128> unsure if it's a theme or a widget bug, maybe we should set some bg
[12:19] <willcooke> seb128, thanks.  yes, I think that's exactly it
[12:49] <andyrock> desrt: https://bugzilla.gnome.org/show_bug.cgi?id=765723
[13:01] <desrt> no shit
[13:01] <desrt> andyrock is andrea?
[13:01] <desrt> how did i not already know this?
[13:01] <andyrock> lol
[13:01] <desrt> everything makes so much more sense now
[13:20] <seb128> pitti, NLSPATH doesn't seem to work, seeing that we patch the glibc code to add the langpack dir I'm going to assume that there is no dynamic way (though we might have done it this way to get to work in any case and not relying on an env to be set?)
[13:20] <seb128> anyway I don't need to get that working today
[13:20] <seb128> I was just playing with it to see if I get somewhere
[13:22] <a1fa> grr.. run into a nasty bug with unity
[13:24] <a1fa> unity 7.4 - unable to interact with windows (gnome terminal 3.18) after a while
[13:24] <desrt> you have a more general problem there: apps give hard-coded paths to bindtextdomain() as a matter of course
[13:24] <desrt> so even if you managed to get the system message catalogs working properly, pretty much every app using gettext is gonna have a bad time
[13:25] <seb128> going to need to "fix" bindtextdomain() :p
[13:25] <desrt> or snappy...
[13:25] <seb128> you would think so
[13:26] <desrt> we should be using mount namespaces
[13:26] <desrt> this /snap/ business is a mountain of pain
[13:28] <desrt> another alternative is to recompile things
[13:28] <desrt> the core issue here is that we're using .debs that assume that they are installed at a particular point -- and they are not
[13:30] <ogra_> just use jhbuild for gtk snaps ;)
[13:30] <desrt> won't help you with glibc :p
[13:30] <desrt> but ya... otherwise, it's actually a pretty nice idea
[13:30] <larsu> put glibc in jhbuild!!!!!!!111!
[13:30] <ogra_> hah
[13:31] <desrt> this is why larsu doesn't work here anymore
[13:31] <a1fa> https://answers.launchpad.net/unity/+question/292688
[13:31] <a1fa> anybody else having same issues?
[13:31] <seb128> a1fa, hey, I don't think that was mentioned/reported before
[13:32] <a1fa> thanks
[13:32] <desrt> hikiko, andyrock, Trevinho: ^^
[13:32] <a1fa> it's annoying as hell, seb128 anything i can collect from unity to post/provide?
[13:32] <seb128> a1fa, the people desrt just pinged might be able to help you
[13:33] <desrt> official response from unity developers: "let's remove gnome-terminal"
[13:33] <desrt> :)
[13:33] <a1fa> lets do it
[13:33] <a1fa> but what do we replace it with?
[13:33] <desrt> terminator, apparently
[13:33] <larsu> vt1
[13:33] <ogra_> the terminal-app snap indeed
[13:34] <a1fa> hm
[13:34] <larsu> term.js!!
[13:34] <desrt> a terminal is just about the last thing that one wants to snap
[13:35] <a1fa> so desrt i sthat really the official answer? bundle something else?
[13:35] <desrt> a1fa: na.. we're joking around here
[13:35] <a1fa> i am all for it
[13:35] <desrt> we're all at a sprint together right now
[13:35] <hikiko> hey a1fa
[13:35] <a1fa> yello' hikiko
[13:35] <desrt> they're speaking italian now.. the only thing i understand is the word "terminal" from time to time
[13:35] <andyrock> a1fa: can you please open a bug
[13:36] <hikiko> he already did andyrock
[13:36] <Trevinho> a1fa: i actually got once...
[13:36] <hikiko> https://answers.launchpad.net/unity/+question/292688
[13:36] <desrt> hikiko: that aws a support request...
[13:36] <andyrock> not an answer
[13:36] <andyrock> a bug report it's easy to track
[13:36] <hikiko> sorry :)
[13:36] <a1fa> https://bugs.launchpad.net/unity/+bug/1576224
[13:36] <andyrock> also try with sudo apt-get remove gnome-terminal should fix the issue
[13:36] <andyrock> ;)
[13:37] <a1fa> this is new, i used 15.10 before unity 7.3? and it never happened in 7.3
[13:37] <hikiko> I don't use gnome terminal but I am going to try to reproduce that issue
[13:37] <hikiko> thanks for reporting a1fa
[13:37] <andyrock> just kidding we are on it
[13:37] <a1fa> you guys are great
[13:37] <a1fa> you fixed my last two bugs with unity and gnome terminal
[13:37] <andyrock> a1fa: when you reproduce it try to switch tty
[13:38] <andyrock> i don't use gnome-terminal too much but i noticed something wrong with the mouse and gnome-terminal
[13:38] <andyrock> usyally a tty switch works here
[13:38] <a1fa> alt+f1?
[13:39] <hikiko> a1fa, ctrl+alt+f1 and then ctrl+alt+f7 to go back
[13:39] <a1fa> yeah did that
[13:39] <a1fa> did not fix
[13:39] <a1fa> only way to fix it, is to "exit"
[13:39] <hikiko> I had some issues with the ttys lately :/
[13:40] <a1fa> now, when i switched back, my unity bar was all garbled
[13:40] <a1fa> but thats a whole another story
[13:40] <hikiko> no it's not
[13:40] <a1fa> and i moved my unity bar to the bottom :)
[13:40] <hikiko> what do you mean garbled?
[13:40] <hikiko> oh
[13:40] <hikiko> a1fa,
[13:40] <a1fa> typical gpu artifacting
[13:40] <hikiko> did you dist-upgrade when you got that issue?
[13:41] <a1fa> i had to do dist-upgrade to go to 16.04
[13:41] <hikiko> the question is:
[13:42] <hikiko> it was after a dist-upgrade (after which you didn't reboot) that you  got your unity bar garbled?
[13:42] <a1fa> oh no
[13:42] <hikiko> ok :)
[13:42] <a1fa> if i take a screenshot of the garble, it disappears
[13:42] <hikiko> oh
[13:42] <a1fa> but also hovering over the menu, clears it
[13:43] <hikiko> then it's the redraw-damage issue I am trying to fix for the ezoom ... :/
[13:43] <hikiko> I'm investigating that a1fa
[13:43] <a1fa> i'm on nvidia gtx970
[13:43] <a1fa> if that would make any difference
[13:43] <hikiko> no :) but thank you
[13:44] <a1fa> cool :)
[13:44] <hikiko> opening the menu causes a redraw
[13:44] <hikiko> and solves the problem
[13:45] <hikiko> but I'm trying to do a proper fix for that
[13:45] <hikiko> so that you don't have to :p
[13:46] <a1fa> how do you guys use your unity launcher? bottom? left? auto hide?
[13:46] <a1fa> i have a hard time adjusting to auto hide, can never get sensitivity right
[13:46] <hikiko> I use it on the left and always visible
[13:47] <a1fa> oh, i had another thing.. mouse acceleration
[13:47] <hikiko> I like it to be visible all the time because the wide screens have all that space on the right
[13:47] <a1fa> turning down mouse pointer speed does not disable mouse acceleration tottally
[13:48] <a1fa> i have to run a script xset m 0 0
[13:48] <hikiko> mmm this must be X not unity
[13:48] <hikiko> how do you disable it?
[13:48] <a1fa> xset m 0 0
[13:50] <a1fa> o i have some more info on the gnome terminal bug.. it literally clicks right through the window, as if the window is not there
[13:50] <a1fa> my mouse pointer just changed to a hand pointing while hovering over a link that was hidden by the top bar
[13:50] <hikiko> oh
[13:50] <hikiko> so then compiz loses track of the window
[13:50] <hikiko> the question is why
[13:51] <a1fa> that sounds like the last bug i reported when switching windows using alt-tab
[13:51] <hikiko> you mean that when you click the window
[13:51] <a1fa> crazy enough, it was gnome terminal
[13:51] <a1fa> yeah
[13:51] <hikiko> and you have some other window behind it
[13:51] <hikiko> the window behind
[13:51] <hikiko> will receive the click?
[13:52] <a1fa> yes, browser behind the terminal, and browser gets a click instead of the terminal
[13:52] <a1fa> but if i click inside the terminal, it works fine
[13:52] <hikiko> this means that compiz doesn't track the gnome terminal anymore
[13:52] <hikiko> so it's probably in a bad state
[13:52] <a1fa> borders, and top bar are the ones having issues
[13:52] <a1fa> is there a way to cycle compiz?
[13:52] <a1fa> w/o affecting content?
[13:52] <hikiko> the question is why gnome terminal, might be a bug in gnome-terminal that causes that
[13:53] <a1fa> ie not turning of terminals
[13:53] <hikiko> when this occurs
[13:53] <a1fa> it was not present in 15.10 as far as i remember
[13:53] <hikiko> cycle compiz?
[13:53] <hikiko> what do you mean?
[13:54] <a1fa> restart compiz without restarting unity
[13:54] <hikiko> compiz --replace &
[13:54] <hikiko> might need to run:
[13:54] <a1fa> should i try to see if it would fix the problem?
[13:54] <hikiko> export COMPIZ_CONFIG_PROFILE=ubuntu first
[13:54] <a1fa> that fixed it
[13:55] <hikiko> sure but this doesn't mean necessarily that the bug comes from compiz
[13:55] <a1fa> ok, i'll let compiz run like this, and if the bug reoccurs, maybe we get some messages?
[13:58] <a1fa> so far so good. i keep on bragging about unity as the only viable desktop for linux without having to edit config files like a caveman
[14:14] <hikiko> a1fa, if you could ping me when you get it again that would be great
[14:18] <hikiko> and if you could update the bug description with all the steps to reproduce it if you haven't done so already
[14:19] <hikiko> + a1fa thanks for letting us know!
[15:08] <a1fa> i am here
[15:08] <a1fa> i just lost all my terminals :(
[15:15] <a1fa> 3 terminals are still running but they are not visible, cant alt tab to thenm
[15:24] <Trevinho> a1fa: is the terminal just hanging?
[15:24] <Trevinho> a1fa: also, if you run other apps do they run, right?
[15:25] <Trevinho> a1fa: try to do an
[15:26] <Trevinho> xwininfo -shape -frame -tree
[15:26] <Trevinho> on that window (launch that from xterm)
[15:33] <andyrock> also run on xterm
[15:33] <andyrock> qdbus --literal org.ayatana.bamf /org/ayatana/bamf/matcher org.ayatana.bamf.matcher.XidsForApplication "/usr/share/applications/gnome-terminal.desktop"
[15:33] <andyrock> and post the output
[15:33] <andyrock> a1fa ^^
[16:08] <a1fa> jk
[16:08] <a1fa> sorry
[16:08] <a1fa> k.. i was afk dealing with work crap
[16:09] <a1fa> [Argument: au {59942595, 59933040, 59913735, 58720266, 59901365, 58844228, 58748122}]
[16:09] <a1fa> but i can only alt tab between 4 windows
[16:15] <seb128> desktoppers, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=snap-desktop-issue
[16:15] <seb128> list of snappy issues we hit with gnome-calculator
[16:16] <seb128> if some are missing feel free to file and tag
[16:16] <willcooke> great stuff, thanks seb128
[16:16] <seb128> yw!
[16:19] <popey> FJKong_: & happyaron if you have a minute or two, could you look at 17:14 <rvr> Done!
[16:19] <popey> bah!
[16:19] <popey> I fail at paste
[16:19] <popey> FJKong_: happyaron 17:14 <rvr> Done!
[16:19] <popey> AAAARGH!
[16:19] <popey> https://translations.launchpad.net/music-app/refactor/+pots/com.ubuntu.music/zh_CN/+translate?show=untranslated
[16:20] <popey> that
[16:21] <happyaron> looking
[16:21] <FJKong_> popey: okay
[16:21] <popey> thank you!  😃
[16:24] <qengho> 12:19:55 < popey> FJKong_: happyaron 17:14 <rvr> Done!
[16:26] <happyaron> popey: done
[16:27] <FJKong_> EOF