[00:02] <GunnarHj> attente, bschaefer: Just read your conversation with interest. A few hours ago I dropped this comment to seb128:
[00:02] <GunnarHj> "I have the impression that the im-config control in language-selector is now a no-op in Ubuntu. If that's the case, I suppose it should be hidden. At the same time, I assume that the im-config control still makes sense in Xubuntu and Lubuntu, and if so we should keep showing it in those derivatives."
[00:02] <GunnarHj> That side of the problem seems to be related (to some extent) to your discussion.
[00:05] <bschaefer> GunnarHj, im-config still does stuff with upstart atm, but possibly it doesn't need to be there
[00:06] <bschaefer> and should be removed, and we'll need to take this into consideration on how its used else where...as we don't want to force ibus for all of ubuntu
[00:07] <bschaefer> one thing mentioned was, if you install fcitx, then upstart will see that and use fcitx as the default
[00:07] <bschaefer> the problem is, g-s-d is start ibus-daemon each time which fixes a big bug but causes some other problems
[00:09] <GunnarHj> bschaefer: Well, I haven't tested yet, so my remark above i only a theory yet. Yes, I understand that the whole issue is about a conflict between the way g-c-c and g-s-d deals with input methods and "the old way" to do it.
[00:10] <bschaefer> GunnarHj, well right now im-config trumps g-s-d, as upstart looks at im-config, if im-config is set to say ibus, g-s-d doesn't do anything crazy
[00:10] <GunnarHj> bschaefer: Right. But what if im-config is set so something else?
[00:10] <bschaefer> im more concerned about what happens when im-config is set to a different IMe, which with ibus it has the --replace which might trump over fcitx (which wont be good)
[00:11] <bschaefer> right, i was going to test that soon :)
[00:11] <GunnarHj> bschaefer: Me to. ;-)
[00:11] <bschaefer> though, fcitx will get ran first through upstart, but ill have to see what happens... :), the more testing the better!
[00:13] <GunnarHj> bschaefer: IIRC, im-config sets fcitx if it's installed *and* Chinese is the current display language.
[00:15] <bschaefer> hmm soo fcitx runs, as well as ibus... so they are both running
[00:15] <bschaefer> though with the ibus-daemon set to --panel disable it just doesn't work
[00:15] <bschaefer> at lease fcitx works
[00:17]  * bschaefer assumes some wont be happy that the ibus-daemon is running when fcitx is set to default and running
[00:56] <GunnarHj> bschaefer: Looks like I was wrong. After having Installed fcitx and fcitx-sunpinyin and selected fcitx in language-selector, I can successfully create those beautiful characters by help of fcitx-sunpinyin. Also the fcitx icon shows up. So the ability to set the input method framework in language-selector still applies in Unity.
[00:58] <bschaefer> GunnarHj, right, but ibus is still running
[00:58] <bschaefer> with fcitx
[00:58] <bschaefer> which it really shouldn't be...
[00:59] <GunnarHj> bschaefer: Yes it is. But does it hurt? And if it didn't run, would the Text Entry window in g-c-c make any sense?
[01:00] <bschaefer> not so much, and that bug would still be around, the problem is...if you've selected xim
[01:01] <bschaefer> then want to us ibus
[01:01] <GunnarHj> bschaefer: What then?
[01:01] <bschaefer> use*
[01:01] <GunnarHj> bschaefer: Well, if you want to use ibus, why on earth would you select xim?
[01:01] <bschaefer> GunnarHj, the problem is that dbus command makes ibus not work, so the only way to get ibus to work if your im-config -n xim
[01:02] <bschaefer> GunnarHj, cause ibus still works with xim :)
[01:02] <bschaefer> if it is your XMOD* is set to none, which mean upstart doesn't start ibus, then the dbus call starts up a non working ibus daemon
[01:05] <GunnarHj> bschaefer: Hmm... The "none" option in language-selector actually sets xim. Is that possibly a problem then?
[01:06] <GunnarHj> bschaefer: Of is it maybe a good thing?
[01:06] <GunnarHj> Or
[01:06] <bschaefer> GunnarHj, well XIM isn't an input engine
[01:06] <bschaefer> its an extra layer on top that most all input engines work through
[01:11] <GunnarHj> bschaefer: In any case, if you want to use ibus, is there any reason not to select ibus?
[01:13] <bschaefer> GunnarHj, well we are attempting to assume the user does not know about im-config
[01:13] <bschaefer> if they don't...then it'll fun to try and get ibus working when you select chinese in the text entry
[01:13] <bschaefer> and only english is coming out
[01:14] <bschaefer> GunnarHj, would you mind testing that? Set the text entry to a chinese language and have im-config -n xim
[01:14] <bschaefer> which means g-s-d is starting the ibus-daemon (with options that makes ibus not work for me)
[01:14] <bschaefer> then I try to use chinese/pinyin and i only get english
[01:15] <GunnarHj> bschaefer: Sure, I can try. Logging out first and get back in a few minutes.
[01:16] <bschaefer> GunnarHj, thank you
[01:28] <GunnarHj> bschaefer: You are right, I couldn't use Chinese/Pinyin. Checking the env variables:
[01:28] <GunnarHj> $ env | grep IM_
[01:28] <GunnarHj> CLUTTER_IM_MODULE=xim
[01:28] <GunnarHj> IM_CONFIG_PHASE=1
[01:28] <GunnarHj> QT4_IM_MODULE=xim
[01:28] <GunnarHj> GTK_IM_MODULE=xim
[01:28] <bschaefer> echo $XMODIFIERS
[01:28] <bschaefer> as well
[01:29] <bschaefer> GunnarHj, its not the problem with whats set, its the problem with the dbus activation
[01:29] <bschaefer> GunnarHj, do a "ps aux | grep ibus-daemon"
[01:29] <bschaefer> you'll see the --disable panel
[01:35] <GunnarHj> bschaefer: But I'm still confused. The default option in language-selector is "default", which means that dbus/im-config starts ibus if only ibus is installed and one of the CJKV languages is the display language, or else dbus doesn't run im-config at all (but g-s-d does). In both cases it works for me.
[01:36] <bschaefer> GunnarHj, in both cases ibus/pinyin works for you?
[01:36] <GunnarHj> bschaefer: Yes. Hmm... Maybe I should try again to confirm it... Getting back soon.
[01:46] <asac> RAOF: hey ... i somehow have no X anymore on latest saucy
[01:46] <asac> RAOF: not sure what happened, but i hoped you can help
[01:46]  * asac types from a console
[01:46] <RAOF> asac: Hm. Let me see what changed while I was away...
[01:46] <asac> RAOF: the lightdm upstart log says:
[01:47] <asac> seat: cant create unsupported display server 'x'
[01:47] <asac> i removed the xorg.conf.failsafe a few times
[01:47] <asac> that didnt help
[01:47] <RAOF> That's odd.
[01:47] <RAOF> What's in /etc/lightdm/lightdm.conf.d?
[01:48] <asac> 10-ubuntu.con
[01:48] <asac> f
[01:48] <asac> 50-greeter-wrapper.conf
[01:48] <asac> 50-ubuntu.con
[01:48] <asac> 50-unity-greeter.conf
[01:48] <asac> 50-xserver-command.conf
[01:48] <asac> 52-ubuntu-touch.conf...
[01:48] <asac> hmm
[01:48] <asac> whats that :)_
[01:49] <asac> wow ... that one surely has to go away :)?
[01:49] <asac> RAOF: ^^
[01:49] <RAOF> I note that *I* don't have that config file.
[01:49] <asac> wow
[01:50] <asac> that helped
[01:50] <asac> wtf :)
[01:50] <RAOF> Where did that come from?
[01:50] <asac> not sure... 3 month ago i had accidentially the phablet ppa enabled
[01:50] <asac> however, ...  the system was cleaned from that incident
[01:50] <asac> and it worked since then for many reboots... so not sure
[01:51] <asac> ubuntu-touch-session
[01:51] <asac> wonder howthat can be instlaled
[01:51]  * asac purges that
[01:52] <RAOF> Maybe lightdm got updated past the point that the config file started to take effect?
[01:52] <asac> RAOF: thanks so much... i doubt thats anything you need to be worried about... except maybe how it ended up getting bad just now
[01:52] <asac> yeah i assume so. thx
[01:52]  * asac goes to X rather than console
[01:53] <asac> something is very odd
[01:53] <asac> all looks different than before... but well, its unity running, so why would i complain :)
[01:54] <asac> RAOF: thx!
[01:54] <RAOF> Glad to be of service!
[02:03] <GunnarHj> bschaefer: Yes, I can produce those beatiful characters using ibus/pinyin also when dbus doesn't run im-config at all, i.e. when "default" is selected in language selector and my display language is English. But when I select "ibus", and the proper env variables for ibus are set, a help window is shown which I don't see when "default" is selected. Also, to see the ibus/pinyin icon, "ibus" needs to be selected.
[02:04] <GunnarHj> bschaefer: But this should really be tested by an im user, shouldn't it?
[02:05] <bschaefer> GunnarHj, whats your im-config set to?
[02:06] <bschaefer> GunnarHj, and when you say you select ibus, do you mean in that language app?
[02:06] <bschaefer> umm
[02:06] <GunnarHj> bschaefer: What do you mean by "set to"?
[02:06] <bschaefer> language support app?
[02:07] <bschaefer> GunnarHj, i mean, if you type im-config and the gui pops up
[02:07] <bschaefer> whats the active IM?
[02:07] <bschaefer> or do: echo $XMODIFIERS
[02:07] <bschaefer> and let me know what it says...
[02:09] <GunnarHj> bschaefer: When "default" is selected in l-s, the active IM is default, and when "IBus" is selected in l-s, the active IM is ibus.
[02:10] <bschaefer> GunnarHj, im not sure what language selector is then :)
[02:11] <GunnarHj> bschaefer: Or when "default" is selected, there is no ~/.xinputrc file, while when "IBus" is selected, there is a ~/.xinputrc file saying "run_im ibus".
[02:11] <GunnarHj> bschaefer: The IM selector in language-selector just sets the active IM.
[02:12] <bschaefer> GunnarHj, well the overall thing is to look how ibus-daemon is started
[02:12] <bschaefer> ps aux | grep ibus-daemon
[02:12] <bschaefer> will tell you the options on it
[02:12] <bschaefer> if it has --panel disable then its not going to work :), which if im-config is not set to ibus seems to always be on for it ...
[02:16] <GunnarHj> bschaefer: I was the one who prepared im-config for Ubuntu. I chose to make it default to "cjkv mode" to avoid that ibus-daemon is started for everyone, also those users who don't know what an input method is. Now I wonder: What if we would change that, and make "ibus" the default for im-config?
[02:17] <bschaefer> GunnarHj, then all will work, but some don't want ibus-daemon to always be on
[02:17] <GunnarHj> bschaefer: I mean, ibus-daemon is always started anyway nowadays.
[02:17] <bschaefer> GunnarHj, right, which I think thats a bug?
[02:17] <bschaefer> GunnarHj, but if im-config -n ibus was set then we would be all fine
[02:18] <GunnarHj> bschaefer: That would be a simple thing that even might be possible to fix before the release...
[02:19] <bschaefer> very true, and i don't think it would cause any problems...hmm
[02:19] <GunnarHj> bschaefer: Not saying that it's an ideal solution, but given the ibus integration in g-c-c, it may prevent user confusion.
[02:20] <bschaefer> GunnarHj, yeah, its better then what we have now
[02:20] <bschaefer> kylin want fcitx then it wont be a problem there either
[02:21] <bschaefer> as they should be able to set that them selfs (which you hope they do...)
[02:21] <GunnarHj> bschaefer: I'm not sure how the achieve the fcitx default.
[02:21] <GunnarHj> they
[02:22] <bschaefer> GunnarHj, if we actually set ibus to default as well we can drop the dbus activation thing with out causing that bug/crash? Along with not always having the ibus daemon
[02:22] <bschaefer> GunnarHj, hmm couldn't they have a patch? I mean how to they set fcitx to default atm anyway?
[02:22] <bschaefer> how do*
[02:22] <GunnarHj> bschaefer: Don't know.
[02:22]  * bschaefer isn't super how they version of ubuntu works...
[02:22] <bschaefer> GunnarHj, but I think thats our best solution atm
[02:23] <GunnarHj> bschaefer: It's over 4 a.m. here now... But I can file an im-config bug tomorrow, and involve e.g. happyaron in it.
[02:23] <bschaefer> GunnarHj, o geez! Sorry for keeping you up so late!
[02:24] <bschaefer> GunnarHj, thanks a ton! Have a good night!
[02:24] <bschaefer> its only 7:24 pm here :)
[02:24] <GunnarHj> bschaefer: My choice; no problem. ;-)
[02:24] <bschaefer> GunnarHj, cya!
[02:24] <GunnarHj> bschaefer: Good night to you as well.
[02:25] <bschaefer> thanks :)
[05:30] <jibel> Good morning
[05:31] <didrocks> salut jibel
[05:31] <didrocks> jibel: getting up earlier than few weeks ago?
[05:32] <jibel> Salut didrocks, ça va?
[05:32] <jibel> didrocks, yes, I'm starting earlier to finish my day earlier :)
[05:32] <didrocks> heh :)
[05:32] <didrocks> ça va bien, et toi?
[05:33] <jibel> and I realized there are living creatures outside ;)
[05:33] <jibel> didrocks, ça va ça va
[05:35] <didrocks> ahah, really, living creatures outside?
[08:05] <Laney> hey!
[08:11] <seb128> hey Laney, hey desktopers
[08:11] <seb128> how is everyone?
[08:12] <Laney> great, good climbing session last night!
[08:12] <Laney> you?
[08:13] <seb128> I'm good thanks
[08:15] <didrocks> hey seb128, Laney!
[08:15] <seb128> didrocks, lut, en forme ?
[08:15] <didrocks> ça va, et toi?
[08:16] <seb128> nickel
[08:16] <Laney> hey didrocks
[09:17] <seb128> Laney, do you if the fact that you can't go to the settings list when you open "system-settings <panel>" is a feature or a bug?
[09:18] <Laney> pretty sure it was on purpose
[09:18] <Laney> so you can't go "back" confusingly
[09:18] <Laney> we had it that way originally
[09:19] <seb128> I think we should add it back
[09:19] <seb128> the current situation is a bit buggy
[09:19] <seb128> if you open a specific panel from an indicator
[09:19] <seb128> you get screwed until you force close the app
[09:20] <Laney> how would being able to go to the index help?
[09:20] <seb128> e.g battery indicator ->settings
[09:20] <seb128> go back to the dash
[09:20] <seb128> search for settings
[09:20] <seb128> click on it
[09:20] <seb128> it refocus the running instance open on battery
[09:20] <Laney> that should send the app back to the main page
[09:20] <seb128> ok, that's one other way to fix it
[09:20] <Laney> it'd also break if you then try to open another panel from a different indicator I suppose
[09:20] <seb128> though I'm not sure we are in control of what is happening there
[09:21] <seb128> I think it's upstart-app-launch doing the single instance
[09:22] <seb128> no, opening from a different panel works
[09:22] <Laney> is that because single instance is broken?
[09:22] <seb128> it doesn't seem so, I've only one preview in my recent apps list
[09:23] <Laney> it must kill the old one then
[09:23] <seb128> it seems it do
[09:23] <seb128> "upstart-app-launch ubuntu-system-settings" on my desktop closes the old one
[09:24] <Laney> you should talk to unity people
[09:24] <seb128> yeah, I'm going to talk to ted when he gets online
[09:24] <seb128> he's the one who has been working on the app launch stuff
[09:24] <seb128> Laney, thanks
[09:29] <Laney> phablet@ubuntu-phablet:~$ date
[09:29] <Laney> Thu Oct  3 10:29:08 BST 2013
[09:29] <Laney> yay
[09:29] <mlankhorst> up to date!
[09:29] <seb128> working and persistent?
[09:29] <seb128> Laney, I opened https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+bug/1234588
[09:29] <ubot2> Launchpad bug 1234588 in ubuntu-system-settings (Ubuntu) "Can't go back to the summary after opening a specific subpanel" [High,Confirmed]
[09:29] <Laney> it updated /etc/timezone which I think was missing before
[09:29] <Laney> err I mean localtime
[09:30]  * Laney reboots
[09:30] <seb128> good
[09:30] <Laney> it's still not a symlink on first boot though
[09:30] <Laney> yeah, persisted
[09:33] <seb128> \o/
[09:34] <seb128> shrug, why is firefox not remembering my google login, I've to log in again every time I reopen it
[09:36] <Tm_T> seb128: keyloggers need more chances on catching your password
[09:45] <Laney> Mirv: is gitorious the place to submit qtsystems patches?
[09:50] <seb128> Laney, I think it's on https://bugreports.qt-project.org
[09:51] <Laney> hmm
[09:51] <Laney> don't see qtsystems in the projects tehre
[09:51] <seb128> Laney, https://bugreports.qt-project.org/browse/QTBUG-31624
[09:51] <seb128> " Systems: SystemInformation " it seems
[09:51] <seb128> (that's one I had in my awesome bar)
[09:52] <seb128> Laney, https://wiki.canonical.com/UbuntuEngineering/ContributingToQt btw
[09:52] <Mirv> Laney: either bugzilla or a straight codereview request to gitorious (needs certain setupping)
[09:54] <Laney> yeah I don't know what applies to qtsystems
[09:54] <Laney> that seems to be a separate project
[09:55] <Mirv> Laney: the same https://codereview.qt-project.org/#q,status:open+project:qt/qtsystems,n,z
[09:55] <Laney> aha
[09:56] <Laney> ok, doing that then
[09:56] <Laney> better test the patch first though ...
[10:09] <Laney> Mirv: could you add me to the group please?
[10:10] <Mirv> Laney: done, should be visible now
[10:11] <Laney> it is, thanks
[10:33] <JamesTait> Laney, remember that problem I had a coupleof weeks back, where I'd login and get dumped back to the greeter?
[10:34] <JamesTait> And bcurtiswx had the same problem - well, I've got the same thing happening again now.  I can get to a desktop in the guest session, but not using my proper account.
[10:37] <JamesTait> Nothing has been touched in ~/.cache/upstart - the datestamps are an hour old.
[10:37] <Laney> JamesTait: Try moving ~/.Xauthority
[10:39] <JamesTait> Laney, OK, giving that a go...
[10:39] <JamesTait> Laney, success!  Thanks!
[10:40] <JamesTait> Laney, is this a known problem with a bug report I can contribute to?
[10:41] <Laney> It's fixed in lightdm already, just not in saucy yet
[10:41] <JamesTait> Excellent! :)
[10:41] <JamesTait> I'll be getting on with my work now then. :)  Thanks again!
[13:42] <seb128> chrisccoulson, hey, how are you?
[13:43] <seb128> chrisccoulson, do you know if that known issue with the current firefox and "session handling"
[13:43] <seb128> chrisccoulson, it keeps forgetting my google session (e.g I've to re-auth every day) and I often gets the "didn't close properly, do you want to restore the tabs" screen when simply closing and reopening a bit later
[13:43] <seb128> chrisccoulson, it looks like some stuff wouldn't get saved properly or would get corrupted
[13:44] <chrisccoulson> seb128, i haven't noticed anything like that before
[13:46] <seb128> chrisccoulson, hum, ok :/
[13:51] <chrisccoulson> seb128, file permissions are ok?
[13:54] <seb128> chrisccoulson, from what I know yes, on what file should I check?
[13:55] <seb128> *** WARN addons.xpi: Exception running bootstrap method shutdown on webapps-team@lists.launchpad.net: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIComponentRegistrar.autoUnregister]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"
[13:55] <seb128> I wonder if that's another webapp issue
[13:55] <seb128> the addon is turned off though
[13:57] <seb128> brb, session restart
[14:03] <mterry> oops, got disconnected
[14:03] <mterry> attente, (assuming you didn't see my previous poke) What can we do to speed up landing of indicator-keyboard branches/package?
[14:04] <mterry> attente, is indicator-stack on manual saucy landing?
[14:05] <attente> mterry, i'll try to find someone to review it
[15:25] <seb128> Laney, bah, there are bugs in your MR adding TRANSLATORS comments, that will teach me to just glance at those rather than do a proper review :p
[15:25] <Laney> NO!
[15:25] <seb128> Laney, http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/revision/409/plugins/system-update/PageComponent.qml
[15:26] <seb128> Laney, see the 2 first chunks
[15:26] <seb128> Laney, (I'm just pushing a fix)
[15:26] <Laney> ahaha
[15:26] <seb128> the first one seems a middle click error
[15:26] <seb128> not sure what happened to the else
[15:26] <Laney> the first one is probably that stupid qt creator behaviour
[15:26] <seb128> the completion on alt-tab?
[15:26] <Laney> yes
[15:26] <seb128> yeah, I hate that one :/
[15:27] <Laney> other one is general failure i guess
[15:29] <seb128> Laney, btw, did you get a reply for ev about whoopsie on touch?
[15:29] <Laney> oh, no
[15:30] <Laney> I forgot what the specific question was
[15:30] <seb128> I saw him talk on IRC yesterday and today
[15:30] <seb128> Laney, I think it was about enabling whoopsie from the security panel
[15:30] <seb128> in context of logind/polkit/ro?
[15:30] <Laney> oh yes
[15:31] <seb128> Laney, https://code.launchpad.net/~seb128/ubuntu-system-settings/update-working-check-update/+merge/189118
[15:32] <Laney> pinged him in devel
[15:34] <seb128> Laney, thanks
[15:46] <Laney> is there some problem with screen blanking / unlocking in desktop atm?
[15:47] <Laney> when unlocking I see the contents of the display instead of the wallpaper on one of the monitors
[15:51] <seb128> I ran into that a few time as well
[15:51] <seb128> I'm sure mdeslaur doesn't like it
[15:51] <seb128> give access to whatever is under the lock for a second
[15:51] <seb128> I wonder if that's an xorg thing (e.g wrong buffer on screen or something)
[15:53] <Laney> don't know
[15:53] <Laney> mlankhorst: what do you think about this xorg theory? :P
[15:54] <Laney> it doesn't seem to happen when locking explicitly
[15:54] <Laney> only after the timeout
[16:01] <seb128> Laney, it's not easy to reproduce in any case
[16:01] <seb128> but I've a 2 screens setup, and I just had a case where I could see my right screen "unlocked" with the unlock dialog on the left
[16:02] <seb128> e.g I had xchat showing on one in the screens during the lock
[16:02] <Laney> yeah
[16:02] <Laney> was it updating?
[16:02] <Laney> or just what was there when it locked
[16:02] <seb128> I don't think so
[16:02] <seb128> it was a buffer of the lock time I think
[16:12] <desrt> merge ALL the things!!
[16:12]  * desrt loves that start-of-the-cycle feel
[16:31] <seb128> desrt, you live in the futur it seems, come back to real time, we still have some bug fix fun before getting there ;-)
[16:32]  * desrt should have kept his mouth shut
[16:32] <desrt> uh.... lunchtime!
[16:32]  * desrt runs
[16:33] <seb128> ;-)
[16:35] <bschaefer> seb128, hey
[16:36] <seb128> bschaefer, hello
[16:36] <bschaefer> seb128, soo something interesting about the ibus problem in g-s-d
[16:37] <bschaefer> seb128, if you're not aware...if g-s-d starts up ibus, CJK fails to work unless you restart the ibus-daemon with correct options
[16:37] <bschaefer> seb128, soo GunnarHj  proposed this bug: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1234768
[16:37] <ubot2> Launchpad bug 1234768 in im-config (Ubuntu) "Consider a change of the im-config default" [High,New]
[16:38] <seb128> happyaron, attente: ^ do you know what's going there
[16:38] <robru> seb128, hey. any known issues with power saving on desktop? i recently switched back to xorg (after beta testing xmir for a long time), and now my screens never power down. they were on all last night
[16:38] <seb128> bschaefer, I'm pretty useless when it comes to understand CJK and what role im-config plays there
[16:39] <bschaefer> seb128, no worries :), thanks!
[16:39] <seb128> robru, not that I know, it could be a gnome-settings-daemon issue... what value do you have in g-c-c for "turn screen off if unactive for..."
[16:39] <happyaron> seb128: it would be good to revert the triggerred startup of im-config, and revert im-config behavior to auto
[16:39] <happyaron> this will let ibus running for everyone, but it will resolve all the headaches
[16:39] <seb128> happyaron, "triggered startup of im-config"?
[16:40]  * didrocks waves good evening and see you next thursday!
[16:40] <seb128> where did we add that?
[16:40] <didrocks> (or before for some of you ;))
[16:40] <seb128> didrocks, night, good luck for the next days, see you on saturday
[16:40] <happyaron> seb128: I was once told it's started using upstart user session
[16:40] <didrocks> see you on saturday seb128!
[16:40]  * happyaron on holidays right now, but anyway, ;-)
[16:41] <robru> seb128, 10 minutes
[16:41] <bschaefer> upstart starts the selection of what im-config is set to, and +1 from me to setting it to auto
[16:41] <happyaron> I short revert to upstream behavior is a working choice, but it's not cool...
[16:41] <seb128> happyaron, oh, I didn't know, enjoy!
[16:41] <happyaron> :)
[16:42] <seb128> bschaefer, happyaron, attente: you guy just tell me what you think is best (or comment on https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1234768) and we can make that happen
[16:42] <ubot2> Launchpad bug 1234768 in im-config (Ubuntu) "Consider a change of the im-config default" [High,New]
[16:42] <bschaefer> seb128, alright sounds good
[16:43] <happyaron> bschaefer: I'm not sure if the upstart handled startup would affect users, but I think it's started when Xsession is run anyway.
[16:44] <bschaefer> happyaron, that could be it as well, I only started digging into upstart/im-config last week :)
[16:47] <happyaron> bschaefer: In my experiment, Xsession runs im-config, and it works for cjkv, others run im-config when they click on something that triggers it, which will make indicator-keyboard not working.
[16:47] <happyaron> if we switch to auto for default, triggered activation is not needed at all.
[16:49] <bschaefer> true, which is nice, the problem i was running into is the ibus-daemon was being started with --panel disable which was causing the ibus-daemon to not work at all
[16:49] <bschaefer> happyaron, but in either case, go enjoy your time off :)
[16:50] <happyaron> :)
[16:53] <seb128> bschaefer, can't we just make g-s-d not drop --panel? or would that be wrong (e.g make an indicator appear for everyone not using the feature)?
[16:54] <bschaefer> seb128, at that point we might as well just set im-config to ibus or auto
[16:54] <seb128> same question
[16:54] <seb128> would that make everyone get an indicator?
[16:54] <bschaefer> yes
[16:54] <happyaron> I think auto is better than ibus, though.
[16:55] <bschaefer> seb128, im starting to think it could be a possible bug in ibus...
[16:55] <bschaefer> happyaron, agreed
[16:55] <seb128> we don't want an ibus icon for users not have an im need/configured
[16:56]  * bschaefer wonders if the k-indicator is just stealing the super+space shortcut from ibus if --panel disable...
[16:57] <bschaefer> seb128, true, but the ibus daemon is already running anyway...
[16:57] <seb128> well, that's a problem by itself
[16:57] <seb128> (use resources for nothing)
[16:58] <bschaefer> right, hmm, its just when the ibus-daemon has --panel disable you can't actually use ibus at all (but its running!)
[16:58] <bschaefer> so if you were to go into ibus-setup, or even in the text-entry and add pinyin/chinese it wouldn't work
[16:59] <bschaefer> at lease from my testing...
[17:00] <seb128> bschaefer, why would ibus have a mode where it's not usable?/why would we call it in this mode?
[17:01] <bschaefer> seb128, that im not sure of...but thats what it seems to be in when im-config is set to none, and g-s-d starts it
[17:01] <bschaefer> soo this could very well be the overall issuse that needs to be addressed...
[17:01] <bschaefer> seb128, so right now, you have a default set up im wise?
[17:02] <bschaefer> and echo $XMODIFIERS
[17:02] <bschaefer> says none right?
[17:02] <seb128> $ echo $XMODIFIERS
[17:02] <seb128> $
[17:02] <seb128> I've a "default set up"
[17:02] <seb128> I'm using french and I've added a GB layout
[17:03] <seb128> e.g just standard layout, no im
[17:03] <bschaefer> seb128, that seems good, and umm ps aux | grep ibus-daemon shows a --panel disable option?
[17:03] <bschaefer> seb128, if so, add chinese/pinyin to text entry
[17:03] <bschaefer> and you would think that since ibus-daemon is started, that it should work right?
[17:05] <happyaron> seb128: that mode makes other stuff manages IM
[17:05] <seb128> happyaron, what is "other stuff"? g-s-d?
[17:06] <happyaron> seb128: for people who'd like to put environmental variables in xsession start sequence
[17:06] <happyaron> seb128: when im-config detects any of those variables are set it quits and do not set any of them.
[17:07] <bschaefer> don't you have to reboot though? I though im-config was only taken into consideration on a xsession restart?
[17:07] <bschaefer> thought*
[17:08]  * bschaefer still gets --panel disable when pinyin is set in the text entry...causing it to fail
[17:08] <bschaefer> though i should double check that
[17:08]  * bschaefer relogs
[17:08] <happyaron> anytime a new Xsession is started im-config tries to do everything again.
[17:08] <bschaefer> right, i thought you were saying in the middle of session it would quit and try to do that again
[17:09]  * bschaefer mis read
[17:09] <happyaron> (or be precise, everytime Xsession is executed)
[17:11] <bschaefer> soo i've chinese set in text entry which doesn't seem to be reflecting in ibus-setup.. ive im-config set to none
[17:11] <bschaefer> which is default (or so it seems?), and im not able to type in pinyin
[17:12] <happyaron> bschaefer: mind run `env | grep IM` ?
[17:12] <bschaefer> /usr/bin/ibus-daemon --replace --xim --panel disable is started, as it doesn't detect the i've chinses set in my text entry
[17:12] <bschaefer> yeah
[17:13] <bschaefer> IM_CONFIG_PHASE=1
[17:13] <bschaefer> which seems to be all...
[17:14] <happyaron> what about `env | grep XMODIFIERS` ?
[17:14] <bschaefer> happyaron, XMO is not set, since im on none
[17:15] <bschaefer> im-config -n none
[17:15] <happyaron> then it won't work...
[17:15] <bschaefer> happyaron, right, but thats the default...
[17:16] <bschaefer> im-config by default with an english layout to set it to none right?
[17:16] <happyaron> that's a ubuntu default, to get rid of starting ibus for non-cjkv locales.
[17:16] <happyaron> debian default is auto for all.
[17:16] <bschaefer> happyaron, right, but then I select a chinese language in my text entry...then reboot and its still none, and now chinese doesn't work :)
[17:16] <bschaefer> happyaron, yeah, this is why I would like auto, this means that the ibus panel will be there though
[17:17] <bschaefer> which is something seb128 doesn't want
[17:17] <happyaron> bschaefer: but g-s-d cannot change those variables if I'm correct
[17:18] <happyaron> when g-s-d is started, it's late to set those variables for the desktop session.
[17:18] <bschaefer> nope, but g-s-d is starting an ibus-daemon that makes it not work if the usr wants chinese...
[17:18] <bschaefer> i don't think it can change it
[17:18] <happyaron> so you added a text entry, but nothing is working to set variables...
[17:18] <bschaefer> yup, and it still thinks you are a non cjkv user
[17:18] <bschaefer> so it starts ibus-daemon with a --panel disable
[17:19] <bschaefer> which means you cannot user CJK languages with out setting im-config your self or killing and restarting the ibus daemon
[17:19] <bschaefer> happyaron, so theres really 2 arguments, 1 we don't want the ibus panel if we don't use ibus, bug g-s-d need ibus to be running
[17:19] <happyaron> don't think restarting ibus daemon will make Chinese input work, though other stuff may work (in g-c-c).
[17:20] <bschaefer> well it makes ibus work again at lease
[17:20] <bschaefer> happyaron, its a fun workaround that doesn't always work on some autopilot tests in unity atm...but i would like a more correct fix for this :)
[17:21] <bschaefer> so how do we ensure ibus works if we want to type chinese, but by default dont want to start the panel?
[17:21] <happyaron> bschaefer: even restarting ibus make itself work, this makes the settings g-c-c pointless...
[17:21] <bschaefer> right...
[17:21] <happyaron> guess no proper way atm.
[17:21] <bschaefer> happyaron, i don't see a solution where we disable the panel correctly, so I still think we should set im-config to auto
[17:22] <bschaefer> and have the ibus panel...
[17:22] <happyaron> agree
[17:22] <bschaefer> the only reason I see to now having the ibus-panel is it looks odd..but the daemon is already running and I don't think theres enough time to fix that correctly
[17:22] <bschaefer> i see to not*
[17:22] <happyaron> I see.
[17:22] <bschaefer> geez english is all i speak and i suck at it :)
[17:24] <bschaefer> so as long as the ibus-daemon is always going to be on, we might as well set it to auto and just have the ibus panel there for now... seb128?
[17:24] <seb128> bschaefer, I don't understand enough of the problem to have a valuable opinion, if you guys think it's the best way, let's go for that
[17:25] <bschaefer> alright sounds good
[17:25] <bschaefer> seb128, sorry for pulling you back in each time :)
[17:26] <seb128> bschaefer, no worry, good that you do because I sort of have to ack/nack the solutions
[17:37] <seb128> robru, do you have the screen locking option enabled as well and on what time?
[17:38] <robru> seb128, turn screen off: 10min, lock: on, lock screen after: screen turns off, require password: checked
[17:39] <robru> seb128, so, when i woke up this morning, screen was black & locked, but definitely powered on.
[17:39] <robru> seb128, also happened last night too, left laptop unattended for several hours, screen was black but on.
[17:42] <seb128> robru, yeah, I don't know, I can't reproduce, I just tried with similar settings (but 1 min), my external screen goes in standby (e.g the led goes from blue to orange)
[17:43] <robru> seb128, any other troubleshooting things you can think of to try? led definitely blue here :-/
[17:43] <seb128> robru, gdbus call --system -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.ListInhibitors
[17:44] <seb128> in case you have an inhibtor app running...
[17:44] <robru> seb128,  ([('sleep', 'root', 'inhibited', 'delay', uint32 0, uint32 866), ('sleep', 'robru', 'GNOME needs to lock the screen', 'delay', 1000, 19330), ('handle-lid-switch', 'robru', 'Multiple displays attached', 'block', 1000, 19330), ('handle-power-key:handle-suspend-key:handle-hibernate-key', 'robru', 'GNOME handling keypresses', 'block', 1000, 19330)],)
[17:44] <robru> ?
[17:46] <seb128> robru, I don't see anything obviously wrong in there :/
[17:46] <seb128> could also be an xorg issue I guess
[17:46] <robru> seb128, arg :-/
[17:46] <seb128> e.g the userland could be doing what it needs
[17:47] <robru> seb128, hummm, this user account i'm using is many years old. sometimes I wonder if i don't have some kind of stale dotfile that interferes with modern software versions somehow...
[17:48] <seb128> robru, I guess you could try in a guest session to see if that happens as well
[17:48] <robru> seb128, ok, next time I have a spare 10 minutes I'll try that ;-)
[17:48] <seb128> robru, that's in 15 years right? ;-)
[17:49] <seb128> (crazy life here)
[17:50] <robru> seb128, lol, haha. I mean when I go for lunch or something, today ;-)
[18:16] <GunnarHj> seb128, bschaefer: Looks like some kind of decision was made to change the im-config default to "auto". Even if nobody mentioned it in today's IRC discussion, I suppose you agree that we should not do that change for derivatives that don't use g-c-c. So a hint how we make that distinction would be nice. Is it possible to use conditional statements directly in http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/im-con
[18:16] <GunnarHj> fig/saucy/view/head:/default/im-config ?
[18:19] <mlankhorst> Laney: ..?
[18:24] <bschaefer> GunnarHj, i agreed with setting im-config to auto
[18:25] <bschaefer> and so did happyaron
[18:26] <GunnarHj> bschaefer: Yes, saw that. That's what I meant with "some kind of decision". ;-)
[18:26] <bschaefer> GunnarHj, o :), is it set to auto already? or was that link to a branch you have?
[18:27] <GunnarHj> bschaefer: No, it was the Debian original variant. There is currently an Ubuntu patch that changes it.
[18:28] <bschaefer> GunnarHj, oo i see, i would think we can just lift that patch, or edit the patch in a way that leaves the auto there?
[18:29] <GunnarHj> bschaefer: But just doing so would also affect Kubuntu, Xubuntu, Lubuntu...
[18:29] <bschaefer> :(, im not sure how that should be handled then...
[18:30] <GunnarHj> bschaefer: Me neither. Hoping for advice from seb128.
[18:31] <bschaefer> well they might end up just using auto by default now anyway
[18:31] <bschaefer> GunnarHj, as it wont cause any more trouble then there already is
[18:31] <bschaefer> ie. the ibus-daemon is still always starting for them in g-s-d...
[18:32] <GunnarHj> bschaefer: They don't have any g-c-c related trouble, since they don't use it. Changing it to auto for them would result in the ibus icon always be shown for everyone.
[18:33] <bschaefer> GunnarHj, o they don't use g-c-c? hmm
[18:33] <bschaefer> i wonder if we can just check if that package is installed haha...
[18:33] <GunnarHj> bschaefer: Or do you mean that they still use g-s-d?
[18:33] <bschaefer> GunnarHj, yeah that is what i ment, also do they install ibus by default?
[18:34] <bschaefer> if ibus isn't installed by default then it wont be a problem...
[18:34] <GunnarHj> bschaefer: They do install ibus by default AFAIK.
[18:35] <GunnarHj> bschaefer: checking whether g-c-c installed sounds like a good idea
[18:36] <bschaefer> GunnarHj, yeah, if they don't have g-c-c/g-s-d? If you have g-c-c you are using g-s-d right? Can you have g-s-d with out g-c-c?
[18:36] <GunnarHj> bschaefer: Don't know the answer to the latter question.
[18:37] <bschaefer> well I would think if they have g-s-d then they are going to run into the problem with the ibus daemon always starting
[18:37] <bschaefer> GunnarHj, so possibly we should check if g-s-d is installed?
[18:38] <bschaefer> if it is, then set auto, i've not clue how to check if a package i installed or not though...
[18:38] <bschaefer> GunnarHj, we might just have to wait for seb128, he might have a better answer :)
[18:38] <GunnarHj> bschaefer: Isn't it the other way around? I mean, if they have g-s-d, it would prevent the ibus icon from showing up, and in that case auto would work for everyone.
[18:39] <bschaefer> GunnarHj, well it depends on what problem we are trying to solve...
[18:40] <bschaefer> GunnarHj, I was thinking we setting auto when g-s-d is installed/running  because we want ibus-daemon to run with the correct arguments?
[18:40] <GunnarHj> bschaefer: I'm trying to avoid a regression meaning that the ibus icon starts showing up for everyone in Kubuntu etc.
[18:41] <GunnarHj> bschaefer: But let's wait and see if seb128 can bring some light.
[18:41] <bschaefer> GunnarHj, thats a problem though...we can't have the ibus-daemon running with the --panel disable...
[18:42] <bschaefer> GunnarHj, if you do, then CJK does not work in ibus at all, unless you set the im-config your self, or restart ibus which defeats the purpose of g-s-d/g-c-c ...
[18:43] <GunnarHj> bschaefer: Now I don't follow you. Changing to auto would take care of that, wouldn't it?
[18:43] <bschaefer> GunnarHj, yes, but the ibus panel will be shown :(
[18:43] <bschaefer> which is what you are trying to prevent
[18:44] <GunnarHj> bschaefer: As long as we keep letting g-s-d do its thing, the icon won't be shown.
[18:44] <bschaefer> GunnarHj, but then ibus doesn't work :)
[18:44] <GunnarHj> bschaefer: auto is in effect the same as setting ibus explicitly.
[18:45] <bschaefer> which is fine for most people who don't use ibus but...as soon as we set auto, g-s-d will no longer hide that icon
[18:45] <bschaefer> when auto is set, ibus will become the default im-config, causing g-s-d to not start the ibus-daemon with --panel disable, as it will be started with upstart
[18:45] <GunnarHj> bschaefer: That's not what I found yesterday.
[18:46] <bschaefer> really?
[18:46] <bschaefer> GunnarHj, hmm as soon as you start auto, upstart should start ibus-daemon from the im-config right?
[18:46] <bschaefer> which should cause the ibus-daemon to not start with --panel disable
[18:47] <GunnarHj> bschaefer: I think so. It's my understanding that g-s-d restarts the ibus-daemon if it's started already. It uses also the --replace argument.
[18:47] <bschaefer> hmm but it shouldn't start ibus if its already started, as I had no problem with ibus when i set im-config -n ibus
[18:47] <bschaefer> and it wasn't getting replaced by g-s-d
[18:48] <bschaefer> GunnarHj, let me re-log and test this auto im-config
[18:48] <bschaefer> GunnarHj, 1000     15607  2.3  0.0 352876  4212 ?        Ssl  11:48   0:00 /usr/bin/ibus-daemon --daemonize --xim
[18:49] <bschaefer> no --panel disable
[18:49] <bschaefer> which means its not being started by g-s-d
[18:49] <GunnarHj> bschaefer: Hmm... Do you see the ibus icon?
[18:49] <bschaefer> i don't actually know what the ibus icon is :)
[18:50] <bschaefer> GunnarHj, i don't think i've ever seen that icon...
[18:50] <GunnarHj> bschaefer: It's an additional icon at the top bar that looks like a keyboard layout icon.
[18:51] <bschaefer> right, i've seen the fcitx one...but i never get the ibus one
[18:51] <bschaefer> GunnarHj, let me set im-config -n ibus
[18:51] <bschaefer> but I don't think it'll start that layout...
[18:51] <bschaefer> as right now im on auto, and ibus started up fine
[18:57] <GunnarHj> bschaefer: It just struck me ... If g-s-d doesn't start im-config if it's already started, the --panel disable option is not the reason why the ibus icon does not show up.
[18:57] <bschaefer> GunnarHj, thats what it looks like to me...
[18:57] <bschaefer> as upstart/im-config is starting up the ibus-daemon for me
[18:58] <bschaefer> and i don't see the ibus panel :(
[18:58] <bschaefer> but ibus works :)
[18:58] <bschaefer> 您好
[18:58] <GunnarHj> bschaefer: And in that case there may be a more serious problem in the derivatives that don't use g-c-c, because there the IM users *need* the ibus icon.
[18:58] <bschaefer> GunnarHj, very true! I just never thought to look for that panel...
[18:58] <bschaefer> as i use ibus-setup when I change things...
[18:59] <GunnarHj> bschaefer: I see.
[19:00] <bschaefer> hmm
[19:00] <GunnarHj> bschaefer: But calling ibus-setup is less convenient than clicking the icon.
[19:00] <bschaefer> GunnarHj, so who is disabling it?
[19:00] <bschaefer> GunnarHj, well I just use ibus-setup to set my IMs from there, I just use super+space to change the IM
[19:00] <bschaefer> and if you hold super+space you get a nice little switcher
[19:00] <GunnarHj> bschaefer: Don't know. Possible it's a ibus 1.5 thing.
[19:00] <bschaefer> GunnarHj, also note, i don't use ibus regularly ...
[19:01] <GunnarHj> bschaefer: Neither do I. I don't know any language that need it.
[19:01] <bschaefer> GunnarHj, yeah, which makes missing things like this easy...as we dont use it often... soo
[19:01] <bschaefer> what is that --panel disable there? If that update came out about the same time ibus 1.5 came out?
[19:02] <bschaefer> GunnarHj, well good news...since that panel is broken we can just set auto to all the *Ubuntus :)
[19:03] <GunnarHj> bschaefer: That may be the short-term conclusion, yes. ;-)
[19:03] <bschaefer> yeah, im going to try to find what the panel is called and try to find its bin...
[19:04] <GunnarHj> bschaefer: But I think I'll install e.g. Lubuntu to see what things look like there.
[19:04] <bschaefer> GunnarHj, if you've the time for that, that wouldn't be a bad idea. If theres a way to check what their default install looks like as well...
[19:04] <bschaefer> we can parse through it to check what they'll have by default
[19:04] <GunnarHj> bschaefer: Right.
[19:10] <seb128> bschaefer, GunnarHj: seems like a busy discussion :/
[19:10] <bschaefer> seb128, much, turns out we can't get the ibus panel to show up when it should :(
[19:10] <seb128> what were we doing before, and can we get back to that?
[19:11] <bschaefer> seb128, i've no clue, i never really use ibus so im not sure where the problem was introduced...
[19:11] <bschaefer> only use it when things are breaking :)
[19:12] <seb128> :-(
[19:12] <bschaefer> seb128, im trying to find the ibus panel where ever it is...to see if I can run it to get some sort of error...
[19:12] <seb128> bschaefer, ibus-setup you mean?
[19:12] <bschaefer> seb128, well the panel that should be on the top right?
[19:12] <bschaefer> that icon you can click? Thats what im talking about :)
[19:13] <bschaefer> and my Show icon on system tray is checked
[19:13] <seb128> that's an indicator provided by ibus-daemon no?
[19:13] <bschaefer> you would think...im digging through the ibus-setup source to see what happens when you check the system tray
[19:13] <bschaefer> thing which should start that ibus indicator...you would think...
[19:14] <seb128> shrug
[19:14] <seb128> https://launchpad.net/ubuntu/+source/ibus/1.5.3-0ubuntu1
[19:14] <seb128> we dropped the ibus indicator patch it seems
[19:14] <bschaefer> o...
[19:14] <seb128> to we still have any ibus UI?
[19:14] <bschaefer> well that explains that...
[19:14] <seb128>   * Dropped changes:
[19:14] <seb128>     - debian/patches/05_appindicator.patch and python-appindicator recommends:
[19:14] <seb128>       + For Saucy, we'll be using indicator-keyboard instead.
[19:14] <bschaefer> seb128, yeah the i-keyboard still work IIRC...with ibus
[19:15] <bschaefer> seb128, which brings me back to the orig problem we were looking at...
[19:15] <bschaefer> why do we have --panel disable?
[19:15] <bschaefer> if its already disabled?
[19:15] <seb128> that's a good question, and I've no idea
[19:15] <bschaefer> seb128, yeah...neither do i :)
[19:15] <seb128> it might be for preventing the notification area icon to show
[19:15] <seb128> but since we don't display those...
[19:15] <bschaefer> seb128, yeah, i set im-config to ibus and no new icons are up there
[19:16] <seb128> bschaefer, so what you are saying is that putting ibus in auto is not going to have an UI impact on the user experience?
[19:16] <bschaefer> seb128, soo im more then happier now to just set im-config to auto
[19:16] <bschaefer> seb128, that is what im saying :)
[19:16] <seb128> how do I set it to auto?
[19:16] <seb128> I want to try that to confirm it
[19:16] <bschaefer> GunnarHj, is going to do that
[19:16] <GunnarHj> seb128: The ibus icon i showing fine in 13.04 when ibus is started via im-config. It's not showing in 13.10, which i fine since we have the Text Entry tab now. However, in the derivatives that don't use g-c-c it's highly desirable that the ibus icon keeps showing up.
[19:16] <bschaefer> right
[19:17] <seb128> GunnarHj, they have support for the notification area though, right?
[19:17] <seb128> (I think only unity dropped that)
[19:17] <bschaefer> seb128, so the problem we are running into is we need to set auto, but only for distros that use g-c-c
[19:17] <GunnarHj> seb128: I don't know. That's one reason I want to install and test one of them.
[19:17] <seb128> bschaefer, why? what would happen for others?
[19:18] <bschaefer> well that ibus icon would always be visible if they install ibus by default
[19:18] <bschaefer> but im not sure if they do...
[19:18] <bschaefer> well..
[19:18] <seb128> bschaefer, that's easy, we have a pile of packages that do (if XDG_CURRENT_DESKTOP="Unity"; then show_unity_ui)
[19:18] <bschaefer> seb128, sweet, GunnarHj ^
[19:18] <seb128> let's do that as well
[19:18] <bschaefer> seb128, thats why we were pinging you mostly :)
[19:18] <seb128> that's what we use to display e.g the unity launcher controls
[19:18] <seb128> haha
[19:18] <bschaefer> :)
[19:19] <bschaefer> awesome, yeah i've not messed with packages that could cause problems in other distros before :)
[19:19] <GunnarHj> seb128, bschaefer: I saw that. Does "Unity" include Kylin?
[19:20] <bschaefer> hmm I would think anyone with the unity desktop will get this setting
[19:20] <bschaefer> GunnarHj, so yes, i think they use unity?
[19:20]  * bschaefer checks
[19:20] <bschaefer> GunnarHj, which is fine, as they will be install fcitx
[19:20] <bschaefer> GunnarHj, yup it uses unity
[19:20] <bschaefer> https://wiki.ubuntu.com/UbuntuKylin
[19:21] <GunnarHj> bschaefer: Nice, thanks!
[19:21] <bschaefer> GunnarHj, soo yay, with that auto patch fix, all should be well again :)
[19:21] <seb128> GunnarHj, Kylin uses Unity but they don't install ibus (they use fcitx)
[19:22] <bschaefer> which auto works perfectly for that :)
[19:22] <seb128> GunnarHj, bschaefer: they don't even install ibus, so that shouldn't be an issue
[19:23] <GunnarHj> seb128: Have they integrated fcitx into the Text Entry tab then?
[19:23] <bschaefer> hopefully g-s-d doesn't have they same problem with Text Entry then
[19:23] <bschaefer> i mean them
[19:23] <seb128> GunnarHj, I don't think so, but that's not going to be a new issue from those changes
[19:23] <bschaefer> cool
[19:24] <GunnarHj> seb128: Do you mean that they use Text Entry for traditional keyboard layout only?
[19:25] <seb128> GunnarHj, I don't know what they are doing, basically they take Unity, remove ibus, install fcitx
[19:25] <bschaefer> GunnarHj, well fcitx has its own icon indicator
[19:25] <seb128> GunnarHj, they might just use the fcitx control and have a non working g-c-c UI
[19:25] <GunnarHj> bschaefer: Yes, I know.
[19:25] <GunnarHj> seb128: Ok. But as you said, it's unrelated to the default change we discuss now.
[19:26] <bschaefer> GunnarHj, sorry, was mostly thinking out loud
[19:28] <GunnarHj> seb128, bschaefer: Since we are so late in the cycle, I think it's time to write an MP. I'll do that by tomorrow.
[19:29] <seb128> GunnarHj, thanks
[19:34] <bschaefer> GunnarHj, awesome, thanks!