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 446503 - crash in Tasks: Restored the .evulation ...
crash in Tasks: Restored the .evulation ...
Status: RESOLVED DUPLICATE of bug 438756
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 446478 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-11 20:29 UTC by gyula.racz
Modified: 2007-06-12 01:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gyula.racz 2007-06-11 20:29:50 UTC
What were you doing when the application crashed?
Restored the .evulation directory and clicked on the sent folder.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 560123904 vsize: 560123904 resident: 47067136 share: 34045952 rss: 47067136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181593736 rtime: 172 utime: 157 stime: 15 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496500320 (LWP 4845)]
[New Thread 1084229968 (LWP 4850)]
(no debugging symbols found)
0x00000033af00d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496500320 (LWP 4845))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #5 e_table_sorting_utils_tree_sort
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #7 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/libetable.so.0
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    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 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
  Minor opcode:  0
  Resource id:  0x1402312
CalDAV Eplugin starting up ...
** (evolution:4845): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4845): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x1a5
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x1a5
--------------------------------------------------
Comment 1 gyula.racz 2007-06-11 21:06:13 UTC
*** Bug 446478 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2007-06-12 01:02:20 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 438756 ***