/srv/irclogs.ubuntu.com/2009/04/21/#ubuntu-bugs.txt

bcurtiswxbdmurray: does greasemonkey automatically keep the LP scripts up-to-date with bzr?00:15
bdmurraybcurtiswx: no, the scripts themselves are not kept up-to-date00:17
nhandlerbcurtiswx: I think there is a greasemonkey script or FF extension that can do that00:18
bcurtiswxbdmurray: ok thx00:18
bcurtiswxnhandler: oh really? do you know what its called? (i can search, just trying to epitomize laziness here)00:18
nhandlerbcurtiswx: No, sorry. I just remember having installed a script that did that at one point or another.00:20
bcurtiswxnhandler: thx for the info !00:21
bcurtiswxbdmurray: 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 out00:32
bdmurraybcurtiswx: maybe next week ;-)00:33
bcurtiswxbdmurray: very understandable.  would an e-mail be a better "reminder"?00:33
bdmurraybcurtiswx: that would rock00:33
bcurtiswxbdmurray: sent, good luck with 9.04 finalization stuff00:36
Prettohey folks, can anyone help me to report a bug in jaunty?01:40
Prettoi don't know how to report it correctly, i just know the symptom01:41
Prettothe problem is that all video player closes when i have "Virtual2560 800"  in Xorg's display section01:42
dholbachgood morning06:52
thurstonGood day, do I need Anti-Virus software on Ubuntu. I am currently using Intrepid and will be moving to 9.04 on Wednesday.07:16
persiathurston, 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.07:22
=== mkorn is now known as thekoern_
=== thekoern_ is now known as thekorn_
=== thekorn_ is now known as thekorn
Le-Chuck_ITAHi 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
ubottuLaunchpad 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/36448809:44
primes2hbdmurray: 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:55
dholbachprimes2h: try asking in #ubuntu-kernel - bdmurray and ogasawara are not awake yet (and probably won't be for the next ~6h)09:59
Le-Chuck_ITAwhat's the name of the xorg-devel channel for ubuntu?10:00
dholbachLe-Chuck_ITA: #ubuntu-x10:01
Le-Chuck_ITAthanks 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/36448810:02
ubottuLaunchpad 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_ITAneeds triaging10:02
dholbachLe-Chuck_ITA: https://wiki.ubuntu.com/X/Debugging might help10:04
Le-Chuck_ITAdholbach: do you have an idea why apport is not collecting the crash?10:05
Le-Chuck_ITAah because it has to ask me first10:05
dholbachLe-Chuck_ITA: I have no idea - maybe it's not a segfault or something?10:06
dholbachanything in /var/crash?10:06
Le-Chuck_ITAnothing in /var/crash but I have a small backtrace in the Xorg log10:06
Le-Chuck_ITAthat meaning that Xorg crashes10:06
Le-Chuck_ITAis there a boot argument to avoid starting gdm and X or should I manually edit the runlevels from a chroot?10:07
Le-Chuck_ITAdholbach: 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:09
dholbachLe-Chuck_ITA: as I said above: I have no clue about X.org10:10
thekornLe-Chuck_ITA: you can also run `apport-collect <#BUGNUMBER>` to get more information10:10
thekornhey dholbach10:11
dholbachhiya thekorn10:11
primes2hdholbach: Thank you!10:11
dholbachprimes2h: no worries10:12
Le-Chuck_ITAthekorn: 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 notes10:12
dholbachLe-Chuck_ITA: try bringing it up in #ubuntu-devel if it's serious10:12
Le-Chuck_ITAthekorn: I can't do that... X does not work :)10:13
Le-Chuck_ITAah10:13
Le-Chuck_ITAincredibly dumb10:13
Le-Chuck_ITAI have to figure how to export the display to a chroot10:13
Le-Chuck_ITAssh -X10:13
Le-Chuck_ITAok this evening I'll have more time10:13
Le-Chuck_ITAdholbach: thanks. Does that mean nobody's going to triage anything in response to this call :)10:14
thekornLe-Chuck_ITA: sorry, but why do you need a running x server to get apport-collect running?10:15
Le-Chuck_ITAthekorn: x-www-browser: cannot connect to X server :0.010:15
dholbachLe-Chuck_ITA: I just said that *I* don't have a clue about x and am not the best person to talk to10:16
dholbachthere's:10:16
dholbach#ubuntu-devel10:16
dholbach#ubuntu-x10:16
dholbachubuntu-x@lists.ubuntu.com10:16
thekornLe-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 release10:17
Le-Chuck_ITAdholbach: thanks, you also helped me a lot a long time ago when I was trying to take care of lyx10:17
Le-Chuck_ITAI always remember that when I meet you :) so ok I bother ubuntu-devel10:17
dholbachLe-Chuck_ITA: all the best with that problem - hope you get it resolved!10:17
dholbachtjaalton: do you have an idea about bug 364488?10:18
ubottuLaunchpad 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/36448810:18
tjaaltondholbach: replied already10:19
dholbachah supeR!10:19
tjaaltonprobably because he might have wacom entries in xorg.conf10:19
* dholbach is definitely too slow for tjaalton10:19
tjaaltonheh10:19
dholbachLe-Chuck_ITA: ^10:19
Le-Chuck_ITAtjaalton: that may be right and explain why on first reboot!10:19
tjaaltonLe-Chuck_ITA: you left #ubuntu-x too quickly10:19
Le-Chuck_ITAtjaalton: I close windows by mistake, I rejoined immediately :)10:20
Le-Chuck_ITAtjaalton: sorry for that10:20
tjaaltonLe-Chuck_ITA: try commenting them out10:20
Le-Chuck_ITAtjaalton: 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:20
tjaaltonLe-Chuck_ITA: no, it doesn't need those entries anymore10:21
Le-Chuck_ITAtjaalton: aaaah right I recall somebody working on that, was it you?10:21
tjaaltonbut it's still a bug that it crashes like that, and the fix is being investigated10:21
tjaaltonyes10:21
Le-Chuck_ITAtjaalton: thank you very much for everything then. I reboot now10:22
* tjaalton needs a proper wacom to work on the driver :)10:23
Le-Chuck_ITAbye all10:24
dholbachLe-Chuck_ITA: let us know if it works10:24
Le-Chuck_ITAdholbach: will report back on the bug10:24
Le-Chuck_ITAdholbach: 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_ITAError (2): WacomConfigOpenDevice: No such device10:28
Le-Chuck_ITASet: Failed to open device 'stylus'10:28
Le-Chuck_ITAtjaalton: a link to an existing documentation would be sufficient :)10:28
tjaaltoncheck 'xinput list' for the device names, it's not 'stylus'10:29
tjaaltoncomes from hal10:29
Le-Chuck_ITAtjaalton: whoa10:30
Le-Chuck_ITAthanks10:30
Le-Chuck_ITAit works nicely. Then I can start advertising that Jaunty works on tablet pcs?10:30
tjaaltonI guess10:30
Le-Chuck_ITAvery good. I waited for this since edgy.10:30
BUGabundonice to hear its finally working for you, Le-Chuck_ITA10:30
BUGabundobut I needed it in Italy, right? not spain10:31
Le-Chuck_ITABUGabundo: no, that's the vga out :)10:31
Le-Chuck_ITAthe tablet I need it in spain too10:31
BUGabundooh ok10:31
Le-Chuck_ITAto be precise it worked _for me_ from the very first day :P I hope it will work for a lot more people now.10:31
Le-Chuck_ITAI will bet my face on that from now on.10:32
Le-Chuck_ITAwell it's really time to go bye all10:32
=== 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
bddebianBoo14:50
KhaaLhi, 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/36448315:10
ubottuUbuntu bug 364483 in pulseaudio "streaming will abort in the beginning with pulseaudio running " [Undecided,New]15:10
=== yofel_ is now known as yofel
MagicFabhi all15:15
MagicFabI have a mouse (USB) that's not recognized, doesn't work unless unsin a PS2 adapter15:17
MagicFabwhat package should I log that against ?15:17
AmpelbeinMagicFab: I'd say the "linux" source-package.15:20
AmpelbeinMagicFab: 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 report15:21
MagicFabAmpelbein, oh cool, didn't know I could use that for non-aplication-specific bugs15:23
AmpelbeinMagicFab: see https://wiki.ubuntu.com/Apport#Per-package%20Apport%20Hooks for a list15:24
AmpelbeinMagicFab: it's a really cool help for bug triaging.15:24
MagicFabsurething15:25
=== Sikon is now known as LucidFox
mvobdmurray: re #364418 - please let me know if the latest u-m fixes this (0.111.6 should have the fix)15:58
bdmurraymvo: is that the disk full one?15:59
mvobdmurray: yes16:00
mvobdmurray: at least in the report the u-m version is a bit dated16:02
=== fenris- is now known as e-jat
sorenDo any of you guys have a good presentation on bug triaging that I can steal^Wreuse?16:24
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:46
bdmurrayprimes2h: ogasawara is really the best one to ask16:47
primes2hbdmurray: Ok, thanks!16:47
ogasawaraprimes2h: that's awesome, lemme review the wiki really quick16:47
bdmurrayprimes2h: how exactly are you going to do it?  manually or programatically?16:47
primes2hmanually, as I did for edgy. :-)16:48
primes2hand in part for feisty...16:48
bdmurrayIf you ask people to test in Jaunty don't forget to mention apport-collect!16:49
primes2hbdmurray: Sure!16:49
ogasawaraprimes2h: 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:49
primes2hogasawara: for edgy I used a wiky page that was really complete, but I can't find it now.16:52
Ampelbeinbdmurray: 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.16:59
seb128we should refuse bugs which have the version in the title and explain them that's not the place to write this information ;-)17:00
bdmurrayAmpelbein: you could try the regular launchpad search for that and see what happens17:02
mnemoseb128: whats the right way? tags?17:02
seb128write it in the description?17:02
bdmurrayAmpelbein: or you could use the mailing list...17:03
seb128the title just doesn't make sense17:03
seb128we have quite some (gutsy) (hardy) (etc) bugs now17:03
seb128does it make the bug is specific to those versions?17:03
seb128or that it has been reported there?17:03
mnemoseb128: for xorg we use [chipset] like [G45] etc and also we append (UXA) to all UXA wishlist bugs17:03
seb128are we supposed to update all the title every 6 months?17:03
bdmurrayAmpelbein: the lp search didn't work out so well so definitely the mailing list17:04
mnemoseb128: good point17:04
hggdhprobably that it was reported there (or during development of the release)17:04
seb128mnemo: the chipset info isn't deprecated over time though17:04
mnemoyea17:04
hggdhso what Ampelbein is proposing is a good search...17:04
Ampelbeinbdmurray: yeah, i tried the lp-search and was not so pleased with the result17:04
bdmurrayAmpelbein: I could make a list of bugs for you next week or so17:05
seb128bugs that would be nice to list are all apport-crash bugs reported before hardy and which didn't change since17:06
ogasawaraprimes2h: 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.2217:06
ogasawaraprimes2h: the first will have a linux-source-2.6.22 task open as well as a linux task open17:06
seb128they are probably good candidates for an automatic "do you still get the issue" comment and closing after a month if nobody replies17:06
Ampelbeinbdmurray: it's not a top priority just a minor issue so no need to spend much time on.17:06
ogasawaraprimes2h: in that case I'd suggest using the following stock reply - http://pastebin.ubuntu.com/155414/17:06
ogasawaraprimes2h: you'll set the linux-source-2.6.22 task to "Won't Fix" and the linux task to "Incomplete"17:06
ogasawaraprimes2h: the other scenario will be that it has a linux-source-2.6.22 task open but will not have a linux task open17:08
ogasawaraprimes2h: 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 Fix17:08
ogasawaraprimes2h: that make sense?17:08
bdmurrayAmpelbein: no problem it took just a minute to write17:09
primes2hogasawara: for edgy I remember I did the same, and I add the tag edgy-close17:09
ogasawaraprimes2h: adding a tag wouldn't hurt either17:10
primes2hogasawara: Do I need to set linux task as incomplete even if it's already present?17:10
primes2hogasawara: There i a point in adding linux-source-2.6.22 tag?17:10
primes2hogasawara: there is17:11
Ampelbeinbdmurray: awesome, thanks.17:11
ogasawaraprimes2h: 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 test17:11
bdmurrayAmpelbein: so I could generate a list of bug numbers that you could then feed to the launchpad api would that work?17:11
ogasawaraprimes2h: 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 task17:11
ogasawaraprimes2h: you'll obviously then tweak the stock reply to not ask them to test jaunty17:12
Ampelbeinbdmurray: yeah, a list of the numbers is enough.17:12
ogasawaraprimes2h: no point really in adding the linux-source-2.6.22 tag17:12
primes2hogasawara: ok, clear. Thank you very much!17:14
ogasawaraprimes2h: no thank you! feel free to ping me if you have any other questions17:14
bdmurrayAmpelbein: http://pastebin.osuosl.org/25787 that's a start at least17:16
ogasawarabdmurray: 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:16
bdmurrayogasawara: oh durh17:17
yoasifnot 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:21
yoasif(i get a warning every time i start up seamonkey)17:22
ogasawaraprimes2h: I had a few typos in the first stock reply, here's a cleaner one - http://pastebin.ubuntu.com/155427/17:22
* yoasif ignore what i said last... :)17:24
Ampelbeinbdmurray: thanks, thats a good start17:25
bdmurrayAmpelbein: you'll want to check the status of them as the bugs may now be closed etc...17:29
Ampelbeinbdmurray: 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:30
bdmurrayAmpelbein: that's correct17:31
primes2hogasawara: That's nice, thanks.17:35
=== fenris- is now known as e-jat
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
bdmurrayadrian15: what bug number?19:04
adrian15bdmurray:  ok, wait a second19:05
adrian15bdmurray: 320623 320626 32062919:06
adrian15bdmurray: Do not read the "vaporware" part. I actually meant that it was a metabug.19:06
Elbrusbugs 320623,  320626, 32062919:07
ubottuLaunchpad bug 320623 in initramfs-tools "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/32062319:07
ubottuLaunchpad bug 320626 in live-initramfs "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/32062619:07
ubottuLaunchpad bug 320629 in busybox "Some problems with mount --bind -o bind syntax" [Undecided,New] https://launchpad.net/bugs/32062919:07
bdmurrayall three of those should be merged into one bug report a bug can affect multiple packages19:12
adrian15ahm19:13
adrian15bdmurray: Going to do so then.19:14
adrian15bdmurray: but what about package version? Should I write the three different packages version in the same bug, isn't it?19:15
adrian15bdmurray:  Or will I text box will appear when I choose another project in order to write specific project bug details?19:16
adrian15bdmurray:  *Or will a19:16
bdmurrayadrian15: you'll want to click "also affects distribution" and then choose a source package for Ubuntu19:16
bdmurrayadrian15: and no a text box won't appear however you can modify the description of a bug by clicking "update description / tags"19:17
adrian15bdmurray: ok19:17
bdmurrayadrian15: you could then also remove the 'vaporware' bit19:17
adrian15bdmurray: Going to update it and ask for your approval.19:17
adrian15bdmurray: 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
adrian15bdmurray: Are they fine?19:25
bdmurrayadrian15: yes, that looks better19:26
bdmurrayadrian15: what software does that patch change?19:26
adrian15bdmurray: It only changes initramfs-tools and live-initramfs. Busybox is affected by the bug but it is not modified by the patch.19:27
adrian15bdmurray: Maybe Binary Package Hint: Busybox is incorrect? Actually, I do not know what does it mean.19:28
adrian15bdmurray: Well, I was wrong.19:30
adrian15bdmurray: 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:31
adrian15bdmurray: 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:33
adrian15What 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:37
Elbrusadrian15: there is no such way to force....19:38
adrian15Elbrus: I know.19:38
Elbrusjust provide as much info as possible19:39
Elbrustesting the patch you taked about helps19:39
Elbruscreate a proper debdiff if you really want to get to the bottom of it19:39
adrian15Elbrus: I have tested it. I have made it myself.19:39
adrian15Elbrus: a debdiff???, url with explanation?19:40
Elbrusok, then build the packages in a chroot (using for instance pdebuild)19:40
adrian15I have already a repository with these packages modified19:40
adrian15(well, busybox is not modified)19:40
Elbrusaha, then it is probably easy19:40
* Elbrus is looking up some commands19:41
adrian15Elbrus: 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:41
Elbrusso you might want to try and create a patch you do like19:42
bdmurrayadding a patch to the bug report will increase the likelyhood of it getting looked at19:42
adrian15bdmurray: Elbrus: I see.19:43
Elbrusadrian15: debdiff <ubuntu-org>.dsc <your-version>.dsc19:43
adrian15Elbrus: Oh! No! I am in a Fedora environment! I should have taken my portable hard disk.19:44
* Elbrus doesn't know anything about Fedora env.19:45
adrian15Elbrus: Hey. I think that this is what you were looking for. It has been generated automatically from the repository.19:46
adrian15Elbrus:  So I just attach this to the bug or add just a link. Is better to attach it, isn't it?19:46
Elbrusattach is prefered19:47
bdmurraylaunchpad searchs for bug with patches will only reveal them if they are in launchpad19:48
adrian15bdmurray: 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
adrian15meet.20:01
dtcheni'm receiving a 403 on the password reset for the iso tracker21:49
dtchenYou don't seem to have the right to access this page.21:50
dtchenPlease make sure you are connected as the right user.21:50
dtchennevermind, must have been process lag.21:50
BUGabundoseb128: ping21:54
BUGabundoseb128: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/36484321:54
BUGabundois it ubuntu or do I need to send upstream too?21:54
seb128BUGabundo: I expect that's a duplicate of the renice bug you opened some days ago21:56
seb128the issue is an upstream one21:56
seb128or maybe that was not you, still a duplicate ;-)21:56
BUGabundoah??21:56
BUGabundorenice?21:56
BUGabundome ?21:56
seb128bug #36355821:56
seb128BUGabundo: sorry it was not you, that's still a duplicate21:56
* BUGabundo kicks ubottu21:56
BUGabundook21:57
BUGabundolet me check that bug21:57
seb128and that's an upstream bug21:57
BUGabundoill send them21:57
seb128thanks21:57
BUGabundoseb128: sent upstream. sorry it took so long22:37
seb128BUGabundo: there was no hurry, thank you for the testing and bug triage work you are doing!22:37
BUGabundoseb128: np. since I can reproduce it and it affects me...22:39
BUGabundohttp://bugzilla.gnome.org/show_bug.cgi?id=57977722:39
ubottuGnome bug 579777 in general "gnome-system-monitor renice or kill causes close" [Normal,Unconfirmed]22:39
BUGabundomaybe I really should run for bug-control team... who knows, maybe I will22:39
yoasifBUGabundo: you're everywhere, you should22:40
yoasifwhat do you get, eprops? ;)22:40
BUGabundonaa22:40
BUGabundojust the ability to change bug priorities and stuff22:40
BUGabundolike seeing private bugs22:40
BUGabundobut I need to have at least 5 good bugs triaged22:41
BUGabundojust adding a me too, good logs, or sending upstream doesn't count22:41
yoasifah gotcha22:41
BUGabundoso yoasif its going to take me a while eheh22:41
jcastroBUGabundo: hero.22:41
jcastroneed more upstreamed bug!22:42
jcastronice job on the backlink too22:42
BUGabundoplus I don't always sound as calm as I should! so I don't want to put users way22:42
BUGabundoon a bad comment22:42
BUGabundojcastro: backlink ??22:42
jcastroBUGabundo: putting the link to the launchpad bug in the upstream tracker22:42
yoasifhow do i triage "firefox lags to hell sometimes"... like it is right now22:42
yoasiff'in dual core processor with flashblock, still lags22:42
BUGabundoyoasif: you change to ff 3.5 ?22:42
BUGabundojcastro: isn't that what "sending upstream" is all about?22:43
yoasifdoesn't that change my .mozilla?22:43
BUGabundoactually no, but you get my drift22:43
yoasifwhat is the preferred method of upgrading to ff3.5?22:43
jcastroBUGabundo: right, but sometimes people link the bug to the upstream bug in launchpad but forget to tell upstream where the launchpad bug is22:43
BUGabundoyoasif: no need to upgrade. it install in paralel and then imports the profile22:43
yoasifi was using abrowser but it didnt share my profile, so i stopped, figuring i should run my web browser as stable22:44
BUGabundoeheh I always link back from both jcastro22:44
BUGabundoI'm used to upstreaming pidgin and kdepim bugs22:44
BUGabundoand reporting bug to pidgin its an HUGE lesson!22:44
jcastroheh22:44
BUGabundofrom all upstreams I talk to, they are the most aggressive ones!22:44
jcastroaggressive fixing or aggressive ... ?22:45
yoasifBUGabundo: how should i go about making this report better? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/36018122:46
ubottuLaunchpad bug 360181 in linux "Acer Aspire 4530 headphones do not work when plugged in, also doesn't mute speakers" [Undecided,Confirmed]22:46
BUGabundois that mine?22:47
BUGabundooh you mean how can YOU improve it22:47
yoasifhehe yes22:47
BUGabundoyoasif: NEVER ever confirm your own bugs!22:47
BUGabundoits bad bug etiquete22:47
BUGabundoyoasif: you need extra logs!22:48
yoasifyeah, i figured since it was a fresh install (beta) it would be slightly kosher but i guess not :p22:48
BUGabundo$ apport-collect -p alsa-base 36018122:48
dtchenno need for that22:49
dtchenhe already has alsa-info.sh output.22:49
dtchenonly ask for apport-collect if alsa-info.sh output is missing22:49
BUGabundodtchen: ok! since its on Kernel22:50
BUGabundoI though it would be nice to add extra logs22:50
dtchenall that apport hook will do is duplicate alsa-info.sh output and spam the bug report22:50
BUGabundook22:51
* BUGabundo stops pushing apport down the users througts22:51
dtchenBUGabundo: it's fine to "[push] apport down the user's [throats]" - just do it conditionally.22:52
dtchenfor sound bugs, if alsa-info.sh output is present, there's no need for additional apport info22:53
BUGabundook22:53
yoasifso yeah, how can i get someone to look at that?22:56
BUGabundoyoasif: if the audio guru says its good, then its good enough22:56
dtchenyoasif: you've already pinged me about it. i'm looking at it.22:56
yoasiflol.. pinged you about the crackling bug22:56
yoasifthis is a nicety22:56
yoasifcrackling bug is horribly annoying ;)22:56
dtchenyoasif: my nick is highlighted across all sound bugs. you've already pinged me (perhaps unintentionally)22:57
yoasifheheh gotcha22:57
dtchenyoasif: 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
dtchenyoasif: if you have quite a bit of RAM and a daily-live, you could try Takashi's latest alsa-driver snapshot22:59
dtchenyoasif: (where "quite a bit of RAM" is on the order of at least 1.5 GB)22:59
yoasifdtchen: 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 machine23:00
yoasifdtchen: in a vm?23:00
dtchenyoasif: bare metal, preferably23:01
dtchenyoasif: also, to me, there is no distinction between "i can make it work with fiddling" and "doesn't work"23:02
yoasifdtchen: glad to hear that :)23:02
yoasifand 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:02
dtchenyoasif: the reason i'd like you to use a current git snapshot is that there are newer quirk configurations in the snapshot23:03
dtchenthere is a fairly hackish script that someone posted on the ubuntuforums23:03
dtchenroughly: boot from daily-live, install linux-headers-$(uname -r) and build-essential, download the snapshot, compile it, install it, run /sbin/alsa force-reload23:04
yoasifyeah, 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
dtchenanything that gets you a pristine, current jaunty environment23:05
yoasifis daily live still available in cd? (my usb stick is only 2gb)23:05
dtchenhttp://cdimage.ubuntu.com/daily-live/current/23:06
BUGabundoyoasif: why use unetbootin? usbcreater is better23:06
yoasifBUGabundo: wasnt even aware of that, will check that out23:06
BUGabundoyoasif: System -> Admin-> make usb disk23:07
yoasifah sweet, i noticed that before, i never looked into what it was23:08

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!