=== zbraniecki is now known as gandi [12:04] i cant find the power button to my scanner :( [12:14] maybe it has none? [12:22] bdrung_: it doesnt from what i can tell but xsane isnt seeing the scanner [12:22] im thinking power cord is bad [12:23] if the scanner has power something should glow [12:24] bdrung_: nothing is glowing thats what makes me think its power. i changed the usb port just incase it was bad but still no luck [12:25] i have another one and ill get it later i guess or see if i have another power cord for it [12:25] hm === ripps_ is now known as ripps === rickspencer3-afk is now known as rickspencer3 === zbraniecki is now known as gandi [15:26] bdrung_, who gonna advocate you for DM? [15:26] andv: don't know. i will ask all my sponsors. [15:27] k [15:37] bug 383670 [15:37] Launchpad bug 383670 in lightning-sunbird "thunderbird-bin crashed with SIGSEGV in strcmp() when using Google Provider extension" [Undecided,Invalid] https://launchpad.net/bugs/383670 [15:50] gnomefreak: do you know anything about the issue regarding bug 417582 [15:50] Launchpad bug 417582 in firefox-3.5 "Firefox can't detect/change KDE default browser" [Undecided,New] https://launchpad.net/bugs/417582 [15:51] micahg: lack of QT support maybe looking now [15:51] hats not helpful in the least [15:51] I didn't know we even had that type of default configurable from Firefox on linux [15:52] we dont IIRC however why should firefox detect something outside our repos? [15:52] !info arora [15:52] arora (source: arora): simple cross platform web browser. In component main, is extra. Version 0.8.0-0ubuntu6 (karmic), package size 1201 kB, installed size 3388 kB [15:52] yeah [15:52] oh it is [15:52] it's the new KDE browser [15:52] firefox has no reason to detect that browser [15:53] that's what I figured [15:53] that it's handled differently than windows [15:53] the default browser changes should be made in update-alternatives [15:53] do we support that at present? [15:53] update-*? [15:54] yeah [15:54] Ubuntu does we dont [15:54] ah [15:54] well kind of [15:54] we have links in our packages for the update-alternatives so you can shoose it from that setting [15:54] oh, ok [15:54] s/shoose/choose [15:55] KDE should have a default browser setting in menu [15:55] if not that is thier issue [15:55] they probably do [15:59] andv: now i see why you asked. :) [16:00] bdrung_, why? [16:00] :) [16:00] andv: you apply for it, too [16:00] bdrung_, yeah [16:00] bdrung_, soon a new package revision will be uploaded [16:01] of what? [16:01] bdrung_, so you should find an advocate / attach a changset asap [16:01] bdrung_, of debian-maintainers package [16:01] andv: i have send an email to 8 DDs, so hopefully someone will advocate me. [16:02] micahg: there maybe a setting in arora to make it default like there is in firefox [16:03] bdrung_, yeah^^ [16:03] bdrung_, prepare your changeset then [16:08] andv: do i need an advocate to create the changeset? [16:08] bdrung_, yes [16:08] bdrung_, in the changeset you have to list all your advocations [16:09] ah, ok === rickspencer3 is now known as rickspencer3-afk === stevel_ is now known as stevel [21:24] ola [21:29] gni [21:31] hi fta [21:35] it's quiet in here [21:35] * micahg has questions, but they are for the man on vacation :) [21:36] ehehe [21:37] so are you saying asac is the one that brings noise here? [21:37] no [21:37] ok [21:37] :D [21:37] just explaining why I'm not making nay [21:37] *any === fta_ is now known as fta [22:53] <[reed]> armin76: ping [22:54] <[reed]> where's asac, hmmz [22:54] <[reed]> jdstrand: around? [22:54] [reed], asas is on vacation [22:54] :) [22:54] <[reed]> ah [22:54] [reed]: yes [22:54] [reed]: what's up? [22:57] <[reed]> jdstrand: msg'd you [23:06] ack [23:11] fta : here? [23:11] e-jat, 1/2 [23:11] half ? :) [23:12] yes [23:12] fta is your chromium still having the flash issue ? [23:13] is it must me 1 plugin show at about:plugins? [23:13] i mean for the flash .. [23:13] e-jat, when i tried, it was crashing, i filed http://code.google.com/p/chromium/issues/detail?id=20045 [23:13] not sure your bug is the same [23:15] for me is not crash .. but it cant view/render video from the youtube .. [23:15] <[reed]> you should just use Firefox ;) [23:15] [reed]: yea :) [23:15] [reed], ff trunk is unusable for me, it just refuses to start [23:15] <[reed]> fta: ? [23:15] <[reed]> fta: works fine for me [23:15] x64 [23:16] 32bit is fine [23:16] <[reed]> hmm, you should tell me these things! [23:16] <[reed]> do you have ia32-libs installed? [23:16] you disappeared for weeks [23:16] <[reed]> you can always e-mail me ;) [23:17] i use x64 at work, and i have better things to do than debug my browser [23:17] <[reed]> well, we want Firefox to work everywhere [23:18] <[reed]> so, if you can spare some time to debug it, that would be awesome [23:18] <[reed]> and hopefully we can get it fixed [23:18] 3.6 is still fine [23:18] <[reed]> I use official mozilla.org nightlies for trunk (3.7) on jaunty [23:19] <[reed]> but I'm also i686 [23:21] well, what could i say? it's been broken for at least a week for me on karmic x64 [23:21] <[reed]> yeah, well, can you give any more information? [23:21] no crash, no error, no nothing, just no window and i'm back to the shell (when started from a shell) [23:22] <[reed]> does gdb say anything? [23:22] strace shows that it starts well, then it releases the lock and exit [23:22] <[reed]> hmm [23:22] I'm on 3.7 [23:22] dailly ppa [23:22] works ok [23:22] on 64bits [23:22] nope, gdb does help, it doesn't catch anything [23:22] only prob: Fullscreen bug [23:22] <[reed]> BUGabundo: x86_64? [23:23] <[reed]> BUGabundo: fullscreen bug? [23:23] [reed]: ^^^^ [23:23] https://bugzilla.mozilla.org/show_bug.cgi?id=511080 [23:23] <[reed]> fta: hmm, could you try building debug? [23:23] Mozilla bug 511080 in General "exiting from full screen doesnt return to regular window" [Normal,Unconfirmed] [23:23] for me, it works only once after each upgrade, the next day in the morning, nada [23:24] <[reed]> hmm [23:24] fta start in safemode, quit, start again it work [23:25] been like that for 4 months :( [23:25] better now in 3.7 [23:25] but still fails to start sometimes [23:25] <[reed]> BUGabundo: so, it works 20090816 but not 20090817 ? [23:25] <[reed]> heh [23:25] greasemokey does make it worse [23:25] <[reed]> have you filed a bug on that? [23:25] [reed]: at least one mine on LP [23:26] [reed]: let me test it again with todays build [23:26] I haven't done it yet [23:26] <[reed]> k [23:26] I didn't even got updates :\\ [23:26] <[reed]> need to find a regression range to really figure it out [23:26] * BUGabundo runs $ sudo aptitude update ; sudo aptitude safe-upgrade ; sudo aptitude full-upgrade [23:27] [reed]: that's why I posted the Revision [23:27] and that's what Dailies are for :) [23:27] <[reed]> yeah, so, it works 20090816 but not 20090817 ? [23:29] right [23:30] <[reed]> hmm [23:34] <[reed]> maybe mozilla bug 503791 [23:34] Mozilla bug 503791 in Layout: Form Controls "Drop down menu at page bottom edge not displayed completely" [Minor,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=503791 [23:36] hum?? [23:36] that's not my bug [23:36] not even close [23:36] don't start spewing bug, or else ill start thinking I have them all :D [23:37] <[reed]> I'm looking at patches that landed [23:37] <[reed]> http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2009-08-16+&enddate=2009-08-18 [23:37] ahh [23:37] [reed]: what would it take to debug what the F**k is causing gmail to kill my firefox? [23:37] it eats all my cpu [23:37] prob one of my addons [23:38] but I disabled them all and still got it [23:38] it happenes on both ubuntu and debian [23:38] [reed], i also have huge repaint problems with trunk, mostly forums [23:38] with the daily ppa [23:38] on 3.6 and 3.7 [23:38] humm I have that too [23:38] though it was a debian X bug [23:39] <[reed]> fta: just trunk? [23:39] <[reed]> 3.6 is fine? [23:40] [reed], i assume the new ff is a security update, right? (3.0.14 & 3.5.3) [23:40] <[reed]> yes [23:41] <[reed]> nothing special [23:41] too bad it's in main, i'm only a motu and i can't update it there [23:41] <[reed]> just normal update [23:41] <[reed]> scheduled release is September 9th [23:42] maybe with the archive reorg, i will gain that power... [23:42] or loose everything :P [23:42] eeh [23:42] you should [23:43] 3.5.3 has some other fixes unless they were pushed back [23:43] <[reed]> security & stability update [23:43] <[reed]> :) [23:43] :) [23:43] I started tagging the fixed versions in LP since we don't have a system to handle that yet [23:45] <[reed]> https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status1.9.1:.3-fixed [23:45] <[reed]> I see 53 bugs fixed [23:45] I see 42 :) [23:45] 42+11 private? [23:45] :) [23:46] at least 3 we have in LP [23:46] including the full screen flash issue [23:47] micahg: 42 :) [23:48] that's the right number [23:48] bdrung_: [reed]sees 53 [23:49] yep, 42 :) [23:49] i mean, "the" number [23:49] <[reed]> micahg: reed is also a member of the security group ;) [23:49] right :) [23:49] fta: :) [23:50] fta: you got it [23:50] sure, 42, the Answer to Life, the Universe, and Everything [23:52] [reed]: is there a document on how crashes are labeled in bmo [23:52] <[reed]> micahg: https://developer.mozilla.org/En/Triaging_crash_bugs [23:53] ty [23:53] that will help to see if it's an upstream issue [23:53] fta "but what is the question?" ehehe [23:54] * micahg knows... [23:55] [reed]: is this anything? http://seclists.org/bugtraq/2009/Aug/0194.html [23:55] <[reed]> looks like just a DoS... I don't know of a bug in bmo that's tracking it, though [23:56] do I need to worry about opening a bug for it? [23:56] or is it not an issue [23:56] <[reed]> well, it's an "issue", but I don't know if we're tracking it yet [23:56] ah, ok [23:56] <[reed]> feel free to open a new bmo bug [23:57] ok [23:57] mabe later tonight [23:57] <[reed]> it's public, but I still would recommend you check the "this bug is a security issue" box so that the security group triages it rather than the normal triagers [23:57] ok [23:57] <[reed]> even though it's public [23:57] <[reed]> it just works out better that way [23:57] I figured I'd open one in Launchpad as well [23:58] <[reed]> sure [23:58] <[reed]> won't be long before launchpad and bmo can be linked [23:58] <[reed]> just waiting on bmo to upgrade [23:58] really? [23:58] <[reed]> yeah [23:58] that's great [23:58] how would that work? [23:58] I could just say push upstream? [23:58] <[reed]> afaik, Bugzilla 3.4 supports everything launchpad needs in order to link [23:58] <[reed]> no [23:59] <[reed]> means you can link bugs [23:59] <[reed]> and comments will flow from one to the other [23:59] ah, well [23:59] that's good and bad [23:59] reporters might not always be interested in upstream comments, but I think triagers would be