How do I fix this “E: Type '*' is not known on line * in source list …” update error?Type 'echo' is not known on line 1 in source list /etc/apt/sources.list.d/mongodb-org-3.2.listHow to fix “/etc/apt/sources.list” could not be read error?How do I fix an error in my apt sources list?Type 'sudo' is not known in source list“E: The list of sources could not be read.” while trying to update“E:Type '<!DOCTYPE' is not known on line 1 in source list” how to fix?How do I get iperf on a Ubuntu 13.10 Live disc?Type '"deb' is not known on line 1 in source list“Type 'debo' is not known on line 1 in source list /etc/apt/sources.list.d/spotify.list”apt-get update fails after upgrade10.10 to 11.04 upgrade unmet dependenciesGrizzly error pops up every time
Is the sentence "pay some in cash" understandable?
Does Global Entry require agreeing to a higher standard of behavior?
What is the purpose of this circuit?
Doubt about Taylor series: do successive derivatives on a point determine the whole function?
Quantification in the infer command of the proof package
For Pressure Canning, can I use any other jar than Ball’s Mason Jar?
In TDD, should I add unit tests to refactored code?
Can increasing the amount of training data make overfitting worse?
A feasible and efficient method of fast global travel?
Why does the asymptote succession compilation result in a non-vector pdf?
Why does Greedo say "Maclunkey" in the Mos Eisley Cantina?
Can I "read" from English books to my infant, but use words from my native language?
Can you use a clue that contains a word on the board within it in an unrelated way in Codenames?
Are commercial VFR flights legal?
Does the horse hair in a bow all go in the same direction?
Why were some early PC 3D cards unsuitable for 2D graphics?
Is there any math conjecture that would cause a lot of damage if disproven?
What is the last point where one can throw away fruits if one has indicated "not bringing any fruit" on the US customs form when flying to the US?
Crack hashed passwords using a known password
Is Scrum actuably suitable for all kind of projects?
Who was the first human to sleep on the Moon?
SMD ceramic capacitor 0805 vs 1206
Is there a text editor that can run shell scripts?
In Flanders Fields
How do I fix this “E: Type '*' is not known on line * in source list …” update error?
Type 'echo' is not known on line 1 in source list /etc/apt/sources.list.d/mongodb-org-3.2.listHow to fix “/etc/apt/sources.list” could not be read error?How do I fix an error in my apt sources list?Type 'sudo' is not known in source list“E: The list of sources could not be read.” while trying to update“E:Type '<!DOCTYPE' is not known on line 1 in source list” how to fix?How do I get iperf on a Ubuntu 13.10 Live disc?Type '"deb' is not known on line 1 in source list“Type 'debo' is not known on line 1 in source list /etc/apt/sources.list.d/spotify.list”apt-get update fails after upgrade10.10 to 11.04 upgrade unmet dependenciesGrizzly error pops up every time
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Every once in a while I see users having issues to update due to errors like this:
E:Type 'ain' is not known on line 1 in source list /etc/apt/sources.list.d/some-ppa.list'
with varying types/line numbers/source list files (often after removing a PPA).
How can such an error be fixed?
apt software-sources
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
Every once in a while I see users having issues to update due to errors like this:
E:Type 'ain' is not known on line 1 in source list /etc/apt/sources.list.d/some-ppa.list'
with varying types/line numbers/source list files (often after removing a PPA).
How can such an error be fixed?
apt software-sources
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
Every once in a while I see users having issues to update due to errors like this:
E:Type 'ain' is not known on line 1 in source list /etc/apt/sources.list.d/some-ppa.list'
with varying types/line numbers/source list files (often after removing a PPA).
How can such an error be fixed?
apt software-sources
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
Every once in a while I see users having issues to update due to errors like this:
E:Type 'ain' is not known on line 1 in source list /etc/apt/sources.list.d/some-ppa.list'
with varying types/line numbers/source list files (often after removing a PPA).
How can such an error be fixed?
apt software-sources
apt software-sources
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
edited Feb 12 '17 at 7:38
Zanna
55.4k15 gold badges151 silver badges253 bronze badges
55.4k15 gold badges151 silver badges253 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
asked Jan 19 '12 at 23:24
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
add a comment
|
3 Answers
3
active
oldest
votes
The error indicates a malformed entry in a source file, which causes the update process to abort. To fix it, you have to either fix the entry (if you know what the right entry should look like) or remove it altogether (that's what I'm going to describe, as it's the fastest way to enable you to update your system again).
First, you need to open the file containing the bad entry. The filename is given in the error message, in your example
/etc/apt/sources.list.d/some-ppa.list. Open a terminal, and typesudo nano /etc/apt/sources.list.d/some-ppa.listand press Enter. After entering your password, you should now see the file opened in the text editor
nano.Now you need to locate the malformed entry. It should be on the line number given in the error message - in your case that would be line 1.
This line should be incomplete and start with the unknown type the update process is complaining about (here
ain). Just delete the whole line, and save/close the file with Ctrl+X.That's it. You should now be able to successfully run the update process!
If that entry is all that's in the file, then you can just delete the file. To do this, just open a terminal and run the following command:
sudo rm /etc/apt/sources.list.d/some-ppa.list
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
You're experiencing Bug #789859 in the software-properties package.
The quick and immediate fix is to open up the file that the error message mentions (in this case /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list) and remove the line that says ain. This is achieved like so:
- Press AltF2
- Enter:
gksudo gedit /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list - Remove the line that says
ain - Save the file
When done, everything should work.
To avoid experiencing this bug in the future, please visit the bug's Launchpad page and mark the bug as affecting you.
edited Mar 6 '17 at 8:55
muru
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
add a comment
|
To completely remove any unwanted ppa we may use the script ppa-purge .
that will remove the ppa and restores Ubuntu default settings for any applications that may have been installed by this ppa.
In your case try if
sudo ppa-purge -purge the-board-team/dev-snapshots
followed by
sudo apt-get update
helps you to get rid of your synaptic error.
edited Mar 11 '17 at 19:00
Community♦
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
add a comment
|
protected by Kaz Wolfe Mar 6 '17 at 17:47
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The error indicates a malformed entry in a source file, which causes the update process to abort. To fix it, you have to either fix the entry (if you know what the right entry should look like) or remove it altogether (that's what I'm going to describe, as it's the fastest way to enable you to update your system again).
First, you need to open the file containing the bad entry. The filename is given in the error message, in your example
/etc/apt/sources.list.d/some-ppa.list. Open a terminal, and typesudo nano /etc/apt/sources.list.d/some-ppa.listand press Enter. After entering your password, you should now see the file opened in the text editor
nano.Now you need to locate the malformed entry. It should be on the line number given in the error message - in your case that would be line 1.
This line should be incomplete and start with the unknown type the update process is complaining about (here
ain). Just delete the whole line, and save/close the file with Ctrl+X.That's it. You should now be able to successfully run the update process!
If that entry is all that's in the file, then you can just delete the file. To do this, just open a terminal and run the following command:
sudo rm /etc/apt/sources.list.d/some-ppa.list
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
The error indicates a malformed entry in a source file, which causes the update process to abort. To fix it, you have to either fix the entry (if you know what the right entry should look like) or remove it altogether (that's what I'm going to describe, as it's the fastest way to enable you to update your system again).
First, you need to open the file containing the bad entry. The filename is given in the error message, in your example
/etc/apt/sources.list.d/some-ppa.list. Open a terminal, and typesudo nano /etc/apt/sources.list.d/some-ppa.listand press Enter. After entering your password, you should now see the file opened in the text editor
nano.Now you need to locate the malformed entry. It should be on the line number given in the error message - in your case that would be line 1.
This line should be incomplete and start with the unknown type the update process is complaining about (here
ain). Just delete the whole line, and save/close the file with Ctrl+X.That's it. You should now be able to successfully run the update process!
If that entry is all that's in the file, then you can just delete the file. To do this, just open a terminal and run the following command:
sudo rm /etc/apt/sources.list.d/some-ppa.list
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
The error indicates a malformed entry in a source file, which causes the update process to abort. To fix it, you have to either fix the entry (if you know what the right entry should look like) or remove it altogether (that's what I'm going to describe, as it's the fastest way to enable you to update your system again).
First, you need to open the file containing the bad entry. The filename is given in the error message, in your example
/etc/apt/sources.list.d/some-ppa.list. Open a terminal, and typesudo nano /etc/apt/sources.list.d/some-ppa.listand press Enter. After entering your password, you should now see the file opened in the text editor
nano.Now you need to locate the malformed entry. It should be on the line number given in the error message - in your case that would be line 1.
This line should be incomplete and start with the unknown type the update process is complaining about (here
ain). Just delete the whole line, and save/close the file with Ctrl+X.That's it. You should now be able to successfully run the update process!
If that entry is all that's in the file, then you can just delete the file. To do this, just open a terminal and run the following command:
sudo rm /etc/apt/sources.list.d/some-ppa.list
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
The error indicates a malformed entry in a source file, which causes the update process to abort. To fix it, you have to either fix the entry (if you know what the right entry should look like) or remove it altogether (that's what I'm going to describe, as it's the fastest way to enable you to update your system again).
First, you need to open the file containing the bad entry. The filename is given in the error message, in your example
/etc/apt/sources.list.d/some-ppa.list. Open a terminal, and typesudo nano /etc/apt/sources.list.d/some-ppa.listand press Enter. After entering your password, you should now see the file opened in the text editor
nano.Now you need to locate the malformed entry. It should be on the line number given in the error message - in your case that would be line 1.
This line should be incomplete and start with the unknown type the update process is complaining about (here
ain). Just delete the whole line, and save/close the file with Ctrl+X.That's it. You should now be able to successfully run the update process!
If that entry is all that's in the file, then you can just delete the file. To do this, just open a terminal and run the following command:
sudo rm /etc/apt/sources.list.d/some-ppa.list
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
edited Mar 6 '17 at 17:53
Kaz Wolfe
29.3k14 gold badges92 silver badges144 bronze badges
29.3k14 gold badges92 silver badges144 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
answered Jan 19 '12 at 23:25
htorquehtorque
55.4k33 gold badges180 silver badges213 bronze badges
55.4k33 gold badges180 silver badges213 bronze badges
add a comment
|
add a comment
|
You're experiencing Bug #789859 in the software-properties package.
The quick and immediate fix is to open up the file that the error message mentions (in this case /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list) and remove the line that says ain. This is achieved like so:
- Press AltF2
- Enter:
gksudo gedit /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list - Remove the line that says
ain - Save the file
When done, everything should work.
To avoid experiencing this bug in the future, please visit the bug's Launchpad page and mark the bug as affecting you.
edited Mar 6 '17 at 8:55
muru
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
add a comment
|
You're experiencing Bug #789859 in the software-properties package.
The quick and immediate fix is to open up the file that the error message mentions (in this case /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list) and remove the line that says ain. This is achieved like so:
- Press AltF2
- Enter:
gksudo gedit /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list - Remove the line that says
ain - Save the file
When done, everything should work.
To avoid experiencing this bug in the future, please visit the bug's Launchpad page and mark the bug as affecting you.
edited Mar 6 '17 at 8:55
muru
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
add a comment
|
You're experiencing Bug #789859 in the software-properties package.
The quick and immediate fix is to open up the file that the error message mentions (in this case /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list) and remove the line that says ain. This is achieved like so:
- Press AltF2
- Enter:
gksudo gedit /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list - Remove the line that says
ain - Save the file
When done, everything should work.
To avoid experiencing this bug in the future, please visit the bug's Launchpad page and mark the bug as affecting you.
edited Mar 6 '17 at 8:55
muru
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
You're experiencing Bug #789859 in the software-properties package.
The quick and immediate fix is to open up the file that the error message mentions (in this case /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list) and remove the line that says ain. This is achieved like so:
- Press AltF2
- Enter:
gksudo gedit /etc/apt/sources.list.d/the-board-team-dev-snapshots-natty.list - Remove the line that says
ain - Save the file
When done, everything should work.
To avoid experiencing this bug in the future, please visit the bug's Launchpad page and mark the bug as affecting you.
edited Mar 6 '17 at 8:55
muru
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
edited Mar 6 '17 at 8:55
muru
1
edited Mar 6 '17 at 8:55
muru
1
edited Mar 6 '17 at 8:55
muru
1
1
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
answered Jul 14 '11 at 12:16
runeksruneks
3311 gold badge2 silver badges8 bronze badges
3311 gold badge2 silver badges8 bronze badges
add a comment
|
add a comment
|
To completely remove any unwanted ppa we may use the script ppa-purge .
that will remove the ppa and restores Ubuntu default settings for any applications that may have been installed by this ppa.
In your case try if
sudo ppa-purge -purge the-board-team/dev-snapshots
followed by
sudo apt-get update
helps you to get rid of your synaptic error.
edited Mar 11 '17 at 19:00
Community♦
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
add a comment
|
To completely remove any unwanted ppa we may use the script ppa-purge .
that will remove the ppa and restores Ubuntu default settings for any applications that may have been installed by this ppa.
In your case try if
sudo ppa-purge -purge the-board-team/dev-snapshots
followed by
sudo apt-get update
helps you to get rid of your synaptic error.
edited Mar 11 '17 at 19:00
Community♦
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
add a comment
|
To completely remove any unwanted ppa we may use the script ppa-purge .
that will remove the ppa and restores Ubuntu default settings for any applications that may have been installed by this ppa.
In your case try if
sudo ppa-purge -purge the-board-team/dev-snapshots
followed by
sudo apt-get update
helps you to get rid of your synaptic error.
edited Mar 11 '17 at 19:00
Community♦
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
To completely remove any unwanted ppa we may use the script ppa-purge .
that will remove the ppa and restores Ubuntu default settings for any applications that may have been installed by this ppa.
In your case try if
sudo ppa-purge -purge the-board-team/dev-snapshots
followed by
sudo apt-get update
helps you to get rid of your synaptic error.
edited Mar 11 '17 at 19:00
Community♦
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
edited Mar 11 '17 at 19:00
Community♦
1
edited Mar 11 '17 at 19:00
Community♦
1
edited Mar 11 '17 at 19:00
Community♦
1
1
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
answered Apr 29 '11 at 12:34
TakkatTakkat
119k40 gold badges263 silver badges386 bronze badges
119k40 gold badges263 silver badges386 bronze badges
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
add a comment
|
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
TY ur Awesome!!!!
– Jonthue Michel
Apr 30 '11 at 12:41
add a comment
|
protected by Kaz Wolfe Mar 6 '17 at 17:47
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
