â../../src/filesdb.c:683: findnamenode: Assertion `(*pointerp)->name[0] == '/'' failed.â

Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I have been trying to update Ubuntu 12.04 on the command line by using the two commands
sudo apt-get update
sudo apt-get dist-upgrade
which ends with the following error:
(Reading database ... 70%dpkg: ../../src/filesdb.c:683: findnamenode: Assertion `(*pointerp)->name[0] == '/'' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
How to fix this on the command line?
dpkg
add a comment |Â
up vote
2
down vote
favorite
I have been trying to update Ubuntu 12.04 on the command line by using the two commands
sudo apt-get update
sudo apt-get dist-upgrade
which ends with the following error:
(Reading database ... 70%dpkg: ../../src/filesdb.c:683: findnamenode: Assertion `(*pointerp)->name[0] == '/'' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
How to fix this on the command line?
dpkg
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have been trying to update Ubuntu 12.04 on the command line by using the two commands
sudo apt-get update
sudo apt-get dist-upgrade
which ends with the following error:
(Reading database ... 70%dpkg: ../../src/filesdb.c:683: findnamenode: Assertion `(*pointerp)->name[0] == '/'' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
How to fix this on the command line?
dpkg
I have been trying to update Ubuntu 12.04 on the command line by using the two commands
sudo apt-get update
sudo apt-get dist-upgrade
which ends with the following error:
(Reading database ... 70%dpkg: ../../src/filesdb.c:683: findnamenode: Assertion `(*pointerp)->name[0] == '/'' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
How to fix this on the command line?
dpkg
dpkg
edited yesterday
Goro
3,24441951
3,24441951
asked Feb 4 '14 at 11:05
Alex
1,629154270
1,629154270
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37
add a comment |Â
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
The solution to this messed up installation is as follows.
Remove some installation files
/var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
Run
sudo apt-get dist-upgradeagain.Now the output is even more garbled up:
Preparing to replace jenkins 1.548 (using .../archives/jenkins_1.549_all.deb) ...
* Stopping Jenkins Continuous Integration Server jenkins [ OK ]
Unpacking replacement jenkins ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid distance code'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/jenkins_1.549_all.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/share/jenkins/jenkins.war'
No apport report written because MaxReports is reached already
* Starting Jenkins Continuous Integration Server jenkins [ OK ]
Errors were encountered while processing:
/var/cache/apt/archives/jenkins_1.549_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)but provides a hint of what was incorrectly installed:
jenkins.Now remove this incomplete installation with
sudo apt-get purge jenkins.- Install it again (if you still need it):
sudo apt-get install jenkins - And finally
sudo apt-get update && sudo apt-get dist-upgrade
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The solution to this messed up installation is as follows.
Remove some installation files
/var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
Run
sudo apt-get dist-upgradeagain.Now the output is even more garbled up:
Preparing to replace jenkins 1.548 (using .../archives/jenkins_1.549_all.deb) ...
* Stopping Jenkins Continuous Integration Server jenkins [ OK ]
Unpacking replacement jenkins ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid distance code'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/jenkins_1.549_all.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/share/jenkins/jenkins.war'
No apport report written because MaxReports is reached already
* Starting Jenkins Continuous Integration Server jenkins [ OK ]
Errors were encountered while processing:
/var/cache/apt/archives/jenkins_1.549_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)but provides a hint of what was incorrectly installed:
jenkins.Now remove this incomplete installation with
sudo apt-get purge jenkins.- Install it again (if you still need it):
sudo apt-get install jenkins - And finally
sudo apt-get update && sudo apt-get dist-upgrade
add a comment |Â
up vote
0
down vote
The solution to this messed up installation is as follows.
Remove some installation files
/var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
Run
sudo apt-get dist-upgradeagain.Now the output is even more garbled up:
Preparing to replace jenkins 1.548 (using .../archives/jenkins_1.549_all.deb) ...
* Stopping Jenkins Continuous Integration Server jenkins [ OK ]
Unpacking replacement jenkins ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid distance code'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/jenkins_1.549_all.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/share/jenkins/jenkins.war'
No apport report written because MaxReports is reached already
* Starting Jenkins Continuous Integration Server jenkins [ OK ]
Errors were encountered while processing:
/var/cache/apt/archives/jenkins_1.549_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)but provides a hint of what was incorrectly installed:
jenkins.Now remove this incomplete installation with
sudo apt-get purge jenkins.- Install it again (if you still need it):
sudo apt-get install jenkins - And finally
sudo apt-get update && sudo apt-get dist-upgrade
add a comment |Â
up vote
0
down vote
up vote
0
down vote
The solution to this messed up installation is as follows.
Remove some installation files
/var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
Run
sudo apt-get dist-upgradeagain.Now the output is even more garbled up:
Preparing to replace jenkins 1.548 (using .../archives/jenkins_1.549_all.deb) ...
* Stopping Jenkins Continuous Integration Server jenkins [ OK ]
Unpacking replacement jenkins ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid distance code'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/jenkins_1.549_all.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/share/jenkins/jenkins.war'
No apport report written because MaxReports is reached already
* Starting Jenkins Continuous Integration Server jenkins [ OK ]
Errors were encountered while processing:
/var/cache/apt/archives/jenkins_1.549_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)but provides a hint of what was incorrectly installed:
jenkins.Now remove this incomplete installation with
sudo apt-get purge jenkins.- Install it again (if you still need it):
sudo apt-get install jenkins - And finally
sudo apt-get update && sudo apt-get dist-upgrade
The solution to this messed up installation is as follows.
Remove some installation files
/var/cache/apt/pkgcache.bin /var/cache/apt/srcpkgcache.bin
Run
sudo apt-get dist-upgradeagain.Now the output is even more garbled up:
Preparing to replace jenkins 1.548 (using .../archives/jenkins_1.549_all.deb) ...
* Stopping Jenkins Continuous Integration Server jenkins [ OK ]
Unpacking replacement jenkins ...
dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid distance code'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/jenkins_1.549_all.deb (--unpack):
short read on buffer copy for backend dpkg-deb during `./usr/share/jenkins/jenkins.war'
No apport report written because MaxReports is reached already
* Starting Jenkins Continuous Integration Server jenkins [ OK ]
Errors were encountered while processing:
/var/cache/apt/archives/jenkins_1.549_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)but provides a hint of what was incorrectly installed:
jenkins.Now remove this incomplete installation with
sudo apt-get purge jenkins.- Install it again (if you still need it):
sudo apt-get install jenkins - And finally
sudo apt-get update && sudo apt-get dist-upgrade
answered Feb 4 '14 at 12:46
Alex
1,629154270
1,629154270
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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%2funix.stackexchange.com%2fquestions%2f113446%2fsrc-filesdb-c683-findnamenode-assertion-pointerp-name0%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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');
);
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');
);
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
This one could be hard to track down. It might be either hardware problems, or a messed-up installation. Please provide complete details in the question of what you did, including commands typed and output.
â Faheem Mitha
Feb 4 '14 at 12:37