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 496214 - crash in Tasks: Distribution: Fedora rel...
crash in Tasks: Distribution: Fedora rel...
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-11-12 19:24 UTC by dcatkin
Modified: 2007-11-14 00:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dcatkin 2007-11-12 19:24:16 UTC 
Version: 2.10

What were you doing when the application crashed?
Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-10-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-4.fc7 #1 SMP Fri Oct 12 20:26:14 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: 119369728 vsize: 119369728 resident: 41488384 share: 29462528 rss: 41488384 rss_rlim: 4294967295
CPU usage: start_time: 1194898156 rtime: 303 utime: 269 stime: 34 cutime:0 cstime: 2 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 -1208174880 (LWP 10822)]
[New Thread -1268364400 (LWP 10878)]
[New Thread -1216926832 (LWP 10845)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 177246

Thread 1 (Thread -1208174880 (LWP 10822))

  • #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
  • #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 


----------- .xsession-errors (13 sec old) ---------------------
Window manager warning: last_focus_time (1194898081) is greater than comparison timestamp (897174382).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: last_user_time (1194898081) is greater than comparison timestamp (897174382).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x3200003 (Blog Maste) appears to be one of the offending windows with a timestamp of 1194898081.  Working around...
CalDAV Eplugin starting up ...
(evolution:10822): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution:10822): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution:10822): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:10822): DEBUG: mailto URL program: evolution
(evolution:10822): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:10822): e-data-server-ui-WARNING **: Key file does not have key 'pop:__dcatkin%40comcast.net@mail.comcast.net_'
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-14 00:53:19 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 ***