CrunchBang Linux

rigid_designator

New Member

Registered: 2013-02-20

Posts: 8

[SOLVED] Can't log-in after apt upgrade

Hi all. I've been a very happy user of Waldorf until I broke it last night. In an ill-advised move, I pressed the "Mark All Upgrades" button in Synaptic on a whim. Now, something's broken and I can't log in.

Here's the last entry in /var/log/apt/history.log:

Start-Date: 2013-02-19  20:07:26
Commandline: synaptic
Upgrade: libswscale2:amd64 (1.0.3-dmo1, 1.0.4-dmo1), dnsmasq-base:amd64 (2.62-3, 2.62-3+deb7u1), libc-bin:amd64 (2.13-37, 2.13-38), gir1.2-gstreamer-0.10:amd64 (0.10.36-1, 0.10.36-1.1), libavutil51:amd64 (1.0.3-dmo1, 1.0.4-dmo1), bind9-host:amd64 (9.8.4.dfsg.P1-4, 9.8.4.dfsg.P1-5), gvfs-fuse:amd64 (1.12.3-3, 

Yes, it's just cut-off like that. (I checked, though, and it looks like gvfs-fuse=1.12.3-4 is currently installed.) Synaptic downloaded and began installing the packages, but then froze on "Configuring Network Manager..." I was watching TV, so I just chilled and let it do it's thing, but nothing happened after a while, so I got frustrated and rebooted it.

Now during boot I get a bunch of floating point exceptions, and a particularly cheerful "Unknown kernel (only linux and FreeBSD are supported)". When I try to log in, the screen flashes a terminal message (it's too fast to read), and returns me to slim's username prompt. I can boot into recovery mode, but I'm not sure what to do from there. I do know that I don't have networking (at least not wi-fi) in recovery. I perused some of the logs in var/log, but I don't know what, if anything, would be relevant or give a clue what went wrong besides the apt log above. I can post anything if you tell me too.

Anyone experience this? Any tips on where to go from here? I'd like to avoid reinstalling, and try to fix it and learn something in the process.

Last edited by rigid_designator (2013-02-21 17:44:53)

rkwurth

#! Junkie

Registered: 2012-09-04

Posts: 365

Re: [SOLVED] Can't log-in after apt upgrade

cat /var/log/dpkg.log
Will show you more.

P.S.  maybe you should chroot into your machine and update-grub.

Last edited by rkwurth (2013-02-20 22:19:54)

rigid_designator

New Member

Registered: 2013-02-20

Posts: 8

Re: [SOLVED] Can't log-in after apt upgrade

Hmm, ok so here's the entries from dpkg.log, starting from 20:07:26 when I clicked the "Apply" button in Synaptic. (I added line breaks in what I thought were logical places to help me read through it):

2013-02-19 20:07:26 startup archives unpack

2013-02-19 20:07:29 upgrade perl:amd64 5.14.2-17 5.14.2-18
2013-02-19 20:07:29 status half-configured perl:amd64 5.14.2-17
2013-02-19 20:07:29 status unpacked perl:amd64 5.14.2-17
2013-02-19 20:07:29 status half-installed perl:amd64 5.14.2-17
2013-02-19 20:07:29 status triggers-pending man-db:amd64 2.6.2-1
2013-02-19 20:07:29 status half-installed perl:amd64 5.14.2-17
2013-02-19 20:07:30 status half-installed perl:amd64 5.14.2-17
2013-02-19 20:07:30 status unpacked perl:amd64 5.14.2-18
2013-02-19 20:07:30 status unpacked perl:amd64 5.14.2-18

2013-02-19 20:07:30 upgrade libperl5.14:amd64 5.14.2-17 5.14.2-18
2013-02-19 20:07:30 status half-configured libperl5.14:amd64 5.14.2-17
2013-02-19 20:07:30 status unpacked libperl5.14:amd64 5.14.2-17
2013-02-19 20:07:31 status half-installed libperl5.14:amd64 5.14.2-17
2013-02-19 20:07:31 status half-installed libperl5.14:amd64 5.14.2-17
2013-02-19 20:07:31 status unpacked libperl5.14:amd64 5.14.2-18
2013-02-19 20:07:31 status unpacked libperl5.14:amd64 5.14.2-18

2013-02-19 20:07:31 upgrade perl-base:amd64 5.14.2-17 5.14.2-18
2013-02-19 20:07:31 status half-configured perl-base:amd64 5.14.2-17
2013-02-19 20:07:31 status unpacked perl-base:amd64 5.14.2-17
2013-02-19 20:07:31 status half-installed perl-base:amd64 5.14.2-17
2013-02-19 20:07:32 status half-installed perl-base:amd64 5.14.2-17
2013-02-19 20:07:32 status half-installed perl-base:amd64 5.14.2-17
2013-02-19 20:07:32 status unpacked perl-base:amd64 5.14.2-18
2013-02-19 20:07:32 status unpacked perl-base:amd64 5.14.2-18

2013-02-19 20:07:33 trigproc man-db:amd64 2.6.2-1 2.6.2-1
2013-02-19 20:07:33 status half-configured man-db:amd64 2.6.2-1
2013-02-19 20:07:35 status installed man-db:amd64 2.6.2-1

2013-02-19 20:07:35 startup packages configure

2013-02-19 20:07:35 configure perl-base:amd64 5.14.2-18 <none>
2013-02-19 20:07:35 status unpacked perl-base:amd64 5.14.2-18
2013-02-19 20:07:36 status half-configured perl-base:amd64 5.14.2-18
2013-02-19 20:07:36 status installed perl-base:amd64 5.14.2-18

2013-02-19 20:07:36 startup archives unpack

2013-02-19 20:07:37 upgrade perl-modules:all 5.14.2-17 5.14.2-18
2013-02-19 20:07:37 status half-configured perl-modules:all 5.14.2-17
2013-02-19 20:07:37 status unpacked perl-modules:all 5.14.2-17
2013-02-19 20:07:37 status half-installed perl-modules:all 5.14.2-17
2013-02-19 20:07:38 status half-installed perl-modules:all 5.14.2-17
2013-02-19 20:07:38 status unpacked perl-modules:all 5.14.2-18
2013-02-19 20:07:38 status unpacked perl-modules:all 5.14.2-18

2013-02-19 20:07:38 upgrade libc-bin:amd64 2.13-37 2.13-38
2013-02-19 20:07:38 status half-configured libc-bin:amd64 2.13-37
2013-02-19 20:07:38 status unpacked libc-bin:amd64 2.13-37
2013-02-19 20:07:39 status half-installed libc-bin:amd64 2.13-37
2013-02-19 20:07:39 status triggers-pending man-db:amd64 2.6.2-1
2013-02-19 20:07:39 status half-installed libc-bin:amd64 2.13-37
2013-02-19 20:07:39 status half-installed libc-bin:amd64 2.13-37
2013-02-19 20:07:39 status unpacked libc-bin:amd64 2.13-38
2013-02-19 20:07:39 status unpacked libc-bin:amd64 2.13-38

2013-02-19 20:07:39 trigproc man-db:amd64 2.6.2-1 2.6.2-1

2013-02-19 20:01:24 startup packages configure

2013-02-19 20:01:24 configure gdb:amd64 7.4.1+dfsg-0.1 <none>
2013-02-19 20:01:24 status unpacked gdb:amd64 7.4.1+dfsg-0.1
2013-02-19 20:01:24 status unpacked gdb:amd64 7.4.1+dfsg-0.1
2013-02-19 20:01:24 status half-configured gdb:amd64 7.4.1+dfsg-0.1
2013-02-19 20:01:25 status installed gdb:amd64 7.4.1+dfsg-0.1
2013-02-19 20:01:25 status triggers-pending menu:amd64 2.1.46
2013-02-19 20:01:25 status triggers-awaited menu:amd64 2.1.46

2013-02-19 20:01:25 configure network-manager:amd64 0.9.4.0-10 <none>
2013-02-19 20:01:25 status half-configured network-manager:amd64 0.9.4.0-10
2013-02-19 20:01:27 status installed network-manager:amd64 0.9.4.0-10

2013-02-19 20:01:27 configure libisccc80:amd64 1:9.8.4.dfsg.P1-5 <none>
2013-02-19 20:01:27 status unpacked libisccc80:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:27 status half-configured libisccc80:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:28 status installed libisccc80:amd64 1:9.8.4.dfsg.P1-5

2013-02-19 20:01:28 configure openssh-client:amd64 1:6.0p1-4 <none>
2013-02-19 20:01:28 status unpacked openssh-client:amd64 1:6.0p1-4
2013-02-19 20:01:28 status unpacked openssh-client:amd64 1:6.0p1-4
2013-02-19 20:01:29 status unpacked openssh-client:amd64 1:6.0p1-4
2013-02-19 20:01:29 status half-configured openssh-client:amd64 1:6.0p1-4
2013-02-19 20:01:31 status installed openssh-client:amd64 1:6.0p1-4

2013-02-19 20:01:31 configure libnm-glib-vpn1:amd64 0.9.4.0-10 <none>
2013-02-19 20:01:31 status unpacked libnm-glib-vpn1:amd64 0.9.4.0-10
2013-02-19 20:01:31 status half-configured libnm-glib-vpn1:amd64 0.9.4.0-10
2013-02-19 20:01:31 status installed libnm-glib-vpn1:amd64 0.9.4.0-10

2013-02-19 20:01:31 configure icedtea-netx-common:all 1.3.1-2.1 <none>
2013-02-19 20:01:31 status unpacked icedtea-netx-common:all 1.3.1-2.1
2013-02-19 20:01:31 status unpacked icedtea-netx-common:all 1.3.1-2.1
2013-02-19 20:01:31 status half-configured icedtea-netx-common:all 1.3.1-2.1
2013-02-19 20:01:31 status installed icedtea-netx-common:all 1.3.1-2.1

2013-02-19 20:01:31 configure gir1.2-gtk-3.0:amd64 3.4.2-6 <none>
2013-02-19 20:01:32 status unpacked gir1.2-gtk-3.0:amd64 3.4.2-6
2013-02-19 20:01:32 status half-configured gir1.2-gtk-3.0:amd64 3.4.2-6
2013-02-19 20:01:32 status installed gir1.2-gtk-3.0:amd64 3.4.2-6

2013-02-19 20:01:32 configure libdns88:amd64 1:9.8.4.dfsg.P1-5 <none>
2013-02-19 20:01:32 status unpacked libdns88:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:32 status half-configured libdns88:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:32 status installed libdns88:amd64 1:9.8.4.dfsg.P1-5

2013-02-19 20:01:32 configure icedtea-netx:amd64 1.3.1-2.1 <none>
2013-02-19 20:01:32 status unpacked icedtea-netx:amd64 1.3.1-2.1
2013-02-19 20:01:32 status half-configured icedtea-netx:amd64 1.3.1-2.1
2013-02-19 20:01:32 status installed icedtea-netx:amd64 1.3.1-2.1
2013-02-19 20:01:32 configure libisccfg82:amd64 1:9.8.4.dfsg.P1-5 <none>
2013-02-19 20:01:32 status unpacked libisccfg82:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:32 status half-configured libisccfg82:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:32 status installed libisccfg82:amd64 1:9.8.4.dfsg.P1-5

2013-02-19 20:01:32 configure libnm-gtk0:amd64 0.9.4.1-5 <none>
2013-02-19 20:01:32 status unpacked libnm-gtk0:amd64 0.9.4.1-5
2013-02-19 20:01:33 status half-configured libnm-gtk0:amd64 0.9.4.1-5
2013-02-19 20:01:33 status installed libnm-gtk0:amd64 0.9.4.1-5

2013-02-19 20:01:33 configure network-manager-gnome:amd64 0.9.4.1-5 <none>
2013-02-19 20:01:33 status unpacked network-manager-gnome:amd64 0.9.4.1-5
2013-02-19 20:01:33 status unpacked network-manager-gnome:amd64 0.9.4.1-5
2013-02-19 20:01:33 status half-configured network-manager-gnome:amd64 0.9.4.1-5
2013-02-19 20:01:33 status installed network-manager-gnome:amd64 0.9.4.1-5

2013-02-19 20:01:33 configure libbind9-80:amd64 1:9.8.4.dfsg.P1-5 <none>
2013-02-19 20:01:33 status unpacked libbind9-80:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:33 status half-configured libbind9-80:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:33 status installed libbind9-80:amd64 1:9.8.4.dfsg.P1-5

2013-02-19 20:01:33 configure bind9-host:amd64 1:9.8.4.dfsg.P1-5 <none>
2013-02-19 20:01:33 status unpacked bind9-host:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:33 status half-configured bind9-host:amd64 1:9.8.4.dfsg.P1-5
2013-02-19 20:01:33 status installed bind9-host:amd64 1:9.8.4.dfsg.P1-5

2013-02-19 20:01:34 configure perl-modules:all 5.14.2-18 <none>
2013-02-19 20:01:34 status unpacked perl-modules:all 5.14.2-18
2013-02-19 20:01:34 status unpacked perl-modules:all 5.14.2-18
2013-02-19 20:01:34 status half-configured perl-modules:all 5.14.2-18
2013-02-19 20:01:34 status installed perl-modules:all 5.14.2-18

2013-02-19 20:01:34 configure perl:amd64 5.14.2-18 <none>
2013-02-19 20:01:34 status unpacked perl:amd64 5.14.2-18
2013-02-19 20:01:34 status half-configured perl:amd64 5.14.2-18
2013-02-19 20:01:35 status installed perl:amd64 5.14.2-18

2013-02-19 20:01:35 trigproc menu:amd64 2.1.46 <none>
2013-02-19 20:01:35 status half-configured menu:amd64 2.1.46
2013-02-19 20:01:36 status installed menu:amd64 2.1.46

The log file ends there. I'm REALLY confused as to why entries time-stamped 20:01:** come after 20:07:**. Also, only one package listed in the apt/history.log is listed here (libc-bin). Are all these other packages dependencies of the seven packages Synaptic chose to update? And why is libswscale2, dnsmasq-base, gir1.2-gstreamer-0.10, libavutil5, bind9-host and gvfs-fuse nowhere to be found? I also see that three packages were only "half-installed". Is that normal, or a bad thing?

I'm thinking that I'll just try to use apt to revert those seven packages back to the previous versions I was using and see what happens. I'll have to get a network connection working in recovery mode to do that, though.

maybe you should chroot into your machine and update-grub.

Can you expand on this? I looked it up and it appears that update-grub (re)generates a config file for grub. Why might I need to do this? And do you mean chroot from a live cd? I'm sorry I don't understand completely. I'm trying to research it now.

Thanks very much for your reply.

rkwurth

#! Junkie

Registered: 2012-09-04

Posts: 365

Re: [SOLVED] Can't log-in after apt upgrade

Reg chrooting to update grub- I think I misread your post- I see you can boot the machine with error messages, but can't get past slim.

rigid_designator

New Member

Registered: 2013-02-20

Posts: 8

Re: [SOLVED] Can't log-in after apt upgrade

Ah, that's what I figured, but I wasn't sure.

Vegetarian Spelling Unit

#! Member

Registered: 2011-08-27

Posts: 85

Re: [SOLVED] Can't log-in after apt upgrade

Sounds like you hosed your system good. This is why I avoid synaptic and just stick with the command line tools. Have you thought about just doing a clean reinstall?

xaos52

The Good Doctor

From: Planet of the @s

Registered: 2011-06-24

Posts: 4,602

Re: [SOLVED] Can't log-in after apt upgrade

Log into a Virtual Console (Ctrl+Alt+F2) and run

sudo apt-get install -f

---

bootinfoscript - emacs primer - wireless problems- I ♥ #!

rigid_designator

New Member

Registered: 2013-02-20

Posts: 8

Re: [SOLVED] Can't log-in after apt upgrade

I finally figured out the terminal message displayed when I tried logging in was "INIT: Id '1' respawning too fast. Disabled for 5 minutes". Did lots of research, but didn't find anything particularly useful.

Log into a Virtual Console (Ctrl+Alt+F2) and run
<code>sudo apt-get install -f</code>

This is good advice. I tried it early on, however, and apt didn't do anything.

Sounds like you hosed your system good. This is why I avoid synaptic and just stick with the command line tools. Have you thought about just doing a clean reinstall?

I'm pretty sure Synaptic is just a front end for apt commands, so...

I ended up just doing a reinstall. I think apt wanted a network connection and I couldn't get wlan0 to associate with an access point in recovery mode, nor did I have have access to a wired connection.

After re-installation, the post-install script wanted to do a apt update, so I decided to let it, and whaddya know: same problem. Apt hung on configuring the network manager. So after waiting a bit, I rebooted it, crossed my fingers and... no errors!

So this time I took xaos52's advice, switched to tty2 and told apt to fix broken packages there, which in turn told me to run dpkg --configure -a, and that fixed everything.

So, maybe the lesson learned here is to not apply system updates willy-nilly, and maybe to avoid doing it in an x environment. Still wish I knew what happened.

rigid_designator

New Member

Registered: 2013-02-20

Posts: 8

Re: [SOLVED] Can't log-in after apt upgrade

Also, thank you for your replies everyone. I appreciate the help.