[00:59] <thewrath> where can i find what all the bug status' mean
[01:08] <Ryan52> thewrath: the wiki.
[01:09] <Ryan52> thewrath: https://wiki.ubuntu.com/Bugs/Status
[01:09] <thewrath> found it all ready
[01:09] <thewrath> thank you thoughs ir
[01:10] <thewrath> was trying to find what bug 220006 and bug 305907 meant
[02:08] <dtchen> thewrath: 220006 updated
[02:08] <dtchen> thanks
[02:08] <thewrath> dtchen: thanks
[02:10] <thewrath> dtchen: r u thanking me
[02:10] <thewrath> what is that, try model=medion?
[02:11] <dtchen> that's the proper quirk for that SSID
[02:12] <thewrath> 220006 is the sound issue
[02:13] <dtchen> thewrath: yes, i know. i asked for additional information.
[02:13] <thewrath> oh ok
[02:13] <thewrath> hwere i dont see ur comment
[02:14] <dtchen> you just mentioned it
[02:14] <thewrath> model=medion ?
[02:15] <thewrath> where do i put htat?
[02:15] <dtchen> thewrath: echo options snd-hda-intel model=medion|sudo tee -a /etc/modprobe.d/test.conf
[02:15] <thewrath> i will post that in the am
[02:16] <dtchen> you will need to reboot
[02:16] <thewrath> after i do that?
[02:17] <dtchen> yes, after the echo..test.conf bit, reboot
[02:17] <thewrath> k
[02:17] <thewrath> and see if i got audio at that point?
[02:18] <dtchen> after you reboot, yes
[02:19] <thewrath> then i will post
[02:19] <thewrath> i am goign to go lay down before bed
[02:19] <thewrath> i will post
[02:19] <dtchen> i'm going by Snowball2050's alsa-info.sh output, however.
[02:19] <thewrath> dtchen: look for a response before 12p EST tomorrow
[02:19] <dtchen> you didn't provide yours, so i don't know if it's identical
[02:19] <thewrath> what if that doesnt work how do i get it back
[02:20] <dtchen> rm /etc/modprobe.d/test.conf
[02:20] <thewrath> my sound comes through headphoens only not comptuer speakers is my issue
[02:20] <dtchen> you really should download http://www.alsa-project/alsa-info.sh and run it
[02:20] <thewrath> is that the asme issue
[02:21] <thewrath> i did hold on i posted it somewhere
[02:21] <dtchen> err, you used an older kernel
[02:21] <thewrath> ?
[02:21] <dtchen> and your model isn't correct
[02:22] <dtchen> you should *not* use model=medion
[02:22] <dtchen> let me look
[02:22] <thewrath> k
[02:22] <thewrath> you see where i posted it
[02:22] <dtchen> it's an older one, and i need an updated one
[02:22] <thewrath> can you link me where you see my post
[02:22] <dtchen> i.e., boot into Jaunty Beta
[02:22] <thewrath> i need to go to bed
[02:22] <thewrath> or i would do that
[02:23] <dtchen> it's comment 10
[02:23] <thewrath> on what page
[02:23] <dtchen> well, catch me about this time tomorrow
[02:23] <thewrath> k
[02:23] <dtchen> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/220006/comments/10
[02:23] <thewrath> that is not mine
[02:24] <thewrath> i am known as m. brown on launchpad
[02:24] <dtchen> err, which one is yours?
[02:24] <dtchen> ugh, please be clear about which bug report is yours
[02:24] <thewrath> i never said which one was mine
[02:24] <dtchen> hence the confusion
[02:24] <thewrath> i was told that bug was the one i was expericning
[02:24] <thewrath> can i see my contribbutions
[02:25] <dtchen> i cannot further diagnose your issue unless you run the alsa-info.sh
[02:25] <thewrath> k
[02:25] <thewrath> i will tomorrow morning
[02:25] <dtchen> or link me to your bug report
[02:25] <thewrath> is ur name usually in here and u just afk
[02:25] <dtchen> yes, i'm generally at work
[02:25] <thewrath> k
[02:25] <thewrath> i will send you a pm with the link of it
[02:25] <dtchen> i won't respond during USA business hours (EDT)
[02:26] <thewrath> that is fine i undrestand
[02:26] <thewrath> is that .com or what
[02:26] <dtchen> sorry?
[02:26] <thewrath> its .org
[02:26] <thewrath> the website
[02:26] <thewrath> didnt have a TLd
[02:26] <thewrath> but i got to go to bed
[02:26] <thewrath> ttyl
[05:48] <dholbach> good morning
[06:50] <YoBoY> good morning
[07:28] <YoBoY> strange i found a bug ( bug 112165 ) reported on a package i can't find on my system ¬_¬"
[07:31] <wgrant> YoBoY: That's because it's the wrong package.
[07:31] <wgrant> Binaries for that package doesn't exist in Ubuntu.
[07:31] <wgrant> (it's m68k and mips only)
[07:31] <YoBoY> hum... ok
[07:31] <wgrant> YoBoY: The correct package is likely to be ubiquity.
[07:33] <YoBoY> don't know if the correct package is ubiquity or not, the bug is old and miss informations to identify this
[07:33] <wgrant> It is certainly about ubiquity, but it may be a bug in something further down the stack.
[07:33] <wgrant> Assign it to ubiquity for now.
[07:34] <wgrant> That is certainly more correct than partitioner.
[07:36] <YoBoY> ok, i reassign to ubiquity and see if there is no duplicates
[07:36] <YoBoY> tanks
[09:24] <BUGabundo> guud morning
[09:29] <thekorn> hello BUGabundo
[09:29] <BUGabundo> hey thekorn
[12:28] <BUGabundo> where would this bug be: when I get 'some' updates, services that were off, are restart (stuff like bluetooth, samba, apache, mysql)
[12:29] <BUGabundo> if I had them turned off, why would the installer restart ??
[12:32] <ogra> depends how you turned them off
[12:34] <BUGabundo> on defauls
[12:34] <ogra> ??
[12:34] <BUGabundo> or using GUI Services
[12:34] <ogra> what did you do to turn them off
[12:35] <BUGabundo> ogra: most of them via Services on System-Admin
[12:35] <ogra> if you used the gui tool thats a bug, it should properly move the S links to K links in rcX.d ...if you simply remove symlinks manually that *doesnt* turn off anything in a persistent manner
[12:36] <ogra> the latter is expected behavior and properly documented in update-rc.d
[12:37] <BUGabundo> I don't remove links manually from /etc/RC
[12:38] <ogra> well, then thats likely a bug in how the gui handles it
[12:41] <BUGabundo> ok
[12:41] <BUGabundo> will need someone to confirm it
[12:41] <BUGabundo> it "always" happened to me
[13:02] <e-jat> may i know y http://paste.ubuntu.com/138930/ <-- happened ?
[13:02]  * BUGabundo blames every bug today on python
[13:04] <e-jat> :(
[13:12] <liw> could someone mark 349336 as "triaged"? bug launchpad priviledges don't allow that (I'm the developer of computer-janitor, and I think it's triaged by now)
[13:13] <thekorn> bug 349336
[13:14] <thekorn> liw, done
[13:14] <liw> thekorn, thanks
[13:34] <thewrath> can anyone comment on 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
[13:34] <thewrath> supporint ALSA
[13:48] <thewrath> hey all
[13:48] <thewrath> whos all in here that starts with d
[14:01] <thekorn> boo
[14:02] <bddebian> Boo too :)
[14:18] <BUGabundo> Foo
[14:27] <thewrath> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/332479
[14:27] <thewrath> the first two comments on 3-18-09
[14:27] <thewrath> how do i implement the fix
[14:59] <marctww> ah here it is!
[14:59] <marctww> the channel i was looking for!
[14:59] <marctww> Anyone here have experience with what looks like a redraw-bug with nvidia-177.82 driver in Ubuntu 8.10?
[15:17] <Ampelbein> marctww: bug #269904 propably? but its fixed in intrepid.
[15:20] <marctww> its ubuntu 8.10 Ampelbein
[15:20] <marctww> what do you mean fixed?
[15:22] <Ampelbein> marctww: yeah, ubuntu 8.10 = intrepid ibex
[15:22] <marctww> its not fixed then
[15:22] <marctww> im having it with ubuntnu 8.10
[15:22] <marctww> how can that be?
[15:25] <Ampelbein> look at the bugreport, perhaps you have to enable some options or another driver.
[15:31] <marctww> Ampelbein: that looks like my problem
[15:31] <marctww> thanks alot
[15:33] <james_w> go go pedro_!
[15:34] <pedro_> james_w: ah?
[15:34] <james_w> all the duplicates of the python problem you've been adding
[15:35] <pedro_> james_w: ah yes I'm checking the list of new bugs every a few minutes to catch those ;-)
[15:35]  * BUGabundo cought all those spam mail cought
[15:35] <BUGabundo> :)
[15:35] <pedro_> isn't too bad yet
[15:36]  * pedro_ stills remember the crash on exit of the mono related apps
[15:37] <pedro_> that was horrible
[15:38] <BUGabundo> or gutsy glib6
[15:38] <BUGabundo> or hardy kernel fixed at last min before build
[15:38] <BUGabundo> or e1000e
[15:38] <BUGabundo> I guess we have at least on critical bug before RC on every cycle
[15:40] <hggdh> interesting. After rebooting with latest kernel, I cannot connect through my wireless (using b43)
[15:42] <BUGabundo> hggdh: drop kernel backport ?
[15:43] <hggdh> BUGabundo, well, it was a standard synaptic update. I am now looking a the logs
[15:45] <hggdh> I am going to reboot, and check
[15:49] <BUGabundo> dholbach: ping. pvt please
[15:51] <hggdh> go figure. A second reboot after the kernel update made wireless work again
[15:51] <BUGabundo> oops?
[15:52] <hggdh> did not see any logged...
[15:53] <hggdh> the error was reported on <gasp> NetworkManager...
[15:54] <hggdh> heh. But now auto-eth0 failed on N-M...
[16:09] <mcas> hi
[16:10] <BUGabundo> mcas: hey
[16:11] <mcas> i need some help with my own bug
[16:11] <mcas> https://bugs.launchpad.net/bugs/349173
[16:11] <mcas> i 've seen that this is partly related to another bug
[16:12] <mcas> https://bugs.launchpad.net/bugs/346589
[16:12] <mcas> this one
[16:12] <mcas> i didn't know this message is a bug, too
[16:13] <mcas> so the only question is, if the second dialog i see the wrong button label is in english wrong, too
[17:17] <bromic94> hey all
[17:44] <bcurtiswx> dtchen: are you present?
[17:45] <BUGabundo> bcurtiswx: too soon for Dan
[17:45] <BUGabundo> try in an hour or 2
[17:45] <bcurtiswx> BUGabondo: lol aww.. ok :P
[17:45] <bcurtiswx> i was gonna tell him i found the answer to my crackling problems
[18:07] <charlie-tca> hggdh: yes
[18:11] <hggdh> charlie-tca, thank you
[18:11] <charlie-tca> no problem.
[18:12]  * hggdh finally decided to get out of the closet ;-)
[20:13] <dtchen> bcurtiswx: ok
[20:15] <bcurtiswx> dtchen: thanks for the help though.  much appreciated
[20:15] <dtchen> bcurtiswx: keep in mind that to prevent regressions from previous Ubuntu releases, pulseaudio will always honour ~/.asoundrc for native alsa apps. it was an intentional SRU for 8.10, so i of course can't prevent people from hanging themselves.
[20:15] <bcurtiswx> dtchen: it helps us bug reporters for jaunty sound issues to ask if that file was altered at all
[20:16] <dtchen> that file should not exist in a fresh install
[20:16] <bcurtiswx> dtchen: is there any way to revert that to default (in the case users don't remember what they changed) ?
[20:16] <dtchen> it is only created by hand or by explicitly running (a frontend to) asoundconf
[20:17] <dtchen> alsa-info.sh will print ~/.asoundrc and /etc/asound.conf
[20:17] <dtchen> that's why i always ask for alsa-info.sh output regardless
[20:18] <bcurtiswx> dtchen: is it bad practice to have users rename those files temporarily and restart pulse to see if the problems still exist?
[20:18] <dtchen> no, that's perfectly valid
[20:18] <dtchen> and one doesn't need to restart pulseaudio; simply killing pulseaudio will suffice due to autospawn
[20:19] <bcurtiswx> dtchen: ok
[20:19] <dtchen> although, to be frank, killing pulseaudio is a red herring
[20:19] <dtchen> you need do nothing to pulseaudio itself. it's native alsa apps that are concerned with ~/.asoundrc. pulseaudio ignores it.
[20:22] <dtchen> i.e., anything configured to use alsa directly (via plug or default or whatever one has defined in ~/.asoundrc) would exhibit such symptoms
[20:22] <bcurtiswx> bdmurray: i think this is important information for triagers (because i imagine lots of sound issue bugs will pop up), whats the best way to spread this to all the triagers?
[20:22] <dtchen> "run alsa-info.sh"
[20:22] <dtchen> that's the one best way to get everything i need
[20:23] <bcurtiswx> dtchen: yup, thats in the sound debugging section of debugging proceedures.. im talking about reading that and noticing old entires in those files (to have them rename the file and have user kill to restart)
[20:24] <dtchen> unfortunately it can't be a cookie-cutter recipe
[20:24] <dtchen> your issue is quite specific to your perices use case *and* HDA codec
[20:24] <dtchen> precise*
[20:24] <dtchen> sheesh, lag over 3G is horrendous
[20:24] <bcurtiswx> yup, undetstood
[20:24] <bcurtiswx> understood*
[20:36] <the99zChris> can anyone help me? i restored my xorg file (didn't help original problem) but now i can't set my screen resolution low enough to play games...(hardy
[20:37] <dtchen> i think you misdirected ; that's really more appropriately in #ubuntu
[20:37] <the99zChris> i know sorry, no help there after 30 minutes of trying
[20:44] <BUGabundo> apw: this is what im getting from kernel oops on every boot or resume http://paste.ubuntu.com/139185/
[20:44] <BUGabundo> it mentions dtchen code too
[20:53] <dtchen> BUGabundo: cat /proc/version_signature
[20:54] <BUGabundo> Ubuntu 2.6.28-11.38-generic
[20:54] <dtchen> hmm, i'm pretty sure you still have vestiges of my kernel somewhere
[20:54] <dtchen> there's no way -11.38 could have my schroot build path
[20:55] <dtchen> right
[20:55] <dtchen> see line 6
[20:55] <dtchen> try blowing away your initramfs and creating it from scratch
[20:56] <dtchen> (you'll need to reboot, of course)
[20:59] <BUGabundo1> dtchen: sorry
[20:59] <BUGabundo1> system froze right after I echoed that
[20:59] <dtchen> 13:54 < BUGabundo> Ubuntu 2.6.28-11.38-generic
[20:59] <dtchen> 13:54 < dtchen> hmm, i'm pretty sure you still have vestiges of my kernel somewhere
[20:59] <dtchen> 13:54 < dtchen> there's no way -11.38 could have my schroot build path
[20:59] <dtchen> 13:55 < dtchen> right
[20:59] <dtchen> 13:55 < dtchen> see line 6
[20:59] <dtchen> 13:55 < dtchen> try blowing away your initramfs and creating it from scratch
[21:00] <dtchen> 13:56 < dtchen> (you'll need to reboot, of course)
[21:00] <BUGabundo1> ok did the last part agaist my will
[21:00] <BUGabundo1> LOL
[21:00] <BUGabundo1> it just fired again, and I had /var/crash clean!
[21:00] <BUGabundo1> dtchen: how can I redo initrams?
[21:02] <dtchen> update-initramfs -d ; update-initramfs -c (or just reinstall the current linux-image-2.6.28-11-generic)
[21:04] <BUGabundo1> reinstalling now
[21:06] <BUGabundo1> dtchen: done!
[21:06] <dtchen> BUGabundo1: if you reinstall, you still need to have removed the existing initramfses
[21:06] <BUGabundo1> I deleted them before reinstaling
[21:07] <BUGabundo1> update-initramfs: Deleting /boot/initrd.img-2.6.28-11-generic
[21:07] <BUGabundo1> update-initramfs: Deleting /boot/initrd.img-2.6.28-10-generic
[21:07] <BUGabundo1> update-initramfs: Deleting /boot/initrd.img-2.6.27-7-generic
[21:07] <dtchen> ok, make sure you regenerate initramfses for kernels you wish to boot
[21:07] <dtchen> ^^^^^^
[21:08] <BUGabundo1> doesn't re-installing do that?
[21:08] <dtchen> only for the currently installing one.
[21:08] <BUGabundo1> its the only one I need...
[21:08] <dtchen> well, you have been warned.
[21:09] <BUGabundo1> don't know why I still had 27-7 around
[21:09] <BUGabundo1> lol
[21:09] <BUGabundo1> dtchen: if anything fails, I'll boot from usb, and chroot
[21:09] <BUGabundo1> to fix