Re: Current SVN broken?

2007-02-19 Thread Simon Geard 
On Tue, 2007-02-06 at 17:03 +1300, Simon Geard wrote:
 I've just grabbed the latest NM code from SVN (revision 2287), finding
 it badly broken for me. It builds fine, but crashes shortly after
 startup, apparently just after retrieving scan results from
 wpa_supplicant. 
 
 Anyone else having problems with this? It's a clean snapshot from SVN,
 with none of my code changes in it. I've attached a log, if that
 helps...

Ok, I've given this a couple of weeks for recent changes to settle, but
still finding trunk (rev 2337) completely unstable. It takes about 10
seconds to start up, going through the business of reconnecting to the
system bus before aborting with the stacktrace.

An updated log is attached. Can anyone offer any suggestions as to the
cause? The libhal issues seem an obvious concern, though I've no
problems with HAL on other packages, including NM 0.6.4...

Simon.
lt-NetworkManager: info  starting...
lt-NetworkManager: info  eth0: Device is fully-supported using driver 
'forcedeth'.
lt-NetworkManager: info  Now managing wired Ethernet (802.3) device 'eth0'.
lt-NetworkManager: info  Deactivating device eth0.
lt-NetworkManager: info  ath0: Device is fully-supported using driver 
'ath_pci'.
lt-NetworkManager: info  Now managing wireless (802.11) device 'ath0'.
lt-NetworkManager: info  Deactivating device ath0.
lt-NetworkManager: info  (eth0) supplicant interface is now in state 2 (from 
1).
lt-NetworkManager: info  (ath0) supplicant interface is now in state 2 (from 
1).
lt-NetworkManager: info  disconnected by the system bus.
libhal.c 3031 : Error unsubscribing to signals, error=Connection is closed
lt-NetworkManager: WARN  nm_hal_deinit(): libhal shutdown failed - Connection 
is closed
lt-NetworkManager: dispatch_signal: assertion `sender != NULL' failed
lt-NetworkManager: info  reconnected to the system bus.
lt-NetworkManager: WARN  nm_dbus_manager_init_bus(): DBus Manager already has 
a valid connection.
lt-NetworkManager: info  disconnected by the system bus.

(lt-NetworkManager:26687): GLib-GObject-WARNING **: instance of invalid 
non-instantiatable type `invalid'

(lt-NetworkManager:26687): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: 
assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
lt-NetworkManager: WARN  nm_signal_handler(): Caught signal 11.  Generating 
backtrace...
lt-NetworkManager: *** START **
lt-NetworkManager: Frame 0: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager 
[0x806fb25]
lt-NetworkManager: Frame 1: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager 
[0x806fcae]
lt-NetworkManager: Frame 2: [0xb7f15420]
lt-NetworkManager: Frame 3: /usr/lib/libgobject-2.0.so.0 [0xb7e25ed7]
lt-NetworkManager: Frame 4: /usr/lib/libdbus-glib-1.so.2 [0xb7e96369]
lt-NetworkManager: Frame 5: /usr/lib/libgobject-2.0.so.0(g_object_unref+0xcb) 
[0xb7e2614b]
lt-NetworkManager: Frame 6: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager 
[0x80635a7]
lt-NetworkManager: Frame 7: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager 
[0x8063bd5]
lt-NetworkManager: Frame 8: /usr/lib/libglib-2.0.so.0 [0xb7db4e56]
lt-NetworkManager: Frame 9: 
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb7db4881]
lt-NetworkManager: Frame 10: /usr/lib/libglib-2.0.so.0 [0xb7db785f]
lt-NetworkManager: Frame 11: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1a7) 
[0xb7db7c07]
lt-NetworkManager: Frame 12: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager(main+0xa52)
 [0x806c312]
lt-NetworkManager: Frame 13: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7c057cc]
lt-NetworkManager: Frame 14: 
/home/delgarde/Development/NetworkManager/src/.libs/lt-NetworkManager 
[0x8055171]
lt-NetworkManager: *** END **


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

RE: My wireless card activity could not be recognized by NetworkManager

2007-02-19 Thread Joan Moreau 
I had the same problem with whatever wireless card I got. The solution was to 
empty /etc/network/interfaces and put only the local dummy interface but not 
ethX nor wlanX

-Original Message-
From: Jihua Cheng [EMAIL PROTECTED]
To: Paul Betts [EMAIL PROTECTED]
Cc: networkmanager-list@gnome.org
Sent: 16.02.07 04:37
Subject: RE: My wireless card activity could not be recognized by   
NetworkManager

Hi,

Thanks so much!

My wireless card is a PCI card. I use the lspci and I can find my PCI
interface. When I use the lshal -l, I find my device too.

I am wondering if 
1) some setting is need for Network Manager, for the wireless interface.
2) my wireless card driver does not response some Wireless Extension
ioctl() correctly.

Could you give me more hints?

Charles

 
-Original Message-
From: Paul Betts [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 15, 2007 12:13 PM
To: Jihua Cheng
Cc: networkmanager-list@gnome.org
Subject: Re: My wireless card activity could not be recognized by
NetworkManager

On Thu, 2007-02-15 at 12:00 -0800, Jihua Cheng wrote:
 However, my NetworkManager could not detect my wireless card activity,
 no matter my wireless interface is up or down. My network manager
 detects my wired Ethernet card correctly.

Perhaps you can post your wireless card brand and the relevant section
of of lshal -l (ie the section with your wireless card in it)?

-- 
Paul Betts [EMAIL PROTECTED]



Original question

Hi, 

I am new for Network manager. I install wireless card and driver on my
Fedora Core 6 desktop. I can associate to AP and ping PA. I also can
check my wireless card activity via network tools and Network
Configuration.

However, my NetworkManager could not detect my wireless card activity,
no matter my wireless interface is up or down. My network manager
detects my wired Ethernet card correctly.

Could any Guru help to indicate where the problem is?

Thanks!

Charles

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Current SVN broken?

2007-02-19 Thread Tambet Ingo 
On Mon, 2007-02-19 at 21:03 +1300, Simon Geard wrote:
 Ok, I've given this a couple of weeks for recent changes to settle, but
 still finding trunk (rev 2337) completely unstable. It takes about 10
 seconds to start up, going through the business of reconnecting to the
 system bus before aborting with the stacktrace.

Don't use the SVN head. We know it's completely unstable. We'll let you
know when it's usable again.

Tambet

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Re: Current SVN broken?

2007-02-19 Thread Simon Geard 
On Mon, 2007-02-19 at 14:54 +0200, Tambet Ingo wrote:
 On Mon, 2007-02-19 at 21:03 +1300, Simon Geard wrote:
  Ok, I've given this a couple of weeks for recent changes to settle, but
  still finding trunk (rev 2337) completely unstable. It takes about 10
  seconds to start up, going through the business of reconnecting to the
  system bus before aborting with the stacktrace.
 
 Don't use the SVN head. We know it's completely unstable. We'll let you
 know when it's usable again.

Ok, I'll do that. Do you have any rough idea how long that might take -
I don't mean dates, just whether it's days, weeks, or at worst, months.

Simon.


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list