[arch-general] Shutdown issue - after updates yesterday
mike.cloaked at gmail.com
Fri Jun 15 12:39:28 EDT 2012
On Fri, Jun 15, 2012 at 5:33 PM, mike cloaked <mike.cloaked at gmail.com> wrote:
> On Fri, Jun 15, 2012 at 4:04 PM, mike cloaked <mike.cloaked at gmail.com> wrote:
>> After updating my systems yesterday I am getting a line with a fail at
>> shutdown at the sigterm/killterm point on the screen after exiting
>> from X.
>> I can't find anything in the logs directly related to this but I do
>> have in /var/log/errors/log:
>> Jun 15 10:58:22 localhost NetworkManager:
>> nm_supplicant_info_set_call: assertion `call != NULL' failed
>> during the bootup time.
>> I know that NetworkManager has had issues in Fedora 16 for a while -
>> eg https://bugzilla.redhat.com/show_bug.cgi?id=826706
>> but I don't know if this is related or not.
>> I am running networkmanager 0.9.4.0-5
> To be more clear during the shutdown at the point where there is
> "Sending SIGTERM signal to processes" it gives "BUSY" at the right
> side which stays some seconds and turns to "FAIL" in red before moving
> on to "Sending SIGKILL to processes" on the next line and then shuts
> down quickly after that. Before updates yesterday this did not happen.
> The pacman log for yesterday's updates is:
> [2012-06-14 18:11] Running 'pacman -Syu'
> [2012-06-14 18:11] synchronizing package lists
> [2012-06-14 18:11] starting full system upgrade
> [2012-06-14 18:11] upgraded jre7-openjdk-headless (7.u4_2.2-1 -> 7.u5_2.2.1-1)
> [2012-06-14 18:12] upgraded jre7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
> [2012-06-14 18:12] upgraded jdk7-openjdk (7.u4_2.2-1 -> 7.u5_2.2.1-1)
> [2012-06-14 18:12] upgraded kdelibs (4.8.4-1 -> 4.8.4-2)
> [2012-06-14 18:12] installed pambase (20120602-1)
> [2012-06-14 18:12] upgraded pam (1.1.5-3 -> 1.1.5-4)
> [2012-06-14 19:08] Running 'pacman -Syu'
> [2012-06-14 19:08] synchronizing package lists
> [2012-06-14 19:08] starting full system upgrade
> [2012-06-14 19:08] upgraded unrar (4.2.3-1 -> 4.2.4-1)
> Only today was the kernel moved to 3.4 with the same issue.
> Anyone else seeing this, or suggest how I might get some debug info?
Hmm - it seems this may be related to an update today:
[2012-06-15 09:42] upgraded networkmanager (0.9.4.0-4 -> 0.9.4.0-5)
Others are posting the same symptoms at:
More information about the arch-general