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 472246 - crash in Tasks: sending/receiving e-mail...
crash in Tasks: sending/receiving e-mail...
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-31 15:40 UTC by brunohendryckx
Modified: 2007-09-24 18:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description brunohendryckx 2007-08-31 15:40:41 UTC
Version: 2.10

What were you doing when the application crashed?
sending/receiving e-mail with evolution


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: Enabled
GTK+ Theme: Bluecurve-Grape
Icon Theme: Mist

Memory status: size: 115597312 vsize: 115597312 resident: 36474880 share: 28831744 rss: 36474880 rss_rlim: 4294967295
CPU usage: start_time: 1188574554 rtime: 87 utime: 77 stime: 10 cutime:2 cstime: 3 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 -1208723744 (LWP 2496)]
[New Thread -1219064944 (LWP 2673)]
[New Thread -1231029360 (LWP 2522)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208723744 (LWP 2496))

  • #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 ---------------------
(pidgin:2566): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstice.so': libjinglep2pbase-0.3.so.0: cannot open shared object file: No such file or directory
(pidgin:2566): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstjrtp.so': libjrtp-3.7.0.so: cannot open shared object file: No such file or directory
(pidgin:2566): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstpulse.so': libpulse.so.0: cannot open shared object file: No such file or directory
(pidgin:2566): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstrtppayloads.so': /usr/lib/gstreamer-0.10/libgstrtppayloads.so: undefined symbol: gst_rtp_g729_pay_plugin_init
GTK Accessibility Module initialized
Bonobo accessibility support initialized
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Lucky Wankhede 2007-09-07 14:12:18 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-09-24 18:01:06 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 ***