[00:25] <FoD__> I just installed Lubuntu and I cannot seem to get sound to work. I have a pair of cheapo Logitech USB speakers on the machine, and weirdly enough the volume +/- and mute buttons work on them, and it seems to detect the device fine... But no matter what I do, I can't hear anything.
[00:25] <ianorlin> FoD__: I personally have not used usb speakers but do you know which output device you are trying to use?
[00:26] <FoD__> I installed the audio mixer, and tried using both the default setting, and the one with the device's name.
[00:26] <FoD__> No luck with either.
[00:27] <FoD__> I had Ubuntu on the machine before, and audio worked fine out of the box there.
[00:27] <FoD__> If that helps at all.
[00:40] <FoD__> When I run alsamixer, it seems to switch back the the default/generic output every time...
[00:40] <FoD__> Is that a sign that somehow it's not actually changing the output?
[00:53] <ianorlin> FoD__: you can also try audicous as that has prefrences to slect differnt audio
[00:59] <FoD__> audicous?
[00:59] <ianorlin> it is under sound and video as a music player
[00:59] <ianorlin> in prefrences
[01:06] <FoD__> I was able to get it to play audio.
[01:06] <FoD__> But I still cannot hear system sounds or audio from the browser or anything.
[01:06] <ianorlin> ah ok do you know with which settings
[01:07] <FoD__> sysdefault:CARD=AUDIO
[01:08] <FoD__> Via ALSA
[01:18] <FoD__> How do I set the default audio output?
[01:18] <holstein> i use alsamixer.. in the terminal.. but, there are many ways, im sure.. whats the goal?
[01:18] <holstein> i do like pulseaudio and pavucontrol for routing..
[01:19] <FoD__> I just have a simple USB audio device
[01:19] <holstein> does it support linux?
[01:19] <FoD__> It worked in Ubuntu.
[01:19] <holstein> most are "class compliant"
[01:19] <holstein> hmmm.. lubuntu *is* ubuntu
[01:20] <FoD__> I was able to get audacious to play an mp3 on the device.
[01:20] <holstein> sure
[01:20] <FoD__> But I can't seem to get the system to use it.
[01:20] <FoD__> I'm pretty new to all this, very confused.
[01:20] <holstein> !audio
[01:20] <holstein> what i do is, i run "aplay -l" in a terminal
[01:20] <FoD__> alsamixer doesn't seem to change the default
[01:21] <holstein> i see that the devices are present.. if they are not present in "aplay -l", then, you wont get sound
[01:21] <holstein> are they present?
[01:21] <FoD__> Yes, it's there.
[01:21] <holstein> so, then, i *dont* test with web audio, like flash, or mp3's..
[01:22] <holstein> i get a known good audio file playing on the internal audio device.. then, i'll stop that, and close everything,and use alsamixer to select the USB device
[01:22] <holstein> but, for me, if im juggling multiple devices, i use pulse, and pavucontrol
[01:22] <FoD__> Is there a way to set it as the default card using aplay?
[01:22] <holstein> FoD__: yes
[01:22] <holstein> FoD__: i do that in alsamixer. but, as i said, i ideally just install pulseaudio and pavucontrol
[01:23] <holstein> FoD__: if you want to set soething as default, you'll have to just try the alsamixer tool, and share what isnt working for you
[01:23] <FoD__> Each time I relaunch alsamixer it goes back to the one I DON'T want to use as default.
[01:24] <holstein> FoD__: sure.. but, it *is* putting audio out, correct?
[01:24] <holstein> there are many ways to have the USB audio device be default.. but, see that you are getting audio to it, first
[01:24] <FoD__> As stated, I was able to get an audio player application to use it.
[01:24] <FoD__> But not the system.
[01:25] <holstein> FoD__: so, one easy way to use the USB device is, disable the internal in the bios. then, the only audio device for the system will be the USB device
[01:25] <ianorlin> holstein: that is what I do with hdmi on my desktop
[01:25] <FoD__> I'll give that a whirl.
[01:26] <holstein> FoD__: this looks like what i would do, if, i wanted to keep both, and set one as default, without installing pulseaudio, and pavucontrol https://bbs.archlinux.org/viewtopic.php?id=124380
[01:26] <holstein> here is the *exact* scenario http://superuser.com/questions/626606/how-to-make-alsa-pick-a-preferred-sound-device-automatically
[01:27] <holstein> the issue with that ^ is, those labels can change, between reboots
[01:28] <FoD__> I don't want to keep both.
[01:29] <holstein> cool.. then, ideally, just disable, or blacklist the internal, since, you dont want it at all
[01:29] <holstein> then, you wont even need to bother with which is default..
[01:29] <FoD__> Is there a way to do that without the BIOS?
[01:29] <holstein> you'll only have the one, and the system will use it
[01:29] <FoD__> Annoyingly the BIOS seems to have no option to disable onboard audio.
[01:29] <holstein> !blacklist
[01:31] <FoD__> How do I know what the modulename is
[01:33] <holstein> http://askubuntu.com/questions/110835/how-to-disable-the-internal-sound-card
[01:33] <holstein> ^ looks like how i would attempt
[01:37] <FoD__> ugh
[01:37] <FoD__> I did no realize I would need an engineering degree to get the soundcard set as the default.
[01:37] <FoD__> not*
[01:37] <holstein> lol
[01:37] <holstein> well, you can use main ubuntu, or, pulse from main ubuntu
[01:38] <FoD__> ubuntu was running slowly, wanted something lighter weight for my dad's computer.
[01:38] <holstein> you may find just adding pulse makes your experience more like that. you dont need an engineering degree, but, the goal of lubuntu is to be light..
[01:38] <holstein> its not necessarily as friendly at all things.. since, things have to be stripped down/out
[01:38] <holstein> xfce is lighter.. mate is lighter..
[01:39] <holstein> no doubt, you can get what you need.. but, you'll have to learn to do with with alsa only
[01:41] <FoD__> I'm unable to create a conf file in /etc/
[01:41] <FoD__> I'm guessing changing the permission will be another whole ordeal all it's own?
[01:41] <holstein> sudo
[01:41] <holstein> !sudo
[01:41] <holstein> sudo nano /path/to/file
[01:42] <FoD__> That will create a blank file?
[01:43] <holstein> FoD__: sudo gives you root permission.. to access and write in /etc
[01:43] <holstein> nano is a text editor.. so, as root, open this text editor, and create the file "/path/to/filename"
[01:47] <FoD__> Understood.
[01:47] <FoD__> When I do "cat /proc/asound/cards"
[01:47] <FoD__> What part of the device name is the name I'm supposed to be using?
[01:47] <FoD__> What's between the brackets?
[01:47] <FoD__> Including the 13 following spaces?
[01:51] <holstein> FoD__: i like this command, in the terminal /sbin/lsmod | grep snd
[01:52] <holstein> FoD__: you'll want the module.. the linux kernel is modular, and what you are going to do, basically, since, your hardware bios doenst facilitate disabling, and you want the internal audio device off, is, you keep the system from loading the driver for it.. basically
[01:52] <holstein> blacklisting the module.. should make the device not present.
[01:53] <FoD__> I'm currently attempting the asound.conf method.
[01:53] <FoD__> Fingers crossed.
[01:53] <holstein> sure.. but, those labels can change
[01:53] <holstein> if you are leaving it with someone, who is not familiar with linux, and want it to be "bullet-proof". they *could* reboot, and have the labels change..
[01:55] <FoD__> It somehow screwed everything up.
[01:55] <FoD__> Can't even run alsamixer now.
[01:56] <holstein> ubuntu-mate is my "go-to" for family members
[02:00] <FoD__> How do I find the module I need to disable?
[02:00] <FoD__> To kill the other useless soundcard.
[02:00] <holstein> i like using /sbin/lsmod | grep snd
[02:01] <FoD__> Oh, you already said that, sorry.
[02:01] <holstein> that lists out all the modules being used with "snd" in them..
[02:01] <FoD__> Thank you.
[02:01] <holstein> snd_hda_controller     32768  1 snd_hda_intel
[02:02] <holstein> for example. thats where i would start.. just testing as i reboot, and check
[02:09] <FoD__> Is it normal for there to be no existing blacklist file?
[02:10] <holstein> i dont have anything blacklisted
[02:11] <FoD__> snd_hda_intel
[02:11] <FoD__> Just that part?
[02:12] <holstein> FoD__: i dont know what your module will be, but, for me, if i were trying to implement blacklisting my driver for my internal audio, i would start with that.. i would keep note of what i have done, and how to undo it, and reboot, and test
[02:13] <FoD__> Well I see a similar entry
[02:13] <FoD__> But Only that should be added to the blacklist?
[02:13] <FoD__> I'm confused, since it's displayed on one line...
[02:14] <holstein> FoD__: i would make it look like it does at http://askubuntu.com/questions/110835/how-to-disable-the-internal-sound-card
[02:14] <holstein> snd_pcm          80388   5 snd_ens1370 for example
[02:15] <holstein> so, the module is snd_ens1370 in that specific case.. so..
[02:15] <holstein> sudo nano /etc/modprobe.d/blacklist
[02:15] <holstein> then, create, or add.. blacklist snd_ens1370
[02:15] <holstein> # disable my PCI ensoniq sound card
[02:15] <holstein> blacklist snd_ens1370
[02:16] <holstein> the # is a comment.. so, you can say "# disabling internal audio" then on the next line "blacklist module_name"
[02:17] <holstein> then, you can easily find what you have done, and undo it, if you need..
[02:21] <FoD__> ugh
[02:22] <FoD__> I've tried disabling two different obvious candidates.
[02:22] <FoD__> No luck.
[02:22] <holstein> feel free and share any output you like
[02:22] <holstein> !paste
[02:23] <holstein> you'll have to reboot, for the changes to work
[02:25] <FoD__> I'm aware.
[02:25] <FoD__> I've been rebooting.
[02:26] <FoD__> There's no way to actually find out what module a card is using...?
[02:26] <FoD__> Outside of guessing.
[02:26] <holstein> FoD__: again, you can share any output you like, and a volunteer can assist you with that
[02:26] <FoD__> Output?
[02:27] <FoD__> Oh, you mean the names of the modules
[02:27] <holstein> FoD__: correct. you run a command. you get output.. you assume the module name. you can share the output here, and a volunteer can assist with getting the name
[02:27] <FoD__> Well, I just tried disabling the USB audio card module.
[02:27] <FoD__> Which is the card I actually want to use.
[02:27] <holstein> why?
[02:27] <FoD__> And rebooted.
[02:28] <holstein> you just unplug it.. ;)
[02:28] <FoD__> aplay -l
[02:28] <FoD__> still shows the device
[02:28] <FoD__> So my blacklist is being ignored?
[02:28] <holstein> could be..
[02:28] <holstein> In later versions since 12.10 (12.04?) the file is /etc/modprobe.d/blacklist.conf
[02:29] <FoD__> .conf has to be added?
[02:29] <holstein> so, it could be, we are editing an older filenam.. and it should be ^
[02:29]  * FoD__ face on desk
[02:29] <holstein> try that location.. you can simply rename the one you have..
[02:41] <FoD__> I disabled the intel one.
[02:41] <FoD__> And things are no partially working.
[02:41] <FoD__> But...
[02:41] <FoD__> The volume +/- and mute buttons no longer work.
[02:41] <FoD__> Also.
[02:41] <FoD__> I can no longer run alsamixer.
[02:42] <holstein> not sure what you mean, you cant run alsamixer..
[02:42] <FoD__> open terminal
[02:42] <FoD__> type "alsamixer"
[02:42] <FoD__> press enter
[02:42] <holstein> you open a terminal, and type "alsamixer", and share errors
[02:42] <holstein> anyways, to get the buttons to now control the USB device will probably be a bit trickier
[02:43] <holstein> so, id say, just to save time, and hassle, consider just giving dear ol' dad ubuntu-mate
[02:43] <FoD__> cannot open mixer, no such file or directory
[02:44] <holstein> FoD__: http://askubuntu.com/questions/509791/alsamixer-no-such-file-or-directory is relevant for that
[02:47] <FoD__> Interesting.
[02:47] <FoD__> Why is USB audio so hated? hah
[02:47] <holstein> ?
[02:47] <holstein> its not
[02:48] <FoD__> Doesn't want to use it as a default, doesn't want to run aslamixer if it's the only device present...
[02:48] <holstein> its just that lubuntu is stripped down. its not really intended to easily manage usb only audio
[02:48] <holstein> pulse audio addresses a lot of that.. but, its a trade off
[02:49] <FoD__> I tried the second solution in that link
[02:49] <FoD__> commenting out the one line.
[02:49] <FoD__> Has not fixed the problem.
[02:49] <FoD__> I guess I can live without alsamixer, since at least the sound works...
[02:49] <holstein> well, i think looking at it like that is a miss-step
[02:49] <holstein> its not really something that is broken to be fixed, in that manner.. its going to take some time to hack at lubuntu and make it what you intend for your case
[02:50] <FoD__> To "comment out" a line I'm just putting a pound and a space in front of it, no?
[02:50] <holstein> correct
[02:50] <FoD__> Alright, well.
[02:50] <FoD__> Commented out.
[02:50] <FoD__> rebooted.
[02:51] <FoD__> Alsamixer still refuses to run.
[02:51] <FoD__> So...
[02:51] <FoD__> Time to throw in the towel on that?
[02:51] <holstein> though, thats not your module, corect?
[02:51] <FoD__> "options snd-usb-audio index=-2"
[02:51] <FoD__> I found that in the same file he mentions.
[02:51] <FoD__> It's the same module name.
[02:51] <holstein> FoD__: when i run "man alsamixer" i see the -c option
[02:52] <holstein> so, i would expect to be able to run "alsamixer -c" and specify the USB device
[02:52] <holstein> but, in no way would i *ever* leave someone unfamiliar with linux using alsamixer to control the audio device
[02:52] <holstein> have you tried ubuntu-mate? its just that, its quite light, and the creator actually created it for that.. for his dad
[02:53] <FoD__> System sound is now working.
[02:53] <holstein> its using pulse, and would allow you to deal with this in a GUI, as you expect
[02:53] <FoD__> But I still can't run alsamixer.
[02:53] <FoD__> I guess this is good enough.
[02:53] <holstein> FoD__: sure. have you tried specifying the audio device properly?
[02:53] <FoD__> What do you mean?
[02:54] <FoD__> Thanks for your patience by the way.
[02:54] <holstein> FoD__: with the -c flag
[02:54] <holstein> FoD__: sure.. its not easy, i understand..
[02:54] <FoD__> If it's working wouldn't that mean it's already specified?
[02:55] <holstein> FoD__: if its working, you can use it.. if its not, then, when you run "alsamixer" it wont work... and, if you want, you can specify to alsamixer what device.. "alsamixer -c". using the -c flag to specify the USB device
[02:56] <FoD__> I run firefox, go to youtube.
[02:56] <FoD__> I hear sound.
[02:56] <FoD__> But I still cannot run alsamixer.
[02:56] <holstein> FoD__: have you tried specifying the audio device to alsamixer with the -c flaf?
[02:56] <holstein> flag*
[02:56] <FoD__> It says invalid number.
[02:57] <holstein> FoD__: try another # ;)
[02:58] <FoD__> I got it to work, I had messed up the syntax.
[02:58] <FoD__> So lastly then, I guess...
[02:58] <FoD__> Any chances of getting the buttons on the USB device to work again?
[02:58] <holstein> sure
[02:59] <holstein> its *all* open, so, theres more than just a chace
[02:59] <holstein> chance*
[02:59] <FoD__> Why would disabling the intel module make the buttons stop working?
[02:59] <holstein> i would expect it to be a bit more challenging than what you have done so far
[02:59] <holstein> and, i would expect it to be a bit odd for someone to use, that is not experienced with linux
[02:59] <holstein> FoD__: it didnt
[03:00] <FoD__> They were working prior.
[03:00] <holstein> FoD__: the buttons are still doing what they always did.. the device is not there, anymore
[03:00] <FoD__> Why are the buttons on the USB device linked to the onboard device that I blacklisted? O_O
[03:00] <holstein> FoD__: why not? i mean, thats the norm
[03:01] <holstein> its the normal desktop use, the scenario that would be most likely
[03:01] <FoD__> What should I do to restore the functionality of the buttons?
[03:02] <holstein> FoD__: what would i do? i think it would be easiest to learn the commands that control and set what you want.. volume up and down and mute.. and make new keyboard shortcuts for those commands
[03:02] <FoD__> Or should I just be thrilled I got it working to the extent it is, and walk away.
[03:02] <holstein> FoD__: the issue is, the more of this you hack at, the more unstable you make it for the end user.. which, is not you
[03:03] <FoD__> The computer is for my 68 year old dad, so.
[03:03] <holstein> correct
[03:03] <FoD__> I don't think keyboard macros are the way to go.
[03:03] <holstein> so, why does he even need a USB device?
[03:03] <FoD__> It's the only speakers around here.
[03:03] <FoD__> I don't have anything besides maybe a crappy pair of earbuds that I could plug into the 1/8" jacks on the back of the computer.
[03:04] <holstein> i would give him the most "out of the box" default setup.. if that meant getting speakers from the charity shop..
[03:04] <FoD__> Well, what's working now is working good enough.
[03:05] <holstein> cool.. enjoy!
[03:05] <FoD__> I'll tell him he just has to use the volume icon in the taskbar to change volume.
[03:05] <FoD__> And that the buttons don't work anymore.
[03:05] <holstein> sounds great. except, it sound like an excuse.. since, it used to work the other way, and he may not like it
[03:07] <FoD__> It's a very crappy computer, and even Ubuntu running Metacity was very bogged down.
[03:08] <FoD__> So I went for Lubuntu because it seemed like the best compromise of user friendliness and lack of bloat.
[03:10] <FoD__> All he uses it for is browsing the web.
[03:11] <FoD__> Thank you for all your help.
[03:15] <FoD__> Is there anything I should do to optimize a lubuntu installation on a slow computer?
[03:16] <FoD__> On which I'm pretty sure the bottleneck is the CPU.
[03:16] <FoD__> Even opening Firefox is kind of slow.
[03:16] <FoD__> Though the box has more than enough RAM to comfortable browse the internet...
[05:41] <llogiq> Hi folks. My mouse cursor went invisible.
[05:42] <llogiq> lubuntu 15.04 x64 desktop, intel on-board chipset
[05:43] <llogiq> Anybody have an idea? I do need the mouse every now and then.
[05:43] <ianorlyn> llogiq, press control alt t open a terminal
[05:43] <llogiq> the xorg.0.log says that hardware mouse cursor was active. I already have multiple terminals open.
[05:44] <llogiq> :-)
[05:44] <ianorlyn> then run sudo apt-get install suckless-tools and then you can use a command called swarp to move it to a a coordinate you specify on the command line
[05:45] <llogiq> That may be a good idea, but I think that using the actual mouse to move it to a coordinate of my choosing would be preferrable.
[05:45] <llogiq> (Well, touchpad, but anyway)
[05:45] <ianorlyn> llogiq, do you have any work that needs saving currently
[05:45] <ianorlyn> you could try logging out and logging in again
[05:46] <llogiq> Already rebooted.
[05:46] <ianorlyn> and happens again?
[05:46] <llogiq> Yep.
[05:46] <llogiq> Perhaps this has something to do with a failed apt-get upgrade I had yesterday...
[05:47] <ianorlyn> llogiq, ah did power run out during it?
[05:47] <llogiq> No. The java installer crashed it.
[05:48] <llogiq> I'm currently restarting the upgrade, maybe that'll help.
[05:50] <llogiq> It just stopped again.
[06:00] <llogiq> Apparently my network connection is a bit flaky and the java downloader just stops. I'm restarting it manually with dpkg --configure -a (as root)
[06:03] <llogiq> Yeah I got it working. No mouse cursor yet, though.
[06:07] <llogiq> brb.
[06:11] <llogiq> re. I got it to work by adding ``Option "HWCursor" "off"'' to my X11 config.
[09:37] <llogiq> cu folks.
[15:26] <sakang> anyone using the lxqt ppa?  the appearance is not working and desktop missing in the lxqt config
[19:41] <whouser> hi.  i am looking for a little assistance getting a better multi monitor solution.  I am currently using LXLE and ARandR for the multimonitor.  is there a better option?
[19:41] <whouser> please ping when you reply.  thanks in advance
[19:43] <ianorlin> whouser: is this a desktop or a laptop
[19:44] <whouser> laptop.  with a hdmi connected monitor
[19:44] <whouser> ianorlin:
[19:44] <ianorlin> arandr has an unxrandr command that can give you how to make that with a command line and you you could maybe make a keyboard shortcut if you connect to this monitor evry time you take your laptop home
[19:45] <ianorlin> or you could make a script that does the same thing
[19:46] <whouser> no it is connected and working
[19:46] <whouser> i was hoping for a better multi monitor soluition
[19:46] <ianorlin> better in what way?
[19:46] <whouser> ARandR seems to "square" the worksurface
[19:47] <whouser> not give two seperate work surfaces
[19:47] <whouser> and i cannot force the "main" desktop to the monitor i desire
[19:47] <ianorlin> whouser: you can you drag the rectangles to get two that way
[19:48] <ianorlin> and then press apply and you can change resolution by the menu
[19:56] <whouser> the resoluitions are fine
[19:56] <whouser> is there a image paste that is most agreeable
[19:56] <whouser> because it might be best to show you
[19:56] <whouser> but however one drage the monitors, the desktop 'squares' the outer outline
[19:56] <whouser> drags*
[19:57] <whouser> so if one orients the monitors vertically , and the upper monitor is 'wider' than the lower, the lowest right corner is off the visable screen
[19:59] <whouser> if you orient them left and right, the taller makes a unuseable uppercorner
[19:59] <whouser> ianorlin: