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 477014 - crash in Tasks: I had just deleted an em...
crash in Tasks: I had just deleted an em...
Status: RESOLVED DUPLICATE of bug 239441
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-14 19:05 UTC by dsteckbeck
Modified: 2007-09-25 01:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dsteckbeck 2007-09-14 19:05:33 UTC 
Version: 2.10

What were you doing when the application crashed?
I had just deleted an email message, then clicked on another message folder to read additional messages.


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 200884224 vsize: 200884224 resident: 85696512 share: 42258432 rss: 85696512 rss_rlim: 4294967295
CPU usage: start_time: 1189532940 rtime: 382953 utime: 379306 stime: 3647 cutime:3 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208629536 (LWP 11157)]
[New Thread -1254548592 (LWP 19487)]
[New Thread -1211413616 (LWP 12732)]
[New Thread -1244058736 (LWP 11202)]
[New Thread -1221219440 (LWP 11201)]
0x00110402 in __kernel_vsyscall ()

+ Trace 162964

Thread 1 (Thread -1208629536 (LWP 11157))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 resort_node
    at e-tree-table-adapter.c line 158
  • #6 etta_sort_info_changed
    at e-tree-table-adapter.c line 824
  • #7 resort_model
    at e-tree-table-adapter.c line 751
  • #8 g_idle_dispatch
    at gmain.c line 3928
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 bonobo_main
    at bonobo-main.c line 311
  • #13 main
    at main.c line 586
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7529815 sec old) ---------------------
** Message: don't know how to handle video/x-flv
** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.
gstplaybasebin.c(2182): prepare_output (): /play
totem-video-thumbnailer couln't open file 'file:///home/dsteckbeck/Media/WorkingWithMonkeys.flv'
Reason: The playback of this movie requires a Flash demuxer plugin which is not installed..
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Error: Bad annotation destination position
Error: Bad annotation destination position
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x1274111 ().
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1278746 (Pictures); these messages lack timestamps and therefore suck.
** (gnome-panel:2671): WARNING **: Could not ask power manager to suspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security polic
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-25 01:48:41 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 239441 ***