[06:47] <Abdullah9> any one can help me ?
[06:50] <Abdullah9> so no help  ?
[07:09] <rugby471> hi
[07:20] <Abdullah9> any one?
[07:24] <rugby471> MadsRH: I saw your software store icon
[07:24] <rugby471> pretty cool
[07:24] <rugby471> however I think the ubuntu logo needs a border and to be smaller
[08:06] <MadsRH> rugby471: hi, I think you are right - I really hate drawing vector :P. Sebastians look *much* better. Besies, I'm not sure who well the shopping bag idea works a icon for a software store :-/
[08:06] <rugby471> hehe
[08:07] <rugby471> the idea  you had of the application wall behind (like the blackberry store) will work really well
[08:07] <rugby471> MadsRH: you should try it
[08:07] <MadsRH> rugby471: What color would you suggest?
[08:08] <rugby471> different colors for the apps in the background
[08:08] <rugby471> and then experiment with what to put infront of them
[08:08] <rugby471> the smaller icon sizes would have to be a 2d perspective
[08:09] <rugby471> but for the larger ones you could have the sideview 3d perspective
[08:15] <MadsRH> rugby471: that's a good idea. I saw also thinking about a shopping cart http://dl.getdropbox.com/u/175241/tango_basket.png
[08:16] <rugby471> yeah that is also a good dea!
[08:16] <rugby471> just experiment I know you will produce a great one :-)
[08:16] <rugby471> dea > idea
[08:17] <MadsRH> rugby471: not sure I will spent more time on it. I think I'll leave icon to the icon creators ;-)
[08:19] <rugby471> madsRH : that's fine :-)
[08:19] <rugby471> MadsRH: I might have a go at it myself :-)
[08:19] <MadsRH> rugby471: You should
[08:20] <MadsRH> rugby471: ...do that :-D
[08:20] <rugby471> :-) thx
[10:38] <mac_v> rugby471: lol! it was your folder we'v used for Breathe right?
[10:38] <rugby471> yup :-)
[10:39] <mac_v> rugby471: hehe , looking back at my question "Do you know how to export to png" ! lmao ;)
[10:39] <rugby471> yeah :-)
[10:39] <rugby471> I was going to tell you, but I thought you might find out :-)
[10:40] <mac_v> oops... well played ;)
[10:40] <rugby471> hehe
[12:07] <Laney> rugby471: are you aware that the memaker update is broken?
[12:08] <Laney> http://pastebin.com/m10c4ab5d
[12:11] <rugby471> damn it
[12:11] <rugby471> Laney: thanks I thouight that bug had been fixed :-)
[12:12] <Laney> no
[12:12] <rugby471> I shall fix it right away
[12:12] <Laney> i'm testing a fix
[12:12] <Laney> ok
[12:12] <rugby471> oh
[12:12] <Laney> your fix is probably better
[12:12] <Laney> i was just going to make it not build for 2.4
[12:12] <rugby471> wait a min
[12:13] <rugby471> Laney: the fix is described here :https://bugs.launchpad.net/ubuntu/+source/memaker/+bug/214401
[12:14] <Laney> yeah i thought about doing that
[12:14] <rugby471> Laney : could you do your fix? i don't have time to work on a patch today
[12:14] <Laney> fixing it properly is a better idea
[12:15] <rugby471> http://launchpadlibrarian.net/15979113/fix_install_errors.patch
[12:15] <Laney> yes
[12:15] <rugby471> this is the type of fix we need
[12:15] <rugby471> can you fix it like that?
[12:15] <Laney> already done
[12:15] <rugby471> thx
[12:15] <Laney> please fix it in trunk
[12:16] <rugby471> I shall mention your contribution on the mailing list
[12:16] <rugby471> sure
[12:16] <rugby471> will you upload the packge (or is it uploaded?)
[12:16] <Laney> very soon
[12:16] <rugby471> thanks
[12:16] <rugby471> well I'll have lunch now and then i'll fix it in trunk
[12:16] <rugby471> see ya
[12:42] <rugby471> Laney: is it going all right with that bug?
[12:42] <Laney> yeah
[12:42] <Laney> i hit upon an sbuild bug and started investigating
[12:43] <rugby471> I have fixed it upstream in the trunk branch
[12:44] <Laney> ok
[12:45] <rugby471> do you need me to release 1.5.1 or can you just do the patch as a dpatch?
[12:47] <rugby471> Laney:?
[12:47] <Laney> already uploaded
[12:47] <Laney> its not worth a release imo
[12:48] <Laney> by the way the maintainer of the package is still listed as pete savage
[12:48] <Laney> so we really shouldn't be uploading it
[14:03] <rugby471> ah okay
[14:03] <rugby471> Laney: should I tell pete what has happened?
[14:04] <Laney> just confirm he's not interested in it any more
[14:04] <Laney> and fix it for the next time
[14:06] <mac_v> awalton: hi... got a min? could you have a look at a weird nautillus bug?
[14:06] <awalton> mac_v: #?
[14:07] <mac_v> awalton: https://bugs.launchpad.net/bugs/416251 , i'v also filed it upstream
[14:09] <awalton> ugly problem.. but the label thing is a red herring.. changing the label is just causing the icon view to be updated by the file monitor callback
[14:11] <awalton> it's probably related to the problem we've seen with nautilus loading whole video files into memory and crashing
[14:12] <awalton> someone provided a really good trace for that bug the other day, but I haven't had time to go back and look at it until now
[14:12] <mac_v> awalton: do you have the bug # , pls :)
[14:13] <mac_v> so i could follow it
[14:13] <awalton> ehh.. not off the top of my head no, I just got a new laptop and I'm in the process of transfering everything over
[14:13] <awalton> but searching lp for "nautilus video crash" should find you it or one of its half dozen duplicates
[14:13] <mac_v> oh... ok
[14:13]  * awalton is looking for it now
[14:15] <mac_v> also , i find nautilus has memory leaks in Karmic , when i keep the system running for long hours , it starts to consume memory... how do i debug it? run valgrind from the begining?
[14:16] <awalton> pretty much. kjmaaras has a pretty neat setup where he runs the whole session in valgrind, it might be worth tracking him down for that
[14:17]  * awalton just nautilus -q && valgrind (ton of options) nautilus
[14:17] <mac_v> so i have to run valgrind as root right?
[14:17] <awalton> shouldn't have to, no
[14:18] <mac_v> oh ok... was just wondering about the desktop
[14:20] <awalton> gnome bug 588446 is the large video crashing bug
[14:21]  * mac_v reads
[14:22] <awalton> I think that one's being caused by one of the more recent changes to the thumbnailing code where we simply use the mime types returned by gdkpixbuf as capable of being thumbnailed, I think for whatever reason it's being stupid and thinking video can be thumbnailed that way
[14:22]  * awalton originally thought it was attempting to make a text thumbnail of it, but that was proven wrong by the newer trace
[14:24] <mac_v> yeah that looks like the video thumbnail part of my bug...
[14:25] <mac_v> awalton: BTW why has the desktop layout been changed? why are all icons smaller now? and the thumbnails are not shown at a fixed size of 96px?
[14:25] <mac_v> rather at their own sizes if smaller than 96px
[14:25] <awalton> someone poking with gconf keys?
[14:26] <awalton> that's all controlled by gconf, you can set the thumbnail size and the icon size independently (I have them set to equal, looks better that way IMO)
[14:26] <mac_v> are you asking if i changed the gconf?
[14:26] <awalton> you, ubuntu, someone
[14:27] <mac_v> awalton: actually i havent changed gconf manually for that , maybe th esetting has now been changed in the gconf... hehe nice to know its change-able somewhere ;)
[14:27] <awalton> if you're wondering about the borders around small images (like e.g. icons), that was a bug (and a regression) that we had a patch for
[14:27] <mac_v> yeah^
[14:29] <awalton> that was a regression that sneaked in whenever alex did the gio migration, and iirc jaap fixed it.
[14:30] <mac_v> nice... thanx for the info... , regarding my Karmic memory leak bug , bug #417589 , do i have to file this upstream or is lp enough?
[14:31] <awalton> usually fine to leave it as an lp bug until we can track down a cause or reproduce it on e.g. fedora
[14:31] <mac_v> oh... ok , thanks for the help :)
[14:31] <awalton> even that isn't needed sometimes, if I'm looking through lp bugs and find an easy fix I'll upstream it.
[14:31] <mac_v> ah , nice
[14:37] <mac_v> awalton: i run valgrind using > $ nautilus -q && G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log nautilus
[14:37] <mac_v> i get this error > (nautilus:1783): GLib-GIO-WARNING **: Could not initialize inotify
[14:38] <awalton> odd error, haven't seen that one.. but it shouldn't stop you from using nautilus
[14:38] <awalton> there's always the polling monitor and fam/gamin (idk if ubuntu builds with fam support though, but I do personally)
[14:38] <mac_v> i can use nautilus , but valgrind stops
[14:38] <mac_v> thats another problem i have ! when i logout or shutdown , nautilus keeps telling that old file operations are still running
[14:39] <awalton> mac_v: fixed that one monday
[14:39] <awalton> or tuesday.. just hasn't made it to ubuntu yet
[14:39] <mac_v> oh...
[14:39] <awalton> bug 419184
[14:40] <awalton> (I was apparently off a couple of days, looks like thursday)
[14:41] <mac_v> hehe ;)
[14:41] <mac_v> hmm... now i'm stumped about valgrind :(
[14:42] <awalton> it might be yet another case of the pathological session manager respawning nautilus.. you could try chmod -x /usr/bin/nautilus, killing it, adding back the exec bit and then running it in valgrind
[14:42] <awalton> I think that's what davidz does
[14:43]  * awalton has been dev'ing on intrepid, missing out on evilness like that.
[14:56] <mac_v> awalton: \o/ that worked just perfect :) , now valgrind is working... of course for some reason i got kicked out of the session , now valgrind is running
[14:56] <mac_v> thanks :)
[14:57] <awalton> mac_v np
[15:48] <Laney> rugby471: f-spot debs soon
[15:48] <Laney> will you test for me?
[15:48] <rugby471> sure
[15:49] <rugby471> Laney: hehe I'll do anything to get that deb uploaded :-)
[15:49] <Laney> good
[15:49] <Laney> builds
[15:49] <Laney> i need to add the other patch
[15:51] <Laney> just sweated it out over forest's narrow victory
[15:52] <rugby471> hehe
[15:58] <Laney> rugby471: what is the effect of your patch on existing users?
[15:58] <Laney> no change, right?
[15:59] <rugby471> correct
[15:59] <Laney> good
[15:59] <rugby471> if the gconf settting for where the photos should be stored has been set, then it does nothing
[15:59] <rugby471> however if that gconf entry has not been set
[15:59] <rugby471> then it does x, y and z...
[16:02] <Laney> "
[16:02] <Laney> "
[16:02] <Laney> Wow. A hard-coded photos folder.
[16:02] <Laney> Cultural imperalism at its finest.
[16:02] <Laney> Please remove f-spot from Ubuntu main. It clearly doesn't follow guidelines.
[16:02] <Laney> At least not when it comes to respecting languages and culture.
[16:02] <Laney> "
[16:02]  * Laney rolleyes
[16:29] <rugby471> Laney: hehe yeah
[16:30] <rugby471> that guy commented upstream
[16:30] <rugby471> welll when I say commented, he ranted
[16:30] <rugby471> broke the code of conduct, got banned and his comments removed :-)
[16:31] <mac_v> rugby471: they do that o.0,ban if you rant , cooool
[16:31] <rugby471> ironic thing is, his rant made the bug getting fixed go even slower
[16:31] <mac_v> lp should have a feature like that
[16:31] <Amaranth> mac_v: Ever since we signed onto a GNOME Code of Conduct people not following it get reprimanded
[16:31] <rugby471> well I didn't see it, but if he broke the Coc he obviously was quite out of line
[16:32] <rugby471> mac_v : I think the admins can do it
[16:32] <Amaranth> Seems at least once a month someone gets banned from a GNOME mailing list for such things
[16:32] <mac_v> Amaranth: we have the COC , but could someone ban the guys ranting on th epapercut bugs !
[16:33] <Amaranth> mac_v: hehe, I think I'm getting a rant on the compiz shadow fix too
[16:33] <mac_v> because of papercuts , lp has become worse than the comment section of blogs
[16:33] <Amaranth> Either this guy has a legitimate bug I can't reproduce or he just wants the old style back because it made sense with his autohide panels
[16:34] <mac_v> bug #
[16:34] <mac_v> ?
[16:34] <Amaranth> he originally seemed upset we were ruining his experience to make users of awn and gnome-do happy due to a misunderstanding
[16:34] <Amaranth> bug 421056
[16:35] <Amaranth> I guess I should mark it back to incomplete
[16:35] <Amaranth> when I took the bug I wasn't near my ubuntu machine to see what he meant and figured it was a silly mistake on my part
[16:36] <mac_v> ooh , i forgot about that patch , still havent removed the exclusion :)
[16:37] <mac_v> Amaranth: perfect! works like a charm :)
[16:39] <mac_v> Amaranth: why havent you marked the bug fix released? just forgot? shall i ?
[16:40] <Amaranth> mac_v: which?
[16:40] <mac_v> Bug #91786
[16:40] <Amaranth> Thought I included the LP: # thing in my changelog :/
[16:41] <Amaranth> wait, is that package out?
[16:42] <mac_v> i'v seen the changelog entry a few days back , let me get it , i can see the patch works
[16:42] <Amaranth> mac_v: hey, just in time for round 9
[16:42] <Amaranth> was hoping to get that one fixed ahead of time ;)
[16:43] <mac_v> compiz (1:0.8.2-0ubuntu16) karmic; urgency=low
[16:43] <mac_v>   [ Travis Watkins ]
[16:43] <mac_v>   * debian/patches/015_draw_dock_shadows_on_desktop.patch:
[16:43] <mac_v>     - change decoration plugin to draw dock shadows only on the
[16:43] <mac_v>       desktop window instead of on top of all other windows
[16:43] <mac_v> you forgot the lp#
[16:44] <Amaranth> yeah, oops :P
[16:44] <Amaranth> I should probably use more user speak in things like that too
[16:44] <Amaranth> most of them don't know their panels are actually dock type windows :P
[16:45] <mac_v> wrong ;p , compiz devs should label properly ;)
[16:46] <Amaranth> err
[16:46] <rugby471> mac_v : did mvo tell you that we have very nearly got your icon working in software-store?
[16:46] <Amaranth> mac_v: Blame the guys back in 1990 or so who named them ;)
[16:46] <mac_v> yeah i blame them only ^
[16:47] <mac_v> rugby471: let me check the rev \o/
[16:47] <Amaranth> oh, I guess that was defined in the EWMH spec
[16:47] <rugby471> it's not working completely yet
[16:47] <rugby471> we have the code, we just need to put it into software-store itself
[16:47] <Amaranth> _NET_WM_WINDOW_TYPE_DOCK
[16:47] <Amaranth> 2005 or so in that case
[16:47] <rugby471> mac_v if you download my branch and run
[16:48] <Amaranth> although if you think about it dock makes since as it docks to the side of your screen
[16:48]  * mac_v hates memcheck! hogging memory 
[16:48] <Amaranth> s/since/sense/
[16:48] <rugby471> python softwarestore/view/animated/animatedimage.py ../../data
[16:48]  * Amaranth gets more caffeine
[16:48] <rugby471> then you can see it working (but in a seperate window)
[16:49] <mac_v> Amaranth: lol! you commented too
[16:49] <mac_v> on the bug , i didnt notice now double fix ;p
[16:50] <mac_v> rugby471: where is your branch?
[16:50] <rugby471> https://code.launchpad.net/~rugby471/software-store/software-store-andrew
[16:53] <rugby471> Laney : how is f-spot coming along?
[16:53] <Laney> building
[16:54] <rugby471> link?
[16:54] <Laney> there is no link

[16:54]  * mac_v needs to learn to build and not to be selfish
[16:54] <rugby471> Laney: what is matrix?
[16:54] <Laney> never mind :(
[16:54] <rugby471> sorry being a bit clueless
[16:54] <Laney> i'm building it on my computer
[16:54]  * hyperair chuckles
[16:54] <rugby471> ah
[16:55] <hyperair> rugby471: you ever heard of this dude called neo?
[16:55]  * rugby471 feels like he just made an ass of himself but doesn't know how
[16:55] <rugby471> hyperair: haha very funny
[16:55] <hyperair> rugby471: what?
[16:55] <rugby471> I thought he was referring to a build machine called matrix or something
[16:56] <rugby471> yes I know of a guy called neo :-)
[16:56] <hyperair> mmhmm
[16:56] <hyperair> i'm sure you've heard of "there is no spoon"
[16:56]  * mac_v heard about spooning ;p
[16:56] <hyperair> heheh
[16:56] <rugby471> there is no spoon!? THEN WHAT HAVE I BEEN USING FOR CEREAL?
[16:57] <hyperair> telekinesis, obviously
[16:57] <rugby471> i need to watch the matrix films, for some reason just never go around to it
[16:57] <rugby471> go > got
[16:57] <hyperair> it's in the first one
[16:57] <hyperair> the whole spoon business
[16:57]  * mac_v tries to ban rugby471 for saying that
[16:57] <rugby471> hehe
[16:58] <hyperair> /mode +b mac_v
[16:58] <hyperair> eh whoops ;-)
[16:58] <rugby471> haha
[16:59] <mac_v> hyperair: have you run nautilus with valgrind?
[16:59] <hyperair> mac_v: never tried, why?
[16:59] <hyperair> when i was debugging nautilus-share, i ran it with a tailored LD_PRELOAD library
[16:59] <mac_v> i'm running it right now and the darn thing is killing me with its slow respinse :(
[16:59] <hyperair> heh yeah valgrind does that kind of thing
[17:00] <hyperair> if you're attempting to catch a segfault, try gdb first
[17:00] <mac_v> i need to run this for 24 hrs!
[17:00] <hyperair> if that doesn't give you enough info, then do valgrind
[17:00] <hyperair> 24 hours?!
[17:00] <hyperair> that a pain, yes.
[17:00] <mac_v> not segfault , memory leaks :(
[17:00] <hyperair> ouch
[17:00] <hyperair> that sucks.
[17:00] <hyperair> good luck with that
[17:00] <hyperair> i don't have enough patience lol
[17:01]  * mac_v i'v been using it for 1 hr and already thinking about stopping it !
[17:02] <rugby471> mac_v : do you work for canonical, I see you everywhere (bug reports etc.)?
[17:02] <mac_v> rugby471: hehe , more than you ?
[17:02] <rugby471> hehe
[17:03] <mac_v> rugby471: nope dont work for canonical , its papercuts which has me in all places! :(
[17:03] <rugby471> yeah
[17:03] <mac_v> rugby471: why would i have had to sign the contributors ? ;)
[17:03] <rugby471> good point
[17:06] <rugby471> mac_v : did you look at my branch?
[17:07] <mac_v> rugby471: i can not see the animation , i'm not sure what is wrong... i'm running nautilus using valgrind so , maybe delay in access to file?
[17:07] <rugby471> nothing in the terminal?
[17:08]  * mac_v loosing patience with valgrind :/
[17:08] <rugby471> ah wait I think I know why
[17:08] <rugby471> mac_v: cd into softwarestore/view and run command
[17:08] <rugby471> mac_v : tell me of that works
[17:09] <rugby471> of > if
[17:12]  * rugby471 just looks back at the irc log and got Laney 's joke
[17:13] <Laney> want a deb?
[17:13] <rugby471> sure
[17:13] <Laney> amd64 or i386?
[17:14] <rugby471> i386
[17:14] <Laney> sec then
[17:14] <rugby471> Laney : anything special (apart from my patch & the screensaver working) that you want me to test for
[17:14] <rugby471> kl
[17:14] <Laney> not really
[17:14] <mac_v> rugby471: its not working now , :( i'll check later
[17:14]  * mac_v gotta step away from the keyboard before i get really pissed with valgrind
[17:14] <Laney> if you know of any lp bugs that are fixed by this though
[17:15] <rugby471> mac_v: hehe
[17:15] <rugby471> Laney: sure
[17:15] <rugby471> just the two paper cuts for the moment
[17:15] <Laney> just got a bug on debian about the screensaver not working at all
[17:16] <Laney> is that right? I don't use it
[17:16] <rugby471> yup
[17:16] <rugby471> link?
[17:16] <rugby471> (and none of that matrix stuff this time :-] )
[17:16] <Laney> debian bug 544204
[17:17] <rugby471> yeah that is true
[17:17] <rugby471> I noticed that earlier actually
[17:17] <rugby471> well if this f-spot version doesn't fix it do you want to sneak a quick patch in there :-)
[17:18] <rugby471> it is only a ln -s /usr/libexec/gnome-screensaver/f-spot-screensaver /usr/lib/xscreensaver/
[17:18] <Laney> it's the same
[17:18] <rugby471> sorry?
[17:19] <Laney> not fixed
[17:20] <rugby471> so should we make a patch?
[17:21] <Laney> http://orangesquash.org.uk/~laney/f-spot_0.6.0.0-1_i386.deb
[17:21] <Laney> wait
[17:22] <Laney> wrong link
[17:22] <Laney> http://orangesquash.org.uk/~laney/f-spot_0.6.1.1-1_i386.deb
[17:22] <Laney> !
[17:23] <rugby471> Laney: it's just installing
[17:23] <Laney> k
[17:26] <rugby471> first bug - check
[17:27] <rugby471> second bug ...
[17:30] <rugby471> Laney : okay one bug has been fixed
[17:30] <rugby471> however the second one about the screensaver
[17:30] <rugby471> has not becuase of the debian bug you mentioned
[17:30] <rugby471> the command
[17:30] <rugby471> ln -s /usr/libexec/gnome-screensaver/f-spot-screensaver /usr/lib/xscreensaver/
[17:30] <rugby471> mentioned on the bug report
[17:31] <rugby471> does work
[17:31] <Laney> gyes of course
[17:31] <Laney> i haven't done that yet
[17:31] <rugby471> can a patch containing that be put in?
[17:31] <rugby471> Laney : otherwise not only does it affect one bug
[17:31] <rugby471> but at *least* two papercuts
[17:32] <Laney> yes yes stop worrying
[17:32] <rugby471> Laney: okay :-)
[17:33] <rugby471> Laney : it's just we have debdiffs that have been papaercut bug reports that have been waiting there for a long time and have still not been touched so I wanted to make sure that another debdiff has to be made and that we can do it in one upload
[17:33] <rugby471> Laney: BTW thanks for your help and persistance so far :-)
[17:33] <Laney> it's all very good having diffs
[17:33] <Laney> but it doesn't help if the right people don't see them
[17:33] <rugby471> I know
[17:34] <rugby471> but ubunut-main-sponsors have been subscribed for a while
[17:34] <Laney> forward them to debian
[17:34] <rugby471> ubunut > ubuntu
[17:34] <rugby471> it's just they are papercuts so specific to ubuntu in some cases
[17:34] <Laney> we keep f-spot in sync
[17:34] <Laney> really?
[17:34] <rugby471> yup an example is ...
[17:35] <Laney> if this is some kind of branding
[17:35] <Laney> then ...
[17:35]  * Laney turns green
[17:35] <rugby471> nope
[17:35] <rugby471> https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/204567
[17:36] <rugby471> there is a debdiff attached that goes back twowards upstream behaviour
[17:36] <rugby471> and it is a one-liner, it is just frustrating :-)
[17:37] <rugby471> anyway it (hopefully) will get fixed before ui freeze etc. so I am happy :-)
[17:38] <Laney> that's not an f-spot bug
[17:38] <rugby471> no just an example of where it is ubuntu specific
[17:39] <rugby471> but I see what you mean as regards to being in sync
[17:39] <rugby471> is there a list of packages that are kept specifically in sync?
[17:40] <Laney> not really
[17:40] <Laney> just check the version number
[17:40] <Laney> that tells you
[17:44] <rugby471> k
[18:15] <mac_v> rugby471: that bug is scheduled to be fixed before karmic ;)
[18:18] <rugby471> mac_v: yup
[18:38] <rugby471> hi MadsRH
[18:59] <mac_v> awalton: hi , nautilus-memcheck is as of now using 339Mib [~17%] of the memory in just 5 hrs , is the info sufficient? or do i need to run it for a longer period?
[19:09] <rugby471> mac_v: in 5 minutes I will the progress icon fully integrated into software-store :-)
[19:10] <mac_v> rugby471: was that a pun for my 5hrs :/
[19:11] <rugby471> hehe no, but thinking about it it would have been funny :-)
[19:11] <MadsRH> Hi
[19:11] <mac_v> stupid thing is preventing me from getting anything done!
[19:12]  * mac_v wants to make humanity icons :(
[19:12] <rugby471> mac_v: actaully give me 10 mins :-)
[19:12] <mac_v> ;p
[19:14] <MadsRH> mac_v: I've heard a lot of Breathe bashing lately, but I actually like it better than humanity (though humanity looks really good)
[19:16] <mac_v> MadsRH: hehe... ;) , i think the colors are nicely done in humanity , and the Cory/Sebastien are busy :( so things are just stuck
[19:17] <MadsRH> mac_v: right, but at least there's a roadmap now LOL
[19:17] <mac_v> lol roadmap!
[19:19] <mac_v> MadsRH: so , i'v been doing icons for humanity ;) in the mean time
[19:19] <MadsRH> rugby471: any progress on your Software store icon? ;-)
[19:20] <MadsRH> mac_v: good call - betting on both horses
[19:20] <rugby471> MadsRH: nope I have been coding today :-)
[19:20] <mac_v> MadsRH: rugby471 is more all over the place than me , fspot coding , software store coding , and i thought i was everywhere ;p
[19:21] <rugby471> hehe
[19:23] <MadsRH> :-D
[19:42] <Laney> rugby471: can you try the deb again? I moved the screensaver
[19:42] <rugby471> sure
[19:42] <rugby471> same link?
[19:42] <Laney> yeah
[19:42] <rugby471> mac_v: I have now added the progress icon :-)
[19:45] <rugby471> Laney: yup it all works now
[19:45] <Laney> cool beans
[20:02] <Laney> uh
[20:02] <Laney> is it possible to rename an image in f-spot?
[20:07] <rugby471> Laney : what do you mean?
[20:07] <Laney> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530537
[20:07] <Laney> that
[20:07] <Laney> trying to reproduce bugs
[20:09] <rugby471> umm..
[20:10] <rugby471> have you tried it?
[20:10] <rugby471> I have to go now
[20:10] <rugby471> Laney: however I can try it tomorrow if you want
[20:12] <awalton> mac_v: if we're leaking that profusely it should be pretty easy to see. go ahead and dump the log
[20:13] <Laney> what?!
[20:13] <Laney> I don't just ask without trying :(
[20:13] <awalton> mac_v: I'll get to the bug when I get back, going out for a bit.
[20:14] <rugby471> Laney : gotta go now, but I shall try it in the morning
[20:14] <Laney> k
[20:14] <mac_v> awalton: no probs , actually i notice the nautilus leak a
[20:14] <rugby471> see ya guys!!
[20:14] <Amaranth> apport keeps crash reports around on stable releases even though it doesn't report them, right?
[20:14] <mac_v> only after several hours... but mencheck on its own is bugging me :(
[20:15] <mac_v> yup
[20:15] <mac_v> Amaranth: ^
[20:15] <Amaranth> mac_v: hmm, where?
[20:15]  * Amaranth should just look on the wiki
[20:16] <mac_v> Amaranth:  i'v had apport crash even if it does not report bug
[20:17] <Amaranth> well I need to get someone to submit a core dump
[20:17] <mac_v> *reports
[20:17] <Amaranth> I think they may have told apport to leave them alone since the crash happens when they hit alt-tab
[20:18] <mac_v> Amaranth: which release?
[20:18] <mac_v> jaunty?
[20:18] <Amaranth> karmic
[20:18] <Amaranth> but you can tell apport to ignore crashes for this package version
[20:18] <mac_v> yup
[20:18] <Amaranth> it'll still do the dump though
[20:19] <Amaranth> either that or the guy freaked at the upload size of the full report, which seems more likely
[20:19] <mac_v> lol , which package ?
[20:21] <Amaranth> compiz
[20:21] <Amaranth> I really need to get into the habit of using email for updating launchpad
[20:23] <mac_v> lp is bad , regarding email replies , inconsistent , sometimes mail are add as comments nearly an hr later :/