[01:18] <Jazzva> nhandler: changelog version is still 0.1-0ubuntu1. I suppose it should be 0.4.1-...
[01:19] <Jazzva> nhandler: please fix "mozilla" to "Mozilla" in description field
[01:20] <Jazzva> nhandler: and now running a test-{build,drive}
[01:23] <Jazzva> nhandler: and I think that's it. It's working here. A really helpful extension :)
[01:24] <Jazzva> nhandler: thanks for packaging it
[04:45] <nhandler> Jazzva: Thanks for looking it over. I'm not used to having to manually edit the version in debian/changelog, I'll have to remember to do that. As for 'mozilla', I'm only changing it in the long description. The one in the short description should be lower case
[05:49] <micahg> does anyone know if the mozilla-thunderbird bin symlink is permanent?
[10:46] <stefanlsd> hihi
[10:46] <stefanlsd> asac: had any time off work to have a look gears libpng and libjpeg?
[13:49] <askand> What debug packages do I need to get debugsymbols to trace a segfault for firefox?
[15:25] <BUGabundo> guud day
[15:37] <nhandler> Hello BUGabundo
[15:39] <BUGabundo> he nhandler
[15:43] <nhandler> Are you attending UDS BUGabundo ?
[15:43] <BUGabundo> no
[16:37] <asac> wow
[16:37] <asac> i can go online again ;)
[16:37] <micahg> hi asac
[16:37] <BUGabundo> heeey asac
[16:37] <stefanlsd> hihi
[16:37] <BUGabundo> wow to you too
[16:37] <BUGabundo> LOLOLOL
[16:37] <BUGabundo> slow network, still??
[16:37] <asac> a bit better now
[16:37] <asac> i couldnt get online yesterdy at all
[16:37] <micahg> Can I replace mozilla crash backtrace reporting with apport?
[16:38] <micahg> on the wiki?
[16:38] <BUGabundo> micahg: humm better not replace
[16:38] <asac> right. extend
[16:38] <BUGabundo> just enfatize that the user can use apport instead
[16:38] <BUGabundo> leave the _manual_ process around
[16:38] <micahg> How about this section?
[16:39] <asac> i thought we already said that preferred way is to use apport for crashes
[16:39] <micahg> Obtain a backtrace from an apport crash report (using gdb)
[16:39] <BUGabundo> someone without a working apport may need it
[16:39] <micahg> Is this necessary anymore?
[16:39] <micahg> https://wiki.ubuntu.com/MozillaTeam/Bugs/#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29
[16:39] <asac> micahg: well, often apport retracers fail and you can still get a good backtrace
[16:39] <asac> locally
[16:39] <micahg> ah
[16:39] <micahg> ok
[16:40] <asac> imo we should add a section for: how to attach crashes using apport to existing bugs
[16:40] <micahg> see BUGabundo, that's why I wanted to ask asac
[16:40] <micahg> :)
[16:40] <micahg> I'd like to know that myself
[16:40] <asac> also users might not want to attach a crash report to bugs
[16:40] <BUGabundo> micahg: that's what I Said!!
[16:40] <asac> because of privacy concefrns
[16:41] <micahg> ok, so if I were to update the crash page for FF3, what version should I use
[16:41] <micahg> or should I make it generic for all versions?
[16:41] <asac> at best we would have 4 types of instrtuctions:
[16:41] <asac> a) report crashes using apport
[16:42] <asac> b) attach crash data to open bugs using apport
[16:42] <asac> c) use gdb to get backtraces from .crash files locally
[16:42] <asac> d) run mozilla apps in a debugger
[16:42] <asac> (e.g. firefox -g)
[16:42] <micahg> Does that work in FF3 as well?
[16:42] <micahg> part d?
[16:42] <asac> micahg: does that answer your question (i dont think i understood the question about versions)
[16:43] <micahg> Ubuntu versions
[16:43] <asac> micahg: yes. d) has the same prerequisites as c)
[16:43] <asac> (e.g. you need all the dbg symbol packages before you do that)
[16:43] <asac> all mozilla apps usually can be started with -g
[16:44] <micahg> on the wiki, it show ff2 with -g
[16:44] <BUGabundo> I didn't know option d)
[16:44] <micahg> and ff3 using gdb
[16:44] <micahg> so, can I clean that up?
[16:45] <asac> yes, definitly
[16:45]  * gnomefreak hasnt gotten around to updating wiki, i was hoping to have -dbgsym for tbird before i did it, but being short on time until fall its unlikely ill get to it
[16:46] <gnomefreak> would be nice to have a script that installed all debug packages
[16:47] <BUGabundo> john +1
[16:47] <gnomefreak> maybe a hook in apt to do it
[16:47] <BUGabundo> something like apt-get firefox-debugpackages
[16:47] <BUGabundo> eheh
[16:47] <BUGabundo> and have that a metapackage with ALL it needs
[16:48] <gnomefreak> meta package wont work since im not just talking firefox
[16:48] <micahg> For apport submits, should I just link to the other wiki page that describes it?
[16:48] <gnomefreak> although apport should do this for you but only on crashes
[16:49] <asac> right
[16:49] <asac> but i think apport already has such a script
[16:50] <stefanlsd> asac: have you had any time off work to have a look gears libpng and libjpeg?
[16:50] <gnomefreak> asac: to just grab -dbg* packages so you can run a debug session yourself
[16:50] <gnomefreak> ?
[16:52] <asac> stefanlsd: no.
[16:53] <micahg> are the dbg packages in main now?
[16:53] <BUGabundo> gnomefreak: not sure if apport is ready for that
[16:53] <asac> stefanlsd: maybe i can look for 1h a bit laer today
[16:54] <asac> gnomefreak: i think you can say to apport to isntall all required dbg symbols
[16:54] <stefanlsd> asac: oki :)  np. i suspect stuff will really only start happening again after uds.  is it worthwhile working on a debian gears package without mozilla-devscripts, or is it expected soon in debian?
[16:54] <stefanlsd> asac: if you could, that would be great.  if not, np :)
[16:54] <asac> stefanlsd: we can upload mozilla-devscripts this week for sure
[16:55] <thunderstruck> i guess it wasnt lavabit having issues
[16:55] <stefanlsd> asac: kk. great. will wait then :) thanks
[16:56] <gnomefreak> what are the chances that xserver-common xserver-xorg-core woll fix X
[16:59] <micahg> I added apport to the crash page, but I'll have to fix the debug stuff later
[17:01] <micahg> gnomefreak: should bug 52667 be changed to in progress and moved to the thunderbird package?
[17:01] <micahg> ah it ok
[17:01] <micahg> I meant the Ubuntu part of the bugs
[17:05] <asac> micahg: thx
[17:05] <micahg> asac: for what?
[17:05] <gnomefreak> no shouldnt be set to inprogree
[17:05] <micahg> ok
[17:05] <asac> for wiki work ;)
[17:05] <gnomefreak> its not in progress
[17:05] <micahg> is incomplete the correct setting?
[17:06] <micahg> ok, I thought I saw you working on it
[17:06] <micahg> nevermind
[17:06] <micahg> I would think then wishlist->triaged
[17:07] <micahg> asac: did you have a chance to talk to bug control people about me?
[17:07]  * BUGabundo micahg is asking for favours .... lol
[17:08] <micahg> not asking, reminding...
[17:09] <gnomefreak> micahg: it should be confirmed. did i already set that bug to what i wanted it.
[17:09] <micahg> gnomefreak: it's set to incomplete
[17:09] <gnomefreak> micahg: bug number please
[17:09] <micahg> oh, I also wanted to ask about confirmed vs triaged for mozilla bugs
[17:09] <micahg> bug 52667
[17:10] <micahg> I was told if there's enough info for a developer or if it's reported upstream it should be marked triaged
[17:10] <micahg> is that not the case for mozilla bugs?
[17:10] <gnomefreak> micahg: most of time yes
[17:11] <micahg> gnomefreak: which one?
[17:11] <micahg> :)
[17:11]  * micahg hasn't had caffeine yet, needs things spelled out...
[17:11] <gnomefreak> i forgot to do a few things with the bug
[17:12] <micahg> ok, but in general, they should be set to triaged then if there's an upstream bug?
[17:13] <gnomefreak> micahg: yes
[17:13] <micahg> ok
[17:13] <micahg> BTW, I'm moving bug 52667 to thunderbird from mozilla-thunderbird in ubuntu
[17:13] <gnomefreak> micahg: upstream status set to confirmed yes our bug to triaged
[17:13] <gnomefreak> asac: can you decline the nominations from bug 52667
[17:13] <micahg> oh, gnomefreak, we have to wait for upstream to confirm before setting to triaged?
[17:14] <gnomefreak> micahg: im on the bug dont worry about package atm
[17:14] <micahg> ok
[17:14] <micahg> I was trying to clean up mozilla-thunderbird last night
[17:14] <asac> gnomefreak: done
[17:14] <gnomefreak> asac: thanks
[17:15] <micahg> I was assuming that crash reports for 1.5 won't help debug 2.0 problems
[17:15] <micahg> is that correct?
[17:15] <gnomefreak> micahg: ok ill take care of this bug but yes mozilla-thunderbird if happening on 2.0 should be moved to thunderbird.
[17:15] <gnomefreak> although mozilla-thunderbird is a transitional package
[17:16] <gnomefreak> so really doesnt matter since it will install 2.0
[17:16] <micahg> yes, but it will go away at some point
[17:16] <gnomefreak> but LP sources is using it for 1.5
[17:16] <gnomefreak> micahg: not likely for a while
[17:17] <gnomefreak> since LTS still has it we wont remove it may cause upgrade problems
[17:17] <micahg> bug 312738
[17:17] <micahg> did I do that right?
[17:18] <asac> checking
[17:18] <gnomefreak> loooks good
[17:18] <nhandler> gnomefreak: or asac: Do one of you want to update the ~mozilla-extensions-dev to include long-url-please ?
[17:19] <gnomefreak> backport will not happen
[17:19] <asac> micahg: not sure. did i forget to close that bug when aqdding that symlink?
[17:19] <asac> otherwise it is a dupe
[17:19] <asac> micahg: https://edge.launchpad.net/ubuntu/+source/thunderbird
[17:19] <asac> ... fix LP: #145716 - panel launcher breaks on upgrade; we provide a
[17:20] <asac> so its a dupe of that bug
[17:20] <asac> but well ... it doesnt matter much anyway ;)
[17:20]  * gnomefreak really wish people would stop adding nominations since we never backport or update a stable release with new feature 
[17:20] <micahg> ok
[17:20] <asac> but folks that want to seee that backported should rather nominate that bug than the other
[17:20] <micahg> well, I know I didn't understand what it was for until recently
[17:20] <asac> so duping would make sense
[17:21] <micahg> asac: done
[17:21] <asac> gratias
[17:21] <micahg> sorry, I forgot to check the changelog for jaunty
[17:21] <gnomefreak> nhandler: can we get links, to want you want done
[17:22] <nhandler> gnomefreak: Add https://launchpad.net/ubuntu/+source/long-url-please to the description on https://launchpad.net/~mozilla-extensions-dev
[17:23] <asac> micahg: no problem at all :)
[17:23] <asac> you do amazing work.
[17:23] <micahg> Will a crash report for 1.5 help for debugging 2.0 or can it be closed?
[17:23] <gnomefreak> asac: you got it?
[17:23] <micahg> thanks asac
[17:24] <asac> gnomefreak: i think we can add him to extensions dev team ... if thats what you ask
[17:24] <gnomefreak> asac: i will
[17:25] <gnomefreak> https://edge.launchpad.net/ubuntu/+source/long-url-please get supdated when package is pushed IIRC
[17:25] <gnomefreak> ok what was i doing
[17:26] <gnomefreak> we dont list all extensions on that link, it would cause lag when opening if we listed all of them
[17:26] <gnomefreak> nhandler: can i have your LP home page please
[17:27] <nhandler> gnomefreak: https://edge.launchpad.net/~nhandler
[17:27] <gnomefreak> nhandler: i may need to apply but im looking at it atm
[17:27] <nhandler> gnomefreak: If we don't list them on the LP page (which I think we should) can we try to get the List wiki page up-to-date?
[17:27] <gnomefreak> nhandler: yes we should update the wiuki we have already for extensions
[17:29] <gnomefreak> nhandler: thanks you have been added to extension team
[17:30] <nhandler> Awesome! Thanks gnomefreak
[17:31] <gnomefreak> nhandler: np
[17:33] <gnomefreak> micahg: i killed one of you bugs that you just commented on :)
[17:33] <micahg> ok
[17:34] <gnomefreak> micahg: iits was likely caused by not restarting after update
[17:34] <micahg> I guess I"ll probably get the e-mail soom
[17:34] <micahg> soon
[17:35] <asac> gnomefreak: the long-url-please link you posted looks just like a package ölink in launchpad
[17:35] <asac> not sure i understand your question
[17:36] <gnomefreak> asac: it was one he posted
[17:36] <gnomefreak> .:12:22:47:. >>        nhandler << gnomefreak: Add
[17:36] <gnomefreak> https://launchpad.net/ubuntu/+source/long-url-please to the description on  https://launchpad.net/~mozilla-extensions-dev
[17:36] <gnomefreak> i just opened it :)
[17:37] <asac> ah
[17:38] <asac> gnomefreak: i think we can add all packages that are maintained by the ext-dev team there , yes
[17:39] <gnomefreak> asac: that is a long list and LP is slow most of time anyway
[17:39] <asac> gnomefreak: right. i think its more important that extensions maintained by us, get the Extension Team in the Maintainer: field
[17:40] <gnomefreak> right
[17:40] <asac> , but either we add all extensions there or we dont add any
[17:41] <nhandler> I personally would prefer to see all extensions there
[17:41] <gnomefreak> asac: i have to update mine, im hoping in time to get them in KK but we really need to decide on ice* package extensions. once this is done we can clean up the extensions since we dont package ice* for ubuntu.
[17:42] <gnomefreak> nhandler: we will work something out. First i need a list of every extension in repos before i can do that
[17:44] <gnomefreak> oops you did apply. sorry i didnt get that far in email but either way you have been added
[17:44] <micahg> gnomefreak: I just found out that the partner acroread package apparently has a mozilla extension in it
[17:45] <gnomefreak> it does?
[17:45] <micahg> that what the maintainer told me
[17:46] <gnomefreak> we wont package that anyway as a firefox extension
[17:46] <micahg> it used to be a separate pageckage
[17:46] <gnomefreak> at least mozilla team wont
[17:47] <micahg> right, but should it be a separate package or do we not get involved with partner stuff at all
[17:47] <gnomefreak> until it get a free license we wont package it
[17:47] <gnomefreak> i would stay out of partner IMHO but as i recall same devs for that and our core devws
[17:48] <micahg> ok, I just requested that description say it has the mozilla extension as well
[17:48] <gnomefreak> works for me
[17:48] <micahg> it used to provide separate packages for each piece
[17:48] <micahg> ok
[17:49] <gnomefreak> arcobat works in default gnome
[17:49] <gnomefreak> forgive my spelling but evince works fine out of box
[17:50] <micahg> I know
[17:51] <micahg> it had to do with a bug submitted to firefox package I think
[17:52] <micahg> I prefer evince myself
[17:52] <micahg> Adobe's had too many security flaws lately
[17:53] <micahg> gnomefreak: I didn't feel comfortable closing that upgrade bug, not enough experience for me yet
[17:54] <gnomefreak> micahg: np
[18:09] <micahg> gnomefreak: should bug 135066 be set to triaged?
[18:19] <micahg> gnomefreak: also, is bug 379894 a bug?   It happens to me too, but is it the expected behavoiur?
[18:19] <gnomefreak> micahg: that i commented on already but i may not have sent it yet 279094 as for the above im on that one already
[18:21] <gnomefreak> let me see if i sent it yet
[18:21] <gnomefreak> yep everything should be updated onboth those bugs
[18:23] <micahg> should I move the package?
[18:24] <gnomefreak> closed it
[18:24] <micahg> ok :)
[18:24] <micahg> gnomefreak: can we chat about bug 135066
[18:25] <gnomefreak> micahg: what about it? it has nothing to do with icon itself
[18:25] <micahg> I thought that Ubuntu could provide a theme package in addition to the standard TB icons
[18:25] <micahg> as a wishlist thing
[18:25] <micahg> TB ahs themes
[18:25] <micahg> so why not a GTK theme?
[18:26] <asac> micahg: tbird 2 is similar to ffox 3 which wasnt able to use the gtk theme for icons
[18:26] <gnomefreak> we can provide themes for it however we _have_ to use defualt theme when using official branding
[18:26] <micahg> of course
[18:26] <asac> tbird 3 should be able to though ... but i am not sure what upstream plans
[18:26] <micahg> but it could be a separate package though, no?
[18:26] <asac> micahg: yes... it could be a tbird theme
[18:26] <gnomefreak> bug 126354 is most likely a setting
[18:27] <micahg> asac: that was the bug I was arguing for 45 min in teh bugs channel last night
[18:27] <asac> micahg: is it rreproducible in tbird 3 ?
[18:27] <micahg> asac: not that one
[18:28] <micahg> sorry the one above the one gnomefreak just posted
[18:28] <gnomefreak> makiung a tbird-2 theme package is not likley but for tbird 3 i like the idea only we have to wait and see how it handles themes likel firefox-2 -> 3 was a big change as i recall
[18:28] <micahg> gnomefreak: you confirmed it worked in TB2 and the user was unresponsive
[18:28] <micahg> so I closed
[18:28] <micahg> was that wrong?
[18:28] <gnomefreak> what bug?
[18:28] <gnomefreak> too many bugs floating around to keep track
[18:29] <micahg> bug 126354 gnomefreak
[18:29] <gnomefreak> you closed it that is good. i never confirmed it however
[18:29] <micahg> you wrote: This works here and has in 8.10.
[18:29] <gnomefreak> plus too old without comment anyway closed is perfect
[18:29] <asac> i think its ok to have it closed if its not reproducible
[18:29] <gnomefreak> micahg: works not that it happens
[18:30] <micahg> right, that's what I meant
[18:30] <micahg> sorry :)
[18:31] <gnomefreak> anything before jan1 can be closed if all info is not provided
[18:31] <micahg> well, the bugday should help in the TB pacakge
[18:31] <gnomefreak> maybe even feb1 but lets stick with jan 1 as a general rule
[18:31] <gnomefreak> dont count on it
[18:32] <micahg> well
[18:32] <micahg> maybe not that much..
[18:32] <gnomefreak> be back i have to eat
[18:32] <micahg> probably get 20-30 isssues looked at by others
[18:32] <asac> tbird bugday?
[18:33] <micahg> yep, this thursday
[18:33] <gnomefreak> looked at does not mean helpful there ar e afew people in the past that just ade more work
[18:33] <gnomefreak> s/ade/made
[18:33] <micahg> gnomefreak: true
[18:34] <gnomefreak> close all tbird bugs without backtrace/crash report
[18:34] <micahg> wow
[18:34] <micahg> that's bold, isn't it?
[18:34] <gnomefreak> micahg: nothing we can do with them
[18:34] <micahg> find upstream issue if open?
[18:35] <gnomefreak> micahg: you need a backtrace/crash report to do that
[18:35] <gnomefreak> actions do not define a crash
[18:35] <micahg> It's not always a crash
[18:35] <gnomefreak> mozilla needs same info to look into it
[18:35] <gnomefreak> thats why i said close crash reports without the info
[18:35] <micahg> yes, but if there are steps to reproduce the bug, then that should be enough, no?
[18:36] <asac> yes. if there are instructions that have been acked by someone keep it open
[18:36] <asac> even forward upstream
[18:36] <gnomefreak> if you can get a crash report sure. the problem is same steps can cause different crashes
[18:36] <micahg> yes, but sometimes it's not a crash, but an unintended result
[18:36] <gnomefreak> now IMAp needs alot of work
[18:37] <gnomefreak> micahg: that is not a crash than :)
[18:37] <micahg> I know, but they should still be valid issues to be fwd upstream, no?
[18:37] <gnomefreak> closing unexpectedly can be calle da crash
[18:37] <micahg> yes
[18:38] <micahg> but it 1 hot key is assigned to 2 functions, that's still an issue
[18:38] <gnomefreak> micahg: if it is reproducible leave it open with asking for steps and trying yourself
[18:38] <micahg> ok
[18:38] <micahg> gnomefreak: I think I know what you're saying
[18:38] <gnomefreak> micahg: that is keyboard layout IMHO
[18:39] <gnomefreak> crash when checking email is not helpful bug at all :)
[18:39] <micahg> right
[18:39] <micahg> basically, if it's not a useful bug, close it out
[18:39] <gnomefreak> if there is enough info to send upstream go for it
[18:40] <gnomefreak> alot of older bugs there was no debug packages/symbols for
[18:40] <micahg> I opened LP upstream requests for 2 bugs that I couldn't find the upstream for and was too tired to look/create
[18:40] <micahg> but I could confirm the behaviour
[18:40] <gnomefreak> <2.0 and i think in begining for 2.0 we didnt
[18:42] <gnomefreak> mozilla is having an all out bug war atm, in the sense of how traging goes mainly for seamonkey. not sure how dupilicates are working but not everyone can mark them as such and normally i suggest than they get marked
[18:42] <gnomefreak> they are trying to determine how to handle unconfirmed bugs atm (at least from the mailing lists)
[18:43] <gnomefreak> i dont have duplicate powers upstream yet. not real sure how to get them either
[18:43] <micahg> is confirming something I can do for our bugs?
[18:43]  * gnomefreak smoke
[18:43] <gnomefreak> yes
[18:43] <micahg> Do I have to mark a setting or jsut comment?
[18:43] <micahg> Do I need special privs?
[18:44] <gnomefreak> you are able to do both
[18:44] <micahg> ok, should I mark confirmed if our users confirm on LP or only if I can confirm myself?
[18:44] <gnomefreak> make sure its not an extension issue first. most firefox bugs are extensions or propfile bugs
[18:44] <micahg> right
[18:45] <micahg> that's what I usually do
[18:46] <asac> micahg: its important that real issues get eventually filed upstream
[18:46] <asac> thats basically one of the exit states we in ubuntu have for bugs
[18:46] <asac> so either file upstream, invalidate or fix on our own
[18:46] <asac> but adding upstream target without bug is good way to indicate that a bug should be upstreamed
[18:46] <asac> so you did the right thing when you were tired ;)
[18:48] <micahg> is there a policy on bugs in alpha/beta Ubuntu releases that users don't respond to and aren't percevied to be an issue?
[18:48] <micahg> like bug 340086
[18:49] <micahg> gnomefreak responded 2 months ago and user has not responded
[18:49] <gnomefreak> that is a local bug
[18:49] <gnomefreak> close it
[18:49] <gnomefreak> for non responsive
[18:49] <asac> micahg: if users didnt response and there is not enough info to process it its just invalid
[18:49] <micahg> I'm just adding a note that if they are still having issues, to reopen
[18:50] <gnomefreak> all bugs should have steps to reproduce actual and expected resluts with that you should beable to reproduce if not its nomrally addon/system state ect... those are valid bugs depending on what it is
[18:50] <micahg> ok
[18:50] <gnomefreak> micahg: thats perfect
[18:51] <gnomefreak> can not start thunderbird isnt a bug in thunderbird unless others have same issue but in a pre-release ubuntu version its hard to say
[18:52] <gnomefreak> asac: while you are here, we need to add thunderbird->help->file a bug  like we do with firefox, this should give us info on if its user set up or tbirds
[18:52] <gnomefreak> addons for tbird are becoming popular with users
[18:59] <gnomefreak> you have got to be kidding, how the hell are you going to be able to use an "undo close feature" if the undo button is in firefox you would have to start it to use it :(
[18:59] <micahg> lol
[18:59] <gnomefreak> micahg: looking to see if he ment tabs
[18:59] <gnomefreak>  Bug 394759 -  Add undo close window feature
[19:01] <micahg> gnomefreak: is that a mozilla bug?
[19:02] <gnomefreak> im confused they talk about restore dialog but that already lets you choose what closed or start new. btw that feature is bullshit. if a sote caused you to lockup and crash why would you want to reopen it
[19:02] <gnomefreak> micahg: yes mozilla 394759
[19:03] <micahg> ah, it seems like it means tabs
[19:08] <gnomefreak> as in undo tabs from the restore dialog so you can drop the tab that caused crash and leave rest to open?
[19:09] <gnomefreak> at least that is what i was thinking the further i read it
[19:09] <micahg> I thought it was saying someone closed a tab too quickly and have an option to restore it
[19:09] <micahg> but that's just from the initial summary
[19:10] <gnomefreak> that is what my sencond thought was but since its in histroy why would you need it. hint see recently closed tabs
[19:10] <micahg> well, tabs have their own history
[19:10] <micahg> so maybe to restore all that
[19:11] <gnomefreak> ill be back in a bit.
[19:26] <gnomefreak> anyone use firefox?
[19:27] <gnomefreak> no not a trick question
[19:28] <gnomefreak> i need someont to test firefox-notify on firefox not abrowser
[19:30] <micahg> yes
[19:30] <micahg> which version?
[19:30] <micahg> I'm running the latest 3.5 daily and 3.0.10
[19:35] <gnomefreak> micahg: any version. its top level <<3.6 but when you install firefox-notify in ubufox you should see disable and preferences are either greyed out?
[19:35] <gnomefreak> that was my fault i really should have added 3.6 in there but ask for 3.5 as top version
[19:36] <gnomefreak> easy to fix when needed
[19:37] <micahg> how do you install firefox-notify in ubufox?
[19:37] <gnomefreak> micahg: apt-get install
[19:37] <micahg> ubufox doesn't work in 3.5+ yet afaik
[19:37] <gnomefreak> it will open ubufox once installed
[19:38] <micahg> I can't find the package
[19:38] <gnomefreak> i jaunty
[19:38] <gnomefreak> in
[19:39] <gnomefreak> !info firefox-notify
[19:39] <gnomefreak> !info firefox-notify karmic
[19:39] <gnomefreak> ah not in jaunty
[19:40] <gnomefreak> ok re phrase: anyone on Karmic that runs firefox-3.0 3.5 test firefox-notify and let me know if you can enter preferences using ubufox
[19:41] <gnomefreak> we really need to look at .desktop file for deja-dup
[19:41] <gnomefreak> but thats least of my worries
[19:42] <gnomefreak> it should be moved hmmm
[19:44] <gnomefreak> i how it compresses final data not just per volume *.gz's
[19:45] <gnomefreak> ok im gone maybe be back tuesday since tomorrow is a holiday
[23:26] <fta_nano> yop
[23:26] <BUGabundo> fta_nano: hi
[23:29] <fta_nano> bouh, django error in the uds schedule
[23:31] <BUGabundo> yep
[23:41] <fta_nano> hm, no more click when i double tap my touchpad
[23:43] <BUGabundo> lol
[23:44] <fta_nano> i should use laptops more often
[23:44] <BUGabundo> you don't?
[23:44] <fta_nano> i'm mostly a desktop user
[23:59] <fta_nano> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-social-from-the-start