debian without dbus: login/systemd complains about failing to connect to d-bus after motd

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












4















I have barebones raspbian, i.e. basically Debian 8, with systemd and no X. I removed dbus with "apt-get remove dbus". It deinstalled cleanly, with no apparent programs depending on it. Now, whenever I login on the console after the motd I get this line:




Failed to get D-Bus connection: No such file or directory




What's the source of that message, and how can I make it stop? Must be something somewhere in /etc I can set, right?



It looks like systemd still thinks there is a dbus. There is still a dbus.service which I manually disabled with systemctl, just to be sure. It complained (inserv warning current start runlevel(s) (empty) of script dbus overrides LSB defaults ....) but, all my services do seem normal; I don't know for sure. Running "systemctl start anythinghere" as non-root produces the same error. So user-level privilege systemd, whatever it is called, appears to be the source but I don't have systemd-logind running on my system, and I don't understand how /bin/login is calling systemd.










share|improve this question
























  • Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

    – dirkt
    Dec 21 '16 at 8:38















4















I have barebones raspbian, i.e. basically Debian 8, with systemd and no X. I removed dbus with "apt-get remove dbus". It deinstalled cleanly, with no apparent programs depending on it. Now, whenever I login on the console after the motd I get this line:




Failed to get D-Bus connection: No such file or directory




What's the source of that message, and how can I make it stop? Must be something somewhere in /etc I can set, right?



It looks like systemd still thinks there is a dbus. There is still a dbus.service which I manually disabled with systemctl, just to be sure. It complained (inserv warning current start runlevel(s) (empty) of script dbus overrides LSB defaults ....) but, all my services do seem normal; I don't know for sure. Running "systemctl start anythinghere" as non-root produces the same error. So user-level privilege systemd, whatever it is called, appears to be the source but I don't have systemd-logind running on my system, and I don't understand how /bin/login is calling systemd.










share|improve this question
























  • Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

    – dirkt
    Dec 21 '16 at 8:38













4












4








4








I have barebones raspbian, i.e. basically Debian 8, with systemd and no X. I removed dbus with "apt-get remove dbus". It deinstalled cleanly, with no apparent programs depending on it. Now, whenever I login on the console after the motd I get this line:




Failed to get D-Bus connection: No such file or directory




What's the source of that message, and how can I make it stop? Must be something somewhere in /etc I can set, right?



It looks like systemd still thinks there is a dbus. There is still a dbus.service which I manually disabled with systemctl, just to be sure. It complained (inserv warning current start runlevel(s) (empty) of script dbus overrides LSB defaults ....) but, all my services do seem normal; I don't know for sure. Running "systemctl start anythinghere" as non-root produces the same error. So user-level privilege systemd, whatever it is called, appears to be the source but I don't have systemd-logind running on my system, and I don't understand how /bin/login is calling systemd.










share|improve this question
















I have barebones raspbian, i.e. basically Debian 8, with systemd and no X. I removed dbus with "apt-get remove dbus". It deinstalled cleanly, with no apparent programs depending on it. Now, whenever I login on the console after the motd I get this line:




Failed to get D-Bus connection: No such file or directory




What's the source of that message, and how can I make it stop? Must be something somewhere in /etc I can set, right?



It looks like systemd still thinks there is a dbus. There is still a dbus.service which I manually disabled with systemctl, just to be sure. It complained (inserv warning current start runlevel(s) (empty) of script dbus overrides LSB defaults ....) but, all my services do seem normal; I don't know for sure. Running "systemctl start anythinghere" as non-root produces the same error. So user-level privilege systemd, whatever it is called, appears to be the source but I don't have systemd-logind running on my system, and I don't understand how /bin/login is calling systemd.







debian systemd d-bus






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '16 at 2:52









Jeff Schaller

41k1056131




41k1056131










asked Dec 21 '16 at 3:42









TibinahTibinah

213




213












  • Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

    – dirkt
    Dec 21 '16 at 8:38

















  • Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

    – dirkt
    Dec 21 '16 at 8:38
















Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

– dirkt
Dec 21 '16 at 8:38





Systemd is very likely tightly integrated with DBus. If you want to get rid of both, have a look at Devuan, though I don't think there's something ready-made for the RaspPi.

– dirkt
Dec 21 '16 at 8:38










3 Answers
3






active

oldest

votes


















0














Maybe some package only recommends the dbus package, you could try to run apt-get rdepends --installed dbus to see if anything has still references to it






share|improve this answer























  • Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

    – Tibinah
    Dec 21 '16 at 15:48











  • What about libpam-systemd?

    – Bigon
    Dec 21 '16 at 21:50


















0














The culprit is service ssh status executed by /etc/profile.d/sshpasswd.sh. The funny part is how there is no openssh installed on the system.






share|improve this answer


















  • 1





    See raspberrypi.stackexchange.com/a/58470/30915

    – JdeBP
    Dec 21 '16 at 19:30


















0














This command helped remove orphan packages:



apt-get autoremove



Might write your own Kernel to remove services and daemons from the source: take out anything ssh, dbus, etc.



My fun has been taking Mint 17 to the bare bones: firefox with flash, sauerbraten and wesnoth, and to play DVDs.



No more Python, Gnome, or GTK. Now, working to remove dbus. Went from 2,000 packages installed to only 775. The computer is more responsive and uses 20% less CPU, but ping still around 200.



My motivation for this is to simplify Linux Mint and remove all the red tape it is wrapped in. I like multimedia support and excellent installation with Mint, but feel we've digressed a bit on the size of the install and the 'CPU and HDD are infinite' philosophy.






share|improve this answer























  • Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

    – Shadur
    Jun 30 '17 at 10:05










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%2f331817%2fdebian-without-dbus-login-systemd-complains-about-failing-to-connect-to-d-bus-a%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









0














Maybe some package only recommends the dbus package, you could try to run apt-get rdepends --installed dbus to see if anything has still references to it






share|improve this answer























  • Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

    – Tibinah
    Dec 21 '16 at 15:48











  • What about libpam-systemd?

    – Bigon
    Dec 21 '16 at 21:50















0














Maybe some package only recommends the dbus package, you could try to run apt-get rdepends --installed dbus to see if anything has still references to it






share|improve this answer























  • Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

    – Tibinah
    Dec 21 '16 at 15:48











  • What about libpam-systemd?

    – Bigon
    Dec 21 '16 at 21:50













0












0








0







Maybe some package only recommends the dbus package, you could try to run apt-get rdepends --installed dbus to see if anything has still references to it






share|improve this answer













Maybe some package only recommends the dbus package, you could try to run apt-get rdepends --installed dbus to see if anything has still references to it







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 21 '16 at 9:22









BigonBigon

1,257713




1,257713












  • Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

    – Tibinah
    Dec 21 '16 at 15:48











  • What about libpam-systemd?

    – Bigon
    Dec 21 '16 at 21:50

















  • Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

    – Tibinah
    Dec 21 '16 at 15:48











  • What about libpam-systemd?

    – Bigon
    Dec 21 '16 at 21:50
















Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

– Tibinah
Dec 21 '16 at 15:48





Thanks, didn't think of that! I'm As you meant apt-cache rdepends --installed dbus. There was still a libdbus-1-3 installed on thtis system. Removing that didn't help. The only other package is systemd, which I confirms my initial suspicion.

– Tibinah
Dec 21 '16 at 15:48













What about libpam-systemd?

– Bigon
Dec 21 '16 at 21:50





What about libpam-systemd?

– Bigon
Dec 21 '16 at 21:50













0














The culprit is service ssh status executed by /etc/profile.d/sshpasswd.sh. The funny part is how there is no openssh installed on the system.






share|improve this answer


















  • 1





    See raspberrypi.stackexchange.com/a/58470/30915

    – JdeBP
    Dec 21 '16 at 19:30















0














The culprit is service ssh status executed by /etc/profile.d/sshpasswd.sh. The funny part is how there is no openssh installed on the system.






share|improve this answer


















  • 1





    See raspberrypi.stackexchange.com/a/58470/30915

    – JdeBP
    Dec 21 '16 at 19:30













0












0








0







The culprit is service ssh status executed by /etc/profile.d/sshpasswd.sh. The funny part is how there is no openssh installed on the system.






share|improve this answer













The culprit is service ssh status executed by /etc/profile.d/sshpasswd.sh. The funny part is how there is no openssh installed on the system.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 21 '16 at 16:24









TibinahTibinah

213




213







  • 1





    See raspberrypi.stackexchange.com/a/58470/30915

    – JdeBP
    Dec 21 '16 at 19:30












  • 1





    See raspberrypi.stackexchange.com/a/58470/30915

    – JdeBP
    Dec 21 '16 at 19:30







1




1





See raspberrypi.stackexchange.com/a/58470/30915

– JdeBP
Dec 21 '16 at 19:30





See raspberrypi.stackexchange.com/a/58470/30915

– JdeBP
Dec 21 '16 at 19:30











0














This command helped remove orphan packages:



apt-get autoremove



Might write your own Kernel to remove services and daemons from the source: take out anything ssh, dbus, etc.



My fun has been taking Mint 17 to the bare bones: firefox with flash, sauerbraten and wesnoth, and to play DVDs.



No more Python, Gnome, or GTK. Now, working to remove dbus. Went from 2,000 packages installed to only 775. The computer is more responsive and uses 20% less CPU, but ping still around 200.



My motivation for this is to simplify Linux Mint and remove all the red tape it is wrapped in. I like multimedia support and excellent installation with Mint, but feel we've digressed a bit on the size of the install and the 'CPU and HDD are infinite' philosophy.






share|improve this answer























  • Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

    – Shadur
    Jun 30 '17 at 10:05















0














This command helped remove orphan packages:



apt-get autoremove



Might write your own Kernel to remove services and daemons from the source: take out anything ssh, dbus, etc.



My fun has been taking Mint 17 to the bare bones: firefox with flash, sauerbraten and wesnoth, and to play DVDs.



No more Python, Gnome, or GTK. Now, working to remove dbus. Went from 2,000 packages installed to only 775. The computer is more responsive and uses 20% less CPU, but ping still around 200.



My motivation for this is to simplify Linux Mint and remove all the red tape it is wrapped in. I like multimedia support and excellent installation with Mint, but feel we've digressed a bit on the size of the install and the 'CPU and HDD are infinite' philosophy.






share|improve this answer























  • Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

    – Shadur
    Jun 30 '17 at 10:05













0












0








0







This command helped remove orphan packages:



apt-get autoremove



Might write your own Kernel to remove services and daemons from the source: take out anything ssh, dbus, etc.



My fun has been taking Mint 17 to the bare bones: firefox with flash, sauerbraten and wesnoth, and to play DVDs.



No more Python, Gnome, or GTK. Now, working to remove dbus. Went from 2,000 packages installed to only 775. The computer is more responsive and uses 20% less CPU, but ping still around 200.



My motivation for this is to simplify Linux Mint and remove all the red tape it is wrapped in. I like multimedia support and excellent installation with Mint, but feel we've digressed a bit on the size of the install and the 'CPU and HDD are infinite' philosophy.






share|improve this answer













This command helped remove orphan packages:



apt-get autoremove



Might write your own Kernel to remove services and daemons from the source: take out anything ssh, dbus, etc.



My fun has been taking Mint 17 to the bare bones: firefox with flash, sauerbraten and wesnoth, and to play DVDs.



No more Python, Gnome, or GTK. Now, working to remove dbus. Went from 2,000 packages installed to only 775. The computer is more responsive and uses 20% less CPU, but ping still around 200.



My motivation for this is to simplify Linux Mint and remove all the red tape it is wrapped in. I like multimedia support and excellent installation with Mint, but feel we've digressed a bit on the size of the install and the 'CPU and HDD are infinite' philosophy.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 26 '16 at 2:01









MikeMike

1




1












  • Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

    – Shadur
    Jun 30 '17 at 10:05

















  • Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

    – Shadur
    Jun 30 '17 at 10:05
















Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

– Shadur
Jun 30 '17 at 10:05





Careful with the custom kernel. Keep the default handy as backup until you're absolutely sure that you didn't need the driver you removed. Not everything is named obviously and it's really embarrassing to remote reboot a system only to find out you'd forgotten the driver for its HDD controller...

– Shadur
Jun 30 '17 at 10:05

















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%2f331817%2fdebian-without-dbus-login-systemd-complains-about-failing-to-connect-to-d-bus-a%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

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay