“sudo gparted” is not working. It says, “The process gpartedbin is already running. Only one gpartedbin...

Screenshot image:

This is Ubuntu 18.10 dual booted with Windows 10.
For some reason, I have never been able to launch Gparted clicking its app icon. So I have to launch it through terminal every-time.

Sometimes it gives this warning:

tmp.mount doesn't exist.

Sometimes it gives this error:

The process gpartedbin is already running.
Only one gpartedbin process is permitted."

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

1. I think you need not worry about the warning; 2. I guess that gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'. What happens if you identify the process: ps -Af|grep gpartedbin and kill it? What happens after a reboot? 3. It is a good habit to use sudo -H with graphical programs, so sudo -H gparted.

– sudodus
Feb 7 at 13:34

Usually after reboot/shutdown I get: 1. OS cashes a lot. If a wifi dongle is connected, then it try to send error log. And then for some reason it can't and leave me nowhere but to press hard the power button. 2. Os crashes saying "Bad rip value". @sudodus

– Prabesh Bhattarai
Feb 7 at 18:30

add a comment |

Screenshot image:

This is Ubuntu 18.10 dual booted with Windows 10.
For some reason, I have never been able to launch Gparted clicking its app icon. So I have to launch it through terminal every-time.

Sometimes it gives this warning:

tmp.mount doesn't exist.

Sometimes it gives this error:

The process gpartedbin is already running.
Only one gpartedbin process is permitted."

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

1. I think you need not worry about the warning; 2. I guess that gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'. What happens if you identify the process: ps -Af|grep gpartedbin and kill it? What happens after a reboot? 3. It is a good habit to use sudo -H with graphical programs, so sudo -H gparted.

– sudodus
Feb 7 at 13:34

Usually after reboot/shutdown I get: 1. OS cashes a lot. If a wifi dongle is connected, then it try to send error log. And then for some reason it can't and leave me nowhere but to press hard the power button. 2. Os crashes saying "Bad rip value". @sudodus

– Prabesh Bhattarai
Feb 7 at 18:30

add a comment |

Screenshot image:

This is Ubuntu 18.10 dual booted with Windows 10.
For some reason, I have never been able to launch Gparted clicking its app icon. So I have to launch it through terminal every-time.

Sometimes it gives this warning:

tmp.mount doesn't exist.

Sometimes it gives this error:

The process gpartedbin is already running.
Only one gpartedbin process is permitted."

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

Screenshot image:

This is Ubuntu 18.10 dual booted with Windows 10.
For some reason, I have never been able to launch Gparted clicking its app icon. So I have to launch it through terminal every-time.

Sometimes it gives this warning:

tmp.mount doesn't exist.

Sometimes it gives this error:

The process gpartedbin is already running.
Only one gpartedbin process is permitted."

dual-boot gparted 18.10

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

edited Feb 7 at 11:50

asked Feb 7 at 11:43

Prabesh Bhattarai

877

asked Feb 7 at 11:43

Prabesh Bhattarai

877

asked Feb 7 at 11:43

Prabesh Bhattarai

877

1. I think you need not worry about the warning; 2. I guess that gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'. What happens if you identify the process: ps -Af|grep gpartedbin and kill it? What happens after a reboot? 3. It is a good habit to use sudo -H with graphical programs, so sudo -H gparted.

– sudodus
Feb 7 at 13:34

Usually after reboot/shutdown I get: 1. OS cashes a lot. If a wifi dongle is connected, then it try to send error log. And then for some reason it can't and leave me nowhere but to press hard the power button. 2. Os crashes saying "Bad rip value". @sudodus

– Prabesh Bhattarai
Feb 7 at 18:30

add a comment |

1. I think you need not worry about the warning; 2. I guess that gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'. What happens if you identify the process: ps -Af|grep gpartedbin and kill it? What happens after a reboot? 3. It is a good habit to use sudo -H with graphical programs, so sudo -H gparted.

– sudodus
Feb 7 at 13:34

Usually after reboot/shutdown I get: 1. OS cashes a lot. If a wifi dongle is connected, then it try to send error log. And then for some reason it can't and leave me nowhere but to press hard the power button. 2. Os crashes saying "Bad rip value". @sudodus

– Prabesh Bhattarai
Feb 7 at 18:30

1. I think you need not worry about the warning; 2. I guess that gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'. What happens if you identify the process: ps -Af|grep gpartedbin and kill it? What happens after a reboot? 3. It is a good habit to use sudo -H with graphical programs, so sudo -H gparted.

– sudodus
Feb 7 at 13:34

Usually after reboot/shutdown I get: 1. OS cashes a lot. If a wifi dongle is connected, then it try to send error log. And then for some reason it can't and leave me nowhere but to press hard the power button. 2. Os crashes saying "Bad rip value". @sudodus

– Prabesh Bhattarai
Feb 7 at 18:30

add a comment |

1 Answer
1

active

oldest

votes

Instead of pressing the power button (hard shutdown), you can often reboot gracefully with SysRq REISUB or shutdown gracefully with SysRq REISUO. This prevents damage to the file system.

See this link: en.wikipedia.org/wiki/Magic_SysRq_key.

SysRq is often activated with Alt + PrintScreen and then, while those two keys are still pressed, type slowly the letters R E I S U B or R E I S U O.

The root file system may be damaged.
- Boot from another drive, for example an Ubuntu install USB drive or DVD disk.
- Check that your installed system's root partition is not mounted.
- Now you can check and if necessary repair with
```
sudo e2fsck /dev/sdxn
```
  where x is the drive letter and n is the partition number, /dev/sda6 according to your screenshot.

Now to what you asked for:

I think you need not worry about the warning.

Probably gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'.
- Identify the process:
```
ps -Af|grep gpartedbin
```
  and try to kill it.

Since you have problems with reboot, please reboot gracefully, and I hope, these problems will disappear.

It is a good habit to use
```
sudo -H
```
with graphical programs, so
```
sudo -H gparted
```
The reason is that programs, for example editors and file browsers write in configuration files, and with plain sudo the configuration of your own user ID can be overwritten by root and it stops working for normal use. This will not happen if you use sudo -H.

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116368%2fsudo-gparted-is-not-working-it-says-the-process-gpartedbin-is-already-runni%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

Instead of pressing the power button (hard shutdown), you can often reboot gracefully with SysRq REISUB or shutdown gracefully with SysRq REISUO. This prevents damage to the file system.

See this link: en.wikipedia.org/wiki/Magic_SysRq_key.

SysRq is often activated with Alt + PrintScreen and then, while those two keys are still pressed, type slowly the letters R E I S U B or R E I S U O.

The root file system may be damaged.
- Boot from another drive, for example an Ubuntu install USB drive or DVD disk.
- Check that your installed system's root partition is not mounted.
- Now you can check and if necessary repair with
```
sudo e2fsck /dev/sdxn
```
  where x is the drive letter and n is the partition number, /dev/sda6 according to your screenshot.

Now to what you asked for:

I think you need not worry about the warning.

Probably gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'.
- Identify the process:
```
ps -Af|grep gpartedbin
```
  and try to kill it.

Since you have problems with reboot, please reboot gracefully, and I hope, these problems will disappear.

It is a good habit to use
```
sudo -H
```
with graphical programs, so
```
sudo -H gparted
```
The reason is that programs, for example editors and file browsers write in configuration files, and with plain sudo the configuration of your own user ID can be overwritten by root and it stops working for normal use. This will not happen if you use sudo -H.

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

add a comment |

Instead of pressing the power button (hard shutdown), you can often reboot gracefully with SysRq REISUB or shutdown gracefully with SysRq REISUO. This prevents damage to the file system.

See this link: en.wikipedia.org/wiki/Magic_SysRq_key.

SysRq is often activated with Alt + PrintScreen and then, while those two keys are still pressed, type slowly the letters R E I S U B or R E I S U O.

The root file system may be damaged.
- Boot from another drive, for example an Ubuntu install USB drive or DVD disk.
- Check that your installed system's root partition is not mounted.
- Now you can check and if necessary repair with
```
sudo e2fsck /dev/sdxn
```
  where x is the drive letter and n is the partition number, /dev/sda6 according to your screenshot.

Now to what you asked for:

I think you need not worry about the warning.

Probably gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'.
- Identify the process:
```
ps -Af|grep gpartedbin
```
  and try to kill it.

Since you have problems with reboot, please reboot gracefully, and I hope, these problems will disappear.

It is a good habit to use
```
sudo -H
```
with graphical programs, so
```
sudo -H gparted
```
The reason is that programs, for example editors and file browsers write in configuration files, and with plain sudo the configuration of your own user ID can be overwritten by root and it stops working for normal use. This will not happen if you use sudo -H.

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

add a comment |

Instead of pressing the power button (hard shutdown), you can often reboot gracefully with SysRq REISUB or shutdown gracefully with SysRq REISUO. This prevents damage to the file system.

See this link: en.wikipedia.org/wiki/Magic_SysRq_key.

SysRq is often activated with Alt + PrintScreen and then, while those two keys are still pressed, type slowly the letters R E I S U B or R E I S U O.

The root file system may be damaged.
- Boot from another drive, for example an Ubuntu install USB drive or DVD disk.
- Check that your installed system's root partition is not mounted.
- Now you can check and if necessary repair with
```
sudo e2fsck /dev/sdxn
```
  where x is the drive letter and n is the partition number, /dev/sda6 according to your screenshot.

Now to what you asked for:

I think you need not worry about the warning.

Probably gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'.
- Identify the process:
```
ps -Af|grep gpartedbin
```
  and try to kill it.

Since you have problems with reboot, please reboot gracefully, and I hope, these problems will disappear.

It is a good habit to use
```
sudo -H
```
with graphical programs, so
```
sudo -H gparted
```
The reason is that programs, for example editors and file browsers write in configuration files, and with plain sudo the configuration of your own user ID can be overwritten by root and it stops working for normal use. This will not happen if you use sudo -H.

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

Instead of pressing the power button (hard shutdown), you can often reboot gracefully with SysRq REISUB or shutdown gracefully with SysRq REISUO. This prevents damage to the file system.

See this link: en.wikipedia.org/wiki/Magic_SysRq_key.

SysRq is often activated with Alt + PrintScreen and then, while those two keys are still pressed, type slowly the letters R E I S U B or R E I S U O.

The root file system may be damaged.
- Boot from another drive, for example an Ubuntu install USB drive or DVD disk.
- Check that your installed system's root partition is not mounted.
- Now you can check and if necessary repair with
```
sudo e2fsck /dev/sdxn
```
  where x is the drive letter and n is the partition number, /dev/sda6 according to your screenshot.

Now to what you asked for:

I think you need not worry about the warning.

Probably gparted was run before, and not closed correctly, when 'the process gpartedbin is already running'.
- Identify the process:
```
ps -Af|grep gpartedbin
```
  and try to kill it.

Since you have problems with reboot, please reboot gracefully, and I hope, these problems will disappear.

It is a good habit to use
```
sudo -H
```
with graphical programs, so
```
sudo -H gparted
```
The reason is that programs, for example editors and file browsers write in configuration files, and with plain sudo the configuration of your own user ID can be overwritten by root and it stops working for normal use. This will not happen if you use sudo -H.

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

edited Feb 7 at 19:45

answered Feb 7 at 18:52

sudodus

24.9k32877

answered Feb 7 at 18:52

sudodus

24.9k32877

answered Feb 7 at 18:52

sudodus

24.9k32877

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

add a comment |

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

Thanks, i have heard about "reboot gracefully" method and tried using it before but without "those two keys are still pressed". So never worked. Form now on, i will press those buttons continuously and give it a shot.

– Prabesh Bhattarai
Feb 8 at 1:27

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Bdtyktl