GNOME Bugzilla – Bug 466098
crash in Evolution: Checking Main
Last modified: 2007-10-01 13:44:31 UTC
What were you doing when the application crashed? Checking Main Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Xfce-kde2 Icon Theme: ikons Memory status: size: 215871488 vsize: 215871488 resident: 31248384 share: 19505152 rss: 31248384 rss_rlim: 4294967295 CPU usage: start_time: 1186964449 rtime: 148 utime: 118 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1236883744 (LWP 18944)] [New Thread -1381385312 (LWP 18980)] [New Thread -1369990240 (LWP 18968)] [New Thread -1361597536 (LWP 18967)] [New Thread -1352811616 (LWP 18966)] [New Thread -1292104800 (LWP 18959)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 154759
Thread 1 (Thread -1236883744 (LWP 18944))
----------- .xsession-errors (1144883 sec old) --------------------- channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=0, remote_address=<null>, remote_port=0 ConnectDisconnectManager::mainLoop::150,ConnectDisconnectManager::access$500::45,ConnectDisconnectManager$3::runSupport::140,AEThread::run::69 java.net.SocketException: Network is unreachable at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager.addNewRequest(ConnectDisconnectManager.java:241) at com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager.addNewOutboundRequests(ConnectDisconnectManager.java:172) at com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager.mainLoop(ConnectDisconnectManager.java:150) at com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager.access$500(ConnectDisconnectManager.java:45) at com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager$3.runSupport(ConnectDisconnectManager.java:140) at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69) DEBUG::Mon Jul 30 14:20:45 EDT 2007::com.aelitis.azureus.core.networkmanager.impl.tcp.ConnectDisconnectManager::addNewOutboundRequests::172: ConnectDisconnectManager::address exception: full=/24.85.100.195:32459, hostname=24.85.100.195, port=32459, unresolved=false, full_sub=24.85.100.195/24.85.100.195, host_address=24.85.100.195 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=0, remote_address=<null>, remote_port=0 ...Too much output, ignoring rest... --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 431459 ***