[00:32] <duffydack> hmm http://aeric.poon.my/?p=496   might mean something to someone.
[01:14] <dnielsen> ajmitch, I apologize for the delay https://bugzilla.gnome.org/show_bug.cgi?id=626962
[01:14] <ubot4> Gnome bug 626962 in Community Extensions "Ubuntu One Music Store extension fails to build" [Normal,Resolved: notgnome]
[14:20] <Chipaca> apachelogger: nessita: rodrigo_: ping
[14:21] <apachelogger> Chipaca: ahoy
[14:22] <nessita> Chipaca: pong
[14:23] <Chipaca> nessita: rodrigo_:
 nessita, verterok: any objections against uploading my gsoc KDE stuff to universe for maverick?
[14:23] <Chipaca>  (that is if it gets a FFe)
[14:23] <Chipaca> I wanted to check apachelogger was working with all the latest bugfixes
[14:23] <verterok> Chipaca: +1
[14:24] <nessita> Chipaca: I'm not aware of what apachelogger has been working on
[14:24] <rodrigo_> apachelogger, what does that include?
[14:24] <nessita> besides "KDE" :-)
[14:24] <Chipaca> nessita: quite. So, talk with him :)
[14:24] <verterok> Chipaca: we need to be sure about the sso dbus signals :)
[14:24] <apachelogger> http://apachelog.wordpress.com/2010/08/21/ubuntu-one-technical-aspects/
[14:24] <rodrigo_> apachelogger, remember the kwallet patch you submitted is going to be removed in the next upload (today), so you might want to make sure you add that to ubuntu-sso-client
[14:25] <apachelogger> do I have something to patch against?
[14:25] <apachelogger> seeing as my patch was rejected due to sso being in a constant state of flux
[14:25] <Chipaca> apachelogger: also note we can't merge your patch upstream until you sign the canonical contributor agreement (if you want to do that)
[14:25] <rodrigo_> apachelogger, ubuntu-sso-client, should be stable now for you to patch it
[14:27] <rodrigo_> apachelogger, about the UI, we even added DBus interfaces to u-sso-client to allow other UIs to be implemented
[14:28] <apachelogger> Chipaca: last I saw the agreement I got advised not to sign it... so...
[14:28] <Chipaca> apachelogger: by whom?
[14:28] <apachelogger> a lawyer friend of mine
[14:29] <Chipaca> apachelogger: okie then :)
[14:30] <nessita> Chipaca: I'm not sure what you want me to look :-)
[14:30] <nessita> Chipaca: do we have a merge proposal to review?
[14:30] <rodrigo_> nessita, http://apachelog.wordpress.com/2010/08/21/ubuntu-one-technical-aspects/
[14:31] <apachelogger> supposedly we could just use ubuntu-sso-client as is in KDE too?
[14:32] <apachelogger> i.e. only deploy the UI components (based on syncdaemon's dbus interface) in maverick
[14:32] <rodrigo_> apachelogger, there is a low-level DBus interface in u-sso-client that you could use to provide a QT ui
[14:33] <nessita> apachelogger: we provide a DBus interface and you could build a KDE GUI on top of that
[14:33] <rodrigo_> apachelogger, we added that in fact based on your needs to have a QT UI
[14:33] <Chipaca> nessita: so... I'm not sure what apachelogger's current work entails, but I thought the easiest way to get him an answer as to whether it should/could go in universe.
[14:33] <nessita> apachelogger: let me give you a pointer
[14:33] <Chipaca> nessita: or rather, I'm pretty sure it shouldn't, for the reasons I think you're explaining (that I already explained), but you could get into more detail than i can
[14:33] <nessita> alecu: do you have the wiki pointer for ussoc?
[14:34] <apachelogger> nessita: do we need to create a Qt UI on top of it?
[14:35] <alecu> nessita, yes... just a sec.
[14:35]  * apachelogger finds it unlikely to roll out a somewhat stable UI in time to accumulate testing for maverick
[14:35] <Chipaca> apachelogger: what we could do is split ubuntu-sso-client into ubuntu-sso-client and ubuntu-sso-client-gtk, and you patch the former and replace the latter with -qt
[14:36] <nessita> Chipaca: the latter you meant?
[14:36] <Chipaca> nessita: patch the former to also use kwallet
[14:36] <nessita> ah
[14:36] <nessita> :-)
[14:36] <alecu> https://wiki.ubuntu.com/SingleSignOn/UbuntuSsoClient
[14:37] <alecu> nessita, but that's the doc for programs that need credentials
[14:37] <nessita> apachelogger: ok, the link that alecu pasted shows the high level DBUS interface. I forgot we haven't documented yet the "low-level" interface that the GUI's use
[14:38] <alecu> nessita, yup, we still need to write the docs for someone wanting to login/register
[14:38] <alecu> * to make a login/register ui
[14:39] <nessita> apachelogger: so, basically, SSO provides a DBUS service with 2 main interfaces: the Credentials which is what we call "high level" (apps like syncdaemon use them)
[14:39] <nessita> apachelogger: and the UserManagement, which is a lower level interface, that is used by the GTK GUI
[14:40] <nessita> apachelogger: and that any other interface (let's say, KDE), can use to provide the same functionality
[14:57] <rye> nessita, hi, i wanted to ask what is the correct way for up-to-date maverick system to authorize the machine. In my case a browser window is opened when I run ubuntuone-preferences, should it be this way or I should get a GUI for that?
[14:58] <apachelogger> nessita: sso-client package misses recommends on gnome-keyring
[14:58] <nessita> rye: we're landing the latests versions for everything, do you have trunk for all?
[14:58] <nessita> apachelogger: why should it recommend it?
[14:59] <apachelogger> nessita: because you only support gnome-keyring
[15:00] <nessita> apachelogger: we have the requirement of python-keyring, which requires gnome-keyring
[15:00] <nessita> apachelogger: so I don't understand why we need to "recommed" gnome-keyring being that we need it to work (at least the current version)
[15:00] <apachelogger> me@osiris:~$ apt-cache show python-gnomekeyring|grep gnome-keyring
[15:00] <apachelogger> Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.12.0), libgnome-keyring0 (>= 2.20.3), python (<< 2.7), python (>= 2.6), python-support (>= 0.90.0), python-gtk2
[15:00] <apachelogger> Suggests: gnome-keyring
[15:00] <apachelogger> I beg to differ
[15:01] <nessita> Chipaca: what was the command you taught me to see package dependencies?
[15:01] <Chipaca> nessita: apt-get rdepends?
[15:01] <nessita> let's see
[15:02] <Chipaca> nessita: or apt-cache putty :)
[15:02] <Chipaca> not putty, dotty
[15:02] <Chipaca> off-by-180
[15:02] <apachelogger> rdepends has a misleading name, it lists reverse relations rather than depends in particular BTW
[15:03] <nessita> Chipaca: E: Invalid operation (for rdepends) :-)
[15:03] <apachelogger> nessita: apt-cache, not get :P
[15:03] <nessita> apachelogger: "libgnome-keyring0" -> "gnome-keyring";
[15:03] <nessita> apachelogger: so, "python-gnomekeyring" -> "libgnome-keyring0"; and "libgnome-keyring0" -> "gnome-keyring";
[15:04] <nessita> apachelogger: we do depend on gnome-keyring :-)
[15:04] <apachelogger> me@osiris:~$ apt-cache show libgnome-keyring0 | grep gnome-keyring | grep -v libgnome
[15:04] <apachelogger> Suggests: gnome-keyring
[15:04] <apachelogger> Breaks: gnome-keyring (<< 2.30)
[15:04] <apachelogger> I again beg to differ
[15:05] <nessita> apachelogger: what I showed you is the output of apt-cache dotty python-gnomekeyring
[15:05] <apachelogger> dotty also tracks relations and not dependencies in particular
[15:06] <nessita> apachelogger: I'm new at packaging, so I probably made a mistake (or ten), but honestly I'm not convinced of this
[15:06] <nessita> apachelogger: how come python-gnomekeyring does not depend of gnome-keyring? that sounds weird
[15:07] <apachelogger> because it only depends on the library and the library only suggest gnome-keyring
[15:07] <apachelogger> I am sure there is a reason for that
[15:07] <apachelogger> but why exactly you will have to ask someone who has to do with those packages
[15:07] <apachelogger> not exactly my area of work either :P
[15:09] <nessita> heh
[15:26] <nessita> rye: hey, you never answered
[15:28] <rye> nessita, i am running bleading-edge maverick , not the version from trunk
[15:52] <rodrigo_> anyone knows about glibc brokenness on latest maverick packages? I seem to be having weird memory corruption bugs, and after 1 hour looking at my code, it doesn't seem to be my fault
[16:06] <rye> rodrigo_, are you talking about nautilus plugin?
[16:07] <rodrigo_> rye, I am talking about a nautilus plugin branch I'm working on, yes
[16:08] <rodrigo_> it's segfaulting on a g_free call
[16:11] <rye> rodrigo_, related to _CBData ?
[16:12] <rodrigo_> rye, no
[16:12] <rodrigo_> rye, it's crashing here:
[16:12] <rodrigo_> if (finfo->priv->path != NULL)
[16:12] <rodrigo_> 		g_free (finfo->priv->path);
[16:13] <rye> rodrigo_, is finfo->priv != NULL ?
[16:13] <rodrigo_> rye, it should, yes
[16:14] <rodrigo_> it's crashing on the g_free
[16:23] <rodrigo_> aha, I found it!!
[16:24] <rodrigo_> stupid copy&paste
[16:52] <rodrigo_> alecu, nessita, Chipaca: https://code.edge.launchpad.net/~rodrigo-moya/ubuntuone-client/check-published-files/+merge/33660
[17:13] <alecu> rodrigo_, reviewing your branch
[17:26] <apachelogger> nessitalunch: I am getting a segfault with ubuntu-sso-client
[17:32] <trichard> hey, is there any way to see which file ubuntuone is syncing at the moment?
[18:39] <nessita> apachelogger: can you please be more specific? :-)
[18:45] <apachelogger> nessita: trying to login -> backend goes down with segfault
[18:45] <nessita> apachelogger: how are you trying to login?
[18:45] <apachelogger> last log entry: 2010-08-25 18:26:15,602:602.580070496 ubuntu_sso.main keyring_store_credentials: app_name dbus.String(u'Ubuntu').
[18:45] <apachelogger> nessita: using the GTK UI
[18:45] <nessita> apachelogger: how are you running the GTK UI?
[18:46] <apachelogger> from terminal without args
[18:46] <nessita> apachelogger: you're having a mismatch between the version of the UI and the version of the daemon
[18:47] <nessita> be sure you're running both from the same branch
[18:47] <apachelogger> I am running from the packages
[18:47] <nessita> apachelogger: you shouldn't be running the GUI other than from a dbus call
[18:47] <nessita> apachelogger: can you paste how are you running the GUI?
[18:47] <nessita> the exact command
[18:48] <apachelogger> me@osiris:~$ ubuntu-sso-login-gui
[18:48] <apachelogger> and in another tab
[18:48] <apachelogger> me@osiris:~$ /usr/lib/ubuntu-sso-client/ubuntu-sso-login
[18:49] <nessita> apachelogger: where are you getting the  ubuntu-sso-login-gui from? is not shipped in the package
[18:49] <nessita> apachelogger: that script is not supported (just FYI)
[18:49] <nessita> apachelogger: we will be removing it soon
[18:50] <apachelogger> me@osiris:~$ dpkg -L ubuntu-sso-client | grep login-gui
[18:50] <apachelogger> /usr/bin/ubuntu-sso-login-gui
[18:50] <apachelogger> it is shipped in the package
[18:51] <nessita> apachelogger: it shouldn't be, I'll file a bug. Thanks for pointing this out!
[18:51] <apachelogger> nessita: how should one be starting the gui?
[18:51] <nessita> apachelogger: anyways, you should raise the GUI using Dbus
[18:51] <nessita> apachelogger: use d-feet or something similar to call the dbus method
[18:52] <nessita> apachelogger: the methods you want are in the Credentials interface. Either "login_or_register_to_get_credentials" or "login_to..."
[18:52] <apachelogger> k
[19:00] <apachelogger> nessita: http://paste.ubuntu.com/483561/
[19:00] <nessita> apachelogger: you don't have the gnome keyring available
[19:01] <nessita> apachelogger: I'm a bit lost what your question is
[19:01] <apachelogger> what part is supposed to create it though?
[19:01] <nessita> apachelogger: the keyring is a dbus service
[19:01]  * apachelogger has a default keyring, it just seems that it falls over not having a login keyring
[19:01] <nessita> alecu: look ^
[19:01] <apachelogger> me@osiris:~$ qdbus org.gnome.keyring
[19:02] <apachelogger> /
[19:02] <apachelogger> gnome keyring is there
[19:02] <nessita> apachelogger: ah yes, sorry
[19:02] <apachelogger> also in seahorse I can access it properly
[19:02] <nessita> apachelogger: I'm just passing this to al
[19:02] <nessita> alecu*
[19:02] <apachelogger> aye
[19:02] <nessita> apachelogger: we have a bug reported for that
[19:02] <alecu> I'm about to start working on this issue, yes
[19:03] <apachelogger> simply creating a login keyring should suffice to work around it?
[19:03] <alecu> it's #624033
[19:03]  * apachelogger finds "login" a bit of a generic name TBH
[19:03] <nessita> apachelogger: not sure, let the master answer
[19:04] <apachelogger> nessita: segfault again
[19:04] <apachelogger> last line of log: 2010-08-25 20:04:16,309:309.218883514 ubuntu_sso.main keyring_store_credentials: app_name dbus.String(u'ubuntuone-syncdaemon').
[19:05] <nessita> apachelogger: may be related to not having the keyring available?
[19:05] <apachelogger> I created one :P
[19:05] <nessita> hum
[19:05] <apachelogger> that is after I obtained a token
[19:05] <nessita> apachelogger: just FYI, app_name should be "Ubuntu One", which is a constant defined in ubuntuone.clientdefs
[19:05] <nessita> apachelogger: so the token actually works with syncdaemon
[19:06] <apachelogger> k
[19:06] <apachelogger> well, since it crashes anyway... ;)
[19:07] <alecu> apachelogger, "login" is the keyring that's automatically unlocked by some pam module using your login in password when you have just logged in with gdm.
[19:07] <apachelogger> alecu: I c
[19:07] <apachelogger> that is bound to fail on KDE systems
[19:07] <apachelogger> or you are missing a dep for that
[19:08] <alecu> apachelogger, which dep do you think might solve this?
[19:08] <apachelogger> dunno
[19:08] <apachelogger> I never heared of such a pam module before
[19:09] <alecu> apachelogger, also it's failing on some gnome systems that have a keyring named "default" but no "login" keyring.
[19:09] <alecu> apachelogger, it's lib-pam-gnomekeyring
[19:10] <apachelogger> installed
[19:10] <apachelogger> http://live.gnome.org/GnomeKeyring/Pam
[19:10] <apachelogger> login gets created if not present
[19:10] <apachelogger> but it seems KDM will not include the PAM module
[19:11] <apachelogger> (which IIRC was also the problem that early on lucid was not able to start gnome-keyring in KDE - in GNOME it did get autostarted frome the module but in KDE not)
[19:11] <rodrigo_> apachelogger, I think that's your pam setup, nothing to do with kdm
[19:11] <rodrigo_> but yeah, you'd need gnome-keyring autostarted
[19:16] <apachelogger> me@osiris:/etc/pam.d$ grep -ri gnome_key .
[19:16] <apachelogger> ./common-password:password      optional        pam_gnome_keyring.so
[19:16] <apachelogger> no autostart -> no login keyring
[19:17] <apachelogger> alecu: I would check for existance of the keyring and if not manually create it
[19:46] <kklimonda> rye: any chance I'll get access to my contacts before I get old and wrinkled? ;)
[20:09] <ajmitch> rodrigo_: so you've managed to track down how to fix up the mono bindings?
[20:10]  * ajmitch was looking for a fix yesterday for it
[20:13] <apachelogger> nessita: want me to get a backtrace?
[20:14] <rodrigo_> ajmitch, not yet, busy with other stuff, but will look at it soon
[20:19] <nessita> apachelogger: for the segfaulting? yes please
[20:20] <nessita> apachelogger: also, you're running kde, right? (just to know)
[20:21] <ajmitch> rodrigo_: ok, you'll probably end up cursing gapi2-codegen's lack of useful output as I did :)
[20:23] <apachelogger> nessita: yes, I am running KDE
[20:24] <rodrigo_> ajmitch, yeah :(
[20:25] <rodrigo_> ajmitch, only output I get is something about not knowing what GtkVBoxClass is
[20:25] <rodrigo_> ajmitch, do you get the same?
[20:25] <ajmitch> yep
[20:25] <ajmitch> adding in the syncdaemon header header into ubuntuone.source generated C# files for at least that part, but still no useful u1ms code
[20:25] <ajmitch> & it of course failed to compile, not unsurprising
[20:27] <ajmitch> apparantly the gapi stuff hasn't seen a lot of love recently
[20:31] <rodrigo_> ajmitch, it used to work ok, and there have been no changes, so not sure what's up
[20:32] <ajmitch> the only code changes to the u1ms widget recently have been adding in the syncdaemon support, but I'm not sure how that should affect it
[20:32] <apachelogger> nessita: http://paste.ubuntu.com/483608/
[20:33] <ajmitch> diving into the gapi code to get some useful answers takes a little while
[20:33] <rodrigo_> ajmitch, in fact, it started happening when I removed the previous files that were talking to syncdaemon, to replace them with libsyncdaemon
[20:33] <rodrigo_> ajmitch, so not sure what doesn't make gapi happy
[20:33] <ajmitch> the previous code didn't link to an external library (libsyncdaemon)?
[20:34] <ajmitch> it would seem rather strange if you did need to have any information about libsyncdaemon in the code for gapi to look at
[20:35] <rodrigo_> hmm
[20:35] <rodrigo_> but it's just internal usage, not in the headers it is supposed to be parsing
[20:35] <rodrigo_> or does gapi look at the .c files?
[20:36] <ajmitch> the headers afaik
[20:36] <rodrigo_> yeah, that's what I thought
[20:37] <ajmitch> without useful output from the tool this is just speculation really
[20:38] <ajmitch> & frustrating at that :)
[20:38] <rodrigo_> Field ParentClass has unknown Type GtkVBoxClass in Struct UbuntuOne.U1MusicStoreClass
[20:38] <rodrigo_> yeah, that's the only thing I get
[20:39] <ajmitch> that's boilerplate widget code you've got there too
[20:39] <rodrigo_> but I guess he should know UbuntuOne.U1MusicStoreClass is a GTK class struct
[20:39] <nessita> apachelogger: I have no idea what's going on there, seems like a dbus issue
[20:39] <nessita> apachelogger: maybe you have a too old/ too new dbus?
[20:39] <nessita> apachelogger: maybe gnomekeyring depends on a different dbus than the one that kde provides?
[20:40] <apachelogger> there is only one dbus
[20:40] <apachelogger> so either what is currently in maverick is broken or it is something else
[20:40] <nessita> apachelogger: what's currently in maverick is working on gnome desktops
[20:40] <nessita> apachelogger: do you have a gnome VM? maybe you can try there and see if it fails for you
[20:42] <apachelogger> dont have one around
[20:42] <rodrigo_> ajmitch, well, that's the usual boilerplate for GTK widgets, so I'd assume gapi knows about it
[20:48]  * ajmitch shall have to get back to it later
[20:51] <rodrigo_> ajmitch, in /usr/share/gapi-2.0/gtk-api.xml, there is no Gtk*Class at all, so not sure why it tries to parse the music store one :(
[20:52] <ajmitch> or more, why did it work up until now/
[20:53]  * ajmitch will be back later
[20:57]  * apachelogger pokes his dbus with a long pointy stick of fluff
[21:53] <rodrigo_> apachelogger, I just removed your kwallet patch from the u1-client package, since it didn't apply anymore
[21:54] <rodrigo_> ajmitch, for when you get back, I've succeeded in not having the GtkVBoxClass warning, but still doesn't create any .cs files
[21:54]  * ajmitch is around now
[21:54] <ajmitch> so that warning may have been somewhat spurious?
[21:55] <ajmitch> fwiw, I can get a U1MusicStoreClass.cs created by commenting out the line that refers to parent_class in the .xml file
[21:55] <rodrigo_> ajmitch, unfortunately, seems so
[21:55] <ajmitch> I haven't checked to see if the assembly that is created is at all useful though
[21:56] <rodrigo_> ajmitch, hmm, maybe we can mark it to be removed on the ubuntuone-api.metadata file
[21:56] <rodrigo_> let me try...
[21:56] <ajmitch> that would probably remove it, but I don't know if it should be
[21:56] <ajmitch> worth a try
[21:58] <rodrigo_> no, no luck :(
[21:58] <apachelogger> rodrigo_: cruel world
[21:59] <rodrigo_> apachelogger, patch ubuntu-sso-client, as you talked with nessita
[22:08] <apachelogger> http://simplest-image-hosting.net/jpg-0-plasma-desktoplm3446
[22:09] <rodrigo_> ajmitch, so, you get something in ubuntuone-api.xml?
[22:09] <rodrigo_> ajmitch, right now, I get it empty
[22:10] <ajmitch> rodrigo_: empty after changing what?
[22:10] <ajmitch> at the moment I'm rebuilding the previous libubuntuone in a chroot to have a look at it
[22:10] <rodrigo_> ajmitch, empty when it gets generated
[22:10] <rodrigo_> ajmitch, ok
[22:15] <ajmitch> assuming that pbuilder will cooperate & let me into the chroot after it built
[22:15] <ajmitch> but I can at least see that the gapi2-codegen output is different in the build log
[22:15]  * ajmitch just needs to look at the xml file
[22:19] <rodrigo_> ajmitch, I'm looking at the gtk-sharp package, to see if anything changed there
[22:19] <ajmitch> nothing has changed there
[22:20] <rodrigo_> ah, you checked already?
[22:20] <ajmitch> it hasn't changed for quite awhile (last upload 14 weeks ago)
[22:21] <ajmitch> yeah, I've been complaining about the gapi stuff in the debian mono channel as well :)
[22:21] <rodrigo_> ok
[22:25]  * ajmitch is wanting to get this as working as possible before uploading to debian experimental
[22:40]  * ajmitch wonders why the ubuntuone-api.xml file is so very different between the 2 releases
[22:40] <ajmitch> in 0.3.2, it has object name="U1MusicStore", and in 0.3.3 it only gets the struct name="U1MusicStoreClass"
[22:41] <apachelogger> nessita: the gui uses gobject signals?
[22:41] <ajmitch> yet more evidence that gapi is just crap :)
[22:45] <dobey> eh, let's just rewrite it all in vala, and not provide any bindings to anything ;)
[22:45] <ajmitch> dobey: can you get it done by next week? :)
[22:46] <nessita>  apachelogger: yes
[22:48] <dobey> sure, but i don't measure time in earth days, so one week is actually 3 years in earth time, for me ;)
[22:56] <ajmitch> dobey: we were just discussing how it'd be nice to use gobject introspection for mono bindings, if you have a free evening to work on it :)
[22:59] <dobey> me and mono don't mix well
[23:02] <ajmitch> it was worth a try
[23:03] <ajmitch> don't worry, the gapi code that parses C at the moment is written in perl, which is such an improvement
[23:07] <apachelogger> nessita: why not dbus?
[23:07] <dobey> eh, i like perl
[23:08] <nessita> apachelogger: the GUI part is not a dbus service, is just a plain GTK interface, so it signals thru gobject
[23:09] <apachelogger> nessita: but the backend is a dbus service so the gui could just call a method of the backend's dbus api
[23:13] <nessita> apachelogger: yeah, propably. We didn't design it that way, we should be able to re-think that for the next cycle