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 493918 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431459
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-11-05 21:35 UTC by weinerdog
Modified: 2007-11-05 23:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description weinerdog 2007-11-05 21:35:51 UTC
Version: 2.10

What were you doing when the application crashed?



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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Cillop-Midnite
Icon Theme: gnome

Memory status: size: 147587072 vsize: 147587072 resident: 55185408 share: 33312768 rss: 55185408 rss_rlim: 4294967295
CPU usage: start_time: 1194296807 rtime: 11880 utime: 11789 stime: 91 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209088288 (LWP 2704)]
[New Thread -1252000880 (LWP 4363)]
[New Thread -1229231216 (LWP 2796)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209088288 (LWP 2704))

  • #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 ---------------------
DEBUG::Tue Nov 06 07:27:22 EST 2007::org.gudy.azureus2.core3.peer.impl.transport.PEPeerTransportProtocol$2::exceptionThrown::274:
    NetworkConnectionImpl::notifyOfException::189,MultiPeerDownloader::doProcessing::169,ReadController::doHighPriorityRead::224,ReadController::readProcessorLoop::199,ReadController::access$100::43,R
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$100(ReadController.java:43)
	at com.aelitis.azureus.core.networkmanager.impl.ReadController$2.runSupport(ReadController.java:77)
	at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69)
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-05 23:18:58 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 431459 ***