=== cody-somerville_ is now known as cody-somerville
[07:05] <dholbach> good morning
=== seb128_ is now known as seb128
[08:57] <dholbach> hey mvo, njpatel, seb128
[08:58] <seb128> hello dholbach
[08:58] <njpatel> morning  dholbach
[09:10] <mvo> hey dholbach, seb128, njpatel
[09:10] <seb128> hello mvo
[09:10] <seb128> mvo: how went the sponsoring yesterday? ;-)
[09:12] <seb128> mvo: just teasing you ;-)
[09:12] <mvo> *cough*
[09:12] <mvo> *cough*
[09:13]  * seb128 hugs mvo
[09:13] <seb128> ut crevette
[09:13] <seb128> lut
[09:13] <crevette> salut seb128
[09:26] <seb128> mvo: could you look to https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/210680 if that's a known issue?
[09:26] <ubotu> Launchpad bug 210680 in gedit "un able to upgrade" [Undecided,New]
[09:27] <seb128> "Package udev has broken dep on libdevmapper1.02"
[09:27] <seb128> upgrade issue
[09:29] <seb128_> re
[09:29] <seb128_> mvo: did you get the gedit bug and my question before I got disconnected?
[09:30] <crevette> yes we did seb128
[09:33] <seb128_> crevette: thanks
[09:41] <mvo> seb128_: looking
[09:43] <mvo> seb128_: comment added
[09:44] <seb128_> mvo: thanks
[09:46] <seb128_> mvo: the apt.log was not useful?
[09:46] <seb128_> <seb128> "Package udev has broken dep on libdevmapper1.02"
[09:46] <mvo> seb128_: no, that is just the resolver log
[09:46] <seb128_> dunno if you got that before the disconnect
[09:46] <seb128_> ok
[09:46] <mvo> seb128_: that is useful, but it should be fixed since a couple of days
[09:52] <mvo> seb128_: doing metacity sponsoring now
[09:55] <seb128_> mvo: cool
[09:55] <seb128_> mvo: did you read my comment about the firefox patch yesterday?
[09:56] <mvo> seb128_: this is something that should go upstream too I think
[09:56] <seb128_> the change for firefox?
[09:56] <seb128_> that's being discussed but the topic is not trivial
[09:56] <seb128_> the spec doesn't describe what should be done there
[09:56] <mvo> seb128_: I mean the fix for bug #199402
[09:56] <ubotu> Launchpad bug 199402 in metacity "gnome-appearance-properties crashed with SIGSEGV in meta_theme_get_frame_style()" [Medium,Confirmed] https://launchpad.net/bugs/199402
[09:56] <seb128_> ah
[09:56] <pochu> asac: I've got bug 178558 after X crashed yesterday. I restarted X after seeing the bug to see if that would solve it but it didn't help. I'm going to reboot just in case it helps, but I doubt it as restarting X didn't help
[09:56] <ubotu> Launchpad bug 178558 in xulrunner-1.9 "Firefox 3.0 makes everything annoyingly huge" [High,Fix released] https://launchpad.net/bugs/178558
[09:57] <seb128_> mvo: the patch is from the upstream maintainer so I think he'll commit to svn too if the didn't yet
[09:57] <mvo> seb128_: heh :) ok, cool
[09:57] <seb128_> s/the/he
[09:57] <asac> pochu: please a screenshot
[09:57] <pochu> sure, attaching in a minute
[09:57] <asac> pochu: and your screen dpi + the gconf dpi setting
=== seb128_ is now known as seb128
[09:58] <asac> ah ok that info is there
=== seb128 is now known as seb128_
=== seb128_ is now known as seb128
[10:03] <kwwii> pitti: did my gdm changes get uploaded? Sorry to bother but it is quite important
[10:04] <pitti> kwwii: I know nothing
[10:06] <pochu> asac: there they are
[10:06] <kwwii> pitti: erm, on Monday I put up a source package and asked you to upload it....let me get the links again
[10:09] <soren> 10:12 < kwwii> pitti: http://sinecera.de/ubuntu-gdm-themes_0.28.dsc,  http://sinecera.de/ubuntu-gdm-themes_0.28.tar.gz,  http://sinecera.de/ubuntu-gdm-themes_0.28_source.build,  http://sinecera.de/ubuntu-gdm-themes_0.28_source.changes
[10:09] <soren> I was looking through logs anyway.. :)
[10:09] <pitti> ah, I uploaded that, yes
[10:10] <pitti> $ rmadison -s hardy ubuntu-gdm-themes
[10:10] <pitti> ubuntu-gdm-themes |       0.28 |         hardy | source, all
[10:10] <pitti> :)
[10:10] <pitti> kwwii: I thought you literally meant 'gdm'
[10:10] <kwwii> pitti: lol, you don't want me touching gdm itself :-)
[10:10] <kwwii> thanks soren :-)
[10:10] <soren> :)
[10:20] <asac> pochu: thats just the zoom level?
[10:20] <asac> not dpi related imo
[10:20] <asac> did you try to rest the zoom level on that page to 0?
[10:21] <asac> s/rest/reset/
[10:23] <pochu> asac: ctrl+0 ?
[10:23] <pochu> doesn't change it
[10:24] <pochu> or ctrl-- will make it ugly
[10:24] <pochu> as in some fonts too small
[10:24] <pochu> e.g. the portlets
[10:25] <asac> pochu: maybe a non default font setup?
[10:26] <pochu> don't think so, haven't changed it
[10:26] <pochu> this is strage, why does only launchpad looks weird?
[10:26] <pochu> asac: I'll try moving out ~/.firefox/
[10:26] <asac> pochu: well crashes might have wierd effects on preferences
[10:26] <asac> yes
[10:26] <asac> try that
[10:27] <pochu> s/firefox/mozilla/
[10:29] <pochu> asac: nothing changed
[10:29] <asac> pitti: we ended up having a C application (by davidm) that does the basic transformation from po2xpi ... how can we make use of that in the langpack generator? do we need that packaged in the archive?
[10:29] <pochu> e.g. liferea still looks good, and in firefox only launchpad.net looks wrong
[10:29] <pochu> s/good/wrong/
[10:30] <asac> pochu: why do you think its too large?
[10:30] <pochu> the dpi in firefox is -1, which is the default
[10:30] <pochu> asac: did you see the screenshot? ;)
[10:30] <asac> yes
[10:30] <asac> i am really bad at look at such things though :(
[10:31] <pochu> this is clearly broken right now
[10:31] <asac> pochu: looks ok to me
[10:32] <asac> for me font in the main content area of bugs is considerably larger then the default font
[10:32] <asac> i remember that things were hard to read, so maybe thats intended
[10:32] <pochu> I haven't read any feed since the crash in Liferea because I can't have more than 2 lines in the window :p
[10:32] <pochu> well yesterday before the crash everything was fine
[10:32] <pochu> I could read launchpad.net, and liferea was nice
[10:33] <asac> pochu: didn't you say that liferea is back to normal now?
[10:33] <pochu> yes, and s/good/wrong/ too, sorry :)
[10:34] <pochu> look at http://launchpadlibrarian.net/13043699/Screenshot-1.png, I have a 22" wide screen monitor and I can't even see the entire description of the bug report now
[10:34] <pochu> the portlets are fine for some reason, but the description and that is big
[10:34] <pochu> is *huge* :)
[10:35] <pochu> they should be like the fonts at ubuntu.com in the same screenshot
[10:35] <pochu> asac: may I reboot to see if it changes anything?
[10:35] <asac> yes... portlets are fine
[10:35] <asac> which makes me think that everything is fine
[10:35] <asac> go to your gnome appearence dialog and see what fonts are configured there
[10:35] <pochu> ok
[10:35] <asac> maybe its also related with some theme package upgrades landed recently ... who knows
[10:36] <pitti> asac: depends which part should do the XPI generation, a script that you run yourself, or LP translations
[10:36] <pochu> Sans, 10
[10:36] <asac> pitti: i think the idea is to ship translations in main language-support-XX
[10:36] <pochu> no visual effects
[10:36] <pitti> asac: if you want to run it on rookery or so, we don't need it packaged (would be nice to do so for intrepid, of course)
[10:36] <asac> that means that its done in LP translations, right?
[10:36] <pochu> hmm, wait, I have metacity compositor enabled
[10:36] <pitti> asac: right
[10:36] <asac> ok, then thats it (unless we find anything blocking)
[10:36] <pochu> I'll disble it to check
[10:36] <pitti> asac: well, not necessarily; we can do it outside until Rosetta learns to put xpi into the exported tarballs
[10:37] <pochu> well, before the crash it was enabled too and was working fine, but it could be that it's buggy
[10:37] <pochu> I don't know why it would only affect xulrunner applications though ;)
[10:37] <asac> pitti: yes. thats what i ask. i think you already run something somewhere :) ... and i wonder if you need a package if we want that hooked in there ;)
[10:38] <asac> pitti: in intrepid i want to get that into launchpad directly of course
[10:38] <pochu> hmm, metacity has crashed when disabling the compositor... it has disabled it though
=== dholbach_ is now known as dholbach
[10:41] <asac> pitti: i can also produce a directory where the compiled tools are included (along with some meta info we still need in hardy)
[10:42] <pochu> asac: this still looks bad, I'm going to reboot, hopefully it changes anything
[10:42] <pochu> is there any xulrunner dir somewhere?
[10:42] <pochu> or only .mozilla/firefox/ ?
[10:42] <pochu> .mozilla/ ?
[10:42] <asac> pochu: not that i am aware of
[10:42] <pitti> asac: if you could put all that on rookery somewhere, that would be good; then I can integrate it into the langpack-o-matic cronjobs to call your scripts and put the resulting XPIs into the langpacks
[10:42] <pochu> ok, brb
[10:43] <seb128> re
[10:43] <pitti> asac: maybe you can do that installation, and write Arne and me a mail what to call and which files to put into which directories?
[10:43] <asac> pitti: can you run a script for each language with the following arguments: 1) language 2) path_to_extracted_translation_tarball 3) debian/$language_package_name ?
[10:44] <seb128> kwwii: did you change the gdm human theme which lists users in the new version?
[10:44] <asac> or isn't that put into packages?
[10:44] <seb128> kwwii: we got several users having gdm not starting using this theme since recently
[10:44] <kwwii> seb128: yes, I included bersace's changes
[10:44] <pitti> asac: I can (although you should be able to figure out everything from just the path to the extracted source package)
[10:44] <seb128> kwwii: did you try it?
[10:44] <pitti> asac: but I'm happy to extract the source pakcage name and language code for you
[10:45] <kwwii> seb128: hrm, if the list theme does not work then someone should beat up bersace
[10:45] <seb128> kwwii: what was the change about?
[10:45] <asac> pitti: well ... thats too much logic imo
[10:45] <kwwii> seb128: just a visual change to keep it inline with my normal gdm theme changes
[10:45] <seb128> hum
[10:45] <kwwii> when he comes online I will ask him about it
[10:45] <pitti> asac: WDYM with debian/$language_package_name  ?
[10:46] <seb128> kwwii: ok, thanks
[10:46] <kwwii> ouch, is it bad when a system update fails while creating the initramfs :p
[10:46] <pitti> asac: phone call?
[10:53] <pochu> asac: nothing has changed. But I've looked at the log of the X crash (which should have the DPI I had before the crash, when everything was fine), which I attached to bug 190418, and it's the same I have now, so it's not X's fault. Also, I've logged as a different user and everythings'f fine there (yelp and firefox/launchpad.net). So there's something in my profile... I guess it's safe to assume it's not Xulrunner's fault?
[10:53] <ubotu> Launchpad bug 190418 in xserver-xorg-video-intel "[965GM]  Server crash when starting totem-xine to play a DVD" [High,Confirmed] https://launchpad.net/bugs/190418
[10:53] <asac_> pitti: for each application and language combination i have two files, like xulrunner-de.jar xulrunner-de-chrome.manifest ... should i put them in /usr/share/locale-langpack/de/ or /usr/share/locale-langpack-chrome/
[10:54]  * pochu moves .gconf/ and .gnome2/ out
[10:54] <asac_> (those will be linked to the appropriate application chrome directories then)
[10:55] <pitti> asac_: can we have a phone call to discuss this?
[10:55] <asac_> ok. after lunch?
[10:55] <seb128> mvo: ok, so you didn't consider the firefox change while doing the upload
[10:56] <pochu> brb
[10:56] <seb128> asac: you can upload the metacity change to fix firefox workspace switching issue if you want
[10:56] <pitti> asac_: sure
[10:56] <seb128> asac: that seems to be what users expect and the easier way to fix the issue
[10:56] <asac_> pitti: good. when will you do lunch?
[10:57] <pitti> asac_: around 13:30 probably, when my wife comes back from uni
[10:57] <asac_> seb128: are the negative implications for other applications?
[10:57] <asac_> pitti: ok, ill do the same then :)
[10:58] <seb128> asac_: not sure, redhat is using the change and seems they didn't get complains
[10:58] <seb128> asac_: we can give it a try and revert if users start screaming
[11:00] <mvo> seb128: no, sorry. will look at that next
[11:01] <seb128> mvo: that's alright, no need to do another upload, let asac decide since that's mainly a firefox issue
=== asac_ is now known as asac
[11:01] <mvo> ok
[11:08] <pochu> asac: bah, it was .gnome2/monitors.xml
[11:08] <pochu> everything's looks fine now :)
[11:08] <pochu> sorry for making so much noise... i'll comment on the bug to make clear everything's fine
[11:08] <pochu> http://paste.ubuntu.com/6354/ <--- the culprit file
[11:09] <pochu> I can't see what's wrong there though, but everything's working perfectly after removing it and logging in
[11:14] <asac> popey: ok. thanks
[11:15] <asac> oops, pochu ^^
[11:16] <popey> :)
[11:20] <seb128> pochu: what was the bug?
[11:21] <seb128> the effects rather
[11:24] <pochu> seb128: liferea, yelp, devhelp, ephy, firefox-3 (all xul-based) had large fonts
[11:24] <pochu> but for firefox, it was only affecting launchpad.net pages
[11:24] <pochu> seb128: http://launchpadlibrarian.net/13043699/Screenshot-1.png, http://launchpadlibrarian.net/13043689/Screenshot.png
[11:39] <pochu> seb128: did you see my reply?
[12:05] <seb128_> pochu: no
=== seb128_ is now known as seb128
[12:09] <pochu> 12:24 <     pochu> seb128: liferea, yelp, devhelp, ephy, firefox-3 (all xul-based) had large fonts
[12:09] <pochu> 12:24 <     pochu> but for firefox, it was only affecting launchpad.net pages
[12:09] <pochu> 12:24 <     pochu> seb128: http://launchpadlibrarian.net/13043699/Screenshot-1.png, http://launchpadlibrarian.net/13043689/Screenshot.png
[12:09] <seb128> weird
[12:10] <pochu> it started after an X crash, and after removing .gnome2/monitors.xml it's been fixed
[12:12] <pochu> asac: I could attach a screenshot with everything fixed so you see the difference ;)
[12:13] <pochu> luckily the intel driver is really more stable than it was at the beggining of the hardy cycle...
[12:13] <asac> pochu: no i don't mind ;)
[12:13] <pochu> I assumed that :)
[12:28] <seb128> kwwii: bug #210538
[12:28] <ubotu> Launchpad bug 210538 in ubuntu-gdm-themes "gdm hangs after theme upgrade and reboot" [High,Confirmed] https://launchpad.net/bugs/210538
[12:29] <seb128> kwwii: the theme upgrade seems to break gdm for all the users running it
[12:29] <seb128> http://ubuntuforums.org/showthread.php?t=742511 too
[12:33] <seb128_> re
[12:34] <seb128_> I was saying
[12:34] <kwwii> seb128: ouch that sucks
[12:34] <seb128_> asac: btw don't bother too much fixing epiphany to work with xul1.9 since they will drop the xulrunner support soon anyway
[12:34] <seb128_> asac: having the invalid certifcate issue fixed in hardy would be still nice though ;-)
[12:34] <seb128_> kwwii: indeed
[12:34] <seb128_> kwwii: testing before uploading is a good idea usually ;-)
[12:34] <kwwii> bersace takes care of that theme
[12:34] <seb128_> can you get him to fix it?
[12:34] <kwwii> definitely
[12:35] <seb128_> I don't blame anybody, and that's not the default theme
[12:35] <seb128_> but fixing it today would be nice
[12:35] <kwwii> if not I will have to fix it myself or remove it
[12:35] <kwwii> I will make sure it gets taken careof
[12:35] <seb128_> well, we can revert to the previous version
[12:35] <seb128_> that should be easy
[12:35] <seb128_> but right, if you can fix it better
[12:35] <kwwii> seb128_: it seems my latest changes did not make it in anyway, so I am working on a new theme package anyway
[12:36] <seb128_> ok, good
[12:38] <asac> seb128_: yes, i read that. however, i read as well, that even 2.24 might not be done so in worst case even the next release will be xul
[12:41] <seb128_> asac: right
[12:58] <pochu> I hope webkit is in a sane state as to be in main for Intrepid, there's a new contributor in Liferea which has been fixind and improving the webkit backend a lot
[15:01] <gNewPower> hi everybody. I just set up a computer with the latest version of Ubuntu and all my fonts lack "crispness" (for lack of a better word). they look kind of blurred. any idea of what might be causing this?
[16:26] <Keybuk> I hate DST
[16:42] <vuntz> seb128__: stop disconnecting, I can't talk to you in a query if you do this!
[16:42] <vuntz> :-)
[16:43] <seb128__> vuntz: tell that to orange!
[16:45] <kwwii> seb128__: I found some more links that I needed to add so there is another human icon theme package coming soon
[16:45] <kwwii> seb128__: and the human list error is simply freaky...cannot figure out why it is b0rked
[17:00] <seb128__> kwwii: weird
[17:00] <seb128__> kwwii: https://bugs.launchpad.net/ubuntu/+source/ubuntulooks/+bug/210837 btw
[17:00] <ubotu> Launchpad bug 210837 in ubuntulooks "Colors of human theme are displayed incorrectly in gnome-appearance-properties" [Undecided,New]
[17:00] <seb128__> kwwii: the theme preview is incorrect since the ubuntulooks changes
[17:09] <kwwii> seb128__: apparently that is a bug in the way the previews are made
[17:10] <kwwii> seb128__: when I have the metacity with the gtkrc together it shows up right
[17:11] <seb128__> together?
[17:11] <tedg> So, let's say someone has their laptop configured to suspend on lid close, but there is another application inhibiting GPM, should we blank the screen?
[17:11] <kwwii> yes, like a normal theme, with the index.theme in the main dir and the gtkrc and metacity in subdirs
[17:12] <seb128__> kwwii: that's how it is now, no?
[17:12] <seb128__> tedg: I would say that the screen should always be cut when the lid is closed, what is the point to use energy for something which you can't look at anyway?
[17:13] <seb128__> -which
[17:13] <kwwii> seb128__: erm, right in the installed system they are together
[17:14] <kwwii> gosh, I just love packaging
[17:14] <tedg> seb128__: Yeah, my only worry is that someone may perceive that as suspending, throw the laptop in a backpack and destroy their hardware.
[17:14] <tedg> seb128__: I don't know if we're thinking for them in that case.
[17:14] <seb128__> tedg: well if they don't look they will not notice that the screen which is closed is still on anyway
[17:14] <mvo> seb128__: /etc/gconf/gconf.xml.defaults/%dconf-tree.xml is something we do not use, right?
[17:15] <mvo> or do we?
[17:15] <seb128__> mvo: dconf? is that the new desrt thing ;-)
[17:15] <mvo> meh, typo
[17:15] <seb128__> mvo: that's a bit complicated
[17:15] <tedg> seb128__: True, and I guess by default we do play a sound...  it's a tough situation.
[17:16] <seb128__> mvo: that's what upstream use, we do use /var/lib/gconf/defaults though
[17:16] <tedg> seb128__: I think we should blank, let's see what bugs that generates ;)
[17:16] <seb128__> tedg: it's not though, just cut the screen on lid close, there is not a lot you can't do for people who don't look at what they are doing
[17:16] <mvo> seb128__: I look at a gutsy->hardy upgrade <-> fresh hardy install diff currently and for the upgrade there is this gconf.xml.defaults/%gconf-tree.xml stuff with lots of gthumb in it
[17:17] <seb128__> mvo: but /etc/gconf/gconf.xml.defaults is what broken packages (which don't use dh_gconf) and sys admins will use
[17:17] <mvo> and I was wondering if that is something we need to worry about
[17:17] <mvo> aha!
[17:17] <mvo> gthumb in gutsy?
[17:17] <tedg> Well, no, the problem is apps like Rhythmbox don't really tell you that they're inhibiting the power manager.  And as they all add those features (which they should) people will be surprised by what happens.
[17:17] <seb128__> mvo: dunno, let me get the sources
[17:17] <mvo> and gnome-translate it seems uses /etc/gconf/schemas/ too
[17:17] <mvo> only worry about it if its something important
[17:18] <tedg> Perhaps what we really need is something to pop up in the notification area when we're inhibiting.
[17:18] <mvo> I also have some stuff in /etc/gnome/config after the upgrade but not on a fresh install
[17:18] <mvo> Motif.ad, Tk.ad etc
[17:18] <tedg> Wow, I think I might have actually come up with a *good* use of the notification area ;)
[17:21] <dashua`> tedg: I'm running Hardy on a Dell XPS m1530 and suspend works upon closing lid, but upon resume there is a blank screen which you have to blindly type in your password (nvidia driver)
[17:21] <dashua`> Need me to test anything, let me know?
[17:21] <kwwii> seb128__: the really freaky thing about the preview stuff is that the metacity theme is exactly the same
[17:21] <kwwii> seb128__: same as before, I mean
[17:23] <seb128> re
[17:23] <seb128> so
[17:23] <tedg> dashua`: By blank screen do you mean no graphics or no backlight?  If it's no graphics that either an X or compiz thing, if it's no backlight it might be a GPM thing.
[17:23] <seb128> kwwii: the colors slightly changed in the workspace switcher applet too, the "non active widget" color is white white now when it used to be a bit grey I think, and the orange is rather flashy it was almost brown before
[17:24] <seb128> tedg: so as said I would just not stop suspend by default and let people enable the option if you are concern about the surprise effect
[17:24] <kwwii> seb128: yes, the new theme with choosable colors is hard to make perfectly like it used to be
[17:24] <seb128> mvo: looking to those
[17:25] <dashua`> tedg: Just a white screen.
[17:25] <kwwii> seb128: perhaps we should just use the old version and forget the GUI configurable stuff
[17:25] <seb128> kwwii: you did a quite good job compared to the version I tried some cycles ago
[17:25] <dashua`> I'm running compiz as well.
[17:25] <seb128> kwwii: out of the workspace applet I didn't really notice a difference
[17:25] <seb128> kwwii: oh, no, the preview is likely something easy to fix, and otherwise I think there is no notable difference
[17:26] <seb128> kwwii: I was just mentionning the workspace switcher in case one color was not defined or something
[17:26] <kwwii> seb128: the freaky thing is that when I put the theme in my .themes dir it looks correct
[17:26] <seb128> weird
[17:26] <kwwii> the preveiw I eman
[17:26] <kwwii> s/eman/mean
[17:26] <seb128> what do you copy?
[17:27] <seb128> mvo: what was the packages? gthumb and gtranslator?
[17:27] <tedg> dashua`: My guess would be compiz on that.  I think that they must be putting some sort of overlay on.  I've seen that on my nVidia card also (doesn't seem to be happening now, but I didn't fix it).
[17:28] <tedg> dashua`: That was happening to me, but it hasn't in a while, but I've been running metacity.
[17:28] <kwwii> seb128: hrm, I take that back...it does look different, let me look at this closer and get back to you
[17:28] <seb128> tedg: new gnome-screensaver tarball available btw
[17:28] <dashua`> tedg: Yeah, I figured it either related to compiz or the nvidia driver.
[17:29] <seb128> mvo: the hardy gthumb postinst has a case to fix the bug, maybe the transition version need to be updated for ubuntu though
[17:29] <tedg> seb128: Man, let me read my e-mail first ;)
[17:30] <seb128> tedg: I just read the svn tag on #commits ;-)
[17:30] <tedg> seb128: Could you sponsor the GPM package in my PPA?
[17:30] <seb128> tedg: sure
[17:30] <tedg> seb128: It should be 2.22.1-1ubuntu2
=== fta_ is now known as fta
[17:54] <mvo> seb128: that would be the line with --makefile-uninstall-rule ?
[17:54] <seb128> mvo: right
[17:54] <seb128> mvo: the 3 lines rather
[17:54] <mvo> that looks pretty old, 2.6.9
[17:55]  * mvo tests it
[17:57] <seb128> ok, time for diner, see you later
[20:32] <pochu> seb128: hi, could you look at this RFS? The patch is from upstream, and has got confirmation that it solves the crash in the bug report. i didn't test it because I don't use Evo, but it builds and installs fine: http://emilio.pozuelo.org/~deb/tracker.debdiff
[20:33] <seb128> pochu: sure, thanks for working on the change
[20:34] <pochu> thanks for looking into it :)
=== onestone_ is now known as onestone
[20:59] <vuntz> can anyone check if http://bugzilla.gnome.org/show_bug.cgi?id=513138 still happens in hardy?
[21:01] <seb128> vuntz: looking
[21:01] <seb128> vuntz: no it's fixed
[21:02] <vuntz> seb128: thanks
[21:02] <seb128> you are welcome
[21:13] <pochu> seb128: thanks for the upload
[21:14] <seb128_> pochu: you are welcome
=== seb128_ is now known as seb128
=== seb128_ is now known as seb128