Archive for the ‘HowTo’ Category
When trying to install Gnome Planner ( http://live.gnome.org/Planner ) in Arch Linux, I came across this error:
Error:
/usr/bin/pygobject-codegen-2.0: line 11: /usr/bin/python2: No such file or directory
make[2]: *** [planner.c] Error 127
make[2]: Leaving directory `/home/alex/Desktop/planner-0.14.4/python'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/alex/Desktop/planner-0.14.4'
make: *** [all] Error 2
To fix this, I made a symbolic link from /usr/bin/python2.7 to /usr/bin/python2, this should work with other similar errors involving missing python2 file.
sudo ln -s /usr/bin/python2.7 /usr/bin/python2
Once you have made the made the symbolic link continue to make and install the program as usual.
After my installation of Arch Linux I had some trouble using my wifi card which was working while I was running the live CD. What was strange was that the card would show up in iwconfig and ifconfig -a but not ifconfig It turns out I needed to install the wireless drivers and here’s how I did it:
Error:
ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
dhcpcd wlan0
dhcpcd: version .2.2 starting
dhcpcd: wlan0: up_interface: No such file or directory
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
Find out what card you are using:
lspci | grep Network
04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Install: iwlwifi-3945-ucode-15.32.2.9-2-any.pkg.tar.gz
If you don’t have access to a wired connection, check out this guide to installing packages from the Arch Linux cd.
Once you get it up and running, updating via pacman (-Syu) will probably replace these drivers for newer ones which continue to work.
Okay, so you have Arch Linux installed and let’s say you’re wifi isn’t working and you need the package “iwlwifi-3945-ucode-15.32.2.9-2-any.pkg.tar.gz” to fix this but you don’t have a wired connect. What do you do? Blast in your Arch cd, mount it, mount the packages sqfs file and install using pacman.
Mount cdrom:
mkdir /mnt/cdrom/
mount /dev/cdrom /mnt/cdrom/
Mount *-pkgs.sqfs:
mkdir /mnt/pkgs/
mount -o loop core-pkgs.sqfs /mnt/pkgs/
cd /mnt/pkgs/
Install pkg.tar.gz:
pacman -U package-name.pkg.tar.gz
If you’re running off a live USB disk or changing your graphics card the error below might appear when Xorg is looking for the wrong drivers or device. You might also get this error while using the Nvidia drivers, I found however this was caused by some of the extra options added into the xorg.conf file (usually located /etc/X11/xorg.conf). If the case is that it’s a problem with the aditional options I suggest making a backup of the file and attempting to comment out (#) aditional options, this will need a bit more of an expert eye to see what isn’t needed though.. You can also use the following to rollback to a working version when using the Nvidia drivers.
There is a pretty simple fix, if it is caused by broken or changed xorg.conf file:
Fix:
Make a backup of your current Xorg.conf, just in case something goes even more wrong and it can be easily restored:
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.bckup
Now you’ll want to restore the failsafe (sometimes called xorg.conf.backup) config to be used as the default:
sudo cp /etc/X11/xorg.conf.failsafe /etc/X11/xorg.conf
Yeah, it was that simple (if this error was caused by a broken or changed xorg.conf anyway. So you can continue and start the x server with:
startx
Error:
X.Org X Server 1.9.0
Release Date: 2010-08-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-27-server i686 Ubuntu
Current Operating System: Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686
Kernel command line: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
Build Date: 16 September 2010 05:39:22PM
xorg-server 2:1.9.0-0ubuntu7 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.18.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 4 11:35:54 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) No devices detected.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
So, you’ve created an awesome Live USB Linux stick with a persistence file which let’s you boot anywhere and carry all your sweet sweet datas around on it too. If you want to see those files in Linux on your desktop or laptop outside the USB you’re going to have to mount the loop device (the casper-rw file) somewhere first. The following commands show how to make a folder and mount the loop and then unmount it too.
Just change the /media/USB/ for the mounted location of your mounted USB stick which contains the casper-rw file you want to view the contents of and the /home/alex/caspermnt/ for the mount point on your system.
Mount:
mkdir ~/caspermnt
sudo mount -o loop /media/USB/casper-rw /home/alex/caspermnt/
Unmount:
sudo umount ~/caspermnt/
This can be useful for recovering data from a borked Live USB stick or for backing up your files on your computer just to be sure.
If you’re getting this error but you’re still connected to the internet this page might help. This error is sometimes caused by repository’s which are down or broken.
Failed to download repository information
Check your Internet connection.
From terminal run the following command:
sudo apt-get update
If the output runs through a few repositorys but ends with something similar to the below (most probably with different repositorys failing) and ultimately stopping your updating process then there is a good chance you can fix it by just removing those failing sources from the software sources.
Err http://ppa.launchpad.net maverick/main Sources
404 Not Found
Err http://ppa.launchpad.net maverick/main amd64 Packages
404 Not Found
W: Failed to fetch http://ppa.launchpad.net/bugs-sehe/gparted/ubuntu/dists/maverick/main/source/Sources.gz 404 Not Found
W: Failed to fetch http://ppa.launchpad.net/bugs-sehe/gparted/ubuntu/dists/maverick/main/binary-amd64/Packages.gz 404 Not Found
E: Some index files failed to download, they have been ignored, or old ones used instead.
Software Sources can be found under either:
Applications > Ubuntu Software Centre > Edit > Software Sources..
OR
System > Administrator > Synaptic Package Manager > Settings > Repositorys
Click the Other Software tab.
Nnow find the repositories which caused the failure on the update and uncheck them and then close the Software Centre.
Re-run the update command and hopefully everything will work!
sudo apt-get update
Check the example below where gparted was causing the error:
Having gone through several upgrades and countless repository’s added to the software sources, things can begin to get really messy really quickly and often begin to screw up when updating the system if you’re not careful. You may find yourself, like I have, wanting to restore your sources.list file back to its default in order to get things working again.
In order to do this there is a pretty handy webapp available called the “Ubuntu Sources List Generator” - http://repogen.simplylinux.ch/
By moving through each section it enables you to select your country, release and then check each repository you want to add, not only does it support all the official ones for things like security and updates, it also allows for 3rd party repos such as Banshee, Chromium, Conky and VLC amongst a bunch others. Once you have what you want hit generate and it’ll create a nice, comment, new sources.list file ready for you to replace your old one with.
You may want to backup your old sources.list just in case with the following command:
sudo cp /etc/apt/sources.list /etc/apt/sources.list.bkup
Once you have that you can open the sources.list and simply paste the new one in from the repogen:
sudo gedit /etc/apt/sources.list
Paste, Save and Close the file and now you should paste the generated GPG keys, found just below the generated sources.list file, into your terminal.
Everything should be back to default and allow you to once again update everything.
Attempting Boot From USB Device
SYSLINUX 3.63 Debian-2008-07-15 EBIOS Copyright (C) 1994-2008 H. Peter Anvin
Unknown keyword in configuration file.
boot:
_
After creating a USB bootable version of Ubuntu from the Startup Disk Creator (or usb-creator-gtk) and attempting to boot, I was greeted by the error above. It might look a bit scary but it’s really easy to fix, just plug the USB flash drive into a computer (windows or linux, mac too probably but I haven’t tried that.)
Solution 1:
- Open the the syslinux folder in the root of the flash drive.
- Inside is a file called syslinux.cfg you’ll want to edit that.
- Find the line “ui gfxboot bootlogo” and simply remove the “ui “.
- Save and try booting again.
Below is how my syslinux.cfg file looks after editing:
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 50
gfxboot bootlogo
Solution 2
Alternatively it looks as though there is another way of fixing this issue if there is no “ui” in the file, this is to do as followed (as pointed out in the comments below):
- Type “help” and press enter
- Hit Enter again
This should boot correctly and shouldn’t need to be done every time.
With the latest update of Android “Froyo”, it’s now possible to take screenshots/screen captures without the need to be plugged into a computer, mess around with the Android SDK or Root your phone. You are easily able to take screenshots of the home screen and while in any app. I have only been able to test this with a Samsung Galaxy S (I9000-GT) running
Froyo so comment on your results.
Here’s how to take a screenshot in Froyo:
Hold down Back and then press the Home button.
You should now see a pop-up near the bottom saying “Screen captured. Saved as image file” as in the following image. The files will be saved to a folder named ScreenCapture in your home directory as a .PNG.
By holding down the Back button it doesn’t actually go back if held down, it waits for you to press Home. After a few seconds of holding it down however(I can’t quite figure it out) pressing Home will continue the “going back” operation as if the Back button was tapped.
E: Type ‘n’ is not known on line 2 in source list /etc/apt/sources.list.d/bean123ch-burg-lucid.list
E: The list of sources could not be read.
To fix this or similar errors open the file, for example “/etc/apt/sources.list.d/bean123ch-burg-lucid.list” and check for rouge characters. In this case there was new line with the letter ‘n’ in place, removing it solved the issue. Make sure to run “sudo apt-get update” to refresh the sources and everything should be fixed. I was also unable to see any software in the “Ubuntu Software Center” because of this.
|
About Hi, my name is Alex. I just got through studying Robotics at UWE and I am continuing to do a MSc by Research also in Robotics.
I enjoy a whole heap of things but on this website I mostly post linux, programming, machine vision and other similar topics.
You're free to redistribute anything you find on here, unless it states otherwise, as long as you are not selling it for profit and you link back to my site. Cheers.
Disclaimer Just to cover my ass.
Any information on this site is for informational purposes only, I take no responsibility for the accuracy, reliability, bla, bla or bla to it. Any information you use, you are using at your own risk. I am in no way liable for any loss, damage of data, hardware or anything else in connection with the use of this website.
|
Goodreads
Last.fm