Your message dated Mon, 29 Nov 2010 18:06:58 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#478099: Bug#478099: 
[network-manager] NetworkManager hangs indefinitely on boot after initializing  
  an ethernet interface while a link beat is detected -   regardless of device 
module
has caused the Debian Bug report #478099,
regarding [network-manager] NetworkManager hangs indefinitely on boot after 
initializing an ethernet interface while a link beat is detected - regardless 
of device module
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
478099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478099
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.6-1
Severity: serious

--- Please enter the report below this line. ---
NetworkManager hangs indefinitely on boot after initializing an ethernet
interface while a link beat is detected - regardless of device module.  The
only solution to fix it is to actually kill the service:
killall -9 NetworkManager && /etc/init.d/NetworkManager start

Sorry for the lack of technical logs, this bug frustrated me to the point by
which I simply purged the packages (network-manager and
network-manager-kde).  Fortunately, this bug is always reproducible for me
across very diverse environments: a desktop using the forcedeth module for
ethernet, a compaq presario 1500 laptop (uses intel modules), and a really
old dell latitude ls series.

To reproduce, set network-manager to run on the runlevel that X would be on
and reboot with an rj45 connection hot to a simple home router (netgear,
linksys, d-link, the usual).

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.24-2.6.24.5.slh.1-sidux-686

Debian Release: lenny/sid
  500 unstable        sidux.net
  500 unstable        ftp.de.debian.org
  500 unstable        ftp-mirror.internap.com
  500 gutsy           download.tuxfamily.org
    1 experimental    ftp.de.debian.org

--- Package information. ---
Depends                   (Version) | Installed
===================================-+-===============
adduser                             | 3.107
dbus                      (>= 0.60) | 1.2.1-1
dhcdbd                  (>= 1.12-2) | 3.0-4
hal                    (>= 0.5.7.1) | 0.5.11~rc2-1
ifupdown                            | 0.6.8
iproute                             | 20080108-1
iputils-arping                      | 3:20071127-1
libc6                    (>= 2.7-1) | 2.7-10
libdbus-1-3              (>= 1.1.1) | 1.2.1-1
libdbus-glib-1-2          (>= 0.74) | 0.74-2
libgcrypt11              (>= 1.4.0) | 1.4.1-1
libglib2.0-0            (>= 2.16.0) | 2.16.3-2
libgpg-error0              (>= 1.4) | 1.4-2
libhal1                (>= 0.5.8.1) | 0.5.11~rc2-1
libiw29              (>= 28+29pre7) | 29-1
libnl1                              | 1.1-2
libnm-util0                         | 0.6.6-1
lsb-base                 (>= 3.0-6) | 3.2-10
wpasupplicant            (>= 0.4.8) | 0.6.3-1

--- End Message ---
--- Begin Message ---
On 28.04.2008 02:07, Michael Biebl wrote:
> severity normal
> thanks
> 
> DamentZ wrote:
>> I found source of the hangs on NetworkManager - apparently if syslog is not
>> running, it'll freeze after trying to enable my eth0 interface.  I rebooted
>> with syslogd enabled to catch a log and to my amazement, knetworkmanager was
>> fully functional and reported that I was connected to a wired network.
> 
> Hm, unfortunately I'm unable to reproduce your problem. I disabled the 
> syslogd and the only thing that changes during boot, is that the output 
> of NetworkManager is sent to stdout instead to a log file, that's all.
> It is still working fine and successfully connects.

I'm going to close this bug report. For one, I was not able to reproduce the
problem when disabling syslog. Also the network-manager init script has the
necessary Should-Start: $syslog entry to at least ensure it is run at the
correct time during boot.

If this is still a problem for you, please reopen the bug report or let me know.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to