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 367432 - crash in Networking: I was opening network-ad...
crash in Networking: I was opening network-ad...
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-30 06:36 UTC by trogdoor
Modified: 2006-11-01 09:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description trogdoor 2006-10-30 06:36:19 UTC 
Version: 2.15.5

What were you doing when the application crashed?
I was opening network-admin after waking from suspend.


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

Memory status: size: 50462720 vsize: 0 resident: 50462720 share: 0 rss: 8732672 rss_rlim: 0
CPU usage: start_time: 1160429836 rtime: 0 utime: 6 stime: 0 cutime:6 cstime: 0 timeout: 0 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 -1225828688 (LWP 22480)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80253

Thread 1 (Thread -1225828688 (LWP 22480))

  • #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


André Klapper





          2006-10-30 11:36:11 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


André Klapper





          2006-11-01 09:04:10 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.
Can you please answer the question in bug report 360435? Thanks in advance.

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