HAL / NetworkManager / nm-applet

[John (J5) Palmieri]

Looks like you are up to date.  I can't reproduce the bug here.  What
you might want to do is edit the /etc/init.d/haldaemon file and add
--use-syslog and --verbose=yes to the daemon line in the start()
procedure.  Reboot and then open a bug and attach the relevent portions
of /var/log/messages.

On Fri, 2006-01-13 at 17:23 -0500, Brian C. Huffman wrote:
> Sorry for the lack of threading - I was in digest mode, so I had to
> recreate your email.  
> 
> Also sorry for the top-posting.  Here's the output of my selinux:
> 
> [bhuffman at xyz ~]$ rpm -qa |grep selinux-policy-targeted
> selinux-policy-targeted-2.1.9-2
> 
> If it makes a difference, this is a full yum upgrade from FC4.
> Everything else seems to be working..
> 
> Thanks,
> Brian
> 
> ________________________________________________________________________
> What version of se-linux are you running (rpm -q
> selinux-policy-targeted)?  There was a bug where if HAL could not
> execute its scripts because of an se-linux rule HAL would crash and
> NetworkManager would not start up.
> 
> On Fri, 2006-01-13 at 16:53 -0500, Brian C. Huffman wrote:
> > All,
> > 
> > I'm having a problem where both hald and NetworkManager die when my
> > session starts (and therefore nm-applet starts).  If I kill the
> > remaining hal processes (hald-addon-acpi and hald-addon-storage) and
> > then restart hald and NetworkManager
> > 
> > /etc/init.d/haldaemon start
> > /etc/init.d/NetworkManager start
> > 
> > Then everything works fine and my (still running) nm-applet comes up in
> > the notification panel.  Any ideas?
> > 
> > Thanks,
> > Brian
> 
> -- 
> John (J5) Palmieri <johnp redhat com>
> 

-- 
John (J5) Palmieri <johnp at redhat.com>