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 372697 - crash in Networking: I clicked the Configure ...
crash in Networking: I clicked the Configure ...
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: 2006-11-08 22:05 UTC by John
Modified: 2006-11-17 03:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description John 2006-11-08 22:05:14 UTC
Version: 2.15.5

What were you doing when the application crashed?
I clicked the Configure button on the applet.


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

Memory status: size: 33374208 vsize: 0 resident: 33374208 share: 0 rss: 11284480 rss_rlim: 0
CPU usage: start_time: 1163002790 rtime: 0 utime: 28 stime: 0 cutime:26 cstime: 0 timeout: 2 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 -1225607504 (LWP 19548)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225607504 (LWP 19548))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 IA__g_slice_free_chain_with_offset
    at gslice.c line 858
  • #5 IA__g_list_free
    at glist.c line 53
  • #6 ??
  • #7 ??
  • #8 gtk_combo_box_set_active_iter
  • #9 ??
  • #0 __kernel_vsyscall

Comment 1 Carlos Garnacho 2006-11-16 13:10:17 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 John 2006-11-16 17:00:10 UTC
Memory status: size: 33402880 vsize: 0 resident: 33402880 share: 0 rss: 11288576 rss_rlim: 0
CPU usage: start_time: 1163696161 rtime: 0 utime: 34 stime: 0 cutime:32 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

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

Thread 1 (Thread -1225156944 (LWP 9193))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 IA__g_slice_free_chain_with_offset
    at gslice.c line 858
  • #5 IA__g_list_free
    at glist.c line 53
  • #6 gst_network_locations_get_current
    at network-locations.c line 379
  • #7 select_matching_profile
    at locations-combo.c line 306
  • #8 gst_locations_combo_constructor
    at locations-combo.c line 505
  • #9 IA__g_object_newv
    at gobject.c line 937
  • #10 IA__g_object_new_valist
    at gobject.c line 1022
  • #11 IA__g_object_new
    at gobject.c line 795
  • #12 gst_locations_combo_new
    at locations-combo.c line 547
  • #13 gst_network_tool_constructor
    at network-tool.c line 210
  • #14 IA__g_object_newv
    at gobject.c line 937
  • #15 IA__g_object_new_valist
    at gobject.c line 1022
  • #16 IA__g_object_new
    at gobject.c line 795
  • #17 gst_network_tool_new
    at network-tool.c line 360
  • #18 main
    at main.c line 166
  • #19 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #20 _start
  • #0 __kernel_vsyscall

Comment 3 Carlos Garnacho 2006-11-17 03:53:38 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 bug has been marked as a duplicate of 354536 ***