/srv/irclogs.ubuntu.com/2009/03/27/#ubuntu-bugs.txt

=== d-b_ is now known as d-b
=== scott_ev_ is now known as scott_ev
thewrathwhere can i find what all the bug status' mean00:59
Ryan52thewrath: the wiki.01:08
Ryan52thewrath: https://wiki.ubuntu.com/Bugs/Status01:09
thewrathfound it all ready01:09
thewraththank you thoughs ir01:09
thewrathwas trying to find what bug 220006 and bug 305907 meant01:10
ubottuLaunchpad bug 220006 in linux "Sound Card Detected, but only headphone sound" [Medium,Triaged] https://launchpad.net/bugs/22000601:10
ubottuLaunchpad bug 305907 in linux-restricted-modules "Complete system freeze when trying to connect to WPA2 network" [Medium,Fix committed] https://launchpad.net/bugs/30590701:10
dtchenthewrath: 220006 updated02:08
dtchenthanks02:08
thewrathdtchen: thanks02:08
thewrathdtchen: r u thanking me02:10
thewrathwhat is that, try model=medion?02:10
dtchenthat's the proper quirk for that SSID02:11
thewrath220006 is the sound issue02:12
dtchenthewrath: yes, i know. i asked for additional information.02:13
thewrathoh ok02:13
thewrathhwere i dont see ur comment02:13
dtchenyou just mentioned it02:14
thewrathmodel=medion ?02:14
thewrathwhere do i put htat?02:15
dtchenthewrath: echo options snd-hda-intel model=medion|sudo tee -a /etc/modprobe.d/test.conf02:15
thewrathi will post that in the am02:15
dtchenyou will need to reboot02:16
thewrathafter i do that?02:16
dtchenyes, after the echo..test.conf bit, reboot02:17
thewrathk02:17
thewrathand see if i got audio at that point?02:17
dtchenafter you reboot, yes02:18
thewraththen i will post02:19
thewrathi am goign to go lay down before bed02:19
thewrathi will post02:19
dtcheni'm going by Snowball2050's alsa-info.sh output, however.02:19
thewrathdtchen: look for a response before 12p EST tomorrow02:19
dtchenyou didn't provide yours, so i don't know if it's identical02:19
thewrathwhat if that doesnt work how do i get it back02:19
dtchenrm /etc/modprobe.d/test.conf02:20
thewrathmy sound comes through headphoens only not comptuer speakers is my issue02:20
dtchenyou really should download http://www.alsa-project/alsa-info.sh and run it02:20
thewrathis that the asme issue02:20
thewrathi did hold on i posted it somewhere02:21
dtchenerr, you used an older kernel02:21
thewrath?02:21
dtchenand your model isn't correct02:21
dtchenyou should *not* use model=medion02:22
dtchenlet me look02:22
thewrathk02:22
thewrathyou see where i posted it02:22
dtchenit's an older one, and i need an updated one02:22
thewrathcan you link me where you see my post02:22
dtcheni.e., boot into Jaunty Beta02:22
thewrathi need to go to bed02:22
thewrathor i would do that02:22
dtchenit's comment 1002:23
thewrathon what page02:23
dtchenwell, catch me about this time tomorrow02:23
thewrathk02:23
dtchenhttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/220006/comments/1002:23
ubottuUbuntu bug 220006 in linux "Sound Card Detected, but only headphone sound" [Medium,Triaged]02:23
thewraththat is not mine02:23
thewrathi am known as m. brown on launchpad02:24
dtchenerr, which one is yours?02:24
dtchenugh, please be clear about which bug report is yours02:24
thewrathi never said which one was mine02:24
dtchenhence the confusion02:24
thewrathi was told that bug was the one i was expericning02:24
thewrathcan i see my contribbutions02:24
dtcheni cannot further diagnose your issue unless you run the alsa-info.sh02:25
thewrathk02:25
thewrathi will tomorrow morning02:25
dtchenor link me to your bug report02:25
thewrathis ur name usually in here and u just afk02:25
dtchenyes, i'm generally at work02:25
thewrathk02:25
thewrathi will send you a pm with the link of it02:25
dtcheni won't respond during USA business hours (EDT)02:25
thewraththat is fine i undrestand02:26
thewrathis that .com or what02:26
dtchensorry?02:26
thewrathits .org02:26
thewraththe website02:26
thewrathdidnt have a TLd02:26
thewrathbut i got to go to bed02:26
thewrathttyl02:26
=== jmarsden_ is now known as jmarsden
dholbachgood morning05:48
YoBoYgood morning06:50
YoBoYstrange i found a bug ( bug 112165 ) reported on a package i can't find on my system ¬_¬"07:28
ubottuLaunchpad bug 112165 in partitioner "Partitioner fails installing from Live CD on AMD64" [Undecided,New] https://launchpad.net/bugs/11216507:28
wgrantYoBoY: That's because it's the wrong package.07:31
wgrantBinaries for that package doesn't exist in Ubuntu.07:31
wgrant(it's m68k and mips only)07:31
YoBoYhum... ok07:31
wgrantYoBoY: The correct package is likely to be ubiquity.07:31
YoBoYdon't know if the correct package is ubiquity or not, the bug is old and miss informations to identify this07:33
wgrantIt is certainly about ubiquity, but it may be a bug in something further down the stack.07:33
wgrantAssign it to ubiquity for now.07:33
wgrantThat is certainly more correct than partitioner.07:34
YoBoYok, i reassign to ubiquity and see if there is no duplicates07:36
YoBoYtanks07:36
=== thekorn_ is now known as thekorn
BUGabundoguud morning09:24
thekornhello BUGabundo09:29
BUGabundohey thekorn09:29
=== a|wen_ is now known as a|wen
=== d-b_ is now known as d-b
BUGabundowhere would this bug be: when I get 'some' updates, services that were off, are restart (stuff like bluetooth, samba, apache, mysql)12:28
BUGabundoif I had them turned off, why would the installer restart ??12:29
ogradepends how you turned them off12:32
BUGabundoon defauls12:34
ogra??12:34
BUGabundoor using GUI Services12:34
ograwhat did you do to turn them off12:34
BUGabundoogra: most of them via Services on System-Admin12:35
ograif 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 manner12:35
ograthe latter is expected behavior and properly documented in update-rc.d12:36
BUGabundoI don't remove links manually from /etc/RC12:37
ograwell, then thats likely a bug in how the gui handles it12:38
BUGabundook12:41
BUGabundowill need someone to confirm it12:41
BUGabundoit "always" happened to me12:41
e-jatmay i know y http://paste.ubuntu.com/138930/ <-- happened ?13:02
* BUGabundo blames every bug today on python13:02
e-jat:(13:04
=== thunderstruck is now known as gnomefreak
liwcould 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:12
thekornbug 34933613:13
ubottuLaunchpad bug 349336 in computer-janitor "Ambiguous wording in confirmation alert box" [Undecided,Confirmed] https://launchpad.net/bugs/34933613:13
thekornliw, done13:14
liwthekorn, thanks13:14
thewrathcan anyone comment on 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)13:34
thewrathsupporint ALSA13:34
=== thunderstruck is now known as gnomefreak
=== bromic94 is now known as thewrath
thewrathhey all13:48
thewrathwhos all in here that starts with d13:48
thekornboo14:01
bddebianBoo too :)14:02
BUGabundoFoo14:18
thewrathhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/33247914:27
ubottuUbuntu bug 332479 in linux "[jaunty] [regression] - sound does not work {hp hdx18-1080eg} {HDA Intel}" [Medium,Confirmed]14:27
thewraththe first two comments on 3-18-0914:27
thewrathhow do i implement the fix14:27
marctwwah here it is!14:59
marctwwthe channel i was looking for!14:59
marctwwAnyone here have experience with what looks like a redraw-bug with nvidia-177.82 driver in Ubuntu 8.10?14:59
Ampelbeinmarctww: bug #269904 propably? but its fixed in intrepid.15:17
ubottuLaunchpad bug 269904 in nvidia-graphics-drivers-180 "Screen refresh problems with nvidia on intrepid" [Undecided,Confirmed] https://launchpad.net/bugs/26990415:17
marctwwits ubuntu 8.10 Ampelbein15:20
marctwwwhat do you mean fixed?15:20
Ampelbeinmarctww: yeah, ubuntu 8.10 = intrepid ibex15:22
marctwwits not fixed then15:22
marctwwim having it with ubuntnu 8.1015:22
marctwwhow can that be?15:22
Ampelbeinlook at the bugreport, perhaps you have to enable some options or another driver.15:25
marctwwAmpelbein: that looks like my problem15:31
marctwwthanks alot15:31
james_wgo go pedro_!15:33
pedro_james_w: ah?15:34
james_wall the duplicates of the python problem you've been adding15:34
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 cought15:35
BUGabundo:)15:35
pedro_isn't too bad yet15:35
* pedro_ stills remember the crash on exit of the mono related apps15:36
pedro_that was horrible15:37
BUGabundoor gutsy glib615:38
BUGabundoor hardy kernel fixed at last min before build15:38
BUGabundoor e1000e15:38
BUGabundoI guess we have at least on critical bug before RC on every cycle15:38
hggdhinteresting. After rebooting with latest kernel, I cannot connect through my wireless (using b43)15:40
BUGabundohggdh: drop kernel backport ?15:42
hggdhBUGabundo, well, it was a standard synaptic update. I am now looking a the logs15:43
hggdhI am going to reboot, and check15:45
BUGabundodholbach: ping. pvt please15:49
hggdhgo figure. A second reboot after the kernel update made wireless work again15:51
BUGabundooops?15:51
hggdhdid not see any logged...15:52
hggdhthe error was reported on <gasp> NetworkManager...15:53
hggdhheh. But now auto-eth0 failed on N-M...15:54
mcashi16:09
BUGabundomcas: hey16:10
mcasi need some help with my own bug16:11
mcashttps://bugs.launchpad.net/bugs/34917316:11
ubottuUbuntu bug 349173 in ubiquity "wrong german translation of buttons in ubiquity" [Undecided,Confirmed]16:11
=== jtisme is now known as jtholmes
mcasi 've seen that this is partly related to another bug16:11
mcashttps://bugs.launchpad.net/bugs/34658916:12
ubottuUbuntu bug 346589 in ubiquity "[Jaunty] Misleading information when installing with mounted partitions" [High,Fix committed]16:12
mcasthis one16:12
mcasi didn't know this message is a bug, too16:12
mcasso the only question is, if the second dialog i see the wrong button label is in english wrong, too16:13
=== jtholmes is now known as jtisme
=== jtisme is now known as jtholmes
=== jtholmes is now known as jtisme
=== jtisme is now known as jtholmes
=== jtholmes is now known as jtjr
=== jtjr is now known as jtholmes
=== jtholmes is now known as jtjr
=== jtjr is now known as jtholmes
=== jtholmes is now known as jthII
=== jthII is now known as jtholmes
=== jtholmes is now known as jtisme
=== jtisme is now known as jtholmes
=== jtholmes is now known as jtisme
=== jtisme is now known as jtholmes
=== jtholmes is now known as jtisme
=== jtisme is now known as jtholmes
=== jtholmes is now known as jth2
=== jth2 is now known as jtisme
=== jtisme is now known as jtholmes
=== fader_ is now known as fader|lunch
bromic94hey all17:17
=== bromic94 is now known as thewrath
bcurtiswxdtchen: are you present?17:44
BUGabundobcurtiswx: too soon for Dan17:45
BUGabundotry in an hour or 217:45
bcurtiswxBUGabondo: lol aww.. ok :P17:45
bcurtiswxi was gonna tell him i found the answer to my crackling problems17:45
=== fader|lunch is now known as fader_
charlie-tcahggdh: yes18:07
hggdhcharlie-tca, thank you18:11
charlie-tcano problem.18:11
* hggdh finally decided to get out of the closet ;-)18:12
=== yofel_ is now known as yofel
=== jtholmes is now known as jtisme
dtchenbcurtiswx: ok20:13
bcurtiswxdtchen: thanks for the help though.  much appreciated20:15
dtchenbcurtiswx: 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
bcurtiswxdtchen: it helps us bug reporters for jaunty sound issues to ask if that file was altered at all20:15
dtchenthat file should not exist in a fresh install20:16
bcurtiswxdtchen: is there any way to revert that to default (in the case users don't remember what they changed) ?20:16
dtchenit is only created by hand or by explicitly running (a frontend to) asoundconf20:16
dtchenalsa-info.sh will print ~/.asoundrc and /etc/asound.conf20:17
dtchenthat's why i always ask for alsa-info.sh output regardless20:17
bcurtiswxdtchen: is it bad practice to have users rename those files temporarily and restart pulse to see if the problems still exist?20:18
dtchenno, that's perfectly valid20:18
dtchenand one doesn't need to restart pulseaudio; simply killing pulseaudio will suffice due to autospawn20:18
bcurtiswxdtchen: ok20:19
dtchenalthough, to be frank, killing pulseaudio is a red herring20:19
dtchenyou need do nothing to pulseaudio itself. it's native alsa apps that are concerned with ~/.asoundrc. pulseaudio ignores it.20:19
dtcheni.e., anything configured to use alsa directly (via plug or default or whatever one has defined in ~/.asoundrc) would exhibit such symptoms20:22
bcurtiswxbdmurray: 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
dtchenthat's the one best way to get everything i need20:22
bcurtiswxdtchen: 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:23
dtchenunfortunately it can't be a cookie-cutter recipe20:24
dtchenyour issue is quite specific to your perices use case *and* HDA codec20:24
dtchenprecise*20:24
dtchensheesh, lag over 3G is horrendous20:24
bcurtiswxyup, undetstood20:24
bcurtiswxunderstood*20:24
the99zChriscan 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...(hardy20:36
dtcheni think you misdirected ; that's really more appropriately in #ubuntu20:37
the99zChrisi know sorry, no help there after 30 minutes of trying20:37
BUGabundoapw: this is what im getting from kernel oops on every boot or resume http://paste.ubuntu.com/139185/20:44
BUGabundoit mentions dtchen code too20:44
dtchenBUGabundo: cat /proc/version_signature20:53
BUGabundoUbuntu 2.6.28-11.38-generic20:54
dtchenhmm, i'm pretty sure you still have vestiges of my kernel somewhere20:54
dtchenthere's no way -11.38 could have my schroot build path20:54
dtchenright20:55
dtchensee line 620:55
dtchentry blowing away your initramfs and creating it from scratch20:55
dtchen(you'll need to reboot, of course)20:56
BUGabundo1dtchen: sorry20:59
BUGabundo1system froze right after I echoed that20:59
dtchen13:54 < BUGabundo> Ubuntu 2.6.28-11.38-generic20:59
dtchen13:54 < dtchen> hmm, i'm pretty sure you still have vestiges of my kernel somewhere20:59
dtchen13:54 < dtchen> there's no way -11.38 could have my schroot build path20:59
dtchen13:55 < dtchen> right20:59
dtchen13:55 < dtchen> see line 620:59
dtchen13:55 < dtchen> try blowing away your initramfs and creating it from scratch20:59
dtchen13:56 < dtchen> (you'll need to reboot, of course)21:00
BUGabundo1ok did the last part agaist my will21:00
BUGabundo1LOL21:00
BUGabundo1it just fired again, and I had /var/crash clean!21:00
BUGabundo1dtchen: how can I redo initrams?21:00
dtchenupdate-initramfs -d ; update-initramfs -c (or just reinstall the current linux-image-2.6.28-11-generic)21:02
BUGabundo1reinstalling now21:04
BUGabundo1dtchen: done!21:06
dtchenBUGabundo1: if you reinstall, you still need to have removed the existing initramfses21:06
BUGabundo1I deleted them before reinstaling21:06
BUGabundo1update-initramfs: Deleting /boot/initrd.img-2.6.28-11-generic21:07
BUGabundo1update-initramfs: Deleting /boot/initrd.img-2.6.28-10-generic21:07
BUGabundo1update-initramfs: Deleting /boot/initrd.img-2.6.27-7-generic21:07
dtchenok, make sure you regenerate initramfses for kernels you wish to boot21:07
dtchen^^^^^^21:07
BUGabundo1doesn't re-installing do that?21:08
dtchenonly for the currently installing one.21:08
BUGabundo1its the only one I need...21:08
dtchenwell, you have been warned.21:08
BUGabundo1don't know why I still had 27-7 around21:09
BUGabundo1lol21:09
BUGabundo1dtchen: if anything fails, I'll boot from usb, and chroot21:09
BUGabundo1to fix21:09
=== thunderstruck is now known as gnomefreak

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