[08:05] <mterry> robert_ancell,  https://wiki.ubuntu.com/DesktopTeam/DejaDup
[08:06] <mterry> robert_ancell, https://wiki.ubuntu.com/UbuntuEngineering/12.04/UpstreamDevelopment/ProjectTracking
[08:07] <mterry> robert_ancell, https://wiki.ubuntu.com/UbuntuEngineering/12.04/UpstreamDevelopment talks about requirements a bit
[08:25] <kenvandine> mterry, i just proposed https://code.launchpad.net/~ken-vandine/gwibber/lp_906916/+merge/88455
[08:25] <kenvandine> which i would like to include in this mornings upload
[08:25] <mterry> kenvandine, looking
[08:25] <kenvandine> mterry, thx
[08:25] <kenvandine> mterry, it's been in the unity-team ppa and several people have tested it
[08:27] <pitti> cyphermox: bug 836250
[08:27] <ubot2`> Launchpad bug 836250 in linux "[Oneiric] [Regression] Intel Corporation Centrino Ultimate-N 6300 poor networking, packet loss and very slow Lenovo X201 and T500 laptops" [Medium,In progress] https://launchpad.net/bugs/836250
[08:34] <robert_ancell> seb128, https://wiki.ubuntu.com/DesktopTeam/LightDM https://wiki.ubuntu.com/DesktopTeam/UnityGreeter
[08:37] <kenvandine> mterry, watch -n0.1 'ps -e -o pcpu,rss,comm|grep gwibber-service'
[08:46] <seb128> desrt, https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/911263
[08:46] <ubot2`> Launchpad bug 911263 in gtk+3.0 "Update overlay scrollbar patch" [Undecided,New]
[08:55] <cyphermox> kenvandine:
[09:05] <kenvandine> mterry, do you have time to do a review of the libdee/libunity port too?  i think didrocks is a bit busy atm
[09:05] <mterry> kenvandine, sure
[09:05] <kenvandine> ok, let me make sure he hasn't started it
[09:06] <pitti> vuntz: bonjour! ca va?
[09:06] <vuntz> pitti: mon ami !
[09:06] <kenvandine> mterry, https://code.launchpad.net/~ken-vandine/gwibber/libdee_libunity_port/+merge/88454
[09:06] <kenvandine> mterry, thx
[09:07] <pitti> vuntz: got a minute to pick your brain about libwnck?
[09:08] <vuntz> pitti: sure thing
[09:09] <pitti> vuntz: so, I was debugging why notify-osd wakes up with each key press and focus change event
[09:09] <pitti> vuntz: and eventually found out that calling wnck_screen_get_default () triggers that
[09:09] <pitti> vuntz: this sets up an X event filter (_wnck_event_filter_init())
[09:09] <pitti> vuntz: but there is no API to shut that down again
[09:09] <didrocks> mvo: good morning!
[09:10] <didrocks> good morning vuntz :)
[09:10] <pitti> vuntz: and it's a static reference, you can't use _unref() or so to stop it
[09:10] <pitti> vuntz: would you be opposed to something like wnck_screen_uninitialize() which stops the event filter?
[09:10] <didrocks> mvo: I uploaded gir1.2-unity-5.0. Do you want to update update-manager yourself or do you want me to do it (for real, this time ;))?
[09:10] <vuntz> pitti: https://bugzilla.gnome.org/show_bug.cgi?id=642692
[09:10] <pitti> vuntz: I'll file an upstream bug in a minute and are happy to work on a patch
[09:10] <ubot2`> Gnome bug 642692 in general "Provide wnck_shutdown() (?)" [Normal,New]
[09:10] <didrocks> mvo: I saw there is some UNRELEASED stuff there, hence the question
[09:10] <vuntz> pitti: there you go
[09:11] <pitti> vuntz: hah
[09:11] <vuntz> didrocks: blop :-)
[09:11] <pitti> vuntz: so, if that approach is fine with you, I'll get started on that
[09:11] <pitti> "kill all unnecessary wakeups"
[09:11] <vuntz> sure
[09:11] <pitti> vuntz: merci Monsieur
[09:12] <vuntz> pitti: although I'm unsure if this would fix the thing for notify-osd -- it sounds weird to use libwnck there, to start with
[09:12] <pitti> vuntz: it uses it to check if there is any maximized window
[09:13] <vuntz> pitti: hrm, does that mean that you want to call wnck_screen_get_default() each time there's a notification, and then wnck_shutdown()?
[09:13] <pitti> i. e. it iterates over wnck_screen_get_windows()
[09:13] <pitti> vuntz: is there a better way?
[09:13] <seb128> pitti, can you bump the build score of lightdm in https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages?
[09:13] <mterry> kenvandine, seriously?  ;)
[09:13] <mterry> - _model = new Dee.FilterModel (_sort_filter, _streams_model);
[09:13] <mterry> + _model = new Dee.FilterModel (_streams_model, _sort_filter);
[09:13] <vuntz> pitti: don't know, but that's pretty ugly :-)
[09:14] <pitti> vuntz: for sure :)
[09:14] <kenvandine> mterry, yes...
[09:14] <kenvandine> i know :)
[09:15] <vuntz> pitti: but there's probably no good & easy way to do that another way, I guess (without adding some new stuff elsewhere, I mean)
[09:16] <pitti> vuntz: is wnck_screen_get_default () very expensive?
[09:16] <pitti> it didn't seem so from my cursory glance at the code
[09:18] <vuntz> pitti: what's expensive is getting all windows and their attributes
[09:19] <pitti> vuntz: ack; but it already does that each time when there is a bubble :/
[09:19] <vuntz> pitti: not really
[09:19] <vuntz> pitti: if you don't call wnck_shutdown(), then the data is automatically fetched when there's a change
[09:19] <vuntz> (hence all the wakeups)
[09:20] <vuntz> pitti: so it comes for free in that case
[09:20] <pitti> wnck_screen_force_update() doesn't update it again?
[09:20] <vuntz> you're kidding me
[09:20] <pitti> vuntz: but even then, updating it at each key press sounds even worse to me
[09:20] <vuntz> wnck_screen_force_update() is called every time?
[09:20] <vuntz> even though there's a main loop?
[09:21] <vuntz> so, the current  code is mis-using the API
[09:21] <vuntz> anyway
[09:21] <vuntz> pitti: if you want to avoid the wakeups, what you propose sound right
[09:21] <pitti> vuntz: http://bazaar.launchpad.net/~canonical-dx-team/notify-osd/oneiric/view/head:/src/dnd.c#L201
[09:21] <pitti> vuntz: it's calling that for each new bubble
[09:21] <pitti> and yes, it's ridiculously expensive :(
[09:22] <vuntz> the wnck_screen_force_update() call shouldn't be needed there
[09:22] <pitti> in fact, it calls dnd_dont_disturb_user() each time, which dnd_has_one_fullscreen_window () is part of
[09:22] <vuntz> unless you do the shutdown thing, of course
[09:22] <pitti> vuntz: *nod*
[09:22] <pitti> what this tries to do is to not show a notification if there is a fullscreen window
[09:23] <pitti> but at least notification bubbles are relatively rare, especially when you are offline and on battery
[09:23] <vuntz> but, to be fair, I guess that, while still expensive, all the X communications in wnck_screen_force_update() are not too expensive either
[09:23] <pitti> so I would at least fix the wakeups with every X event
[09:24] <vuntz> yeah
[09:40] <tjaalton> a friend of mine upgraded to precise, but has no clock/calendar on the top panel
[09:40] <tjaalton> should "unity --reset" fix that?
[09:41] <TheMuso> tjaalton: Do they have indicator-datetime installed
[09:41] <tjaalton> TheMuso: good point, I'll ask
[09:43] <tjaalton> TheMuso: apparently not..
[09:43] <tjaalton> wonder how's that possible
[09:43] <tjaalton> after apt-get --fix-policy install and all
[09:46] <seb128> ok, who is wanting to test a new lightdm?
[09:46] <seb128> debs in https://launchpad.net/~ubuntu-desktop/+archive/ppa
[09:47] <seb128> i.e ppa:ubuntu-desktop/ppa
[09:47] <seb128> works fine here
[09:56] <tjaalton> TheMuso: so it got removed post-upgrade
[10:02] <mvo> hey didrocks
[10:02] <didrocks> mvo: hey hey! :)
[10:02] <mvo> didrocks: sorry, missed the ping, what channel was it in?
[10:02] <didrocks> mvo: this one ;) one sec
[10:02] <mvo> didrocks: no problem, I can upload
[10:02] <didrocks> 10:10:40      didrocks | mvo: I uploaded gir1.2-unity-5.0. Do you want to update update-manager yourself or do you want me to do it (for real, this time ;))?
[10:02] <mvo> didrocks: found it now in the backtrace
[10:03] <didrocks> backtrace? too used to python-gobject? :p
[10:03] <mvo> haha
[10:05] <didrocks> mvo: so, do you want to deal with that yourself? :)
[10:07] <mvo> didrocks: yes, will do
[10:08] <didrocks> mvo: awesome! thanks :-)
[10:13] <agateau> dobey: hi, when you're online can you point me to ubuntuone-client packaging branch?
[10:16] <bschaefer> seb128, nope
[10:16] <seb128> bschaefer, hey
[10:16] <seb128> so bug #880876
[10:16] <ubot2`> Launchpad bug 880876 in unity "Unity causes ibus to not work correctly (spaces incorrectly placed)" [High,Confirmed] https://launchpad.net/bugs/880876
[10:17] <bschaefer> seb128, I installed that fix today and every working for me
[10:17] <seb128> bschaefer, what fix? the one in precise?
[10:17] <bschaefer> seb128, the one from the link, pretty much what your patch was
[10:18] <seb128> agateau, lp:ubuntu/ubuntuone-client
[10:18] <seb128> bschaefer, but the patch doesn't work?
[10:18] <bschaefer> seb128, well this https://bugs.launchpad.net/ubuntu/+source/unity/+bug/880876
[10:18] <ubot2`> Launchpad bug 880876 in unity "Unity causes ibus to not work correctly (spaces incorrectly placed)" [High,Confirmed]
[10:18] <bschaefer> opps
[10:18] <bschaefer> https://github.com/fujiwarat/ibus
[10:18] <bschaefer> this branch is what you were going off wasn't it?
[10:18] <bschaefer> from git
[10:19] <agateau> seb128: ah thanks!
[10:20] <agateau> dobey: unping, seb128 answered
[10:21] <bschaefer> seb128, the patch was working, or at lease that git fork. It isn't merged with the main one though
[10:22] <bschaefer> seb128, screen shot of the 2, the first half was that git branch and other is the main ibus https://launchpadlibrarian.net/89804609/ibus_fix.png
[10:24] <mvo> didrocks: uploaded
[10:24] <didrocks> mvo: great! thanks a lot :)
[10:24] <mvo> yw
[10:26] <seb128> bschaefer, ok thanks
[10:30] <bschaefer> seb128, well I am hoping that bug has been resolved. There was also another small bug where the im_context was not getting focus
[10:31] <bschaefer> seb128, well I am hoping that bug has been resolved. There was also another small bug where the im_context was not getting focus
[10:31] <seb128> bschaefer, I need to have another look why people say the precise version doesn't work where the git version does
[10:33] <bschaefer> seb128, hmm, yeah because your patch looked exactly like the git version.
[10:33] <cyphermox> bschaefer: the patch *is* merged, no?
[10:34] <cyphermox> isn't it that context async stuff?
[10:34] <seb128> bschaefer, cyphermox said some variable need to be set or not set for it to work correctly
[10:34] <cyphermox> Use ibus_input_context_process_key_event_async in ibus-x11
[10:34] <bschaefer> seb128, cyphermox  that was changed in that patch wasn't it?
[10:35] <cyphermox> seb128: could they already have dropped the env in the new inuty?
[10:35] <seb128> cyphermox, no idea
[10:35] <bschaefer> cyphermox, are you talking about IBUS_ENABLE_SYNC_MODE env var?
[10:35] <cyphermox> bschaefer: afair the patch was that "Use ibus_input_context_process_key_event_async in ibus-x11" commit, 28abee something something
[10:35] <cyphermox> bschaefer: yeah
[10:36] <bschaefer> cyphermox, that is still used because with out it the normal XIM cant handle the ibus like say the shell can
[10:37] <bschaefer> cyphermox, it is in IMTextEntry, though it should get unset after the search bar is created, so it doesn't effect other programs
[10:37] <cyphermox> yeah, that's the problem -- the shell isn't dealing with ibus the same way as the other apps :)
[10:37] <cyphermox> ok
[10:37]  * cyphermox reloads his session back to korean
[10:38] <bschaefer> cyphermox, seb128 yeaah njpatel and I had a big problem with this a while ago when we first got the ibus working
[10:38] <bschaefer> cyphermox, seb128 that env var was the only way to make the ibus handle normal text
[10:39] <bschaefer> otherwise the ibus would only handle CJK chars and leave the normal text alone, but that would make the dash not handle normal text...
[10:40] <cyphermox> bschaefer: what seems weird to me is that variable shouldn't have been working without the patch seb128 added, if I read the ibus code right (which I might not, obviously)
[10:41] <cyphermox> why is my ibus suddenly not starting?
[10:41] <bschaefer> cyphermox, seb128 well with the patch seb128 added it should have fixed the bug...
[10:41] <bschaefer> is the ibus-daemon running?
[10:42] <cyphermox> yeah, everything is running but the indicator doesn't show for some reason. no big deal for now
[10:42] <bschaefer> cyphermox, yeah, it seems to be something in ibus-table that gets it going again for me (ibus seems to just want to not work!!!)
[10:42] <cyphermox> bschaefer: I was testing this yesterday -- it kind of works depending on the applications and the value of IBUS_ENABLE_SYNC_MODE
[10:43] <bschaefer> cyphermox, yes, when the env var is set to 0 or its NULL everything works correctly
[10:43] <cyphermox> 몸누랑ㄴ러
[10:43] <cyphermox> alright, got it :)
[10:43] <cyphermox> yup
[10:44] <bschaefer> cyphermox, sweet, and yeah it is a weird bug but at the same time ibus should still work correctly with that env set
[10:45] <cyphermox> I guess
[10:46] <cyphermox> it almost seems to me like this might be interaction between sync mode and RTL, since that's what I can think of that would trigger spaces to show before a character... but only for space?
[10:46] <bschaefer> and return
[10:46] <mterry> https://launchpad.net/~ubuntu-toolchain-r/+archive/glibc/+packages
[10:46] <mterry> pitti, ^
[10:46] <cyphermox> oh, return too?
[10:46] <bschaefer> yup
[10:46] <bschaefer> it is the preedit that seems to mess up. So what is in the preedit and you hit space or return it will get commited after the space or return
[10:48] <bschaefer> because preedit text is still not actually text yet; so it doens't hit the commit yet.
[10:48] <cyphermox> aye
[10:49] <bschaefer> sorry, slightly tired nearing 3 am here haha. That is why it looks like it's an upstream problem
[10:49] <bschaefer> and that git branch fixed the problem for me, and it looked like seb128 patch but I havn't compared them both.
[10:49] <bschaefer> ill do that tomorrow!
[10:50] <cyphermox> alright
[10:50] <seb128> bschaefer, let us updated
[10:52] <bschaefer> cyphermox, seb128 cool. Sorry about being so late to helping! Good luck!
[10:52] <cyphermox> good night
[10:52] <seb128> bschaefer, thanks for helping, 'night
[10:52] <bschaefer> thanks, have a good day
[11:02] <mandel> Is anyone experiencing the following with libre office in x64 on P: http://paste.ubuntu.com/802809/
[11:03] <pitti> mandel: bug 915271, fix underway
[11:03] <ubot2`> Launchpad bug 915271 in libreoffice "package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty" [Critical,Triaged] https://launchpad.net/bugs/915271
[11:04] <mandel> pitti, superb, thx!
[11:04] <pitti> well, not superb..
[11:04] <pitti> but at least "known"
[11:05] <mandel> pitti, well, I'm a positive lad, being know is way better than a new bug :)
[11:28] <Riddell> precise testers needed for Qt! https://launchpad.net/~kubuntu-ppa/+archive/experimental/+packages
[11:32] <BigWhale> mandel, that depends on the bug. ;)
[12:23] <eee_man> Good Afternoon
[12:24] <eee_man> does anyone knows how to setup / pan a Desktop at current ubuntu ?
[14:46] <dobey> chrisccoulson: is there a way to migrate data from one firefox profile to another (private data and all, but not just copying files over)?
[14:47] <xclaesse> hey, today had to debug my grandpa's laptop, updates were not working anymore (lucid LTS). the problem is that he did every updates since the lucid release, resulting in 4G of useless kernels filling the /
[14:48] <xclaesse> linux-image-* and linux-headers-*
[14:48] <xclaesse> those should really be cleaned automatically IMO...
[14:51] <nerochiaro> xclaesse: isn't "apt-get autoremove" enough to remove them ?
[14:53] <xclaesse> nerochiaro, do you seriously think ma grandpa knows that? but even then, not it's not removing them ;)
[14:54] <xclaesse> I think more recently version of ubuntu does remove linux-headers though
[14:54] <xclaesse> but not linux-images
[14:54] <dobey> nerochiaro: no
[14:56] <nerochiaro> ok, my mistake then. but yeah, ideally it should be automatic, i agree
[14:56] <dobey> well, it should only leave the currently running kernel installed (and the newly installed one)
[14:57] <dobey> since having the old one around is useful in case the new one breaks something
[14:57] <dobey> but you don't need more than the currently running one
[14:57] <xclaesse> yep exactly
[15:10] <pitti> Sweetshark: ssh scheat.canonical.com
[15:52] <ricotz> Sweetshark, hi :)
[15:52] <ricotz> Sweetshark, is the gtk3 rendering working already?
[15:52] <ricotz> (for libreoffice)
[15:53] <Sweetshark> working basically but not that largely tested
[15:54] <Sweetshark> ricotz: feel free to give it a ride ;)
[15:55] <ricotz> Sweetshark, i guess installing the -gtk3 package and removing the -gtk would be enough to turn it on?
[16:41] <seb128> pitti, help
[16:41] <pitti> seb128: ?
[16:41] <pitti> seb128: I'm in the ballroom
[16:41] <seb128> pitti, how do I make sure the debs are published hard enough that I can upload my rebuilds?
[16:41] <seb128> pitti, I'm in the desktop room ;-)
[16:41] <seb128> pitti, I don't want to make a fool myself yet another time :p
[16:42] <pitti> seb128: safest is to wait until archive.u.c. Packages.gz has them
[16:42] <pitti> seb128: but it's usually enough if cocoplum shows the version
[16:42] <seb128> pitti, thanks
[16:42] <pitti> seb128: rmadison should be the best compromise
[16:42] <pitti> seb128: i. .e rmadison -r precise pkgbinarymangler
[16:42] <seb128> if I'm lucky the run finishing at 6pm will be ready
[16:42] <pitti> it finished 14 mins ago
[16:42] <seb128> the debs finished to build before 17:30
[16:43] <pitti> and it's being published
[16:43] <pitti> -s, not -r, sorry
[16:43] <pitti> rmadison is faster than archive.u.c. and "slow enough" for buildds
[16:43] <seb128> pitti, thanks
[16:43] <pitti> de rien
[16:43] <pitti> seb128: you will handle the rebuilds?
[16:44] <seb128> pitti, yes, I'm stacking them already
[16:44] <pitti> seb128: I re-opened the tasks BTW, so that people stop wondering
[16:44] <pitti> (and did a followup)
[16:44] <pitti> seb128: nice, thanks
[16:44] <seb128> I just don't want to upload too early and have to do another round :p
[16:44] <seb128> yw
[16:44] <seb128> sorry for the screwing
[16:44] <pitti> seb128: let me know when you upload control-center
[16:44] <pitti> so I can bump it
[16:44] <pitti> RAOF and I are currently sending a gazillion KDE packages buildd-wards
[16:44] <seb128> (hate perl)
[16:44] <seb128> pitti, ok
[17:01] <jbicha> seb128: did you want my recently-merged-from-Debian control-center?
[17:01] <seb128> jbicha, since it was not uploaded I figured you were not done with it
[17:02] <jbicha> seb128: it works, one change I didn't add to the changelog yet is that I renamed the Appearance panel to User Interface to match that design spec
[17:04] <jbicha> I like having the appearance panel being first in the list though so I don't know if that design idea will be final...
[17:05] <seb128> jbicha, ok
[17:05] <pitti> pkgbinarymangler |        113 |       precise | source, all
[17:05] <pitti> seb128: looks fine
[17:05] <seb128> pitti, yeah, I just uploaded
[17:06] <seb128> pitti, https://launchpad.net/ubuntu/precise/+source/gnome-settings-daemon/3.2.2-0ubuntu10
[17:06] <seb128> https://launchpad.net/ubuntu/precise/+source/gnome-control-center/1:3.2.2-0ubuntu9
[17:06] <seb128> pitti, if you want to bump scores
[17:07] <pitti> seb128: done
[17:07] <seb128> pitti, danke
[18:59] <dobey> desrt: how do i run an app from the source tree, which uses gsettings, but which doesn't yet have the schemas installed in the system (because i want to run it from the source tree, not install it)?
[19:00] <BigWhale> dobey, I would ask the same for app-indicator icons... :>
[19:01] <dobey> BigWhale: plug-ins for other applications are a different problem. and that's basically what app indicators are :)
[19:02] <BigWhale> I figured it is a different problem, but the outcome is the same! :>
[19:02] <BigWhale> you have to install it if you want to run from source tree :/
[19:02] <dobey> can't you just hand a pixbuf over the indicator API to use for the icon?
[19:02] <BigWhale> no
[19:02] <BigWhale> :/
[19:03] <dobey> app indicators seem wrong anyway
[19:03] <dobey> i would like to make the top panel smaller though
[19:03] <BigWhale> Bug #657857
[19:03] <ubot2`> Launchpad bug 657857 in kazam "Appindicator cannot use a local icon file" [Low,Confirmed] https://launchpad.net/bugs/657857
[19:03] <dobey> it looks huge
[19:06] <BigWhale> huge?
[19:07] <BigWhale> it's like 28 pixels?
[19:07] <BigWhale> probably less
[19:07] <dobey> yes, and that is huge
[19:08] <dobey> 24 px
[19:08] <dobey> hrmm
[19:08] <dobey> the icons look huge though
[19:08] <BigWhale> icons are 22px
[19:08] <BigWhale> stop using 50" TV as your monitor :>
[19:08] <dobey> i'm not, it's 23"
[19:09] <dobey> i thought i made the launcher panel be smaller too
[19:09] <dobey> but apparently it's 48px wide
[19:09] <BigWhale> I have launcher set on 32
[19:09] <BigWhale> 48 is way too much
[19:10] <BigWhale> Hmm, would many people be pissed off if I make Kazam Ubuntu only? I have to port support for gnome-indicators :/
[19:11] <dobey> probably the wrong place to ask
[19:11] <dobey> :)
[19:11] <BigWhale> :>
[19:13] <dobey> hrmm, i have the icon size set to 32 too
[19:13] <dobey> but the whole launcher is 48px
[19:13] <dobey> meh
[19:16] <BigWhale> that's strange
[19:38] <dobey> BigWhale: not really. the icons are 32px. there's just a lot junk around the icons too (spacing, borders, arrows)
[19:39] <dobey> but man do these gnome icons look so much better than the humanity ones
[19:41] <BigWhale> hm true it is 50 pixels
[19:41] <BigWhale> horrific
[19:42] <dobey> well, at least it's not 64 px
[19:42] <dobey> i just need an ibm t221
[19:42] <dobey> problem solved.
[19:43] <dobey> sigh; and compiz just crashed :(
[20:39] <dobey> meh, i need ken
[20:41] <OwaisL> Guys, is this a feature or a bug? https://twitter.com/#!/Chris_Wilkinson/status/157903375470563328/photo/1
[20:42] <OwaisL> bug report: https://bugs.launchpad.net/unity/+bug/912682
[20:42] <ubot2`> Launchpad bug 912682 in compiz "Compiz add transparency to titlebar along with the panel" [Undecided,Incomplete]
[20:48] <dobey> how gwibber-accounts manages to even work in its current state is beyond me :-/
[20:52] <dobey> OwaisL: i have no idea
[21:14] <desrt> dobey: GSETTINGS_SCHEMA_DIR
[21:14] <dobey> ah, hrmm
[22:07] <TheMuso> D/c
[22:27] <maxb> In gnome-terminal, when it says "Use colours from system theme", where can I look up what the actual colour codes are?
[22:28] <maxb> Because I want to configure terminator to use the same colours, but if I "Use colours from system theme" in terminator, it picks entirely different colours