Bug#775065: dpkg --configure -a results in "Hangup" after first package

Michael Biebl biebl at debian.org
Sun Jan 11 20:02:39 GMT 2015


Am 11.01.2015 um 20:54 schrieb Chris Carr:
> On 11/01/2015 19:25, Michael Biebl wrote:
>> Is your system fully booted or did systemd drop you into emergency
>> shell? How are you logged into your system?
> The default boot drops me into an emergency shell. It was not fully booted.

Now that the system is fully upgraded, does systemd still fail to boot
and drop you into emergency mode?
In that case, please add systemd.log_level=debug to the kernel command
line and attach the output of "journalctl -alb"

>> Assuming, the sysvinit is still installed (which should be the case on
>> upgrades), please select the sysvinit option from the grub extended menu.
>> If it's not available, boot with init=/lib/sysvinit/init
>>
>> Does that change anything?
> Yes! Thank you, thank you.

Ok, so this sounds like this is specific to systemd emergency mode.
Assuming systemd boots properly for you now, it would be interesting to
know, if dpkg now works properly as well when booted into a regular mode.

> Selecting the (sysvinit) option from the grub extended menu results in a
> full boot: gdm3 doesn't start but I do get a login prompt. After logging
> in, sudo dpkg --configure -a actually worked. This meant that I could
> complete a sudo apt-get dist-upgrade.
> 
> All packages are now fully configured except gkrellmd (which I removed
> to ensure everything is clean).
> 
> I still cannot start gdm3:
> 
> chrisc at tony:~$ sudo invoke-rc.d gdm3 start
> [....] Starting GNOME Display Manager: gdm3[ 1094.663256]
> systemd-logind[9907]: Failed to enable subscription: Launch helper
> exited with unknown return code 1
> [ 1094.669994] systemd-logind[9907]: Failed to fully start up daemon:
> Input/output error
> Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
> with unknown return code 1
>  failed!

That somehow sounds like something with your dbus installation is broken.
What is the output of
$ ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper

> invoke-rc.d: initscript gdm3, action "start" failed.
> chrisc at tony:~$
> 
> There seem to be two problems there: one is gdm3 not starting, and the
> other is logind complaining about not being fully started.

Is the dbus package installed? What's the output of "systemctl status
dbus.socket dbus.service"?
You might consider attaching the full output of the systemd state via
"systemd-analyze dump"

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150111/bfea9799/attachment-0005.sig>


More information about the Pkg-systemd-maintainers mailing list