=== duflu_ is now known as duflu
[03:44] <coder-guy22296> hey guys
[03:45] <coder-guy22296> im new and i want to get involved in the Development process
[03:50] <coder-guy22296> hey ther
[03:50] <coder-guy22296> im new and i want to get involved in the Development process
[03:50] <sarnold> hello coder-guy22296 -- you've arrived a bit late in the day for most users, not yet early engh for europe to be awake, but after .us has quit for the night :)
[03:51] <coder-guy22296> are you a developer?
[03:52] <sarnold> coder-guy22296: for me, it's complicated. I'm not an official ubuntu developer, but I'm on the security team, so I've got upload privileges to all the released distributions -- but not the development distribution. haha. :)
[03:53] <coder-guy22296> thats cool
[03:53] <sarnold> coder-guy22296: usually people will pick a few projects that they want to help improve, and provide patches or test patches or so forth, and eventually start getting some developer privileges
[03:53] <coder-guy22296> I noticed a bug in Ubuntu that has been around for a couple releases
[03:55] <coder-guy22296> and I would like to help out
[03:55] <sarnold> coder-guy22296: well, first start, is the bug filed in launchpad yet?
[03:56] <coder-guy22296> no, not yet
[03:56] <sarnold> you might be surprised, I got ready to file a bug earlier tonight and foud someone else had beat me to it :)
[03:56] <coder-guy22296> I want to get to a position where i can fix bugs
[03:57] <sarnold> coder-guy22296: anyway, the first step is filing a bug -- you can file a bug with 'ubuntu-bug', and if you know the name of the package or program that is buggy, 'ubuntu-bug` takes pid or program or package arguments...
[03:57] <sarnold> cool :) more help squashing bugs is always welcome
[03:58] <coder-guy22296> first of all, what language is Ubuntu coded in?
[03:59] <sarnold> coder-guy22296: dozens of languages; C, C++, Python 2, Python 3, shell, awk, sed, perl, go, erlang, java, vala, qml, javascript, ...
[04:00] <coder-guy22296> Im not really sure what the package or program would be, its a small bug where I noticed a 1-2 pixel shift to the right in the desktop's display area
[04:01] <sarnold> coder-guy22296: so, is it something like a strip of black pixels running along the edge of the screen?
[04:01] <sarnold> coder-guy22296: or does part of the contents run off the edge of the screen?
[04:03] <coder-guy22296> I have to multiple displays, so yes it is a 2pixel strip of my left desktop on the left side of my right monitor
[04:03] <coder-guy22296> *2
[04:04] <coder-guy22296> and it is possible that a 2pixel strip on the right is also missing
[04:04] <sarnold> coder-guy22296: ha! never seen that one before. :)
[04:04] <sarnold> coder-guy22296: okay, I'd say file that against 'xorg' -- "ubuntu-bug xorg" -- and then fill out the fields once your web browser prompts you  :)
[04:05] <coder-guy22296> it has not been fixed in the last 2 releases
[04:14] <sarnold> coder-guy22296: okay, time for me to call it a night; have fun!
[04:14] <coder-guy22296> night
[05:38] <pitti> Good morning
[09:02] <Laney> morning
[09:02] <Laney> happy friday!
[09:03] <seb128> hey Laney
[09:03] <seb128> happy friday!
[09:10] <Laney> hey seb128
[09:10] <Laney> how are you?
[09:11] <Sweetshark> Moin!
[09:12] <seb128> Laney, I'm good thanks, a bit tired though ... looking for something easy to do today ;-) (it might end up being some debian merges/updates/bug triage)
[09:13] <seb128> Laney, you?
[09:13] <seb128> Sweetshark, hey
[09:13] <pitti> bonjour seb128
[09:13] <seb128> pitti, salut, ça va ?
[09:13] <pitti> hey Laney, moin moin Sweetshark
[09:13] <Laney> hey pitti seb128
[09:13] <pitti> seb128: un peu fatigue, mais bien ! (merci dieu c'est vendredi :) )
[09:13] <seb128> pitti, pareil ici ;-)
[09:13] <Laney> I'm good, remembering that my go at "reset API" yesterday didn't work
[09:13] <Laney> so now I want to ignore that and look at something else :P
[09:20] <seb128> hehe, joining me on the easy friday ;-)
[09:20] <Laney> I don't understand why online accounts wants to open its own window
[09:20] <Laney> my approach was "look for a 'reset' method in each of the pagecomponents"
[09:21] <Laney> but that breaks it
[09:21]  * Laney goes to ask mardy
[09:34] <seb128> Laney, did you use the vcs for the e-d-s update and forgot to push or did you not use it? (in the former case can you push? if that's the later one, I can copy the changes back there no worry)
[09:34] <Laney> oh I think I did, sec
[09:36] <Laney> seb128: yep, pushed
[09:36] <seb128> Laney, thanks
[10:07] <seb128> didrocks, cyphermox, larsu: good, indicator tests/daily build are back to green with the new libffi
[10:09] <didrocks> seb128: yeah, so everything was rebuilt?
[10:09] <didrocks> seb128: I'll ask cyphermox to release it as soon as he's around :)
[10:09] <didrocks> after some phone testing :p
[10:10] <seb128> didrocks, seems like rebuilds are not needed after all (at least the binaries stop hitting smashed stack issues)
[10:10] <larsu> seb128: \o/
[10:10] <seb128> oh, a larsu!
[10:11] <seb128> larsu, hey, how are you? happy friday!
[10:11] <didrocks> seb128: sweetness!
[10:11] <larsu> seb128: oh, I forgot the happy-Friday wishes this morning... Happy Friday!
[10:11] <larsu> seb128: I'm good thanks. How are you?
[10:11] <Laney> oh, no datetime indicator this morning
[10:11] <Laney> don't we have that fix in trusty?
[10:11] <Laney> hmm, we do
[10:11] <seb128> Laney, no we don't, we need an indicator landing, that was the heated discussion a week ago
[10:11] <Laney> https://launchpad.net/ubuntu/+source/indicator-datetime/13.10.0+13.10.20131023.2-0ubuntu1
[10:11] <Laney> = trusty
[10:11] <seb128> oh, datetime
[10:12] <seb128> the session one is missing for sure
[10:12] <seb128> Laney, is indicator-datetime-service running?
[10:12] <Laney> nope
[10:12] <Laney> i wonder...
[10:12] <seb128> ok, so different issue
[10:13] <seb128> is it installed?
[10:13] <Laney> yeah
[10:13] <seb128> does it work if you run it manually?
[10:13] <larsu> did the upstart stuff land?
[10:13] <seb128> no
[10:13] <Laney> just did, it worked
[10:13] <seb128> larsu, landing was blocked due to the ppc smashed stack issue
[10:14] <seb128> it might happen today if the moons are correctly aligned, who knows ;-)
[10:14] <larsu> Laney: do you have the same issue if you kill indicator-datetime-service and restart unity-panel-service
[10:14] <larsu> seb128: I'll check the moons
[10:14] <seb128> ;-)
[10:14] <Laney> I see that it timed out in dbus.log
[10:15] <Laney> comes up properly with u-p-s
[10:15] <seb128> ok, so we don't know
[10:16] <Laney> oh well
[10:16] <seb128> would be useful to see if the service is running and get a bt, if you get the issue again
[10:16] <Laney> I saw that it wasn't running
[10:16] <seb128> because it timeouted
[10:16] <Laney> because dbus activation timed out
[10:16] <Laney> yeah
[10:16] <seb128> which could be the lock issue
[10:16] <seb128> but without a bt we can't say...
[10:16]  * larsu tries to dbus-activate it manually
[10:16] <seb128> trick is to think about getting the bt before it timeouts ;-)
[10:16] <Laney> a bt of what?
[10:16] <Laney> haha
[10:16] <seb128> indicator-datetime-service
[10:17] <seb128> well, if you ever get the issue again
[10:17] <seb128> I don't here, I just get it with indicator-session, but that one is missing the lock fix in trusty
[10:17] <larsu> hm, works fine here
[10:18]  * didrocks doesn't see any moon, just snow clouds
[10:18] <didrocks> omg, the cloud is snowy, we are all lost!
[10:18]  * didrocks runs in circle
[10:19] <Laney> we were supposed to get snow this week
[10:19] <Laney> never happened
[10:19] <didrocks> we stole it from you!
[10:19] <Laney> >:|
[10:19] <Laney> post it back right this instant
[10:19] <didrocks> hehe
[10:19] <didrocks> Laney: so, after mostly a week, still loving your new chair?
[10:20] <Laney> didrocks: yeah, it's still nice
[10:20] <didrocks> great ;)
[10:21] <Laney> the only bad thing is that it's not so good to put your feet up on
[10:21] <Laney> the side of the armrests is a bit sharp
[10:21] <didrocks> yeah, but that's a bad position for your back!
[10:21] <Laney> it sure is
[10:45] <seb128> chrisccoulson, hey, how are you?
[10:46] <seb128> chrisccoulson, I guess you noticed that your recent firefox upload to trusty failed to build on arm/ppc?
[10:48] <chrisccoulson> seb128, http://hg.mozilla.org/mozilla-central/rev/0787526e0ed6
[10:48] <chrisccoulson> i'll sort that out in a bit
[10:48] <seb128> chrisccoulson, thanks
[11:04] <seb128> Laney, do you know what's the deal with dbus-sharp changing it's abi version, do we simply need a rebuild of tomboy/banshee or do they need change? is anyone working on doing those changes in Debian?
[11:04] <Laney> seb128: they need a bit of porting, and yes people are working on it
[11:04] <Laney> I'm not tracking it though
[11:04] <seb128> ok
[11:04] <Laney> check with directhex in -devel
[11:05] <Laney> he should know how far along that is
[11:05] <seb128> I just saw it being stucked in trusty-proposed
[11:05] <Laney> yeah
[11:06] <seb128> thanks
[11:17] <chrisccoulson> lol, I didn't expect anyone would add a serious comment to bug 1253763
[11:17] <ubot2> Launchpad bug 1253763 in firefox (Ubuntu) "xxx" [Undecided,Incomplete] https://launchpad.net/bugs/1253763
[11:19] <seb128> chrisccoulson, lol, I see that you still get top quality bug reports ;-)
[11:20] <chrisccoulson> seb128, yep :)
[11:20] <chrisccoulson> did you see my comment? ;)
[11:20] <didrocks> seb128: you know what? chrisccoulson even participated at UDS!
[11:20] <seb128> yes ;-)
[11:20] <seb128> did he?
[11:20] <chrisccoulson> i attended 1 session!
[11:20] <didrocks> seb128: on the last client2 session
[11:20] <seb128> I didn't see an oxyde session this time
[11:20] <didrocks> chrisccoulson: the best for the end, right?
[11:20] <didrocks> :)
[11:20] <seb128> or the webapp stuff
[11:20] <didrocks> seb128: webapps on desktop
[11:20] <seb128> oh*
[11:21] <seb128> that makes sense
[11:21] <seb128> chrisccoulson, btw, did you have a look to libebook/tb?
[11:21] <chrisccoulson> seb128, yeah, we decided we didn't need any sessions for oxide this time around. we had one last time, and all of the major items already have assignees. we don't want more work :)
[11:21] <chrisccoulson> seb128, not yet
[11:21] <seb128> k
[11:22] <didrocks> seb128: see, they are slacking
[11:22] <didrocks> I'm sure all those security guys, they check the html5 youtube security watching cat videos all the day along
[11:22] <didrocks> :)
[11:22] <seb128> chrisccoulson hates cats for some reason
[11:22] <seb128> I don't get it
[11:23] <chrisccoulson> they crap all over the garden!
[11:23] <seb128> well, they dig a small hole and hide their stuff
[11:24] <seb128> clever animals!
[11:24] <chrisccoulson> i wish that were true. they try to do it, but it doesn't work so well when they do it in the middle of the lawn ;)
[11:45] <Sweetshark> oh great
[11:46] <Sweetshark> Open LibreOffice 4.2 beta1 on trusty => works. And there was much rejoicing! Click "File->Close" => Crash.
[11:46]  * Sweetshark bets it would work like a charm on saucy though :/
[11:47] <Laney> crashing seems like an efficient way to end the program to me :P
[11:50] <Sweetshark> Laney: File->Close isnt File->Quit. We didnt gnome3-simplified ("it would confuse users") that difference away yet.
[11:57] <Laney> oh man, I've been simplified
[11:59]  * xnox feels basic
[12:00]  * Sweetshark feels relieved.
[12:01] <Sweetshark> seems (hopefully) to be only a dependency mess up.
=== MacSlow is now known as MacSlow|lunch
[13:26] <dwarakesh> I am unable to adjust brightness on a newly installed ubuntu system (laptop), can anyone help?
=== MacSlow|lunch is now known as MacSlow
[13:48] <pitti> desrt: aaaargh!
[13:50] <pitti> desrt: I was wondering what on earth would talk to the session bus (which fails) in shim; look again at https://github.com/desrt/systemd-shim/commit/136ed11430 ...
=== greyback is now known as greyback|lunch
[13:54] <pitti> desrt: trivial, but for the sake of peer review: http://paste.ubuntu.com/6458615/
[14:12] <seb128> pitti, hey, I just crossed https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1080745 while looking at gdu bugs ... do you want me to forward that to the BTS or is launchpad enough?
[14:12] <ubot2> Launchpad bug 1080745 in udisks2 (Ubuntu) "shoulds Recommends gdisk since it uses sgdisk commands" [Low,Confirmed]
[14:19] <pitti> seb128: LP is enough
[14:19] <pitti> seb128: can you please subscribe or assign me?
[14:19] <seb128> pitti, thanks
[14:20] <seb128> pitti, btw do you have an opinion on updating gdu to 3.10? it seems to not have newer depends and there is like 15 code commits between 3.8 and 3.10, mostly bug fixes and small things
[14:20] <seb128> pitti, done
[14:20] <pitti> seb128: yep, sounds good to me
[14:20] <seb128> ok, doing the update then
[14:20] <pitti> seb128: I'll do that in Debian, too
[14:20] <pitti> or that
[14:20] <pitti> thanks
[14:20] <seb128> pitti, thanks ;-)
[14:21] <pitti> ah, we have ubuntu mods, argh
[14:21] <seb128> pitti, Debian already has 3.10, I'm just merging
[14:21] <pitti> seb128: anyway, I just finished wrestling with suspend bugs; now watchign didrocks live (CI airline), and then I'll call it a week
[14:21] <pitti> seb128: ah, splendid
[14:22] <pitti> seb128: will do gvfs early next week (sorry, didn't get to it yet)
[14:22] <seb128> pitti, no worry about gvfs ... btw we might want to directly go with 1.19, seems like gvfs finally has an active maintainer and is getting some overdue bugs fixes
[14:22] <seb128> pitti, enjoy the CI video and w.e ;-)
[14:23] <pitti> yeah, I'll check
[14:23] <pitti> I also want to update pygobject, that got some nice fixes too
=== greyback|lunch is now known as greyback
[15:10]  * pitti waves to Captain didrocks, merci :)
[15:10] <pitti> didrocks: can we collect bonus miles?
[15:10] <seb128> chrisccoulson, is that something you know about https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1231273 ?
[15:10] <ubot2> Launchpad bug 1231273 in firefox (Ubuntu) "Firefox does not show google geo location map" [Undecided,Confirmed]
[15:10] <seb128> chrisccoulson, that bug states we need a custom key
[15:10] <chrisccoulson> seb128, yeah, i'm aware of that
[15:10] <pitti> didrocks: i. e. people who land changes with a high percentage of success get processed faster, or get a personal handshake from you, or so? :-)
[15:10] <seb128> chrisccoulson, ok, I was mentioning it in case it's useful information ;-)
[15:12] <chrisccoulson> heh, thanks ;)
[15:12] <didrocks> pitti: heh, yeah, you will be able to get upgrades as well :)
[15:12] <didrocks> and we'll introduce CI coins
[15:13]  * didrocks buys a lot before the market is going crazy
[15:13] <pitti> didrocks: oh, we'll get bitcoins for uploads? :-)
[15:13] <didrocks> pitti: CIcoins, easier for us to produce "money"
[15:13] <didrocks> ;)
[15:13] <pitti> bah
[15:13] <didrocks> come on, who would refuse a first-class upgrade to fly to ubuntu? :)
[15:14]  * seb128 reads the story about that guy who bough for 50€ of bitcoins back then to end up with some 300 000€ today
[15:14] <seb128> I wonder if CIcoins are going to be the same
[15:14] <seb128> didrocks, can I get some of those reserved, just in case? ;-)
[15:14] <pitti> seb128: I think it was > 1M, as he bought an appartment for that
[15:14] <pitti> (in NY)
[15:14] <chrisccoulson> seb128, no, don't do that. we need you here!
[15:15] <didrocks> seb128: you surely do have some provisionned for you :)
[15:15] <seb128> pitti, could be, I just know it was "almost nothing" to "a lot of money"
[15:15] <seb128> chrisccoulson, lol
[15:15] <pitti> seb128: yeah, indeed; he bought them at the time when ~ 1.200 B$ == 1US$
[15:15] <pitti> and now 1B$ is roughly 700 US$
[15:15] <chrisccoulson> we have to try and keep seb128 away from all "get rich quick" schemes
[15:16] <didrocks> heh
[15:16] <seb128> chrisccoulson, what's wrong with me getting rich? I mean throw up nice conf^parties then and invite you all :p
[15:17] <chrisccoulson> hah :)
[15:22] <mdeslaur> seb128: don't move to an island :)
=== alan_g is now known as alan_g|tea
[15:37] <desrt> pitti: oh christ
[15:37] <desrt> pitti: please proceed
[15:38] <desrt> pitti: i'm so used to working on the session bus....
[15:38] <pitti> desrt: I have some feeling that I'm being haunted by this stuff
[15:38] <pitti> desrt: pushed
[15:38] <pitti> desrt: but some bug reporter just said "njargh, still broken", waiting for a debug log from him
[15:38] <desrt> pitti: we're in an inherently ugly business
[15:39] <pitti> it's like every time I look at such a bug report I hear a little Lennart in my head, shouting "you will be in pain!!!"
[15:40] <desrt> :)
[15:43] <seb128> cyphermox, hey, could you commit your g-c-c fix/upload to the packaging vcs? (lp:~ubuntu-desktop/gnome-control-center/ubuntu)
[15:45] <pitti> desrt: followed up to the bug again
[15:45] <pitti> and with that, I wish everyone a nice weekend, otherwise this week will never stop
[15:46]  * Laney hugs pitti
[15:46] <Laney> have a good weekend
[15:46] <seb128> pitti, have a nice w.e as well, say hello to Annett from me ;-)
[15:46] <desrt> pitti: take care :)
[15:46] <pitti> seb128: I will!
[15:46] <pitti> desrt: no parcel for you today either? :-(
[15:46] <desrt> Laney: did you get my poke yesterday?
[15:47] <Laney> kind of
[15:47] <desrt> pitti: parcel?
[15:47] <Laney> I can't remember thinking that I needed to answer though
[15:47] <Laney> re-poke me
[15:47] <desrt> Laney: poke!
[15:47] <Laney> ow :(
[15:47] <desrt> Laney: hey.  when will we have new glib/dconf in t-?
[15:47] <pitti> didrocks, cyphermox: https://code.launchpad.net/~mathieu-tl/autopilot-gtk/source-format/+merge/196297 - 1.0 !?!
=== alan_g|tea is now known as alan_g
[15:48] <Laney> desrt: oh, maybe next week
[15:48] <desrt> Laney: nice
[15:48] <Laney> kind of scared about glib
[15:48] <seb128> pitti, you don't want to start that discussion tonight ;-) basically everything under CI is 1.0
[15:48] <desrt> Laney: what's wrong with glib?
[15:49] <pitti> desrt: sorry, nick fail; I meant didrocks
[15:49] <Laney> seems big
[15:49] <pitti> seb128: I don't? ok
[15:49] <desrt> pitti: damn.  i thought i was getting a parcel :)
[15:49] <didrocks> pitti: yeah, in a hangout, there are multiple reasons for that, I can expose it for you after the meeting
[15:49] <desrt> Laney: changeset is big, you mean?
[15:49] <Laney> ya
[15:49] <seb128> pitti, Lyon has been under snow so maybe traffic to get there has some delay
[15:49] <desrt> ya... that's true
[15:49] <pitti> didrocks: no worries; I thought it was due to the recent dpkg changes
[15:49] <desrt> but at least it'll work on ppc?
[15:49] <Laney> well, better to get it in early in that case
[15:49] <Laney> haha
[15:50] <pitti> seb128: no, didrocks doesn't answer his doorbell :-P
[15:50] <Laney> it always passed on ubuntu ppc for some reason
[15:50] <didrocks> pitti: it's a consequence, but it's also the only way to support upstream
[15:50] <seb128> pitti, haha
[15:50] <desrt> the phone guys are poking me about dconf work they need ... ideally by end-of-year
[15:50] <didrocks> tsss
[15:50] <desrt> and i won't be able to land it without a new glib
[15:50]  * didrocks continues his meeting :)
[15:50] <Laney> okay, well do your work based on it
[15:50] <Laney> we'll get it in
[15:50] <desrt> i am :)
[15:50] <desrt> thanks
[15:50] <seb128> pitti, well, it takes some time to get dressed to be able to go open the door... ;-)
[15:50] <pitti> ok, really off now &
[15:50]  * pitti waves
[15:51] <seb128> pitti, have fun!
[15:51] <seb128> ttyl
[15:51] <desrt> pitti: i hope your parcels make it!
[17:05] <Laney> hmm
[17:19] <seb128> Laney, ?
[17:20] <Laney> thinking about this custom plugins thing
[17:22] <Laney> how would you handle library directories?
[17:22] <Laney> files under XDG_DATA_DIRS are easy
[17:27] <seb128> Laney, "library directories"?
[17:27] <Laney> yes, the private libraries
[17:27] <Laney> PLUGIN_PRIVATE_MODULE_DIR currently
[17:29] <seb128> oh, to load plugins from other locations?
[17:29] <seb128> I don't really know :/
[17:29] <seb128> seems like a good question for the qt/sdk guys
[17:30] <seb128> or kenvandine/mardy maybe have an idea about that
[17:30] <Laney> Don't know if it's valid to ask foreach XDG_DATA_DIR/../libdir
[17:30] <seb128> DATA feels wrong
[17:30] <Laney> but that's shonky
[17:31] <Laney> so, dunno what else you could do other than hardcode it at build time
[17:32] <Laney> which isn't very well matched with using XDG_DATA_DIRS
[17:45]  * didrocks waves good evening and good week-end
[17:47] <seb128> Laney, we should maybe check with e.g the online accounts are doing
[17:47] <seb128> but that feels like something for next week
[17:47]  * seb128 calls it a week
[17:48] <chrisccoulson> hah, i like french weather reports - http://www.telegraph.co.uk/news/worldnews/europe/france/10465935/French-weathergirl-stuns-viewers-with-nude-report.html
[17:48] <chrisccoulson> seb128 ;)
[17:48] <Laney> yeah
[17:48] <Laney> see you
[17:49] <seb128> chrisccoulson, lol
[17:49] <chrisccoulson> heh :)
[17:52] <seb128> have a good w.e everyone!
=== alan_g is now known as alan_g|EOW
[18:27] <desrt> chrisccoulson: attente was thinking about porting firefox to gmenumodel.  any thoughts on that?
[18:29] <chrisccoulson> desrt, i don't mind, as long as it continues to work with dbusmenu ;)
[18:30] <chrisccoulson> desrt, is attente volunteering to maintain firefox? :)
[18:30] <desrt> you've got SRUs on the brain
[18:30] <desrt> chrisccoulson: we fooled him once with taking up working on the input methods infra.  i doubt we're going to fool him with firefox :)
[18:30] <chrisccoulson> ah, it was worth a try ;)
[18:31] <attente> oh you guys... :P
[18:32] <chrisccoulson> attente, firefox is in need of a loving maintainer ;)
[18:32] <attente> desrt, you're working for canonical now, right :P
[18:33]  * desrt leaves early for the weekend -- goodbye everyone!
[18:33] <chrisccoulson> have a good weekend desrt!
[18:34] <attente> lol...
[18:34]  * desrt (kidding, unfortunately)
[18:35] <attente> chrisccoulson, how are the menus in firefox passed off to dbusmenu right now?
[18:36] <chrisccoulson> attente, http://bazaar.launchpad.net/~mozillateam/firefox/firefox-trunk.head/view/head:/debian/patches/unity-menubar.patch
[18:36] <attente> chrisccoulson, wow. big patch :)
[19:10] <cyphermox> chrisccoulson: yo
[19:11] <cyphermox> you still looking after thunderbird and all? I'd like to rebuild it for e-d-s fun stuff
[19:11] <cyphermox> namely, thunderbird-gnome-support depends on an old e-d-s lib and blocks the transition, AFAICT
[19:12] <Laney> he knows
[19:12] <Laney> but it is tied into fun things via mapi anyway
[19:12] <cyphermox> oh ok
[19:12] <Laney> the eds transition, that is
[19:12] <cyphermox> looks to me like mapi is probably not that bad though?
[19:12] <Laney> depends how much you like libav
[19:13] <cyphermox> craphouse
[19:13] <Laney> it's pretty sad
[19:13]  * Laney relocates to pub to drown sorrows over it
[19:13] <Laney> ttyl!
[19:14] <cyphermox> haha, have fun
[19:14] <cyphermox> all this is blocking indicators...
[19:14] <cyphermox> suddently, drowning sorrows sounds like such a good idea
[19:34] <chrisccoulson> cyphermox, rebuilding thunderbird won't fix it. it needs source changes, even if it's just bumping the library version (but i suspect it needs lots more than that)
[19:35] <cyphermox> needs to be fixed anyway
[19:36] <cyphermox> are you planning to do it or should I allocate some time that I look at it?
[19:36] <cyphermox> perhaps I'll start with figuring out anything re. libav first though
[20:27] <csslayer> attente: ping, aron told me something about fcitx and unity-greeter.. but I've no idea what unity-greeter is
[20:54] <attente> csslayer, hi, unity-greeter is where the user logs into their session
[20:55] <csslayer> attente: so why do you mention this? is there any special requirements for unity-greeter?
[20:56] <attente> csslayer, if we were to hypothetically switch to fcitx, and use fcitx for keyboard layouts too, then we'd need some way to get fcitx running at the login screen
[20:57] <attente> csslayer, alternatively we need a way to query any user's fcitx input methods at the login screen
[20:58] <csslayer> emm.. can you give me a usecase that why people need to change layout on login screen?..
[21:00] <attente> csslayer, for example, if there are more than one user on a machine, and each user is using a different keyboard layout to type their password
[21:01] <attente> maybe one person is using the us layout to type their password, another is using azerty, another is using ru layout
[21:03] <csslayer> if so, is user allowed to choose whatever layout supported by system in the login screen?
[21:04] <attente> csslayer, it should be possible since there can be multiple users with different keyboard layouts
[21:05] <csslayer> I mean, is it must be pre-configured? or it's limited to what user already chose
[21:05] <attente> csslayer, it should only have the layouts that the users have chosen
[21:09] <csslayer> IMHO, running an input method service on login screen is introducing potential security problem. (this is proven by MS(tm)), so I think have some limited information of layout is better.
[21:11] <attente> csslayer, ok. how are the user's list of input methods stored in fcitx?
[21:12] <csslayer> though, I could also try to implement a restricted mode for fcitx, but even in that case, there needs a way to pass the information of layout..
[21:12] <csslayer> currently a file on the disk
[21:13] <csslayer> how does the unity-greeter get the wallpaper information?
[21:13] <attente> csslayer, it's obtained through accountsservice
[21:14] <attente> if we can get fcitx to start using accountsservice for storing the user's input methods list, then the problem would go away
[21:14] <csslayer> ok, then I think we can implement a plugin for fcitx and populate the input method information to accountservice
[21:15] <attente> ah, ok :)
[21:15] <attente> csslayer, one other thing i wanted to ask you about
[21:15] <attente> in fcitx, the input trigger is implemented how?
[21:17] <csslayer> key event passed to fcitx then triggered.
[21:18] <csslayer> not keygrab on X like ibus
[21:19] <attente> sorry, i'm not very familiar with this topic, but what's the difference exactly? i thought doing a passive key grab entailed handling key events as well
[21:20] <attente> i guess specifically how does fcitx get the event without doing the key grab on the root window?
[21:20] <csslayer> fcitx doesn't grab any key, it is the application forward the key event to fcitx
[21:22] <attente> how does the application know it should forward the key event to fcitx?
[21:26] <csslayer> it's application's own logic, like, if you're using gtk/qt, then textbox implementation already handles this.
=== Mapley is now known as rainbowdash`