Processing triggers for man-db
When running sudo aptitude upgrade, the console freezes for long after almost every package upgrade with a message "Processing triggers for man-db ...". What could be the problem and how can I fix it?
Ubuntu version: 12.04 (both Server and Xubuntu)
Thanks in advance.
Update: It looks like this problem is related to package autofs upon my further tests. Removing autofs resolved the issues. No idea why. I then have to use soft links instead of autofs for my file system to avoid this issue (and other two issues posted here as well).
12.04
asked Mar 25 '13 at 13:12
slacktty
2616
add a comment |
When running sudo aptitude upgrade, the console freezes for long after almost every package upgrade with a message "Processing triggers for man-db ...". What could be the problem and how can I fix it?
Ubuntu version: 12.04 (both Server and Xubuntu)
Thanks in advance.
Update: It looks like this problem is related to package autofs upon my further tests. Removing autofs resolved the issues. No idea why. I then have to use soft links instead of autofs for my file system to avoid this issue (and other two issues posted here as well).
12.04
asked Mar 25 '13 at 13:12
slacktty
2616
I have the same problem, will see if removingautofshelps. Thanks!
– Lukas Stejskal
May 1 '13 at 8:54
add a comment |
When running sudo aptitude upgrade, the console freezes for long after almost every package upgrade with a message "Processing triggers for man-db ...". What could be the problem and how can I fix it?
Ubuntu version: 12.04 (both Server and Xubuntu)
Thanks in advance.
Update: It looks like this problem is related to package autofs upon my further tests. Removing autofs resolved the issues. No idea why. I then have to use soft links instead of autofs for my file system to avoid this issue (and other two issues posted here as well).
12.04
asked Mar 25 '13 at 13:12
slacktty
2616
When running sudo aptitude upgrade, the console freezes for long after almost every package upgrade with a message "Processing triggers for man-db ...". What could be the problem and how can I fix it?
Ubuntu version: 12.04 (both Server and Xubuntu)
Thanks in advance.
Update: It looks like this problem is related to package autofs upon my further tests. Removing autofs resolved the issues. No idea why. I then have to use soft links instead of autofs for my file system to avoid this issue (and other two issues posted here as well).
12.04
12.04
asked Mar 25 '13 at 13:12
slacktty
2616
asked Mar 25 '13 at 13:12
slacktty
2616
edited Mar 25 '13 at 15:53
asked Mar 25 '13 at 13:12
slacktty
2616
asked Mar 25 '13 at 13:12
slacktty
2616
asked Mar 25 '13 at 13:12
slacktty
2616
2616
I have the same problem, will see if removingautofshelps. Thanks!
– Lukas Stejskal
May 1 '13 at 8:54
add a comment |
I have the same problem, will see if removingautofshelps. Thanks!
– Lukas Stejskal
May 1 '13 at 8:54
I have the same problem, will see if removing
autofs helps. Thanks!– Lukas Stejskal
May 1 '13 at 8:54
I have the same problem, will see if removing
autofs helps. Thanks!– Lukas Stejskal
May 1 '13 at 8:54
add a comment |
2 Answers
2
active
oldest
votes
I had something similar just after installing Ubuntu 18.04 on Windows Subsystem for Linux and running update and upgrade: it got stuck at processing triggers for man-db (2.8.3-2).
And also later, after running
sudo apt install python3-pip
My solution: I just waited. In the second case even some 15 minutes.
I do not know whether this is normal, as I am very new to Linux. But this so people just know another experience if they run into the same problem.
answered Aug 11 at 8:32
oxfos
11
add a comment |
Might be helpful for someone: I ran into this issue on our CI regularly.
Just execute the following:
sudo apt-get remove -y --purge man-db
The command removes the man-db package completely, which in our case on CI, was completely useless anyway.
answered Dec 8 at 19:46
Andreas
1011
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%2f272248%2fprocessing-triggers-for-man-db%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
I had something similar just after installing Ubuntu 18.04 on Windows Subsystem for Linux and running update and upgrade: it got stuck at processing triggers for man-db (2.8.3-2).
And also later, after running
sudo apt install python3-pip
My solution: I just waited. In the second case even some 15 minutes.
I do not know whether this is normal, as I am very new to Linux. But this so people just know another experience if they run into the same problem.
answered Aug 11 at 8:32
oxfos
11
add a comment |
I had something similar just after installing Ubuntu 18.04 on Windows Subsystem for Linux and running update and upgrade: it got stuck at processing triggers for man-db (2.8.3-2).
And also later, after running
sudo apt install python3-pip
My solution: I just waited. In the second case even some 15 minutes.
I do not know whether this is normal, as I am very new to Linux. But this so people just know another experience if they run into the same problem.
answered Aug 11 at 8:32
oxfos
11
add a comment |
I had something similar just after installing Ubuntu 18.04 on Windows Subsystem for Linux and running update and upgrade: it got stuck at processing triggers for man-db (2.8.3-2).
And also later, after running
sudo apt install python3-pip
My solution: I just waited. In the second case even some 15 minutes.
I do not know whether this is normal, as I am very new to Linux. But this so people just know another experience if they run into the same problem.
answered Aug 11 at 8:32
oxfos
11
I had something similar just after installing Ubuntu 18.04 on Windows Subsystem for Linux and running update and upgrade: it got stuck at processing triggers for man-db (2.8.3-2).
And also later, after running
sudo apt install python3-pip
My solution: I just waited. In the second case even some 15 minutes.
I do not know whether this is normal, as I am very new to Linux. But this so people just know another experience if they run into the same problem.
answered Aug 11 at 8:32
oxfos
11
answered Aug 11 at 8:32
oxfos
11
answered Aug 11 at 8:32
oxfos
11
answered Aug 11 at 8:32
oxfos
11
11
add a comment |
add a comment |
Might be helpful for someone: I ran into this issue on our CI regularly.
Just execute the following:
sudo apt-get remove -y --purge man-db
The command removes the man-db package completely, which in our case on CI, was completely useless anyway.
answered Dec 8 at 19:46
Andreas
1011
add a comment |
Might be helpful for someone: I ran into this issue on our CI regularly.
Just execute the following:
sudo apt-get remove -y --purge man-db
The command removes the man-db package completely, which in our case on CI, was completely useless anyway.
answered Dec 8 at 19:46
Andreas
1011
add a comment |
Might be helpful for someone: I ran into this issue on our CI regularly.
Just execute the following:
sudo apt-get remove -y --purge man-db
The command removes the man-db package completely, which in our case on CI, was completely useless anyway.
answered Dec 8 at 19:46
Andreas
1011
Might be helpful for someone: I ran into this issue on our CI regularly.
Just execute the following:
sudo apt-get remove -y --purge man-db
The command removes the man-db package completely, which in our case on CI, was completely useless anyway.
answered Dec 8 at 19:46
Andreas
1011
answered Dec 8 at 19:46
Andreas
1011
answered Dec 8 at 19:46
Andreas
1011
answered Dec 8 at 19:46
Andreas
1011
1011
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%2f272248%2fprocessing-triggers-for-man-db%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
I have the same problem, will see if removing
autofshelps. Thanks!– Lukas Stejskal
May 1 '13 at 8:54