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 471556 - crash in Tasks: Pressed "send & receive"...
crash in Tasks: Pressed "send & receive"...
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-29 20:33 UTC by vitkinet
Modified: 2007-09-24 18:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vitkinet 2007-08-29 20:33:04 UTC
Version: 2.10

What were you doing when the application crashed?
Pressed "send & receive" after activating Evolution.
The system ran in parallel a P2P application (azureus) which at the moment took 100% of upload and 30% of download rate limit.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Pastel
Icon Theme: Tango

Memory status: size: 255750144 vsize: 255750144 resident: 74268672 share: 63770624 rss: 74268672 rss_rlim: 4294967295
CPU usage: start_time: 1188419226 rtime: 344 utime: 306 stime: 38 cutime:3 cstime: 10 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208457504 (LWP 11910)]
[New Thread -1419662448 (LWP 11969)]
[New Thread -1292469360 (LWP 11937)]
(no debugging symbols found)
0x009c7402 in __kernel_vsyscall ()

Thread 1 (Thread -1208457504 (LWP 11910))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (60123 sec old) ---------------------
    NetworkConnectionImpl::notifyOfException::189,MultiPeerDownloader::doProcessing::169,ReadController::doHighPriorityRead::224,ReadController::readProcessorLoop::199,ReadController::access$1::181,Re
java.lang.NullPointerException
	at org.gudy.azureus2.core3.peer.impl.transport.PEPeerTransportProtocol.decodeAZPeerExchange(PEPeerTransportProtocol.java:2287)
	at org.gudy.azureus2.core3.peer.impl.transport.PEPeerTransportProtocol$7.messageReceived(PEPeerTransportProtocol.java:2046)
	at com.aelitis.azureus.core.networkmanager.impl.IncomingMessageQueueImpl.receiveFromTransport(IncomingMessageQueueImpl.java:123)
	at com.aelitis.azureus.core.networkmanager.impl.MultiPeerDownloader.doProcessing(MultiPeerDownloader.java:150)
	at com.aelitis.azureus.core.networkmanager.impl.ReadController.doHighPriorityRead(ReadController.java:224)
	at com.aelitis.azureus.core.networkmanager.impl.ReadController.readProcessorLoop(ReadController.java:199)
	at com.aelitis.azureus.core.networkmanager.impl.ReadController.access$1(ReadController.java:181)
	at com.aelitis.azureus.core.networkmanager.impl.ReadController$2.runSupport(ReadController.java:77)
	at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69)
DEBUG::Wed Aug 29 07:46:09 MSD 2007::org.gudy.azureus2.core3.peer.impl.transport.PEPeerTransportProtocol$2::exceptionThrown::274:
    NetworkConnectionImpl::notifyOfException::189,MultiPeerDownloader::doProcessing::169,ReadController::doHighPriorityRead::224,ReadController::readProcessorLoop::188,ReadController::access$1::181,Re
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-24 18:28:52 UTC
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 364700 ***