After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 482828 - crash in Network Manager: Connected to a wireless ...
crash in Network Manager: Connected to a wireless ...
Status: RESOLVED DUPLICATE of bug 444319
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-10-03 04:41 UTC by Ingvar Hagelund
Modified: 2007-10-06 17:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Ingvar Hagelund 2007-10-03 04:41:07 UTC 
What were you doing when the application crashed?
Connected to a wireless network


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:59:51 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 274882560 vsize: 274882560 resident: 22687744 share: 20271104 rss: 22687744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191386426 rtime: 15 utime: 12 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nm-applet'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496363728 (LWP 3126)]
(no debugging symbols found)
0x000000325860d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 167310

Thread 1 (Thread 46912496363728 (LWP 3126))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_free
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_free
    from /lib64/libdbus-1.so.3
  • #6 g_free
    from /lib64/libdbus-1.so.3
  • #7 dbus_message_new_method_call
    from /lib64/libdbus-1.so.3
  • #8 nma_dbus_device_update_one_network
  • #9 ??
  • #10 g_free
    from /lib64/libdbus-1.so.3
  • #11 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #12 g_free
    from /usr/lib64/libdbus-glib-1.so.2
  • #13 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #14 g_free
    from /lib64/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
localuser:ingvar being added to access control list
SESSION_MANAGER=local/svelvik:/tmp/.ICE-unix/2978
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
error getting update info:  Cannot retrieve repository metadata (repomd.xml) for repository: xgl. Please verify its path and try again
** (nm-applet:3126): WARNING **: <WARN>  nma_dbus_net_properties_cb(): dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
process 3126: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
--------------------------------------------------
Comment 1 Ingvar Hagelund 2007-10-03 09:01:08 UTC 
Think I found the reason for this. I have a third party softmodem package installed, conexant hsfmodem, see  http://www.linuxant.com/drivers/hsf/full/downloads.php. Disabling this at startup makes nm stable again. This goes for bug #482827 too.

As the hsfmodem driver taints the kernel, I'm not sure if the nm developers want to support it's functionality. It works as a "normal" modem through the symlinked /dev/modem, though.

Ingvar
Comment 2 Susana 2007-10-06 17:26:03 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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