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 467305 - crash in Tasks: opening evolution
crash in Tasks: opening evolution
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-16 13:10 UTC by Juan Pablo Giménez
Modified: 2007-09-24 19:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Juan Pablo Giménez 2007-08-16 13:10:18 UTC
Version: 2.10

What were you doing when the application crashed?
opening 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 175927296 vsize: 175927296 resident: 71532544 share: 38158336 rss: 71532544 rss_rlim: 4294967295
CPU usage: start_time: 1187269632 rtime: 681 utime: 593 stime: 88 cutime:2 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208662304 (LWP 3782)]
[New Thread -1257722992 (LWP 3870)]
[New Thread -1280754800 (LWP 3840)]
[New Thread -1246839920 (LWP 3804)]
(no debugging symbols found)
0x00bf6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208662304 (LWP 3782))

  • #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 (2036 sec old) ---------------------
20060519T080000Z is a recurrence instance
20060519T080000Z is a recurrence instance
20061108T132727Z-5820-500-1-1@maggie.rcom.com.ar has recurrences
20061108T134409Z-8508-500-1-22@maggie.rcom.com.ar has recurrences
20060614T124533Z-7843-500-1-0@maggie.rcom.com.ar has recurrences
20060610115511.19522.10144.398186.9623782@tigris.serverpronto.com has recurrences
20060910055224.5719.54744.636876.4994793@tigris.serverpronto.com has recurrences
20060715143659.10054.41515.478050.6387087@tigris.serverpronto.com has recurrences
20061005051000.5627.41898.100854.7275430@tigris.serverpronto.com has recurrences
20060815114858.9047.86439.595636.7864401@tigris.serverpronto.com has recurrences
20060718215800.13049.92189.342157.2218425@tigris.serverpronto.com has recurrences
20060718215914.13049.20376.651905.7617999@tigris.serverpronto.com has recurrences
20060616062159.5611.84670.447037.8300800@tigris.serverpronto.com has recurrences
20060607084045.19522.44289.706772.1645102@tigris.serverpronto.com has recurrences
--------------------------------------------------
Comment 1 palfrey 2007-08-17 11:04:02 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 19:04:51 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 ***