[00:54] asac: that should be only hinting-slight. The hinting-medium link is a leftover from Hardy which hasn't been removed properly. [01:02] ArneGoetje: hmm. so another left over ;) [01:02] ok [01:03] ArneGoetje: please upgrade to my packages in ppa [01:03] ArneGoetje: you can set the values to "auto" in font_rendering [01:43] asac: will do later. === onestone_ is now known as onestone [03:34] does Ubuntu have the fprintd support that the Gnome 2.26 release notes mentions? [03:34] * calc has a fingerprint reader in his laptop [03:37] The necessary packages seem to be in Universe. [03:37] libpam-fprint etc... [03:38] ah ok [03:38] i didn't know if the fingerprint stuff shows up automatically in about me when that is installed or not [03:38] nor do I [08:13] hello gentlemen and ladies [08:17] hello there [08:49] seb128, hello [08:49] lut crevette [08:50] there is a problem with the plugin empathy of nautilus-sendto-universe [08:51] https://bugs.edge.launchpad.net/ubuntu/+source/nautilus-sendto-universe/+bug/344765 [08:51] Ubuntu bug 344765 in nautilus-sendto-universe "no Telepathy sending" [Undecided,New] [08:51] how can I ask a rebuild ? [08:52] crevette: you can't you need to reupload [08:58] :/ [08:58] seb128: I have written a fix for bug 339228 (which really is bug 307306) [08:58] Launchpad bug 339228 in gnome-settings-daemon "gnome-settings-daemon and gnome-display-properties slow down xserver when external monitor added" [Low,Triaged] https://launchpad.net/bugs/339228 [08:58] Launchpad bug 307306 in gnome-power-manager "upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow" [High,Fix released] https://launchpad.net/bugs/307306 [08:59] tseliot: that's not a g-s-d bug then? [09:00] seb128: it's a bug in gnome-desktop as it does hardware probing even for trivial events [09:00] did you discuss that upstream? [09:00] and g-s-d relies on gnome-desktop [09:00] where is the patch? [09:00] yes, but they don't seem extremely interested [09:01] here are my patches: [09:01] https://code.launchpad.net/~albertomilone/gnome-desktop/tseliot-fixes [09:01] https://code.launchpad.net/~albertomilone/gnome-control-center/tseliot-fixes [09:01] have a look at the latest revision [09:01] revisions [09:01] what is the upstream bug number? [09:01] there are two of them: [09:01] http://bugzilla.gnome.org/show_bug.cgi?id=574931 [09:01] Gnome bug 574931 in general "gnome-settings-daemon and gnome-display-properties slow down xserver when external monitor added" [Major,Unconfirmed] [09:02] http://bugzilla.gnome.org/show_bug.cgi?id=568160 [09:02] Gnome bug 568160 in libgnome-desktop "Gnome Settings daemon causes high CPU usage with an expensive call" [Major,Unconfirmed] [09:03] my change involves a small change in the API (i.e. calling gnome-screen-refresh() with an additional argument) therefore I doubt that it will be accepted by upstream in this version of Gnome [09:03] tseliot: ok, that is no go for jaunty [09:03] that's an ABI breakage, not an addition [09:03] it would require a soname change and to transition everything built against libgnome-desktop in jaunty [09:04] seb128: is there anything else that relies on gnome-desktop? [09:04] better to add a new function doing what you want and make gnome-control-center use it [09:04] tseliot: apt-cache rdepends libgnome-desktop-11 [09:04] tseliot: probably not on the gnome-rr api but still that's an abi breakage [09:08] seb128: ok, would it be ok if I modified only the static functions and add another non-static function? [09:09] tseliot: you can modify anything which is not part of the public api [09:10] you can add a new function doing the non expensive calls and change the code to call that one [09:10] if you do please prefix it ubuntu_ though so we avoid having trouble with upstream because we modify their api in a non obvious way [09:11] seb128: yes, this is exactly what I was thinking of doing. And yes I'll use the ubuntu_ prefix as I did in some other patches of mine [09:11] excellent, thanks for your work [09:11] I will try to ping federico about that when he's online [09:11] ok [09:12] I'll give you my new patches soon [09:13] could you also attach your suggested patches to bugzilla when you done with those? [09:13] thanks [09:14] Good moring [09:15] hey pitti [09:15] pitti: how do you feel today? better? [09:16] seb128: yeah, much better [09:16] unfortunately I had to fiddle with my internet for an entire hour [09:16] my main network is broken, and then it took me another 20 minutes to get my 3G card workoing [09:17] bah [09:17] want DSL [09:19] dsl is coming ;-) [09:20] seb128: shall I attach my patches that break the API in the gnome bugzilla? [09:20] tseliot: yes please [09:21] pitti: :( [09:22] seb128: ok, I'll tell them that if the patches that I attach look good to them and they are interested, I'll add the checks for RandR's version both at runtime and at compilation time. [09:30] seb128: in interface editor there are only 3 fonts, while we have 5 in the appearence dialog ... any clue where the others are configured? [09:30] asac: say that again? [09:31] seb128: ;). sorry. i mean in /desktop/gnome/interface there are 3 font names [09:31] seb128: but in appearence dialog there are five ;) [09:32] asac: ah, the title font is a wm thing and the monospace a g-t one I think [09:32] asac: search for Sans in the gconf key names ;-) [09:32] it should list those [09:32] seb128: monospace is in /desktop/gnome/interface [09:32] but let me search for sans and serif [09:33] well, search in gconf-editor [09:33] check to include the value [09:33] and type the font name [09:33] yeah so its nautilus desktop font [09:34] that one is the one used for the desktop icons only right [09:34] and metacity/general/title_bar_font [09:34] great [09:34] metacity/general/titlebar_font [09:42] tbird is indeed an ugly beast. have to figure why it is such a wrong font there. in thunderbird 3 all seems fine. [09:43] let me first finish this security update round for tbird ... after lunch i can hopefully deal with this === Nicke_ is now known as Nicke [10:20] seb128: I managed to achieve the same effect without breaking the API. This way we don't even have to update gnome-control-center: https://code.launchpad.net/~albertomilone/gnome-desktop/tseliot-fixes [10:21] tseliot: excellent ;-) [10:22] tseliot: set your email in your launchpad account ;) [10:22] tseliot: to match what you use in bzr ;) [10:22] crevette: seb128: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus-sendto-universe/+bug/344765 would be good to rebuild it now Empathy 2.26 reached Jaunty [10:22] @canonical.it ? [10:22] Ubuntu bug 344765 in nautilus-sendto-universe "no Telepathy sending" [Undecided,New] [10:22] whats that? [10:23] asac: I thought I set it to @canonical.com already [10:23] tseliot: seems you changed from @alice.it ... to @canonical.it ;) [10:23] both are not associated with your launchpad account [10:23] so i cannot click on your name (like i can do for Michael Vogt for instance ";)) [10:23] cassidy: yes [10:24] asac: @canonical.com is the default email address on launchpad. Or am I missing something? [10:24] cassidy: somebody screwed the packaging apparently [10:24] tseliot: i dont know. only thing i know is that the emails you used for commit are not associated [10:24] with your LP account [10:24] cassidy: the issue you shows suggest than a soname changes and the library has not be renamed [10:25] if thats transitional its ok. otherwise you can just add multiple emails [10:25] seb128: empathy renames his libs each time soname are changed [10:25] asac: no, it's a typo. It looks like I replaces @alice.it with @canonical.it instead of @canonical.com. Thanks for making me notice ;) [10:26] cassidy: there is something weird there [10:26] cassidy: libempathy-gtk.so.17 => not found [10:26] tseliot: no problem. [10:26] cassidy: that should never happen [10:27] asac: news on the hardy branch of n-m 0.7.1? [10:27] cassidy: ok, nautilus-sendto-universe has no shlib depends apparently and you removed the old soname [10:27] so problem is in nautilus-sendto-universe pkg? [10:27] yes [10:28] it should depends on libempathy-gtk17 [10:28] which would assure this version stay installed even if there is a new one [10:28] tseliot: that kind of got bumped from low to medium prio for me. [10:28] cassidy: I will fix that today [10:28] because we need it else where now [10:28] seb128: we can have multiple version of libempathy installed on the same time? [10:29] tseliot: so it will happen really soon [10:29] seb128: cool [10:29] asac: ah, very well :-) [10:32] Zdra: well, if the soname change they don't conflict so yes, that's the reason we change binary names [10:33] Zdra: do libsomething7 and libsomething8 can be installed together [10:33] which makes easy transitions, you can keep libsomething7 installed while you rebuild things with the new version [10:34] seb128: ok [10:34] anyone else noticed that "paste" with middle mouse became unreliable in jaunty gnome-terminal? [10:34] no [10:34] not really a recent regression. i always thought it was X loosing events. but currently i am thinking its gnome-terminal eating mouse events if its not yet focussed [10:35] interesting. i regularly need to press middle mouse twice or sometimes even three times to get the paste [10:35] I don't copy things there often though [10:35] fta: ^^ do you see this? [10:35] ah right. you use xterm [10:35] too bad [10:40] seb128: patch submitted (just FYI): http://bugzilla.gnome.org/show_bug.cgi?id=568160 [10:40] Gnome bug 568160 in libgnome-desktop "Gnome Settings daemon causes high CPU usage with an expensive call" [Major,Unconfirmed] [10:41] tseliot: thanks [10:41] np [10:54] pitti: ping? MacSlow is building notify-osd latest tarball as I speak [10:55] seb128: apt-get source ubiquity -> ./gui/glade/stepLanguage.glade [10:55] seb128: the title is in "single line mode" ... this seems to have a bug making the label not scaling vertically at all [10:56] asac: ping? do you have new build of network-manager-gnome with the last title fixes? the last one i see (0.7.1~rc3-0ubuntu1) dates back to the 5th of March [10:56] http://ubuntu-pics.de/bild/11246/bildschirmfoto_1_o1tzqH.png [10:56] seb128: ^^ [10:58] davidbarth: yes. i need to put some love into this asap. sorry for the delay. [10:58] today or tomorrow morning i will try to get this through RMs. [11:01] davidbarth: he just told me [11:01] davidbarth: standing by :) [11:05] so for single line mode we have: [11:05] height += PANGO_PIXELS (ascent + descent); [11:05] otherwise its height += PANGO_PIXELS (logical_rect.height); [11:14] doh, GNOME switching to git officially for 2.27 [11:15] ugh, more pain [11:15] seb128: and you are complaining about bzr.. [11:16] I like svn ... [11:16] really?? O_o [11:16] cassidy: svn? yes [11:17] does sending notifications work over dbus? i.e. could I monitor notification requests with dbus-monitor? [11:17] i can't work with it any more [11:17] looking at bug 343261 for Banshee [11:17] git changed my life (in better ;) [11:17] Launchpad bug 343261 in banshee "No notification on audio track changes" [Undecided,Confirmed] https://launchpad.net/bugs/343261 [11:18] cassidy: over complication for no real benefit for what I do [11:18] I guess that depends of your uses cases [11:19] cassidy: get a checkout, do some easy changes, push back [11:19] but for lot of developers that's a real benefit [11:19] yeah for that svn is definitely easier [11:20] but for us, for example, we have a branches oriented dev workflow. git is a must have in that case [11:20] Laney: dbus-monitor --session [11:20] seb128: Yeah, I was just wondering if that would actually work (not on an Ubuntu box atm to test) [11:20] cassidy: git makes that difficult for no good reason compared to bzr in such cases, but *shrug*, the git fanboys didn't bother trying to see if other dcvs work better usually [11:22] seb128: I'm not considering myself as a git fan boy and I'm still using bzr (for my Elisa plugin for example). I recognized that git was scaring me first but now I know how to use it, it wouldn't change it for anything else [11:22] cassidy: but that has been trolled enough, I guess I will just use git the way I used svn [11:23] yeah if you do the same thing as you did with svn that's not so harder [11:23] cassidy: you think bzr is not good enough for what you have to do? what do you miss there? just curious [11:24] seb128: well, frankly, svn is a pain in the neck [11:24] seb128: I think it's generally less flexible and powerfull than git. What I miss most is the fast cloning/branching, the ability to store branches in the same repo, the remote repo, git rebase, etc [11:25] bzr can probably do most of these stuffs with plugins though, I didn't really investigate this area [11:25] I guess I'm not enough of a code writer to need all those things [11:25] svn's lack of branches, and together with that, this hideous websvn is a really major issue [11:25] yep, as said, that's just a matter of uses cases [11:26] I like the viewsvn of GNOME [11:26] but *shrug* ;-) [11:26] cassidy: yeah, bzr has those as well (all built in, except for rebase, which is a plugin for good reason, since it's not a good idea to use it in public development) [11:27] that's similar than vim vs gedit. Both a good editors but one is a lot more complete and require more training [11:27] seb128: really? I always bite into my table if I have to cherrypick a patch from svn; but maybe I just don't know some dirty tricks [11:27] and not everyone needs to use vim :) [11:27] pitti: it lacks a "give the diff for this revision", you have to do it file by file which is no fun but otherwise it's nice [11:27] the simple question "show me the diff of r1234" requires black magic with webcvs/websvn [11:27] seb128: right, that's the thing I'm usually interested in [11:28] yeah, agree with you it lacks this one [11:28] anyway no point to debate on that, it's settled for GNOME [11:28] so for popular projects I just keep a checkout and svn diff it from there (which is slightly easier, although still much harder than in bzr) [11:28] right [11:28] good that they stop discussing tools for ages [11:28] * pitti shuts up [11:29] I just don't quite understand how people can actually like git [11:29] actually my prefered bzr feature is the launchpad integration. So if you could convince your co-workers to support git as well that would be great :D [11:29] but I guess there is so political issues here :) [11:29] cassidy: that's in fact a long-standing wishlist item [11:29] cassidy: lp will be opensource soon so you will perhaps be able to write a patch for it ;-) [11:29] cassidy: no, it's just a manpower thing [11:30] cassidy: writing a bzr interface for git which is really robust is far from trivial [11:30] seb128: bzr is open source.. [11:30] it's got nothing to do with lp [11:30] there's tailor, but it's not robust [11:31] i. e. if you do two git imports with tailor, the resulting branches aren't related to each other [11:31] pitti: I think they want launchpad to do git hosting the way it does with bzr [11:31] I'd like real git integration, not one going through bzr [11:31] ah, I see [11:31] seb128: yep [11:31] cassidy: well, I for my part want a bzr interface for git, so that I can actually *use* it without constantly having to RTFM and think about the git complexities :) [11:32] but I don't mind much either way [11:32] yeah that would be good and useful for lot of people [11:34] seb128: would you mind pinging me on jabber? need to test the new indicator-messages [11:35] pitti: done [11:54] asac: I've noticed Shift-Insert being unreliable in gnome-terminal since jaunty [12:03] pitti: want to test ekiga? [12:04] hey kenvandine_wk [12:05] kenvandine_wk: good day for that today, since I'm on 3G, and not on my weird ISP [12:05] kenvandine_wk: in your PPA? [12:05] kenvandine_wk: give me 30 mins to sponsor two more packages, then we can do that? [12:07] kenvandine_wk: how did the config migration work for you? I think I'll dump my ekiga gconf settings before the upgrade :) [12:09] pitti: sure [12:10] pitti: it just worked :) [12:10] nice [12:20] seb128: ted's two merge requests done; doing notify-osd now [12:21] . o O { with a bzr merge and a bzr bd -S this is all too easy! } [12:23] MacSlow: does the trunk bzr log contain all LP # references? I see two references, is that corect? [12:24] pitti, yeah... right now I cannot think of a bugfix between 0.9.5 and 0.9.6 I might have overlooked [12:24] MacSlow: ok, thanks [12:30] pitti: thanks [12:38] MacSlow: is it expected that tests/test-modules segfaults? [12:38] the actual package works fine for me [12:39] pitti: that upgrade this morning was painful... killed my box, but i blame compiz [12:40] mdeslaur: interesting [12:40] mdeslaur: but for me its also middle click in firefox [12:40] kenvandine_wk: killed how? [12:40] that sometimes doesnt work to close tabs [12:40] memory [12:40] somehow i think its at-spi ... let me disable assistive technolgoies [12:40] compiz was using more than 700M RSS [12:40] while update manager was doing a massive update [12:40] 3G of ram and 2G swap all pegged [12:40] i need a good wikipage about libindicate and the idea about that [12:40] mpt: ? [12:40] and apps started crashing [12:41] * kenvandine_wk wonders why compiz was sucking so much memory [12:41] asac: oh, something else then [12:41] the fonts look great now though :) [12:43] anyone knows when the beta lock will happen? [12:43] asac: today when slangasek wake up and find an IS person to turn the button [12:44] asac: ie in the next hours [12:44] asac: the fonts look great! [12:44] kenvandine_wk: ;) [12:44] but pidgin's fonts look huge :) [12:44] kenvandine_wk: except in thunderbird [12:44] * kenvandine_wk is a evo guy :) [12:45] kenvandine_wk: so ... there are a few more tweakages [12:45] kenvandine_wk: monospace fonts in terminal need to be changed [12:45] let me check pidgin [12:45] maybe we need to use a smaller document_font [12:45] pidgin defaults to the document font [12:45] oh yeah... terminal is huge too [12:46] but they are sharp looking :-D [12:46] kenvandine_wk: terminal font is even in a bug in gnome terminal i think [12:46] kenvandine_wk: but i will know more in a few [12:47] pitti, oh no ... that should not happen [12:48] kenvandine_wk: hehe. for now set document_font to 10.666px [12:48] seb128: bug #345168 ready for review, builds fine with the svn-patch included. [12:48] Launchpad bug 345168 in nautilus-cd-burner "Please sponsor version 2.25.3 in jaunty" [Wishlist,Confirmed] https://launchpad.net/bugs/345168 [12:49] asac: nah... i will wait so i can test the defaults [12:49] Ampelbein: thanks! [12:50] kenvandine_wk: hm, diamondcard seems to work for me, but @ekiga.net not [12:50] kenvandine_wk: I can't get the echo test (immediately disconnects) [12:50] kenvandine_wk: and if I try to ring you, it says "user not available" [12:51] I don't use ekiga but it seems to be buggy every time pitti tries a new version [12:51] heh [12:51] seb128: interestingly enough, using @diamondcard.us has never failed me [12:52] just @ekiga.net [12:52] pitti, I'm looking into the notify-osd test-suite atm [12:52] kenvandine_wk: try to ring me? [12:52] pitti, I'll get back to you once I know more ... btw... which part segfaults for you? [12:52] one sec [12:53] MacSlow: http://paste.ubuntu.com/133617/ [12:53] MacSlow: hang on, trying to get a stack trace [12:54] pitti, wtf ... I fixed that [12:54] that can't be [12:54] * MacSlow tears out his hair [12:57] MacSlow: http://paste.ubuntu.com/133619/ [13:03] asac, I'm sorry, tedg and I haven't had time to write up anything about it yet [13:03] the Empathy developers need it too [13:07] pitti, do you run it on the build-server or locally? [13:08] pitti, question is ... does it have a proper display or not ... the test-suite currently needs that [13:08] hey mvo [13:08] hey MacSlow [13:12] mpt: hmm ... i need to explain to moz the difference of libindicate and why supporting that in the "general" toolkit makes sense ... for background i had http://paste.ubuntu.com/133628/ [13:13] MacSlow: locally [13:13] MacSlow: yes, it's my normal workstation, just debian/rules build and tests/test-modules [13:13] jaunty du jour [13:15] pitti, while it does not crash here it covers only 54% of the tests ... that's unacceptable and I suggest to defer notify-osd for today [13:15] 's beta [13:15] MacSlow: well, the previous versions's test crashed as well; I uploaded it already, too [13:16] since my tests in the real system (volume control, IRC bubbles, etc.) work just fine [13:16] pitti, I just cannot chase everything so fast [13:16] MacSlow: joining dx [13:16] it's such a mess [13:17] hello everyone ! [13:17] lut huats [13:17] hey rickspencer3 [13:17] hello seb128 ! [13:17] ho are you ? [13:17] huats: good, you? [13:19] seb128: good too ! [13:19] it is summer here :) [13:20] ;-) [13:20] it's sunny here too [13:20] Lucky! We just have grey skies [13:23] pitti: having the configure.in diffing and the symbol diff, etc as part of a standard testsuite in bzr-buildpackage would be nice [13:24] yeah [13:24] I always do that by hand [13:24] diff the configure.in between version [13:24] run my diff-symbols.py after build [13:24] ok, time for lunch [13:24] bbl [13:24] and then by debdiff between installed version and new debs [13:24] pitti: enjoy! [13:37] tseliot: still around? was your gnome-desktop change something ready for sponsoring? [13:42] seb128: yep [13:42] seb128: I updated the bzr branch to the latest version that you uploaded [13:43] since the version in the ~ubuntu-core-dev wasn't up-to-date [13:43] tseliot: can you give the bzr url again? [13:43] https://code.launchpad.net/~albertomilone/gnome-desktop/tseliot-fixes [13:43] the branch is: lp:~albertomilone/gnome-desktop/tseliot-fixes [13:43] tseliot: thanks [13:44] seb128: thanks in advance for the upload :-) [13:56] you're welcome [13:56] tedg: hi, got a minute to discuss your pidgin changes? [13:57] seb128: Sure. [13:57] tedg: ok, so 2 questions [13:57] seb128: Heh, there's only two patches ;) [13:57] 1- wouldn't it make sense to use the prefs.xml to change the default option to show the icon? or that's not working? [13:58] 2- did you send your other change upstream, cf patch tagging and lower delta etc discussions [13:59] seb128: I don't see a prefs.xml in the source tree. I think it gets built by that code. That is what sets the defaults for that. [13:59] tedg: cd debian/prefs.xml in the deb source [13:59] seb128: Yes, I will, I just finished it at 2am last night. That's a today thing :) [13:59] cd -> cf rather [14:00] tedg: ok, no hurry I'm just making sure we don't carry diffs for ever for no good reason ;-) [14:01] seb128: Ah, I didn't look in the debian packaging. Sure, that works for me, I was just only looking in the upstream codebase. [14:01] It seems a little weird that the debian packaging does things differently than the upstream project though... [14:02] tedg: ok, let's upload your version for now maybe and figure that later? [14:02] seb128: Sounds good. [14:02] tedg: how differently? we ship a config rather than patching the code [14:02] that seems a better way to me [14:02] redhat does that too in them rpm iirc [14:02] seb128: They don't ship a config at all and build it on the fly. I'm not saying it's bad, I'm just saying it's odd. [14:03] ok [14:03] hello, [14:03] I am looking for a fax frontend to send faxes from my ubuntu to a hylafax server [14:03] I've no strong opinion either way ;-) [14:03] dandre: -> #ubuntu [14:03] For instance if they change the defaults, or the type of a value, that's going to show up as a bug instead of something that just "goes with the flow." [14:03] sorry [14:04] seb128: salut, may you please give your opinion on bug 344431? [14:04] Launchpad bug 344431 in brasero "cd / dvd creator appears in the apps menu, not in places" [Low,New] https://launchpad.net/bugs/344431 [14:04] pedro_: holla! [14:04] * tedg is learning things he shouldn't in Pidgin's debian/lintian-override directory :) [14:04] one minute [14:05] tedg: ah ah [14:11] tseliot: uploaded and pushed to the ubuntu-desktop vcs (it's stored there now, I've updated the control) [14:11] seb128: thanks :-) [14:12] tedg: http://launchpadlibrarian.net/24088024/0.14-1ubuntu6.debdiff [14:13] tedg: why did you remove the VERSION file there? [14:13] seb128: Sorry, that was a bzr-ism. The file got deleted and then the commit caught it. [14:13] I forgot to clean it up. [14:13] tedg: ok, I drop that change then [14:14] seb128: Great, thanks. Sorry about that. [14:14] no problem! [14:14] I think it's a problem in the upstream build system. They also delete some HTML files. [14:20] could piding be less intuitive as an IRC client? [14:20] it opens a nickserv dialog saying the nickname is already registered [14:20] no channel list, nothing obvious on what to do or showing that IRC is connected [14:21] seb128_: hello [14:21] seb128_: hello [14:21] hum [14:21] tedg: it displays 3:23 for the message time when it's 15:23?! [14:22] seb128: Yes, it is a translateable string. You're just seeing it in American ;) [14:23] why does the time need to be translated I will never understand [14:23] it's easy french doesn't use am and pm we use 24 hours [14:23] that should be a locale thing and just work [14:23] seb128: Because Americans can't read 24 hour time. [14:24] well the american locale should say you use am and pm then [14:24] it does [14:24] well so why do we need to translate the time string? [14:24] Well, that seemed like extra information that doesn't seem useful. Are you really looking at IM messages that are over 12 hours old? [14:24] that's what LC_TIME is for [14:24] I though there was a glibc api for that [14:24] dobey: How do you get it from locale then? [14:25] but there are other issues [14:26] Please comment with ideas on bug 334036 [14:26] Launchpad bug 334036 in indicator-applet "Timestamp in messages not consistent with desktop" [Wishlist,Confirmed] https://launchpad.net/bugs/334036 [14:26] like, i don't think there is a glibc api to actually give you a string for the time that is properly formatted for the locale [14:26] or something [14:26] The idea was to pull the GConf key from the clock. But that required pulling in GConf. [14:26] which is why there are a billion time strings in the evo translations for example [14:26] And lots of logic to find the clock. [14:34] that is just ridiculous, there is none of those strftime() function or something to display an hour formatted for your locale? [14:35] strftime is like sprintf but takes time formatting options [14:36] so strftime("%h:%m") or something (though those are definitely not the right ones [14:39] tedg: strftime %X [14:40] displays 15:41:23 with a french locale [14:40] seb128: whoa, I already got a fix for the nfs bug :) [14:40] a _proposed_ fix [14:40] "03:41:56 PM" with an en_US one [14:40] tjaalton: nfs or gnome fix? [14:40] seb128: nfs/kernel [14:41] %X Equivalent to %T . [14:41] and %T is not in the man page... [14:41] seb128: Is there a way to kill the seconds though? [14:41] %T time; same as %H:%M:%S [14:41] from man date [14:41] huh [14:42] tedg: man strftime? [14:42] %T The time in 24-hour notation (%H:%M:%S). (SU) [14:43] %X The preferred time representation for the current locale without [14:43] the date. [14:43] on jaunty [14:44] man stftime doesn't say that on intrepid. hrmm [14:45] GNU 2008-10-29 STRFTIME(3) [14:45] it has been updated recently [14:45] I still don't see how to do without seconds. [14:45] right, me neither but there must be a way ;-) [14:46] I guess I could do %X and then compare it to one of the other cases using strcmp. [14:46] you can use %H:%M but that will be 24 hours format [14:46] and there is a way to query the 24h or amp,pm from libc for sure [14:46] you could query and call with the right parameter for am,pm or 24 hours [14:48] you could do a regex of s/:[0-9][0-9] // on the sring :) [14:48] err [14:48] s/foo / / rather [14:56] Does devhelp work for anyone else? It's not worked on Jaunty for me. [14:59] works for me [14:59] (devhelp) [14:59] mvo: want to sponsor #345168? ;-) [15:00] bug #345168 [15:00] Launchpad bug 345168 in nautilus-cd-burner "Please sponsor version 2.25.3 in jaunty" [Wishlist,Confirmed] https://launchpad.net/bugs/345168 [15:00] * seb128 is trying to tackle the sponsoring queue before beta [15:00] seb128: can do [15:00] I think it's an easy one [15:00] thanks [15:00] kendo! [15:00] I'm just busy with some other change and slangasek will probably trigger the freeze button soon ;-) [15:01] \o/ ... i think i am done wiht the pre-beta-freeze rush [15:01] great that the archive was still open toda [15:01] y [15:01] now looking at gnome-terminal and thunderbird font issue to see what we can do for beta still [15:02] grr, why ooo keeps starting in fullscreen mode? it has no decoration, and i can't make it smaller (metacity) [15:02] seb128: geh, its not in bzr [15:03] crisis! [15:07] mvo: you can put it there if you want ;-) [15:13] mvo: i did not know that nautilus-cd-burner was to be packaged in bzr, the debian/control file did not say so. [15:19] Ampelbein: it's not which is what mvo complain about ;-) [15:20] or not yet [15:20] rather [15:25] seb128: hm, nautilus-c-b looks ok, but I don't see it in the place menu anymore [15:25] seb128: but right click on a iso works - is that a known issue? [15:26] mvo: yes [15:26] mvo: yes, pedro_ pinged me about a similar bug before, forgot to look [15:26] pedro_: ^ [15:26] mvo: we don't use n-c-b by default anyway in jaunty so [15:26] is on the system tools menu now bug 344431 [15:26] Launchpad bug 344431 in brasero "cd / dvd creator appears in the apps menu, not in places" [Low,New] https://launchpad.net/bugs/344431 [15:27] mvo: gnome bug 573790 [15:27] Gnome bug 573790 in general "No way to access burn:// without a blank disc" [Major,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=573790 [15:29] ok I think that's a confusing choice [15:29] vuntz: ^ what do you think about this one? [15:32] seb128: sorry, disconnected. did you say something in between? [15:32] ok I think that's a confusing choice [15:32] vuntz: ^ what do you think about this one? [15:32] so its a choice from upstream? [15:32] mvo: I think we should discuss adding back the item to the place menu [15:32] mvo: mvo: gnome bug 573790 [15:32] Gnome bug 573790 in general "No way to access burn:// without a blank disc" [Major,Resolved: fixed] http://bugzilla.gnome.org/show_bug.cgi?id=573790 [15:33] thanks, I will sponsor the upload then, I was not certain if it was deliberate or a error in the package [15:34] cool [15:34] bah, hate gnome-screensaver [15:34] mvo: thanks. gotta go now, be back later. cu. [15:34] pitti: did you upload/fix jockey in kubuntu to stop using sudo? === Ampelbein is now known as ampelbein [15:35] pitti: it's alright jockey started up before the update :) [15:36] davmor2: yes, yesterday [15:36] pitti: yes jockey started up, then the updates ran, So it worked as expected after reboot [15:37] asac: openoffice also probably [15:38] Laney: hey, are you interested by doing some desktop work today? ;-) [15:39] davmor2: I'm glad to hear that :) [15:39] mdeslaur: me? [15:39] mdeslaur: font issues in ooo? [15:39] seb128: Aye, what needs doing? [15:39] asac: probably the same issue as gnome-terminal and thunderbird [15:40] mdeslaur: gnome terminal has a bug in the font code [15:40] Laney: http://download.gnome.org/sources/evolution-mapi/0.26/evolution-mapi-0.26.0.1.tar.gz is an easy update but current version is totally broken [15:40] mdeslaur: they always reset stuff to point [15:40] mdeslaur: i found that already and have to fix it [15:40] seb128: OK I will be home in 90 mins to have a look [15:40] Laney: and nautilus-sendto-universe uses no shlibs apparently and has been broken by some soname changes, needs a rebuild and to fix the shlibs issue [15:40] uh, weird [15:40] indeed [15:40] mdeslaur: tbird hopefully goes away when building with cairo and not with xft2 .. but i have to verify that. also i have to find out why (if its the case) xft behaves bad for some apps [15:41] mdeslaur: most likely its really just bad app code overwriting stuff [15:41] mdeslaur: tbird 3 is good [15:41] asac: fun fun fun :P [15:41] Laney: that might be because there is only plugins there and the path need to be added to the shlibs option [15:41] Laney: it shlibs are usually for bin and lib [15:41] asac: sorry for the can of worms :P [15:42] Laney: in fact it uses DEB_DH_SHLIBDEPS_ARGS_ALL += --exclude=/usr/lib/nautilus-sendto/plugins explicitly [15:43] Laney: that's to not have strong depends ... anyway it needs a rebuild then ;-) [15:43] asac, I suggest not taking up the topic with Mozilla until we have API documents ready. (We tried doing that with the Empathy developers, which predictably led to a confused response.) And if asked, say that we'll have API documents ready soon. [15:48] mpt: its not my decision [15:48] mpt: the topic was opened by others [15:48] mvo: did we have case in previous cycle where gnome-screensaver upgrade where problematic for unlocking? [15:48] mpt: and they started to implement stuff [15:48] mpt: so we _now_ need to provide input to prevent more resources getting wasted ;) [15:48] mvo: ie 2.24 running and upgrade to 2.26 the unlock dialog will not be showed correctly ... not sure what to do about that [15:50] seb128: we had this in the past, but I'm not sure for what versions [15:50] seb128: we disable the screensaver during upgrades [15:50] mvo: what do you mean? [15:51] hm, I thought we did [15:51] mvo: well, I did lock my screen manually after upgrade [15:51] and had to go back to a vt stop gnome-screensaver to get back to my session [15:52] asac, what kind of "stuff"? libnotify stuff? [15:53] mpt_: yes. i have to tell them that libnotify alone isnt good for messaging. [15:53] mpt_: anyway. i can lead the discussion if you dont want to provide input [15:53] ;) [15:53] i will just give my ideas then. all i will achieve is tell them that we will give more info soon [15:53] Oh, I want to, it's just a matter of finding time :-P [15:53] Is there a bug report or somewhere I could post easily? [15:53] mpt_: right. i showed you my paste and you didnt saw if its completely wrong or not ;) [15:54] seb128: do we have issues with that? [15:54] mpt_: we should channel the input through one channel. its just confusing if multiple folks post different stuff ;) [15:54] mpt_: thats why i asked and i will proxy ;) [15:54] fair enough [15:54] but well ... lets wait till beta freeze [15:55] mvo: wb [15:55] seb128: last ping still valid? [15:55] hrm [15:55] network [15:55] sucks [15:55] vuntz: yes [15:56] vuntz: not sure what I asked but I don't think that was an outdating question ;-) [15:56] seb128: the item was removed from Places, following a bug report [15:56] vuntz: right, but do you think it's a good decision? [15:56] seb128: it's mentioned somewhere in the ChangeLog [15:56] just your personnal opinion [15:56] seb128: I honestly don't care :-) [15:56] I know what happened [15:56] ok [15:56] I'm fine either way [15:56] vuntz: next question, did you run into the gnome-screensaver issue I described? [15:57] I don't read everything [15:57] so I don't know the issue :-) [15:57] vuntz: well now you have 2 items in the menu, one opening the gui and one opening the nautilus location, not very obvious [15:57] vuntz: mvo: did we have case in previous cycle where gnome-screensaver upgrade where problematic for unlocking? [15:57] mvo: ie 2.24 running and upgrade to 2.26 the unlock dialog will not be showed correctly ... not sure what to do about that [15:57] vuntz: ie if you lock the screen without having restarted the session you can't unlock [15:58] vuntz: I get it every time, tried several downgrade and upgrades now [15:58] ah [15:58] err [15:58] 2.24 to 2.26 or 2.25.2 to 2.26.0? [15:59] 2.24 to 2.26 [15:59] distro upgrade [15:59] I didn't try 2.25 ;-) [15:59] so I don't know :-) [15:59] ie intrepid to jaunty [15:59] ok [16:10] seb128: we had this in the past, but I'm not sure for what versions [16:11] seb128: I thought we disable the screensaver during upgrades, but I can not find the code for that right now, maybe it got dropped again? [16:11] good that slangasek sleeps so long ;) [16:11] archive was still open ;) [16:14] seb128: i think the screensaver issue happens on 2.25.2 -> 2.26.0 also [16:15] seb128: or something caused me to not be able to unlock, i ended up killing the running screensaver and then it let me log back in [16:15] ^ vuntz [16:16] I though jaunty didn't have 2.25.2 [16:16] er well whatever we had directly prior to 2.26.0 [16:16] * calc looks in his log [16:16] seb128: well, blame gnome-screensaver people, I'd say :-) [16:16] calc: https://edge.launchpad.net/ubuntu/+source/gnome-screensaver [16:16] but I didn't remember seeing this [16:16] i upgraded jaunty today in any case and that is when it happened [16:16] vuntz: yeah, I'm doing that next [16:16] although... I'm not using a screensaver [16:16] vuntz: maybe you restarted your session before locking screen [16:16] seb128: I don't lock my screen, except when travelling [16:17] me neither [16:17] ah ok i am wrong, i think it must have happened between 2.24.0-0ubuntu4 and 5 [16:17] I noticed because I did switch to my test user and it locked screen [16:17] poor vuntz, bombarded with questions :) [16:17] * calc had just assumed it upgraded to 2.26 along with everything else today [16:17] hmm that is really odd the 5 is from last week? [16:17] no I didn't upload 2.26 because of the issue [16:17] mvo: I'll make seb128 pay, don't worry [16:18] heh! [16:18] ok whatever happened when i upgraded today i noticed the issue i hadn't noticed it before today [16:18] maybe something screensaver uses library-wise is the culprit? [16:18] vuntz: I will pay, GNOME switching to git, that's like paying every day for things you didn't do [16:18] mvo: and he's from Alsace, so that's fine... [16:19] haha [16:19] git :( [16:19] * mvo weeps [16:20] calc: so you are saying that's an issue in the current jaunty gnome-screensaver version already? [16:21] brb testing [16:29] * hyperair likes git [16:34] seb128: yea [16:34] seb128: after restarting it seems to be ok though [16:34] seb128: i did not notice it happening before my upgrade today [16:35] seb128: for whatever reason i also had trouble ssh'ing at the time so i thought it might have been some sort of weird pam issue [16:35] seb128: i could login to the console (ctl-alt-f1) and also after killing the running screensaver process for the dialog (there were two processes) i could log in via screensaver [16:38] * hyperair wonders if anyone here has debian upload privileges and is willing to sponsor my nautilus-share upload to debian (and then sync to ubuntu). this fixes bug #209136 [16:38] Launchpad bug 209136 in nautilus-share "use system icons" [Low,Confirmed] https://launchpad.net/bugs/209136 [17:08] hyperair: i don't understand that bug [17:10] dobey: basically nautilus-share uses very dated looking icons [17:10] like stock GNOME kind of thing [17:10] something like if you kill gnome-settings-daemon.. that kind of effect [17:11] dobey: the screenshots show what it _should_ be, not what it _is_ [17:11] all the gtk+ stock icons are in the tango style now [17:11] which is why i didn't understand it at first eitehr [17:12] well, i don't think that the icon /should/ be what that bug report says it should be, but eh [17:12] dobey: okay, take a look at /usr/share/nautilus-share/pixmaps/something.png (there's only one file and i can't remember the name) [17:12] i don't have it installed [17:12] dobey: what it _should_ be is gnome-fs-share [17:12] wait.. lemme upload it somewhere then. [17:12] gnome-fs-share doesn't exist :) [17:13] wel, it's a symlink to folder-remote [17:13] i don't need to see the old icon [17:13] if it was an old ugly icon, that's fine, it obviously needs to be changed [17:13] i'm just saying that i don't think folder-remote is what it should be changed to, as it's not really the right metaphor [17:15] but i don't really have a better suggestion at the moment either [17:16] probably a folder with emblem-shared overlaid would be better [17:16] dobey: it originally was... stock_shared-by-me for the menu.. [17:16] and a bigger one which is shipped in the tarball [17:16] for the actual properties dialog [17:18] i don't think that's what stock_shared-by-me was [17:18] it is [17:18] the patch says so [17:18] eeejay, hi, is there common terminology for exposing text for accessibility purposes that isn't visible otherwise? [17:18] - "stock_shared-by-me"); [17:18] + "gnome-fs-share"); [17:18] eeejay, i.e. is it called "expose to assistive devices", or something like that? [17:18] that. [17:19] oh i guess it was, but it's old style [17:19] originally the patch only had that, so i made a similar change to the .glade file [17:19] hyperair: i'm not saying it didn't use that [17:19] hyperair: if you're going to change it though, you should change it to a correct name [17:19] not gnome-fs-share [17:19] what's the correct name? [17:19] well, gnome-fs-share is a symlink to folder-remote, which is the name in the icon naming spec [17:20] hmm seriously? [17:20] but it is the opposite metaphor of 'shared by me' [17:20] hmm yeah =\ [17:20] but that's what the patch in 0ubuntu7 had. [17:21] sure. sometimes people make incorrect patches, or don't research or ask people who know, what it should be :) [17:25] alright alright point taken [17:25] i should go upload -3 to mentors.debian.net now =\ [17:26] and then send out yet another email [17:26] RFS email [17:26] heh. i need to just say the hell with it, and go rip out all the 'stock' icons from gnome-icon-theme [17:27] and force people to update stuff [17:27] hmm that won't do =\ [17:27] you'll break every damn thing [17:28] dobey: actually there are differences between gnome-fs-share and folder-remote [17:28] tedg - if i get a new message in pidgin, but immediately close the message window without reading it, would you expect the message to disappear from the indicator applet too? [17:28] it just happens that gnome-icon-theme defaults to using folder-remote [17:28] hyperair: huh? [17:28] differences where? [17:28] some icon themes make them different =\ [17:28] i just dug though soem of my icon themes [17:28] some icon themes are broken [17:29] well how sure are you that gnome-fs-share is _supposed_ to be _exactly_ the same as folder-remote? [17:29] is it documented anywhere? [17:30] chrisccoulson: Hmm, yes. Does it not? [17:30] gnome-* icons don't exist (unless they are application icons for gnome-foo named applications) [17:30] chrisccoulson: I don't think we're attaching anything to the conversation being destroyed. [17:30] it doesn't. the message remains in the applet, and then it crashes pidgin when i try to read the already deleted message [17:30] hyperair: i maintain gnome-icon-theme, tango-icon-theme, and the icon naming spec :) [17:30] hey chrisccoulson [17:30] hi seb128 [17:30] chrisccoulson: don't worry about the tracker build issue [17:30] i was going to ask about that [17:31] chrisccoulson: Okay, have you filed a bug? I'll fix it :) [17:31] chrisccoulson: it's a soyuz bug they will fix it, new section not available yet [17:31] thanks seb128:) [17:31] you're welcome [17:31] thanks for the update ;-) [17:31] tedg - i think i used apport to report it a little while back, but i'll check the latest crash to make sure it's the same trace [17:31] it's against pidgin [17:31] seb128 - no problem ;) [17:33] tedg - bug 340717. i don't think the trace looks that useful though [17:33] Bug 340717 on http://launchpad.net/bugs/340717 is private [17:33] dobey: ah. that adds a whole lot of weight to your words ;) [17:33] hyperair: see the 'Author' part of the icon naming spec ;) [17:33] um which package? [17:34] http://standards.freedesktop.org/icon-naming-spec/latest.html [17:34] dobey: so if you're maintainer of gnome-icon-theme.. what's the point of making gnome-fs-share a symlink of folder-remote? [17:34] hyperair: compatibility for older apps that aren't updated to the new names yet [17:35] which is why there are so many symlinks in gnome-icon-theme [17:35] i see [17:35] development releases default to not enabling the symlinks though [17:36] hm [17:36] but i don't think anyone ever really sees the results of that [17:36] otherwise there'd probably be a lot more open bugs about icons [17:36] i see [17:48] eeejay, I went ahead and did . You're welcome to correct my terminology if I have it wrong. === mpt_ is now known as mpt === rickspencer3 is now known as rickspencer3-afk [20:18] Laney: the notify-osd problem is caused by gsd not notifying notify-osd upon state-change. [20:19] how come it works for some people? [20:19] it does? [20:19] that's surprising. [20:19] yes [20:19] popey has them, for example [20:19] that's how I found out they existed in the first place [20:19] hmmmm [20:20] the problem is that the bug encompasses two i should think [20:20] wait [20:20] i'm not sure [20:20] =\ [20:20] we're talking about notify-osd showing the icon of the media key you just pressed right? [20:21] time to take a peek at gsd patches [20:25] hey [20:26] I remember there is some agreement on the header to set for patch to track what they do, do you have a linkn, [20:35] hyperair: yeah [20:38] Laney: you're right. it should be in already [20:38] Laney: either way the buggy code is in notify-osd [20:38] sorry i meant gsd [20:39] gsd listens for those dbus events? [20:40] wrong. gsd _generates_ those dbus events [20:40] right [20:40] gsd is what sits between your xorg's media keys stuff and dbus [20:40] I know [20:40] banshee and gang connect to gsd via dbus [20:40] and it also is supposed to push a notification? [20:40] yes [20:40] k [20:40] if you dget the dsc, you can look at 16_whatever.patch [20:41] it looks like it pushes the notification... [20:41] + NULL, /* "notification-audio-play", */ /* PLAY_KEY */ [20:41] + NULL, /* "notification-audio-pause",*/ /* PAUSE_KEY */ [20:41] + "notification-audio-stop", /* STOP_KEY */ [20:41] + "notification-audio-previous", /* PREVIOUS_KEY */ [20:41] + "notification-audio-next", /* NEXT_KEY */ [20:41] for the media keys except play/pause [20:44] but it doesn't handle stop/prev/next for me [20:44] and the thing is, if it was an icon theme issue, then you should be noticing a blank popup [20:45] Laney: ^ [20:45] well I just get nothing [20:45] why don't you put some debugging traces in to see what gets called and returned? [20:46] hmm i could try [20:46] but actually i'm on intrepid [20:46] with gsd 2.24-x [20:46] with a backported patch of cuorse [20:47] heh [20:47] you should upgrade :( [20:47] but intel T_T [20:47] is it that bad? [20:47] everything 3d except compiz flies out of the window [20:47] yes it's bad [20:47] and it only affects some people [20:47] it might hit only those with agp + intel [20:47] i'm one of those badly hit [20:49] :( [20:52] * Laney cuts Evolution [20:52] it looks nice, but why does everything have to take so long? [20:52] ? [20:52] what's long? [20:52] evolution runs like a dog on my machine [20:53] evolution frequently hangs on mine [20:53] when i open it and it loads the mailbox, my machine grinds to a halt for 5 minutes [20:53] anything that involves any sort of disk activity on my desktop basically stops it from working [20:53] oh, mine's not that bad [20:53] just the application itself [20:54] mines terrible. the mouse cursor stutters and pauses for several seconds at a time and all the windows fade to gray [20:54] 1 minute+ delay from clicking "Reply" to actually getting a window, message text takes ages to download and so on [20:54] it seems that it queues up a load of network IO and your requests just get shoved at the end [20:55] my desktop takes nearly a full minute to open a gnome-terminal after i launched evolution [20:55] ah [20:55] i have no issues with network IO - mines all disk IO related [20:55] Laney: gsd is not firing off the required notification stuff [20:55] any idea why? [20:56] yop shows i get about ~70% iowait on my dual core when doing anything that involves any sort of disk activity [20:56] and that corresponds to my machine grinding to a halt [20:56] :( [20:56] yop -> top [20:56] lol [20:56] Thunderbird may look like arse, but at least it performs well [20:57] Laney: dunno. i need to figure out my own package first @_@ [20:57] hah [20:57] Laney: i don't know why, but the patch doesn't seem to be in my gsd, yet i'm getting the pretty volume notifications [20:57] damn weird. [20:57] volume started working with a recent update for me [20:57] chrisccoulson: run sqlite3 .db vacuum to fix that [20:58] Laney: it's worked for me on my ppa since the day i backported the patch. [20:58] aha! that's why [20:58] i was looking in the wrong gnome-settings-daemon directory [20:58] damn i feel stupid [20:58] chrisccoulson: upstream knows about the issue, that should be fixed for 2.26.1 before jaunty [20:58] i should git-ify everything [20:58] seb128 - i'll try that, but i think it might be a short-term fix. i have a general issue with anything disk intensive on this machine, so i can't entirely blame evolution ;) [20:59] chrisccoulson: right but evo tend to do a lot of io after time right now, that helps a lot [20:59] thanks, i'll give it a go [20:59] chrisccoulson: ie my evolution was hitting disk for 1 minutes on bugmails box before doing that, after it's some seconds [20:59] probably doesn't help that i have ~60000 unread messages;) [21:01] right, same for my bugmail box [21:01] they are read though [21:01] hmm [21:01] the patch is different [21:01] but that should not make a difference ;-) [21:01] i'll need to backport this patch then [21:01] what are you looking at changing? [21:02] looking into why gsd doesn't send media key notifications [21:03] Laney: can you do dbus-monitor 'interface=org.freedesktop.Notifications' and then start hitting your prev/next keys [21:03] it only has the ones for track change from Banshee [21:04] only huh [21:04] that means it's gsd'd fault [21:04] how about your eject key [21:04] don't have one [21:04] Laney: ctrl-f9 [21:04] set it to an arbitrary shortcut [21:04] k [21:05] yeah that works [21:06] seb128: Do you have any idea how I can repro this mapi crash without a server available? [21:06] can I install something to set one up easily? [21:06] Laney: no, just do the version update ;-) [21:06] or should I just update and ask the reporters to test [21:06] do that [21:06] that's how we do for exchange bugs [21:06] nobody around has an exchange server [21:07] fair enough [21:07] hey o/ I am updating evolution-mapi FYI [21:07] oh [21:07] ok! [21:08] gnome planet is a great ressource ;) [21:08] seb asked me earlier ;) [21:08] but nm [21:08] ok, sorry, didn't see it [21:08] you can do it if you wish :) [21:08] didrocks: I though you were in Lyon for the day [21:08] nah, I only got as far as uscan [21:08] lut didrocks [21:08] (it's already done by my side) [21:08] go for it [21:09] hello seb128 : yes, but it's just 1h30 from Annecy :) [21:09] I see you french guys have a national strike today [21:09] lazy sods ;) [21:09] Laney: yes, I saw a lot of people on strike in Lyon :) [21:11] it builds and installs sucessfully. As last time, I think that nobody have an exchange server around… :/ [21:11] yeah, just ask reporter to test it [21:11] Laney: I wasn't able to test it last time because of that and just uploaded it :/ [21:11] or jelmer/andrewsomething [21:11] they did the initial packaging; guess they tested it the [21:11] n [21:12] seb128 - after vacuuming, evolution opens in a few seconds ;) [21:12] thanks! [21:12] \o [21:12] * hyperair has an exchange account [21:12] chrisccoulson: you're welcome [21:12] Laney: jelmer asked to a friend IIRC, I asked him to do this before I sponsored it ;) [21:12] what's this mapi crashabout? [21:12] I'm letting it filter and process all new mail [21:12] to see if it gets faster after this [21:13] hyperair: it crashes after you authenticate [21:13] without fail? [21:13] sounds like it [21:13] at least for the reporter [21:13] nobody files bugs when it works ;) [21:13] does gnome-sound-properties start for everybody there? [21:13] yep [21:14] hyperair: I can make it available to my ppa if you wish. It fixes http://bugzilla.gnome.org/show_bug.cgi?id=574784 [21:14] Gnome bug 574784 in Mail "evolution-mapi can't fetch messages" [Normal,Resolved: fixed] [21:14] seb128: for me, it's ok [21:14] for me too [21:14] didrocks: i'm on intrepid =\ [21:14] we just got some bugs about the mixer and that one not opening now [21:15] Laney: what happens when you do the eject key test thing again? [21:15] hyperair: It ejects and I see the notification [21:15] strange, does he use virtualbox? (no sound in it) [21:15] Laney: strange, you actually see that notification? [21:15] mine shows a big eject logo [21:15] sure [21:15] traditional style [21:15] =\ [21:15] heh [21:15] you crazy backporting foo' [21:15] looks like i've got additional problems [21:15] * hyperair sighs [21:16] i have to check my notify-osd package again [21:16] seb128 - what are your thoughts on the nautilus auto-restarting issue? upstream seem to be fairly quiet about this. i had a look at it this evening and it looks fairly difficult to fix [21:16] hey somebody had to do it [21:16] chrisccoulson: I think we should set the autorestart to false if they don't fix it and let user who have a crash restartit [21:16] it's easy enough to open a place for example [21:17] that might be a safe compromise for now [21:18] intrepid didn't have the Autorestart key. it relied on setting the restartstyle hint with GnomeClient to a state dependant on whether it was drawing the desktop or not [21:18] #$%^ why do they change the damn capabilities strings EVERY SINGLE RELEASE?! [21:18] damn fickle pricks [21:18] i looked at the possibility of doing the same with eggsmclient, but it doesn't appear to have the features for this [21:18] every single patch has to be updated everytime there's a new release [21:19] it seems that eggsmclient only lets you set the restartstyle hint before connecting to the session manager [21:22] chrisccoulson: right [21:23] that's a known limitation, the bug fix would be to add the api to allow changing dynamically that value [21:23] yeah, that would be nice [21:23] probably a bit too late for this cycle though? [21:23] not sure, better to ask to vuntz [21:23] I would not bother for jaunty and just unset the autostart I think [21:23] vuntz is in a meeting :-) [21:24] vuntz: ;-) [21:24] what notify-osd capability changed this time? [21:24] they were supposed to have support for old and new naming in this version to make updates easier [21:24] " - Add compatibility checks to ease transition period for applications to [21:24] pick up the capability and hint name changes. (LP: #343553)" [21:32] Laney: this is seriously weird. i'm getting the next icon when ipress prev. [21:32] and nothing when i press next [21:32] haha [21:32] well that's a start, right? ¬_¬ [21:33] uint32 0 [21:33] string "notification-audio-next" [21:33] string "Previous" [21:33] string "" [21:33] very interesting [21:34] we're probably seeing some skewed enum or something [21:37] aha [21:37] that's right [21:37] pressing stop gives me.... previous [21:38] okay, what do enums start with? [21:38] 0 or 1? [21:38] oh wait a sec [21:38] i've an idea [21:38] does everyone else get some type of useful notification that updates are available in jaunty? [21:39] dobey: define useful notification? [21:40] seb128: i ran apt-get update, and there are a crapload of updates available, but there's no tray icon or anything. i'm having to run apt-get upgrade, or update-manager by hand to install them [21:40] yes, that's the expected behaviour [21:40] update-manager auto-opens once a week for normal updates now [21:40] how am i supposed to know when updates are available? [21:40] and once a day for security updates [21:41] ugh [21:41] when it auto-opens :( [21:41] dsign team decided that user are not upgrade maniacs [21:41] not all of them, sure [21:41] and that once a week for standard updates will do [21:41] you can turn the gconf key to have the old behaviour back if you want [21:41] what gconf key? [21:42] I think it's /apps/update-notifier/auto_launch [21:42] Laney: do you seriously get a notify-osd popup for eject? [21:43] rofl [21:43] I'm not lying to you :( [21:43] yay [21:43] seb128: thanks, that is much better [21:43] very strange.. [21:43] Laney: maybe you didn't restart something recently [21:43] I don't [21:43] that was working some days ago though [21:43] well I didn't restart after today's updates [21:43] you might still be running the old g-s-d or something [21:43] I'll do that though now [21:44] brb [21:47] Laney: could you do the dbus-monitor thing with eject? [21:48] nothing is sent [21:49] hyperair: It's broken now since I rebooted :) [21:49] loool [21:49] i knew it [21:49] hahaha [21:49] staring down the patch showed that eject was unhandled [21:49] so i just couldn't imagine why you had it working [21:50] now the very strange thing is that the enums seem to magically start from 1. [21:56] eject was working 2 days ago when I sponsored 2.25.92-0ubuntu2 [22:01] the previous and next actions are working fine here [22:01] only eject is not [22:04] seb128 - just looking at the g-s-d patch. in gsd_media_keys_notification(), there is this line: [22:04] if (media_key_icon[key] == NULL) return FALSE [22:04] EJECT_KEY is false [22:04] **NULL even [22:04] d-oh [22:04] right, I could swear I've seen it working though [22:04] it did used to work [22:05] why was it disabled? [22:05] it was not [22:05] they just don't have an icon for it apparently or something [22:06] * Laney wonders what he saw earlier [22:06] well it was working [22:06] the code changed though [22:06] that's right - media_key_icon[EJECT_KEY] is definately NULL [22:06] and the function just returns because of that [22:06] the code did change quite a bit since the last release [22:07] chrisccoulson: well [22:07] +static const char *media_key_icon[] = { [22:07] woah [22:07] NULL [22:07] NULL [22:07] NULL [22:07] etc [22:07] yep;) [22:07] I think they used the standard icon before [22:07] only stop, forward and back are populated [22:07] hyperair: I, er, have next/prev notifications now [22:07] but they changed notify-osd to use better defined icons [22:07] and they don't have one for eject [22:07] Laney: makes sense. i just figured out where i missed out [22:07] XRANDR_KEY was taken out between 2.24 -> 2.26 [22:07] that magical restart fixed it all [22:08] you should havek illed gnome-settings-daemon =\ [22:08] didn't know it got an update [22:08] know or check tbh [22:08] they have notification-device-eject.svg [22:08] * seb128 tries to use that in the enum now [22:10] * Laney misses play/pause too [22:10] right it's not in the enum either [22:10] yeah [22:10] there's no icon for pause [22:10] probably why both play/pause are disabled [22:11] would look odd seeing a notification for play but not for pause [22:11] chrisccoulson: actually i noticed my play/pause button triggering PLAY_KEY [22:11] or something [22:11] chrisccoulson: which means that should be a play/pause icon instead of just play [22:11] possibly [22:12] right [22:13] but yeah you should fix eject [22:13] it was working before the update [22:13] the previous patch worked with eject [22:14] right, it's just a matter to add the icon name in the enum, easy enough [22:14] that's good:) [22:17] hm [22:17] having looked at the Human icons, I feel like I'm missing out now :( [22:17] Laney: dpkg -L notify-osd? [22:17] seb128: There seems to be more in /usr/share/icons/Human/scalable/status/ [22:18] we don't want theme specific icons though [22:18] Laney - i'm not using human icons, but i created symlinks in the icon theme I use so i get all the notifications in my preferred theme [22:18] it looks really neat [22:18] so you get the "human" icons in your regular theme? [22:18] chrisccoulson: the notify-osd icons are in hicolor, should be used in any theme [22:19] i get all the notifications in my regular theme rather than the ones in hicolor [22:19] seb128: "This is a set of fallback icons for Gnome. Canonical icons are in the Human icon theme." [22:19] from the README [22:20] oh ok [22:20] didn't know ;-) [22:20] ? [22:20] eject is working now [22:20] Laney: are you sure that's right? [22:20] sure what's right? [22:20] i remember i was making noise about icons being in human [22:20] and then they shifted it all to notify-osd instead [22:20] there are different icons in Human [22:20] so now it's sitting in notify-osd =\ [22:20] there are? [22:20] and then some fallback ones there [22:21] the nice ones are in Human, and the fallback ones ship with notify-osd for those of us not using Human, or a theme that ships its own icons [22:21] either way, you should just make your icon theme depend on human instead of symlinking =p [22:21] there's a Depends line somewhre at the top of the index.theme file [22:22] i think i'm seeing the human ones [22:22] hyperair - i didn't symlink to human. i symlinked within the theme i use so i get the icons in my native theme;) [22:23] http://ubuntuforums.org/attachment.php?attachmentid=105750&d=1236531402 [22:23] aah [22:23] cool =p [22:23] chrisccoulson: what are the original icon names? [22:24] it depends what theme you use. i just searched in the theme until i found ones that looked correct;) [22:24] lol [22:25] i also did it for the indicator-applet icons too [22:25] although the indicator applet still doesn't do very much for me :/ [22:26] * Laney installs Jaunty on his Macbook [22:34] gnome-settings-daemon with eject action icon uploaded [22:34] I didn't add the play one because of the lack of pause icon for now [22:35] \o/ [22:35] erk, Jaunty live CD counts down to autologin now [22:36] you are the second user to report that this week [22:36] is there a bug? [22:36] I was assuming that xorg or gdm or gnome-session was crashing for mpt and bringing it back to gdm [22:36] ask on #ubuntu-devel maybe, I don't know [22:36] ok [22:44] woo the sun is rising [22:44] time for me to go to bed [22:45] 'night [22:46] seb128: what kind of abi guarantees do exist for _gtk symbols? no guarantee at all? [22:46] night [22:47] sleep well hyperair [22:47] asac: what _gtk symbols? [22:47] asac: the private _gtk symbols that are listed in some headers? [22:47] asac: they will have to always be there for gtk+ 2.x if they are publically exposed [22:47] asac: thanks. by the way, what about bug #248705 ? =p [22:47] Launchpad bug 248705 in evolution-data-server "Evolution Exchange does not authenticate to Exchange servers with a relative path in the form action, e.g. "owaauth.dll"" [Undecided,Fix released] https://launchpad.net/bugs/248705 [22:48] asac: [22:48] $ nm -D /usr/lib/libgtk-x11-2.0.so | grep _gtk [22:48] 000e5130 T hildon_gtk_file_chooser_install_properties [22:48] seb128: those exported in headers [22:48] asac: any example? [22:48] seb128: but for internal use: [22:48] seb128: look in gtkmodules.h [22:48] oh, those, no guaranty [22:48] seb128: good ;) [22:48] ie they rewrote the fileselector and that broke hildonfm which was using that for example [22:48] seb128: except the callbacks of course [22:49] i reawlly just ment tose _gtk symbols [22:49] also wonder why we export those in headers at all [22:49] seb128: as you showed they are even not exported ;) [22:49] in the fileselector case that was to write backends [22:49] only libgnomeui was using that for the gnomevfs backend [22:49] seb128: so what libs are using those now? [22:49] not sure in your case [22:49] ello [22:49] seb128: i mean they are not even exported anymore in the lib [22:50] seb128: so they shouldnt be used anywhere except in gtk [22:50] someone willing to help poor fellow lnx user with openVPN :D [22:50] asac: the fileselector ones? none, they dropped all that since they have gio in glib and don't need backends now [22:50] seb128: no ... i mean those gtkmodules things [22:50] NetSkay: -> #ubuntu [22:50] but well [22:50] i guess the answer is: they are not exported ;) [22:50] asac: I don't know about those sorry [22:50] or not sorry, I just don't know ;-) [22:51] but yeah, don't use private thigns [22:51] that's going to bite you [22:51] seb128: thats ok. i was just hacking around and thought about changing one of those, when i discovered that they are in a exported header [22:51] in code those "_gtk" things really looked like: not exported, nowhere used outside of gtk ;) [22:51] could be used for theme engines [22:52] seb128: but even if those symbols are not even exported. sounds unlikely [22:52] only static linking could allow access to them i guess [22:52] but anyway [22:53] i will see if i can find someone in #gtk+ or sommething [22:53] maybe tim knows ;) [22:53] asac: ask bratsche maybe [22:54] bratsche: ^^ _gtk symbols in gtkmodules.h ... why are they exported in a public header, but then not even visible in .so ? [22:54] bratsche: is it a bug that they are in a public header at all? [22:54] or is that best practice for gtk? === calc_ is now known as calc [23:01] asac: Hang on, let me take a look. Not sure if I know the answer but let me look really quick.. [23:02] bratsche: just look in the header ... the _gtk symbols really look private and even are commented as such. then they are not in nm -D /...gtk-x11... [23:02] thanks [23:03] seb128: so what damage about font sizes was reported on top of terminal, thunderbird ... ? [23:03] did you get anything else? [23:03] asac: That does seem like it should be a bug to me as well. [23:03] bratsche: ok great. [23:04] bratsche: i just was confused when i saw the header getting exported [23:04] Then again, I didn't realize gtkprivate.h was an installed .h file either. I was about to say maybe these should go there. [23:04] asac: some users complained about pidgin I think [23:05] seb128: ok. a bit change is ok and expected. if they claim huge differences i would like to know [23:06] * asac starts pidgin [23:06] asac: not that I know but I will keep an eye on such reports and let you know [23:06] so widgets look good here [23:06] seb128: great. [23:06] asac: I'll ask Matthias or someone about this tomorrow. Now I'm curious. [23:06] seb128: terminal turned out to be a code bug. they always converted to point base without even properly recalcuating leading to a size boost [23:10] why can't i turn on use burnproof in brasero? [23:10] its greyed out [23:10] my drive supports it [23:19] what does evolution use to display mail body content? is that a gtk widget? or something custom? [23:20] gtkhtml2 or gtkhtml3 or something like that. [23:20] I forget the version. [23:20] does that live outside of gtk tree? [23:20] Yes. [23:20] e.g. independent project? [23:20] ah [23:20] lets see if there is a bzr-mirror.gnome.org thing for it [23:21] asac_: gtkhtml3 [23:21] If you saw srag's blog post yesterday of the new Evolution-based mail client aimed at netbooks, they're using GtkWebkit for that. [23:21] asac_: source is gtkhtml3.14 [23:21] But Evolution itself has been stuck on gtkhtml3 for awhile [23:21] seb128: hmm. there is gtkhtml2 and gtkhtml [23:21] asac_: they plan to allow webkit for rendering in the next cycle but probably not for the editor [23:21] asac_: it's gtkhtml then [23:22] gtkhtml2 is libgtkhtml in ubuntu [23:22] seb128: Not for editing? I thought webkit supported that finally? [23:22] asac_: speaking about webkit did you ask about webkit 1.1? [23:22] seb128: gwibber folks dont know how to fix it [23:22] seb128: i asked them to investigate [23:22] so lets give them a few more day [23:23] seems webkit would break it completely [23:23] not sure whats the problem. maybe will try on my own if there is no progress === asac_ is now known as asac [23:23] bratsche: well srag said he has webkit rendering code (he did it for the the netbook software) but not for editing [23:23] Oh, bummer. [23:23] I missed that part I guess. [23:25] too bad that bzr-playground.gnome.org will probably go away when there is git [23:25] thats working so nice ;) [23:29] bratsche: [23:29] is that just for email display or you think you can get a working composer by then too? [23:30] mbarnes, only for display :-) [23:30] dont even think of it for composer for Evo.. its early [23:30] bratsche: that was the after meeting from this week [23:30] Ah, okay. [23:32] http://people.ubuntu.com/~brian/complete-graphs/openoffice.org/plots/openoffice.org-1day-new.png [23:33] just fell off the cliff :) [23:34] check that OUT!!!! [23:34] calc: you rocked the OO bug list down to zero! [23:35] unheard of [23:35] currently my upstream bug report numbers are 88.79% 86.21% 89.16% (working on the upstream linkage tomorrow) [23:35] how responsive is upstream to bugs for openoffice? [23:36] got alex to fix the ctrl-l ssh... mount error in gvfs today btw [23:36] seb128: sometimes very fast other times just ignores them [23:36] seb128: cool! :) [23:36] seb128: i have to test every bug though because they get upset if i send them unverified bugs, esp since we use ooo-build [23:37] way to calc! [23:37] congrats [23:39] rickspencer3: thanks :)