View Single Post
Old 2013-03-20, 13:39   #9
Graff
 
Graff's Avatar
 
Jul 2006
USA (UT-5) via UK (UT)

EC16 Posts
Default

Quote:
Originally Posted by Dubslow View Post
I guess it wasn't the kernel then (which it was never really likely to be).

What other packages did that update mess with?
From the /var/log/apt/history.log file (split one per line for easier
reading):

Code:
Start-Date: 2013-03-19  18:36:43
Install: 
linux-headers-3.2.0-39-generic:amd64 (3.2.0-39.62), 
linux-headers-3.2.0-39:amd64 (3.2.0-39.62), 
linux-image-3.2.0-39-generic:amd64 (3.2.0-39.62)
Upgrade: 
libsmbclient:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4), 
smbclient:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4), 
libevince3-3:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6), 
linux-generic:amd64 (3.2.0.38.46, 3.2.0.39.47), 
libwbclient0:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4), 
samba-common:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4), 
evince-common:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6), 
linux-headers-generic:amd64 (3.2.0.38.46, 3.2.0.39.47), 
linux-image-generic:amd64 (3.2.0.38.46, 3.2.0.39.47), 
evince:amd64 (3.4.0-0ubuntu1.5, 3.4.0-0ubuntu1.6), 
linux-libc-dev:amd64 (3.2.0-38.61, 3.2.0-39.62), 
samba-common-bin:amd64 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4)
Both machines were running this morning.

Gareth
Graff is offline   Reply With Quote