Cannot write bytes: Broken pipe
I uninstalled 11.04 and installed 12.04 and grub was not detecting the partitions, so I fixed it with boot-repair and 12.04 loaded perfectly, then I tried to install the device driver for Nvidia Graphics card and it took a long time, so I stopped it and shut down.When I restarted the computer I got the message cannot write bytes: broken pipe.Then I followed this thread for help.
could not write bytes broken pipe 12.04
I went to recovery mode and drooping to root prompt and typed this command
sudo gedit /var/log/apt/history.log
For this I got the following error message as gedit did not open that file:
(gedit : 856):Warning : Command line 'dbus-launch --autolaunch=somernadomnumbers --
binary-syntax --close-stderr' exitted with non-zero exit
status 1: Autolaunch error: X11 initialization failed. n
cannot open display:
Run 'gedit --help' to see a full list of available command options.
Did this happen because of stopping the installation of Nvidia device driver in the middle of its installation?
I am running 12.04 with Winodws 7 dual boot.Any help would be appreciated.
When 12.04 was working normally I started and quit in the middle of the installation of the Grahpics driver for Nvidia Grahpics card and I restarted the computer and got the could not write bytes: broken pipe error.
12.04 boot
edited Apr 13 '17 at 12:23
Community♦
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
add a comment |
I uninstalled 11.04 and installed 12.04 and grub was not detecting the partitions, so I fixed it with boot-repair and 12.04 loaded perfectly, then I tried to install the device driver for Nvidia Graphics card and it took a long time, so I stopped it and shut down.When I restarted the computer I got the message cannot write bytes: broken pipe.Then I followed this thread for help.
could not write bytes broken pipe 12.04
I went to recovery mode and drooping to root prompt and typed this command
sudo gedit /var/log/apt/history.log
For this I got the following error message as gedit did not open that file:
(gedit : 856):Warning : Command line 'dbus-launch --autolaunch=somernadomnumbers --
binary-syntax --close-stderr' exitted with non-zero exit
status 1: Autolaunch error: X11 initialization failed. n
cannot open display:
Run 'gedit --help' to see a full list of available command options.
Did this happen because of stopping the installation of Nvidia device driver in the middle of its installation?
I am running 12.04 with Winodws 7 dual boot.Any help would be appreciated.
When 12.04 was working normally I started and quit in the middle of the installation of the Grahpics driver for Nvidia Grahpics card and I restarted the computer and got the could not write bytes: broken pipe error.
12.04 boot
edited Apr 13 '17 at 12:23
Community♦
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21
add a comment |
I uninstalled 11.04 and installed 12.04 and grub was not detecting the partitions, so I fixed it with boot-repair and 12.04 loaded perfectly, then I tried to install the device driver for Nvidia Graphics card and it took a long time, so I stopped it and shut down.When I restarted the computer I got the message cannot write bytes: broken pipe.Then I followed this thread for help.
could not write bytes broken pipe 12.04
I went to recovery mode and drooping to root prompt and typed this command
sudo gedit /var/log/apt/history.log
For this I got the following error message as gedit did not open that file:
(gedit : 856):Warning : Command line 'dbus-launch --autolaunch=somernadomnumbers --
binary-syntax --close-stderr' exitted with non-zero exit
status 1: Autolaunch error: X11 initialization failed. n
cannot open display:
Run 'gedit --help' to see a full list of available command options.
Did this happen because of stopping the installation of Nvidia device driver in the middle of its installation?
I am running 12.04 with Winodws 7 dual boot.Any help would be appreciated.
When 12.04 was working normally I started and quit in the middle of the installation of the Grahpics driver for Nvidia Grahpics card and I restarted the computer and got the could not write bytes: broken pipe error.
12.04 boot
edited Apr 13 '17 at 12:23
Community♦
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
I uninstalled 11.04 and installed 12.04 and grub was not detecting the partitions, so I fixed it with boot-repair and 12.04 loaded perfectly, then I tried to install the device driver for Nvidia Graphics card and it took a long time, so I stopped it and shut down.When I restarted the computer I got the message cannot write bytes: broken pipe.Then I followed this thread for help.
could not write bytes broken pipe 12.04
I went to recovery mode and drooping to root prompt and typed this command
sudo gedit /var/log/apt/history.log
For this I got the following error message as gedit did not open that file:
(gedit : 856):Warning : Command line 'dbus-launch --autolaunch=somernadomnumbers --
binary-syntax --close-stderr' exitted with non-zero exit
status 1: Autolaunch error: X11 initialization failed. n
cannot open display:
Run 'gedit --help' to see a full list of available command options.
Did this happen because of stopping the installation of Nvidia device driver in the middle of its installation?
I am running 12.04 with Winodws 7 dual boot.Any help would be appreciated.
When 12.04 was working normally I started and quit in the middle of the installation of the Grahpics driver for Nvidia Grahpics card and I restarted the computer and got the could not write bytes: broken pipe error.
12.04 boot
12.04 boot
edited Apr 13 '17 at 12:23
Community♦
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
edited Apr 13 '17 at 12:23
Community♦
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
edited Apr 13 '17 at 12:23
Community♦
1
1
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
asked Jan 12 '14 at 5:56
Sai PrashanthSai Prashanth
112
112
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21
add a comment |
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21
add a comment |
1 Answer
1
active
oldest
votes
A quick fix: boot in recovery mode with networking and issue sudo apt-get install --reinstall xserver-xorg, then reboot.
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f404208%2fcannot-write-bytes-broken-pipe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A quick fix: boot in recovery mode with networking and issue sudo apt-get install --reinstall xserver-xorg, then reboot.
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
add a comment |
A quick fix: boot in recovery mode with networking and issue sudo apt-get install --reinstall xserver-xorg, then reboot.
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
add a comment |
A quick fix: boot in recovery mode with networking and issue sudo apt-get install --reinstall xserver-xorg, then reboot.
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
A quick fix: boot in recovery mode with networking and issue sudo apt-get install --reinstall xserver-xorg, then reboot.
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
answered Sep 11 '14 at 11:51
FrantiqueFrantique
7,1422649
7,1422649
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f404208%2fcannot-write-bytes-broken-pipe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
No the error was not because you stopped the installation, it was because gedit cannot be opened in recovery mode. You should try to use command-line based test-editors like nano or vim. When exactly do you get the broken pipe error? Please edit you question to post the answer.
– jobin
Jan 12 '14 at 7:22
I have added at the end of the question, the point at which I got the broken pipe error.
– Sai Prashanth
Jan 12 '14 at 13:21