dpkg seems to be broken: command not found
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
Tested on two 18.04 installs, while trying to install printer drivers and a few other packages. (Also see EDIT below)
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
sudo /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb: command not found
Testing with:
sudo dpkg --configure -a
Command completes OK, but no messages
This works:
sudo dpkg --help:
But the moment I add any command line options, I get "Command not found".
$PATH=
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Edit....
I tried other packages and they worked.
So I re-downloaded the deb from the source.
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
Then a few seconds later, with no other changes - it worked:
sudo dpkg -i --force-all LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
(Reading database ... 230357 files and directories currently installed.)
Preparing to unpack LPR_mfcj4620dwlpr-3.0.1-1.i386.deb ...
Unpacking mfcj4620dwlpr:i386 (3.0.1-1) over (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
Setting up mfcj4620dwlpr:i386 (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
dpkg is not giving me any meaningful output if there is a problem with the actual file
In fact, this is very odd - inconsistent behaviour:
sudo dpkg -i nonexistentfile
dpkg: error: cannot access archive 'nonexistentfile': No such file or directory
But:
sudo dpkgÃÂ -i nonsensename
sudo: dpkgÃÂ -i: command not found
sudo dpkgÃÂ -i thursday
sudo: dpkgÃÂ -i: command not found
Also interesting, when using filename completion, dkpg will not expand the filename if the test results in a command not found error. But will do so with a valid package. This almost suggests a problem with the shell.
dpkg
add a comment |Â
up vote
0
down vote
favorite
Tested on two 18.04 installs, while trying to install printer drivers and a few other packages. (Also see EDIT below)
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
sudo /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb: command not found
Testing with:
sudo dpkg --configure -a
Command completes OK, but no messages
This works:
sudo dpkg --help:
But the moment I add any command line options, I get "Command not found".
$PATH=
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Edit....
I tried other packages and they worked.
So I re-downloaded the deb from the source.
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
Then a few seconds later, with no other changes - it worked:
sudo dpkg -i --force-all LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
(Reading database ... 230357 files and directories currently installed.)
Preparing to unpack LPR_mfcj4620dwlpr-3.0.1-1.i386.deb ...
Unpacking mfcj4620dwlpr:i386 (3.0.1-1) over (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
Setting up mfcj4620dwlpr:i386 (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
dpkg is not giving me any meaningful output if there is a problem with the actual file
In fact, this is very odd - inconsistent behaviour:
sudo dpkg -i nonexistentfile
dpkg: error: cannot access archive 'nonexistentfile': No such file or directory
But:
sudo dpkgÃÂ -i nonsensename
sudo: dpkgÃÂ -i: command not found
sudo dpkgÃÂ -i thursday
sudo: dpkgÃÂ -i: command not found
Also interesting, when using filename completion, dkpg will not expand the filename if the test results in a command not found error. But will do so with a valid package. This almost suggests a problem with the shell.
dpkg
1
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Tested on two 18.04 installs, while trying to install printer drivers and a few other packages. (Also see EDIT below)
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
sudo /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb: command not found
Testing with:
sudo dpkg --configure -a
Command completes OK, but no messages
This works:
sudo dpkg --help:
But the moment I add any command line options, I get "Command not found".
$PATH=
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Edit....
I tried other packages and they worked.
So I re-downloaded the deb from the source.
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
Then a few seconds later, with no other changes - it worked:
sudo dpkg -i --force-all LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
(Reading database ... 230357 files and directories currently installed.)
Preparing to unpack LPR_mfcj4620dwlpr-3.0.1-1.i386.deb ...
Unpacking mfcj4620dwlpr:i386 (3.0.1-1) over (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
Setting up mfcj4620dwlpr:i386 (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
dpkg is not giving me any meaningful output if there is a problem with the actual file
In fact, this is very odd - inconsistent behaviour:
sudo dpkg -i nonexistentfile
dpkg: error: cannot access archive 'nonexistentfile': No such file or directory
But:
sudo dpkgÃÂ -i nonsensename
sudo: dpkgÃÂ -i: command not found
sudo dpkgÃÂ -i thursday
sudo: dpkgÃÂ -i: command not found
Also interesting, when using filename completion, dkpg will not expand the filename if the test results in a command not found error. But will do so with a valid package. This almost suggests a problem with the shell.
dpkg
Tested on two 18.04 installs, while trying to install printer drivers and a few other packages. (Also see EDIT below)
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
sudo /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: /usr/bin/dpkgÃÂ -VÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb: command not found
Testing with:
sudo dpkg --configure -a
Command completes OK, but no messages
This works:
sudo dpkg --help:
But the moment I add any command line options, I get "Command not found".
$PATH=
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
Edit....
I tried other packages and they worked.
So I re-downloaded the deb from the source.
sudo dpkgÃÂ -iÃÂ --force-allÃÂ LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
sudo: dpkgÃÂ -iÃÂ --force-allÃÂ : command not found
Then a few seconds later, with no other changes - it worked:
sudo dpkg -i --force-all LPR_mfcj4620dwlpr-3.0.1-1.i386.deb
(Reading database ... 230357 files and directories currently installed.)
Preparing to unpack LPR_mfcj4620dwlpr-3.0.1-1.i386.deb ...
Unpacking mfcj4620dwlpr:i386 (3.0.1-1) over (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
Setting up mfcj4620dwlpr:i386 (3.0.1-1) ...
Stopping printer spooler: lpd.
Starting printer spooler: lpd.
dpkg is not giving me any meaningful output if there is a problem with the actual file
In fact, this is very odd - inconsistent behaviour:
sudo dpkg -i nonexistentfile
dpkg: error: cannot access archive 'nonexistentfile': No such file or directory
But:
sudo dpkgÃÂ -i nonsensename
sudo: dpkgÃÂ -i: command not found
sudo dpkgÃÂ -i thursday
sudo: dpkgÃÂ -i: command not found
Also interesting, when using filename completion, dkpg will not expand the filename if the test results in a command not found error. But will do so with a valid package. This almost suggests a problem with the shell.
dpkg
edited May 24 at 13:24
asked May 24 at 12:49
abssorb
134
134
1
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08
add a comment |Â
1
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08
1
1
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1039827%2fdpkg-seems-to-be-broken-command-not-found%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Are you copy-pasting this from somewhere?
â muru
May 24 at 13:23
Originally, yes, but to eliminate that I worked within the shell. So copying/pasting from ls results within exact same shell (to save typing errors). PS I've made an edit in the last few minutes
â abssorb
May 24 at 13:26
So this happens even if you type out every single character in the command line?
â muru
May 24 at 13:32
Yes. All the above after "Edit" was typed character by character.
â abssorb
May 24 at 14:55
wild guess here: are you typing this from an OSX terminal and happen to type alt-space accidentally (which would produce the unicode 0083 or "no break here" character, indistinguishable from space)
â Sebastian Stark
May 24 at 17:08