[00:11] <robru_> qengho, I was having tons of trouble with pulseaudio recently
[00:11] <robru_> qengho, as in, nothing using pulseaudio could make any noise at all, and there were no error messages.
[00:11] <qengho> Ubuntu updated from 2.1 to 3.0.
[00:11] <qengho> I think some clients are not prepared for that.
[00:12] <robru_> qengho, oddly, I uninstalled it for a while and was just living my life without it, but then I hit issues where only one app could make sound at a time, and that kinda sucked, so I reinstalled it, and now it seems fine.
[00:12] <qengho> chrome works.  vlc and mplayer do not.
[00:12] <robru_> qengho, yes, vlc is what I was having trouble with
[00:13] <qengho> the one-app-at-a-time is the reason pulse was invented.
[00:13] <robru_> qengho, yeah ;-)
[00:13] <robru_> qengho, confirmed, vlc is still not working
[00:14] <qengho> filing a bug report.  Assigning it to you.  ha ha, only serious.
[00:14] <robru_> qengho, I think I could actually live with one-app-at-a-time, but the problem is that I can't choose which app makes audio at runtime... too annoying to have to quit one app when I want a different one to start making noise ;-)
[00:15] <robru_> qengho, go ahead... if you want it to stagnate for years ;-)
[00:17] <qengho> oss, esound, alsa, pulseaudio.  Things are getting better, but slowly.
[00:25] <mandoguit> just out of curiosity how are you determinining that pulseaudio and vlc aren't working?
[00:28] <robru_> mandoguit, ... I ran vlc, and it was silent. and the only configuration of VLC that was not silent, had 'ALSA' selected as the audio output.
[00:28] <robru_> mandoguit, and this was fine a few weeks ago before pulseaudio was updated.
[00:33] <mandoguit> robru_:    thanks for the reply.     not sure where to check for this though " had 'ALSA' selected as the audio output"    is that in vlc itself or sys config?
[00:41] <robru_> mandoguit, I'm talking about VLC's preferences. the only way I can make it have any audible output whatsoever is to choose ALSA and make sure no other applications are making noise before launching it.
[00:43] <mandoguit> robru_:   ok but where in vlc (not really familiar with the preference sections in that program)  thanks
[00:45] <robru_> mandoguit, it's under Tools->Preferences->Audio
[00:45] <robru_> mandoguit, you have to select 'ALSA audio output' and then some more options will appear underneath that, make sure it isn't just using the pulseaudio backend to ALSA, because that's also broken
[00:47] <robru_> qengho, actually it seems that firefox is also broken.
[00:47] <mandoguit> robru_:   ok thanks... I selected Pulseaudio audio output and then save   started a movie file and the audio works fine
[00:48] <robru_> mandoguit, did you restart vlc? changes to the audio system only take effect after restarting vlc
[00:48] <mandoguit> ahhh...no will do then
[00:48] <bjsnider> qengho, why put mplayer in quotes?
[00:50] <mandoguit> hmmm...that was interesting.  restart vlc and it immediately barfed.   restarted it again (with pulseaudio set) and it played fine
[00:52] <mandoguit> just tried another documentary avi file.... vlc started fine and audio is fine too
[00:54] <mandoguit> I;ve got to scoot for now... will try mplayer later on
[00:55] <mandoguit> fwiw     VLC media player 2.0.5 Twoflower (revision 2.0.5-0-g1661b7d)  pulseaudio 3.0   Kernel: 3.8.0-8-generic x86_64 (64 bit)
[00:55] <mandoguit>            Desktop: KDE 4.10.00 Distro: Ubuntu Raring Ringtail
[00:56] <mandoguit> thanks for the pointers.... much appreciated.  :)
[00:57] <bjsnider> robru_, if vlc is silent check the applications tab in the sound menu
[00:57] <bjsnider> it may be turned off
[00:59] <robru_> bjsnider, nope, it's maxed there. doesn't help that the 'test audio' button also fails to make any noise! seems pulseaudio itself is thoroughly broken
[01:01] <bjsnider> robru_, have you got the right output device selected?
[01:02] <robru_> bjsnider, you mean the only one that there is? yes, it is selected.
[01:50] <johnjohn101> is there a chanel for the ubuntu phone and tablet?
[01:53] <jbicha_> !touch
[01:55] <johnjohn101> thanks.
[01:55] <johnjohn101> 8 more weeks until 13.04.  I saw ubuntu touch has more Qt stuff for it.  Is that same ability coming to the desktop unity?
[04:27] <roasted> hello friends
[04:49] <robru> qengho, actually I rebooted and now stuff seems to be working (both firefox and vlc can play audio through pulseaudio now...) go figure
[04:49] <humanoids> sokah, his eyes open
[06:56] <SuperLag> So tell me, guys... on the lists, where the one guy (don't remember his name) proposes the rolling release schedule... he made a comment to the effect that 13.04 is much more stable/reliable than previous pre-release versions. Would you guys agree with that sentiment?
[06:59] <SuperLag> Okay. Maybe I don't capture it quite the same... here's the actual text: The result is that 13.04 has been as robust a release
[06:59] <SuperLag> over the last many weeks as 12.10 was when we delivered. We have achieved
[06:59] <SuperLag> rolling release quality in our development practices, so we can capitalize
[06:59] <SuperLag> doh
[06:59] <SuperLag> I'm sorry.
[06:59] <SuperLag> I thought that would paste as a single line :(
[12:32] <penguin42> hmm, why does Google say that FF19 can't play HTML5 video - I thought it was in since FF4?
[12:32] <penguin42> ^google^youtube
[12:36] <jtaylor> the question is which codec?
[12:36] <jtaylor> firefox can't to webp, maybe also no webm?
[12:39] <penguin42> hmm odd, this was one video on youtube, all the others seem fine - I'd assumed that it would be consistent
[13:57] <vivid> seems to be an issue with java? specifically java windows like minecraft.  but theres been no java updates so im guessing the issue is in the latest push of compiz/unity?
[13:58] <jtaylor> what kind of issue?
[13:59] <vivid> http://s14.postimage.org/ps6eyybtt/Screenshot_from_2013_03_02_05_58_40.png
[13:59] <vivid> also happens with my citrix webviewer crap thing for virtual machines
[14:00] <vivid> the title bar is rendered...somewhere else
[14:01] <jtaylor> looks like bug 1110138
[14:02] <jtaylor> or is it new?
[14:02] <jtaylor> maybe the upload a few days ago regressed something
[14:03] <vivid> no it looks like the bug to me
[14:03] <vivid> the package that resolves must still be in the build queue
[14:03] <jtaylor> not sure I do see the same thing with jdownloader
[14:03] <jtaylor> I have the "fixed" unity
[14:04] <jtaylor> never had the old one, only installed yesterday
[14:04] <vivid> well it says fixed in compiz 1:0.9.9~daily13.02.26-0ubuntu1 but thats not available yet
[14:05] <jtaylor> I have it installed
[14:05] <vivid> oh wow, yeah lol
[14:05] <vivid> 03.01 is what i have
[14:05] <vivid> certainly is not fixed
[14:05] <jtaylor> unfotunately I can't install an older on and logout, got a powerpc chroot running and rebuilding that would take 4 hours
[14:06] <jtaylor> if you have the time try the old package and see if its still the case
[14:06] <vivid> the one thats supposed to fix it?
[14:06] <jtaylor> the one before that
[14:06] <jtaylor> or was it always the case?
[14:06] <vivid> no this happened very recently
[14:06] <jtaylor> so the update probably broke it not fixed it
[14:07] <vivid> i just noticed it yesterday
[14:09] <vivid> eh, where can i get the older packages?
[14:10] <jtaylor> good question
[14:13] <jtaylor> can I upload the screenshot to the bug?
[14:14] <vivid> oh, yes, but i already did :p
[14:15] <jtaylor> k good
[14:15] <jtaylor> I guess you have to build the old package from source to see if it really caused the issue
[14:15] <jtaylor> are you familiar with how that works?
[14:17] <vivid> well, the debian method yes, but im not familiar with pulling revisions from bazaar
[14:17] <vivid> but yeah, i can figure that out
[14:18] <jtaylor> vivid: download this diff: https://code.launchpad.net/~compiz-team/compiz/compiz.fix_1110138/+merge/147548
[14:18] <jtaylor> revert it with patch -p0 -R <file
[14:18] <jtaylor> and build regulary
[14:18] <jtaylor> the normal apt-get source compiz
[14:18] <jtaylor> afk 20 min
[14:20] <vivid> i cant get build-dep right now unfortunately, due to some package conflicts that i assume are in the build queue
[14:32] <jtaylor> can you restart compiz without logging out?
[14:32] <jtaylor> it builds for me
[14:34] <vivid> i dont know. does compiz --replace work for that?
[14:34] <BluesKaj> Howdy all
[14:34] <vivid> still, libx11-6 is missing its i386 counterpart, so apt-get build-dep fails with broken packages
[14:34] <jtaylor> strange
[14:35] <vivid> wants to remove all my i386 stuff
[14:35] <jtaylor> mk-build-deps -ir worked, but my system is very clean as its a fresh install
[14:36] <vivid> i guess if i disable raring-proposed that package conflict will disappear
[14:37] <jtaylor> maybe, but build depdencies often have issues with multiarch
[14:40] <jtaylor> compiz --replace works
[14:40] <jtaylor> the patch is the problem
[14:41] <vivid> the resolving patch?
[14:41] <vivid> im still building
[14:41] <vivid> maybe you want to add that to the bug report
[14:44] <vivid> jtaylor: thanks for the help btw.  time for me to move on to other tasks :p
[14:45] <jtaylor> oh man I'm a moron
[14:46] <jtaylor> wanted to put the compiz --replace into the background, with ctrl+z -> bg
[14:46] <jtaylor> this obviously does not work ._.
[14:46] <jtaylor> and my terminal with the chroot did not survive the restoring with -CONT :/
[14:46] <jtaylor> well I was stuck anyay
[16:00] <ejat> anyone can verify the package need to be removed? http://paste.ubuntu.com/5579567/
[16:01] <mirak> hi
[16:02] <mirak> is the TV mode available on the next ubuntu version ?
[16:02] <mirak> I mean the one we see when he takes a remote
[16:03] <jbicha_> ejat: no those shouldn't be removed and we don't recommend that you use -proposed during the development cycle
[16:07] <jbicha> more specifically, https://launchpad.net/ubuntu/+source/libx11/2:1.5.0-1ubuntu1 failed to build on i386
[16:11] <ejat> but im using 64
[16:11] <yofel> parts of it are only built on i386
[16:12] <ejat> yofel: noted ..
[16:12] <ejat> so waiting for someone looks into it right ? or someone already working on it already/
[16:13] <yofel> dunno, disable -proposed and you should be able to upgrade fine
[16:13] <yofel> someone will look at it
[16:13] <ejat> owh okie
[16:13] <jbicha> ejat: yes, but turn off raring-proposed updates to avoid these problems
[16:13] <ejat> will do .. thanks
[16:14] <BluesKaj> pasting errors with a url , without any explanation or context of what ppl are trying to do is becoming annoying
[17:38] <tekoholic> After upgrade from linux-image-3.8.0-8 to -9, either the ad-hoc mode for several different wlan drivers has been broken, or batman-adv (built in or built 2013.0.0 from src) modules aren't running correctly any longer.  This REBOOTS OpenWRT routers to which this network attaches
[17:38] <tekoholic> Is this a known issue?
[17:39] <penguin42> tekoholic: I don't honestly know but either way thay means there is a bug in OpenWRT that needs fixing; but it would be fair to file against ubuntu as well so it's known
[17:40] <tekoholic> penguin42: Really?  OpenWRT didn't change, nor did the batman-adv modules I regularly use (always build current), just the Ubu kernel...  Where'd ya' say the breakage happened?
[17:41] <penguin42> tekoholic: Well I say that whatever a nasty client does OpenWRT should never reboot
[17:41] <penguin42> tekoholic: So however broken Ubuntu may or may not be, OpenWRT shouldn't get too upset
[17:42] <tekoholic> penguin42: I believe that it's doing so as a result of a kernel panic...  Ubu does the same thing, if it can...
[17:42] <penguin42> tekoholic: Right, and you shouldn't be able to kernel panic the thing on the other end of your wireless connection
[17:42] <penguin42> tekoholic: After all that means if someone figures out what causes it in your case then they could do it from any host and go around nuking OpenWRTs for fun and profit
[17:43] <tekoholic> OK, I guess that's a good darn point...
[17:43] <tekoholic> Hadn't looked at it like that.
[17:45] <tekoholic> Is there anything I can do to dig deeper into this issue's cause (on the Ubu side), prior to filing bug or what-not?
[17:46] <penguin42> I don't know much wireless side
[17:46] <penguin42> tekoholic: You could go back to 3.8.0-8 and see if it stabilises to see if that's the actual cause
[17:49] <tekoholic> It DID stabilize
[17:50] <tekoholic> As well, there is quite a variety of wlan devices in use, so it's gotta' be something they all have in common, such as batman-adv, mac80211, etc
[17:51] <penguin42> tekoholic: Can you explain that - you mean 3.8.0-9 on any of these machines causes your openwrt to crash?
[17:53] <tekoholic> That is exactly correct, altho incomplete.  3.8.0-9 with either in-kernel or built from src batman-adv modules, and all wlan dev's in ad-hoc mode
[17:54] <penguin42> sorry, I don't understand about 'all wlan dev's' - is tis multiple wlan devices connected to one host running 3.8.0-9 or what?
[17:54] <tekoholic> All worked fine on 3.8.0-8 with 2013.0.0 modules from src
[17:55] <tekoholic> No, several hosts, each with single wlan device, all ad-hoc / mesh-networked, and an OpenWRT router in the mix as well, as gateway
[17:55] <penguin42> ok, and did you upgrade one host to 3.8.0-9 or all of them?
[17:57] <tekoholic> All of them, but I've eliminated all but 1 (all's fine until traffic is passed), and switched which one
[17:57] <tekoholic> All do the same
[17:58] <tekoholic> Individually or in concert
[17:58] <penguin42> so if you take them all back to 3.8.0-8 and then switch one of them to 3.8.0-9 does openwrt nuke?
[17:59] <tekoholic> Had not tried that, but with just one, I tested 3.8.0-9 (oops) and immediately 3.8.0-8 (worx as expected)...
[17:59] <penguin42> right, so it's difficult to tell if it's specific to one driver or what
[18:00] <tekoholic> No, it's NOT.  Same issue on all the wlan devices running the new kernel
[18:00] <tekoholic> Some atheros, other intel, etc
[18:01] <tekoholic> Reread above...  I troubleshot down to a single client, then switched clients
[18:01] <penguin42> I don't understand how you've figured that out if they're all running the 3.8.0-9
[18:03] <tekoholic> I'm not sure I understand what you're getting at, with that.  What I can say is that all the machines had the same issue with the 3.8.0-9, none of them had it with anything prior, and they've all got diff wlan dev's
[18:04] <tekoholic> So, its something common between them all, not specific to any one driver (ath9k and such)
[18:05] <tekoholic> brb
[18:05] <penguin42> tekoholic: Lets start again; what symptom do you see on the individual machines as opposed to the problem you have with OpenWRT rebooting
[18:12] <tekoholic> penguin42: The only issue that is apparent on each of the machines is that they will not get an address issued, or if they do, they immediately lose any usable connection due to the immediate router reboot and consequent disassociation
[18:13] <tekoholic> As yet, I can't even pin it down to bare ad-hoc or batman-adv cause, as I've not tried ad-hoc without batman
[18:13] <tekoholic> That will require quite a reconfig to test, and I've not yet had the time
[18:16] <penguin42> I don't see anything in the linux-image-3.8.09 changelog that sounds promising
[18:18] <tekoholic> Neither did I, altho I honestly didn't have a whole lotta' clue what to be looking for...
[18:23] <penguin42> well there didn't seem to be anything wireless specific
[18:24] <tekoholic> OK, so could it be a kernel config that batman-adv expects, or something like that?
[18:25] <penguin42> dunno anything about batman; but I would have expected the changelog to have mentioned kernel config changes, and I didn't notice any relevant but might have missed something
[19:07] <tekoholic> penguin42: Here's a bit more info, if useful...  dmesg shows an error "iwlwifi unable to find TIM element in beacon" a coupla times, on one of the machines.  I've not looked at others yet
[19:32] <penguin42> tekoholic: Probably need to find some wifi person
[19:52] <zorro-in> hello. i'm on zorin os and while trying to update, it asks for a specific ubuntu cd. i know this is not the channel to be, but since i can't seem to find that iso i was wondering if you could help me. i'm looking for this: CD/DVD 'Ubuntu 13.04 _Raring Ringtail_ - Alpha i386 (20130211)
[19:52] <bazhang> check your sources.list zorro-in
[19:53] <zorro-in> hmm... should have thought of that. thanks bazhang.
[19:54] <bazhang> zorro-in, then place a # in front of it, and save
[19:55] <zorro-in> yea i know about that. thanks again.
[20:11] <ironhalik> is it a good idea to do a dist-upgrade if it want's to remove most of my ia32 libs?
[20:12] <penguin42> not if you're trying to run some 32 bit stuff
[20:12] <ironhalik> Dunno if it's inteded or just some dependency issue
[20:43] <ironhalik> Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg  Something wicked happened resolving 'dl.google.com:http' (-11 - System error)
[20:43] <ironhalik> Wicked.
[22:20] <bekks> ironhalik: Then you just have to wait until they fixed it.
[23:25] <Allard> hello
[23:25] <Allard> I can't start Libre Office
[23:26] <Allard> it won't load
[23:27] <Allard> is somebody here at all
[23:27] <Allard> will someone help
[23:27] <bekks> Allard: 160 people are in here. Be patient.
[23:27] <Allard> ok
[23:28] <Allard> at least I know I have to wait
[23:46] <Allard> still no answer
[23:48] <bekks> Be more patient.
[23:48] <bekks> And all your questions already have been answered in #ubuntu
[23:52] <jtaylor> more specific information would be useful