How to uninstall conky
I downloaded conky from github: https://github.com/brndnmtthws/conky
then I installed it using this method:
$ mkdir build
$ cd build
$ ccmake /home/user/conky
# this will launch a curses-based UI where you can configure
# everything, when you are ready you can build as usual:
$ sudo make # This will compile conky in the `src` subdirectory
$ sudo make install
then I wanted to uninstall it; I deleted the directories /build and /conky
and I did sudo apt-get --purge remove conky conky-all
then I rebooted, but conky still starts.
How do I delete conky?
linux conky uninstall
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I downloaded conky from github: https://github.com/brndnmtthws/conky
then I installed it using this method:
$ mkdir build
$ cd build
$ ccmake /home/user/conky
# this will launch a curses-based UI where you can configure
# everything, when you are ready you can build as usual:
$ sudo make # This will compile conky in the `src` subdirectory
$ sudo make install
then I wanted to uninstall it; I deleted the directories /build and /conky
and I did sudo apt-get --purge remove conky conky-all
then I rebooted, but conky still starts.
How do I delete conky?
linux conky uninstall
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I downloaded conky from github: https://github.com/brndnmtthws/conky
then I installed it using this method:
$ mkdir build
$ cd build
$ ccmake /home/user/conky
# this will launch a curses-based UI where you can configure
# everything, when you are ready you can build as usual:
$ sudo make # This will compile conky in the `src` subdirectory
$ sudo make install
then I wanted to uninstall it; I deleted the directories /build and /conky
and I did sudo apt-get --purge remove conky conky-all
then I rebooted, but conky still starts.
How do I delete conky?
linux conky uninstall
I downloaded conky from github: https://github.com/brndnmtthws/conky
then I installed it using this method:
$ mkdir build
$ cd build
$ ccmake /home/user/conky
# this will launch a curses-based UI where you can configure
# everything, when you are ready you can build as usual:
$ sudo make # This will compile conky in the `src` subdirectory
$ sudo make install
then I wanted to uninstall it; I deleted the directories /build and /conky
and I did sudo apt-get --purge remove conky conky-all
then I rebooted, but conky still starts.
How do I delete conky?
linux conky uninstall
linux conky uninstall
asked Jun 5 '17 at 11:49
user1557314user1557314
111
111
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 13 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There is no 100% sure way to find all new files that were installed during the make install since you removed the build directories that might have contained a list of installed (but usually not the overwritten ones) files.
You might try something like
find /directory_path -mtime -1 -ls
(stolen from here), but you may run in all kinds of trouble if you did some more building and installing the time frame.
The apt-get method you tried, fails because you confgured, built and installed outside of the integrated package management system that apt is.
In the future when you want to do this again, make at least an index of the files already installed before the make install
part and do the same afterwards. Comparing those indexes should give you the installed and overwritten files.
Good luck.
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That lastmake uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.
– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
add a comment |
I think I got it.
First I reinstalled using the same method
then I did this:
killall conky
cd build
make clean
cd
sudo rm -r build
sudo rm -r conky
sudo rm -r /usr/local/bin/conky-1.10.7_pre
sudo rm /usr/local/bin/conky
sudo apt-get update ; sudo apt-get autoclean ; sudo apt-get clean ; sudo apt-get autoremove
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f369296%2fhow-to-uninstall-conky%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no 100% sure way to find all new files that were installed during the make install since you removed the build directories that might have contained a list of installed (but usually not the overwritten ones) files.
You might try something like
find /directory_path -mtime -1 -ls
(stolen from here), but you may run in all kinds of trouble if you did some more building and installing the time frame.
The apt-get method you tried, fails because you confgured, built and installed outside of the integrated package management system that apt is.
In the future when you want to do this again, make at least an index of the files already installed before the make install
part and do the same afterwards. Comparing those indexes should give you the installed and overwritten files.
Good luck.
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That lastmake uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.
– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
add a comment |
There is no 100% sure way to find all new files that were installed during the make install since you removed the build directories that might have contained a list of installed (but usually not the overwritten ones) files.
You might try something like
find /directory_path -mtime -1 -ls
(stolen from here), but you may run in all kinds of trouble if you did some more building and installing the time frame.
The apt-get method you tried, fails because you confgured, built and installed outside of the integrated package management system that apt is.
In the future when you want to do this again, make at least an index of the files already installed before the make install
part and do the same afterwards. Comparing those indexes should give you the installed and overwritten files.
Good luck.
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That lastmake uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.
– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
add a comment |
There is no 100% sure way to find all new files that were installed during the make install since you removed the build directories that might have contained a list of installed (but usually not the overwritten ones) files.
You might try something like
find /directory_path -mtime -1 -ls
(stolen from here), but you may run in all kinds of trouble if you did some more building and installing the time frame.
The apt-get method you tried, fails because you confgured, built and installed outside of the integrated package management system that apt is.
In the future when you want to do this again, make at least an index of the files already installed before the make install
part and do the same afterwards. Comparing those indexes should give you the installed and overwritten files.
Good luck.
There is no 100% sure way to find all new files that were installed during the make install since you removed the build directories that might have contained a list of installed (but usually not the overwritten ones) files.
You might try something like
find /directory_path -mtime -1 -ls
(stolen from here), but you may run in all kinds of trouble if you did some more building and installing the time frame.
The apt-get method you tried, fails because you confgured, built and installed outside of the integrated package management system that apt is.
In the future when you want to do this again, make at least an index of the files already installed before the make install
part and do the same afterwards. Comparing those indexes should give you the installed and overwritten files.
Good luck.
answered Jun 5 '17 at 13:12
JdeHaanJdeHaan
357213
357213
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That lastmake uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.
– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
add a comment |
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That lastmake uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.
– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
1
1
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
consider downloading the package again, creating the makefile, then running "make uninstall"?
– Jeff Schaller
Jun 5 '17 at 13:16
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
tried it, didn't work unfortunately.
– user1557314
Jun 5 '17 at 13:37
That last
make uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.– JdeHaan
Jun 5 '17 at 13:41
That last
make uninstall
might have failed because conky was still running (a executable file deletion in linux does not actually become effective until all processes using it are ended). Try a reboot.– JdeHaan
Jun 5 '17 at 13:41
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@JdeHaan what? Executables do get deleted even if they’re running. The space they occupy isn’t recovered until all running processes using them have closed the corresponding file descriptor (same as any file on Unix-style systems), but they do disappear from the directory containing them.
– Stephen Kitt
Jun 5 '17 at 13:58
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
@Stephen Kitt: true, more accurate.
– JdeHaan
Jun 5 '17 at 14:23
add a comment |
I think I got it.
First I reinstalled using the same method
then I did this:
killall conky
cd build
make clean
cd
sudo rm -r build
sudo rm -r conky
sudo rm -r /usr/local/bin/conky-1.10.7_pre
sudo rm /usr/local/bin/conky
sudo apt-get update ; sudo apt-get autoclean ; sudo apt-get clean ; sudo apt-get autoremove
add a comment |
I think I got it.
First I reinstalled using the same method
then I did this:
killall conky
cd build
make clean
cd
sudo rm -r build
sudo rm -r conky
sudo rm -r /usr/local/bin/conky-1.10.7_pre
sudo rm /usr/local/bin/conky
sudo apt-get update ; sudo apt-get autoclean ; sudo apt-get clean ; sudo apt-get autoremove
add a comment |
I think I got it.
First I reinstalled using the same method
then I did this:
killall conky
cd build
make clean
cd
sudo rm -r build
sudo rm -r conky
sudo rm -r /usr/local/bin/conky-1.10.7_pre
sudo rm /usr/local/bin/conky
sudo apt-get update ; sudo apt-get autoclean ; sudo apt-get clean ; sudo apt-get autoremove
I think I got it.
First I reinstalled using the same method
then I did this:
killall conky
cd build
make clean
cd
sudo rm -r build
sudo rm -r conky
sudo rm -r /usr/local/bin/conky-1.10.7_pre
sudo rm /usr/local/bin/conky
sudo apt-get update ; sudo apt-get autoclean ; sudo apt-get clean ; sudo apt-get autoremove
answered Jun 5 '17 at 13:36
user1557314user1557314
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f369296%2fhow-to-uninstall-conky%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