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 469925 - crash in Tasks: sending an email
crash in Tasks: sending an email
Status: RESOLVED DUPLICATE of bug 426807
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 471912 478203 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-24 15:06 UTC by bernie
Modified: 2008-03-20 13:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bernie 2007-08-24 15:06:11 UTC 
Version: 2.10

What were you doing when the application crashed?
sending an email


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.23-0.115.rc3.git1.fc8.bernie #1 SMP Wed Aug 22 16:59:02 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 785276928 vsize: 785276928 resident: 98349056 share: 56213504 rss: 98349056 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187966427 rtime: 2472 utime: 2124 stime: 348 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912562657856 (LWP 28166)]
[New Thread 1094719824 (LWP 1824)]
[New Thread 1115965776 (LWP 1802)]
[New Thread 1115699536 (LWP 1800)]
[New Thread 1084229968 (LWP 28257)]
(no debugging symbols found)
0x00002aaaac0e001f in waitpid () from /lib64/libpthread.so.0

+ Trace 157608

Thread 1 (Thread 46912562657856 (LWP 28166))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #8 ??
    from /lib64/libglib-2.0.so.0
  • #9 bonobo_ui_engine_dispose
    from /usr/lib64/libbonoboui-2.so.0
  • #10 ??
    from /usr/lib64/libbonoboui-2.so.0
  • #11 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #12 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #15 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #16 ??
    from /lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #19 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (54364 sec old) ---------------------
  Resource id:  0x141026d
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x141026d
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1410314
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1410314
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-08-30 16:38:38 UTC 
*** Bug 471912 has been marked as a duplicate of this bug. ***
Comment 2 palfrey 2007-12-04 18:22:59 UTC 
*** Bug 478203 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Mueller 2008-03-20 13:36:53 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 426807 ***