[08:09] <Eldunar> hello, can u tell me what wrong with my cairo-dock? When it apears it push bottom of windows currently oppened  up. ill give u screenshot. how to fix it? http://www.zimagez.com/zimage/przechwycenieobrazuekranu-12122014-090704.php
[08:17] <krytarik> Eldunar: How about that?: http://glx-dock.org/bg_topic.php?t=7840
[08:20] <Eldunar> thank u man:) have a nice day:)
[10:48] <_littleb> hi people, I have installed for vim some addons. Among some of them is the addon solarized and NERDtree in order to add some colors and usability to it. Now when i use vim in my semitransparent terminal all of it gets black only some characters in the nerdtree section stay transparent.
[10:48] <_littleb> Cam someone help??
[10:51] <brainwash> _littleb: did you already ask in #vim?
[10:51] <_littleb> no not yet I think it has to do with the transparency of the terminal
[10:52] <brainwash> uploading a screenshot could help to visualize the problem
[10:52] <brainwash> also, try a different terminal emulator
[10:52] <brainwash> I assume you are using xfce4-terminal
[10:54] <_littleb> that is true
[13:30] <xubuntu02w> Hello. I have a problem. Installed the newest xubuntu 32bit, but screen resolution is 640x480 and i cant change it, there are no additional drivers for GPU. When i start live it works, after install 640x480 and cant change
[13:32] <bekks> So which GPU do you have then?
[13:32] <xubuntu02w> some internal SIS
[13:32] <bekks> Oh, SIS. Good luck then.
[13:33] <xubuntu02w> it works good on live
[13:34] <xubuntu02w> and it works good after install linux mint
[13:34] <xubuntu151> hi
[14:38] <Wacky386> Im having problems with installing the nvidia drivers...using Xubuntu 14.04...anyone had this problem?
[14:39] <Wacky386> Ive tried running the installation script....it says that it cant find version.h (kernel headers not configured)
[14:39] <ObrienDave> you were here earlier this week
[14:39] <Wacky386> yup
[14:40] <Wacky386> tried doing what you said
[14:40] <Wacky386> didnt work out from the command line
[14:40] <Wacky386> got confused along the way :(
[14:40] <ObrienDave> http://ubuntuhandbook.org/index.php/2014/12/install-nvidia-340-65-ubuntu-1504/
[14:41] <ObrienDave> in case you need the link again
[14:41] <Wacky386> thank you...Im currently updating linux-generic, if that helps
[14:42] <ObrienDave> ok, once you get the kernel installed, reboot BEFORE installing anything else
[14:43] <Wacky386> will do
[14:44] <ObrienDave> you will have better luck asking in main ubuntu channel. more people there to help you. #ubuntu
[14:45] <Wacky386> ok...I though it was an xubuntu issue, will try in #ubuntu then
[14:46] <ObrienDave> naw, same core system, just different desktops
[14:46] <ObrienDave> there are other differences but none that would affect nvidia driver install, afaik
[14:49] <Wacky386> thank you, rebooting now
[14:51] <cziko> hello, I installed xdiagnose and i lost boot screen, is there any way to restore default booting with xubuntu logo and circle?
[15:02] <ObrienDave> i don't know. you might try asking in #ubuntu. more people there to help you
[17:09] <halpme> hi, im about to create a livecd in a usb stick to try n solve the wireless problem
[17:09] <halpme> I have a "clonezilla-live-20141208-utopic.iso
[17:10] <halpme> and a "xubuntu-14.10-desktop-amd64.iso"
[17:10] <halpme> which one do I choose?
[17:13] <bekks> Which one did you download?
[17:14] <halpme> bekks: both, apparently, but i chose the second one
[17:15] <halpme> will unetbooting be enough?
[17:15] <halpme> with what do I create a livecd?
[17:16] <drc> are you on linux or windows atm?
[17:17] <halpme> drc: linux
[17:18] <halpme> but given that my linux doesnt hae a working wireless connection im typing from a windows one. Windows only to communicate
[17:18] <drc> the either dd or unetbootin will work...choose wisely :)
[17:18] <Poisoned_Dragon> dd is a little bit advanced. requires you to triple check what you type.
[17:19] <halpme> is dd command line?
[17:19] <Poisoned_Dragon> Because, once you hit enter, it's final.
[17:19] <Poisoned_Dragon> in linux, yes.
[17:19] <drc> yup...I did say wisely, didn't I? :)
[17:20] <Poisoned_Dragon> Sadly, I'm finding unetbootin to be less useful than it use to be. Most isos can be dd'd to a usb stick.
[17:20] <halpme> ok, extracting and copying
[17:20]  * drc lost 2tb of data last week because he was distracted while using dd...good thing I have multiple backups
[17:20] <halpme> then ill have to reboot and change BIOS parameters to boot first from the usb stick, right? am I forgetting steps?
[17:20] <Poisoned_Dragon> And, the last time I used unetbootin, it made an arch install stick very angry.
[17:20] <Poisoned_Dragon> Wow, 2TB?!
[17:21] <drc> =halpme: external USB drive
[17:21] <Poisoned_Dragon> If your bios has a key for a boot menu, you won't have to change the bios at all.
[17:21] <Poisoned_Dragon> Most do now.
[17:21] <drc> data=video...forgot sdb1 was the data drive not the USB stick :)
[17:23] <drc> halpme: 1) create live USB, 2) attempt to boot from it, 3) if no go, then worry about changing BIOS.
[17:24] <halpme> beautiful splashscreen
[17:24] <drc> Don't over think it (doesn't help, I know from [sad] experience) :)
[17:25] <halpme> hope not to have made the same mistake
[17:28] <perfarator> Hi everybody!
[17:28] <perfarator> Please teach me how to clone and build from git...
[17:30] <halpme> right
[17:30] <halpme> booting from the livecd what I get is: failed to load COM32 file menu.c32
[17:30] <halpme> boot...
[17:30] <halpme> and it cycles
[17:32] <brainwash> perfarator: build what? Xfce -> http://docs.xfce.org/xfce/building
[17:36] <perfarator> brainwash, sources from github
[17:36] <holstein> perfarator: the sources should have directions.. i would ask for instruction from the creators
[17:41] <drc> halpme: Did you run the "test the media" (or whatever it's called) in the initial menu?  If not, re-boot and test.
[18:07] <halpme> drc: how do I test the mnedia?
[18:07] <holstein> !md5 | halpme
[18:07] <holstein> that tests the iso you download.. and there is a test in the menu..
[18:08] <holstein> https://help.ubuntu.com/community/Installation/CDIntegrityCheck
[18:08] <drc> halpme: As holstein said, md5sum tests the iso itself (before burning to the mecia).  I was talking about the menu item in the initial menu (upon boot) that tests the media <after> burning.
[18:08] <holstein> though, i wouldnt get to caught up in this, halpme .. you are trying to address support for an older b wifi use device.. and now, by trying to "fix' that, you are acutally just running into, and making more issues
[18:09] <holstein> this doesnt "fix" your wifi device, and as i said before, unless you have seen it functioning in a supported OS, it could be broken, and not a driver issue at all
[18:09] <drc> ah...the "over thinking" issue... holstein's right, listen to him :)
[18:10] <holstein> drc: it happens :) ..easy to overthink it.. or, just get side tracked
[18:10] <drc> It's hard to remember you mission was to fix the wifi when you're up to you butt in boot errors :)
[18:11] <halpme> holstein: im trying to install a version of xubuntu I know had wireless fuctions, (not install , but test from the livecd). If it works then its a problem in the newer os, am I wrong`?
[18:11] <holstein> halpme: you are not "wrong".. i think you are just assuming..
[18:12] <halpme> ok holstein , how do I proceed then? I though i was following what you suggested
[18:12] <holstein> halpme: even if, say, 14.04 doesnt support the wifi, and 12.04 does.. its still not really a problem in the newer OS.. and, it could be, support for that "legacy" device was dropped from the kernel.. and it also could be that, due to technical limiatations, it cant easily be added back in
[18:13] <holstein> halpme: i think, booting a newer 14.04 live cd, and as you said, an older one that you *know* works *is* a good idea.. but, i wouldnt get too caught up in doing so, since, its not fixing the wifi in any way
[18:13] <halpme> ouch
[18:13] <halpme> .....
[18:14] <holstein> when i run into an issue like that i want to 1. see the device run on a supported OS, or, on a live iso that i *know* supported it.. this tells me that the device is still functional, so i dont waste time troubleshooting a driver issue, if the hardawre is bad
[18:14] <halpme> i keep forgetting the wifi troubleshooting link. Please paste it again. There is a list somewhere in the link with supported wifi cards...
[18:14] <holstein> !wifi
[18:15] <holstein> though, a link for "legacy hardware" or "legacy wifi" would be more appropriate for you
[18:15] <holstein> i mean, these days, the wifi setup works like this.. plug it in, use it.. if its not like that, the, typically, its either *really* challenging to add support into the kernel, or, support is just not there for it
[18:16] <holstein> the other option in that case is, a proprietary firmware that is easy to add.. but, i dont think that is the case with that chipset
[18:17] <holstein> though, it wont hurt to identify the chipset.. last time you were looking, it (lsusb) didnt report, and gave some output that made me still think and suggest troubleshooting if the device is actually functional or not
[18:18] <holstein> and, also, thinking, realistically, about how much time you want to spend on a device of that age. an older b device.. when, you can typically find well supported (out of the box supported) g devices either *very* cheap, or free in many cases..
[18:22] <halpme> holstein: For chips that are not USB but included in the computer, type:  lspci -v  and read the last section. << does that change anything?
[18:23] <halpme> i have output for this one
[18:23] <holstein> halpme: sure.. you stated it was usb
[18:23] <halpme> holstein: sorry for that
[18:24] <holstein> halpme: i mean, run *both*. run literally anything that shows the device chipset
[18:24] <holstein> share the chipset, and we look for driver support
[18:28] <halpme> holstein: http://paste.ubuntu.com/9492413/
[18:30] <holstein> halpme: sure.. i dont see it there.. do you?
[18:30] <holstein> halpme: i do see a nice wired NIC
[18:30] <halpme> there is nothing wired atm
[18:31] <halpme> what is NIC?
[18:31] <genii> Network Interface Card
[18:31] <holstein> 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
[18:33] <halpme> so if I had wireless i should see the words "wireless" or "wifi" somewhere in that list. is that right?
[18:33] <holstein> halpme: you dont have to
[18:34] <holstein> halpme: the company that made that device never promised you linux support, so, it may not show there, or it may read as somethint differet.. but, i dont see anything there that shows a wifi device
[18:34] <halpme> ok,
[18:35] <holstein> halpme: so, if what you are saying is, its an internal wifi NIC, and not a usb device, i would be looking in the bios, making sure its on.. i would try *all* hardware switches and keyboard commands
[18:37] <halpme> holstein: holy ****, just now 3 wireless networks appeared
[18:37] <halpme> i dont know what did I do
[18:38] <drc> change anything in the bios?
[18:38] <halpme> drc: no, i pressed the f keys
[18:38] <halpme> and ctrl i believe
[18:39] <halpme> or alt gr
[18:40]  * drc would guess that pressing one/some of the F keys turned on the wifi (on my laptop its a slider on the front of the laptop).
[18:40] <halpme> i didnt know I could turn it off
[18:41] <drc> Unless holstein has a better idea, I'd reboot, and test the keys you pressed ONE AT A TIME to see what turned on the wifi.
[18:42] <drc> or read the manual to see if it says what turns the wifi on/off:)
[18:42] <halpme> i believe is f11, the key has a small icon that looks like an antenna
[18:43] <halpme> drc: i have no idea where to find the manual
[18:43] <drc> Then I'd press it again and see if the wifi turns off.
[18:44] <drc> halpme: google for you laptop model...lots of companies have their manuals in pdf nowadays.
[18:44] <halpme> curious
[18:44] <GrinchCube> halpme: its the same color? dont you have a fn key the same color than the antena icon?
[18:44]  * drc can't find his paper manual, but does nkow where his pdf version is.
[18:45] <halpme> the network applet shows 3 exisiting wifi networks, but neither firefox nor chromium show any results
[18:45] <halpme> o wait, this may be orivoxy+
[18:46] <drc> GrinchCube is correct. On my computer, there is a"fb" key at the bottom that when pressed with other keys does things (brightness, ertc)
[18:46] <drc> halpme: just because it shows them doesn't mean they are "connected"
[18:47] <GrinchCube> usually thers a light
[18:47] <GrinchCube> somewhere wiht the same icon
[18:47] <GrinchCube> that lights when its pressed
[18:49] <drc> a wifi light/LED that lights up when a wifi connection is made (not just a wifi available)?  Mine does.
[18:51] <halpme> ok, like 2 years ago I rerouted all traffic through privoxy via a modified /etc/environment file. exception I added is the university where I stud that grants students free wifi connections in campus
[18:52] <halpme> are there programms that override the changes I made?
[18:52] <halpme> false question
[18:52] <halpme> are there programs that ignore the environmental variables I establish with theis etc/environment file?
[18:54] <holstein> halpme: sure
[18:54] <holstein> halpme: but, what did you set? where? and why?
[19:00] <halpme> gtg
[19:00] <halpme> thanks a lot for all the help
[19:00] <halpme> today we solved an issue
[19:00] <halpme> more to come :D
[19:00] <halpme> tomorrow
[19:37] <halp> hi
[19:37] <halp> is there any command I can use to know the model of laptop I own?
[19:38] <holstein> halp: no.. but, you dont need that for any linux support
[19:38] <halp> :D
[19:38] <halp> sorry, im used to ask here
[19:38] <holstein> halp: what you need, as we discussed when looking for your wifi chipset, is the chipsets
[19:38] <halp> chipsets to know the model?
[19:38] <holstein> halp: you are not promised by the creators of that model that you get linux support, so, the model, though, helpful for searching, is not as important as the chipset
[19:39] <holstein> halp: for example, if hp makes a laptop with a wifi NIC in it, and changes chipsets, the model# stays the same, though, there can be, and often is, 2 or more differnt chipsets in that same model unit
[19:39] <holstein> so, the "best" thing to so, is, as the !wifi suggest, run lspci/lsusb, and look for chipsets, and search for support based on that information
[19:40] <halp> but holstein im not trying to do anything with the wifi (that now works), i just need to locate a pdf copy of my model
[19:41] <holstein> halp: sure. im just stating that, since you dont need that, for anything related to linux support, you may or may not need that.. and, nothing in linux will generate a .pdf like that
[19:41] <holstein> though, you are welcome to create one
[19:41] <halp> dont brain much today :D
[19:41] <halp> I
[19:42] <holstein> what are you looking for? the model information? it should be printed on the unit somewhere
[19:42] <drc> halp: inxi -M should give you the model of your laptop (it does mine)
[19:42] <drc> in a terminal
[19:42] <halp> thanks drc !!
[19:42] <holstein> wont hurt to try that ^ and you can copy paste it into a document which you switch to pdf
[19:43] <halp> my laptop is 5 years old
[19:43] <drc> holstein: I think he's looking for a pdf of his computer's manual.
[19:43] <holstein> drc: i agree
[19:44] <halp> thanks for writting that
[19:45] <halp> can I update the bios?
[19:45] <holstein> halp: nothing about xubuntu will prevent you from doing so
[19:46] <holstein> on a machine that old, i wouldnt bother.. unless something is specifically addressed.. i typically take an "if it aint broke" approach to the bios.. though, today, you can find serious vulnerabilities addressed in a bios update..
[19:47] <drc> It can be done (for my computer), but it can be fairly complicated (i.e., dl the new bios, burn to a bootable floppy, install bios....for my computer). You need to check your computer company's website to see if they support things like that.
[19:48] <holstein> sometimes they make a tool.. not often to be used from linux.. but, a tool that can be ran in the desktop OS
[19:48] <holstein> i would *never* try such a tool in wine
[19:48] <drc> and for an older computer, most companies don't bother with updating bios' unless there is a compelling reason/
[19:48] <drc> holstein: +1000
[19:48] <holstein> yup.. a 5 year old machine, i wouldnt bother.. even if it said there was a newer one.. unless something was broken
[19:50] <drc> My laptop is about about that old, and there has been one bios update (fairly early on for a security bug), nothing for the past 4 years.
[19:51] <halp> drc: better than here: not a single updaate in 5 years
[19:51] <holstein> halp: they dont promise those. its not part of the agreement.. and, there may be no need for a bios update
[19:52] <halp> today is being productive
[20:32] <quantibility> i use a lap top A8 vision AMD. i usually keep my battery out so i don't kill the battery cause its usally pluged in.. yesterday i kicked out the power cord for it on accident and for some strange reason the optical usb mouse just doesn't work anymore?? i haven't tested it on other places, the usb port seems to work fine, can someone please help?
[20:42] <holstein> quantibility: in the future, leave the battery in
[20:42] <holstein> quantibility: what i would do is, boot live iso's and try and see what exactly doesnt work, and why
[20:43] <Poisoned_Dragon> The battery is going to die, regardless of whether you use it, or not.
[20:43] <Poisoned_Dragon> Li-ion batteries age, whether stored or used. So, use it or lose it.
[20:43] <quantibility> alright, noted. thank you holstein, hope it works, but now i must find the darn cd.
[20:44] <holstein> quantibility: sounds to me like, you could have just damaged the USB..
[20:44] <quantibility> possible but how? unplugging it causes damage?
[20:44] <Poisoned_Dragon> is the optical mouse wireless?
[20:45] <quantibility> the usb is fine. im using a 32 gig stick for my HD.. working good.
[20:45] <holstein> quantibility: well, as they say, the first step is to admit you have a problem.. then ,we can move on to what exactly it is
[20:45] <quantibility> yes Poisoned_Dragon
[20:46] <Poisoned_Dragon> Maybe when you kicked out the charging cord, you also struck the usb radio stick.
[20:46] <holstein> i would check/change the batteries. or simlply go and check the mouse on different hardware
[20:46] <Poisoned_Dragon> If the stick no longer works in any usb port, I would suspect the stick is suspect.
[20:46] <Poisoned_Dragon> Oh yeah. What holstein said.
[20:47] <holstein> especially if you cant get it to work on multiple machines..
[20:47] <quantibility> holstein, i know im a bit of a big mouth can get a bit antsy but i genuinely have a problem and don't need sarcasm. thank you.
[20:47] <Poisoned_Dragon> It's not sarcasm. it's honest.
[20:47] <holstein> quantibility: not offering any.. and mean no harm. but you *do* have an issue with USB.. please try it with another machine
[20:47] <quantibility> radio stick? Poisoned its an optical wired mouse
[20:47] <holstein> quantibility: i am only volunteering here, and intend no harm at all...
[20:48] <quantibility> yeah if i had another machine
[20:48] <quantibility> its fine
[20:48] <Poisoned_Dragon> I asked you if the mouse was wireless. You said yes.
[20:48] <quantibility> just irritated
[20:48] <quantibility> i apolize its wired posioned
[20:48] <holstein> quantibility: if you find the device doesnt work on another machine, which, you can find *anywhere*, like a PC shop, or friend/neighbor, then, you can stop thinking its the OS or USB or machine, and know more about where the issue likely is
[20:48] <Poisoned_Dragon> If the mouse is wired, that's only increases the likelihood that the wire was damaged.
[20:49] <Poisoned_Dragon> When you kicked out the charger cord, did you kick out the mouse too?
[20:49] <Poisoned_Dragon> If so, could have cause a break in the wire.
[20:49] <quantibility> yeah but the power cored was the only thing that was yanked out i watched it come out... it hit nothing
[20:49] <holstein> again, *something* happened..
[20:49] <quantibility> no poisned the mouse and cored stayed exactly in their place.
[20:50] <Poisoned_Dragon> It doesn't take much to stress a wire. Even if the mouse was never unplugged, during the incident, the stress could have caused issues.
[20:50] <quantibility> ugh hold on ill find something real quick
[20:51] <Poisoned_Dragon> Sadly, usb cords aren't known for their tensile strength. :(
[20:51] <drc> Let's recap here: 1) USB wired optical mouse doesn't work, 2) USB port works (the 32 gig USB stick works there) Correct?
[20:52] <Poisoned_Dragon> So far, yes, drc.
[20:52] <drc> The only thing I can see to do is to try the mouse on another machine.
[20:53] <drc> I'm assuming (yes, I know) that there is not another USB mouse to test whatever software is used on that machine?
[20:58] <quantibility> nope no where to test it :(
[20:58] <drc> Here's a thought:  1) unplug mouse 2) open Removeable Drives and Media> Input media and check Auto run when USB mouse is connected  and enter "synclient TouchPadOff=1" in Command (this command works with my touchpad and USB optical mouse) 4) plug in mouse.  There should be popup balloons telling you a USB mouse was detected.
[20:58] <Poisoned_Dragon> Phone a friend and borrow access to their rig.
[20:59] <drc> That will tell you if the mouse is detected by the computer or not.
[21:00] <Poisoned_Dragon> Sounds like a plan
[21:00] <quantibility> hmm
[21:00] <quantibility> ok
[21:01] <quantibility> ill that
[21:01] <Poisoned_Dragon> Because, even if the mouse is receiving power, it could be that the data lines are damaged.
[21:01] <drc> Be aware this will turn off the touch pad, so I's open a teminal and input synclient TouchPadOff=0 BUT dont hit enter first.
[21:02]  * drc has a bad habit of tapping the touchpad when thinking, so it's necesssary to turn it off when using a mouse :)
[21:03] <Poisoned_Dragon> I can imagine the madness that follows.
[21:05] <quantibility> hmm
[21:05] <quantibility> brb restarting
[21:05] <drc> waiting with baited breath :)
[21:08] <drc> With my system (wireless optical mouse) plugging in the radio stick will activate the command, even with the mouse itself turned off.
[21:09] <Poisoned_Dragon> Well, that's normal
[21:09] <Poisoned_Dragon> the stick acts as a virtual mouse. it' just relays signals from the real thing.
[21:09] <drc> yup...just noting it.
[21:09] <drc> with a wired mouse, it shouldn't matter
[21:11]  * drc once had a dead battery in the mouse that took half an hour to diagnose...Never said I was quick on the uptake :)
[21:12] <Poisoned_Dragon> :D
[22:10] <halpme> im on a different part of campus now and the wifi is again undetected...
[22:12] <drc> Was it the F key?
[22:13] <halpme> apparently not. I have been testing combinations of f to not avail. What do I need if I want a better wifi coverage?
[22:13] <halpme> an antenna with a usb port?
[22:13] <halpme> whats it called?
[22:15] <drc> You want to replace your internal wifi with an external wifi system?  No idea, never bothered.
[22:15] <bazhang> an extender
[22:15] <halpme> no not replace
[22:15] <halpme> but maybe the inside-wifi is not powerful enough
[22:16] <bazhang> doubtful
[22:16] <drc> Doean't an extender just extend the wifi source, not the reciever (in the computer)
[22:16] <bazhang> yep, didnt fully read up
[22:17] <halpme> ill have to further test
[22:17]  * drc had that problem at home...then my daughter told me to stop being so cheap and but one that really worked well :)
[22:17] <bazhang> I read inside as indoors, what he meant was integrated
[22:18] <drc> s/but/buy/
[22:19] <drc> But that may be part of his problem, the source of his first wifi was not sufficiently powerful enough so when he moved to another source it was...and voila...wifi :)
[22:21] <drc> laters all
[22:21] <halpme> if everyone is getting wifi, even students with crapple computers, then i need to get a better antenna
[22:22] <bazhang> or associate correctly with the existing networks
[22:26] <quantibility> problem solved
[22:26] <quantibility> i have to get a new mouse. its broke.