Bug 463468

Summary:	shutdown hangup
Product:	[openSUSE] openSUSE 11.1	Reporter:	kendall green <kendall.green>
Component:	Network	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	volker.barth
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description kendall green 2009-01-04 21:33:00 UTC

Shutdown hangs up with the following message everytime:

bridge-utils not installed
doneShutting down service (localfs) network  .  .  .  .  .  .  .  .  .done
Shutting down D-Bus daemon<notice>killproc: kill(1880,15)
nm-system-settings: disconnected from the system bus, exiting.

nm-system-settings: nm_sysconfig_settings_remove_connection: assertion `NM_IS_SYSCONFIG_SETTINGS (self)' failed

Does not continue on the shutdown sequence or power on.  I have openSUSE 11.0 and previously 10.3 working on this Compaq Athlon 3200 without problem.

Comment 1 Volker Barth 2009-01-21 10:07:52 UTC

Same happens here. A 32 bit machine did shut down cleanly under 10.2. Now it sometimes does shut down, sometimes it hangs in shutdown process.

Last message in the latter case on console 1 is:

Running /etc/init.d/halt.local   done
nm-system-settings: nm_sysconfig_settings_remove_connection: assertion `NM_IS_SYSCONFIG_SETTINGS (self)' failed

last line is repeated several times; halt.local is empty, btw. Network setup uses traditional ifup/ifdown. The home is mounted via NFS, but last user was logged out 45 min before (a script starts an automatic shutdown process after 45 min of inactivity). On console 10 I get the following messages:

nfs: server ... not responding, still trying
console-kit-dae[..]: segfault ... in libglib-2.0.so.0.1800.2

This happens only with this one machine. Mine and others (all 64 bit) do not show this behavior. They shut down cleanly every time.

Comment 2 Cyril Hrubis 2009-03-02 15:38:53 UTC

Most likely duplicate.

*** This bug has been marked as a duplicate of bug 480355 ***