[01:08] im looking at bug #373916 , and i am wondering in trying to help this person.. Im thinking i should get a log file of some sort from them, but im not sure which would be best... anyone know which one would be best.. or if im going in the wrong direction to grab a log file [01:08] Launchpad bug 373916 in ubuntu "Ubuntu 8.04 temporary freezes" [Undecided,New] https://launchpad.net/bugs/373916 [01:10] first off, i know the bug title is vague... but I don't think its at the fault of the reporter [01:12] bcurtiswx, might be known. Ask him to attach dmesg... we might see (I hope) a message about a soft lockup) [01:13] hggdh: hmm, for my own learning here... what is a "soft lockup" message (asking for dmesg now too, thx hggdh) [01:14] let me see if I find the bug I was thinking about [01:14] damn. is gnome's bugzilla just slow for me? it currently makes launchpad feel like a rocketship ;-) [01:14] Ampelbein, welcome to b.g.o ;-) it can get slow. If it is too slow, ping #bugs, perhaps someone is running a big search there [01:15] happens every so often... [01:15] hggdh: it's probably a sign and tells me I should go to bed now... [01:16] just got home from watching the new star trek - it's awesome! [01:16] cool. Will watch it one of these days. Been hearing good about it [01:17] i've heard the other side too, that the plot just screws up the whole star-trek series plotline [01:17] bcurtiswx, for example, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/245779 [01:17] Launchpad bug 245779 in linux "Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0" [High,Confirmed] [01:18] hggdh: ah, it actually says "soft lockup", neat [01:18] bcurtiswx, it *might* be something like it. There are some bugs about it on LP [01:21] hggdh: thx [01:31] whats used on the LiveCD to format partitions? GParted? [01:32] I do not know, never used the livecd, sorry [01:32] bcurtiswx: AFAIR gparted is no longer on the livecd [01:32] bcurtiswx: yes [01:32] I thought it was [01:32] that's what I used last [01:33] they have some code to handle the disk from the installer [01:34] what package should I file a wishlist bug about that package manager [01:35] BUGabundo: I just checked the jaunty alternate CD and couldn't find it [01:35] micahg: alternate =! desktop [01:35] ah [01:35] true [01:35] bcurtiswx: ubiquity I thikn [01:35] I'm to lazy to boot a kvm to check if it is on livecd or not [01:40] BUGabundo: haha, i know how you feel. thx [01:40] Anybody else has a problem in that there is no icon in the notification area when update-manager is running? [01:41] vocx: i don't think that this is a problem. I believe that hows its designed in jaunty [01:42] bcurtiswx, oh, yes,... that's another possibility. Do you know anything concrete about that? A forum post, bug report, mailist post perhaps? [01:43] vocx: Is http://www.ubuntu.com/getubuntu/releasenotes/904#Change%20in%20notifications%20of%20available%20updates what you are seeking? [01:44] vocx: Bug 332945 [01:44] Launchpad bug 332945 in null "[Jaunty] Update Notifier icon would provide useful status information" [Low,Fix released] https://launchpad.net/bugs/332945 [01:44] humm when did that change from WontFIX to fix release??? [01:44] ok now I have 100 emails to read that I didn't want to.... grrrr [01:44] vocx: https://wiki.ubuntu.com/NotifyOSD may help [01:45] BUGabundo: its "fixed" in Karmic [01:46] heheh [01:46] mmm... what's NULL project? [01:46] I'll get there.... some day [01:46] vocx: it's a project to replace another one added by mistake [01:46] i've deleted 'em all.. got sick after 10 of 'em [01:46] so that that team doesn't get all the bug mail [01:47] So... I guess nobody subscribes to NULL project because it would get like 2313134534546 mails a day [01:47] squared... [01:47] ahaha [01:49] ooh, "restart required" just popped up in front of IRC... brb [01:52] 2 min rebioot [01:52] that's slowwww [01:53] lol, i don't have irc on auto-load [01:54] ah [01:54] http://dl.getdropbox.com/u/112892/9-05-2009.png latest desktop [01:54] wow! [01:54] As said Notify OSD is an unpolished feature, right? So right now it may have lotsa bugs that will be fixed in koala [01:55] BUGabundo: you got too much going on, holy cow (moo) [01:55] vocx: yea, its a work in progress until Karmic [01:55] vocx, yes [01:56] Well, I just one to mention that right now, on my end it doesn't obey the top left, right, etc. options [01:57] vocx: they know about that. I don't know though if they will change it from a static location to user-selected [01:57] BUGabundo, how big is your monitor and screen? [01:57] (i imagine they will) [01:58] bcurtiswx, they will, I just wanted to note the obvious bug... hehee [01:59] ...that way I don't need to actually report it... which would be like the 56th duplicate [02:00] bcurtiswx: here is another in expose http://fileland.bugabundo.net/fotos/Linux/Desktop/09-05-2009-expose.png.php [02:01] vocx: https://wiki.ubuntu.com/NotifyOSD/Comments is you don't see it there, add it [02:02] BUGabundo: you have 10 desktops? [02:02] bcurtiswx: yep. its great on multimonitor [02:02] vocx: The PNG file is 1280x800, so... I'd guess that is BUGabundo's screen resolution :) [02:02] and to show of the cube and expose [02:02] jmarsden: yep [02:03] BUGabundo: seen Gnome 3 ? [02:03] mines 1280x1024 [02:03] 1920x1200 [02:03] my monitor in 1280X1028 but use a "virtual" size of 1800x1024, I wonder how a screenshot would look like [02:03] and how much was THAT montior? [02:04] vocx: easy: prtscrn [02:04] bcurtiswx: I have not [02:05] hggdh: you should see gouki's system. 3x20" [02:05] ... [02:05] * hggdh dreams [02:05] BUGabundo, hey it worked with the screenshot thingy in the accessories menu, but it takes more than usual... unless that's a bug [02:06] vocx: send it to us [02:06] BUGabundo: http://www.youtube.com/watch?v=bRL-Qtefy68 [02:08] Try this is jaunty, select a folder with a few text files in it, right click and choose archive. Then the next dialog window takes quite a while to appear. It wasn't as slow before. (<--- bug?) [02:09] vocx: I can't.... I'm on karmic [02:09] ... anybody else? [02:10] ... karmic ... [02:10] you guys are too bleeding edge! [02:10] ahahaahahhaahahahahah [02:10] * vocx shoots edgy people [02:10] we ? nnaaaaaa [02:10] or crazy, not that different from bleeding edge [02:10] I waited more then a week before I upgraded [02:12] vocx: im not bleeding edge yet... and my window pops up just as _fast_ as the others [02:12] bcurtiswx, thanks for trying [02:13] I skimmed through the NotifyOSD specification... do you guys go to the developer summits often? Do they always sketch things in napkins? [02:20] vocx: yes [02:20] vocx: usually over dinner [02:20] bedtime [02:22] by looking at BUGabundo screenshots, I wonder if he actually goes to bed, or if he actually turns off the PC... Many people don't even log off IRC in months. [02:25] lol; === jcastro_ is now known as jcastro === tim__sharitt is now known as tim_sharitt === paul_ is now known as Elbrus [10:17] hggdh: I think I've got your audio bug now [10:17] with new updates [10:17] dtchen: fyi my sound now starts muted. had to kill PA for it to work [10:17] dtchen: still Flash is not playing any sound :( [10:18] oh and Good morning everyone [10:29] ohh and dtchen: the last tab on pavucontrol should have a big RED sigh WARNING not to use! === jussi01 is now known as Tuhina === Tuhina is now known as jussi01 === paul_ is now known as Elbrus [12:11] anyone using kmail ? [12:11] need to confirm a bug [12:11] * BUGabundo goes to #kdepim [12:12] * maxb wonders how long he's been running without any swap partitions enabled [12:13] maxb: is it working? [12:13] had two mem leaks todays [12:13] would be damned without 8GiB Swap [12:13] Somehow my swap partition seems to have changed UUID, hence it didn't get mounted at boot [12:14] I have 2GiB RAM in this laptop, which is apparently enough to run firefox, thunderbird and eclipse without swap [12:15] 4GiBs here [12:15] maxb: so you don't hibernate either [12:15] * penguin42 goes for the mean and points out he's on 3GB [12:15] penguin42: windows laptop? [12:16] hi everyone [12:16] hi bdmurray [12:16] you there ? [12:16] G__81: hi [12:16] BUGabundo: No! i945 chipset - can only do 3GB even on 64bit Linux [12:16] Hi BUGabundo [12:17] penguin42: humm no. BIOS option [12:17] penguin42: there's an option to change the amount of RAM [12:17] BUGabundo: No, I checked the datasheets for the chipset - it can only manage a total of 4GB physical including space for PCI etc [12:18] that's so bad.... bad INTEL. [12:19] if the BIOS was a bit kinder it would probably let you configure less PCI space and maybe get 3.5 [12:28] penguin42, is bdmurray here ? [12:28] * penguin42 wouldn't know [13:57] bdmurray: ping === Flare-laptop is now known as Flare183 [14:27] <|tohms|> can anyone tell me what SRU is? [14:28] * penguin42 is not sure, but I think it's sometype of proposed update [14:28] !sru [14:28] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [14:28] <|tohms|> cheers! [14:28] penguin42: learn to use the Force ^W bot [14:28] hmm, clever bot [14:29] penguin42: which one? me or ubot4`? [14:29] BUGabundo: You might be a bot - how would we know? [14:30] <|tohms|> another question (started today in bugsquad) ... if one has fixed something in trunk than the correct status would be "fix commited" isn't it? [14:31] penguin42: some say I pass the turin test. maybe I'm really a bot [14:31] but a smart bot, that makes typos too [14:31] |tohms|: I think so [14:32] <|tohms|> k thx! === asac_ is now known as asac [14:37] can somebody check that bug 369383 is tagged correctly? it is a sync-request I made from a previous bug of mine. [14:37] Launchpad bug 369383 in lesstif2 "Please sync lesstif2 0.95.0-2.3 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/369383 [14:39] * |tohms| is confused [14:40] <|tohms|> see bug https://bugs.launchpad.net/ubuntu/jaunty/+source/bluez/+bug/268502 there are several "affects" a few with status "fix released" and "fix commited" and other in "new" and so on ... shouldn't they all have the same status?? [14:40] Launchpad bug 268502 in linux "Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)" [Medium,Fix committed] [14:40] Elbrus: you have to subscribe ubuntu-universe-sponsors [14:41] kklimonda: they are subscribed [14:41] hmm.. i don't see that [14:41] I do... [14:42] right under my own name: Ubuntu Sponsors for universe [14:42] bbl [14:42] Elbrus: also the best way of requesting sync is using requestsync tool - it will take care of almost everything [14:43] Elbrus: but it looks fine to me.. [14:43] the point is that I already had a bug which I wanted to turn into the sync request [14:43] |tohms|: not necessarily. Each version will need the fix backported, thus each version could have a different status [14:43] * Elbrus knows the tool [14:43] ya, i see [14:44] kklimonda: thanks for checking [14:44] hmm.. i wonder why I don't see ubuntu sponsors.. [14:44] maybe there is a bug in edge.. [14:45] <|tohms|> charlie-tca: let me see if i understood: that means bug is fixed in package linux (means kernel) but bluez is not prepared to work with that fixed version? [14:45] I see the bug mentioned on https://bugs.launchpad.net/~ubuntu-universe-sponsors/+bugs?start=75 so they are subscribed I would say [14:45] yeah, looks like it - without edge it works.. [14:45] what is edge anyway, the beta of launchpad? [14:46] |tohms|: more or less. The ubuntu linux kernel team created a fix, but Jaunty and Intrepid both need the fix backported. [14:46] yes [14:46] The kernel fix does not fix the bluez package [14:47] That needs its own fix put into its own package [14:47] does the status of the sync request need to be "wishlist"? [14:47] it should be [14:47] |tohms|: and the top two items are separate bugs filed in different bugzilla's [14:47] aha, I will change that [14:48] <|tohms|> charlie-tca: the top 2 are clear to me ... only bluez was confusing me [14:48] |tohms|: It may even be that the bluez source package bugs are invalid, since the bug may not need to have been filed against it [14:48] * Elbrus is not allowed. [14:49] could somebody set bug 369383 to wishlist? [14:49] Launchpad bug 369383 in lesstif2 "Please sync lesstif2 0.95.0-2.3 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/369383 [14:51] |tohms|: the hard part is remembering that each source item is a separate package/application that must have its own fix submitted to the package [14:51] <|tohms|> charlie-tca: understand - thx! [14:52] <|tohms|> think it's best i stay at the beginning with bugs in one package :) [14:52] I does get confusing! [14:53] <|tohms|> indeed [14:59] Elbrus: done. [14:59] blueyed: thanks [15:44] What would be an appropriate importancelevel for bug 355155? [15:44] Launchpad bug 355155 in linux "Computer hard locks randomly with ubuntu jaunty" [Undecided,Confirmed] https://launchpad.net/bugs/355155 [15:48] per https://wiki.ubuntu.com/Bugs/Importance if it only affects uncommon configurations or hardware, low. Otherwise, medium [15:53] askand: looks like medium. Might be two or three different bugs, though, mixed together. [15:53] charlie-tca: are you sure? To me it sounds like it has a moderate impact on a large (hard to define large, but hundreds of people are experiencing it) portion of Ubuntu users and some people can not even boot ubuntu, it freeze before GDM, that would make a default Ubuntu installation generally unusable for some users? [15:54] It is far from critical but I would say it qualfies as high? [15:54] * Hobbsee notes that anything that says "randomly happens" effectively has an importance of "low" [15:55] First, some can't boot, some are using -40 kernel, some are not using experimental kernel, that is separate issues [15:55] or "untriaged" [15:55] It's indeed a somewhat messy bugreport [15:56] The only common thing is random freezes. [15:56] askand: what bug ? [15:56] BUGabundo1: bug 355155 [15:56] Launchpad bug 355155 in linux "Computer hard locks randomly with ubuntu jaunty" [Undecided,Confirmed] https://launchpad.net/bugs/355155 [15:56] I had that once [15:57] Is everybody running ext4 file system? [15:57] askand / charlie-tca: are they all using the nvidia binary driver? [15:57] charlie-tca: no, different FS and different videocards [15:57] oh, some ati as well [15:57] No, one confirmed with Nvidia and ATI [15:58] As far as I can see the common denominator is networking [15:58] charlie-tca: I am on ext3 + XFS [15:58] It seems to be related to networking and the freezes does not appear in kernels before Jaunty or after (karmic) [15:58] i'd also say that looks like multiple people reporting the same symptoms for different bugs [15:58] I have nvidia [15:59] It is too early for karmic [15:59] BUGabundo1: are your sound symptoms in jaunty or karmic? [15:59] when I was on jaunty [15:59] let me read the full bug to match [15:59] charlie-tca: Yes, but people have sucessfully stopped the freezes by upgrading to 2.26.30 kernels [15:59] instead of that in Jaunty [16:00] haven't had any on karmic dought [16:00] so upgrading kernel to mainline may help those users [16:00] BUGabundo1: Indeed [16:00] askand: i find it interesting that *none* of those people reference intel video cards, only (mostly) nvidia, and a few ATI. [16:00] askand: which 2.6.30? [16:01] dtchen: I meant that :) [16:01] askand: either way, it'll have to be tracked down furhter before there's any point putting an importance on it, i guess [16:01] askand: and yet the original report was based on Ubuntu 2.6.28-11.40-generic [16:01] askand: err, no, 2.6.30 isn't out. are you talking rc3? rc4? rc5? ... [16:01] Hobbsee: yes, I dont know how it should be tracked down, I told them to attach information such as /var/log/Xorg.0.log, dmesg and lspci -vvnn output and they did [16:02] askand: I don't have the expertise either, sorry [16:02] Looks like it needs to have the bugs separated out, even before it can be triaged [16:02] charlie-tca++ [16:02] There is a thread in the forums, http://ubuntuforums.org/showthread.php?t=1135055 , but it is 21 pages long and also somewhat messy [16:02] well, people tend to just latch onto whatever vague description or comment appears [16:03] Maybe have them use the debugging procedures at https://wiki.ubuntu.com/DebuggingProcedures [16:04] You could request networking debugging and kernel debugging both, maybe [16:04] charlie-tca: Yes, however https://help.ubuntu.com/community/DebuggingSystemCrash is hard to do since Sysrq does not work after a crash and not ssh either [16:05] askand: that can be collected with $ apport-collect -p linux 355155 [16:06] If they have wireless problems, use https://wiki.ubuntu.com/DebuggingNetworkManager [16:06] dtchen: As far as I know there is no chrashing in rc2 and up, and I think there is no crashing in 2.6.29 either [16:06] BUGabundo1: what does apport-collect -p linux 355155 collect? [16:07] gets the information from the crash [16:07] askand: all that you were asking before [16:07] even works after a reboot [16:07] oh ok [16:07] So directly after crash and reboot, run apport-collect -p linux 355155 ? [16:07] askand: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies [16:08] askand: package linux was just one example! [16:08] it can be anyother that you suspect its causing it [16:08] plus it will generate a LOT of bugmail [16:08] and sometimes (bug??) with will not upload all the logs, if that user already sent before [16:10] BUGabundo1: since it is not a problem in kernels earlier or later than 2.26.28, I guess it would be linux? [16:10] Im not sure however [16:11] or rather linux-image-`uname -r` perhaps? [16:12] askand: I would try that. Might get some information that can help narrow it down. [16:13] Kernel bugs are pretty hard to triage sometimes. They can change too much for each kernel minor version [16:16] charlie-tca: there seems to be someone who stopped the crashes by disabling his networkconnection, perhaps it is worth a try to ask people experiencing crashes to do that and see if the crashes continue? [16:16] to try to narrow it down a bit [16:18] askand: I used to see several traces from intel wifi on shutdown [16:18] You can try it. but try to get them all to submit the same reports. Usually if they don't submit the required logs, the bug is going to just get messed up worse [16:18] But there is also airport involved [16:19] Yes, a resetting airport and that is actually kind of what got me to experience the freeze for the first time, my router restarted itself and my computer froze [16:20] BUGabundo1: I see, it indeed looks to be networkrelated (both wifi and cable) [16:22] so I need apport from linux and nm [16:22]

If they have wireless problems, use https://wiki.ubuntu.com/DebuggingNetworkManager [16:23] works for cable connections, too [16:25] tail -n0 -f /var/log/syslog > /tmp/syslog would that work after a crash/reboot too? [16:25] It will be /var/log/syslog.0 [16:26] after the reboot [16:26] I think syslog gets rewritten each boot [16:27] charlie-tca: I've touched that page... 3G is mine eheh [16:27] Don't forget, run apport-collect -p network-manager 355155 [16:27] to get the information it can [16:28] omg I hope no one is subscribed to that bug lol [16:28] hi BUGabundo1 [16:28] ola hggdh [16:29] BUGabundo1, you said earlier on today you had found/resolved my sound issue? [16:30] uhh hggdh I killed PA and on autospawn it worked (for me) [16:30] need to do that with recent upgrades [16:31] on jaunty? [16:31] kk [16:31] dtchen: on boot sound is muted [16:31] on jaunty? [16:31] karmic dtchen [16:32] kk = karmic koala [16:32] sorry to be a pain, but please be very specific. i'm tracing several sets of symptoms, and it really does matter which release is used. [16:32] dtchen: I understand... for future references I am running karmic [16:33] dtchen: 6h ago here I stated that, if you check the log [16:33] well, just to save my sanity (and because my memory is awful), please just mention it whenever you bring it up [16:33] Is there a way to split a bugreport or do one create a new one? [16:33] askand: create a new one; reference it in the old [16:34] dtchen: will do. unless my bad memory fails on me [16:34] askand: unforn NO === jussi01 is now known as tuhina [17:02] hi everyone [17:02] BUGabundo1, you just pusleaudio --kill > [17:02] ? [17:02] killall pulseaudio [17:02] then just allow it to autospawn [17:02] e.g., speaker-test -c2 [17:02] dtchen, thanks, will try it now [17:03] bloody hell, it seems to work! [17:04] back [17:04] anyone was talking to me? [17:04] hggdh: pulseaudio -k [17:04] yes, I was asking how to do it, but Daniel told me [17:04] and it worked -- or so it seems [17:05] dtchen: I have no sound at this moment (using karmic) [17:05] hggdh: give me back my audio... you stole it from me :) [17:05] :-) [17:05] but padevchooser still fails to run [17:06] wokring here [17:06] but no sound [17:06] let me check alsamixer [17:06] padevchooser has avahi bits [17:07] if avahi detects that your nameserver is serving .local, it will barf [17:07] ahh and I have that ON [17:07] thus, padevchooser will refuse to start [17:07] that would explain why it died this morning [17:07] oh [17:07] dtchen: oh and pavu has a new tab "configuration" where I chose other then analogo [17:08] BUGabundo1: yes, the new pavucontrol is much improved [17:08] after I reset it, PA didn't work again until reboot [17:08] improved == not working ? [17:08] lol [17:08] it works for me [17:08] change to digital while audio plays, and back to analog [17:08] ehhe [17:09] dtchen: I have an Playback stream [17:10] ohh wait [17:10] it was set to digital.... [17:10] that would explain why no audio [17:10] hggdh: next time check that last tab [17:10] meanwhile I will see what I have on NS, and if avahi tells me something [17:10] BUGabundo1, will do [17:12] dtchen: pavu control says link lib 9.15 and complied 9.14. is this good ? [17:13] hggdh: sudo rm -f /var/run/avahi-daemon/disabled-for-unicast-local, sudo service avahi-daemon restart [17:16] dtchen: pavu control says link lib 9.15 and complied 9.14. is this good ? [17:17] dtchen, the default conf for avahi comes with domain=local... I changed it, and restarted the beast [17:17] hggdh: actually, the recommended procedure is in the jaunty release notes [17:18] hggdh: sudo sed -i -e'/AVAHI_DAEMON_DETECT_LOCAL/s/1/0/' /etc/default/avahi-daemon && sudo service avahi-daemon restart [17:18] BUGabundo1: should be ok, but we can force a no-change rebuild if crashers appear [17:19] ok dtchen [17:22] dtchen: ping [17:23] will restart X... padevchooser does not return a browser error anymore, but hangs [17:24] dtchen: i dtchen i have a laptop Qosmio F50 and i use ubuntu jaunty. My subwoofer doesnt work. [17:24] i use HDA intel alsa mixer [17:25] hggdh: where does it hang+ [17:25] dtchen: so what I need to restart to have sound again? [17:25] s/\+/\?/ [17:26] BUGabundo1: reselect the analog device in pavucontrol? [17:26] its already [17:26] but let me check [17:26] BUGabundo1: of course the drastic route is to nuke ~/.pulse* and logging back in [17:27] migbuntu: bug report #? [17:27] dtchen, at startup (it seems. No window is displayed). I can install the debug packages, and gdb it, if you want [17:27] dtchen, this is on kk [17:27] dtchen: sinks are on default, and Profile is at output analog+input analog [17:27] hggdh: padevchooser goes to the notification area [17:27] hggdh: or are you saying it doesn't even do that? [17:28] dtchen, I am saying I am dumb... ;-( [17:28] dtchen: nuking .pulse [17:28] what are the bugs in 9.04 can someone give me the link for it ? [17:29] G__81: that would be a gigantic list [17:29] very sorry. I will take the next few seconds and try to drink a cup of water, and check that I indeed get the cup to my mouth. [17:29] G__81: the milestones? [17:29] hggdh: np ;) [17:29] no i am intereted in triaging and fixing bugs so hence let me do some triaging and some fix too [17:30] so want the list of bugs for 9.04 [17:30] G__81: then fix the ones for karmic and backport [17:30] just open launchpad and see the list [17:30] !bugs [17:30] If you find a bug in Ubuntu or any of its derivatives, please file a bug report at: http://bugs.launchpad.net/ubuntu - Bugs in/wishes for the bots can be filed at http://launchpad.net/ubuntu-bots [17:31] g_81, https://launchpad.net/ubuntu, and then search for 9.04 or jaunty, etc. It is difficult to say which bug is from which version (reporters not always state that, they may state but be wrong, etc) [17:31] humm is it me or lp is not opening ? [17:31] Bugabundo1: you... [17:32] hggdh: he can see the milestones for examle [17:32] yeah i understand [17:32] bcurtiswx: me [17:32] hi hggdh [17:32] G__81: https://bugs.edge.launchpad.net/ubuntu/jaunty/+bugs [17:32] there you go [17:32] BUGabundo1, not a good idea -- milestone setting should be done by people with a good understanding of impacts [17:32] but KK is better https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs [17:32] ah ok [17:33] I have no knolage of what G__81 knows about coding [17:33] he said he *wanted to fix* [17:33] BUGabundo1, yes i will try to fix it i ve quite some experience with coding but not done any packaging stuff at all [17:34] migbuntu: pong, did you reply to my question here? [17:34] G__81: welcome [17:34] dtchen: migbuntu is uploding the but to lp [17:34] so you have the alsa.sh [17:34] from apport alsa-base [17:35] slow typer eheh [17:36] uhhhh dtchen: sound just came back on its own! . [17:37] dtchen: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/374166 [17:37] Launchpad bug 374166 in alsa-driver "HDA intel integrated subwoofer doesnt work" [Undecided,New] [17:37] oh, i thought you had already commented on a bug [17:38] G__81, just start at launchpad; a good reference is http://wiki.ubuntu.com/HelpingWithBugs [17:38] dtchen: its new [17:38] LOL [17:38] bug 371048 [17:38] Launchpad bug 371048 in linux "Subwoofer doesn't work with HDA-Intel" [Undecided,Incomplete] https://launchpad.net/bugs/371048 [17:39] but how are bugs generally re produced and fixed here do you all test it in VM or is there some other way ? [17:39] maybe a dupe [17:39] G__81: each user/dev has its ways [17:39] I'm an alpha tester and run on my own laptop cutting edge and kvm [17:40] but whats the easy way of setting up an environment [17:40] G__81: depends on the bug! [17:40] G__81, any way you can get it done is good enough. Of course, being able to run as near to the reporter's version is better, so having other test systems (or VMs) is a good idea [17:41]