=== fta_ is now known as fta [08:49] pitti: hey man, did both of my packages get into the last alpha? (the ones I gave you before leaving for vacation) [08:49] hey kwwii [08:49] kwwii: which versions? (just use "rmadison foo" to check the version of foo in all Ubuntu releases) [08:51] ahh, thanks, now I see it [09:04] seb128: Hey, welcome back [09:05] hello lool, thanks [09:05] seb128: We discussed some desktop bits on Friday [09:05] seb128: (I was the fallback contact for desktop stuff last week as everybody was on vac) [09:05] who is we and which ones exactly? ;-) [09:06] During release meeting [09:06] You might want to read the first part of the log, skipping mobile stuff [09:06] Concerning desktop, gvfsd-trasher crasher and gtk+ screen flicker were discussed [09:07] mdz brought up an old gpm bug [09:07] I've noticed those bugs in the summary [09:07] I mentionned cheese shall be updated [09:07] seb128: I bought a webcam last week [09:07] the gvfsd-trash crasher is not really an issue out of the number of duplicates and I've no clue how to get good informations or fix it [09:08] the gtk+ screen flicker, mclasen consider it as an xorg bug [09:08] seb128: Yeah, me neither, the valgrind log isn't very helpful [09:08] seb128: That said, the valgrind log might be better with more ddebs or something [09:08] no [09:08] seb128: The problem with the screen flicker is that it is a lack of API on the xorg side [09:08] I did get valgrind logs for the trash crasher using a debug build, etc [09:09] there is an incorrect jump listed but the top stacktrace has no symbol [09:09] seb128: So what happened is that gtk+ moved to a new API only to realize that it was too expensive/disruptive [09:09] I don't think it's in my power to fix the xorg api ;-) [09:09] or gtk [09:09] I would rather prefer let upstream sort that [09:09] seb128: Exactly my point, I agree with the analysis that going forward we ought to fix the API [09:10] seb128: But this will be in xrandr 1.3, then all drivers will have to be updated to support it, then gtk+ will be able to use it [09:10] And the new API wasn't yet accepted [09:10] So we're talking of a 3 months minimum cycle here [09:10] (AIUI) [09:10] I'm confident that upstream will do something for FC10 which is due around the intrepid schedule too [09:10] gtk upstream [09:11] so I would just let them sort that [09:11] Ok; I personally think gtk+ should defer using randr's problematic API until it has what they need [09:11] Hey pitti, welcome back! [09:12] pitti: You also might want to poke at the release team meeting's log from friday! :) [09:12] pitti: One of the thing which came up was the consolekit config patch to not allow everybody to shutdown or reboot the machine; this prevents shutdown/reboot from the desktop though [09:13] lool: hey, thanks [09:13] pitti: I guess we should revert to the gdm socket method [09:13] lool: right, either we enable the functionality in CK like upstream, or use gdm [09:13] pitti: Yup; I thought this was your choice to make as you were on top of misc hal/dbus/ck issues and have some security clue [09:14] pitti: I am disturbed too with this shutdown/reboot dbus interface [09:14] lool: I have bug 250506 open in a tab to address it ASAP [09:14] Launchpad bug 250506 in consolekit "shutdown and restart buttons do nothing" [High,Confirmed] https://launchpad.net/bugs/250506 [09:14] That's indeed the one we discussed I think [10:11] morning everyone [10:12] lut huats [10:12] plop seb128 [10:12] I hope you had nice (and deserved) holidays :) [10:14] yes, excellent, thanks ;-) [10:14] :) [10:33] seb128: Since you seem to be lord of all things g-s-d and g-c-c, what do you think of my proposed fixes for bug #207781? [10:33] Launchpad bug 207781 in gnome-settings-daemon "gnome-control-center and gnome-settings-daemon hardcode "Synaptics Touchpad", which breaks without xorg.conf" [Low,Confirmed] https://launchpad.net/bugs/207781 [10:34] wgrant: I've no clue about touchpad so I would prefer let somebody else comment [10:34] wgrant: and apparently there is no patch attached to this bug? [10:35] seb128: That's true, I apparently forgot to attach debdiffs. [10:35] seb128: Who is more qualified? [10:35] you could ask bryce maybe or #ubuntu-x [10:35] OK, will do. Thanks. [10:36] would be nicer to have an xorg api to query that rather than relying on the naming [10:37] My patch relies on the name of a property, but that property is what is used to set things, so it's safe. [10:37] I can't see a better way. [11:25] * NCommander is away: This creature sleeps beyond the reaches of time itself === asac_ is now known as asac [13:45] hey pedro_ [13:45] hey seb128! welcome back ;-) [13:46] thanks ;-) [13:46] pedro_: pitti has started fixing the retracers, that's not perfect yet but the intrepid one should be running again now [13:46] woohoo go pitti ;-) [13:46] seb128: thanks for let me know dude [13:52] seb128: hey [13:52] hello vuntz [13:52] seb128: just wanted to know what were the ubuntu plans for the logout dialog? [13:52] vuntz: I was sort of waiting on you because you told me you were going to land the opensuse dialog upstream but I guess that's not going to happen this cycle now? [13:53] seb128: I hope that http://bugzilla.gnome.org/show_bug.cgi?id=507101 will get committed today, but I'm not sure it's fine for you [13:53] Gnome bug 507101 in general "New UI for logout/shutdown dialogs" [Minor,New] [13:53] seb128: heh. So, it's going to happen really soon now. Just need an icon and a second release team approval [13:53] vuntz: ah excellent [13:54] vuntz: ping those lazy r-t lurkers, ping them to death! [13:55] andre__: waiting for the icon to be ready (I'm making artists work right now ;-)) [13:56] seb128: you can see the screenshots at the end of the bug [13:56] seb128: if you want one dialog with everything, it's possible, but you'll likely need to patch gnome-session (I suggest adding an Ubuntu-specific dbus method for the new dialog) [13:56] vuntz: right, I like the dialog but I've the feeling we will be asked to get a variant listing all the options for ubuntu [13:57] right [14:16] lool: how busy are you nowadays? would you have some time to look at desktop packaging issues? [14:18] seb128: I'm overcommitted, but depends what you're going to ask [14:20] lool: the pygobject update is tricky because they added a library and that doesn't play nicely with the multi python versions, doko started doing the packaging changes required before his holidays but there is a bug and it doesn't build [14:20] lool: I've planned to look at it but I think I'll be swamped with updates and catching up this week so I was trying to see if you were maybe interested by having a look at the update [14:21] seb128: What source version didn't build? [14:21] 2.15.2 [14:21] Where I can get this? [14:21] ("buildd" says 2.15.1-0ubuntu2 and that it built fine) [14:21] lool: http://people.ubuntu.com/~seb128/pygobject/ is the work in progress that doko did [14:21] lool: right, I didn't upload the new one since it's buggy [14:25] lool: you have the version before the changes (which fails to build because there is a conflict on the new lib because python versions) and the doko changes which ftbfs too but for an another reason (not sure which one now, I looked at it before my holidays quickly) [14:25] seb128: Do you know what doko intendend to do? [14:25] He added autoconf and automake bdeps and changed the way the source is built [14:26] Ah I need to rebase on my version it seems [14:26] lool: I think he wanted to version the library name, he said that's similar to what python-svn does [14:31] seb128: Do you know why the library is public instead of being e.g. a python module? [14:31] - Add a new installed library libpyglib-2.0, which contains the extension [14:31] API for third-part modules instead of relying on macros which accesses [14:31] struct fields. [14:31] I'm not quite sure who's going to use it [14:31] There's no .pc file at least [14:32] Hmm there's also public API [14:34] lool: no, better to ask to jdahlin on the gnome IRC [14:34] you already did ;-) [14:40] seb128: the ubuntulooks package was removed from the seed for intrepid, right? [14:41] no clue, but that's public information so you can look as quickly as I can do [14:41] erm, where? [14:41] kwwii: lp:~ubuntu-core-dev/ubuntu-seeds/intrepid or some such [14:42] /platform.intrepid and /ubuntu.intrepid rather [15:48] loic, I've been pointed in your direction for implementing improvements to the codec installation interface. Do you have a few minutes to discuss the current implementation? [15:48] lool, ^^ === emgent is now known as emgent`NL [16:50] mpt: Hmm [16:50] mpt: Sure [16:50] mpt: I might not be the best person depending on what you ask, but I'm happy to discuss this topic [16:52] lool, the window that lists the available codecs looks like a subset of the Add/Remove Programs window, right? How difficult is it to change bits in that window? [16:52] mpt: It's gnome-app-install [16:52] mpt: Indeed, it's built using synaptic IIRC [16:52] which? :-) [16:53] Specifically, the Help button needs removing (currently it does more harm than good in the codec context), and the "Quick Introduction" is a non-sequitur [16:53] mpt: What's the problem with the Help button? [16:54] mpt: When I press it, I land in the "Install and Remove Applications" manual in yelp [16:54] The help it displays is completely irrelevant [16:54] exactly [16:54] It's nothing whatsoever to do with installing codecs [16:55] and whenever that happens it makes people less likely to use help anywhere else [16:56] mpt: Ok, so currently this uses a generic tool, gnome-app-install; you can launch it manually and imagine that it's useful in different scenarii; I fear that if you want to provide help specialied for code installation, you will have to provide some sort of wrapper or derived app which links to that [16:56] It would be nice to have help for it, but we're past FeatureFreeze, so just removing it is probably best for now [16:56] lool, yes, I realize that, that's why I'm asking how difficult it is to change bits in this window [16:57] What you want to do is change bits in this window when it's called for codec installs, correct? [16:57] exactly [16:57] I assume the "Canonical Codec Store" link is context-dependent [16:58] I agree that solving this "properly" might be too intrusive post FF, but I wouldn't want to remove the Help button unconditionally [16:58] Indeed [16:58] Right, I don't want to remove the Help button unconditionally, just in the codec situation [16:59] mpt: I guess you probably know some python; check /usr/lib/python2.5/site-packages/AppInstall/distros/Ubuntu.py [17:01] (label, url) = distro.get_codec_information_link() [17:01] if (label is not None) and (url is not None): [17:01] button = gtk.LinkButton(url, label) [17:01] mpt: in AppInstall/activation.py [17:01] I'm in 8.04 at the moment [17:01] mpt: grab lp:~ubuntu-core-dev/gnome-app-install/main [17:01] ah, thanks [17:03] I was just wanting to know whether it was possible :-) [17:04] mpt: Sure, it should be [17:04] ok [17:04] mpt: BTW it's the first time I poke at this :) [17:05] It seems the UI already supports various mode of operation by subclassing ActivationStyle [17:05] class CodecSearchActivationStyle(SearchActivationStyle): [17:05] mpt: So it's very trivial [17:06] mpt: I think it would be cleaner to provide Help for installing codecs rather than dropping the button completely though [17:06] Sure, but I'm assuming we can't do that past feature freeze [17:06] If we can, I'll happily write some [17:07] This will all likely be revamped for Intrepid+1 [17:09] mpt: I think it's a fairly trivial UI tweak, but I could be wrong [17:09] mpt: You could discuss this with release team to make sure [18:00] Thanks for your info lool [19:17] hallo alle zusammen [19:55] what can make pkg-config --cflags return something but --exists none? [19:57] seb128: in gtk2-engines i've added to .install the right .pc but it seems debian/ has the old .pc, should i remove the old .pc from debian or revert the .install? [20:06] If Banshee sometimes stops responding to GNOME global hotkeys that I've set up, whose bug is that? [20:06] And if the answer is "it depends", how can I find out? [20:14] ember_: why did you add the .pc to start? it was not installed because the debian maintainer decided it was not required [20:51] does any1 know about video editing?