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 494510 - crash in Network Manager: launching vmware, runnin...
crash in Network Manager: launching vmware, runnin...
Status: RESOLVED DUPLICATE of bug 436553
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-11-07 09:25 UTC by zeugma
Modified: 2007-11-15 22:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description zeugma 2007-11-07 09:25:15 UTC
What were you doing when the application crashed?
launching vmware, running windows vm.


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 117796864 vsize: 117796864 resident: 44376064 share: 42192896 rss: 44376064 rss_rlim: 4294967295
CPU usage: start_time: 1194427070 rtime: 22 utime: 16 stime: 6 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209047328 (LWP 3500)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209047328 (LWP 3500))

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


----------- .xsession-errors (11 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(gnome-panel:3478): Gtk-CRITICAL **: gtk_icon_theme_lookup_icon: assertion `GTK_IS_ICON_THEME (icon_theme)' failed
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
** (nm-applet:3500): 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 3500: 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 Dan Williams 2007-11-15 22:49:12 UTC

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