[07:33] <ppisati> moin
[07:34] <smb> ciao
[08:30] <ppisati> brb
[08:57] <ppisati> the push to talk button doesn't work... :(
[08:57] <ppisati> i can crackling hear you
[08:57] <ppisati> but can't talk
[08:57] <ppisati> :(
[08:58] <smb> bah
[09:08] <ppisati> i just dist-upgraded
[09:08] <ppisati> let's see if it helps...
[09:08]  * ppisati -> reboot
[09:14] <ppisati> i can hear you, but my push-to-talk button doesn't work
[09:14] <ppisati> and changing it, doesn't actually make any difference
[09:14] <ppisati> :(
[09:37] <smb> ppisati, One of those mysteries about mumble to me is that even if you tell it to not use speech for status messages, it still causes the speech-dispatcher to start. Which is one more needless complication.
[09:38] <ppisati> smb: eh...
[09:38] <ppisati> ppisati: it usually works for me
[09:38] <ppisati> smb: ^
[09:38] <ppisati> smb: but today it's completely broken... :(
[09:39] <smb> ppisati, Not saying it does not work (usually) but sometimes when one has to kill things to unbreak it, I also have to make sure to kill speech
[09:39] <smb> But I don't use it, so I would not need it to run
[09:39] <ppisati> smb: i rebooted after a dist-upgrade, hoping it would fix it
[09:39] <smb> ppisati, You should be more *experienced* by now... :-P
[09:40] <ppisati> smb: and i had this problem before this dist-upgrade, so it was something from last week
[09:41] <smb> ppisati, Unfortunately for you it seems something bad very much restricted to your hda codec
[09:41] <ppisati> smb: i don't know, it's like the input channel is completely broken
[09:42] <ppisati> smb: lips don't turn red if i press the push-to-talk button
[09:42] <ppisati> smb: and even switching from ptt to continous or voice recognition, doesn't make any difference
[09:42] <ppisati> bah
[09:42] <smb> ppisati, Not sure this helps, but did you try to go into config and change input to samething different and back
[09:42] <ppisati> life sucks, and then you mumble
[09:42] <smb> somthing
[09:44] <ppisati> smb: i could try wiping the entire config
[09:44] <ppisati> smb: lemme try
[09:44] <ppisati> uhm, first problem
[09:44] <ppisati> where does mumble store its config?
[09:44] <smb> ppisati, I believe to remember that sometimes you had to fiddle around with the config to make it use what you wanted it to use.
[09:45] <smb> .mumble ?
[09:45] <smb> no .Mumble
[09:45] <ppisati> [flag@luxor ~]$ ls -la .mumble*
[09:45] <ppisati> ls: cannot access .mumble*: No such file or directory
[09:45] <ppisati> [flag@luxor ~]$ ls -la .Mumble
[09:45] <ppisati> ls: cannot access .Mumble: No such file or directory
[09:46] <smb> Sorry
[09:46] <smb> Had some sockets there... actually .congig/Mumble
[09:46] <smb> .config! 
[09:46] <smb> Gah
[09:54] <apw> ppisati, when i get that i find going into the 'audio wizard' and clicking forward a few times
[09:55] <apw> will either hang mumble completely (then killall mumble; killall pulseaudio; sleep 10; mumble -- is needed)
[09:55] <apw> or it fixes it magically ... and you are good
[10:02] <ppisati> can't set any shortcut for PTT now
[10:02] <ppisati> ok, i give up
[11:12] <rbasak> If a driver works on an old release when a linux-backports-modules* package is installed, does that mean there should be support in the latest upstream kernel? ie. is linux-backports-modules fed from the upstream kernel, the Ubuntu kernel, or somewhere else?
[11:18] <apw> rbasak, it is fed from the wireless backports tree, but yes in principle it means that it is supprted in mainline
[11:18] <apw> (compat wireless is the right name)
[11:19] <rbasak> Great - thanks!
[11:19] <apw> rbasak, though testing kernels from later releases should be as simple as installing the newer kernel and testing
[11:20] <rbasak> I need a USB wireless dongle because I'm working with the latest upstream kernel on my ARM Chromebook to experiment with ARM KVM, and the upstream kernel doesn't have support for the Chromebook's wireless yet. Trying to figure out what to buy.
[11:21] <apw> something old :)
[11:21] <rbasak> linuxemporium.co.uk said that 10.04 worked with linux-backports-modules-... installed, so I figured I'd get that one. But they're sold out :(
[11:23] <rbasak> There are various people selling cheap stuff on eBay with "Linux" support but I don't know if that means mainline or some binary driver built for !arm.
[11:24] <rbasak> This is when I wish the Linux trademark were used more. If they said "Linux first-class" means mainline support only, then it'd be easier for me to shop for hardware that declares that.
[11:24] <rbasak> (since "Linux" support can mean anything)
[11:29] <apw> yeah indeed, it is a minefield, buy something older, and you'll likely be ok, maybe
[12:06] <infinity> rbasak: USB ethernet tends to be less headache than USB wireless, FWIW.
[12:06] <infinity> rbasak: And dirt cheap.
[12:07] <infinity> rbasak: I've got one similar to this http://www.amazon.com/Cisco-USB300M-Cisco-Linksys-Ethernet-Adapter/dp/B001NLV4TQ
[12:08] <infinity> rbasak: (And those dongles have had mainline support forever, and I use 'em on all sorts of ARM boards when they lack ethernet or their own is buggered)
[12:10] <ogra_> just dont use to many of them at the same time :)
[12:11] <ogra_> (at least on teh same bus) 
[12:16]  * henrix -> lunch
[17:52]  * henrix -> EOD