How to avoid password prompt when starting Synaptic?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Whenever I start the Synaptic package manager, it asks for a password. How do I make it skip that dialog?



I'm using Debian 9.8.










share|improve this question

























  • It will not be a problem for Debian 10. (-:

    – JdeBP
    14 mins ago











  • @JdeBP Why? What are people supposed to use for package management? Only terminal?

    – Fabian Röling
    13 mins ago











  • Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

    – Fabian Röling
    12 mins ago


















0















Whenever I start the Synaptic package manager, it asks for a password. How do I make it skip that dialog?



I'm using Debian 9.8.










share|improve this question

























  • It will not be a problem for Debian 10. (-:

    – JdeBP
    14 mins ago











  • @JdeBP Why? What are people supposed to use for package management? Only terminal?

    – Fabian Röling
    13 mins ago











  • Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

    – Fabian Röling
    12 mins ago














0












0








0








Whenever I start the Synaptic package manager, it asks for a password. How do I make it skip that dialog?



I'm using Debian 9.8.










share|improve this question
















Whenever I start the Synaptic package manager, it asks for a password. How do I make it skip that dialog?



I'm using Debian 9.8.







debian sudo password root synaptic






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 35 mins ago









Rui F Ribeiro

41.9k1483142




41.9k1483142










asked 41 mins ago









Fabian RölingFabian Röling

8111




8111













  • It will not be a problem for Debian 10. (-:

    – JdeBP
    14 mins ago











  • @JdeBP Why? What are people supposed to use for package management? Only terminal?

    – Fabian Röling
    13 mins ago











  • Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

    – Fabian Röling
    12 mins ago



















  • It will not be a problem for Debian 10. (-:

    – JdeBP
    14 mins ago











  • @JdeBP Why? What are people supposed to use for package management? Only terminal?

    – Fabian Röling
    13 mins ago











  • Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

    – Fabian Röling
    12 mins ago

















It will not be a problem for Debian 10. (-:

– JdeBP
14 mins ago





It will not be a problem for Debian 10. (-:

– JdeBP
14 mins ago













@JdeBP Why? What are people supposed to use for package management? Only terminal?

– Fabian Röling
13 mins ago





@JdeBP Why? What are people supposed to use for package management? Only terminal?

– Fabian Röling
13 mins ago













Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

– Fabian Röling
12 mins ago





Also, this is technically not Synaptic specific, but that's the only program where I remember encountering that, so people will likely search for that.

– Fabian Röling
12 mins ago










1 Answer
1






active

oldest

votes


















0














Edit the file /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy (yes, even in Debian), it's an XML document. In the <policyconfig> tag, there is a <action id="com.ubuntu.pkexec.synaptic"> tag, somewhere in there is a <defaults> tag. This tag includes the tags <allow_any>, <allow_inactive> and <allow_active>. Set the value in all of them to yes. Now the prompt should be skipped.



The same also works for other prompts like this. They all have a "Details" button, clicking that shows which the exact ID of the program is that requests root access. Edit the corresponding <ID>.policy file in a similar way to skip their prompts.






share|improve this answer
























  • No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

    – muru
    2 mins ago














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


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510927%2fhow-to-avoid-password-prompt-when-starting-synaptic%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









0














Edit the file /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy (yes, even in Debian), it's an XML document. In the <policyconfig> tag, there is a <action id="com.ubuntu.pkexec.synaptic"> tag, somewhere in there is a <defaults> tag. This tag includes the tags <allow_any>, <allow_inactive> and <allow_active>. Set the value in all of them to yes. Now the prompt should be skipped.



The same also works for other prompts like this. They all have a "Details" button, clicking that shows which the exact ID of the program is that requests root access. Edit the corresponding <ID>.policy file in a similar way to skip their prompts.






share|improve this answer
























  • No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

    – muru
    2 mins ago


















0














Edit the file /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy (yes, even in Debian), it's an XML document. In the <policyconfig> tag, there is a <action id="com.ubuntu.pkexec.synaptic"> tag, somewhere in there is a <defaults> tag. This tag includes the tags <allow_any>, <allow_inactive> and <allow_active>. Set the value in all of them to yes. Now the prompt should be skipped.



The same also works for other prompts like this. They all have a "Details" button, clicking that shows which the exact ID of the program is that requests root access. Edit the corresponding <ID>.policy file in a similar way to skip their prompts.






share|improve this answer
























  • No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

    – muru
    2 mins ago
















0












0








0







Edit the file /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy (yes, even in Debian), it's an XML document. In the <policyconfig> tag, there is a <action id="com.ubuntu.pkexec.synaptic"> tag, somewhere in there is a <defaults> tag. This tag includes the tags <allow_any>, <allow_inactive> and <allow_active>. Set the value in all of them to yes. Now the prompt should be skipped.



The same also works for other prompts like this. They all have a "Details" button, clicking that shows which the exact ID of the program is that requests root access. Edit the corresponding <ID>.policy file in a similar way to skip their prompts.






share|improve this answer













Edit the file /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy (yes, even in Debian), it's an XML document. In the <policyconfig> tag, there is a <action id="com.ubuntu.pkexec.synaptic"> tag, somewhere in there is a <defaults> tag. This tag includes the tags <allow_any>, <allow_inactive> and <allow_active>. Set the value in all of them to yes. Now the prompt should be skipped.



The same also works for other prompts like this. They all have a "Details" button, clicking that shows which the exact ID of the program is that requests root access. Edit the corresponding <ID>.policy file in a similar way to skip their prompts.







share|improve this answer












share|improve this answer



share|improve this answer










answered 41 mins ago









Fabian RölingFabian Röling

8111




8111













  • No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

    – muru
    2 mins ago





















  • No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

    – muru
    2 mins ago



















No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

– muru
2 mins ago







No, that's not the way to do this. Any edits to files in /usr/share will be lost when the package owning that file gets updated. The right way to set Polkit privileges is to create PKLA files in /etc/polkit-1, allowing your user the com.ubuntu.pkexec.synaptic.policy action with allow_active, etc. set to yes. You don't need to, and shouldn't, edit these XML files instead. See, e.g., askubuntu.com/a/614537/158442

– muru
2 mins ago




















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510927%2fhow-to-avoid-password-prompt-when-starting-synaptic%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震