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 458037 - crash in Tasks: Trying to install fc7 wi...
crash in Tasks: Trying to install fc7 wi...
Status: RESOLVED DUPLICATE of bug 450947
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-18 17:07 UTC by Charles Brewster
Modified: 2007-07-19 15:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Charles Brewster 2007-07-18 17:07:34 UTC 
What were you doing when the application crashed?
Trying to install fc7 with minimal luck


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 153333760 vsize: 153333760 resident: 49299456 share: 24104960 rss: 49299456 rss_rlim: 4294967295
CPU usage: start_time: 1184723441 rtime: 3151 utime: 2936 stime: 215 cutime:0 cstime: 0 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 -1208858912 (LWP 3968)]
[New Thread -1353786480 (LWP 5454)]
[New Thread -1364276336 (LWP 5453)]
[New Thread -1259377776 (LWP 4111)]
[New Thread -1228166256 (LWP 4071)]
[New Thread -1322316912 (LWP 4043)]
(no debugging symbols found)
0x00404402 in __kernel_vsyscall ()

+ Trace 148894

Thread 1 (Thread -1208858912 (LWP 3968))

  • #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 /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #11 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (43087 sec old) ---------------------
(evolution:3968): e-data-server-DEBUG: Loaded default categories
(evolution:3968): e-data-server-DEBUG: Saving categories to "/root/.evolution/categories.xml"
** (evolution:3968): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3968): DEBUG: mailto URL program: evolution
(evolution:3968): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3968): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:3968): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
BBDB spinning up...
(evolution:3968): 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?)
(evolution:3968): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa41d128'
(evolution:3968): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa41d248'
--------------------------------------------------
Comment 1 palfrey 2007-07-19 15:11:04 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 450947 ***