[01:07] <seme> how does one search the mailing list
[01:07] <seme> all I can find are these crappy archive pages
[01:07] <seme> which doesn't really do much for me
[01:07] <maco> you could do a google site search
[01:08] <seme> true
[01:08] <seme> there isn't an interface to search through the mailing lists on the ubuntu site?
[01:14] <Flannel> seme: Which mailing list?
[01:15] <seme> ubuntu-devel-discuss
[01:15] <Flannel> seme: http://dir.gmane.org/index.php?prefix=gmane.linux.ubuntu  Archives a lot of them, and has some more searchability  http://dir.gmane.org/gmane.linux.ubuntu.devel.discuss
[02:06] <fcuk112> in ubuntu bugs advanced search, would it be useful to have an option to show bugs that have been reproduced?  i think it would help devs.
[02:07] <fcuk112> since there is already a flag for it in launchpad i don't think it would be too difficult to add.
[02:09] <hggdh> fcuk112: in theory, all bugs in Triaged state, and a lot of the Confirmed have been reproduced, or considered good enough for maintainer attention
[02:15] <fcuk112> hggdh: hummm it is not always the case...  a count of how many people are impacted would be useful too to allow devs to focus their energy.  at the moment it's hard to seperate those nasty transient bugs from those that can easily be reproduced and resolved.  another thing i have an issue with it is hard to drill down into bugs that don't yet have a patch.
[02:16] <hggdh> well. For the count -- the "I am/am not affected" helps there, as does the # of duplicates
[02:17] <hggdh> for the "without a patch" -- a bit more difficult, since most of the times we end up upstreaming the issue
[02:17] <hggdh> but, anyway
[02:17] <hggdh> we already have quite a number of bugs *with* patches, and still have not gone through them
[02:18] <hggdh> so I am not sure how much it would help, having this option
[02:19] <hggdh> finally -- if a triaged bug is not good enough for maintainer's attention... then it probably means it has been raised to triaged erroneously
[02:22] <fcuk112> Yes, the "I am/am not affected" is useful, it would be nice to have an additional column in the search results screen to show # affected.  What do you think?
[02:24] <hggdh> now, yes, I agree. it should be visible, either in the search, or in the bug itself
[02:26] <fcuk112> can we get someone to look into it?  what would be the best way to do that?
[02:26] <micahg> fcuk112: there should already be a bug report for it
[02:26]  * micahg is looking
[02:26] <hggdh> this would be a Malone (the LP bug tracker component); I would be surprised if there is not already a but for it
[02:26] <hggdh> heh. micahg preempted my response
[02:27] <fcuk112> :)
[02:27] <micahg> bug 271332
[02:27] <hggdh> thanks micahg
[02:28] <micahg> ugh, any estimate on ubot4?
[02:28] <micahg> https://bugs.edge.launchpad.net/malone/+bug/271332
[02:28] <hggdh> not to my knowledge. jdps was/is looking
[02:30] <hggdh> just subsribed myself to the bug. "the next few days", it says. since what, May?
[02:30] <micahg> it's low priority with no one assigned, doubt it'll be looked at before mid next year
[02:30] <hggdh> nooo, since Sep 2008!
[02:30] <micahg> it's open source though, so they take patches :)
[02:31] <hggdh> I guess so. Pretty good point for a hacker to look at
[02:31] <hggdh> dammit. Again you preempted me ;-)
[02:51] <linuxuser_ubuntu> hi
[02:51] <linuxuser_ubuntu> I recently downloaded the Ubuntu Karmic Koala and installed it on my Samsung NC10 netbook.
[02:52] <linuxuser_ubuntu> I am getting a mountall error while booting up Ubuntu on this netbook
[02:52] <linuxuser_ubuntu> Please help
[02:52] <micahg> linuxuser_ubuntu: try #ubuntu
[02:53] <linuxuser_ubuntu> micahg, this is posted as a bug in launchpad https://bugs.launchpad.net/ubuntu/karmic/+source/mountall/+bug/456806
[02:54] <micahg> linuxuser_ubuntu: ok, so you're asking about the bug...we don
[02:54] <linuxuser_ubuntu> micahg, which is why I posted this in this channel
[02:54] <micahg> ''t do regular support, but we do look at and help file bugs :)
[02:54]  * micahg is looking
[02:54] <linuxuser_ubuntu> micahg, the bug is cosidered to be fixed but I do not see a solution listed there
[02:54] <micahg> linuxuser_ubuntu: it's been fixed in the latest development version
[02:55] <micahg> linuxuser_ubuntu: you said it happens when you boot though
[02:55] <linuxuser_ubuntu> micahg, yes it happens when linux is loading
[02:56] <micahg> linuxuser_ubuntu: does this work for you? https://bugs.edge.launchpad.net/ubuntu/karmic/+source/mountall/+bug/456806/comments/8
[02:56] <hggdh> also, a new mountall has been released (probably in karmic-proposed now
[02:57] <linuxuser_ubuntu> micahg, the exact error I get is mountall: fsck . [607] killed by TERM signal.General fsck error
[02:57] <micahg> hggdh: nothing in proposed yet
[02:57] <hggdh> oh
[02:57] <hggdh> Scott released on Lucid
[02:57] <micahg> yep
[02:57] <hggdh> so we need a SRU
[02:58] <micahg> hggdh: that's why I was asking linuxuser_ubuntu if that fix in the comment works :)
[02:58] <hggdh> but yes, comment 8 should do the trick
[02:58] <micahg> hggdh: that's the one I posted
[02:58] <linuxuser_ubuntu> micahg, I will check it out and see if it works for me.
[02:58] <hggdh> yes indeed, I was acknowledging you
[02:58] <micahg> linuxuser_ubuntu: if you confirm it does, I'll prepare the patch
[02:59] <hggdh> SRUitis still strorn, I see ;-)
[02:59] <hggdh> strong
[02:59] <micahg> hggdh: just uploaded a test build for apparmor allowing chromium :)
[02:59] <hggdh> LOL
[03:00] <micahg> I see my SRU for apport still didn't wasn't allowed :(
[03:01] <micahg> or rather approved
[03:02] <hggdh> I think they are busy with alpha1 right now
[03:02] <micahg> yeah
[03:03] <linuxuser_ubuntu> micahg, Thanks a lot. I think it has solved my problem.
[03:04] <micahg> ok, I'll prepare the patch a little later
[03:04] <micahg> thanks linuxuser_ubuntu
[03:04] <hggdh> linuxuser_ubuntu: can you add a comment on the bug stating you tested it and it works?
[03:05] <linuxuser_ubuntu> hggdh, Yes I will. How do I do it ?
[03:05] <micahg> hggdh: actually, it might be better if linuxuser_ubuntu tests a build I make with the patch
[03:05] <hggdh> ah, OK. linuxuser_ubuntu ^^
[03:06] <linuxuser_ubuntu> micahg, I may not be able to download the patch if it is huge. I am using a 64kpbs dialup connection. heh
[03:06] <hggdh> and, with that, I call it a night. Bed awaits
[03:06] <linuxuser_ubuntu> \quit
[03:34]  * bcurtiswx kicks micahg's ethernet card
[03:34] <micahg> bcurtiswx: ath9k on karmic :)
[03:34] <bcurtiswx> :)
[03:34]  * micahg probably needs a reboot after the kernel update
[03:35]  * bcurtiswx knows you will
[03:35]  * micahg didn't think it would kill the wireless
[03:47] <micahg> bcurtiswx: just rebooted so I hope it's better :)
[03:48] <bcurtiswx> micahg: yeah hopefully
[04:04] <spO> hi
[04:04] <spO> when is the gcc version going to be updated from gcc version 4.4.1 to 4.4.3 ?
[04:07] <micahg> spO: lucid is on 4.4.2 right now
[04:07] <spO> yeah
[04:07] <spO> well when is karmic going to use 4.4.2 ?
[04:07] <micahg> karmic will not be changing
[04:07] <spO> are karmic people sleepy or something? how do i update that and allow everyone else to updat eit
[04:07] <spO> huh?
[04:07] <spO> WTF
[04:08] <micahg> spO: we don't jump versions in stable releases
[04:08] <spO> is this because karmic was a mishap?
[04:08] <spO> i heard that karmic was a mishap
[04:08] <micahg> spO: what do you mean?
[04:08] <spO> 4.4.0 and 4.4.1 are said to be HIGHLY BUGGY
[04:08] <spO> [19:43:59] * Now talking in #mplayer
[04:08] <spO> [19:43:59] * Topic is 'Do NOT paste inside the channel, use www.pastebin.com | gcc 4.4.0 causes problems, use >= gcc 4.4.2 | http://wiki.multimedia.cx/index.php?title=MPlayer_FAQ | svn co svn://svn.mplayerhq.hu/mplayer/trunk | 64bit real codecs available, win32 dlls still need 32bit mplayer, in /usr/local/lib/codecs | 1080 h264 requires 2.4ghz c2d / amd x2 2.8ghz+ | no plugin help | windows builds: http://oss.netfarm.it/mplayer-wi
[04:09] <spO> the gcc version is not stable
[04:09] <micahg> spO: the karmic version has been patched quite a bit
[04:09] <spO> ?
[04:09] <micahg> spO: is something still broke?
[04:09] <spO> just rad that topci okay
[04:10] <micahg> spO: I donm't see anything there
[04:10] <spO> i don't like you
[04:10] <micahg> !coc > sp0
[04:11] <micahg> ubot4: I need you
[04:11] <ubot4> Factoid 'I need you' not found
[04:11] <micahg> ubot4: coc
[04:11] <ubot4> The Ubuntu Code of Conduct to which we ask all Ubuntu users to adhere can be found at http://www.ubuntu.com/community/conduct/
[04:11] <spO> ?
[04:11] <spO> are you joking?
[04:11] <micahg> spO: no
[04:12] <spO> whatever you think I did, you lacked respect for what i said
[04:12] <spO> this is highly subjective
[04:12] <micahg> You said you don't like me, that violates the coc as I understand it
[04:12]  * micahg is trying to help
[04:12] <spO> i kept on saying something, and you acted like you didn't understand what iw as saying
[04:13] <spO> it was meant to cause disrespect for the words that i said
[04:13] <micahg> you said gcc-4.4 was buggy before 4.4.2, you posted a link with no information, I asked you for another one
[04:13] <spO> the #mplayer topic says that 4.4.0 and 4.4.1 cause bugs
[04:13] <spO> you can go to #mplayer
[04:13] <spO> they are the people who wrote it
[04:14] <micahg> spO: I don't have time to chase a ghost...do you have a link to gcc or something more authoritative?
[04:15] <spO> you cause me frustration and stress
[04:15] <micahg> spO: you might want to take this to #ubuntu-devel
[04:27] <CarlFK> ubuntu-bug xserver-xorg-video-nouveau  = "Collecting problem information ... This might take a few minutes. ............." it just filled the 80x25 screen with 2000 dots, at about 1/2 sec per is 15 minutes.  I have never seen it take this long.
[04:28] <CarlFK> any chance it is stuck in a loop?
[04:34] <emma> I went to report a bug and i was redirected to this page -- https://help.ubuntu.com/community/ReportingBugs
[04:35] <emma> At the beginning of that page it says, If you've come here when trying to file a bug about Ubuntu in Launchpad this was deliberate.
[04:35] <emma> Does that mean that it's some sort of punative action?
[04:36] <CarlFK> no
[04:36] <emma> Something about it seems wrong. And the wording makes it seem like I was kicked from launchpad.
[04:36] <CarlFK> yeah, I was kind bothered by it too
[04:36] <emma> the entire experience makes me feel like saying fine then forget it. It's already a bit of a hassle to bother reporting a bug.
[04:37] <CarlFK> ditto
[04:38] <CarlFK> especially when the recommended "utunbu-bug" thing as been collecting info for over 20 min...  grumble
[04:39] <CarlFK> I am sure the number of reports has dropped.  I only hope that the quality of info has made up for it
[04:41] <micahg> CarlFK: the number hasn't dropped and the quality is better
[04:41] <Hellow> Bleh, why did they have to add *that* crap to Launchpad?
[04:41] <micahg> emma: what bug are you trying to file?
[04:41] <Hellow> For most people, it will be just making the experience of trying to file a bug even harder.
[04:41] <micahg> Hellow: ??
[04:42] <micahg> Hellow: it's to prevent having to ask for information we need anyways
[04:42] <Hellow> micahg, A "Before you file a bug, please read http://url" line at the top of the bug filing page would have been better.
[04:42] <micahg> this was it saves the triagers time
[04:42] <micahg> Hellow: no, because people ignore it
[04:42] <micahg> we want people to use ubuntu-bug
[04:42] <emma> CarlFK: i just read through the page it redirects me to. The message i'm getting is that they don't want me to file bugs on Launchpad anymore.
[04:43] <CarlFK> emma: the bugs still get filed on lp - run ubuntu-bug, it collects info and uploads it as attchmetns to what you find on lp
[04:44] <emma> CarlFK: I see.
[04:44] <micahg> either ubuntu-bug or the report a bug link in each program
[04:44] <CarlFK> assuming it actually finishes collecting info.  I am about to file a bug against u-bug
[04:44] <micahg> CarlFK: apport-gtk never popped up?
[04:45] <CarlFK> ubuntu-bug xserver-xorg-video-nouveau  = "Collecting problem information ... This might take a few minutes. ............." it just filled the 80x25 screen with 2000 dots, at about 1/2 sec per is 15 minutes.  I have never seen it take this long.
[04:45] <Hellow> Another option would have been a page directly after clicking "File Bug" or whatever it is that says "Before you file a bug on Launchpad, please read url" then "If you have read that page and wish to continue with filing a bug, please press button at the bottom of the page".
[04:45] <CarlFK> except it has now filled a 80x50 term window, still dotting.....
[04:45] <Hellow> Instead of a hard link to the Ubuntu Community Documentation page.
[04:45] <Hellow> s/link/redirect
[04:45] <emma> CarlFK: Then the message I'm getting is that Canonical has created a launchpad which is not human readable/writable.
[04:45] <micahg> CarlFK: I'd say CTRL-C it and try again
[04:46] <CarlFK> emma: incorrect...  just roll with it for now
[04:46] <emma> Okay
[04:46] <CarlFK> emma: you can't critized it like this till you have tried it.  then you can, and it will make more sense :)
[04:47] <emma> micahg: im going to try to submit a bug report on irssi.
[04:47] <micahg> emma: ah, so, ubuntu-bug irssi
[04:48] <emma> alright.
[04:50] <Hellow> I also just noticed a bad flaw with wanting everyone to use ubuntu-bug: Quite a few people who use Launchpad don't use Ubuntu or Debian.
[04:50] <micahg> Hellow: ubuntu-bug is only for Ubuntu
[04:51] <maco> Hellow: non http://bugs.launchpad.net/ubuntu/* pages accept bugs through the web interface
[04:51] <maco> only ubuntu paths tell you to go use ubuntu-bug
[04:51] <Hellow> maco, Ah, thanks. I didn't know that one.
[04:54] <CarlFK> is it OK to have /n in a translated string?
[04:54] <CarlFK> _('The collected information can be sent to the developers to improve the\n'   'application. This might take a few minutes.'))
[04:55] <micahg> CarlFK: idk
[04:56] <CarlFK> Package ubuntu-bug does not exist
[04:56] <CarlFK> what package is it in?
[04:57] <micahg> apport
[04:59] <micahg> CarlFK: what bug are you filing against ubuntu-bug?
[04:59] <CarlFK> that it is taking so long
[04:59] <micahg> CarlFK: did you retry?
[05:00] <CarlFK> not yet
[05:00] <aburch> Can somebody verify that anyevent-perl is really a duplicate of libanyevent-perl and then requesting removal? See also #470560.
[05:02] <emma> https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/493048
[05:02] <emma> Is that a good bug report
[05:02] <emma> ^
[05:03] <micahg> emma: looks good
[05:03] <CarlFK> #397140
[05:03] <CarlFK> bug 397140
[05:04] <micahg> ubot4: bug 397140
[05:04] <micahg> ugh
[05:04] <CarlFK> I am not having a good bug day
[05:06] <emma> CarlFK: micahg the ubuntu-bug thing is not as bad as i thought it was. Being redirected to a page that is written in a way that makes me wonder if I am being repremanded is not good though. I hope someone reconsiders that or at least changes the wording.
[05:08] <CarlFK> emma: my feelings exactly.
[05:15] <CarlFK> according to strace...
[05:15] <CarlFK> gettimeofday({1260076377, 725769}, NULL) = 0
[05:15] <CarlFK> select(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout)
[05:16] <micahg> aburch: looks like a duplicate package, I'll look into it a little later
[05:22] <CarlFK> micahg: ^c, re-ran... still collecting...
[05:22] <micahg> CarlFK: ugh, yeah, strace + ubuntu-bug apport?
[05:23] <CarlFK> https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/493050
[05:25] <nigel_nb> micahg: apport having an issue?
[05:25] <micahg> nigel_nb: idk, CarlFK was
[05:25] <nigel_nb> small world, I was just reading his report
[05:27] <nigel_nb> CarlFK: just FYI, it works fine for me
[05:28] <micahg> for me too
[05:28] <CarlFK> it worked for apport :)
[05:28] <nigel_nb> you're getting timed out?
[05:29] <nigel_nb> strange
[05:29] <nigel_nb> i'm not an expert at debugging though
[05:30] <CarlFK> so I ran it with xforwading, and got the gui "collecting..." dialog - hitting cancel does not stop it
[05:32] <nigel_nb> I've no clue, we'll have to wait and see
[05:34] <nigel_nb> micahg: does this bug qualify to be confirmed as there is enough info?
[05:35] <micahg> nigel_nb: I think confirmed means you can confirm
[05:35] <micahg> triaged would mean enough info even if you can't confirm
[05:35] <nigel_nb> ah
[05:35] <nigel_nb> I can't set it then
[05:37] <^arky^> hi micahg
[05:38] <micahg> hi ^arky^
[05:40] <^arky^> howz is it going over there in windy city micahg
[05:40] <micahg> ^arky^: ok
[05:40] <^arky^> have you seen jcostro around ?
[05:40]  * ^arky^ needs to renew his bugsquad membership 
[05:40] <micahg> ^arky^: it's the weekend
[05:40] <micahg> ^arky^: bugsquad is open, you mean bug-control
[05:40] <^arky^> yes
[05:41] <micahg> ^arky^: might have to wait until monday, don't know if any admins are on over the weekend
[05:42] <^arky^> ok, I leave a message on lp then
[05:54] <nigel_nb> anyone on irssi?
[05:57] <dtchen> yes
[05:58] <nigel_nb> dtchen: how do u change windows?
[05:58] <nigel_nb> hold on, I'll give u the bug number
[05:58] <dtchen> for buffers 1-10, meta+#
[05:58] <dtchen> or, /win #
[05:58] <nigel_nb> bug 493048, https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/493048
[05:58] <dtchen> (10 -> 0)
[05:59] <nigel_nb> using the /join command is not supposed to change windows if I'm not mistaken?
[06:00] <dtchen> it does here
[06:01] <nigel_nb> what i mean is if u are in channels a,b,c
[06:01] <nigel_nb> does using join again change windows?
[06:02] <dtchen> yes, it does
[06:02] <dtchen> it works just fine for me in Hardy, Jaunty, and Karmic
[06:02] <nigel_nb> okay, so its my ignorance that I can't reproduce it
[06:02] <dtchen> both joining a new channel and switching to an existing (already-joined) channel
[06:03] <nigel_nb> oh
[06:03] <nigel_nb> when i'm using it
[06:03] <nigel_nb> all new channels come like a new horizontal bar
[06:03] <nigel_nb> thats normal?
[06:03] <maco> no
[06:03] <maco> should be a new number on the horizontal bar
[06:03] <maco> though of course your .irssi/config has an effect
[06:03] <maco> since it's what determines your layout
[06:04] <nigel_nb> great
[06:04] <nigel_nb> why is my default like this, grr
[06:04] <dtchen> I should be clear that I'm using hardy-security/updates, jaunty-security/updates, and karmic
[06:05] <dtchen> (so, 0.8.12-3ubuntu3.1, 0.8.12-6ubuntu1.1, and 0.8.14-1ubuntu1, respectively)
[06:05] <nigel_nb> i think my issue is something at my end
[06:05] <nigel_nb> but I got the bug confirmed
[06:06] <nigel_nb> when u use /join to switched to an already joined channel, the extra space is creating problems
[06:08] <nigel_nb> maco: feeling better?
[06:08] <maco> yes thanks
[06:08] <maco> and you?
[06:08] <dtchen> very odd; I cannot reproduce that symptom on any of these [freshly created] users
[06:09] <CarlFK> http://dev.personnelware.com/carl/a/guid_mountpoint.png  using the guid for the window title seems odd.  is this worth filing a bug against?
[06:09] <nigel_nb> maco: I'm frustrated and sleepy, and nursing a headache
[06:10] <micahg> CarlFK: yes
[06:10] <dtchen> CarlFK: if you feel that the UUID is distracting, yes, please file a bug
[06:10] <CarlFK> package?
[06:10] <micahg> CarlFK: my geuss is it's already filed, but please check
[06:10] <micahg> nautilus?
[06:10] <CarlFK> micahg: yes - I filed it :)
[06:10] <micahg> CarlFK: gnome?
[06:12] <nigel_nb> irssi bugs should be filed upstream?
[06:14] <micahg> yep: http://bugs.irssi.org/
[06:15] <nigel_nb> hm, singing up
[06:15] <nigel_nb> oops, signing up
[06:32] <nigel_nb> irssi upstream has a very odd interface
[06:34] <nigel_nb> micahg: just a confusion
[06:35] <nigel_nb> bug 493048, is a bug or feature request (my instincts say bug)
[06:37] <micahg> nigel_nb: low priority bug
[06:38] <nigel_nb> thanks, the upstream version lets me select all this (i'm surprised though)
[06:38] <nigel_nb> i mean the upstream tracker
[06:39]  * micahg never played with flyspray
[06:43] <nigel_nb> micahg: flyspray cannot be tracked by launchpad?
[06:44] <micahg> nigel_nb: idk
[06:45] <nigel_nb> not able to link it up
[06:45] <micahg> nigel_nb: not on the list https://help.launchpad.net/Bugs/RemoteTrackerCoverage
[06:45] <micahg> nigel_nb: jsut add a note in the bug
[06:45] <nigel_nb> did that
[06:45] <nigel_nb> been playing around for quite some time
[06:45] <nigel_nb> flyspray is a terror
[06:45] <micahg> https://bugs.edge.launchpad.net/malone/+bug/28738
[06:46] <nigel_nb> first it sent confirmation mail to my spam box
[06:47] <nigel_nb> anything i can do there?
[06:47] <micahg> nigel_nb: nope
[06:47] <micahg> nigel_nb: unless you want to write the code for LP :)
[06:48] <nigel_nb> I'll pass
[06:48] <nigel_nb> I can't edit gcalctool's code
[06:54] <nigel_nb> micahg: once reported upstream, we leave the original bug alone?
[06:54] <nigel_nb> in confirmed, undecided?
[06:55] <micahg> nigel_nb: I should mark triaged
[06:55] <micahg> hold on
[06:55] <nigel_nb> oh, thanks :)
[06:57] <micahg> nigel_nb: done
[06:57] <nigel_nb> :)
[07:43] <what_if> I am working on a bug (#394373 ) and would like to know the proper steps to take in order to close it.
[07:44] <andre__> URL?
[07:46] <what_if> https://bugs.launchpad.net/ubuntu/+source/qalculate-kde/+bug/394373
[07:46] <micahg> what_if: what's the question?
[07:47] <micahg> what_if: first, you don't assign yourself a bug unless you are working on a fix
[07:48] <what_if> What to do now. A fix was released withthe newer packages, so I set the status to "Fix Released", but does this close the bug or must I nominate for a release?
[07:48] <micahg> nominate for release if you want it in a previous release
[07:49] <what_if> So assigning the bug to myself was incorrect in this case?
[07:49] <micahg> yes
[07:49] <micahg> you should subscribe if you want to keep up to date
[07:51] <what_if> who then would I notify that a bug has been fixed and released, but that nobody updated the launchpad entry?
[07:53] <micahg> what_if: no one, you should note the version that it's fixed in and marked fixed released if it's a confirmed bug, if it's an unconfirmed bug, mark as invalud
[07:53] <micahg> invalid
[07:53] <micahg> ubot4: status
[07:53] <ubot4> Factoid 'status' not found
[07:53] <micahg> ubot4: Status
[07:53] <ubot4> Factoid 'Status' not found
[07:53] <micahg> what_if: https://wiki.ubuntu.com/Bugs/Status
[07:56] <what_if> apologies... I have been assigning bugs to myself as a way to track them and assumed this was the proper way to do things.
[07:57] <what_if> that said, I have one more assigned bug. https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/206176
[07:59] <what_if> that is also on it's way to being closed. Thank you for all your help, I'm still learning the way things are done in launchpad.
[08:15] <micahg> what_if: no, you don't assign if you're not making a patch
[08:15] <micahg> you can ask a question and subscribe
[08:16] <what_if> ok, I unassigned myself. Won't do that in the future. :)
[08:16] <micahg> what_if: you should probably talk to #kubuntu-devel about this bug, their new policy is to close bugs that are upstream
[08:17] <micahg> thanks for helping out though what_if
[08:17] <micahg> what_if: if you have a special interest in KDE, you should definitely talk to #kubuntu-devel
[08:18] <what_if> YW. This is why I'm starting out with such simple bugs, until i "learn the ropes"
[08:18] <micahg> what_if: have you read the initial documentation on how to triage
[08:19] <micahg> in here we don't actually "fix" bugs, but get them into the hands of those that can fix
[08:19] <micahg> what_if: https://wiki.ubuntu.com/Bugs/HowToTriage
[08:23] <what_if> I have... but am reluctant to invalidate this bug as a "read the manual" problem until I get a response back that my proposed solution fixes the problem the users are seeing.
[08:23] <what_if> was also reluctant to set it to confirmed, as from here it seems to just be an issue of a change in the way the Kate program operates.
[08:24] <micahg> what_if: triaged means that it's ready for a developer to look at
[08:24] <micahg> what_if: if you want to "triage" bugs, you should focus on New, Incomplete, and Confirmed
[08:25] <micahg> what_if: if you want to make patches/fixes, then this is the wrong channel
[08:26] <micahg> what_if: I'm not trying to discourage you, but just explaining that we have different teams for these things
[08:26] <what_if> I am assuming ubuntu-devel is for patches/fixes?
[08:26] <micahg> what_if: no, that's for development discussion, #ubuntu-motu is for patches/fixes
[08:27] <micahg> what_if: but that bug, you need to talk to #kubuntu-devel
[08:28] <what_if> ok, I will get with the kubuntu-devel people about the process for this bug. Thank you again for all the help.
[08:32] <damagednoob> why "report a bug" link redirect me to the wiki?
[08:32] <damagednoob> why does*
[08:35] <micahg> damagednoob: because we have a process for reporting bugs
[08:36] <damagednoob> okay
[08:36] <damagednoob> i'm trying to file a "needs packaging" bug
[08:36] <damagednoob> what's the process for that
[08:37] <micahg> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[08:37] <damagednoob> "To get a package into Ubuntu, please file a bug in Launchpad"
[08:37] <micahg> damagednoob: there's a link there that will work
[08:40] <damagednoob> aaah got it
[08:40] <damagednoob> i have to join the bugsquad team first
[08:41] <micahg> damagednoob: to do what?
[08:41] <damagednoob> to report a bug
[08:41] <micahg> damagednoob: no you don't
[08:41] <damagednoob> well it's working now and it wasn't before
[08:41] <aburch> Is there any rationale why Ubuntu restricts changing the priority of bugs to members of ubuntu-bugcontrol when anybody can mark a bug as invalid/fixed/...?
[08:41] <micahg> damagednoob: where does it say that?
[08:42] <aburch> In Debian it seems to work quite well without any access restrictions.
[08:42] <damagednoob> https://wiki.ubuntu.com/MOTU/Contributing -> Preparing New Packages
[08:42] <micahg> aburch: I'm sure there is, but I don't know offhand
[08:42] <micahg> damagednoob: that's if you want to package something
[08:43] <damagednoob> micahg, it doesn't matter what anything says, i'm saying what happened
[08:43] <aburch> I would like to set priority for packages that I maintain in Debian, but first launchpad silently drops my mails to the bugcontrol mailing list, then I forgot about it for a while.
[08:43] <damagednoob> i couldn't file a bug until i joined the bug squad
[08:43] <micahg> aburch: we use the priorities to determine what to work on, and ubuntu is more of an everyone OS than debian is
[08:43] <micahg> damagednoob: I don't think that's the case
[08:44] <micahg> damagednoob: I think that was coincidence
[08:44] <damagednoob> micahg, okay
[08:44] <micahg> aburch: it prevents people from setting their issues to High because they want it fixed and distracting the developers, I would think
[08:45] <micahg> aburch: that's also across all of launchpad, not just ubuntu
[08:46] <aburch> Now I actually managed to send a mail to the list, but nobody relied (for 3 weeks).
[08:46] <micahg> aburch: https://help.launchpad.net/Bugs/Statuses
[08:46] <micahg> aburch: which list, for whast?
[08:47] <aburch> micahg: Everybody can change severity (the equivalent of importance) in the Debian BTS. It does not seem to cause many problems.
[08:47] <aburch> micahg: The ubuntu-bugcontrol mailing list.
[08:47] <micahg> aburch: debian is mainly used by sysadmins and power users, ubuntu is used on the desktop
[08:48] <micahg> aburch: that was right before UDS, please send a followup message and someone should reply this time
[08:49] <micahg> I see your message
[08:49] <micahg> aburch: in the mean time, you can ping someone in here and we'll be happy to set the importance for you
[09:00] <aburch> Ok.
[09:01] <aburch> Could somebody set 237233 to wishlist (feature request), 424404 to wishlist (feature request).
[09:02] <micahg> aburch: yep :)
[09:02] <micahg> aburch: is it triaged, do you have all the info you need?
[09:03] <aburch> While 312051 is already fixed (in Debian unstable), should bugs like there be low or medium in Ubuntu?
[09:03] <aburch> IMO giving wrong results (i.e. scheduling a job at the wrong time) is not so nice ;)
[09:04] <micahg> aburch: fix committed is if we have  a fix in the archive
[09:04] <micahg> aburch: I'll set that one to high
[09:05] <aburch> micahg: Hmm? If the fix is in the archive, shouldn't that be fix released?
[09:05] <micahg> is it in Lucid?
[09:05] <aburch> No, only in Debian Sid and the VCS.
[09:06] <micahg> nope, not in lucid
[09:06] <micahg> yeah, so that's triaged still
[09:06] <micahg> aburch: we're syncing from testing this round
[09:08] <micahg> aburch: BTW, if you can include the LP bug # in your changelog in addition to the debian bug if you have it, LP will automatically close bugs that are in packages that are sync'd
[09:08] <micahg> aburch: nm, I see you already do :)
[09:09] <aburch> micahg: The first two bugs have all required information, it's just missing time to actually fix them ;)
[09:09] <micahg> aburch: midi music bug is wishlist?
[09:11] <aburch> micahg: I see it as a feature request (changing features enabled at compile time).
[09:11] <aburch> micahg: If you see it as a bug, low is fine too.
[09:12] <micahg> just wanted to double check, I'll set it as wishlist
[09:12] <micahg> aburch: unless it's a regression
[09:13] <aburch> No, MIDI support was never enabled in the Debian package.
[09:13] <micahg> aburch: ok, wishlist it is
[09:13] <micahg> done for all of them I think
[09:13] <aburch> Thank you.
[09:50] <damagednoob> micahg, okay i figured it out, the link automatically redirects me to help. I have to use the redirect link to file a bug against no package
[09:50] <damagednoob> the no redirect*
[09:55] <micahg> damagednoob: you should only file a no-redirect bug if it's for a needs packaging bug
[09:57] <damagednoob> micahg: i was trying to file a needs packaging bug :P
[13:50] <cdavis> Can I set 493131 to invalid?
[13:57] <mrand> cdavis: in general we mark questions back to submitters as incomplete rather than invalid.  Having said that, 1B sounds like a rather strange "speed", doesn't it?  Almost like the submitter is referring to bytes transferred rather than speed.
[14:00] <cdavis> No, I believe the default conky install labels it as speed even though that doesn't sound like speed at all: Up:$color ${upspeed eth0} ${color grey} - Down:$color ${downspeed eth0}
[14:23] <craigbass1976> Figures I talk in the midst of a split....
[14:23] <craigbass1976> https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379...  I have an updated Jaunty and still can't print.  I was in here on  Nov 20 17:51:25 talking to qense (my name was judy that day) and I can't seem to print pdf files correctly or sometimes at all
[14:23] <craigbass1976> https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379...  I have an updated Jaunty and still can't print.  I was in here on  Nov 20 17:51:25 talking to qense (my name was judy that day) and I can't seem to print pdf files correctly or sometimes at all
[14:35] <BUGabundo> boas
[14:54] <craigbass1976> https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379...  I have an updated Jaunty and still can't print.  I was in here on  Nov 20 17:51:25 talking to qense (my name was judy that day) and I can't seem to print pdf files correctly or sometimes at all
[15:00] <deuxpi>  
[15:01] <BUGabundo> any idea whose upstream of smplayer?
[15:03] <jpds> BUGabundo: http://smplayer.sourceforge.net/ ?
[15:19] <craigbass1976> https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379...  I have an updated Jaunty and still can't print.  I was in here on  Nov 20 17:51:25 talking to qense (my name was judy that day) and I can't seem to print pdf files correctly or sometimes at all
[15:25] <BUGabundo> great... :( compiz has its own BTS
[15:25] <BUGabundo> anyone has an account there that can upstream this bug
[15:25] <BUGabundo> https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/493197 ?
[15:25] <BUGabundo> http://bugs.opencompositing.org/
[15:53] <jpds> BUGabundo: Talk to Amarath. :)
[15:54] <BUGabundo> gonna be nauty and sub him to the bug :)
[15:54] <jpds> He's already replied.
[15:54] <BUGabundo> lol
[15:54] <hggdh> craigbass1976: would you please stop repeating yourself?
[15:56] <hggdh> darn, I am late, at least 1.5 hours late ;-)
[15:56] <hggdh> ola BUGabundo, long time
[15:56] <hggdh> bug 12345
[15:56] <BUGabundo> hggdh: orly?
[15:56] <BUGabundo> been here every day my friend
[15:57] <hggdh> olry? Qui?
[15:57] <hggdh> I have not
[15:57] <BUGabundo> ahh
[15:57] <BUGabundo> lol
[15:57] <hggdh> :-)
[15:57] <BUGabundo> your nick has
[15:57] <^arky^> hi
[15:57] <hggdh> but my nick and I parted for a while
[15:58] <hggdh> hi ^arky^
[15:58] <hggdh> the nick stayed here, and I went elsewhere
[15:58] <BUGabundo> eeh
[15:59] <BUGabundo> enjoyed the vacations?
[15:59] <hggdh> no, not really, it was more like work
[16:01] <hggdh> craigbass1976: what is your issue?
[16:01] <BUGabundo> le
[16:03] <BUGabundo> hggdh: work is good :)
[16:04] <hggdh> BUGabundo: I know, I know ;-) but a lot of places do not allow us to connect to IRC -- <gasp> There Be Malware </gasp>
[16:04] <BUGabundo> hahhaahahaha
[16:04] <BUGabundo> web FTW
[16:04] <nigel_nb> hey hggdh :)
[16:04] <hggdh> is there a web interface to IRC? I am an old hand, not used to these new thingies
[16:05] <hggdh> hi nigel_nb
[16:05] <nigel_nb> hggdh: webchat.freenode.net
[16:05] <nigel_nb> thats the web interface if you're interested
[16:06] <hggdh> oh boy
[16:06] <hggdh> YES, I am interested. Is there, also, per chance, a HTTPS one?
[16:06] <nigel_nb> dont remember
[16:06] <nigel_nb> checking
[16:07] <nigel_nb> welcome hggdh-web
[16:07] <hggdh-web> cool
[16:07] <BUGabundo> hggdh there's freenode webchat but it SUCKs
[16:07] <nigel_nb> hggdh-web: thats how I was talking from work yday
[16:07] <BUGabundo> compared to mibbit
[16:07] <nigel_nb> BUGabundo: better than nothing
[16:07] <nigel_nb> ;)
[16:07] <BUGabundo> thers a better one
[16:07] <nigel_nb> there is?
[16:07] <BUGabundo> jcastro bloged about it
[16:07] <nigel_nb> there was?
[16:07] <BUGabundo> let me look for it
[16:07] <hggdh-web> alice?
[16:08] <nigel_nb> the best is irssi + screen
[16:08] <hggdh-web> does not work on Hardy
[16:08] <nigel_nb> and SSHing into it
[16:08] <BUGabundo> hggdh maybe
[16:08] <hggdh-web> nigel_nb: there is also alice (which, methinks, runs irssi also)
[16:09] <craigbass1976> hggdh, I wasn't sure if the netsplit cause trouble with my being heard;  I'm also using xchat on someone else's box, and wasnt' sure if I was being heard.  I guess I am.  my issue is trouble with printing pdfs in jaunty to a networked brother.  I'm going to solve it I guess by trying karmic
[16:09] <hggdh-web> but my servers run hardy
[16:10] <nigel_nb> craigbass1976: to a networked ?
[16:10] <nigel_nb> printer?
[16:10] <hggdh> craigbass1976: this is an option. the bug you pointed to is closed fix released on jaunty-updates
[16:11] <craigbass1976> hggdh, despite updates, I still have the trouble
[16:11] <hggdh> hum
[16:11] <nigel_nb> hggdh: I couldn't use that option coz the only comp I have is a laptop wich I shutdown when I'm not here
[16:12] <hggdh> craigbass1976: difficult to say what might be, then. Nothing prints? Something prints?
[16:12] <nigel_nb> so, webchat is the only way for me :(
[16:12] <hggdh> nigel_nb: ah, that would make it very hard indeed
[16:12] <nigel_nb> checkout bug 394373
[16:13] <nigel_nb> someone (who I dont think is the developer) has assigned it to himself
[16:13] <craigbass1976> hggdh, sometimes nothing, sometimes only the first page.  pdfs are the biggest problems.  I just printed a web page though, and the text pages went fairly quickly, but the one with images took a while longer
[16:14] <nigel_nb> ubot4: bug 394373
[16:14] <hggdh> craigbass1976: images *may* take much longer, this is expected
[16:14] <hggdh> nigel_nb: looking at it
[16:14] <nigel_nb> strange, the bot in #ubuntu-motu works, ontly ubot4 is having an issue
[16:15] <BUGabundo> nigel_nb: hggdh: http://castrojo.wordpress.com/2009/12/04/alice-where-have-you-been-all-my-life/
[16:15] <craigbass1976> hggdh, but the pdfs just hog out.  Printer says "receiving data" forever.  I've left it a half hour before calling it a bust
[16:15] <nigel_nb> BUGabundo: thanks, read through it 2 minutes ago :)
[16:16] <hggdh> craigbass1976: the only suggestion I can give you is to open a new bug on it
[16:17] <hggdh> nigel_nb: I really cannot understand this bug. I am guessing the guy as trying to help, but did not get through the wiki
[16:17] <nigel_nb> I got to the bug from the logs
[16:18] <nigel_nb> micah asked him not to assign bugs to himself if he's not fixing
[16:18] <hggdh> ah, OK. Let me follow his bug mail
[16:20] <hggdh> oh boy. There we go into another issue with well-intentioned, but mistaken folks
[16:22] <nigel_nb> hggdh: well, at least he tried to help
[16:22] <nigel_nb> I'm happy with that, though he needs to update his reading skills a bit and read the wiki
[16:24] <hggdh> indeed
[16:26] <nigel_nb> oh, just a suggestion, we need to make more people aware of the mentorship program
[16:27] <hggdh> nigel_nb: we need to speed up the mentorship... we have a lot of candidates. Until we catch up, I would rather lay it low
[16:27] <nigel_nb> oops
[16:27] <nigel_nb> okay, then we should encourage people to hang out here and ask any doubts
[16:29] <hggdh> this is what I have been doing. etali, for example, is waiting for a mentor (and could ask questions here -- nugde, nugde)
[16:34] <hggdh> s/nugde/nudge/ # sigh dyslexia won
[16:35] <nigel_nb_> hggdh: got my last message?
[16:36] <hggdh> nigel_nb_: last one: <nigel_nb> okay, then we should encourage people to hang out here and ask any doubts
[16:36] <nigel_nb_> hmm,
[16:36] <nigel_nb_> even though officially I have a mentor, I general ask the room
[16:36] <nigel_nb_>  been taking help from micah often, coz he's up till I hit the bed :)
[16:37] <hggdh> I know, I have been following your work :-)
[16:37] <nigel_nb_> oh :)
[16:37] <nigel_nb_> now that's an awesome mentor :)
[16:38]  * hggdh bows
[16:38] <hggdh> but this is the point: anyone here can help, and *will* help
[16:39] <nigel_nb_> yep
[16:39] <hggdh> the mentor is mostly the one that will give a final say (well, an initial final say)
[16:39] <nigel_nb_> haha
[16:39] <nigel_nb_> just need people ask out here
[16:39] <hggdh> yes
[16:40] <hggdh> etali => ask <= we will help
[16:40] <hggdh> :-)
[16:40] <nigel_nb_> :)
[16:43] <hggdh> what I think happens is new folks are worried of saying something (they classify as) dumb. Well, let me say this publicly: it will be difficult for anyone to be dumber than I am (or stubborner, or slower). But, usually, I do understand -- eventually.
[16:45] <nigel_nb_> bug 493191, looks more like its a brainstorm idea, can you take a look?
[16:46] <hggdh> nigel_nb_: BTW -- https://webchat.freenode.net/ they do provide HTTPS :-) \o/
[16:46] <nigel_nb_> wow cool
[16:46] <nigel_nb_> but my office network is thankfully secure
[16:47] <hggdh> for me this is important because some sites I get to go I do not want them to monitor me that much
[16:47] <hggdh> it is more of a privacy issue than a security one
[16:47] <nigel_nb_> our office is kind in that way
[16:48] <nigel_nb_> they gave given us one computer, which we can do all our personal stuff, mails, browsing
[16:48] <nigel_nb_> almost any thing can be done on that one computer (except work)
[16:48] <nigel_nb_> they just dont want us to do both on the same system due to security concerns
[16:48] <hggdh> heh
[16:48] <nigel_nb_> hggdh, are you in the US?
[16:48] <hggdh> nigel_nb_: yes, TX
[16:49] <nigel_nb_> then you should have an idea about how security is required for medical documents
[16:49] <hggdh> oh, I know very well...
[16:50] <nigel_nb_> thats the reason :)
[16:50] <nigel_nb_> along with the bug I mentioned earlier is bug 493195 (this could be wishlisted I think, but I'm not sure it needs to be)
[16:52] <hggdh> well, I would have to run UNR to check -- and I do not have a netbook
[16:53] <hggdh> I am split if this is a bug or a wish
[16:53] <hggdh> so I will leave it alone...
[16:53] <nigel_nb_> nothing?
[16:53] <hggdh> sorry, nigel_nb_, no opinion here
[16:54] <nigel_nb_> okay, skipping
[16:58] <nigel_nb_> I cant understand bug 493187
[17:00] <hggdh> nigel_nb_: this is not an Ubuntu bug
[17:00] <hggdh> it is for Mint and Mithbuntu
[17:01] <nigel_nb_> do we support mythubuntu?
[17:01] <hggdh> so -- I guess -- ubiquity (ubuntu) is wrong
[17:01] <hggdh> bugsquad does not
[17:01] <hggdh> (support Mint or mithbuntu)
[17:01] <nigel_nb_> ah, so we change the package to what?
[17:01] <hggdh> good question ;-)
[17:02] <nigel_nb_> haha
[17:03] <hggdh> I really do not know, never dealt with them
[17:03] <nigel_nb_> wonder which package actually deals with reading data from partitions
[17:04] <hggdh> this would be, on UBuntu, an ubiquity bug
[17:04] <hggdh> for Mint, or Mith*, I am unsure
[17:04] <nigel_nb_> so we'll leave it at that
[17:04] <nigel_nb_> and change to invalid?
[17:05] <hggdh> it is not invalid, it is just not Ubuntu
[17:07] <hggdh> nigel_nb_: I am adding linuxmint as an affects
[17:08] <nigel_nb_> ok :)
[17:15] <nigel_nb_> does linux mint doesn't use launchpad for tracking, does it?
[17:16] <hggdh> as far as I knkow, yes, it does
[17:17] <nigel_nb_> ah, so our work is done for that one
[17:18] <hggdh> probably, yes
[17:18] <hggdh> SEP (Somebody else's problem)
[17:18] <nigel_nb_> ah :)
[17:22] <nigel_nb_> check out bug 493175, I think there is some trouble with the browser there
[17:23] <nigel_nb_> when you click connect and ubuntuone does not have your username/pass, it will open firefox, thats not happening for this user
[17:24] <hggdh> are there any updates to ubuntu-one-client?
[17:25] <nigel_nb_> oops, dont remember, checking
[17:35] <nigel_nb_> there was one update to ubuntu one
[17:35] <nigel_nb_> donno when
[17:36] <nigel_nb_> I'm having the ubuntu2 version
[17:37] <hggdh> we can ask the OR to upgrade to current (-proposed?) and try again
[17:38] <nigel_nb_> he's on the latest
[17:38] <hggdh> hold on
[17:38] <hggdh> yes
[17:38] <nigel_nb_> ubuntuone-client 1.0.2-0ubuntu2
[17:39] <hggdh> bad config somewhere?
[17:39] <nigel_nb_> to be honest, ubuntuone is kinda buggy
[17:39] <nigel_nb_> I dont see it on my taskbar now
[17:46] <nigel_nb_> hggdh: saw the log file?
[17:46] <nigel_nb_> a cycle of missing tokens
[17:46] <nigel_nb_> Can't get the auth token Traceback
[17:53] <hggdh> sounds like a bug indeed. Should, at least, gracefully fail
[17:54] <nigel_nb_> can't confirm coz I guess it happens before you've given your info
[17:54] <hggdh> yes, I agree. And I do not know how u1 works
[17:55] <nigel_nb_> anything we can do to trace this one?
[17:56] <hggdh> nigel_nb_: only looking at the source for u1
[17:57] <hggdh> since it is python, should not be difficult...
[17:58] <nigel_nb_> ah
[18:04] <hggdh> be back in a few. Trying Yet Another IRC Client
[18:18] <nigel_nb_> hggdh: how was the other client?
[18:20] <hggdh> weechat, now
[18:20] <hggdh> so far, so good
[18:28] <hggdh>      /alias rmsfilter filter del irc_smart_$server_$channel
[18:28] <hggdh>      /alias rmsfilter filter del irc_smart_$server_$channel
[19:25] <nigel_nb_> micahg: are you around?
[19:25] <micahg> yeah nigel_nb_
[19:26] <nigel_nb_> does firfox has some known trouble with javascript
[19:26] <micahg> nigel_nb_: bug #?
[19:26] <nigel_nb_> assisting a user, reports that there is some site that he can browse properly with IE (windows), but not FF (ubuntu)
[19:26] <micahg> nigel_nb_: javascript is a bug part of firefox
[19:27] <micahg> nigel_nb_: it's possible
[19:27] <micahg> have the user try a new profile to make sure it's not an addon
[19:27] <micahg> nigel_nb_: IE doesn't follow the standard for JS and has it's own stuff as well
[19:28] <nigel_nb_> so the site may as have been designed for IE
[19:39] <nigel_nb_> micahg: someting strange, the user runs  "firefox -ProfileManager" and the profile manager doesn't show up
[19:40] <hggdh_> WFM
[19:40] <micahg> nigel_nb_: what verison?
[19:41] <nigel_nb_> asking
[19:42] <nigel_nb_> 3.5.5
[19:43] <micahg> nigel_nb_: on jaunty or karmic?
[19:43] <nigel_nb_> karmic
[19:43] <micahg> nigel_nb_: so, what happens?
[19:44] <nigel_nb_> he types "firefox -ProfileManager" and a new FF window opens
[19:44] <nigel_nb_> no profile manager
[19:44] <yofel> why not just use -safe-mode to disable addons?
[19:44] <maco> nigel_nb_: i think you have to run the actual firefox
[19:44] <micahg> nigel_nb_: firefox has to be closed first
[19:45] <nigel_nb_> i checked that first
[19:45] <maco> like, there are 3 layers of symlinks to a script
[19:45] <maco> and then the script calls the binary
[19:45] <nigel_nb_> told him to close everything
[19:45] <maco> and i think you need to call the binary directly
[19:45] <micahg> maco: no
[19:45] <maco> micahg: no? i remember it being rather complicated...
[19:45] <micahg> nigel_nb_: have the user do "ps -ef | grep firefox"
[19:45] <micahg> maco: /usr/bin/firefox is meant to work
[19:46] <maco> micahg: ok
[19:46]  * micahg bets it's still running
[19:46]  * nigel_nb_ is with micahg on that one
[19:46] <nigel_nb_> maco: I thought u were busy today ;)
[19:47] <BUGabundo> nigel_nb_: are you sure there isn't already another FF running ?
[19:47] <micahg> yofel: safe-mode has everything disabled, but then you can't test adding stuff back
[19:47] <maco> nigel_nb_: just finishing up working on school project. as soon as my compile's done, i have to go cook to prepare for a potluck
[19:47] <nigel_nb_> bingo
[19:47] <BUGabundo> nigel_nb_: $ ps xauw | grep fox
[19:47] <yofel> micahg: good point
[19:47] <nigel_nb_> micahg: he's got one running silently
[19:47] <BUGabundo> eh
[19:48] <micahg> nigel_nb_: killall firefox
[19:49] <micahg> yofel: safe mode also can't help detect profile (sqlite) corruption
[19:49] <nigel_nb_> maco: oh okay :)
[19:49] <yofel> ah
[19:50] <nigel_nb_> wierd
[19:50] <nigel_nb_> he did a killall
[19:50] <nigel_nb_> still has a --color=auto firefox running
[19:51] <thekorn> that's the grep process
[19:51] <BUGabundo> lol
[19:51] <BUGabundo> hey thekorn
[19:52] <nigel_nb_> okay, my mistake
[19:52] <thekorn> hola BUGabundo
[19:52]  * nigel_nb_ smacks himself on the head for not seeing that one
[19:57] <nigel_nb_> micahg: nothing changes with new profile
[19:57] <nigel_nb_> so i guess it has something to do with the website
[20:00] <micahg> nigel_nb_: probably, you can have the user file a bug: ubuntu-bug firefox
[20:00] <micahg> nigel_nb_: does the website say anything about being made for IE
[20:00] <nigel_nb_> lemme try to read
[20:00] <nigel_nb_> turkish
[20:07] <hggdh_> at least you can identify the language ;-)
[20:08] <nigel_nb_> i just got lucky hggdh_
[20:08] <nigel_nb_> the website with the issue ended with .tr
[20:08] <hggdh_> ah
[20:14]  * hggdh_ is starting to like weechat (development version)
[20:16] <BUGabundo> hggdh_: link?
[20:17] <hggdh_> BUGabundo: http://www.weechat.org/ you will have to build the git version
[20:17] <BUGabundo> bah
[20:18] <hggdh_> we are still on 2.6, and there some more cool features on 3.0 and git
[20:18] <hggdh_> actually, 0.3.1.*
[20:36] <WeatherGod> dtchen, I have come across 4 bug reports today stating that their sound stopped after rebooting for system updates
[20:36] <dtchen> WeatherGod: well, there haven't been any alsa-lib updates or pulseaudio updates
[20:36] <dtchen> WeatherGod: so if it isn't a mixer element, it has to be linux
[20:37] <WeatherGod> kernel updates, maybe?
[20:37] <WeatherGod> two of the reports involved Realtec cards
[20:37] <WeatherGod> the other two are unknown
[20:37] <dtchen> they all need to make sure they have linux-backports-modules-alsa-$(uname -r) is installed
[20:38] <WeatherGod> ok, I will start with that for them
[20:38] <WeatherGod> also, one of them complained that the system beep has been replaced with a system sound
[20:38] <WeatherGod> that's not a bug, right?
[20:38] <dtchen> no
[20:39] <WeatherGod> I vaugely remembering something about system beeps getting disabled for some reason or another
[20:39] <dtchen> see libgnome.
[20:39] <WeatherGod> ok, will do
[20:39] <dtchen> 2.28.0-0ubuntu3 debian/libgnome2-common.gconf-defaults: Disable keyboard bell mode by ...
[20:41] <WeatherGod> ah
[20:44] <yofel> if we're already at system beeps, could someone take a look at bug 486154. I'm not sure what to do about it
[20:44] <yofel> https://bugs.edge.launchpad.net/ubuntu/+bug/486154
[20:47] <WeatherGod> I like that title
[20:49] <WeatherGod> yeah, that's a doozy
[20:49] <WeatherGod> can PA intercept a system beep?
[20:50] <dtchen> no, it can't.
[20:50] <WeatherGod> that's what I thought
[20:50] <dtchen> so there are two issues in that really meandering report
[20:51] <WeatherGod> lovely
[20:53] <dtchen> 1) we disable hda beep in the linux source
[20:53] <dtchen> 2) compiz doesn't do the right thing with x11 bell
[20:54] <dtchen> both are fairly trivial to test
[20:54] <dtchen> 1) revert the change in sound/pci/hda/hda_beep.c
[20:55] <dtchen> 2) use metacity, which uses libcanberra directly for system bell
[20:55] <dtchen> see also bug #301174
[20:56] <WeatherGod> why does metacity have anything to do with sound?
[20:56] <dtchen> you'll have a clearer idea why I refer to metacity after you read the report that I just mentioned
[20:56] <WeatherGod> !info metacity
[20:56] <ubot4> WeatherGod: metacity (source: metacity): A lightweight GTK2 based Window Manager. In component main, is optional. Version 1:2.28.0-0ubuntu1 (karmic), package size 260 kB, installed size 704 kB
[20:56] <dtchen> compiz does not use libcanberra completely
[20:57] <WeatherGod> ok, I had a different idea for what metacity was...
[20:57] <WeatherGod> maybe I am thinking of the beagle thingy...
[20:57] <dtchen> ok, maybe I wasn't being clear.
[20:57] <dtchen> you can hear system bell properly if you use metacity
[20:57] <BUGabundo> dtchen: do you have any reports of PA on laptops just working in one side of ear speakers, unlike builtin ones?
[20:58] <dtchen> you can't hear it properly if you use non-metacity in GNOME
[20:58] <dtchen> BUGabundo: yes, but I can't pull the bug report #s from the top of my skull
[20:58] <BUGabundo>  no prob
[20:58] <BUGabundo> just wondering
[20:58] <BUGabundo> I thought it was HW on my side
[20:58] <BUGabundo> but a friend he had a similar one
[20:59] <BUGabundo> ill look it up
[20:59] <BUGabundo> is it trivial to fix, or permanent dtchen?
[21:01] <dtchen> I haven't debugged it fully
[21:01] <dtchen> codec problem, controller problem, bios problem, hw problem
[21:02] <BUGabundo> :(
[21:02] <BUGabundo> can't find it in LP
[21:02] <dtchen> i.e., I have no idea whether it's trivial, because I don't have cycles (rather, I have higher priority bugs) to debug it
[21:02] <BUGabundo> will have to digg dipper
[21:03] <BUGabundo> dtchen: I'll see if I can find the bug, and when ever you got a tiny bit of free time
[21:03] <BUGabundo> ping me for logs and debug resulst
[21:03] <BUGabundo> maybe we can put this one aside pretty quickly
[21:04] <dtchen> BUGabundo: or, rather than ping-pong, just tell me the pastebin url
[21:04] <BUGabundo> once I find it :)
[21:04] <dtchen> I need an administrative assistant, heh
[21:04] <BUGabundo> haahah
[21:04] <BUGabundo> who doesn't, this days
[21:05] <dtchen> use memoserv as appropriate, please
[21:05] <BUGabundo> I need 12 clones of me, just to parse all my email
[21:06] <BUGabundo> dtchen: I was planning on spending 50€ on my xtmas gift buying a new headphones, but better keep them for now
[21:06] <BUGabundo> or donate part of it to you :)
[21:09] <dtchen> money won't help me :)
[21:09] <nigel_nb_> BUGabundo: unfortunately, we can transfer time
[21:09] <nigel_nb_> everyone gets only 24
[21:10] <BUGabundo> dtchen: oh well, more to me or other donations :)
[21:10] <BUGabundo> nigel_nb_: not really true... ever hear of time banks?
[21:10] <nigel_nb_> what are they?
[21:10] <BUGabundo> social groups of ppl that "lend"/"sell" their free time
[21:10] <BUGabundo> in exchange of others time
[21:11] <nigel_nb_> yeah, but to help dtchen you should be expert in sound
[21:11] <BUGabundo> ehehh
[21:11] <BUGabundo> and beyond
[21:11] <dtchen> or you could forcibly hold OEMs responsible for manufacturing crappy equipment.
[21:11] <BUGabundo> ahaha
[21:12] <WeatherGod> that would go a long way
[21:12] <BUGabundo> if I could, bet your arse I would
[21:12] <BUGabundo> but I'm just a little guys whose emails go unread
[21:12] <BUGabundo> my laptop was so bad assembled, I was removing dust and old cpu mass,
[21:12] <BUGabundo> and found a seal on the GPU
[21:13] <BUGabundo> 18 months *after* assembly
[21:13] <BUGabundo> no wonder my GPU was always at >70+
[21:13] <BUGabundo> *70º
[21:13] <kklimonda> at least you don't have to service your laptop every year due to faulty gpu ;)
[21:13] <WeatherGod> must be part of their "forced obscelescense" plan
[21:14] <BUGabundo> kklimonda: I was planing to send it back to swich GPU due to bad support of vdpau, and bad sectores in the disc
[21:14] <BUGabundo> but... my laptop felt into the ground and broke a corner of the chassi
[21:14] <BUGabundo> they won't touch it now
[21:14] <BUGabundo> :\
[21:15] <kklimonda> BUGabundo: bad support for vdpau is a matter of the faulty chip or technology?
[21:15] <BUGabundo> kklimonda: in my case according to nvidia foruns: bad lot
[21:15] <kklimonda> I couldn't use vdpau on my laptop when compiz was enabled and now I'm wondering whenever that was an early sign of gpu meltdown
[21:16] <BUGabundo> wait
[21:16] <kklimonda> gotta love nvidia for releasing whole bunch of broken chipsets into the wild.. now all I can think of is whenever I'll be able to break my nvidia again before warranty expires ;)
[21:17] <BUGabundo> is vdpau and compiz related?
[21:17] <kklimonda> BUGabundo: well - both are heavily using your gpu resources
[21:17] <BUGabundo> I would test vpau again
[21:17] <BUGabundo> but smplayer is broken in lucid
[21:18] <BUGabundo> don't know of anyother player that allows  me to set vdpau processing
[21:18] <kklimonda> you already using lucid?
[21:18] <BUGabundo> totem and vlc won't
[21:18] <BUGabundo> kklimonda: since day one
[21:18] <kklimonda> no rest for the wicked? ;)
[21:18] <BUGabundo> why do you still ask?
[21:18] <BUGabundo> I've been doing so since 6.10 beta
[21:18] <kklimonda> hyhy - I'm always suprised :)
[21:18] <BUGabundo> ee
[21:18] <BUGabundo> ehh
[21:19] <BUGabundo> now go help me find LP bug on single sided headfones bug
[21:19] <BUGabundo> darn search and google don't like me
[21:19] <kklimonda> BUGabundo: are there many lucid users? I'm considering asking desktop guys to get Transmission 1.80 beta1 uploaded so it gets as wide testing as possible
[21:19] <BUGabundo> all I find are USB related
[21:19] <BUGabundo> kklimonda: let me guess: DHT and magnetic links?
[21:20] <kklimonda> magnetic
[21:20] <BUGabundo> I read something on transmission foruns about all this mess
[21:20] <BUGabundo> from a dev, that I really didn't like
[21:20] <kklimonda> yeah, this feature is pretty big and pretty important for the LTS release
[21:20] <BUGabundo> he was STFUing an user who was just asking for support
[21:21] <kklimonda> BUGabundo: I wonder who this user was - there is a guy who is simply trolling on forums and irc ;)
[21:21] <BUGabundo> no idea
[21:21] <BUGabundo> brand new to the forums
[21:21] <kklimonda> and T developers aren't really kind of guys who go and STFU users
[21:21] <BUGabundo> it was just on the 1st or second page
[21:22] <kklimonda> I don't use forums ;)
[21:22] <BUGabundo> deuxpi: !?
[21:22] <BUGabundo> lol
[21:22] <deuxpi> ha ha
[21:22] <BUGabundo> deuxpi: well its not _my_ bug report
[21:22] <deuxpi> well let's see :)
[21:22] <BUGabundo> just want to see if it is the same bug I have
[21:22] <BUGabundo> so I can help dtchen triage it
[21:23] <deuxpi> I'm looking for it too
[21:23] <BUGabundo> it would be faster if nvidia/compiz wasn't corrupting my screen (
[21:23] <kklimonda> BUGabundo: have you tried nouveau?
[21:23] <BUGabundo> https://bugs.edge.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/493221
[21:24] <BUGabundo> kklimonda: won't install with PPA version of X 1.5
[21:24] <kklimonda> I was wondering lately whenever nouveau is getting to the point when it's usable
[21:24] <BUGabundo> I could try archive version dough
[21:24] <kklimonda> feature matrix looks promising
[21:25] <deuxpi> i see black boxes on my geode, but not this bad
[21:25] <BUGabundo> deuxpi: that screenshot was a "good" one
[21:25] <BUGabundo> I've got worse
[21:27] <deuxpi> bug #355375 has left/mono sound, but I don't think it's the bug
[21:27] <BUGabundo> No results for search single ear
[21:27] <BUGabundo> bah
[21:27] <BUGabundo> let me see
[21:27] <deuxpi> it's also in his speakers
[21:27] <BUGabundo> why aint the bot working ??
[21:28] <deuxpi> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/355375
[21:28] <kklimonda> BUGabundo: looks scary..
[21:28] <kklimonda> BUGabundo: that's why I'm not going to update to lucid yet ;)
[21:28] <kklimonda> BUGabundo: I see you are using chromium? :)
[21:28] <BUGabundo> it was fine up until 3 days agi
[21:28] <BUGabundo> yep
[21:29] <BUGabundo> and FF
[21:29] <BUGabundo> chromium is just faster and less UI
[21:29] <kklimonda> indeed
[21:29] <BUGabundo> FF is more feature enabled
[21:29] <kklimonda> but it uses more ram
[21:29] <kklimonda> it's still faster than Fx on my old laptop though..
[21:31] <BUGabundo> $ top | grep fox
[21:31] <BUGabundo> 12709 bugabund  20   0  579m 167m  30m S    0  4.2   0:55.66 firefox-3.7
[21:31] <BUGabundo> $ top | grep chrom
[21:31] <BUGabundo>  3674 bugabund  21   1  890m  76m  12m S    0  1.9   1:15.25 chromium-browse
[21:32] <kklimonda> BUGabundo: chromium-browser have much more processes than Fx
[21:32] <deuxpi> chromium seems to use less resident memory, shared mem usage due to webkit?
[21:33] <BUGabundo> NPROCS  SYSCPU  USRCPU  VSIZE  RSIZE  RDDSK WRDSK RNET SNET  CPU CMD     1/8
[21:33] <BUGabundo>      1   3m30s  10m51s 433.3M 90372K  41640   112    0    0   9% Xorg
[21:33] <BUGabundo>      1  96.75s   5m28s   1.0G 265.4M  60792 322e3    0    0   5% pidgin
[21:33] <BUGabundo>      6  27.52s   3m41s   3.4G 233.4M  168e3 509e3    0    0   3% chromium-brows
[21:33] <BUGabundo> .......
[21:33] <BUGabundo>      1   2.39s  53.82s 584.2M 171.8M  78320 11272    0    0   1% firefox-3.7
[21:33] <kklimonda> BUGabundo: interesting, is that htop?
[21:33] <BUGabundo> kklimonda: not that much CPU
[21:33] <BUGabundo> atop
[21:34] <BUGabundo> cpu stats
[21:34] <kklimonda> atop, htop, top.. heh..
[21:35] <BUGabundo> I love atop
[21:37] <kklimonda> how to sum up memory ussage of all processes with the same name?
[21:37] <BUGabundo> deuxpi: that doesnt make much sense
[21:37] <BUGabundo> there's not prob in audio being mono and still working in both speakers
[21:38] <BUGabundo> in the mean time, I'm playing a stereo file
[21:38] <BUGabundo> and paman says mono
[21:38] <BUGabundo> on the headphones output
[21:38] <BUGabundo> let me test on builtin speakers
[21:41] <BUGabundo> Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
[21:41] <BUGabundo> AUDIO: 22050 Hz, 1 ch, s16le, 16.0 kbit/4.54% (ratio: 2003->44100)
[21:41] <BUGabundo> Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
[21:41] <BUGabundo> bad example lol. movie was mono
[21:41] <BUGabundo> let me test another
[21:42] <BUGabundo> bah now I have a stereo and it won't play anything...
[21:47] <BUGabundo> kklimonda: [vdpau] Error when calling vdp_device_create_x11: 1
[21:47] <BUGabundo> Error opening/initializing the selected video_out (-vo) device.
[21:47] <BUGabundo> see what I mean ?
[21:47] <kklimonda> nah, my error was completely different
[21:48] <kklimonda> I was getting hundreds of lines with errors similar to out of memory etc.
[21:48] <BUGabundo> oh wait
[21:48] <BUGabundo> google has stuff for this
[21:49] <BUGabundo> "it works fine if I remove -vf-add screenshot from the command."
[21:49] <BUGabundo> lol
[21:54] <Jeruvy> anyone running karmic see the 'two volume icons on the panel' issue?
[21:59] <nigel_nb> under what package does a card reader issue gets filed under?
[21:59] <nigel_nb> hal?
[22:03] <WeatherGod> matters by the issue
[22:03] <WeatherGod> if the driver loads, it isn't udev
[22:03] <WeatherGod> I don't know what hal is still used for (might want to check the halsectomy page)
[22:04] <WeatherGod> if the card is not automounting, maybe it is devicekit?  maybe gnome-desktop?
[22:04] <kklimonda> I wonder whenever you could use ubuntu-bug storage to get a target package
[22:04] <WeatherGod> jeruvy, no, I have not seen such an issue
[22:05] <WeatherGod> might want to find  out which desktop manager they are using
[22:05] <dtchen> Jeruvy: upgrade from 9.04?
[22:05] <Jeruvy> dtchen: yep
[22:05] <dtchen> Jeruvy: yep, known issue. Find the bug in LP.
[22:05] <nigel_nb> WeatherGod: apport is kewl
[22:05] <Jeruvy> Well I did something really strange :)
[22:05] <nigel_nb> the user just ran ubuntu-bug and it asked her what the problem was, GUI :O
[22:06] <nigel_nb> so, the gui will take care of it.. it asked first for storage devices
[22:06] <Jeruvy> dtchen: One of the icons was obviously a valid volume control, the other didn't appear to.  So I removed it from the panel.  Now the panel and display constantly flickers.
[22:07] <Jeruvy> dtchen: I'm wondering how I can recover the desktop, or if I should try to reinstall gnome-desktop?
[22:07] <WeatherGod> nigel_nb, so, in other words, apport made a guess as to the problem?
[22:07] <nigel_nb> not really
[22:07] <nigel_nb> well, the gui who programmed the gui made a guess
[22:08] <nigel_nb> you have doubt as to the package when u're talking about storage devices
[22:08] <dtchen> Jeruvy: ~/.gconf*
[22:08] <nigel_nb> WeatherGod: if you dont select a package, it will assume its external device
[22:08] <nigel_nb> WeatherGod: or else give a package
[22:08] <WeatherGod> ah... ok
[22:08] <WeatherGod> I was completely missing your point there
[22:08] <Jeruvy> dtchen: just delete it?
[22:09] <dtchen> Jeruvy: mv it, log out and back in
[22:09] <dtchen> Jeruvy: you'll need to reconfigure stuff, I presume
[22:09] <WeatherGod> yeah, that is funny that it assumed a storage device problem
[22:09] <Jeruvy> dtchen: I can try that.  thanks.
[22:10] <nigel_nb> WeatherGod: I know, I didn't believe until I tried it on my own
[22:10] <nigel_nb> WeatherGod: I guess this is the OSS versus closed source difference
[22:10] <WeatherGod> how so?
[22:11] <nigel_nb> here the developer is writing the code, also using the code, and solving issues, so he has an idea what is going to go bust ;)
[22:11] <WeatherGod> ah, I see
[22:12] <WeatherGod> meanwhile, those who do closed source don't really know the weaknesses of other programs
[22:12] <nigel_nb> exactly
[22:12] <nigel_nb> they just care about their module (s)
[22:12] <nigel_nb> when the developer is also the user, there is a whole lot of difference
[22:14] <WeatherGod> well, even for closed source software, the developer can also be the original user
[22:15] <nigel_nb> can
[22:15] <nigel_nb> but slim chances
[22:16] <nigel_nb> take a look at bug 493250
[22:17] <nigel_nb> that request while sounds good, has a couple of problems before I ask someone to wishlist
[22:17] <WeatherGod> you know, I misread that title to be something totally inappropriate at first
[22:19] <WeatherGod> well, maybe it just requires making sure that the word "dictionary" is in the summary or something
[22:19] <WeatherGod> not exactly sure how Software Center does its searches
[22:19] <WeatherGod> I wonder if it shows up in Synaptics
[22:20] <nigel_nb> WeatherGod: I'll explain what I understood from that
[22:21] <nigel_nb> the thing is in software center, if u search for "Dict"
[22:21] <nigel_nb> it will search for all matches where dict is the *first four letters*
[22:21] <nigel_nb> so, if the word is in between, like this entry, software center will miss it
[22:22] <Jeruvy> dtchen: thanks that got rid of the flickering.  Is there anything I should review for consideration to the bug?
[22:22] <WeatherGod> nigel_nb, the Software Center has the world's dumbest search engine
[22:22] <nigel_nb> I know
[22:22] <nigel_nb> I checked synaptics
[22:23] <nigel_nb> it checks for the searched phrase in the full name, anywhere
[22:23] <nigel_nb> so, I wanted to know if its worthy enough
[22:23] <WeatherGod> this could then be retooled into a wishlist item for improved search
[22:23] <dtchen> Jeruvy: gconf, perhaps. Don't know, sorry. I'm kinda busy.
[22:23] <nigel_nb> yep, thats what I thought, I just wanted to hear your opinion
[22:24] <Jeruvy> dtchen: thats cool, I'll keep looking around and save it just in case.  Thanks again.
[22:24] <nigel_nb> only thing is I need to change the description appropriately
[22:24] <WeatherGod> Jeruvy, I would just mark your bug as a duplicate
[22:24] <WeatherGod> nigel_nb, yeah
[22:24] <nigel_nb> lemme get to work on it then :)
[22:25] <WeatherGod> ok, I gotta cook dinner
[22:25] <Jeruvy> WeatherGod: I didn't add or confirm the original bug at this point.  I was going to confirm it
[22:30] <nigel_nb> hggdh_: are you around?
[22:35] <nigel_nb> can someone wishlist bug 493250 for me please
[23:13] <nigel_nb> WeatherGod: back?
[23:13] <WeatherGod> yuppers...
[23:14] <WeatherGod> had a nasty freeze, though
[23:14] <WeatherGod> can't figure it out
[23:14] <WeatherGod> nothing responded at all