/srv/irclogs.ubuntu.com/2014/11/12/#lubuntu.txt

Steven-erm.. i have no sound and tried to follow a hand full of different sound troublshooting tutorials out there to no avail. I'm not sure how to go about fixing it.00:39
Steven-any sugggestions00:39
Steven-It was working then somthing happend00:40
Steven-Shockwave flash also stopped working00:42
=== IdleOne is now known as PopsNClicks
holstein!audio | Steven-03:33
ubottuSteven-: If you're having problems with sound, click the Volume applet, then Sound Preferences, and check your Volume, Hardware, Input, and Output settings.  If that fails, see https://help.ubuntu.com/community/Sound - https://help.ubuntu.com/community/SoundTroubleshooting - http://alsa.opensrc.org/DmixPlugin - For playing audio files,  see !players and !mp3.03:33
holsteinSteven-: i would just elaboarate.. *what* specifically happened? when? and how?03:33
holsteinSteven-: remove flash from the euqation, since, adobe doesnt provide a current linux version03:34
holsteinhttp://www.adobe.com/software/flash/about/ you can use the chrome browser, which adobe provides a current version of flash for.. you can use that flash with chromium03:35
Unit193Lubuntu comes only with alsa by default, if sound never worked you can try pulse.03:37
Unit193!info pepperflashplugin-nonfree03:37
ubottupepperflashplugin-nonfree (source: pepperflashplugin-nonfree): Pepper Flash Player - browser plugin. In component multiverse, is optional. Version 1.7ubuntu1 (utopic), package size 10 kB, installed size 69 kB (Only available for i386; amd64)03:37
=== PopsNClicks is now known as IdleOne
Steven-Sound worked then I must have broke it. I couldn04:00
Steven-I couldn't tell you what software I was installing or what I was doing to break it04:01
Steven-lol04:01
holsteinSteven-: ok.. then, i suggest you back up and reinstall04:01
holsteinSteven-: try and keep notes on what commands you run, and why.. and what packages you install, or PPA's04:02
Steven-I'll think I'll go without sound04:02
holsteincool.. enjoy!04:02
holsteinthere are a couple easy tips at that link above ^04:02
holsteinlspci or lsusb to see the interface.. then, aplay -l04:02
holsteinthose in a terminal.. then, check alsamixer to make sure all is up or at an expected level04:03
holsteincheck the bios.. test the hardware with a supported operating system.. try a live CD.. see if the hardware is working properly04:03
Steven-hw is fine04:03
Steven-checking out the linl04:04
Steven-link04:04
holsteinSteven-: sure.. just dont assume the hardware is fine. actually try and test it, otherwise, you can be wasting time trying to address a hardware problem in software04:05
holsteini only say this becuase i have done it at least a half-dozen times.. and a few times with audio devices..04:05
Steven-I did a live cd to check it04:05
Steven-i think im having permission errors04:06
holsteinSteven-: what makes you think that? you can try playing audio as a new user, or the guest user.. please dont test audio with the web browser..04:07
Steven-**** List of PLAYBACK Hardware Devices ****04:07
Steven-Home directory not accessible: Permission denied04:07
Steven-what returns after  sudo aplay -l04:08
holsteinSteven-: who said sudo?04:08
Steven-https://help.ubuntu.com/community/SoundTroubleshooting04:08
holsteinanyways.. you'll be able to see if you have devices to playback on using "aplay -l".. and you can test as another user04:09
holsteinthat will troubleshoot your user permisions vs the hardware/software config04:09
Steven-ya I guess I wasn't supposed to use sudo lol04:10
Steven-holstein, the command to refresh/reinstall the drivers on the ubuntu wiki used aptitude. Should I install that and use that instead of apt-get?04:16
holsteinSteven-: you shouldnt have any drivers you have installed for the audio04:23
holsteinSteven-: the kernel is modular, and just has drivers basically "baked" into it.. and you didnt add any to make it work, so you should need to mess wit hthat04:23
holsteinSteven-: it would be helpful to know what you did before this happened.. like, a kernel update, or adding a PPA, or whatever.. you can easily try booting the older kernel from grub, and running the guest account and checking the audio04:24
Steven-I could probably try that04:27
holsteincould? no.. you can easily try all of those, if you feel it will help you figure out what is up with your system04:27
Steven-I did  upgrade from 14.04 LTS to 14.10 to see if that would fix it04:27
holsteinSteven-: i suggest a fresh install of 14.04, after backing up, since, you should have a backup regardless04:28
holsteinits likely something with the user account, and is a common element between the 2 versions..04:28
Steven-ya I got a back up and will likely reinstall later. Was just trying to see if I could figure out how to fix it04:29
holsteindoes it work as another user?04:29
Steven-I only have one user. can I just create a new user to test?04:30
holsteinSteven-: there is a guest user04:30
holsteinSteven-: you can create one if you like..04:30
Steven-Holstein I appreciate the time and help. Will have to work on it tomorrow.04:47
|aaroni have a really old dell (2003) with an intel integrated "3d extreme graphics". any chance of getting this to work?07:08
|aaronso the answer is YES! booted up fine!07:50
Garbonzohi all, was just installing on a virtualbox vm and this is what the installer looked like! http://picpaste.com/what-have-you-done-to-me-lenny-VbyMkJAc.png10:37
dkesselGarbonzo: switch to vt1 using crtl+alt+f1, then switch back to vt7 using ctrl+alt+f710:42
Garbonzodkessel: thanks, good tip. was just checking dmesg in vt1 when you suggested that! now have a desktop... any idea what caused the screenburp?10:44
dkesselor, in virtualbox that often is right ctrl+f1, then right ctrl+f710:44
dkesselGarbonzo: it's a known issue with virtualbox10:44
Garbonzoah, ok. likely to carry over from the live cd or will i be ok on install? had 14.04 working perfectly in virtualbox until i went too far playing with lxqt -- shame to have to vt each boot...10:45
dkesselGarbonzo: if i remember correctly it is gone after installation10:47
Garbonzodkessel: great, thanks. halfway through install so i'll see what happens10:47
Garbonzodkessel: all working fine in new vm, thanks11:00
dkesselGarbonzo: you're welcome :)11:01
fastedHi everyone.20:50
fastedI am running ubuntu 14.04, and have just installed lubuntu-desktop.20:51
fastedI need help with turning capslock to control.20:52
fastedThis works for me: xmodmap -e 'clear Lock'20:53
fastedxmodmap -e 'keycode 0x42 = Control_R'20:53
fastedxmodmap -e 'add Control = Control_R'20:53
fastedBut how do I make it permanent?20:54
testdrfasted: there is no way to make it permanent - you have to set it every time in your session - if you do the setting systemwide, then you have to ensure that no other thing (like x11-keymapping etc.) makes any changes21:00
fastedOk, can I make it happen automatically whenever I start a new session?21:01
testdrfasted: you have to try (i dont use this and wont test it for you): one way is to set it systemwide in an init-script (probably that runs after start of keyboard initialization - for example in /etc/rc2.d    but if anything later changes the keyboardsettings, then it has to be done after this or the changes have to be disabled (for example in the language-keyboard-setting lxpanel-icon)21:08
fastedtestdr: ok, thank you21:31

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