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 466110 - crash in Tasks: I was trying to type in ...
crash in Tasks: I was trying to type in ...
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-13 02:06 UTC by Basil Mohamed Gohar
Modified: 2007-08-13 14:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Basil Mohamed Gohar 2007-08-13 02:06:51 UTC 
Version: 2.10

What were you doing when the application crashed?
I was trying to type in the "Search" bar someone's name to find their e-mail address


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-2.3228.fc7.ez #1 SMP Sat Jun 16 12:17:55 BST 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: 187674624 vsize: 187674624 resident: 82968576 share: 52064256 rss: 82968576 rss_rlim: 4294967295
CPU usage: start_time: 1186944318 rtime: 4739 utime: 4206 stime: 533 cutime:485 cstime: 69 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208236320 (LWP 29162)]
[New Thread -1301107824 (LWP 31740)]
[New Thread -1300841584 (LWP 29222)]
[New Thread -1228694640 (LWP 29187)]
0x00747402 in __kernel_vsyscall ()

+ Trace 154770

Thread 1 (Thread -1208236320 (LWP 29162))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 IA__g_utf8_offset_to_pointer
    at gutf8.c line 302
  • #6 get_entry_substring
    at e-name-selector-entry.c line 520
  • #7 entry_activate
    at e-name-selector-entry.c line 1402
  • #8 user_focus_out
    at e-name-selector-entry.c line 1464
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    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 g_type_class_meta_marshal
    at gclosure.c line 567
  • #20 IA__g_closure_invoke
    at gclosure.c line 490
  • #21 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #22 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #23 IA__g_signal_emit
    at gsignal.c line 2243
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #27 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #28 g_main_context_iterate
    at gmain.c line 2677
  • #29 IA__g_main_loop_run
    at gmain.c line 2881
  • #30 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #31 main
    at main.c line 586
  • #0 __kernel_vsyscall 


----------- .xsession-errors (25446 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-08-13 14:11:55 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 458670 ***