On Fri, 22 Aug 2014 07:47:43 +0200
Jochen Spieker <m...@well-adjusted.de> wrote:
> To me it looks like systemd is unable to start any service, maybe
> because of the missing/unconfigured libpam-systemd. I would probably
> try to dpgk --force-depends libpam-systemd or something like that. But
> I am just guessing.
Well, wrong guess for 2 reasons: 'dpgk' is not a known program ;) and
more seriously, forcing even all in dpkg didn't work.
I downgraded dpkg to the -1 version (bugreport say there's problem
with symlink path), then tried to force dbus install (-1 version)
without success:
# dpkg --force-all -i dbus_1.8.6-1_i386.deb
(Reading database ... 446321 files and directories currently installed.)
Preparing to unpack dbus_1.8.6-1_i386.deb ...
Unpacking dbus (1.8.6-1) over (1.8.6-1) ...
Setting up dbus (1.8.6-1) ...
Job for dbus.service canceled.
invoke-rc.d: initscript dbus, action "start" failed.
dpkg: error processing package dbus (--install):
subprocess installed post-installation script returned error exit
status 1 Errors were encountered while processing:
dbus
Now I really see why many people are ranting against systemd; I had
several pkg problems in the past, but I never was completely stucked.
From the point I see it, this shit is gonna push me to reinstall!
Gooood work systemd, you're drawing Linux down almost to the windows
level:(((
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140822173439.6af52b52@msi.defcon1
