[00:13] <lindol> hi all
[00:16] <octoquad> darkxst, any updates for this: https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749
[02:07] <darkxst> octoquad, I know the cause, but haven't had a chance to look into it
[02:08] <darkxst> octoquad, bug 1385572
[02:09] <darkxst> and it will go away anyway, once we are switched to systemd init
[02:28] <darkxst> but does need to be fixed for trusty
[02:35] <darkxst> Noskcaj, can you rebuild g-s-d so I can test your ppa?
[02:38] <darkxst> Noskcaj, and it would possibly better to use a team ppa for these transition type things ubuntu-gnome-packaging perhaps? you should be able to make ppa's there!
[04:38] <Noskcaj> darkxst, Yes, i should have used a team ppa. Rebuilding now
[06:00] <darkxst> Noskcaj, seems to be dependency issues
[06:02] <darkxst> Noskcaj, oh gnome-backgrounds is stuck in proposed
[06:02] <darkxst> can you copy that to your ppa
[06:02] <darkxst> also gnome-shell-extensions
[06:03] <darkxst> ^also in proposed
[06:11] <darkxst> Noskcaj, no matter, moved everything to ppa:ubuntu-gnome-packaging/core3.14
[06:41] <lindol> hi all
[06:43] <lindol> I came to Ubuntu Korea forum in Seoul. :)
[06:47] <darkxst> hi lindol
[06:49] <lindol> darkxst, hi :)
[06:52] <darkxst> lindol, how is the forum?
[06:54] <lindol> Ubuntu Korea forum is Ubuntu Community for Korea in Repulbic of Korea (South Korea)
[06:55] <darkxst> any other of our crew there?
[06:57] <lindol> No any one, Sorry.
[07:01] <darkxst> maybe they are hiding (though I don't know if we have any other Korean members ;) )
[07:16] <LinDol_phone> sorry.  My computer was disconnect. no any one. Sorry I just talked it.
[07:18] <LinDol_phone> darkxst, Sorry
[07:18] <darkxst> LinDol_phone, ok
[12:16] <octoquad> There doesn't seem to be any builds for the yesterday and today. Is there a problem again?
[15:33] <superdingus> Hello. Having trouble with keyrings/seahorse
[15:34] <octoquad> Hello superdingus. What problem are you having?
[15:34] <superdingus> Sorry if I take long to explain. See, I have autologin set to off
[15:34] <superdingus> And each time when I log in, I must also unlock a keyring (empathy wants access for my chat accounts)
[15:35] <superdingus> I then set the keyring to automatically unlock when I log in, since they have the same password
[15:36] <superdingus> Instead of logging in manually and having the keyring unlocked automatically, I am forcibly autologged in, and met with the same "unlock keyring" prompt
[15:36] <superdingus> The issue is that I cannot seem to set the behavior to what I expected
[15:37] <octoquad> What version of Ubuntu Gnome are you using? 14.04 or 14.10?
[15:38] <superdingus> 14.10
[15:38] <octoquad> ok
[15:39] <octoquad> Was this an upgrade from 14.04 to 14.10?
[15:39] <superdingus> Nope, a fresh install
[15:39] <octoquad> ok
[15:40] <superdingus> may be worth noting that in config, autologin is still shown as set to off, despite this latest behavior change
[15:41] <octoquad> are using stock 14.10 or do you have either the main or main and staging ppa's enabled?
[15:41] <octoquad> I've had this problem before, but in another release
[15:42] <octoquad> Have you tried resetting your password for you login?
[15:42] <octoquad> *your
[15:44] <superdingus> stock 14.10, no additional PPA's enabled at all
[15:44] <superdingus> I can try resetting the password now, should I reset password for the login and keyring at same time?
[15:45] <octoquad> ok, yes, please change your password to something else and log out and log in again. If it still asks for a password for the keyring change the password again for the user account and for the keyring at the same time and log out and log in again.
[15:46] <superdingus> Alright thank you, will try that now
[15:57] <superdingus_> No go, tried resetting each password seperately, to no avail
[15:57] <superdingus_> keeps bypassing my login
[16:08] <octoquad> interesting so the user account and for login under seahorse are exactly the same?
[16:09] <octoquad> is login also set to default?
[16:09] <octoquad> in seahorse
[16:11] <octoquad> sorry I meant: interesting so the password for the user account and for login under seahorse are exactly the same?
[16:12] <octoquad> brb
[16:24] <superdingus_> sorry. Yes, the passwords are the exact same, and login is set to default in seahorse
[16:25] <superdingus_> Should I just destroy the old keyring and force empathy to generate new keyring under default (which is now login)?
[16:26] <octoquad> superdingus_, yes you can try that as well.
[16:27] <superdingus_> giving that a shot now
[19:13] <x00e> Hello
[19:16] <x00e> is it safe to add gnome3 staging ppa ?
[20:06] <Noskcaj> darkxst, I'm going to be away for the next week. Anything i should do before i leave? (lunchtime)
[20:06] <darkxst> Noskcaj, did you file MP's for 3.14 updates?
[20:07] <Noskcaj> I'd just left everything on the bug. Should i be filing MPs even though geoclue-2.0 isn't actually in main yet?
[20:08] <darkxst> Noskcaj, yes
[20:08] <Noskcaj> ok
[20:08] <darkxst> once an upload depends on geoclue it will get promoted
[20:19] <darkxst> Noskcaj, https://launchpadlibrarian.net/193116367/gnome-settings-daemon_3.14.2-2ubuntu1~ppa1_3.14.2-2ubuntu1~ppa3.diff.gz
[20:20] <Noskcaj> ok
[20:37] <darkxst> Noskcaj, g-c-c can drop the zoom patch
[20:40] <darkxst> Noskcaj, you should use --author when merge other peoples diff's ;0
[20:41] <Noskcaj> I just copied stuff from what was in the diff, but ok
[20:47] <darkxst> ok, everything else looks fine
[21:05] <darkxst> Noskcaj, if you have time, epiphany needs a merge
[21:06] <darkxst> (there is a headerbar patch on ppa)
[21:06] <Noskcaj> ok
[21:06] <darkxst> and empathy should enable geoclue-2.0
[21:07] <Noskcaj> i'll see what i can do
[21:09] <Noskcaj> https://code.launchpad.net/~noskcaj/empathy/geoclue-2.0/+merge/241187