[00:01] <greg-g> dtchen: if you get a chance later (I know you're probably busy with beta freeze) I'd be more than willing to help figure out my sound bug. It is causing me to be unable to watch fullscreen videos.
[00:03] <greg-g> or anyone else who knows linux audio/pulse well
[00:06] <greg-g> for completeness sake, the bug is bug 344057
[00:08] <dtchen> greg-g: there are two components. i'll generate a kernel later for you to test. will you be around in 4-5 hours?
[00:10] <greg-g> 4-5? as in 12-1am EDT? I suppose :)
[00:10] <greg-g> dtchen: yeah.
[00:11] <greg-g> you rock, btw.
[00:11] <dtchen> depending on $work, i may not get to it today, but i'm trying.
[00:13] <greg-g> dtchen: cool man. just let me know when you can, I'll do my best to be responsive.
[01:18] <brendon1> hello
[01:25] <mrooney> brendon1: hello!
[01:25] <brendon1> hello mrooney, there you are again.  I just finished a nap, I'm ready to look at more bugs ;)
[01:25] <mrooney> oh how fun :)
[01:26] <mrooney> do you know about #ubuntu-bugs-announce ?
[01:26] <brendon1> know, what's that?
[01:26] <brendon1> another channel?
[01:26] <mrooney> it is a channel that announces new bugs as they come in
[01:26] <brendon1> I'll check it out
[01:26] <mrooney> it is a good source of fresh triage material
[01:27] <brendon1> ok, I'm in there.
[01:27] <brendon1> I want to organize my 1000  firefox bookmarks before I start triaging today though
[01:28] <mrooney> haha, sounds good
[01:58] <carlosjh> folks how do i know which alpha I have installed?
[01:59] <carlosjh> so I know I am triaging the bugs on the right place.
[02:02] <greg-g> carlosjh: are you updating your system on a semi-regular basis?
[02:03] <greg-g> short answer: it doesn't matter, just update your system with "aptitude safe-upgrade" and you will be running the latest version of Jaunty
[02:15] <carlosjh> i have like an Jaunty-alpha-5, i'll do a aptitude safe-upgrade, thanks!
[02:18] <mrooney> carlosjh: once you upgrade you have a daily :)
[02:53] <dtchen> greg-g: linux is building now, but i have no idea how to upload this test deb for you. pushing over a 56 kbps connection will be painful.
[03:08] <greg-g> dtchen: eek
[03:09] <dtchen> greg-g: obviously i'll rsync it, but it may take the better part of a half-day
[03:09] <greg-g> dtchen: ok. unless you want me to do anything locally with my bandwidth
[03:10] <dtchen> greg-g: oh, this will be a 64-bit kernel, so i trust you're running amd64
[03:10] <greg-g> dtchen: indeed I am.
[03:47] <dtchen> greg-g: uploading. f1f226342f3111ee1e74cbc8ec3f413f92e24f9354c97dc2dbe07a9c2c08ae56  sound-amd64-linux-image-2.6.28-11.35-generic.tar.lzma
[03:47] <dtchen> (sha256sum)
[03:55] <greg-g> dtchen: to where?
[04:07] <dtchen> greg-g: http://kernel.ubuntu.com/~dtchen/
[04:07] <dtchen> greg-g: please read the README first
[04:08] <dtchen> greg-g: note that those modules are compiled against the latest linux, 2.6.28-11.35-generic
[04:10] <greg-g> dtchen: /me nods
[04:12] <greg-g> again, you rock.
[04:12] <Hobbsee> dtchen: oh, you were right, btw.
[04:12] <Hobbsee> dtchen: new kernel fixed that part of the problem
[04:13] <dtchen> Hobbsee: excellent.
[04:13] <Hobbsee> indeed!
[04:14] <Hobbsee> dtchen: now, if i could get it so it doesn't kernel panic when trying to boot from uuid...that'd be nice
[04:17] <seclm193> hel all
[04:19] <mrooney> hello again :)
[04:19] <seclm193> lol
[04:19] <seclm193> you must work on bugs
[04:19] <mrooney> I do!
[04:19] <seclm193> lol, was thinking that if i was gonna start working on bugs, wanted to intoduce myself
[04:19] <seclm193> lol
[04:20] <scott_ev> seclm193: this will get you started: https://wiki.ubuntu.com/Bugs/HowToTriage
[04:21] <scott_ev> help is always wanted, welcomed, and needed
[04:22] <seclm193> ok, well the name is Chris, and i'm new here and just wanna help
[04:22] <scott_ev> my name is obvious, welcome
[04:22] <seclm193> lol, thanks
[04:23] <scott_ev> I soend my 'bug' time triaging bugs and have found it to be fun and rewarding
[04:23] <scott_ev> and the launchpad karma is nice too
[04:23] <scott_ev> where are you located, chris?
[04:24] <seclm193> Mississippi, i'm a software engineer major at Mississippi State University
[04:24] <scott_ev> sweet, I was born in Meridian
[04:24] <seclm193> kewl
[04:24] <seclm193> i'm from McComb origionally
[04:24] <scott_ev> are you a member of the local LOCo
[04:25] <scott_ev> doesn Mississippi have a LoCo?
[04:25] <seclm193> yea, we have one at school, just they meet Wensdays and I have to work
[04:25] <seclm193> :(
[04:25] <scott_ev> bummer
[04:25] <seclm193> i know
[04:25] <scott_ev> I have alot of fun with my AZ LoCo
[04:25] <scott_ev> here in the PHX arfea
[04:25] <scott_ev> area
[04:26] <seclm193> maybe soon I can be more active!!
[04:26] <scott_ev> in time
[04:26] <seclm193> yup
[04:26] <scott_ev> school must have priority
[04:26] <seclm193> i'm just reading all the info on the sites
[04:26] <scott_ev> cool
[04:26] <seclm193> #1, right beside my wife
[04:27] <scott_ev> the link I sent you is a great intro
[04:27] <scott_ev> it takes you to just about everything you'll want to know about workin with bugs
[04:27] <seclm193> that's what i'm reading
[04:27] <scott_ev> nice
[04:27] <scott_ev> well, good luck.  I have to get goin
[04:28] <seclm193> well, I've never done any ubuntu system programming so i'm really green to ubuntu development, so it's gonna take time
[04:28] <seclm193> it was nice to meet you, take care scott
[04:28] <mrooney> seclm193: a great tip I have is to sit in #ubuntu-bugs-announce which announces new bugs as they come in, help out any of them that you can, and subscribe to ones that you can't, to learn how other people triage them and such
[04:28] <mrooney> that is how I started out, just subscribing to tons of bugs and watching what other triagers did
[04:28] <seclm193> how do you subscrive to a bug?
[04:29] <mrooney> when you have it pulled up, there is a "subscribe" link in launchpad on the right, sort of near the top
[04:29] <seclm193> kewl, what happens when you subscribe to them?
[04:30] <mrooney> you get an email every time a change is made to it
[04:30] <seclm193> ok, kewl
[04:30] <mrooney> so you will see what changes / comments triagers are making, what questions to ask and such!
[04:30] <greg-g> dtchen: FATAL error: http://paste.lisp.org/display/77262
[04:31] <dtchen> greg-g: please pastebin `dmesg'
[04:32] <greg-g> dtchen: all of it: http://paste.lisp.org/display/77263
[04:34] <seclm193> thank you guys, i will hope I will be a lot of help in the time to come
[04:34] <seclm193> it's getting late, and i'm tired, I will talk to all of you later
[04:34] <seclm193> thanks again
[04:38] <dtchen> greg-g: hmm, ok. i'll have to rebuild the entire image
[04:38] <greg-g> dtchen: weee
[04:39] <greg-g> so, to go back to normal, I mv the backup back into place, depmod -e, and modprobe?
[04:40] <dtchen> greg-g: rm -rf sound that you just extracted, but then yes
[04:40] <greg-g> dtchen: right right.
[04:44] <greg-g> dtchen: warnings: http://paste.lisp.org/display/77264#1
[04:45] <dtchen> greg-g: you're not running current jaunty.
[04:46] <greg-g> oh dang, I just updated about 5 hours ago, heh
[04:46] <dtchen> erm, if you just updated 5 hours ago, you probably aren't running 11.35, either
[04:46] <dtchen> cat /proc/version_signature
[04:48] <greg-g> dang, yeah, 11.34, my bad.
[04:48] <dtchen> right.
[04:48] <dtchen> [    0.000000] Linux version 2.6.28-11-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #34-Ubuntu SMP Tue Mar 17 20:33:41 UTC 2009 (Ubuntu 2.6.28-11.34-generic)
[04:48] <dtchen> from your paste
[04:48] <greg-g> updating
[04:48] <greg-g> sorry
[04:48] <dtchen> np
[05:16] <greg-g> dtchen: is the plan still that you are going to rebuild that image?
[05:18] <dtchen> greg-g: yes, and i'll have to use jaunty's compiler this time
[05:18] <dtchen> those modules were built on my hardy machine
[05:18] <greg-g> dtchen: ok. I'm going hit the sack soon. just ping me when I should try again.
[05:18] <greg-g> gotcha
[06:05] <dholbach> good morning
[06:21] <mrooney> dholbach: morning!
[06:21] <mrooney> happy beta freeze day, I think?
[06:59] <thekorn> good morning
[07:28] <YoBoY> good morning
[07:55] <brendon> and a good morning to you sir/ma'am
[07:55] <Twin> morning ;)
[08:06] <YoBoY> ^^
[09:29] <pitti> hello
[09:31] <thekorn> hi pitti
[11:31] <BUGabundo> YoBoY: ping
[11:31] <BUGabundo> its not only you closing my bugs! eheh
[11:32] <YoBoY> ?
[11:32] <YoBoY> you have another minion?
[11:34] <YoBoY> BUGabundo: i'm blocked on your triaged bugs, i don't know how to deal with them
[11:34] <BUGabundo> ehehe
[11:34] <BUGabundo> are those so many?
[11:35] <YoBoY> BUGabundo: 72 but some are old bugs who have fix released
[11:36] <YoBoY> like bug 30584
[11:47] <BUGabundo> YoBoY: checking
[11:51] <BUGabundo> YoBoY: yes! those are dead in the water!
[11:52] <BUGabundo> until someone touch them
[11:52] <BUGabundo> LP needs a nudge button
[12:00] <YoBoY> ^^
[13:31] <pedro_> Hey Bugsquad! today we're having a cups hug day https://wiki.ubuntu.com/UbuntuBugDay/20090319 let's start squashing those bugs!
[13:31] <pedro_> hola MrKanister
[13:32] <MrKanister> hey pedro
[13:38]  * thekorn hugs pedro_ and MrKanister, happy hugday
[13:38]  * pedro_ hugs thekorn back
[13:38] <pedro_> happy hug day to you too ;-)
[13:40] <MrKanister> and /me huggs pedro back
[13:40] <MrKanister> damn
[13:40] <MrKanister> this should work...
[13:42] <MrKanister> oh...I mixed it up, I wanted to hug thekorn
[13:54] <jgoguen> bug 280233, is that actually cups or is it hplip?
[13:57] <pedro_> jgoguen: no idea, but probably some cups logs would help to determine where the issue is: https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS%20error_log
[13:58]  * pedro_ wonders why he didn't added that to the page
[13:58] <bddebian> Boo
[13:58] <pedro_> buuu!!
[13:59] <bddebian> :)
[14:10] <thekorn> can anybody with some CUPS insides please help me: forme bug 339591 looks like a regression of bug 300135
[14:10] <pitti> hey pedro_
[14:11] <pitti> thekorn: foomatic is tkamppeter's domain
[14:11] <pedro_> hello pitti
[14:11] <pedro_> thekorn: pitti is the man there ;-)
[14:15] <thekorn> ok, tkamppeter , when you have a minute, can you please help me with the bugs I mentioned a few lines above
[14:47] <johanbr> If I add a remote bug watch by putting in the URL, the project is chosen automatically.
[14:47] <johanbr> If this is wrong, how do I change the project?
[14:49] <charlie-tca> Is the source package correct?
[14:50] <charlie-tca> what bug number?
[14:50] <johanbr> there is no source package, it's an upstream bug watch
[14:50] <charlie-tca> The original bug has a source package, doesn't it?
[14:50] <johanbr> yes :) https://bugs.launchpad.net/ubuntu/+source/cups/+bug/285666
[14:51] <johanbr> I got the Poppler remote bug watch correct now, but would like the CUPS remote bug watch to be deleted.
[14:51] <charlie-tca> You just change the status on it to invalid them. We can't delete them
[14:52] <pedro_> it's a duplicate of bug 150187
[14:52] <pedro_> come one ubottu wake up
[14:52] <pedro_> s/one/on
[14:52] <pedro_> grg
[14:52] <johanbr> apparently I'm not allowed to change the status either
[14:53] <charlie-tca> You also should confirm the ubuntu bug in cups.
[14:54] <charlie-tca> CUPS status done
[14:55] <johanbr> charlie-tca: thank you. Would I be able to do that myself, or do you have special powers?
[14:55] <thekorn> pedro_, I think something went wrong while creating https://wiki.ubuntu.com/UbuntuBugDay/20090319#11%20Confirmed%20Bugs   there are more than 11 and the first ~10 have never been "confirmed"
[14:56] <charlie-tca> Bug control can do it. You can change the new to confirmed, though
[14:56] <tkamppeter> thekorn, at first note that foomatic-rip is a wrapper around Ghostscript and the printer driver. It is needed because CUPS expects a defined behavior (command line, environment variables, exit codes, ...) from its filters and the behavior of Ghostscript is different. So a "foomatic-rip failed" always needs further investigation, especially the CUPS error_log (with "debug" LogLevel) is needed as then one can see why foomatic-rip failed.
[14:56] <tkamppeter> In 90 % of the cases it is Ghostscript or the driver. Then the bug has to be moved to the approprioate package and the bug title should be changed and never left as "foomatic-rip failed".
[14:57] <pedro_> thekorn: yep just noticed that, I'm re-creating the list now, check again in 30 secs
[14:57] <tkamppeter> bug 300135 I have already triaged as described and found out that Ghostscript is the culprit. I have reported the problem upstream and got a fix.
[14:57] <johanbr> charlie-tca: well, pedro_ was right that it's a dup
[14:57] <pitti> tkamppeter: btw, I think I recently overheard Mike Sweet saying "that we still use foomatic", and it sounded as if it were obsolete?
[14:58] <charlie-tca> johanbr: pedro_ is almost always right, he knows the bugs better than most of us. So, just mark it as a duplicate
[14:58] <johanbr> :) done
[15:00] <tkamppeter> bug 339591 does not have enough info to determine what is the problem. One big problem of Intrepid was that hal-cups-utils created non-functional print queues if there was no matching driver. I have fixed this by auto-creating print queues only with an exact driver match, but I am not sure whether the reporter of the bug already got all my fioxes on the day when he reported the bug.
[15:01] <thekorn> tkamppeter, ok, thanks for this explanation, I will ask the reporter for more informations according to https://wiki.ubuntu.com/DebuggingPrintingProblems
[15:02] <tkamppeter> thekorn, so he needs to be asked to remove his non-working print queue(s), do a full update of his system and plug in his Brother printer again. If system-config-printer opens by itself, he has to choose the driver manually, if only a notification bubble about a newly created queue appears, he can go on testing.
[15:04] <tkamppeter> He should tell what exactly happened after plugging the printer. When he tries to print, he should activate debug mode with "cupsctl LogLevel=debug" and after the job going into "Stopped" state provide error_log as an attachment.
[15:04] <tkamppeter> He also should attch the PPD file(s) of his non-working print queue(s).
[15:05] <tkamppeter> pitti, Foomatic is not obsolete, I have issued 4.0.0 in January and got good comments on news sites. Many drivers including HPLIP need it.
[15:06] <thekorn> pedro_, thank you, it is looking much better now
[15:06] <pedro_> thekorn: should be fine now
[15:06] <pedro_> thekorn: alright thanks for checking ;-
[15:06] <pitti> tkamppeter: right, I found that quite surprising as well; maybe I (or he) mixed up something
[15:07] <tkamppeter> pitti, Mike Sweet does not like it because there are problems with jobs coming from Windows clients, using the CUPS driver for Windows. I never got a bug report to investigate this.
[15:07] <tkamppeter> As he told this the last time on one of the CUPS mailing lists I asked him to post a bug report, but he never did.
[15:09] <tkamppeter> pitti, I have also taken the CUPS costum options into foomatic-rip 4.0 as this was an important missing CUPS feature. I never got any reaction from Mike.
[15:14] <tkamppeter> jgoguen: bug 280233 is most probably HPLIP. What communicates directly with the printer is the "hp" CUPS backend, part of HPLIP. system-config-printer chooses this backend automatically for supported printers. You should check whether the user really uses it ("lpstat -v") and you should also get some additional info, like "lsusb", "lpinfo -v", the PPD which the user is using and perhaps also the error_log of a failed job.
[15:15] <tkamppeter> Note also that HP is using the Launchpad also for their upstream bugs. So for HPLIP bugs which are not packaging bugs you can add an upstream task (project HPLIP).
[15:15] <jgoguen> tkamppeter: thanks, that's what I figured.  Should I switch it to hplip now and add the upstream task, or wait for the error log?
[15:24] <tkamppeter> jgoguen: You can move it over already.
[15:58] <pedro_> tkamppeter: do you know if someone is working on bug 318742 ?
[16:04] <c0p3rn1c> Flash Player 10 Prerelease works MUCH better as the current packaged flash 10 on a 64 bit system, which can be found on this site:http://labs.adobe.com/downloads/flashplayer10.html
[16:04] <c0p3rn1c> I would recommend in updating the flashplugin-nonfree amd64 package with this module
[16:05] <c0p3rn1c> I havent seen any bugs on this version + a huge performance increase
[16:05] <BUGabundo> c0p3rn1c: is it new?
[16:06] <tkamppeter> pedro_, pitti does most uploads of CUPS ...
[16:06] <BUGabundo> I have the one that came out a few weeks back
[16:06] <bdmurray> mvo: I was looking at bug 341208 and I'm not really sure its a cups package issue
[16:06] <BUGabundo> as a security update
[16:06] <c0p3rn1c> BUGabundo: I don't know it just works better
[16:06] <pedro_> tkamppeter: alright thanks :-)
[16:06] <tkamppeter> pitti, can you have a look at bug 318742? Perhaps you can fix it for the beta?
[16:06] <pitti> pedro_: dbus policy checking> I'll take that
[16:07] <pedro_> pitti: should we assign bug 318742 to you?
[16:07] <pedro_> pitti: rock on, thanks!
[16:07] <c0p3rn1c> BUGabundo: southparkstudio.com works now, I never get gray flash panes anymore ...
[16:07] <pitti> tkamppeter: nah, it's not really critical for beta
[16:08] <tkamppeter> pitti, but for the rlease you will do it? Thanks.
[16:08] <pitti> tkamppeter: sure
[16:10] <c0p3rn1c> BUGabundo: I've found this flash player fix on http://ubuntuforums.org/showthread.php?t=772490&page=64
[16:11] <mvo> bdmurray: looking
[16:14] <c0p3rn1c> are there people in here who are experiencing bugs using the current 64bit flashplugin-nonfree package ?
[16:15] <BUGabundo> c0p3rn1c: define bugs!
[16:15] <BUGabundo> c0p3rn1c: I have one that needs reproducion test
[16:15] <BUGabundo> multiscreen, youtube fullscreen, ff 3.1
[16:15] <c0p3rn1c> BUGabundo: bugs: not working as it supposed to
[16:16] <BUGabundo> video will appear on laptop display and not external LCD where Firefox is
[16:16] <c0p3rn1c> everythings works perfectly here now, right, fullscreen also diden't always work on the current flashplugin-nonfree
[16:17] <c0p3rn1c> BUGabundo: I have a laptop aswell, I can test it now, 1 sec
[16:19] <c0p3rn1c> that bug sadly remains
[16:20] <c0p3rn1c> but I just enabled twinview, maybe it works better if I write the config to my xorg.conf
[16:22] <c0p3rn1c> brb
[16:24] <c0p3rn1c> back
[16:24] <c0p3rn1c> ok it works
[16:25] <c0p3rn1c> BUGabundo: now the video plays at the right screen
[16:26] <c0p3rn1c> BUGabundo: but it's not really full screen, it's not using the complete screen
[16:26] <c0p3rn1c> so that bug remains
[16:27] <c0p3rn1c> BUGabundo: scratch that, when I place firefox to my laptop screen, it still plays it at my CRT screen.
[16:27] <c0p3rn1c> on*
[16:30] <BUGabundo> so it's a bug c0p3rn1c?
[16:30] <BUGabundo> flash? FF? nvidia driver?
[16:31] <c0p3rn1c> nvidia 180.037
[16:32] <c0p3rn1c> FF?
[16:33] <BUGabundo> c0p3rn1c: 3.1 daily build from mozilla daily ppa
[16:33] <BUGabundo> nvidia-glx-180:  Installed: 180.37-0ubuntu1
[16:34] <BUGabundo> firefox-3.1:  Installed: 3.5~b4~hg20090317r23798+nobinonly-0ubuntu1~umd1
[16:34] <c0p3rn1c> I have a different firefox
[16:35] <c0p3rn1c> 3.07
[16:35] <BUGabundo> so it may not be FF
[16:35] <BUGabundo> that leaves GPU driver or Flash
[16:36] <c0p3rn1c> BUGabundo: well how do you explain that I can play normal video's full screen using totem?
[16:36] <BUGabundo> its not flash?
[16:36] <BUGabundo> I can also play full screen
[16:37] <BUGabundo> let me see if it obeys screen selection
[16:37] <c0p3rn1c> it does
[16:37] <c0p3rn1c> obay screen selection
[16:37] <BUGabundo> it does
[16:37] <BUGabundo> but FF won't
[16:37] <c0p3rn1c> FF = flash ?
[16:37] <BUGabundo> need to text opera or something
[16:37] <BUGabundo> FF= Firefox
[16:38] <c0p3rn1c> ah
[16:38] <c0p3rn1c> I also have problems using my tv-out on full screen mode
[16:39] <c0p3rn1c> I always lose part of the screen
[16:40] <c0p3rn1c> then the screen bounds are also wrong with playing fullscreen movies using totem or any other player
[16:42] <BUGabundo> c0p3rn1c: back
[16:44] <c0p3rn1c> wb BUGabundo
[18:00] <mrooney> jcastro: boy if any project could use that automatic upstream / downstream report, it is notify-osd
[18:00] <mrooney> every report pretty much belongs in both and right now it is such a random mix, some only upstream, some only downstream, some in both
[18:07] <pitti> however, why go through the trouble at all?
[18:07] <pitti> since "upstream" is very closely associated to ubuntu, they could just look at the ubuntu bugs
[18:08] <pitti> and only selectively add upstream tasks for some special situations
[18:08] <pitti> slavishly adding upstream tasks "just because" is just unnecessary bureaucracy IMHO
[18:31] <jcastro> mrooney: IMO I don't think it's so important to worry about upstream tasks for things already in lp.
[18:31] <mrooney> jcastro: the problem is how confusing it is to triage, and for people to find bugs
[18:32] <mrooney> the dupe thing isn't checking the other one for example, is it?
[18:32] <jcastro> yeah, I guess eventually when upstream -osd diverges from what is in the ubuntu release it'll be more important
[18:33] <mrooney> it is still confusing now, people are filing duplicate bugs in upstream and downstream with no idea :)
[18:33] <jcastro> yeah it's not ideal
[18:35] <mrooney> and also as a triager I don't have the same permissions on the upstream project, so I'd have to open an ubuntu task to do certain useful things like set importance
[18:35] <mrooney> how interesting
[18:36] <mrooney> jcastro: I imagine things being developed specifically for Ubuntu will be more and more common, so it seems like a solution like you have been working on / thinking about will be quite useful soon
[18:38] <jcastro> mrooney: I'll put it on the TODO to discuss with an lp bugs guy
[18:38] <mrooney> i like the idea of auto-opening an upstream task and auto-triaging the downstream task, perhaps
[18:38] <jcastro> mrooney: but tbh, at this point in the release I am focusing on links to remote bug trackers
[18:38] <mrooney> then you can still have two different importances which is useful
[18:38] <mrooney> jcastro: yeah I can see where it isn't a top focus :)
[18:49] <mrooney> jcastro: by the way any word on UDS sponsorship results? last I heard it was the 17th, but obviously that has passed. I'd try to be more patient if it wasn't so exciting! :)
[18:50] <jcastro> next week probably, we're a bit behind
[18:52] <greg-g> jono said something like that in his blog post
[20:00] <mrooney> greg-g: ahh, I haven't examined my google reader today
[20:02] <greg-g> mrooney: yeah, it was a pretty recent post from him, last day or so
[20:53] <randomaction> Hello everyone. I just posted a debdiff that will hopefully fix bug 340151 in hardy-backports, do I need to contact backporters to have it reviewed?
[20:58] <bdmurray> randomaction: yes, if it is for a package in backports you should work with the backports team
[21:04] <randomaction> Thanks, I see it's already on their mailing list anyway.
[21:07] <dtchen> greg-g: refreshing my amd64 schroot currently to rebuild a kernel for you
[21:07] <dtchen> greg-g: ETA until post: 4 hours
[21:08] <dtchen> greg-g: i should warn you that the necessary fix won't land for jaunty final. we're discussing post-release SRU.
[21:08] <greg-g> dtchen: awesome.  As long as I'm ok with my sound I'm cool :)
[21:09] <dtchen> greg-g: don't worry, i have a fugly hack for PA since the linux portion won't land for final.
[21:09] <dtchen> i feel like i'm at work all over again. sheesh.
[21:09] <greg-g> heh, sorry man. wish I could help in other ways than testing.
[21:24] <pregier> I'm seeing some nastiness between firefox-3.0 and sun-java6-plugin under hardy that doesn't seem to match any open bugs; I don't suppose anybody here with that particular combination of packages can reload http://java.sun.com/applets/jdk/1.4/demo/applets/JumpingBox/example1.html a few times to help guess what the odds are that this is reproducible?
[22:27] <calc> i have 0 new bugs on OOo! :)
[22:27]  * calc thinks this might be the first time he managed to get it to 0
[22:40]  * bdmurray high-fives calc
[23:02] <bdmurray> Anybody mind testing bug 337133 in Jaunty I just wanted some additional confirmation.
[23:19] <greg-g> calc: that is free drink worthy
[23:25] <greg-g> bdmurray: won't print for me, writing a comment. question though, what would you call that button that is not the power button and not the cancel button on an HP printer, the one that has the icon of a piece of paper and an arrow
[23:25] <greg-g> paper feed button?
[23:26] <hggdh> bdmurray, print job generated successfully on Jaunty
[23:26] <bdmurray> greg-g: did you try to print the whole thing or just 1 page?
[23:26] <greg-g> just one page, should try whole thing
[23:26]  * calc is going to try to get all his upstream bugs linked tomorrow :)
[23:26] <bdmurray> I did just one page too
[23:26] <calc> i might be able to get all three numbers above 90% by tomorrow :)
[23:27] <greg-g> calc++
[23:27] <calc> i think that might OOo as the only package on the report above 90% triaged
[23:28] <greg-g> bdmurray: fails silently when printing the whole thing, well, silently on the computer. I have a flashing amber LED on the printer
[23:30] <tkamppeter> bdmurray: I can also print the document of bug 337133 with the evince from Jaunty.
[23:31] <bdmurray> greg-g: you're just special then ;-)
[23:31] <greg-g> failing with hp DeskJet 952c, here.
[23:31] <greg-g> I guess
[23:32] <greg-g> tkamppeter: lsusb -vv for the printer and what other information would be helpful?
[23:32]  * greg-g goes to the debugging printer bugs wiki page
[23:34] <greg-g> oh yeah, apport-collect!
[23:35] <tkamppeter> greg-g, which bug number?
[23:37] <greg-g> bug 337133
[23:37] <greg-g> apport-collecting for it now
[23:38] <greg-g> bdmurray: umm, I selected "read anything" for apport-collect LP authorization, but it needs "change anything."  how do I change that?
[23:39] <greg-g> tries revoking its authorization
[23:41] <greg-g> nope, that just caused it (apport-collect) to crash and I'm sending a bug report for that now :)
[23:42] <greg-g> bug 345674   :)