[00:15] <bcurtiswx> bdmurray: does greasemonkey automatically keep the LP scripts up-to-date with bzr?
[00:17] <bdmurray> bcurtiswx: no, the scripts themselves are not kept up-to-date
[00:18] <nhandler> bcurtiswx: I think there is a greasemonkey script or FF extension that can do that
[00:18] <bcurtiswx> bdmurray: ok thx
[00:18] <bcurtiswx> nhandler: oh really? do you know what its called? (i can search, just trying to epitomize laziness here)
[00:20] <nhandler> bcurtiswx: No, sorry. I just remember having installed a script that did that at one point or another.
[00:21] <bcurtiswx> nhandler: thx for the info !
[00:32] <bcurtiswx> bdmurray: http://userscripts.org/scripts/show/38017 looks like someone worked on something that makes the scripts check to see if they're updated.. i think its something you insert into your code though.  Maybe you want to check it out
[00:33] <bdmurray> bcurtiswx: maybe next week ;-)
[00:33] <bcurtiswx> bdmurray: very understandable.  would an e-mail be a better "reminder"?
[00:33] <bdmurray> bcurtiswx: that would rock
[00:36] <bcurtiswx> bdmurray: sent, good luck with 9.04 finalization stuff
[01:40] <Pretto> hey folks, can anyone help me to report a bug in jaunty?
[01:41] <Pretto> i don't know how to report it correctly, i just know the symptom
[01:42] <Pretto> the problem is that all video player closes when i have "Virtual	2560 800"  in Xorg's display section
[06:52] <dholbach> good morning
[07:16] <thurston> Good day, do I need Anti-Virus software on Ubuntu. I am currently using Intrepid and will be moving to 9.04 on Wednesday.
[07:22] <persia> thurston, This isn't really a support forum: you might try #ubuntu or #ubuntu-CC where "CC" represents a country code.  The answer is "It depends on what you are doing".  Some people don't use anti-virus software, with no problems.  Some people install such software and scan regularly.
=== mkorn is now known as thekoern_
=== thekoern_ is now known as thekorn_
=== thekorn_ is now known as thekorn
[09:44] <Le-Chuck_ITA> Hi there, I have a very serious bug in jaunty (X locks on boot, black screen and keyboard locked) and it's unclear to me even how to reproduce it: the system installs fine, after some reboot (perhaps just one) it goes bad. I don't install upgrades meanwhile. Can someone triage bug #364488 ? I think it is urgent because jaunty is to be released.
[09:44] <ubottu> Launchpad bug 364488 in ubuntu "After some day of installation, Xorg won't start anymore (black screen and locked keyboard)" [Undecided,New] https://launchpad.net/bugs/364488
[09:55] <primes2h> bdmurray: I'm going to do a cleaning work against kernel 2.6.22 due to Gutsy end of life. Is this wiki page the right one? https://wiki.ubuntu.com/QATeam/KernelBugMigration  (I have to fit it obviously)
[09:59] <dholbach> primes2h: try asking in #ubuntu-kernel - bdmurray and ogasawara are not awake yet (and probably won't be for the next ~6h)
[10:00] <Le-Chuck_ITA> what's the name of the xorg-devel channel for ubuntu?
[10:01] <dholbach> Le-Chuck_ITA: #ubuntu-x
[10:02] <Le-Chuck_ITA> thanks dholbach; may I advertise a serious bug too (I did that above but likely nobody saw it)? it's https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/364488
[10:02] <ubottu> Launchpad bug 364488 in ubuntu "After some day of installation, Xorg won't start anymore (black screen and locked keyboard)" [Undecided,New]
[10:02] <Le-Chuck_ITA> needs triaging
[10:04] <dholbach> Le-Chuck_ITA: https://wiki.ubuntu.com/X/Debugging might help
[10:05] <Le-Chuck_ITA> dholbach: do you have an idea why apport is not collecting the crash?
[10:05] <Le-Chuck_ITA> ah because it has to ask me first
[10:06] <dholbach> Le-Chuck_ITA: I have no idea - maybe it's not a segfault or something?
[10:06] <dholbach> anything in /var/crash?
[10:06] <Le-Chuck_ITA> nothing in /var/crash but I have a small backtrace in the Xorg log
[10:06] <Le-Chuck_ITA> that meaning that Xorg crashes
[10:07] <Le-Chuck_ITA> is there a boot argument to avoid starting gdm and X or should I manually edit the runlevels from a chroot?
[10:09] <Le-Chuck_ITA> dholbach: if you have the time please triage the bug, I will try to gather more information on it this evening (I have to go to work at some point :P)
[10:10] <dholbach> Le-Chuck_ITA: as I said above: I have no clue about X.org
[10:10] <thekorn> Le-Chuck_ITA: you can also run `apport-collect <#BUGNUMBER>` to get more information
[10:11] <thekorn> hey dholbach
[10:11] <dholbach> hiya thekorn
[10:11] <primes2h> dholbach: Thank you!
[10:12] <dholbach> primes2h: no worries
[10:12] <Le-Chuck_ITA> thekorn: ok I am doing that from a chroot but please triage the bug... it's serious and jaunty is going to be released soon, at least it could go in the release notes
[10:12] <dholbach> Le-Chuck_ITA: try bringing it up in #ubuntu-devel if it's serious
[10:13] <Le-Chuck_ITA> thekorn: I can't do that... X does not work :)
[10:13] <Le-Chuck_ITA> ah
[10:13] <Le-Chuck_ITA> incredibly dumb
[10:13] <Le-Chuck_ITA> I have to figure how to export the display to a chroot
[10:13] <Le-Chuck_ITA> ssh -X
[10:13] <Le-Chuck_ITA> ok this evening I'll have more time
[10:14] <Le-Chuck_ITA> dholbach: thanks. Does that mean nobody's going to triage anything in response to this call :)
[10:15] <thekorn> Le-Chuck_ITA: sorry, but why do you need a running x server to get apport-collect running?
[10:15] <Le-Chuck_ITA> thekorn: x-www-browser: cannot connect to X server :0.0
[10:16] <dholbach> Le-Chuck_ITA: I just said that *I* don't have a clue about x and am not the best person to talk to
[10:16] <dholbach> there's:
[10:16] <dholbach> #ubuntu-devel
[10:16] <dholbach> #ubuntu-x
[10:16] <dholbach> ubuntu-x@lists.ubuntu.com
[10:17] <thekorn> Le-Chuck_ITA: also  you asked some time ago why apport did not catch this segfault, I think it's because apport is disabled in preparation of the release
[10:17] <Le-Chuck_ITA> dholbach: thanks, you also helped me a lot a long time ago when I was trying to take care of lyx
[10:17] <Le-Chuck_ITA> I always remember that when I meet you :) so ok I bother ubuntu-devel
[10:17] <dholbach> Le-Chuck_ITA: all the best with that problem - hope you get it resolved!
[10:18] <dholbach> tjaalton: do you have an idea about bug 364488?
[10:18] <ubottu> Launchpad bug 364488 in xorg "After some day of installation, Xorg won't start anymore (black screen and locked keyboard)" [Undecided,New] https://launchpad.net/bugs/364488
[10:19] <tjaalton> dholbach: replied already
[10:19] <dholbach> ah supeR!
[10:19] <tjaalton> probably because he might have wacom entries in xorg.conf
[10:19]  * dholbach is definitely too slow for tjaalton
[10:19] <tjaalton> heh
[10:19] <dholbach> Le-Chuck_ITA: ^
[10:19] <Le-Chuck_ITA> tjaalton: that may be right and explain why on first reboot!
[10:19] <tjaalton> Le-Chuck_ITA: you left #ubuntu-x too quickly
[10:20] <Le-Chuck_ITA> tjaalton: I close windows by mistake, I rejoined immediately :)
[10:20] <Le-Chuck_ITA> tjaalton: sorry for that
[10:20] <tjaalton> Le-Chuck_ITA: try commenting them out
[10:20] <Le-Chuck_ITA> tjaalton: ok will report back and then go to work. Thanks for attention. But then... this means wacom is broken, is it temporary? More info?
[10:21] <tjaalton> Le-Chuck_ITA: no, it doesn't need those entries anymore
[10:21] <Le-Chuck_ITA> tjaalton: aaaah right I recall somebody working on that, was it you?
[10:21] <tjaalton> but it's still a bug that it crashes like that, and the fix is being investigated
[10:21] <tjaalton> yes
[10:22] <Le-Chuck_ITA> tjaalton: thank you very much for everything then. I reboot now
[10:23]  * tjaalton needs a proper wacom to work on the driver :)
[10:24] <Le-Chuck_ITA> bye all
[10:24] <dholbach> Le-Chuck_ITA: let us know if it works
[10:24] <Le-Chuck_ITA> dholbach: will report back on the bug
[10:28] <Le-Chuck_ITA> dholbach: tjaalton: I am now back in my jaunty installation, really thanks. However not everything is perfect: xsetwacom set stylus button2 "button 3"
[10:28] <Le-Chuck_ITA> Error (2): WacomConfigOpenDevice: No such device
[10:28] <Le-Chuck_ITA> Set: Failed to open device 'stylus'
[10:28] <Le-Chuck_ITA> tjaalton: a link to an existing documentation would be sufficient :)
[10:29] <tjaalton> check 'xinput list' for the device names, it's not 'stylus'
[10:29] <tjaalton> comes from hal
[10:30] <Le-Chuck_ITA> tjaalton: whoa
[10:30] <Le-Chuck_ITA> thanks
[10:30] <Le-Chuck_ITA> it works nicely. Then I can start advertising that Jaunty works on tablet pcs?
[10:30] <tjaalton> I guess
[10:30] <Le-Chuck_ITA> very good. I waited for this since edgy.
[10:30] <BUGabundo> nice to hear its finally working for you, Le-Chuck_ITA
[10:31] <BUGabundo> but I needed it in Italy, right? not spain
[10:31] <Le-Chuck_ITA> BUGabundo: no, that's the vga out :)
[10:31] <Le-Chuck_ITA> the tablet I need it in spain too
[10:31] <BUGabundo> oh ok
[10:31] <Le-Chuck_ITA> to be precise it worked _for me_ from the very first day :P I hope it will work for a lot more people now.
[10:32] <Le-Chuck_ITA> I will bet my face on that from now on.
[10:32] <Le-Chuck_ITA> well it's really time to go bye all
=== yofel is now known as yofel_
=== yofel_ is now known as yofel__
=== yofel__ is now known as yofel
=== Adri2000_ is now known as Adri2000
=== asac_ is now known as asac
[14:50] <bddebian> Boo
[15:10] <KhaaL> hi, i'm looking to enhance my bug-reports and I'd like my latest bug report to be examined and recieve feedback on whats good, missing and so on :-) https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/364483
[15:10] <ubottu> Ubuntu bug 364483 in pulseaudio "streaming will abort in the beginning with pulseaudio running " [Undecided,New]
=== yofel_ is now known as yofel
[15:15] <MagicFab> hi all
[15:17] <MagicFab> I have a mouse (USB) that's not recognized, doesn't work unless unsin a PS2 adapter
[15:17] <MagicFab> what package should I log that against ?
[15:20] <Ampelbein> MagicFab: I'd say the "linux" source-package.
[15:21] <Ampelbein> MagicFab: be sure to use "apport-collect -p linux <bug#>" after plugging in the usb-mouse so that updated logfiles will be automatically attached to the report
[15:23] <MagicFab> Ampelbein, oh cool, didn't know I could use that for non-aplication-specific bugs
[15:24] <Ampelbein> MagicFab: see https://wiki.ubuntu.com/Apport#Per-package%20Apport%20Hooks for a list
[15:24] <Ampelbein> MagicFab: it's a really cool help for bug triaging.
[15:25] <MagicFab> surething
=== Sikon is now known as LucidFox
[15:58] <mvo> bdmurray: re #364418 - please let me know if the latest u-m fixes this (0.111.6 should have the fix)
[15:59] <bdmurray> mvo: is that the disk full one?
[16:00] <mvo> bdmurray: yes
[16:02] <mvo> bdmurray: at least in the report the u-m version is a bit dated
=== fenris- is now known as e-jat
[16:24] <soren> Do any of you guys have a good presentation on bug triaging that I can steal^Wreuse?
[16:46] <primes2h>  bdmurray: I'm going to do a cleaning work against kernel 2.6.22 due to Gutsy end of life. Is this wiki page the right one? https://wiki.ubuntu.com/QATeam/KernelBugMigration  (I have to fit it obviously)
[16:47] <bdmurray> primes2h: ogasawara is really the best one to ask
[16:47] <primes2h> bdmurray: Ok, thanks!
[16:47] <ogasawara> primes2h: that's awesome, lemme review the wiki really quick
[16:47] <bdmurray> primes2h: how exactly are you going to do it?  manually or programatically?
[16:48] <primes2h> manually, as I did for edgy. :-)
[16:48] <primes2h> and in part for feisty...
[16:49] <bdmurray> If you ask people to test in Jaunty don't forget to mention apport-collect!
[16:49] <primes2h> bdmurray: Sure!
[16:49] <ogasawara> primes2h: yah, you don't really want to use that wiki.  It was for a one time migration of linux-source-2.6.xx bugs to linux.  Let me craft a quick stock reply for you to use.
[16:52] <primes2h> ogasawara: for edgy I used a wiky page that was really complete, but I can't find it now.
[16:59] <Ampelbein> bdmurray: is there a quick way to list all open bugs with [$something] in the title? i want to search for bugs having a [hardy] or [intrepid] or [jaunty] in the bug title and see if they can be updated/closed.
[17:00] <seb128> we should refuse bugs which have the version in the title and explain them that's not the place to write this information ;-)
[17:02] <bdmurray> Ampelbein: you could try the regular launchpad search for that and see what happens
[17:02] <mnemo> seb128: whats the right way? tags?
[17:02] <seb128> write it in the description?
[17:03] <bdmurray> Ampelbein: or you could use the mailing list...
[17:03] <seb128> the title just doesn't make sense
[17:03] <seb128> we have quite some (gutsy) (hardy) (etc) bugs now
[17:03] <seb128> does it make the bug is specific to those versions?
[17:03] <seb128> or that it has been reported there?
[17:03] <mnemo> seb128: for xorg we use [chipset] like [G45] etc and also we append (UXA) to all UXA wishlist bugs
[17:03] <seb128> are we supposed to update all the title every 6 months?
[17:04] <bdmurray> Ampelbein: the lp search didn't work out so well so definitely the mailing list
[17:04] <mnemo> seb128: good point
[17:04] <hggdh> probably that it was reported there (or during development of the release)
[17:04] <seb128> mnemo: the chipset info isn't deprecated over time though
[17:04] <mnemo> yea
[17:04] <hggdh> so what Ampelbein is proposing is a good search...
[17:04] <Ampelbein> bdmurray: yeah, i tried the lp-search and was not so pleased with the result
[17:05] <bdmurray> Ampelbein: I could make a list of bugs for you next week or so
[17:06] <seb128> bugs that would be nice to list are all apport-crash bugs reported before hardy and which didn't change since
[17:06] <ogasawara> primes2h: so there are a few scenarios you'll run into with the linux-source-2.6.22 bugs - https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22
[17:06] <ogasawara> primes2h: the first will have a linux-source-2.6.22 task open as well as a linux task open
[17:06] <seb128> they are probably good candidates for an automatic "do you still get the issue" comment and closing after a month if nobody replies
[17:06] <Ampelbein> bdmurray: it's not a top priority just a minor issue so no need to spend much time on.
[17:06] <ogasawara> primes2h: in that case I'd suggest using the following stock reply - http://pastebin.ubuntu.com/155414/
[17:06] <ogasawara> primes2h: you'll set the linux-source-2.6.22 task to "Won't Fix" and the linux task to "Incomplete"
[17:08] <ogasawara> primes2h: the other scenario will be that it has a linux-source-2.6.22 task open but will not have a linux task open
[17:08] <ogasawara> primes2h: in that case you'll have to add the linux task and then set it to incomplete and also then set the linux-source-2.6.22 task to Won't Fix
[17:08] <ogasawara> primes2h: that make sense?
[17:09] <bdmurray> Ampelbein: no problem it took just a minute to write
[17:09] <primes2h> ogasawara: for edgy I remember I did the same, and I add the tag edgy-close
[17:10] <ogasawara> primes2h: adding a tag wouldn't hurt either
[17:10] <primes2h> ogasawara: Do I need to set linux task as incomplete even if it's already present?
[17:10] <primes2h> ogasawara: There i a point in adding linux-source-2.6.22 tag?
[17:11] <primes2h> ogasawara: there is
[17:11] <Ampelbein> bdmurray: awesome, thanks.
[17:11] <ogasawara> primes2h: re setting linux task to incomplete sort of depends - if they haven't tested with the latest jaunty then yes please set to incomplete and ask them to test
[17:11] <bdmurray> Ampelbein: so I could generate a list of bug numbers that you could then feed to the launchpad api would that work?
[17:11] <ogasawara> primes2h: if the bug is already up to date with latest testing and debug info, just leave it as is and close the linux-source-2.6.22 task
[17:12] <ogasawara> primes2h: you'll obviously then tweak the stock reply to not ask them to test jaunty
[17:12] <Ampelbein> bdmurray: yeah, a list of the numbers is enough.
[17:12] <ogasawara> primes2h: no point really in adding the linux-source-2.6.22 tag
[17:14] <primes2h> ogasawara: ok, clear. Thank you very much!
[17:14] <ogasawara> primes2h: no thank you! feel free to ping me if you have any other questions
[17:16] <bdmurray> Ampelbein: http://pastebin.osuosl.org/25787 that's a start at least
[17:16] <ogasawara> bdmurray: also fyi, I'm not sure if any other packages may have run into apport-collect issues, but the kernel currently requires using apport-collect -p linux-image-2.6.28-11-generic <bug#>
[17:17] <bdmurray> ogasawara: oh durh
[17:21] <yoasif> not sure if this is the right place to ask, but any particular issue that seamonkey is frozen at a version with security holes in jaunty?
[17:22] <yoasif> (i get a warning every time i start up seamonkey)
[17:22] <ogasawara> primes2h: I had a few typos in the first stock reply, here's a cleaner one - http://pastebin.ubuntu.com/155427/
[17:24]  * yoasif ignore what i said last... :)
[17:25] <Ampelbein> bdmurray: thanks, thats a good start
[17:29] <bdmurray> Ampelbein: you'll want to check the status of them as the bugs may now be closed etc...
[17:30] <Ampelbein> bdmurray: seen that. btw: staging is ok to be used as testing enivorenment? i.e.: I can do no harm to the actual live-system?
[17:31] <bdmurray> Ampelbein: that's correct
[17:35] <primes2h> ogasawara: That's nice, thanks.
=== fenris- is now known as e-jat
[19:04] <adrian15>  I have found an error that involves three packages. I have reported the bug in the three packages one or two months ago and I have not got an answer. Is there any mailing list for discussing bugs that affect several packages? Should I susbcribe to motu mailing list, perhaps?
[19:04] <bdmurray> adrian15: what bug number?
[19:05] <adrian15> bdmurray:  ok, wait a second
[19:06] <adrian15> bdmurray: 320623 320626 320629
[19:06] <adrian15> bdmurray: Do not read the "vaporware" part. I actually meant that it was a metabug.
[19:07] <Elbrus> bugs 320623,  320626, 320629
[19:07] <ubottu> Launchpad bug 320623 in initramfs-tools "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/320623
[19:07] <ubottu> Launchpad bug 320626 in live-initramfs "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/320626
[19:07] <ubottu> Launchpad bug 320629 in busybox "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/320629
[19:12] <bdmurray> all three of those should be merged into one bug report a bug can affect multiple packages
[19:13] <adrian15> ahm
[19:14] <adrian15> bdmurray: Going to do so then.
[19:15] <adrian15> bdmurray: but what about package version? Should I write the three different packages version in the same bug, isn't it?
[19:16] <adrian15> bdmurray:  Or will I text box will appear when I choose another project in order to write specific project bug details?
[19:16] <adrian15> bdmurray:  *Or will a
[19:16] <bdmurray> adrian15: you'll want to click "also affects distribution" and then choose a source package for Ubuntu
[19:17] <bdmurray> adrian15: and no a text box won't appear however you can modify the description of a bug by clicking "update description / tags"
[19:17] <adrian15> bdmurray: ok
[19:17] <bdmurray> adrian15: you could then also remove the 'vaporware' bit
[19:17] <adrian15> bdmurray: Going to update it and ask for your approval.
[19:25] <adrian15> bdmurray: This is the old bug renewed: 320623 and in the other hand 320626 and 320629 are marked as duplicated of the former one.
[19:25] <adrian15> bdmurray: Are they fine?
[19:26] <bdmurray> adrian15: yes, that looks better
[19:26] <bdmurray> adrian15: what software does that patch change?
[19:27] <adrian15> bdmurray: It only changes initramfs-tools and live-initramfs. Busybox is affected by the bug but it is not modified by the patch.
[19:28] <adrian15> bdmurray: Maybe Binary Package Hint: Busybox is incorrect? Actually, I do not know what does it mean.
[19:30] <adrian15> bdmurray: Well, I was wrong.
[19:31] <adrian15> bdmurray: The patch modifies an initrd file that has been generated thanks to mkinitramfs (or similar program). The program behaviour depends on both initramfs-tools and live-initramfs contents.
[19:33] <adrian15> bdmurray: You know an initrd is what FAI uses for setting up the fully automatic installation after booting via PXE. So fai, in its setup process needs to build an appropiated initrd for booting it from clients later. In order to build the initrd it uses a "mkinitramfs" command.
[19:37] <adrian15> What I actually want to know if how to "somewhat force" the three packages developer to discuss about this bug. I do not mind making any test that they ask me but I think it is better for all of us. Because I actually do not know if changing one line to another value will affect other packages or not.
[19:38] <Elbrus> adrian15: there is no such way to force....
[19:38] <adrian15> Elbrus: I know.
[19:39] <Elbrus> just provide as much info as possible
[19:39] <Elbrus> testing the patch you taked about helps
[19:39] <Elbrus> create a proper debdiff if you really want to get to the bottom of it
[19:39] <adrian15> Elbrus: I have tested it. I have made it myself.
[19:40] <adrian15> Elbrus: a debdiff???, url with explanation?
[19:40] <Elbrus> ok, then build the packages in a chroot (using for instance pdebuild)
[19:40] <adrian15> I have already a repository with these packages modified
[19:40] <adrian15> (well, busybox is not modified)
[19:40] <Elbrus> aha, then it is probably easy
[19:41]  * Elbrus is looking up some commands
[19:41] <adrian15> Elbrus: The patch (I do not mean the debug patch but the patch that I used for my own repository) does work but I do not like because it uses "OR" sentences to try one mount syntax or the other mount syntax.
[19:42] <Elbrus> so you might want to try and create a patch you do like
[19:42] <bdmurray> adding a patch to the bug report will increase the likelyhood of it getting looked at
[19:43] <adrian15> bdmurray: Elbrus: I see.
[19:43] <Elbrus> adrian15: debdiff <ubuntu-org>.dsc <your-version>.dsc
[19:44] <adrian15> Elbrus: Oh! No! I am in a Fedora environment! I should have taken my portable hard disk.
[19:45]  * Elbrus doesn't know anything about Fedora env.
[19:46] <adrian15> Elbrus: Hey. I think that this is what you were looking for. It has been generated automatically from the repository.
[19:46] <adrian15> Elbrus:  So I just attach this to the bug or add just a link. Is better to attach it, isn't it?
[19:47] <Elbrus> attach is prefered
[19:48] <bdmurray> launchpad searchs for bug with patches will only reveal them if they are in launchpad
[20:01] <adrian15> bdmurray: Elbrus: Thank you for your help. I will wait for two or three more weeks. If there is no answer I will come back to ask for a mailing list where these three package responsibles/developers.
[20:01] <adrian15> meet.
[21:49] <dtchen> i'm receiving a 403 on the password reset for the iso tracker
[21:50] <dtchen> You don't seem to have the right to access this page.
[21:50] <dtchen> Please make sure you are connected as the right user.
[21:50] <dtchen> nevermind, must have been process lag.
[21:54] <BUGabundo> seb128: ping
[21:54] <BUGabundo> seb128: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/364843
[21:54] <BUGabundo> is it ubuntu or do I need to send upstream too?
[21:56] <seb128> BUGabundo: I expect that's a duplicate of the renice bug you opened some days ago
[21:56] <seb128> the issue is an upstream one
[21:56] <seb128> or maybe that was not you, still a duplicate ;-)
[21:56] <BUGabundo> ah??
[21:56] <BUGabundo> renice?
[21:56] <BUGabundo> me ?
[21:56] <seb128> bug #363558
[21:56] <seb128> BUGabundo: sorry it was not you, that's still a duplicate
[21:56]  * BUGabundo kicks ubottu
[21:57] <BUGabundo> ok
[21:57] <BUGabundo> let me check that bug
[21:57] <seb128> and that's an upstream bug
[21:57] <BUGabundo> ill send them
[21:57] <seb128> thanks
[22:37] <BUGabundo> seb128: sent upstream. sorry it took so long
[22:37] <seb128> BUGabundo: there was no hurry, thank you for the testing and bug triage work you are doing!
[22:39] <BUGabundo> seb128: np. since I can reproduce it and it affects me...
[22:39] <BUGabundo> http://bugzilla.gnome.org/show_bug.cgi?id=579777
[22:39] <ubottu> Gnome bug 579777 in general "gnome-system-monitor renice or kill causes close" [Normal,Unconfirmed]
[22:39] <BUGabundo> maybe I really should run for bug-control team... who knows, maybe I will
[22:40] <yoasif> BUGabundo: you're everywhere, you should
[22:40] <yoasif> what do you get, eprops? ;)
[22:40] <BUGabundo> naa
[22:40] <BUGabundo> just the ability to change bug priorities and stuff
[22:40] <BUGabundo> like seeing private bugs
[22:41] <BUGabundo> but I need to have at least 5 good bugs triaged
[22:41] <BUGabundo> just adding a me too, good logs, or sending upstream doesn't count
[22:41] <yoasif> ah gotcha
[22:41] <BUGabundo> so yoasif its going to take me a while eheh
[22:41] <jcastro> BUGabundo: hero.
[22:42] <jcastro> need more upstreamed bug!
[22:42] <jcastro> nice job on the backlink too
[22:42] <BUGabundo> plus I don't always sound as calm as I should! so I don't want to put users way
[22:42] <BUGabundo> on a bad comment
[22:42] <BUGabundo> jcastro: backlink ??
[22:42] <jcastro> BUGabundo: putting the link to the launchpad bug in the upstream tracker
[22:42] <yoasif> how do i triage "firefox lags to hell sometimes"... like it is right now
[22:42] <yoasif> f'in dual core processor with flashblock, still lags
[22:42] <BUGabundo> yoasif: you change to ff 3.5 ?
[22:43] <BUGabundo> jcastro: isn't that what "sending upstream" is all about?
[22:43] <yoasif> doesn't that change my .mozilla?
[22:43] <BUGabundo> actually no, but you get my drift
[22:43] <yoasif> what is the preferred method of upgrading to ff3.5?
[22:43] <jcastro> BUGabundo: right, but sometimes people link the bug to the upstream bug in launchpad but forget to tell upstream where the launchpad bug is
[22:43] <BUGabundo> yoasif: no need to upgrade. it install in paralel and then imports the profile
[22:44] <yoasif> i was using abrowser but it didnt share my profile, so i stopped, figuring i should run my web browser as stable
[22:44] <BUGabundo> eheh I always link back from both jcastro
[22:44] <BUGabundo> I'm used to upstreaming pidgin and kdepim bugs
[22:44] <BUGabundo> and reporting bug to pidgin its an HUGE lesson!
[22:44] <jcastro> heh
[22:44] <BUGabundo> from all upstreams I talk to, they are the most aggressive ones!
[22:45] <jcastro> aggressive fixing or aggressive ... ?
[22:46] <yoasif> BUGabundo: how should i go about making this report better? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/360181
[22:46] <ubottu> Launchpad bug 360181 in linux "Acer Aspire 4530 headphones do not work when plugged in, also doesn't mute speakers" [Undecided,Confirmed]
[22:47] <BUGabundo> is that mine?
[22:47] <BUGabundo> oh you mean how can YOU improve it
[22:47] <yoasif> hehe yes
[22:47] <BUGabundo> yoasif: NEVER ever confirm your own bugs!
[22:47] <BUGabundo> its bad bug etiquete
[22:48] <BUGabundo> yoasif: you need extra logs!
[22:48] <yoasif> yeah, i figured since it was a fresh install (beta) it would be slightly kosher but i guess not :p
[22:48] <BUGabundo> $ apport-collect -p alsa-base 360181
[22:49] <dtchen> no need for that
[22:49] <dtchen> he already has alsa-info.sh output.
[22:49] <dtchen> only ask for apport-collect if alsa-info.sh output is missing
[22:50] <BUGabundo> dtchen: ok! since its on Kernel
[22:50] <BUGabundo> I though it would be nice to add extra logs
[22:50] <dtchen> all that apport hook will do is duplicate alsa-info.sh output and spam the bug report
[22:51] <BUGabundo> ok
[22:51]  * BUGabundo stops pushing apport down the users througts
[22:52] <dtchen> BUGabundo: it's fine to "[push] apport down the user's [throats]" - just do it conditionally.
[22:53] <dtchen> for sound bugs, if alsa-info.sh output is present, there's no need for additional apport info
[22:53] <BUGabundo> ok
[22:56] <yoasif> so yeah, how can i get someone to look at that?
[22:56] <BUGabundo> yoasif: if the audio guru says its good, then its good enough
[22:56] <dtchen> yoasif: you've already pinged me about it. i'm looking at it.
[22:56] <yoasif> lol.. pinged you about the crackling bug
[22:56] <yoasif> this is a nicety
[22:56] <yoasif> crackling bug is horribly annoying ;)
[22:57] <dtchen> yoasif: my nick is highlighted across all sound bugs. you've already pinged me (perhaps unintentionally)
[22:57] <yoasif> heheh gotcha
[22:59] <dtchen> yoasif: the good news (WRT 360181) is that you could get it to work using hda-verb. The bad news is that you'll have to use hda-verb, which requires alsa debugging to be enabled in the kernel.
[22:59] <dtchen> yoasif: if you have quite a bit of RAM and a daily-live, you could try Takashi's latest alsa-driver snapshot
[22:59] <dtchen> yoasif: (where "quite a bit of RAM" is on the order of at least 1.5 GB)
[23:00] <yoasif> dtchen: i'm not concerned enough about it to "make it work" since i can work around it, i just want it fixed so it's "magic" for anyone else who wants to install on this machine
[23:00] <yoasif> dtchen: in a vm?
[23:01] <dtchen> yoasif: bare metal, preferably
[23:02] <dtchen> yoasif: also, to me, there is no distinction between "i can make it work with fiddling" and "doesn't work"
[23:02] <yoasif> dtchen: glad to hear that :)
[23:02] <yoasif> and is there a wiki for that so i dont have to bother you about it if i wanted to do the daily-live thing?
[23:03] <dtchen> yoasif: the reason i'd like you to use a current git snapshot is that there are newer quirk configurations in the snapshot
[23:03] <dtchen> there is a fairly hackish script that someone posted on the ubuntuforums
[23:04] <dtchen> roughly: boot from daily-live, install linux-headers-$(uname -r) and build-essential, download the snapshot, compile it, install it, run /sbin/alsa force-reload
[23:05] <yoasif> yeah, i may just do that... i can make a daily-live boot on usb using unetbootin right?
[23:05] <yoasif> (running out of optical media)
[23:05] <dtchen> anything that gets you a pristine, current jaunty environment
[23:05] <yoasif> is daily live still available in cd? (my usb stick is only 2gb)
[23:06] <dtchen> http://cdimage.ubuntu.com/daily-live/current/
[23:06] <BUGabundo> yoasif: why use unetbootin? usbcreater is better
[23:06] <yoasif> BUGabundo: wasnt even aware of that, will check that out
[23:07] <BUGabundo> yoasif: System -> Admin-> make usb disk
[23:08] <yoasif> ah sweet, i noticed that before, i never looked into what it was