FS#30305 - After update to networkmanager 0.9.4.0-5 shutdown FAILs at sending SIGTERM to processes

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 17:09 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 15 June 2012, 19:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Using networkmanager 0.9.4.0-5 and after being logged in to KDE, then initiate shutdown.

On the console after X exits at the point where there the line

"Sending SIGTERM signal to processes"

is listed on the screen, 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.


Additional info:

networkmanager 0.9.4.0-5

This did not happen with networkmanager 0.9.4.0-4

I don't know if this is related but I have in /var/log/errors/log:

Jun 15 10:58:22 localhost NetworkManager[1441]:
nm_supplicant_info_set_call: assertion `call != NULL' failed

during the bootup time.

Steps to reproduce:Boot machine, and login to KDE - right click on screen and select "Leave" to initiate shutdown.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 15 June 2012, 19:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  networkmanager 0.9.4.0-6
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 17:31 GMT
I am also seeing this in the errors log:


Jun 15 17:25:17 localhost NetworkManager[397]: <error> [1339777517.736521] [nm-dbus-manager.c:278] nm_dbus_manager_init_bus(): Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: <error> [1339777518.17742] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directory
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_connection_register_g_object: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_proxy_begin_call_with_timeout: assertion `DBUS_IS_G_PROXY (proxy)' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
Jun 15 17:25:18 localhost NetworkManager[397]: <error> [1339777518.73068] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (1) Error initializing authority: Could not connect: No such file or directory

I don't know if this is connected with the shutdown problem?
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 17:33 GMT
Interestingly I just tried to restart networkmanager with this result:

[root@lapmike3 log]# rc.d restart networkmanager
:: Stopping NetworkManager [DONE]
:: Starting NetworkManager [FAIL]

Strange!

dbus is running fine at this point.
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 17:36 GMT
After attempting to restart networkmanager I get in messages.log:

Jun 15 18:33:08 localhost NetworkManager[519]: <warn> disconnected by the system bus.
Jun 15 18:33:12 localhost NetworkManager[519]: <info> reconnected to the system bus.
Jun 15 18:33:12 localhost NetworkManager[519]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 17:36 GMT
However I still have a wifi connection despite the notification that networkmanager has not restarted - very odd.
Comment by Tushar R (fatboy) - Friday, 15 June 2012, 17:40 GMT
mcloaked, is 'dbus' listed before 'networkmanager' in your rc.conf DAEMONS array?
Comment by Tushar R (fatboy) - Friday, 15 June 2012, 17:43 GMT
I am also having my sending SIGTERM step fail due to NM; verified by downgrading networkmanager (0.9.4.0-5 -> 0.9.4.0-4)

But I do not get the other dbus errors.
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 18:13 GMT
yes dbus was before nm - I've moved it and will retest
Comment by Mike Cloaked (mcloaked) - Friday, 15 June 2012, 18:20 GMT
With dbus after nm then once booted and logged in to KDE then networking is no longer working and the network icon is red! I put it back to where it was!
Comment by Tushar R (fatboy) - Friday, 15 June 2012, 18:20 GMT
Oh, please disregard that. I meant to ask whether it is after - because the correct order is dbus then nm. Thanks

Loading...