Bug 218184

Summary:	Problems until restart haldaemon
Product:	[openSUSE] openSUSE 10.2	Reporter:	Marcel Witte <wittemar>
Component:	Other	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	andreas.hanke
Version:	Beta 1 plus
Target Milestone:	---
Hardware:	x86-64
OS:	Linux
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Marcel Witte 2006-11-04 18:12:52 UTC

Hi,

Sometimes after booting I have three problems:

1.) Networkmanager is finding no devices (I have two: eth0 and wlan0)

2.) kpowersave/powersaved isn't working correct. powersave -b is showing:

liblazy (liblazy_dbus_send_method_call:68): Received error reply: The name org.freedesktop.Hal was not provided by any .service files
liblazy (liblazy_hal_get_strlist_manager:109): Error while sending method FindDeviceByCapability to HAL
Could not get battery information.Could not read out battery info properly

3.) the soundcard is only accessable by root. alsamixer as other user is showing:

alsamixer: function snd_ctl_open failed for default: No such device

and aplay is showing:

ALSA lib confmisc.c:670:(snd_func_card_driver) cannot find card '0'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_card_driver returned error: Kein passendes Gerät gefunden
ALSA lib confmisc.c:391:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_concat returned error: Kein passendes Gerät gefunden
ALSA lib confmisc.c:1070:(snd_func_refer) error evaluating name
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer returned error: Kein passendes Gerät gefunden
ALSA lib conf.c:3968:(snd_config_expand) Evaluate error: Kein passendes Gerät gefunden
ALSA lib pcm.c:2143:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:550: audio open error: Kein passendes Gerät gefunden

but both are working as root.


After a lot of try and error I found a way to workaround:
If I restart haldaemon it is all this working, but maybe after next reboot I have to do this again. Which log-files could be useful to troubleshoot??

Greets,
Marcel Witte

Comment 1 Andreas Jaeger 2006-11-04 23:10:42 UTC

Marcel, please describe one bug in one report - and not three at once.

Do I understand you correctly that all three issues work once hal gets restarted?

Comment 2 Andreas Hanke 2006-11-05 07:13:38 UTC

All these symptoms are very typical for a hal crash: hald simply crashed during the boot process (or directory on startup). Restarting it makes it work again, which is logical.

Please do the following:

1. In /etc/init.d/haldaemon, change

HALDAEMON_PARA="--daemon=yes --retain-privileges";

to

HALDAEMON_PARA="--daemon=yes --retain-privileges --verbose=yes
--use-syslog";

2. Reproduce the problem (reboot repeatedly until the symptoms are there), save /var/log/messages and attach it to this bug.

Comment 3 Marcel Witte 2006-11-05 15:02:31 UTC

I took all the three bugs at once because I think they all have to do with one hal-bug. They all are working if I restart hald.

I have added "--verbose=yes --use-syslog" to the HALDAEMON_PARA, but at my system there's no "--retain-privileges" and if I add this I get:

Starting HAL daemon/usr/sbin/hald: unrecognized option '--retain-privileges'
[...]

So I leave it without "--retain-privileges".

Now the "problem" is, what if "--verbose=yes --use-syslog" is set, hald seems to work right without any crash... I tried about 40 reboots and all was working right. But when I remove "--verbose=yes --use-syslog", hald was crashing again most boot-processes... :-(

Is it possible that it's just a "timing-problem"?? So that if "--verbose..." is set, hald is working slower because of writing so much in log, and the point, when he normally would crash is later?? I'm a newbie to hal but this is my idea...

Is there any other possibility to get log from hal??

I hope you have any idea... So "--verbose=yes --use-syslog" would be a "workaround" for now, but he now is flooding my log...

Comment 4 Timo Hoenig 2006-11-06 08:07:57 UTC


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