[15:27] <micahg> xubuntu-docs in lucid-proposed ready for testing :)
[15:54] <charlie-tca> Good morning
[15:54] <ochosi> hi charlie-tca
[15:55] <charlie-tca> Still got the themes issue in Natty. It will not stay in the selected theme.
[15:58] <mr_pouit> if it shows the ugly dark grey thingy with rectangles everywhere, it's not a theme, it's gtk's default uglyness
[15:59] <ochosi> :)
[15:59] <mr_pouit> (meaning, xfsettingsd might have crashed, or you're missing a gtk theme engine)
[15:59] <charlie-tca> Even the live cd?
[16:00] <charlie-tca> this is the light grey theme, both gtk and xfwm
[16:00] <charlie-tca> It also affects the mouse cursor
[16:01] <mr_pouit> could you make a screenshot?
[16:01] <charlie-tca> it is xfsettingsd
[16:01] <mr_pouit> if nothing is themed, xfsettingsd has probably crashed yeah
[16:01] <charlie-tca> I just ran it in terminal, and the greybird theme came up. Mouse cursor changed, too
[16:02] <charlie-tca> that means it is crashing as soon as the desktop starts
[16:02] <charlie-tca> on installs and the live desktop
[16:03] <micahg> charlie-tca: xubuntu-docs in lucid-proposed ready for testing :)
[16:04] <charlie-tca> will get that today, micahg
[16:04] <charlie-tca> thanks
[16:38] <mr_pouit> I tried the daily live in vbox, and the theme is there
[16:38] <mr_pouit> no crash
[16:39] <charlie-tca> hm, I will try today's image then. Yesterday it failed
[16:43] <charlie-tca> It's been failing for several days, screenshot from a few days ago
[16:43] <charlie-tca> mr_pouit : screenshot at http://imagebin.org/133250
[16:45] <mr_pouit> :q
[16:46] <charlie-tca> I will run the images later today. I have to try the lucid docs, too
[17:27] <charlie-tca> ochosi: I think we have to keep thunderbird for email. Claws-mail just is not as easy to use
[17:29] <charlie-tca> and for those who really need to save that little bit of memory, send them to Lubuntu
[17:34] <ochosi> charlie-tca: you're referring to the latest comment on the ml?
[17:34] <charlie-tca> yes. I think we are going to stay with thunderbird
[17:35] <ochosi> right, i don't mind so much
[17:35] <charlie-tca> gmusic?? and browser is up in the air. I don't really care either way
[17:35] <ochosi> mmh
[17:35] <charlie-tca> But I am pretty determined on thunderbird. Claws-mail just is not as easy for users
[17:35] <ochosi> well, the main advantage of gmusicbrowser is the responsive/friendly upstream and that i'm working on it i guess
[17:36] <charlie-tca> Is it in the repositories already?
[17:36] <ochosi> browser, well, i would trust others with the choice, integration is definitely not a problem
[17:36] <ochosi> charlie-tca: check out the shimmer ppa for the latest version
[17:36] <charlie-tca> okay
[17:36] <ochosi> it's natty-ready ;)
[17:36] <charlie-tca> browser we are letting the discussion run until we see which way it leans
[17:36] <ochosi> ppa:shimmerproject/ppa
[17:37] <charlie-tca> I just didn't want you to get too much hope up for claws-mail
[17:37]  * charlie-tca uses claws-mail, too
[17:37] <ochosi> i don't mind so much, i personally use/love it, but i can see why people wouldn't
[17:37] <charlie-tca> I don't really like thunderbird enough to use it
[17:37] <ochosi> :)
[17:37] <charlie-tca> but in configuring it, it wins
[17:38] <ochosi> probably, i've never tried version3
[17:38] <charlie-tca> heh, I wish I could say that
[17:38] <ochosi> btw, one more thing i like about gmusicbrowser: it can use gstreamer as backend, meaning it'll share the same backend with parole meaning less extra dependencies
[17:38] <charlie-tca> setting it up with 10 email addresses and a ton of mailing lists took a couple of days
[17:39] <ochosi> hehe
[17:39] <ochosi> okeydokey, gotta run now
[17:39] <ochosi> looking forward to some gmusicbrowser feedback
[17:39] <ochosi> c u
[17:41] <charlie-tca> thanks
[19:15] <charlie-tca> micahg: found an issue when verifying bug 650806
[19:15] <charlie-tca> all references to www.xubuntu.org fail on the page
[19:16] <micahg> charlie-tca: why did you mark verification-done then?
[19:16] <charlie-tca> they are entered as "file:///usr/share/xubuntu-docs/www.xubuntu.org" which will not work. It needs to be "http:www.xubuntu.org"
[19:16] <charlie-tca> cause the original bug is fixed
[19:17] <charlie-tca> Do I add that to the bug or open a new one?
[19:17] <micahg> charlie-tca: oh, this is a new bug?, please file a new bug, tag regression -proposed and have bookemdano get me a fixed branch as soon as possible
[19:17] <micahg> oops, no space in the tag
[19:17] <charlie-tca> Okay, I can do that
[19:18] <micahg> charlie-tca: is this a regression, or a new bug introduced?
[19:18] <charlie-tca> AFAIK, new bug introduced
[19:18] <micahg> charlie-tca: ok, let me ask pitti then
[19:18] <charlie-tca> but I can not say for sure
[19:18] <micahg> hmm...
[19:20]  * charlie-tca doesn't read the docs each release, and doesn't really know if it was there before or not
[19:24] <micahg> charlie-tca: you could downgrade to the release version and see if it's there :)
[19:24] <charlie-tca> Let me go look
[19:25] <charlie-tca> I have 4 bugs I am verifying, will look in another install
[19:27] <charlie-tca> micahg: new bug. The section has been almost completely re-written
[19:27] <micahg> ok, I think that's a pretty big bug though, right?
[19:28] <charlie-tca> well, Since that is what is being used to test a network connection that failed, ...
[19:28] <charlie-tca> wait a minut
[19:29] <charlie-tca> minor issue. It is a misprint to have it as a link
[19:30] <charlie-tca> It is simply supposed to be a reference to use for ping tests. as in "www.xubuntu.org" instead of a link
[19:30] <micahg> ah, ok
[19:30] <charlie-tca> used as "to ping www.xubuntu.org"
[19:31] <charlie-tca> doesn't really count for anything
[19:31] <micahg> charlie-tca: so we shouldn't fix?
[19:31] <charlie-tca> well, if we have time, sure, let's fix it. But it is really an annoyance
[19:33] <charlie-tca> I don't want to not get these docs in for that, though. They are really nice
[19:34] <micahg> charlie-tca: ok, file the bug and I"ll get pitti to look at it
[19:34] <charlie-tca> Okay.
[19:34] <micahg> charlie-tca: thanks
[19:34] <charlie-tca> thank you
[19:35] <charlie-tca> It helps to have someone working with us
[19:39] <micahg> charlie-tca: glad to help :)
[19:40] <charlie-tca> docs verified for lucid
[19:40] <micahg> cool
[20:28] <charlie-tca> micahg: I guess I should let you know, we are keeping Thunderbird.
[20:29] <charlie-tca> micahg: I gave up answering all those who insist we have to get rid of xulrunner
[20:46] <micahg> charlie-tca: thanks, I thought I was clear on the xulrunner issue :)
[20:46] <cody-somerville> hey folks
[20:46] <charlie-tca> you were, I think.
[20:46] <cody-somerville> how are things?
[20:46] <charlie-tca> Hello, cody-somerville
[20:46] <micahg> hi cody-somerville
[20:46] <charlie-tca> been keeping busy
[20:47] <charlie-tca> We are going to have updated 10.04 docs in .2
[20:47] <cody-somerville> its been a crazy month so far for me. I see a lot of stuff go through my mailbox but haven't had a chance to read yet.
[20:47] <cody-somerville> charlie-tca, sweet :)
[20:47] <charlie-tca> Oh, I don't know if they will be translated, though
[20:49] <charlie-tca> cody-somerville: seems like you are still spread a bit thin... You could really use a double
[20:52] <cody-somerville> charlie-tca, lol. so I'm told.
[21:02] <charlie-tca> cody-somerville: we announced the greybird theme for Natty this week
[21:02] <cody-somerville> is that an entirely new theme or just a big improvement on top of the new one introduced last release?
[21:03] <charlie-tca> grey instead of black/blue of the last release
[21:03] <charlie-tca> same icon set
[21:03] <charlie-tca> and panel arrangement changed
[21:04] <charlie-tca> xfce 4.8 gives us more ability to play with panels
[21:05] <charlie-tca> The theme itself is a change in the bluebird of 10.10
[21:07] <cody-somerville> Cool, ok.


[06:52] <ginggs> enr0n: done for ~ppa11
[11:53] <StevenK> I will note that https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402 has resulted in an extremely frustrating two days
[11:54] <StevenK> "error: out of memory" and then panicing while booting the 22.04 iso is no fun
[12:00] <rbasak> StevenK: "Surely we can do better"> You do realise that developers need to be able to reproduce a problem first, right? Are you familiar with https://www.chiark.greenend.org.uk/~sgtatham/bugs.html ?
[12:39] <enr0n> ginggs: even better, thanks!
[14:19] <jawn-smith> didrocks: now that gsasl has a new major version (2.0) should I re-do the entire MIR template?
[14:26] <didrocks> jawn-smith: no no, just fill in the differences that you are spotting as a new comment
[14:26] <jawn-smith> great, thanks!
[15:30] <rbasak> xnox: why are you the reviewer for https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd ?
[15:30] <rbasak> Shouldn't that be a team, and if so, which one?
[15:30] <rbasak> Asking because I think I need to redirect https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/systemd/+git/systemd/+merge/425082 and https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/systemd/+git/systemd/+merge/425083
[15:48] <enr0n> rbasak: Yeah it probably makes sense to set it to foundations (~canonical-foundations)
[18:48] <enr0n> Can a core-dev please trigger these two PPA autopkgtests? https://autopkgtest.ubuntu.com/request.cgi?release=kinetic&arch=ppc64el&package=systemd&ppa=enr0n/systemd-251&trigger=systemd/251.2-2ubuntu1~ppa12
[18:48] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=kinetic&arch=s390x&package=systemd&ppa=enr0n/systemd-251&trigger=systemd/251.2-2ubuntu1~ppa12
[19:24] <bdmurray> enr0n: doing so
[19:24] <enr0n> bdmurray: thanks!


 Where in the world is Keith I Myers?
 He's out of this world
 @Ivoriesablaze and @ahoneybun - T-Mobile Tuesdays includes a $2.00 movie ticket on Fandango for any movie.
 crap
 Carrie Fisher is dead
 Yes, I saw
 2016 sucked
 It did in many ways
 Good.  Have you ever seen her Twitter?  https://mobile.twitter.com/carrieffisher
 I now have eye cancer
[20:54] <maxolasersquad> I've been following Carrie on the Twitters for a while now. All of her posts are hard to read.
 Apperantly she used to Tweet in Hiroglyphs?
 I have no idea why Leigh died, but I have a feeling her twitter relates somehow.
 it made me die a litte.
 little*
 Couldn't 2016 take Harrison Ford instead?
 Or all the Kardashians and Kanye
 Those would be preferable


[04:44] <valorie> https://twitter.com/kubuntu/status/1087208863147806720
[04:44] <valorie> RT plz
[05:17] <rbalint> ginggs, :-\ updating the hint for now then
[05:17] <ginggs> rbalint: thanks
[11:17] <ahasenack> tjaalton: hi, 'morning
[11:18] <ahasenack> tjaalton: are dogtag-pki dep8 tests broken in disco? Should it be hinted?
[11:24] <tjaalton> ahasenack: dogtag itself is broken.. needs upstream to port it to tls1.3/java11
[11:26] <ahasenack> it's one of the failures holding back openldap in disco-proposed
[11:26] <ahasenack> but only failed on amd64, weird
[11:28] <tjaalton> probably best to remove and blacklist for now
[12:06] <juliank> jdstrand: Still affected by https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338`
[12:06] <juliank> ?
[12:08] <juliank> i have not seen this, nor have i had any other reports, so it might be something unique to your situation
[13:17] <ahasenack> hi, what's the difference between the "platform" and "ubuntu" repositories here?
[13:17] <ahasenack> I've seen seed changes done to both
[13:25] <cjwatson> ahasenack: platform is common to ubuntu and other flavours
[13:26] <xnox> ahasenack, platform is sourced by all flavours; ubuntu is for the ubuntu flavours; kubuntu is for kubuntu flavours; xubuntu is for xubuntu flavours and so on.
[13:26] <ahasenack> hm
[13:26] <ahasenack> thanks
[14:02] <superm1> bdmurray, regarding that SRU it still hasn't released for testing, can you check?
[14:02] <superm1> the 1785165 one
[14:12] <rbasak> cjwatson, xnox: how does that apply to supported-misc-servers in platform?
[14:12] <rbasak> That's AIUI server "flavour" only?
[14:13] <cjwatson> Probably historical reasons
[14:13] <cjwatson> Whether server has had separate seeds has varied over time
[14:13] <cjwatson> And there may have been fiddly germinate issues which I understood ten years ago but have forgotten
[14:15] <cjwatson> I don't know of a fundamental reason why those couldn't be moved, but somebody would have to think moderately hard about the various STRUCTURE files
[14:16] <cjwatson> And whether moving them is actually worth it
[14:16] <rbasak> Thanks
[14:16] <rbasak> The background is that ahasenack is reviewing https://code.launchpad.net/~racb/ubuntu-seeds/+git/platform/+merge/361874 for me
[14:16] <rbasak> Based on that I think the location of the change is acceptable?
[14:19] <cjwatson> I think so
[15:24] <ahasenack> why are there sometimes no build logs when the build failed? Like with https://launchpad.net/ubuntu/+source/ruby2.5/2.5.3-3ubuntu3/+build/16305257
[15:24] <ahasenack> is that still fallout from the incident a while back when files were owned by the incorrect user in the build infrastructure?
[15:30] <xnox> rbasak, cjwatson - if i recall correctly edubuntu server was a server flavour. and like possibly mythbuntu was inheriting some of server things too. but both are now dead.
[15:34] <cjwatson> ahasenack: you've retried so I can't see when that build finished
[15:34] <cjwatson> ahasenack: do you know?
[15:34] <ahasenack> cjwatson: I haven't
[15:34] <cjwatson> somebody has
[15:39] <cjwatson> ahasenack: unexpected out-of-disk on buildd-manager, apparently.  working on it
[15:44] <ahasenack> cjwatson: ah, cool, thanks for checking
[15:44] <ahasenack> cjwatson: is that the cause of the build error, or the cause of the missing build log?
[15:46] <cjwatson> ahasenack: dunno
[15:46] <ahasenack> k
[16:11] <ahasenack> cjwatson: can I retry the failed builds already?
[16:12] <cjwatson> ahasenack: you can do what you like; I have no idea if it'll work yet
[16:12] <ahasenack> ok
[16:33] <doko> ahasenack: https://launchpadlibrarian.net/407262137/buildlog_ubuntu-disco-amd64.ruby2.5_2.5.3-3ubuntu3_BUILDING.txt.gz
[16:33] <doko> this one has a build log
[16:33] <ahasenack> I'll check
[16:34] <ahasenack> it built fine in a ppa
[17:05] <ahasenack> did someone click retry? It's showing green now
[17:05] <ahasenack> just armhf isn't, which I just retried
[17:05]  * ahasenack haunted by armhf build or test failures
[17:38] <cjwatson> ahasenack: given buildd-manager restarting frequently it's possible that it retried itself
[17:38] <ahasenack> ok
[17:39] <cjwatson> I have a theory (it could be bunnies)
[17:41] <ahasenack> or gremlins
[17:42] <cjwatson> (https://www.youtube.com/watch?v=gISEekxuEgk)
[17:47] <ahasenack> yay, armhf built
[17:47] <ahasenack> doko: ruby2.5 built now
[20:22] <juliank> Is there a chance WiFi (iwlwifi) got a lot more laggy recently?
[20:22] <juliank> I'm experiencing ping times to my ap from 5 to 200ms
[20:27] <juliank> hmm early impression is that 4.19 improves things
[20:27] <juliank> hmm no
[20:28] <juliank> WiFi only gets 30 MB/s, wired gets 48/50
[20:28]  * juliank is trying to figure out if the problem is laptop, router, or interference
[21:34] <valorie> cjwatson: <3 for the youtube link
[22:00] <TJ-> juliank: we've been getting a lot of reports of problems with various iwlwifi devices recently, including possibly causing complete system lock-ups. It seems to depend on the age of the chipset and whether firmware updates are still being provided for it
[22:05] <juliank> TJ-: In my case, it's a 8265 / 8275 (rev 78), I don't think there's a lot newer stuff than that?
[22:06] <juliank> TJ-: I should try 4.15 again and see how WiFi performance is there
[22:06] <juliank> I was away over christmas, and when I came back new neighbours moved in; so it's either them causing interference, something else causing interference, a bug in the router, or a kernel bug
[22:06] <TJ-> juliank: I was deep-diving into all this earlier today. I noticed there are some newer firmware files in the linux-firmware repo which might help you.   https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
[22:08] <TJ-> juliank: one was "Add new versions of the firmwares for 8000C, 8265." on Dec  16th
[22:09] <TJ-> juliank: git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[22:10] <juliank> TJ-: hmm, those are in disco, and maybe they are the culprit, I should revert to the previous one
[22:11] <TJ-> juliank: what channels/bandwidth is 'iw' reporting the device using?
[22:11] <juliank> I just hope 4.19 + older firmware is working
[22:12] <juliank>         channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
[22:13] <juliank> hmm no difference
[22:13] <juliank> well, potentially worse
[22:13] <juliank> just down to 5 MB/s
[22:13] <TJ-> juliank: can you poke the AP to move channel?
[22:13] <juliank> TJ-: I've been on channels 36,40,48,64,100, and 116, and all behaved the same
[22:14] <TJ-> juliank: You're ahead of my thought process then :)
[22:14] <juliank> I shall try restarting the router again
[22:14] <juliank> see what that brings
[22:14] <TJ-> Have you tried 2.4GHz too, in case there's a difference?
[22:15] <TJ-> juliank: and as a very unlikely, but possible, scenario... could the u.fl connectors on the wifi device have been dislodged so you've lost use of an antenna? Before you shake your head... I had that happen over the last few months and only figured it out when I got real agitated and opened the device (in this case it was the AP not the PC)!
[22:16] <juliank> TJ-: no precise ping measurements, and throughput is about 25 Mbit/s
[22:16] <juliank> TJ-: I think the AP fell down once
[22:16] <TJ-> juliank: same here!
[22:16] <TJ-> juliank: do all devices see the same throughput, or just the PC?
[22:17] <juliank> Phone is generally slower, so can't really compare I think
[22:17] <juliank> Other laptop is slower too, so
[22:18] <juliank> Waiting for reboot
[22:18] <TJ-> juliank: I found it only started to be noticable when the PC was some way away from the AP, particularly behind obstacles
[22:18] <juliank> I could adb to the TV and see what that does I guess
[22:18] <TJ-> juliank: but sitting under the AP it seemed relatively fine but, as you've observed, felt slow
[22:19] <juliank> TJ-: they are like 4 meters away from each other, but even when I was right next to it, it had issues
[22:20] <juliank> TJ-: phone reports 420 Mbps on fast.com, laptop 220 Mbps
[22:20] <TJ-> juliank: my 'noticable' was stuttering connections and long delays, sometimes losing and regaining the association
[22:21] <juliank> second run 340 Mbit/s
[22:21] <juliank> third run 290
[22:21] <juliank> laptop starts of at 10 Mbit/s, then increases upto 180
[22:23] <TJ-> juliank: there's some trace-cmd debugging you can enable to capture firmware interactions. I've currently got it running in the background to try to capture clues if/when this PC hits the lock-up
[22:24] <juliank> that's with old firmware, with new firmware I get 270 Mbit/s
[22:24] <juliank> now I got 340
[22:25] <TJ-> juliank: in case it helps, "Tracing", "...more switches..." command, at https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
[22:25] <TJ-> juliank: that's logged ~1GB in the last 10 hours for this PC so it is quite busy
[22:27] <juliank> I sometimes think I should get a docking station
[22:27] <juliank> and use cables
[22:28] <juliank> generally what I see is WiFi topping out at 30 MB/s
[22:29] <juliank> which is not really bad
[22:29] <juliank> but it's still a long cry from the 50 I'm paying my ISP for
[22:31] <juliank> I need to test this somewhere outside without interference, and potentially get lenovo to check / replace parts
[22:42] <TJ-> juliank: if it's using NetworkManager, what bitrate does 'nmcli dev wifi list' and 'iwlist bitrate' report maximum link rates ?
[23:42] <cjwatson> valorie: :-) accidentally earwormed myself of course ...
[23:42] <valorie> can't go wrong with Buffy earworms though!


[01:26] <lenky> Kobe_Lee
[01:26] <lenky> Kobe_Lee,
[01:26] <lenky> Kobe_Lee ping
[01:27] <lenky> 我这边的配置向导完成了。不知道indicator做得如何了？需要帮忙不？写的代码在哪里啊？
[01:32] <ypwong> lenky, indicator 是 FJKong 做
[01:33] <lenky> 是啊 所以我在问啊
[01:33] <lenky> 貌似最近两天都不在啊
[01:40] <maclin> FJKong能否介绍一下进展？
[01:46] <FJKong> maclin: 输入法的吗
[01:49] <maclin> 对，indicator的？lenky这边已经完成了qimpanel的功能，如果差不多是不是可以找Aron打包测试了？
[01:50] <maclin> 还有就是两边是不是需要联调一下？
[01:53] <ypwong> maclin, 上次跟 FJKong 沟通是需要实现 全角/半角 和输入法切换
[01:54] <FJKong> lenky: 那个获取输入法列表的你实现了吗
[01:54] <ypwong> 但有部分不会弄，后来是说 FJKong 找上游沟通
[01:55] <FJKong> 联系不上csslayer
[01:55] <FJKong> 我这两天去那个dell大会帮忙来
[01:56] <maclin> 昨天晚上看到他上线一会儿又下了
[01:57] <maclin> 主要是什么地方有问题？需要lenky这边配合一起分析一下不？
[01:57] <FJKong> 那一部分可能需要监控一下dubs
[01:57] <FJKong> 看看别的怎么做
[02:00] <ypwong> FJKong, 你今天是不是不用去 dellworld
[02:01] <FJKong> 我昨天去了,今天aron去,明天我再去
[02:02] <lenky> 上次商讨的indicator工作， 我这边的已经完成了。
[02:02] <lenky> 上一周主要弄系统助手里的输入法配置向导后端，到上周六加班一天才全部弄玩，显示是由另外一个同事在和qml前端进行联调，刚maclin也看了，基本没什么问题，主要界面的文字描述和展示需要再调整一下。
[02:02] <lenky> 整天开始，在弄金山快盘，我要先把金山快盘的框架搭起来，分成几个模块后，做金山快盘的同事就可以分开同时完成各自模块，9月底前出金山快盘1.0版应该没问题。
[02:03] <ypwong> FJKong, 那今天把要理清的东西跟 lenky 一起弄清楚
[02:04] <FJKong> ypwong: 好的
[02:04] <FJKong> 另外 我这边的工作还需要装一下xmir
[02:04] <FJKong> 上次joey已经试出来几个bug
[02:05] <ypwong> FJKong, 还没装好？
[02:05] <FJKong> 我昨天刚拿到测试机
[02:05] <ypwong> uh..
[02:06] <ypwong> 连系统装就 30 分钟的事情，如果已经有 image
[02:06] <FJKong> 22kb的下载速度
[02:06] <ypwong> FJKong, 还是先把 indicator 弄好再说
[02:06] <FJKong> 好的
[02:07] <lenky> 获取输入法列表的 我的配置向导这里就有实现
[02:07] <lenky> https://github.com/lenky0401/fcitx-configtool-wizard/blob/master/youker-assistant/fcitxcfgwizard.cpp#L77
[02:08] <FJKong> ok
[02:08] <maclin> ypwong，赞同你的提议，让lenky和FJKong今天一起把问题梳理一下，后面好推进
[02:09] <ypwong> :)
[02:09] <FJKong> lenky: 现在indicator还需要加什么功能
[02:09] <FJKong> 获取输入法, 设置全角半角
[02:10] <lenky> 啊？
[02:10] <lenky> 上次讨论不是说 现在indicator有的基本功能，qimpanel也要有么？
[02:11] <FJKong> 除了虚拟键盘
[02:11] <FJKong> 还有啥
[02:12] <lenky> 你电脑没装fcitx？
[02:12] <lenky> 看一下啊
[02:12] <jzheng> FJKong, clicked on the icon, you will see all of the options on the list. We should implement all of them.
[02:12] <lenky> 我不知道你已经做了哪些了
[02:12] <jzheng> lenky, ypwong, FJKong: we should have filed the bug in LP for these tasks, I guessed?
[02:13] <ypwong> jzheng, hmm.. as you like :)
[02:13] <maclin> jzheng,+1
[02:14] <maclin> we have proposed a blueprint: https://blueprints.launchpad.net/ubuntukylin/+spec/client-1308-ubuntukylin-input-method-development
[02:14] <jzheng> maclin, I see, but it is not detailed enough, I think.
[02:14] <jzheng> then, if we don't have, anyone can file this bug and list what we need to do?
[02:15] <jzheng> so that I think we can verify what task we have done, and what we have not
[02:15] <jzheng> also we can let others to help verify the features based on those bugs,
[02:15] <jzheng> btw, those bugs can be set as "Wishlist"
[02:17] <maclin> +1, lenky proposes a bug about qimpanel, FJKong about indicator?
[02:19] <jzheng> lenky, FJKong: any ideas?
[02:20] <FJKong> fine with me
[02:21] <jzheng> FJKong, ok, after you have the bug, please link it to https://blueprints.launchpad.net/ubuntukylin/+spec/client-1308-ubuntukylin-input-method-development
[02:21] <FJKong> jzheng: got
[02:22] <lenky> okay~
[02:26] <jzheng> FJKong, lenky: thx, btw, I think we should file the bug against ubuntukylin, but I am not sure if we should "also affect" fctix or not?
[02:34] <lenky> I donot kown how to affect the fcitx in lanuchpad.
[02:34] <ypwong> jzheng, just file in ubuntukylin should be fine
[02:34] <lenky> Maybe the fcitx's bug is managed by github or google groups, for example, https://github.com/fcitx/fcitx/issues?page=1&state=open
[02:34] <ypwong> i think that's part of our new fcitx-qimpanel
[02:35] <ypwong> lenky, yeah
[02:38] <jzheng> there is "also affect" in the bug page once you have filed the bug against UK, but it is OK if we think it is not necessary to do that for fcitx. :)
[02:38] <jzheng> e.g. https://bugs.launchpad.net/ubuntukylin/+bug/937968
[02:39] <jzheng> you can see it is filed against UK, but also for "smplayer".
[02:39] <jzheng> you can make the decision by yourself, ;)
[02:44] <lenky> Related bugs
[02:44] <lenky> Bug #1217658: develop an indicator based on qimpanel 	New
[02:45] <jzheng> lenky, great, thx
[02:45] <jzheng> FJKong, waiting for yours. :)
[02:47] <jzheng> lenky, can you also add more detailed items about what the target is ?
[02:48] <ypwong> bug 1217658 should be assigned to FJKong instead of lenky?
[02:49] <jzheng> ypwong, ah, yes, correct it now
[02:49] <jzheng> :$
[02:49] <smartboyhw> WHOA, you guys are so busy everyday ==
[02:51] <ypwong> smartboyhw, yeah lots of things to do
[02:51] <ypwong> what does == mean?
[02:52] <smartboyhw> ypwong, == is -.-
[02:53] <ypwong> doesn't look like a happy face
[02:55] <smartboyhw> ypwong, no
[02:57] <ypwong> :(
[06:44] <ypwong> FJKong, are you clear how to complete the indicator now?
[06:45] <FJKong> yes ,I am clear what to do, and now i am trying figure How to do it
[07:11] <ypwong> FJKong, cool, let's briefly sync up at the end of the day
[07:32] <JackYu> ypwong, I sent a email to you, about the input method discussion with sogou.
[07:33] <JackYu> and jzheng.
[07:35] <ypwong> thx
[14:12] <ypwong> FJKong, hi
[14:12] <ypwong> nice, new "Region & Languages" settings in Saucy!
[14:13] <FJKong> ypwong:
[14:13] <FJKong> ypwong: hi
[14:14] <ypwong> FJKong, indicator 进行得怎样？
[14:14] <FJKong> ypwong: 我在buglist上更新来进度
[14:15] <FJKong> 今天加了获取输入法 不过好像有点问题,lenky说明天帮我看一下
[14:15] <ypwong> FJKong, https://bugs.launchpad.net/ubuntukylin/+bug/1217658?
[14:15] <FJKong> 是啊
[14:16] <ypwong> 获取输入法什么问题？
[14:16] <FJKong> 获取不到数据
[14:17] <ypwong> FJKong, 使用什么方法获取的？
[14:18] <FJKong> 代码那块就是用的lenky在配置向导的代码
[14:18] <FJKong> 一样的
[14:20] <ypwong> 原理是？
[14:34] <ypwong> FJKong, ^
[14:38] <happyaron> ypwong: 为神码0.1分支的youker-assistant要我手工用sudo运行一下daemon……
[14:38] <happyaron> 貌似policykit的东西还没有在这里。。。
[14:39] <ypwong> 汗。。。
[14:40] <ypwong> 得问问 kobe 什么状况
[14:51] <sj> 你们讨论的最新的0.1代码还是release上面发布的？
[14:53] <sj> 如果是release上的，没有更新，没有policykit
[14:55] <ypwong> sj, happyaron 说的是 0.1 bzr branch 里的
[14:56] <sj> O
[15:08] <sj> ypwong，0.1 分支里边有policykit代码，但功能还有些问题。
[15:09] <Kobe_Lee> 是的，当初为了让可以入库，才建立0.1的，而我们继续在trunk上完善修改policykit后的功能修改
[15:10] <Kobe_Lee> trunck上对应的policykit已经完成
[15:19] <ypwong> happyaron ^^
[15:19] <happyaron> ypwong: 但是他却把license文件改成了有那些policykit代码的。
[15:22] <ypwong> happyaron, 明天改来得及吗？
[15:34] <happyaron> ypwong: 不太清楚，我先看一下吧。
[15:37] <happyaron> ypwong: 实在不行就ffe，一般问题不大


[08:54] <doa> anyone ever compiled a kind of microkernel  called  l4ka?
[08:55] <doa> http://www.l4ka.org/120.php
[20:34] <doa> hi