What is the matter with my package manager?












1














My os info.



uname -a
Linux hwy 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux


Everytime it encounters some error info after installing new soft.



sh: 1: /bin/echo: Permission denied
E: Problem executing scripts DPkg::Post-Invoke '/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null'
E: Sub-process returned an error code


What is the matter with my package manager?



stat /bin/echo
File: /bin/echo
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 802h/2050d Inode: 3932206 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: ( 43/ utmp)
Access: 2018-12-01 08:03:07.846890937 +0800
Modify: 2018-12-01 08:03:07.846890937 +0800
Change: 2018-12-01 08:03:07.846890937 +0800
Birth: -









share|improve this question




















  • 4




    What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
    – Ulrich Schwarz
    Dec 17 at 6:46










  • Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
    – Kusalananda
    Dec 17 at 7:27








  • 2




    You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
    – Henrik
    Dec 17 at 7:28






  • 2




    Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
    – 炸鱼薯条德里克
    Dec 17 at 7:34
















1














My os info.



uname -a
Linux hwy 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux


Everytime it encounters some error info after installing new soft.



sh: 1: /bin/echo: Permission denied
E: Problem executing scripts DPkg::Post-Invoke '/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null'
E: Sub-process returned an error code


What is the matter with my package manager?



stat /bin/echo
File: /bin/echo
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 802h/2050d Inode: 3932206 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: ( 43/ utmp)
Access: 2018-12-01 08:03:07.846890937 +0800
Modify: 2018-12-01 08:03:07.846890937 +0800
Change: 2018-12-01 08:03:07.846890937 +0800
Birth: -









share|improve this question




















  • 4




    What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
    – Ulrich Schwarz
    Dec 17 at 6:46










  • Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
    – Kusalananda
    Dec 17 at 7:27








  • 2




    You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
    – Henrik
    Dec 17 at 7:28






  • 2




    Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
    – 炸鱼薯条德里克
    Dec 17 at 7:34














1












1








1







My os info.



uname -a
Linux hwy 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux


Everytime it encounters some error info after installing new soft.



sh: 1: /bin/echo: Permission denied
E: Problem executing scripts DPkg::Post-Invoke '/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null'
E: Sub-process returned an error code


What is the matter with my package manager?



stat /bin/echo
File: /bin/echo
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 802h/2050d Inode: 3932206 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: ( 43/ utmp)
Access: 2018-12-01 08:03:07.846890937 +0800
Modify: 2018-12-01 08:03:07.846890937 +0800
Change: 2018-12-01 08:03:07.846890937 +0800
Birth: -









share|improve this question















My os info.



uname -a
Linux hwy 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux


Everytime it encounters some error info after installing new soft.



sh: 1: /bin/echo: Permission denied
E: Problem executing scripts DPkg::Post-Invoke '/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null'
E: Sub-process returned an error code


What is the matter with my package manager?



stat /bin/echo
File: /bin/echo
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 802h/2050d Inode: 3932206 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 0/ root) Gid: ( 43/ utmp)
Access: 2018-12-01 08:03:07.846890937 +0800
Modify: 2018-12-01 08:03:07.846890937 +0800
Change: 2018-12-01 08:03:07.846890937 +0800
Birth: -






dpkg






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 17 at 6:58

























asked Dec 17 at 6:41









it_is_a_literature

20742757




20742757








  • 4




    What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
    – Ulrich Schwarz
    Dec 17 at 6:46










  • Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
    – Kusalananda
    Dec 17 at 7:27








  • 2




    You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
    – Henrik
    Dec 17 at 7:28






  • 2




    Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
    – 炸鱼薯条德里克
    Dec 17 at 7:34














  • 4




    What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
    – Ulrich Schwarz
    Dec 17 at 6:46










  • Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
    – Kusalananda
    Dec 17 at 7:27








  • 2




    You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
    – Henrik
    Dec 17 at 7:28






  • 2




    Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
    – 炸鱼薯条德里克
    Dec 17 at 7:34








4




4




What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
– Ulrich Schwarz
Dec 17 at 6:46




What does stat /bin/echo say? echo is also a shell builtin (in at least bash and zsh), so you wouldn't notice quickly if you removed permissions on /bin/echo by accident.
– Ulrich Schwarz
Dec 17 at 6:46












Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
– Kusalananda
Dec 17 at 7:27






Did you do this?: Accidentally changing permission of '/' directory to 'chmod 660 '
– Kusalananda
Dec 17 at 7:27






2




2




You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
– Henrik
Dec 17 at 7:28




You have done something unfortunate to your /bin/echo. stat says it's zero bytes and not executable, neither should be the case. On Debian /bin/echo comes from the coreutils package, so you could try to reinstall that with apt install --reinstall coreutils. I have no idea whether that actually works for essential packages (like coreutils), and in any case it's probably a sign that you've done something bad to your system, so it might just delay the probably inevitable reinstallation.
– Henrik
Dec 17 at 7:28




2




2




Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
– 炸鱼薯条德里克
Dec 17 at 7:34




Although we can only see echo's problem here. But I'm pretty sure you broke your system by accident but you didn't tell us what you've done. The best suggestion would just be re-install your system.
– 炸鱼薯条德里克
Dec 17 at 7:34










1 Answer
1






active

oldest

votes


















0














sudo apt install --reinstall coreutils
sudo apt autoremove
stat /bin/echo
File: /bin/echo
Size: 31464 Blocks: 64 IO Block: 4096 regular file
Device: 802h/2050d Inode: 3932296 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-12-17 18:41:38.876797380 +0800
Modify: 2017-02-22 20:23:45.000000000 +0800
Change: 2018-12-17 18:41:32.229517688 +0800
Birth: -





share|improve this answer

















  • 1




    Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
    – Henrik
    Dec 17 at 19:42










  • No record in history,i forgot.
    – it_is_a_literature
    Dec 18 at 1:42











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%2f489415%2fwhat-is-the-matter-with-my-package-manager%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














sudo apt install --reinstall coreutils
sudo apt autoremove
stat /bin/echo
File: /bin/echo
Size: 31464 Blocks: 64 IO Block: 4096 regular file
Device: 802h/2050d Inode: 3932296 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-12-17 18:41:38.876797380 +0800
Modify: 2017-02-22 20:23:45.000000000 +0800
Change: 2018-12-17 18:41:32.229517688 +0800
Birth: -





share|improve this answer

















  • 1




    Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
    – Henrik
    Dec 17 at 19:42










  • No record in history,i forgot.
    – it_is_a_literature
    Dec 18 at 1:42
















0














sudo apt install --reinstall coreutils
sudo apt autoremove
stat /bin/echo
File: /bin/echo
Size: 31464 Blocks: 64 IO Block: 4096 regular file
Device: 802h/2050d Inode: 3932296 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-12-17 18:41:38.876797380 +0800
Modify: 2017-02-22 20:23:45.000000000 +0800
Change: 2018-12-17 18:41:32.229517688 +0800
Birth: -





share|improve this answer

















  • 1




    Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
    – Henrik
    Dec 17 at 19:42










  • No record in history,i forgot.
    – it_is_a_literature
    Dec 18 at 1:42














0












0








0






sudo apt install --reinstall coreutils
sudo apt autoremove
stat /bin/echo
File: /bin/echo
Size: 31464 Blocks: 64 IO Block: 4096 regular file
Device: 802h/2050d Inode: 3932296 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-12-17 18:41:38.876797380 +0800
Modify: 2017-02-22 20:23:45.000000000 +0800
Change: 2018-12-17 18:41:32.229517688 +0800
Birth: -





share|improve this answer












sudo apt install --reinstall coreutils
sudo apt autoremove
stat /bin/echo
File: /bin/echo
Size: 31464 Blocks: 64 IO Block: 4096 regular file
Device: 802h/2050d Inode: 3932296 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2018-12-17 18:41:38.876797380 +0800
Modify: 2017-02-22 20:23:45.000000000 +0800
Change: 2018-12-17 18:41:32.229517688 +0800
Birth: -






share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 17 at 10:44









it_is_a_literature

20742757




20742757








  • 1




    Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
    – Henrik
    Dec 17 at 19:42










  • No record in history,i forgot.
    – it_is_a_literature
    Dec 18 at 1:42














  • 1




    Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
    – Henrik
    Dec 17 at 19:42










  • No record in history,i forgot.
    – it_is_a_literature
    Dec 18 at 1:42








1




1




Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
– Henrik
Dec 17 at 19:42




Okay, so you managed to get a normal /bin/echo by reinstalling the coreutils package, then that will hopefully not cause you any more problems. But without knowedge of how your /bin/echo ended up that way, you have no idea what other errors are in your installation.
– Henrik
Dec 17 at 19:42












No record in history,i forgot.
– it_is_a_literature
Dec 18 at 1:42




No record in history,i forgot.
– it_is_a_literature
Dec 18 at 1:42


















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.





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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489415%2fwhat-is-the-matter-with-my-package-manager%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

Morgemoulin

Scott Moir

Souastre