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 360856 - crash in Networking: Opstarten van Netwerkbeh...
crash in Networking: Opstarten van Netwerkbeh...
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-09 08:54 UTC by stefan.pollaris
Modified: 2006-10-09 15:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description stefan.pollaris 2006-10-09 08:54:55 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Opstarten van Netwerkbeheer


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

Memory status: size: 59813888 vsize: 0 resident: 59813888 share: 0 rss: 8986624 rss_rlim: 0
CPU usage: start_time: 1160384043 rtime: 0 utime: 13 stime: 0 cutime:12 cstime: 0 timeout: 1 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 -1225611600 (LWP 10982)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75397

Thread 1 (Thread -1225611600 (LWP 10982))

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


Fabio Bonelli





          2006-10-09 09:07:14 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.







Comment 2


stefan.pollaris





          2006-10-09 13:47:57 UTC
        



(In reply to comment #1)
> Thanks for the bug report. Unfortunately, that stack trace is not very useful
> in determining the cause of the crash. Can you get us one with debugging
> symbols? Please see http://live.gnome.org/GettingTraces for more information on
> how to do so.
> 

I'm sorry I can't reproduce the error . I restarted the system and the error is gone , everything is ok now . Thanks for the quick answer .






Comment 3


Karsten Bräckelmann





          2006-10-09 15:59: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 360435 ***