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 360751 - crash in Networking: nothing
crash in Networking: nothing
Status: RESOLVED DUPLICATE of bug 360435
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-10-08 21:27 UTC by olivier.baudouin
Modified: 2006-10-08 23:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description olivier.baudouin 2006-10-08 21:27:18 UTC
Version: 2.15.5

What were you doing when the application crashed?
nothing


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

Memory status: size: 32579584 vsize: 0 resident: 32579584 share: 0 rss: 8871936 rss_rlim: 0
CPU usage: start_time: 1160342803 rtime: 0 utime: 10 stime: 0 cutime:8 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 -1225898320 (LWP 9914)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225898320 (LWP 9914))

  • #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 ??
    from /usr/lib/liboobs-1.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-08 23:17:16 UTC
Thanks for the bug report. 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?


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