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 479248 - crash in Tasks: I was trying to open a m...
crash in Tasks: I was trying to open a m...
Status: RESOLVED DUPLICATE of bug 239441
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-09-22 12:31 UTC by tom.louton
Modified: 2007-10-12 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description tom.louton 2007-09-22 12:31:52 UTC 
Version: 2.10

What were you doing when the application crashed?
I was trying to open a mail from postmaster@eone, cannot read the rest. 
Evolution has crased earlier today, but since i had reinstalled my system, i had forgot the debuggin stuff, but now it is installed too.
I hope this helps.
Sincerely yours,
Tom Louton


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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 167776256 vsize: 167776256 resident: 80568320 share: 31866880 rss: 80568320 rss_rlim: 4294967295
CPU usage: start_time: 1190485691 rtime: 1592 utime: 1574 stime: 18 cutime:0 cstime: 1 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 -1208637728 (LWP 4406)]
[New Thread -1244636272 (LWP 4436)]
[New Thread -1223246960 (LWP 4423)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164632

Thread 1 (Thread -1208637728 (LWP 4406))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #7 resort_model
    from /usr/lib/evolution/2.10/libetable.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-publish-calendar.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-publish-cal
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so.debug" does not match "/usr/lib/evolution-data-server-1.2/camel-providers/li
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution-data-server-1.2/camel-providers/libcamelpop3.so.debug" does not match "/usr/lib/evolution-data-server-1.2/camel-providers/lib
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-not
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise-features.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-12 13:15:35 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 ***