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 477798 - crash in Tasks: I just did a paste of te...
crash in Tasks: I just did a paste of te...
Status: RESOLVED DUPLICATE of bug 458322
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-17 15:16 UTC by sdb
Modified: 2007-09-20 18:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sdb 2007-09-17 15:16:26 UTC
Version: 2.10

What were you doing when the application crashed?
I just did a paste of text into the test box, then entered the recipient into the To: box, and was trying to tab down to Subject:


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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 150577152 vsize: 150577152 resident: 30343168 share: 18137088 rss: 30343168 rss_rlim: 4294967295
CPU usage: start_time: 1189798230 rtime: 2869 utime: 2511 stime: 358 cutime:1 cstime: 6 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 -1208686880 (LWP 26124)]
[New Thread -1263543408 (LWP 26211)]
[New Thread -1283957872 (LWP 26159)]
[New Thread -1253053552 (LWP 26154)]
[New Thread -1210786928 (LWP 26151)]
(no debugging symbols found)
0x00519402 in __kernel_vsyscall ()

Thread 1 (Thread -1208686880 (LWP 26124))

  • #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_utf8_offset_to_pointer
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #7 ??
    from /usr/lib/libedataserverui-1.2.so.8
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emitv
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_bindings_activate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libbonoboui-2.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #41 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #42 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (235513 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e7fef5 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e7fef5 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:26124): gtkhtml-WARNING **: Selection retrieval failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00055 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00055 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e03e6f (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-20 18:07:53 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 458322 ***