Stop pgAdmin 4 from launching on boot (ubuntu 16.04)
up vote
2
down vote
favorite
Lately, pgAdmin would automatically launch on boot. I'm using KDE, and there is no entry for pgAdmin in Autostart, nor was there any in ~/.config/autostart (tho' I'm guessing Autostart uses the file from there anyway).
16.04 kde pgadmin
edited Sep 22 at 13:01
CentaurusA
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
add a comment |
up vote
2
down vote
favorite
Lately, pgAdmin would automatically launch on boot. I'm using KDE, and there is no entry for pgAdmin in Autostart, nor was there any in ~/.config/autostart (tho' I'm guessing Autostart uses the file from there anyway).
16.04 kde pgadmin
edited Sep 22 at 13:01
CentaurusA
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Lately, pgAdmin would automatically launch on boot. I'm using KDE, and there is no entry for pgAdmin in Autostart, nor was there any in ~/.config/autostart (tho' I'm guessing Autostart uses the file from there anyway).
16.04 kde pgadmin
edited Sep 22 at 13:01
CentaurusA
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
Lately, pgAdmin would automatically launch on boot. I'm using KDE, and there is no entry for pgAdmin in Autostart, nor was there any in ~/.config/autostart (tho' I'm guessing Autostart uses the file from there anyway).
16.04 kde pgadmin
16.04 kde pgadmin
edited Sep 22 at 13:01
CentaurusA
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
edited Sep 22 at 13:01
CentaurusA
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
edited Sep 22 at 13:01
CentaurusA
2,2151324
edited Sep 22 at 13:01
CentaurusA
2,2151324
edited Sep 22 at 13:01
CentaurusA
2,2151324
2,2151324
asked Sep 22 at 12:24
Bobby Wibowo
114
asked Sep 22 at 12:24
Bobby Wibowo
114
asked Sep 22 at 12:24
Bobby Wibowo
114
114
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
up vote
0
down vote
You can disable startup services using:
sudo systemctl stop postgresql
sudo systemctl disable postgresql
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
add a comment |
up vote
0
down vote
accepted
Turns out it was due to pgadmin4 was still running in the background, so it would launch itself again on next logins. I just killed the process with old school pkill -f pgadmin4 and it would no longer automatically launch itself on next logins. There's no need to stop postgresql service.
answered Sep 26 at 10:33
Bobby Wibowo
114
It waspkill -f pgAdmin4for me instead ofpkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.
– Ezze
Dec 4 at 12:26
add a comment |
up vote
0
down vote
Facing the same issue on Ubuntu 18.04 with KDE Plasma 5.12.6. The key problem is that KDE saves desktop session and restores it on reboot. That's why pgAdmin 4 starts automatically if it was running before reboot.
In order to fix this go to "System Settings", select "Startup and Shutdown" tab in "Workspace" section and then select "Desktop session":
You will see that "Restore previous session" box is enabled in "On Login" section there. If you want to exclude pgAdmin 4 only from being restored on login then just type a full path to its executable in "Applications to be excluded from sessions":
/usr/bin/pgAdmin4
You can detect a path by running:
which pgAdmin4
If you don't want to save desktop session related data then another simple solution is to tick "Start with an empty session" box.
After that click "Apply" button and reboot the system. Now pgAdmin 4 will start and open a browser only when you make it explicitly.
answered Dec 4 at 13:01
Ezze
2601414
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',
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%2f1077469%2fstop-pgadmin-4-from-launching-on-boot-ubuntu-16-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You can disable startup services using:
sudo systemctl stop postgresql
sudo systemctl disable postgresql
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
add a comment |
up vote
0
down vote
You can disable startup services using:
sudo systemctl stop postgresql
sudo systemctl disable postgresql
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
add a comment |
up vote
0
down vote
up vote
0
down vote
You can disable startup services using:
sudo systemctl stop postgresql
sudo systemctl disable postgresql
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
You can disable startup services using:
sudo systemctl stop postgresql
sudo systemctl disable postgresql
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
answered Sep 22 at 15:00
Kristopher Ives
1,4261014
1,4261014
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
add a comment |
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
It would stop postgresql server from starting on boot, but it wouldn't stop pgadmin (even if there'd be no online servers that could be accessed from it). Either way, I don't mind the sql server starting on boot, in fact I desired that, I just don't want pgadmin in particular to do so.
– Bobby Wibowo
Sep 23 at 15:00
add a comment |
up vote
0
down vote
accepted
Turns out it was due to pgadmin4 was still running in the background, so it would launch itself again on next logins. I just killed the process with old school pkill -f pgadmin4 and it would no longer automatically launch itself on next logins. There's no need to stop postgresql service.
answered Sep 26 at 10:33
Bobby Wibowo
114
It waspkill -f pgAdmin4for me instead ofpkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.
– Ezze
Dec 4 at 12:26
add a comment |
up vote
0
down vote
accepted
Turns out it was due to pgadmin4 was still running in the background, so it would launch itself again on next logins. I just killed the process with old school pkill -f pgadmin4 and it would no longer automatically launch itself on next logins. There's no need to stop postgresql service.
answered Sep 26 at 10:33
Bobby Wibowo
114
It waspkill -f pgAdmin4for me instead ofpkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.
– Ezze
Dec 4 at 12:26
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Turns out it was due to pgadmin4 was still running in the background, so it would launch itself again on next logins. I just killed the process with old school pkill -f pgadmin4 and it would no longer automatically launch itself on next logins. There's no need to stop postgresql service.
answered Sep 26 at 10:33
Bobby Wibowo
114
Turns out it was due to pgadmin4 was still running in the background, so it would launch itself again on next logins. I just killed the process with old school pkill -f pgadmin4 and it would no longer automatically launch itself on next logins. There's no need to stop postgresql service.
answered Sep 26 at 10:33
Bobby Wibowo
114
answered Sep 26 at 10:33
Bobby Wibowo
114
answered Sep 26 at 10:33
Bobby Wibowo
114
answered Sep 26 at 10:33
Bobby Wibowo
114
114
It waspkill -f pgAdmin4for me instead ofpkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.
– Ezze
Dec 4 at 12:26
add a comment |
It waspkill -f pgAdmin4for me instead ofpkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.
– Ezze
Dec 4 at 12:26
It was
pkill -f pgAdmin4 for me instead of pkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.– Ezze
Dec 4 at 12:26
It was
pkill -f pgAdmin4 for me instead of pkill -f pgadmin4. I confirm it works but next time you run pgAdmin you have to kill it again if you don't want to start it automatically on next boot.– Ezze
Dec 4 at 12:26
add a comment |
up vote
0
down vote
Facing the same issue on Ubuntu 18.04 with KDE Plasma 5.12.6. The key problem is that KDE saves desktop session and restores it on reboot. That's why pgAdmin 4 starts automatically if it was running before reboot.
In order to fix this go to "System Settings", select "Startup and Shutdown" tab in "Workspace" section and then select "Desktop session":
You will see that "Restore previous session" box is enabled in "On Login" section there. If you want to exclude pgAdmin 4 only from being restored on login then just type a full path to its executable in "Applications to be excluded from sessions":
/usr/bin/pgAdmin4
You can detect a path by running:
which pgAdmin4
If you don't want to save desktop session related data then another simple solution is to tick "Start with an empty session" box.
After that click "Apply" button and reboot the system. Now pgAdmin 4 will start and open a browser only when you make it explicitly.
answered Dec 4 at 13:01
Ezze
2601414
add a comment |
up vote
0
down vote
Facing the same issue on Ubuntu 18.04 with KDE Plasma 5.12.6. The key problem is that KDE saves desktop session and restores it on reboot. That's why pgAdmin 4 starts automatically if it was running before reboot.
In order to fix this go to "System Settings", select "Startup and Shutdown" tab in "Workspace" section and then select "Desktop session":
You will see that "Restore previous session" box is enabled in "On Login" section there. If you want to exclude pgAdmin 4 only from being restored on login then just type a full path to its executable in "Applications to be excluded from sessions":
/usr/bin/pgAdmin4
You can detect a path by running:
which pgAdmin4
If you don't want to save desktop session related data then another simple solution is to tick "Start with an empty session" box.
After that click "Apply" button and reboot the system. Now pgAdmin 4 will start and open a browser only when you make it explicitly.
answered Dec 4 at 13:01
Ezze
2601414
add a comment |
up vote
0
down vote
up vote
0
down vote
Facing the same issue on Ubuntu 18.04 with KDE Plasma 5.12.6. The key problem is that KDE saves desktop session and restores it on reboot. That's why pgAdmin 4 starts automatically if it was running before reboot.
In order to fix this go to "System Settings", select "Startup and Shutdown" tab in "Workspace" section and then select "Desktop session":
You will see that "Restore previous session" box is enabled in "On Login" section there. If you want to exclude pgAdmin 4 only from being restored on login then just type a full path to its executable in "Applications to be excluded from sessions":
/usr/bin/pgAdmin4
You can detect a path by running:
which pgAdmin4
If you don't want to save desktop session related data then another simple solution is to tick "Start with an empty session" box.
After that click "Apply" button and reboot the system. Now pgAdmin 4 will start and open a browser only when you make it explicitly.
answered Dec 4 at 13:01
Ezze
2601414
Facing the same issue on Ubuntu 18.04 with KDE Plasma 5.12.6. The key problem is that KDE saves desktop session and restores it on reboot. That's why pgAdmin 4 starts automatically if it was running before reboot.
In order to fix this go to "System Settings", select "Startup and Shutdown" tab in "Workspace" section and then select "Desktop session":
You will see that "Restore previous session" box is enabled in "On Login" section there. If you want to exclude pgAdmin 4 only from being restored on login then just type a full path to its executable in "Applications to be excluded from sessions":
/usr/bin/pgAdmin4
You can detect a path by running:
which pgAdmin4
If you don't want to save desktop session related data then another simple solution is to tick "Start with an empty session" box.
After that click "Apply" button and reboot the system. Now pgAdmin 4 will start and open a browser only when you make it explicitly.
answered Dec 4 at 13:01
Ezze
2601414
answered Dec 4 at 13:01
Ezze
2601414
answered Dec 4 at 13:01
Ezze
2601414
answered Dec 4 at 13:01
Ezze
2601414
2601414
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1077469%2fstop-pgadmin-4-from-launching-on-boot-ubuntu-16-04%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
