[03:09] <xubuntu44w> Hello world ! Just playin, I would like a minamal CD/ network install of xubuntu for an older pc.
[03:10] <xangua> !minimal
[03:18] <xubuntu44w> Yea I found that I have tried the 12.04 and it froze at boot, so hell I'm going to try 13.1. What I don't get is why ubuntu's minamal would also install xubuntu? Just sayin.
[03:20] <xangua> ubuntu 13.10 is not supported
[03:21] <xubuntu44w> Well 12.04 didn't load...Any suggestions?
[03:22] <xubuntu44w> Not even as a terminal install. Darn wheres my xp disk. HaHaHa
[03:45] <Finetundra> i am unable to unmute my audio
[03:49] <xubuntu44w> geez I am a newbie but whats the specs on your machine and os finetundra ?
[03:49] <Finetundra> xubuntu44w, how is that relevant?
[03:50] <xubuntu44w> And I said geez because the linux cummunity is supposed to help each other
[03:50] <Finetundra> xubuntu44w, that's why i'm here
[03:50] <ObrienDave> we help with specific issues and questions
[03:51] <Finetundra> ObrienDave, i don't think i can make that anymore specific
[03:51] <holstein> Finetundra: i would check the keyboard mute.. and toggle the one in the mixer volume control.. also, check alsamixer from the terminal. and pavucontrol if nothing there helps
[03:51] <xubuntu44w> and it is relevent. At least if I can help.
[03:53] <Finetundra> holstein, i've tried keyboard toggel and toggeling in the mixer, neither worked, and nothing reads as muted.
[03:53] <holstein> Finetundra: sure.. toggle *everything* though...
[03:53] <Finetundra> holstein, correction, it reads as muted in the mixer
[03:53] <Finetundra> holstein, i have, that's the issue
[03:54] <holstein> Finetundra: i would start with the basics then.. see if the device is functioning properly.. with a live CD or a supported operating system.. then i would test with another user to rule out my users config.. i would try pavucontrol if you have not
[03:54] <holstein> !info pavucontrol
[03:56] <Finetundra> ok holstein, i'll switch to a guest account for a sec
[04:00] <Finetundra> holstein, audio works in guest session, i still cannot unmute from user account
[04:01] <holstein> Finetundra: then, at least you know where the issue is.. so you know the device works, and you dont need to reinstall applications or mess with the system
[04:01] <Finetundra> holstein, well that's a minor relief
[04:01] <ObrienDave> permissions or group privileges perhaps?
[04:02] <holstein> i think its just a bad config issue.. i would just move them temporarily, and see if the issue persists and go from there..
[04:04] <Finetundra> ObrienDave, never even thought that could be an issue, but "use audio devices" is unchecked in my user permissions
[04:04] <holstein> that could do it..
[04:04] <Finetundra> ObrienDave, now how do i have it stay checked
[04:05] <holstein> could have been something you added that changed that for some reason
[04:06] <Finetundra> haven't added anything unusual for a fresh install. everything i have added is stuff i usually install off the bat and none of it has ever caused a problem
[04:07] <ObrienDave> Finetundra, go ahead and check it, then you might have to right click on the top bar and "move" the window up to see the ok box
[04:08] <holstein> as they say, the first step is to adimit you have a problem.. then, you can look for what caused the issue..
[04:08] <ObrienDave> that window shows up as 900 pixels high on a 768 pixel screen LOL
[04:08] <ObrienDave> my laptop that is :)
[04:09] <Finetundra> after doing that, i still can't unmute the blasted thing
[04:09] <Finetundra> do i need to log out then back in?
[04:09] <holstein> Finetundra: i would.. just to be sure
[04:09] <ObrienDave> not sure
[04:09] <Finetundra> ok, back in a sec
[04:09] <holstein> i do in the command line.. never ticked boxes for it..
[04:10] <Finetundra> it also takes a long time to log out for some reason
[04:10] <ObrienDave> saving a lot of things
[04:12] <Finetundra> so, does anyone have a clue WHY it removed that permission?
[04:13] <holstein> Finetundra: it?
[04:13] <ObrienDave> not sure if it was always off on mine but at some time something actually paid attention to it. if that makes sense. *moar beer*
[04:14] <holstein> Finetundra: i had stated something you have installed could have changed that.. you could have any thing from bad hardware to misconfiguration to a bug related to your specific hardware somehow..
[04:14] <cfhowlett> ObrienDave, "moar beer" needs root level permission ...
[04:15] <ObrienDave> i'll work on that immediately, SIR! ;P
[04:15] <Finetundra> holstein, i was refering to any other thing it could have been
[04:15] <ObrienDave> *chuckels on his way to the fridge*
[04:16] <holstein> Finetundra: sure.. thats why i stated a few more things above..such as a bad or failing hard drive or memory.. but i dont think thats what you are having
[04:17] <Finetundra> holstein, i would be a bit ticked if it was a failing hard drive as i bought this one not but 2 or so weeks ago
[04:17] <holstein> Finetundra: i dont think it is, as i said.. but, hard drives are more likely to fail when new
[04:18] <Finetundra> holstein, really? where's the sense in that
[04:19] <holstein> Finetundra: its just a fact.. you can read up on it.. they are most likely to fail when new, or of course, after use
[04:19] <ObrienDave> that's the idea behind a "burn-in"
[04:19] <holstein> yup.. if they dont do a burn in..
[04:19] <holstein> manufacturing errors, which happen, can make new hard drives more likely to fail
[04:20] <Finetundra> i don't know why, but that makes sense
[04:20] <ObrienDave> most new devices fail, if they're going to, fairly quickly. hence the reason for 24 hour, 1 week, and longer burn in times
[04:21] <Finetundra> gotcha
[04:21] <ObrienDave> every new computer i buy stays on for the 1st 2 week constantly
[04:22] <Finetundra> that's something i've never heard of someone doing.
[04:22] <ObrienDave> i also run stress tests so CPU, GPU and HDDs run close to 100%
[04:23] <Finetundra> once again, never heard of someone doing that
[04:25] <ObrienDave> most people don't go that long. i like to make sure it's not going to fail soon
[04:25] <Finetundra> better safe than sorry
[04:27] <ObrienDave> in my case, too broke to buy another ;P
[04:36] <Finetundra> but aren't you  worried about breaking it in the process, ObrienDave?
[04:42] <ObrienDave> it would still be under warranty :)
[06:04] <__unik> hi guys. how can I change the font color in top panel?
[06:05] <__unik> it's grey why the panel is black. so confusing
[06:05] <__unik> while*
[08:39] <psean> hey all having problems with install keep getting /dev/sda uid error on boot i have tried installing on full hard drive and making a /boot partition but keep getting same error i have looked on website but nothing works
[10:27] <dudufuka> Hello my name Heinz
[10:28] <wlxmhls> hi
[11:55] <pjotter> good afternoon everybody
[11:56] <pjotter> I have a question concerning themes in 14.04
[11:56] <cfhowlett> !ask
[11:57] <pjotter> I recently upgraded from 12.04 to 14.04. One thing I noticed, is that the right-scrollbar (for example in firefox) has changed.
[11:58] <pjotter> When I use firefox inmaximized mode and try to use the right scrollbar, I often misclick because the right pixels do not register as a click on the scrollbars.
[11:59] <pjotter> This used to be different. When you woul take your mouse to the utmost rightside of a maximesed application, it would always be on the scrollbar. But now, it seems, this isn't the case anymore.
[11:59] <pjotter> I tried selecting a different theme but with not much succes.
[12:00] <pjotter> Does anybody know a good theme for 14.04 in which the scrollbars work like in 12.04?
[12:03] <pjotter> This is my exact problem: http://ubuntuforums.org/showthread.php?t=1859187
[14:18] <xubuntu103> hello, i'm a new user. After searching the internet it should be possible to install xubuntu on a usb stick and to run it from the stick as a normal os.
[14:19] <xubuntu103> Is it correct? my harddrive is broken and I wand to use a usb-stick instead of a new harddisk
[14:19] <cfhowlett> !persistence | xubuntu103, yes.  i
[14:19] <cfhowlett> xubuntu103, it will be unstable and delicate and likely to break.
[14:22] <xubuntu103> cfhowlett, thanks for this hint, but I have a quite old laptop and itś nearly impossible to find a new harddisk.
[14:22] <xubuntu103> therefor my idea was to use a usb stick a harddisk
[14:25] <xubuntu103> each time when I try to install I get this error message
[14:25] <cfhowlett> xubuntu103, I didn't say DON'T do a USB install ... just be aware
[14:25] <xubuntu103> errno5 Input/output error
[14:26] <xubuntu103> ffhowlett, I know and thanks for your advice ;-)
[14:27] <xubuntu103> does the error mean that my source has an error?
[14:27] <cfhowlett> xubuntu103, easy to test: change usb's.  they do break
[14:27] <xubuntu103>  cfhowlett the usb is brand new and I got the message also when I tried to install on my harddrive
[14:28] <xubuntu103> before the harddrive broke ;-)
[14:28] <cfhowlett> xubuntu103, BEFORE the HDD broke?  not good
[14:29] <xubuntu103> yes before
[14:29] <xubuntu103> I will try to boot from DVD and try to install that way
[14:33] <xubuntu103> exit
[14:48] <Finetundra> how do i prevent the volume from shooting up when i put headphones in?
[14:49] <xubuntu840> hello, instead of searching every prompt I hope you can help me here :-)
[14:50] <cfhowlett> !details | xubuntu840
[14:50] <xubuntu840> I will format my usb-stick and rename it. What is the corect sentence in the terminal window
[14:52] <Finetundra> xubuntu840, if i may ask, why are you formatting the usb?
[14:52] <xubuntu840> finetundra: to have it clean :-) or can I only rename it?
[14:53] <xubuntu840> for the momemt the name of the usb-device is quite chrytical
[14:53] <xubuntu840> chryptical
[14:54] <Finetundra> xubuntu840, you could try to use gparted to format it i believe. someone correct me if i'm wrong
[14:54] <xubuntu840> I quess gparted is a small utility? And not included in Xubuntu?
[14:55] <Finetundra> it's easy to find in the software center
[14:55] <Segger> could probably use fdisk or mkfs
[14:55] <Segger> but i'd just use gparted
[14:56] <xubuntu840> OK, thanks for your help. Will try gparted
[14:59] <xubuntu840> ok, i found it by I can only use it as an administrator. I started Xubuntu directly frum USB-Stick for trying. So how to get admin-rights?
[15:00] <cfhowlett> xubuntu840, sudo gparted from a terminal
[19:17] <longbonglungfish> hey all. on xubuntu 14.04 here. noticed a strange inconsistency when i close my laptop lid that wasn't there on 13.10. upon closing the lid in 13.10, my laptop would go into suspend and when i'd reopen the lid, it would prompt me for my login credentials. now, when i close the laptop lid and come back to reopen it, it goes straight to the desktop without prompting for login information. anyone know how to fix this?
[19:24] <brainwash> longbonglungfish: verify that light-locker is set up properly (settings manager > light locker settings)
[19:25] <brainwash> there is an option named "lock on suspend"
[19:26] <longbonglungfish> brainwash: i use xscreensaver. i have that set up to lock screen after one minute. have waited longer than that and still no prompt when i open the lid. also in power manager i have lock screen for suspend enabled, and in session and startup setting i have lock screen before sleep enabled.
[19:31] <brainwash> does it lock the screen if you trigger suspend via the menu?
[19:31] <longbonglungfish> yes! that works perfectly.
[19:33] <brainwash> you could try this: open /etc/systemd/logind.conf with a text editor and change "#HandleLidSwitch=suspend" to "HandleLidSwitch=ignore"
[19:33] <longbonglungfish> brainwash: i read that could be an issue. i'll change it now and report back.
[19:33] <brainwash> alright
[19:35] <nomic> also power management
[19:35] <nomic> not just 'light locker'
[19:35] <nomic> power settings .. suspend on laptop close
[19:42] <longbonglungfish> brainwash: i changed that setting and now there is no suspension at all when closing the lid.
[19:43] <brainwash> that's bad, the power manager should be in control now
[19:43] <brainwash> are the power manager settings ok?
[19:43] <longbonglungfish> yup, as far as i can see.
[19:44] <longbonglungfish> does it change anything that i use this ppa: https://launchpad.net/~xubuntu-dev/+archive/ubuntu/ppa
[19:45] <brainwash> well, you should have told us from the start that you use this PPA
[19:45] <longbonglungfish> sorry!
[19:46] <longbonglungfish> does their xfce power manager build cause some conflicts i'm not aware of?
[19:46] <brainwash> I don't think so
[19:46] <brainwash> there is a known bug, bug 1307545
[19:47] <brainwash> which describes your current problem
[19:47] <longbonglungfish> shoot. but the workaround doesn't seem to work either :\
[19:48] <nomic> dunno what ppa is
[19:48] <dzho> personal package archive
[19:49] <brainwash> longbonglungfish: lets try this.. run the command "xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s false"
[19:49] <brainwash> this command changes a hidden setting
[19:51] <longbonglungfish> okay. done. should i restart again? should i remove the change i made to the systemd file before?
[19:52] <brainwash> relog and don't revert the logind.conf change
[19:52] <longbonglungfish> okay. be right back.
[19:54] <longbonglungfish> brainwash: no luck
[19:54] <brainwash> bummer
[19:54] <brainwash> how about using a logind compatible screen locker like light-locker or gnome-screensaver?
[20:07] <longbonglungfish> brainwash: problem fixed! have lock screen before suspend enabled in power manager and session settings. added the following line to /etc/systemd/logind.conf "LidSwitchIgnoreInhibited=no" and changed the value for the setting you gave me to "true" (xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -s true). now it all works as it should!
[20:08] <brainwash> great :)
[20:08] <brainwash> really confusing stuff
[20:09] <longbonglungfish> tell me about it! thanks for the help. you got me 9/10ths of the way there.
[20:09] <brainwash> you're welcome
[21:48] <GridCube> how do i fake a dependency? i get this, "Dependency is not satisfiable: libltdl3 (>= 1.5.2-2)" but ubuntu only has libltdl7, thats suppose to replace it
[22:05] <GridCube> nevermind
[22:06] <GridCube> there is a version of the software for 7 lib P:
[22:07] <Unit193> API differences, not exactly "replace".
[22:11] <GridCube> P: great, now the scanner is detected, but doesnt work, probably i need to wait or reboot or something, i've heard thats the case with many scanners
[22:25] <diogo_79> hi
[22:41] <mo0p> Hello