[00:18] hey guys [00:18] just to let you know i just edited this page [00:19] https://wiki.ubuntu.com/BugSquad/KnowledgeBase [00:19] because a link was not working [00:19] and i fixed it === evilnhandler_ is now known as nhandler === yofel_ is now known as yofel [12:27] https://bugs.launchpad.net/bugs/671178 [12:27] Launchpad bug 671178 in alsa-driver (Ubuntu) "[CA0106 - CA0106] ALSA test tone not correctly played back (affects: 1) (dups: 1) (heat: 12)" [Undecided,New] [12:27] anyone has any clue about this bug? [13:06] blemish: I noticed in bug 671178 you native installed Lucid then upgraded to Maverick? May want to try a Live CD of Maverick to see if a configuration change since upgrading from Lucid to Maverick contributed to the problem. [13:06] Launchpad bug 671178 in alsa-driver (Ubuntu) "[CA0106 - CA0106] ALSA test tone not correctly played back (affects: 1) (dups: 1) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/671178 [13:15] blemish: I've upgraded from Lucid to Maverick, Live CD'ed Maverick, & native installed Maverick, whenever the sound did not work it was because of how I configured it. I'm not a dev so I can't say for certain this is the OP's problem, but based on the OP noting that the Maverick Live CD sound works, it seems the way alsa is configured is the problem. [13:17] rusivi: yes, I figured as much. But ALSA modules are loaded and speakers are not muted, so I don't know what could be the problem. [13:20] blemish: IMHO, the bug should be placed in Low Importance as the OP notes sound works in Lucid native install, and Maverick Live CD. In the meantime, the OP should perform a native install of Lucid/Maverick to recover sound while the dev's have at it. [13:21] the OP=me :-) [13:22] blemish: Ah, if you like you may post your IRC name in your Ubuntu profile, no big deal. [13:22] rusivi: already reinstalled ubuntu, but I didn't delete the home directory [13:22] rusivi: will do [13:22] k [13:24] rusivi: do you think I should format the home partition as well? [13:26] blemish: I think a full native install is a good way to go if not massively inconvenient. [13:27] rusivi: it isn't and I'm pretty sure it will bring the sound back. [13:27] blemish: Ok, give it a go and let us know how it went :D [13:27] rusivi: what irks me is that I won't find the cause of the bug [15:04] hi [15:04] i would like someone to triage this bug please [15:04] https://bugs.launchpad.net/ubuntu/+source/yarssr/+bug/675198 [15:04] Launchpad bug 675198 in yarssr (Ubuntu) "yarssr dont support seperate browser command for each rss feed (affects: 1) (heat: 6)" [Undecided,New] [15:04] its a wishlist. === nhandler is now known as evilnhandler === bdrung_ is now known as bdrung [17:00] should I be marking bug 673350 as New again or does it have enough information to be marked as triaged? [17:00] Launchpad bug 673350 in emacs-snapshot (Ubuntu) "Can't install emacs23 (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/673350 [19:21] hey, is there a way to switch a bug on launchpad to another package? eg. from gcc to binutils? [19:24] hmm, i 'switched' it, thanks [20:28] Daniel0108: about yesterdays meta-gnome bug, please make sure you have read https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs [20:29] hello everybody, wich is the package for the binary gnome-keyboard-properties? [20:32] !find gnome-keyboard-properties [20:32] yofel: Please use http://packages.ubuntu.com/ to search for files [20:33] njin: ah well, apt-file says gnome-control-center [20:34] ok, thanks yofel but can i found it ? [20:35] njin: 'apt-file find gnome-keyboard-properties' or 'apt-file find /usr/bin/gnome-keyboard-properties' if you're looking for the specific file [20:35] njin: or if you have the packge installed, dpkg -S works too [20:35] yofel: many thanks again [20:35] see https://wiki.ubuntu.com/Bugs/FindRightPackage [21:15] can someone triage this https://bugs.launchpad.net/ubuntu/+bug/661294 thanks [21:15] Launchpad bug 661294 in ubuntu "System lock-up when receiving large files (big data amount) from NFS server (affects: 1) (heat: 122)" [Undecided,New] === jertox is now known as [n0body]