Bug 115815

Summary:	Installation: HAL/acpid and D-BUS problem after installtion
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Danny Al-Gaaf <dalgaaf>
Component:	Installation	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	aj, dkukawka, jsrain, ms
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	logs from a fresh installed system

Description Danny Al-Gaaf 2005-09-08 10:15:29 UTC

Direct after installation (not rebooted) HAL and DBUS looks like already started 
by YaST while last steps of installation/configuration. The problem is that HAL 
need the acpid, which looks as not started while installation. Without acpid HAL 
know nothing about ac_adapter.

Two possible solutions:
1.) stop hal and dbus after finish YaST (should be started by normal boot way)
2.) start acpid before HAL if YaST/Installation starts HAL.

Comment 1 Lukas Ocilka 2005-09-08 11:33:51 UTC

Please, attach YaST logs and then change the status to ASSIGNED.

Comment 2 Danny Al-Gaaf 2005-09-08 12:40:45 UTC

Created attachment 49197 [details]
logs from a fresh installed system

Comment 3 Danny Al-Gaaf 2005-09-08 12:41:17 UTC

added the requested file.

Comment 4 Lukas Ocilka 2005-09-09 07:10:41 UTC

YaST shouldn't start DBUS or HAL so it must have been started before.

Comment 5 Steffen Winterfeldt 2005-09-09 09:30:23 UTC

yast must ensure hal is running. See bug 114667. 
I'd suggest you go for 2.

Comment 6 Forgotten User ZhJd0F0L3x 2005-09-09 10:04:14 UTC

i'd go for 1 since that ensures that everything is started in the right order.

Comment 7 Jiri Srain 2005-09-09 11:11:09 UTC

Marcus, it is something for YaST's scripts... 
 
I personally think that any soft dependencies between scripts are not problem 
of YaST itself - the scripts of ACPID/HALD should handle it themselfs (eg. 
acpid on start checkes whether HAL is running and if it is, restarts it)

Comment 8 Marcus Schaefer 2005-09-09 11:28:42 UTC

The srcripts starts: 
 
 /usr/sbin/rcdbus start 
 /usr/sbin/rchal start 
 
would it fix the bug if we call 
 
  /usr/sbin/rcdbus start 
  /usr/sbin/rcacpid start 
  /usr/sbin/rchal start 
 
? 
 
Thanks

Comment 9 Timo Hoenig 2005-09-09 11:33:13 UTC

This is sufficient if we make sure that

   rchal start

is triggered _after_

   rcacpid start

has returned.

Comment 10 Marcus Schaefer 2005-09-09 11:50:54 UTC

Is this not the case if call the services as described in #8 ?

Comment 11 Timo Hoenig 2005-09-09 11:53:20 UTC

I guess it is. Just wanted to express that starting rcacpid and rchal parallel might not work out.

Comment 12 Marcus Schaefer 2005-09-09 12:16:24 UTC

ok, thanks I changed the service list as described in #8 
fixed

Comment 13 Marcus Schaefer 2005-09-14 07:35:18 UTC

*** Bug 116753 has been marked as a duplicate of this bug. ***