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 382703 - crash in Networking: accessing networking UI ...
crash in Networking: accessing networking UI ...
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-12-05 19:08 UTC by klichong
Modified: 2006-12-07 10:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description klichong 2006-12-05 19:08:39 UTC
Version: 2.15.5

What were you doing when the application crashed?
accessing networking UI in menu. (was trying to switch from wireless to ethernet)


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

Memory status: size: 33890304 vsize: 0 resident: 33890304 share: 0 rss: 11452416 rss_rlim: 0
CPU usage: start_time: 1165345667 rtime: 0 utime: 31 stime: 0 cutime:29 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 -1226004816 (LWP 14339)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226004816 (LWP 14339))

  • #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 Christian Kirbach 2006-12-05 19:46:00 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 ***
Comment 2 klichong 2006-12-06 17:23:09 UTC
Hi Christian,

Thanks for the information.  I have viewed the bugreport for 354536 and seen that it is NOTGNOME resolution.  Does this imply that I have to reinstall ubuntu to get this functionality back (or configure the networking manually from now on)?

Thanks,

kim
Comment 3 Christian Kirbach 2006-12-07 10:32:13 UTC
from the other report

Comment #12 from Sebastien Bacher (developer, points: 26) 
2006-10-11 14:20 UTC [reply] 
Thank you for tracking that. I've just fixed the Ubuntu edgy package, Ubuntu
dapper and Debian probably don't have the issue, they still use the
gnome-system-tools 1.4 which works fine with sudo. Marking as NOTGNOME

Thus the problem should be fixed with the next (automatic?) update of the network-admin package. no need for a re-install (usually never on Unix/Linux systems)

If it still happens after an upgrade feel free to reopen bug 354536 and say that it still happens with version xyz of network-admin package.