[00:18] <komputes> bdmurray: you may want to edit "("Visibility/security" in the top left pink box)" from https://wiki.ubuntu.com/Bugs/HowToTriage as the "private bug" indicator/container is no longer pink.
[00:23] <bdmurray> komputes: feel free to make the change if you are so inclined
[00:23] <komputes> bdmurray: no prob, just wanted to check with you
[00:39] <bcurtiswx> whats the ubuntu spell checker?
[00:40] <mrooney|w> bcurtiswx: I think there are multiple that different applications use
[00:41] <mrooney|w> aspell is the most popular, perhaps?
[00:41] <bcurtiswx> hmm, how do i find out which empathy uses?
[00:41] <bcurtiswx> bug #411172
[00:41] <ubot4> Launchpad bug 411172 in empathy "empathy doesn't allow the ability to ignore certain "words"" [Undecided,New] https://launchpad.net/bugs/411172
[00:41] <mrooney|w> if it is packaged properly, depends or recommends I imagine
[00:43] <bcurtiswx> mrooney|w: thx
[00:43] <mrooney|w> were you able to figure out which one it uses?
[00:44] <bcurtiswx> nothing in depends or recommends.. im asking in #telepathy
[00:47] <mrooney|w> bcurtiswx: of note is the depend on libenchant1c2a
[00:47] <micahg1> libhunspell-1.2-0 :)
[00:47] <bcurtiswx> ah ha, i am blind
[00:48] <bcurtiswx> i looked through the thing and stupidly forgot to use the find feature
[00:49] <bcurtiswx> so in the case of the bug i mentioned earlier
[00:49] <bcurtiswx> is it an empathy wishlist or libhunspell wishlist/bug ?
[00:50] <bcurtiswx> thats why ive been asking these questions
[00:50] <micahg> libhunspell if that's where the dictionary is
[00:51] <micahg> nah
[00:51] <micahg> that's an empathy bug
[00:51] <micahg> libhunspell probably just provides the dictionary
[00:51] <micahg> bug is to ignore, right?
[00:51] <bcurtiswx> yeah
[00:51] <micahg> so I would think that's in implementation
[00:52] <bcurtiswx> ok, i wasn't sure if libhunspell should already allow ignoring of words
[00:52] <micahg> idk
[00:52] <bcurtiswx> best to keep it with the empathy folks then eh?
[00:53] <micahg> hmm
[00:53] <micahg> library already supports it
[00:53] <micahg> so I'd say an implementation problem
[00:53] <bcurtiswx> okee, where did u find out it supports it?
[00:53] <micahg> but if it's wrong, they'll move it
[00:53] <micahg>  apt-cache show libhunspell-1.2-0
[00:54] <micahg> supports forbidden words list
[00:54] <bcurtiswx> ah, ok thx
[01:01] <bcurtiswx> ok another question... so i know theres no way empathy devs are going to change something... its a wishlist item ... should I mark as wishlist or can i go ahead and mark as wontfix?
[01:02] <bcurtiswx> smarter to go to the devs and get their actual Ok on marking it wontfix
[01:02] <bcurtiswx> ?
[01:03] <micahg> bcurtiswx: unless you know it's wontfix, you can leave as wishlist
[01:03] <micahg> why wouldn't empathy devs change anything?
[01:03] <bcurtiswx> well its nothing yet
[01:03] <bcurtiswx> lol
[01:03] <bcurtiswx> its a wishlist to change the icons for the buddy list
[01:03] <bcurtiswx> to pidgins
[01:04] <micahg> maybe if it was reworded as an icon pack or something
[01:04] <micahg> some apps let you add your own icons
[01:04] <micahg> that would seem more reasonable
[01:07] <LimCore> Any chance Ubuntu could support sound again, on my box?
[01:08] <bcurtiswx> Ubuntu tries to stay the same as upstream as possible.. correct?
[01:08] <LimCore> about, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/418644
[01:08] <ubot4> Launchpad bug 418644 in pulseaudio "Ubuntu 9.04 amd64 ALSA and Pulse stoped working after upgrade " [Undecided,New]
[01:09] <micahg> bcurtiswx: if possible, it depends on what
[01:09] <bcurtiswx> because the telepathy folks say wontfix but that ubuntu can change the icon set if they desire... and i don't think Ubuntu would, but idk
[01:10] <micahg> well, unless ubuntu has a reason to change, probably not
[01:10] <micahg> although
[01:10] <micahg> you might want to check with the package developers
[01:12] <lifeless> bcurtiswx: we don't make spurious changes.
[01:13] <lifeless> bcurtiswx: but we will change a package to improve it or fix bugs; and try to get the changes integrated upstream.
[01:13] <lifeless> for some changes, like theming ones, upstream may not want them, but we may still need them.
[01:13] <bcurtiswx> but it seems its a need = in watnt = wontfix
[01:13] <bcurtiswx> s/watnt/want
[01:14] <lifeless> wontfix is for things that we /won't do/
[01:14] <lifeless> wishlist is for things that a volunteer can do
[01:14] <bcurtiswx> in my case its a request for icon change in empathy that the icons are "too ugly"
[01:14] <bcurtiswx> the icons for away and busy and available
[01:14] <LimCore> I updated the bug, with debug output, please see
[01:15] <bcurtiswx> which bug? i dont see this change
[01:15] <lifeless> well, the icons should be coming from some desktop them yeah? so if you change desktop theme they change?
[01:16] <lifeless> if they don't change with the theme, then I'd split it into two bugs: 1) that empathy hard codes rather than using the theme; 2) that <theme X is ugly>
[01:16] <LimCore> bcurtiswx: I was refeing to my pulse audio bug, linked above
[01:17] <bcurtiswx> LimCore: type alsamixer in terminal
[01:17] <bcurtiswx> make sure nothing it muted
[01:17] <bcurtiswx> is*
[01:17] <bcurtiswx> or at no volume
[01:17] <LimCore> it is quietly farting
[01:17] <LimCore> and OSS is working 100% fine
[01:17] <LimCore> so it seems mixers are ok
[01:18] <LimCore> not playing quietly, but making distorted random noises
[01:18] <LimCore> omg
[01:18] <LimCore> it works :o PCM was muted.
[01:18] <bcurtiswx> :-)
[01:18]  * LimCore fells stupid
[01:18] <bcurtiswx> you are welcome
[01:18] <LimCore> althogh this still ARE bugs
[01:18] <LimCore> 1. wtf why pcm reset to 0 on update
[01:18] <bcurtiswx> karmic fixes a ton
[01:19] <bcurtiswx> idk, pulse has a mind of its own
[01:19] <LimCore> 2. why 0 sound makes farts instead silence
[01:19] <hggdh> LimCore, then you might want to be at the "triaging sound bugs" this Friday
[01:19] <LimCore> here?
[01:19] <hggdh> on #ubuntu-classroom, at 22:00 UTC
[01:19] <bcurtiswx> ET = 6:00PM i think
[01:20] <LimCore> ow but I have to change plans
[01:20] <hggdh> correct, bcurtiswx
[01:20]  * LimCore calls the pimp and rescheduels
[01:20]  * LimCore calls Willson and Amber too
[01:20] <bcurtiswx> friday, 6:00PM
[01:20] <bcurtiswx> i can be mod if you still don't have anyone
[01:20] <hggdh> more correctly, Friday, 6:00 PM EDT
[01:20] <hggdh> (or 22:00 Z)
[01:20] <bcurtiswx> zulu woooo
[01:21] <hggdh> heh. Easier than writing UTC
[01:21] <LimCore> UTC is this universal time riht?
[01:21] <hggdh> yes
[01:21] <bcurtiswx> yup
[01:22] <LimCore> btw,
[01:22] <LimCore> pulse audio is so epically broken
[01:22] <LimCore> one of main reasons why ubuntu is NOT multi user desktop
[01:22] <bcurtiswx> would it hurt LimCore to try the karmic pulses?
[01:22] <LimCore> bcurtiswx: no
[01:22] <hggdh> yes, this is why it is so important to get triage correct for sound
[01:23] <LimCore> switch VTs few times --> constant farting or just no sound
[01:23] <LimCore> if you are lucky, the sound will work, instead the GFX will die lol
[01:23] <bcurtiswx> lol
[01:23] <bcurtiswx> i just bought two usb audio/video devices
[01:23] <bcurtiswx> getting pulse to work with them has been a pain.. so i do know where you are coming from
[01:23] <LimCore> which I am unable to report because kmail dumps some bullshit to log files
[01:24] <bcurtiswx> hggdh: so in case you didn't get this before
[01:24] <LimCore> Oh this option dumps tons of useless KIO debug level stuff to log, why yes! lets turn it on
[01:24] <bcurtiswx> hggdh: if you still need someone, i can mod Friday 6:00PM EDT
[01:25] <hggdh> bcurtiswx, thank you. You have just been opted in ;-)
[01:25] <bcurtiswx> ;-)
[01:25] <bcurtiswx> #ubuntu-classroom and #ubuntu-classroom-discussion   right?
[01:26] <hggdh> or -questions, let me check
[01:27] <hggdh> bcurtiswx, seems to be #ubuntu-classroom-chat
[01:27] <LimCore> there should be a Dr.Linux program
[01:28] <LimCore> it would check for all this common stuff,  check if mixers are on, if there is hd space,  and common pitfalls like that
[01:30] <bcurtiswx> hggdh: is there some bot im suppose to use.. or wiki page im supposed to read up on?
[01:33] <mrooney|w> LimCore: isn't that sort of what hwtest is?
[01:57] <hggdh> bcurtiswx, https://wiki.ubuntu.com/Classroom
[01:58] <hggdh> (and companions)
[01:58] <LimCore> mrooney|w: I ment a gui program with hints etc, user friendly and all
[01:58] <LimCore> bbl
[02:03] <bcurtiswx> hggdh: i don't think the room is ever modded
[02:06] <bcurtiswx> hggdh: hopefully they know im mod and can voice me
[02:06] <bcurtiswx> lol
[02:11] <hggdh> we will tell them about you (and Dan) so there will be no problem. But, yes, modding is an option
[02:11] <bcurtiswx> i doubt it will be needed
[02:11] <hggdh> I wish I could be there... pity I will miss it
[02:11] <bcurtiswx> are there logs?
[02:13] <hggdh> yes, the channel is continuously logged. We will, after the class, prepare the logs into the wiki
[02:15] <bcurtiswx> good deal
[02:35] <hggdh> bcurtiswx, PVT?
[02:35] <bcurtiswx> PVT?
[02:36] <hggdh> private
[02:36] <bcurtiswx> oh , sure
[03:13] <komputes> how many of you use bughelper?
[03:21] <komputes> bdmurray: https://wiki.ubuntu.com/Bugs/BestPractices shows an error: Include: Nothing found for "^= Bug Reporting ="!
[06:12] <dholbach> good morning
[06:23] <MTeck> dholbach: good morning
[06:23] <dholbach> hey MTeck
[06:23] <MTeck> how's it going?
[06:27] <dholbach> good good - how 'bout you?
[06:36] <ejat> morning dholbach :)
[06:36] <dholbach> hi ejat
[06:45] <MTeck> dholbach: doing good except for that complaint - and that I had a fire extinguisher blow up in my car
[06:46] <dholbach> ugh
[07:26] <thekorn> good morning bugsquad
[10:05] <mac_v> Anyone around? i'v got a nautilus issue ,i think is related to my bug where thumbnails dont refresh, when i tried to reboot i'v got a message saying some programs are still running , and shows a huge list of nautilus events [copy,move,delete] these events where completed a long time ago , now my question is how do i catch whats goign on?
[10:22] <gnomefreak> is it just me or is "rm" broken?
[10:23] <Ueland> que?
[10:24] <gnomefreak> i think its working now a little while ago rm filename was giving me a > sign
[10:43] <Hobbsee> did you accidently add a '?
[10:43] <Hobbsee> that usually means it's asking you to end your quote
[11:13] <gnomefreak> checking
[11:15] <gnomefreak> yep
[11:19] <Hobbsee> that'd be the problem, then
[11:19] <gnomefreak> Hobbsee: thanks
[11:19] <Hobbsee> gnomefreak: y/w
[14:26] <AnAnt> Hello, could someone look at LP 418477 ?
[14:26] <ubot4> Launchpad bug 418477 in linux "New kernel causes losetup to hog the system" [Undecided,New] https://launchpad.net/bugs/418477
[14:27] <AnAnt> can anyone confirm this issue ?
[14:32] <hggdh> pedro_, ping
[14:33] <pedro_> hggdh, hey!
[16:09] <mac_v> pedro_: hi... https://bugs.launchpad.net/bugs/388418 ,  i think this bug can be closed
[16:09] <ubot4> Launchpad bug 388418 in nautilus "Smaller icons on the desktop compared to the Nautilus window" [Undecided,Incomplete]
[16:13] <pedro_> mac_v, hello, yeap, closing it now, thanks!
[16:13] <mac_v> thank you :)
[16:20] <azimout> question: what do we do about bugs against software that's no longer included in the latest Ubuntu version? I'm asking because I'm looking at 35 scrollkeeper bugs, and scrollkeeper is replaced by rarian-compat in Karmic
[16:24] <dholbach> azimout: I guess we have scrollkeeper in releases that are still supported
[16:24] <dholbach> still in dapper, hardy, intrepid, jaunty
[16:24] <dholbach> so will be around for a bit longer
[16:25] <dholbach> https://launchpad.net/ubuntu/+source/scrollkeeper
[16:26] <dholbach> same in Debian: http://packages.debian.org/search?searchon=sourcenames&keywords=scrollkeeper
[16:28] <azimout> ok, so I just ask people to confirm on jaunty then? I mean, is anyone going to issue updates (excluding security or SRU) against it? or are we just going to confirm (or close) bugs and then wait until support expires?
[16:28] <matti> :)
[16:30] <dholbach> azimout: upstream is very very very inactive, so I doubt there's going to be further improvements in scrollkeeper
[16:31] <dholbach> azimout: and there's just going to be SRUs or security fixes if at all
[16:31] <dholbach> but the upstream version we have is "well-tested" we had the same version (minus some Debian/Ubuntu fixes) in warty already :)
[16:31] <dholbach> so I'd just wait for it to not be in any supported ubuntu releases, then close the bugs
[16:32] <dholbach> which will be in April 2013 :-)
[16:32] <dholbach> LTSes can be annoying, hm?
[16:32] <hggdh> you may also warn the reporters that there is a low chance of the bugs being fixed, since the upstream project seems orphaned
[16:33] <azimout> I understand. But isn't that wasted triaging work?
[16:33] <hggdh> No. It *is* triaging work still.
[16:33] <hggdh> the reporters deserve a position, anyway.
[16:34] <hggdh> and -- who knows? -- upstream may pick up again
[16:35] <josephpiche> I was wondering if could have someone look at ubuntu bug 396632. I filed it because I feel like I should be able to run `service lighttpd status` as an unprivileged user since I can run `service mysql status` unprivileged, but I'm not familiar enough with init scripts to know what to modify in order to write a patch.
[16:35] <ubot4> Ubuntu bug 396632 in lighttpd "lighttpd init file should not chown or chmod on status check" [Undecided,Incomplete] https://launchpad.net/bugs/396632
[16:35] <hggdh> but this raises a question: should we have a tag for dropped packages?
[16:35] <dholbach> hggdh: I'd probably just mass-close them all once the package is in no supported distro anymore
[16:36] <hggdh> dholbach, yes, that was I was thinking. It's just that the tag would help find them all
[16:36] <micahg> I thought we mark won't fix anything that's not an SRU or security bug?
[16:37] <hggdh> hum
[16:37] <hggdh> We should clear it out, just to be sure, but it certainly sounds like a sane move, micahg
[16:38] <hggdh> like: if it is not SRU-worthy, and not a security issue, then close dropped packages wontfix
[16:38] <micahg> hggdh: I thought you did that for a certain gnome component that was orphaned
[16:39] <hggdh> yes. But I did it *only* for it.
[16:39] <hggdh> after discussing the issue
[16:41] <bdmurray> It'd also be good to update the package bug filing guidelines for removed packages to say don't file anymore.
[16:41] <hggdh> yes, thank you
[16:42] <micahg> bdmurray: how is a user supposed to know if something is an SRU or security issue?
[16:42] <bdmurray> micahg: do you mean the reporter?
[16:42]  * micahg would rather see the triaging guildelines updated
[16:42] <micahg> bdmurray: yes
[16:42] <hggdh> the user does not, always. The triager must find it out (and would be done if it *was* marked as such)
[16:43] <hggdh> and the reporter can always question, and re-open
[16:43] <micahg> one can see in the sidebar for bugs if the package has a version in the latest release
[16:43] <hggdh> bdmurray, is there a list of dropped packages somewhere?
[16:44] <bdmurray> hggdh: no, but it should be determinable.  I could prepare a list if someone wants to use it.
[16:44] <micahg> althought ones that totally no longer exist in supported versions like mozilla-firefox and firefox would make sense to warn not to submit a bug  to
[16:45] <hggdh> or redirect to the correct packages
[16:45] <micahg> well, that's not always easy, althought I would say firefox is the exception in that case
[16:46] <micahg> most packages do normally have something that replaces it
[16:46] <hggdh> bdmurray, that might be good. I was thinking of setting up something like that as a reference, like "package name -> last version supported"
[16:47] <bdmurray> hggdh: something like what?  I'm not following
[16:49] <micahg> could someone tell me if this implies something to try or something to do? http://pastebin.ubuntu.com/259900/
[16:49]  * micahg keeps getting users saying command doesn't help
[16:50] <bdmurray> Maybe put an extra carriage return in there before the command
[16:52] <bdmurray> and put 'of the following command run in a terminal' ?
[16:53] <micahg> bdmurray: what do you think about LP not allowing crash reports to be public until they are retraced at least once?
[16:54] <micahg> bdmurray: ty for the feedback
[16:54] <hggdh> bdmurray, well. In fact, one can look at packages.ubuntu.com for find out what packages have been dropped
[16:54] <bdmurray> micahg: do you mean people have been making bugs public before they have been retraced?
[16:54] <hggdh> but, perhaps more effective, would be a list of packages dropped on each release
[16:55] <micahg> correct
[16:55] <bdmurray> hggdh: I wrote some similar code using the api a bit a go
[16:55] <hggdh> bdmurray, care to share it? I might be able to adjust to what I am thinking of
[16:55] <bdmurray> hggdh: sure, let me fix it though the api seems to have changed on me
[16:55] <hggdh> BTW -- my lp_karma_suffix is getting hit by security errors
[16:56] <micahg> bdmurray: should I file a report?
[16:56] <micahg> actually, who would it be against?
[16:56] <micahg> or rather what?
[16:56] <hggdh> malone, I guess
[16:56] <bdmurray> micahg: that sounds reasonable but putting crash reports in launchpad is kind of hack as it is and isn't use by other projects
[16:57] <micahg> right
[16:57] <micahg> that's why I'm wondering where it goes
[16:57] <micahg> or even how to suggest it
[16:57] <bdmurray> well, it seems unlikely to be fixed via code rather triagers should be educated
[16:57] <micahg> ok
[17:00] <bdmurray> hggdh: http://pastebin.osuosl.org/28415 <- that is the output of the script, I wrote it before the dapper desktop EOL hence the dapper information
[17:00] <bdmurray> iirc the vast majority of packages had 0 bug reports but it'd be good to double check of course!
[17:07] <azimout> ok, thank you all for the answers, bye
[17:16] <josephpiche> I was wondering if could have someone look at ubuntu bug 396632. I filed it because I feel like I should be able to run `service lighttpd status` as an unprivileged user since I can run `service mysql status` unprivileged, but I'm not familiar enough with init scripts to know what to do
[17:16] <ubot4> Ubuntu bug 396632 in lighttpd "lighttpd init file should not chown or chmod on status check" [Undecided,Incomplete] https://launchpad.net/bugs/396632
[17:42] <bdmurray> josephpiche: I'd check with the searver team about that
[17:42] <josephpiche> bdmurray: okay, thanks
[18:02] <thekorn> bdmurray, can we have a quick chat about bughelper/py-lp-bugs after the meeting?
[18:04] <bdmurray> thekorn: sounds good!
[18:59] <eltoozero> Hi there people, where would I go to report a kernel bug in Karmic?
[19:01] <eltoozero> My machine does not fully halt at shutdown since 2.6.31-7-generic, but it worked fine in 2.6.31-5-generic, just want to properly report it.
[19:02] <thekorn> bdmurray, I've seen some discussions here in this channel about bughelper last week, so I think we should decide how to go on with bughelper and py-lp-bugs
[19:02] <greg-g> eltoozero: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug will do it for you.
[19:03] <thekorn> bdmurray, the biggest problem is py-lp-bugs, and the fact that it is not  easy to teach bughelper to use launchpadlib instead of py-lp-bugs
[19:03] <greg-g> eltoozero: actually, can you open up a terminal and type "ubuntu-bug linux" ?
[19:03] <eltoozero> ok, it's against "linux", just wasn't sure if there was a more specific place, thank you greg-g
[19:03] <greg-g> That will report it just the same, but additionly attach some debugging info
[19:03] <eltoozero> love the ubuntu-bug on the cli, very very cool.
[19:03] <greg-g> eltoozero: no problem, thanks for helping
[19:03] <bdmurray> thekorn: right, I think a good thing would be determining what is useful about bughelper
[19:04]  * greg-g still hasn't gotten used to recommending ubuntu-bug to people
[19:05] <thekorn> bdmurray, I think it bugnumbers to get list of tasks in multible output formats and the ability to use cluefiles with bughelper
[19:05] <eltoozero> This is my first time contributing heavily to the project, just want to follow standards.
[19:05] <thekorn> bdmurray, and it should not be hard to also support apport's bugpatterns
[19:05] <bdmurray> Yes, I'd agree there
[19:06] <eltoozero> what information will be most helpful in the summary for a kernel bug regarding halting at shutdown?
[19:06] <eltoozero> my chipset?
[19:06] <bdmurray> I recently added a script to bug patterns for checking a package's bug lists
[19:06] <thekorn> bdmurray, maybe the best (and easiest) solution would be to rewrite bughelper with focus on this points
[19:06] <eltoozero> "does not halt on shutdown"
[19:06] <greg-g> eltoozero: chipset should be automatically included when you use the ubuntu-bug CLI tool (I believe)
[19:06] <thekorn> bdmurray, jup I just found out about this script
[19:07] <greg-g> eltoozero: I would just give as best a description of the problem as possible (known goods, known bads) and use the ubuntu-bug tool, if more info is needed, we'll ask for it :)
[19:07] <eltoozero> greg-g: cool, is it prudent to mention the version of the kernel in the summary? "2.6.31-7-generic"
[19:08] <eltoozero> at least the -7 which is where the problem started vs -5
[19:08] <thekorn> bdmurray, my first reaction was "hey, this bugpatterns makes cluefiles totally useless" but the problem is bugpatterns can only be run against bugreports created with apport
[19:08] <greg-g> eltoozero: that'd be fine, something like "does not half on shutdown starting with 2.6.31-7"
[19:08] <bdmurray> thekorn: thinking about it the utility of clues compared to patterns is that they can be more vague and provide some guidance right?  oh that too
[19:08] <eltoozero> greg-g: that's where I was going, thank you.
[19:09] <thekorn> bdmurray, right
[19:09] <greg-g> eltoozero: yep, you've got the idea! :)
[19:09] <eltoozero> greg-g: here's another one, a very similar bug but very old, obviously not a part of karmic testing, should I add to that bug or create a new one?
[19:09] <bdmurray> eltoozero: with this specific system so it doesn't attract unrelated hardware comments
[19:10] <bdmurray> this bug is likely hardware specific
[19:10] <eltoozero> bdmurray: agreed.
[19:10] <bdmurray> thekorn: so this sounds like a good plan to me
[19:14] <eltoozero> bdmurray, can you clarify?
[19:15] <bdmurray> the ability to poweroff at shutdown can be dependant on your hardware
[19:16] <eltoozero> bdmurray, yes, should I specify in the summary or the full description
[19:16] <bdmurray> ideally both
[19:16] <eltoozero> ok good, and should I attach it to an older, similar bug that was on an old kernel version?
[19:23] <thekorn> bdmurray, ok, good, so when I find some spare time over the next week I will start rewriting bughelper focusing on this three capabilities
[19:27] <bdmurray> eltoozero: only if it is the exact same hardware
[19:29] <eltoozero> bdmurray, perfect, thank you.  I reviewed that bug and included the same debug information that was asked (if you're Brian Murray you were chasing it down before it was abandoned).
[19:53] <hggdh> micahg, ping
[19:53] <micahg> hggdh: pong
[19:53] <hggdh> micahg, why would a javascript http call return status==0 instead of (say) 200?
[19:54] <micahg> bug?
[19:54] <hggdh> no, it's the "follow bug trail" thing I am writing under greasemonkey for us
[19:54] <micahg> bug
[19:54] <micahg> bug 394192
[19:54] <hggdh> ah
[19:54] <ubot4> Launchpad bug 394192 in elisa "cpommened" [Undecided,Incomplete] https://launchpad.net/bugs/394192
[19:54] <micahg> bug 394912
[19:54] <ubot4> Launchpad bug 394912 in launchpad-gm-scripts "XMLHTTPRequest Randomly Fails with Status Code 0 During Reload/Refresh and/or Multiple Requests  " [High,Triaged] https://launchpad.net/bugs/394912
[19:55] <hggdh> brb, VP meeting now
[19:58] <thekorn> bdmurray, I just tried "search-bugs" form the bugpattern branch, there is an "import tempfile" missing: http://paste.ubuntu.com/260000/
[20:04] <bdmurray> thekorn: fixed, thanks
[21:00] <hggdh> micahg, thank you for the link to the bug
[21:04] <micahg> np, I'm trying to push it through upstream
[21:04] <micahg> if I can get someone to show me in the code where the bug is, I'll try to fix it
[21:12] <hggdh> heh
[21:12] <hggdh> go for it, but I understand FF code is a maze...
[21:12] <hggdh> perhaps asac will know
[21:12] <micahg> exactly, that's why I need someone to shwo me where
[21:13]  * micahg is poking around the developer channel on mozilla IRC
[21:58] <BUGabundo> ola
[22:25] <BUGabundo> hggdh: YoBoY: http://p.bugabundo.net/os-alunos-e-o-portugues
[23:20] <jwilliams> Hi all. I've encountered a strange bug and Google is not helping.  The update-manager shows n updates available, but Synaptic shows no updates available.  When I click to install the updates in update-manager they do not get installed, and they still show in the list after I reload.   Has anyone else encountered this?
[23:23] <BUGabundo> jwilliams: what version of ubuntu?
[23:23] <BUGabundo> open a terminal and type:
[23:23] <jwilliams> BUGabundo: Hi, thanks for your reply.  Jaunty (i386)
[23:23] <BUGabundo> sudo aptitude update ; sudo aptitude safe upgrade
[23:23] <BUGabundo> sudo aptitude update ; sudo aptitude safe-upgrade
[23:24] <BUGabundo> and pastebin any errors
[23:24] <jwilliams> Righto ...
[23:25] <jwilliams>  sudo aptitude safe-upgrade is showing the files that update-manager lists (but Synaptic does not)  Installing them now ...
[23:26] <BUGabundo> don't force anything dangeroues
[23:28] <jwilliams> Heh.  The operation completed with no errors
[23:28] <BUGabundo> great
[23:28] <BUGabundo> are you sure you where looking in the right place?
[23:28] <BUGabundo> maybe the bottom left tabs
[23:29] <BUGabundo> where on the wrong one?
[23:30] <jwilliams> BUGabundo: I think so, but I will be more careful next time.  When I click on "Install" I get a gksu prompt and it appears to work (i.e. does not show an error) but then just re-loads the package lists.
[23:31] <BUGabundo> strange
[23:31] <jwilliams> I'll say!
[23:32] <BUGabundo> if it happens again
[23:32] <BUGabundo> take a few screenshots
[23:33] <jwilliams> BUGabundo: Thanks for your help :-)