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 398227 - crash in Networking:
crash in Networking:
Status: RESOLVED DUPLICATE of bug 354536
Product: gnome-system-tools
Classification: Deprecated
Component: network-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2007-01-19 02:14 UTC by neiltaggart
Modified: 2007-01-19 12:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description neiltaggart 2007-01-19 02:14:01 UTC
Version: 2.15.5

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 52477952 vsize: 0 resident: 52477952 share: 0 rss: 11931648 rss_rlim: 0
CPU usage: start_time: 1169172807 rtime: 0 utime: 93 stime: 0 cutime:87 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/network-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226025296 (LWP 32251)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226025296 (LWP 32251))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_slice_free_chain_with_offset
    from /usr/lib/libglib-2.0.so.0
  • #5 g_list_free
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 gtk_combo_box_set_active_iter
  • #9 ??
  • #0 __kernel_vsyscall

Comment 1 Susana 2007-01-19 12:42:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This issue has already been fixed. Please update. Thanks.

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