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 504241 - crash in Tasks: Writing an email.
crash in Tasks: Writing an email.
Status: RESOLVED DUPLICATE of bug 470835
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-18 13:27 UTC by jmoore
Modified: 2007-12-18 22:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jmoore 2007-12-18 13:27:38 UTC
Version: 2.10

What were you doing when the application crashed?
Writing an email.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-61.fc6 #1 SMP Thu Sep 27 18:48:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Fedora

Memory status: size: 400965632 vsize: 400965632 resident: 216944640 share: 46223360 rss: 216944640 rss_rlim: 4294967295
CPU usage: start_time: 1197663131 rtime: 80183 utime: 71494 stime: 8689 cutime:0 cstime: 1 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 -1209121056 (LWP 2538)]
[New Thread -1386226800 (LWP 12807)]
[New Thread -1284576368 (LWP 3387)]
[New Thread -1296094320 (LWP 3125)]
[New Thread -1263596656 (LWP 2549)]
[New Thread -1253106800 (LWP 2548)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209121056 (LWP 2538))

  • #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_type_check_instance_cast
    from /lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libORBit-2.so.0
  • #7 ORBit_object_get_connection
    from /usr/lib/libORBit-2.so.0
  • #8 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #9 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #10 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #11 GNOME_Evolution_Addressbook_BookView_start
    from /usr/lib/libebook-1.2.so.9
  • #12 e_book_view_start
    from /usr/lib/libebook-1.2.so.9
  • #13 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #14 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #15 e_contact_store_set_query
    from /usr/lib/libedataserverui-1.2.so.8
  • #16 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (60986 sec old) ---------------------
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) /dev/hdc: READ 10 failed!
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-12-18 22:54:54 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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