On my Mint install it is in /usr/bin/lspci. Try in a terminal: whereis lspci to locate it.

Which Desktop environment do you have? The gedit text editor used to be fairly standard with Ubuntu/Mint but depending upon the Desktop you are using, it could be a different text editor if you use Mate than if you use Cinnamon or another Desktop.

1 members found this post helpful.

Gedit is either not installed at all, or not properly installed. If you have another text-editor then just replace "gedit" in the commands, with the name of your text-editor.

If you think you should have Gedit in your system and that it is the text-editor you want to use, then do this. In terminal(without quotes):


"sudo apt-get update && sudo apt-get install --reinstall gedit"

As for usb wifi-adapters, they are a struggle even for more advanced users. No wonder you are struggling. There are lots of dongles that simply doesn't work in linux, at least not out of the box. Are I correct in assuming that the usb wifi issue is solved? If that's the case, so thumbs up. Well done! Patience will get you there. Always

gedit is the GNOME Desktop Manager default text editor

if you do not have GNOME installed then gedit is not installed



as to frustration

i guess i missed most of that

by 2003 ( on Windows-XP ) i was building software using Visual Studio and and building LINUX programs in MinGW ( blodeshed DevC++) and building Windows *.exe ports of the linux programs


so by 2005 the full move to linux was rather easy


it took you HOW LONG ???? to learn your way around MS Windows ?
( linux dose NOT!!! use any HKEY_* registry funkiness)

it WILL take you a bit of time to LEARN a NEW way of doing things

It took me a while to get used to using Linux. I started using Ubuntu a few years ago, at the time it was the easiest looking distro I knew about. I remember having many a night batting my head against a wall trying to figure out how things worked, the command line, etc. etc. It wasn't fun but I didn't stop and now have little use for Windows except when I'm at work (funny thing about university libraries they don't really use much else).

Here is a site that helped me out: http://cli.learncodethehardway.org/book/
This will not help you learn how to use apt-get, aptitude, dpkg, or anything else along those lines. I'm not sure where your command line skills are (I know my were non-existent at first) and this website gave me a decent foundation.

It may not be a popular suggestion but perhaps you should just get used to the way the whole system works graphically before diving into the command line. For example: learn how to install programs via synaptic or the software center or graphical versions of text editors...things like that.

Good luck to you

Thanks guys that info was awesome. I'm still around just got courses on coding and also doing courses for certification at work so can't hit forums much. My Linux box is still running and the commands "which" and "locate" will be added to my list of commands I'm trying to learn. I've got a sheet by Minty (my box lol) and I intend to run them all to become a little more aquainted with what they do and their use. Haha I deal with those Windows errors daily so I hear you. I work in a company that is 95% Windows and I'm in the IT department so I have become pretty good at figuring out those cryptic 0x00007a etc. ridiculous errors.

Thanks for the link I've bookmarked it and will go through it for sure. I believe I'm running the KDE desktop. This is good info and as a noob it's great to have.