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 323514 - evolution locks up whon double clicking to add users to the TO: field
evolution locks up whon double clicking to add users to the TO: field
Status: RESOLVED DUPLICATE of bug 323753
Product: evolution
Classification: Applications
Component: Contacts
2.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 323515 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-12-08 04:13 UTC by Robin Cook
Modified: 2006-01-19 07:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robin Cook 2005-12-08 04:13:38 UTC 
Distribution/Version: SourceMage

On either New or Forward message.
Click the To: button.
double click on anyone in my personal address book and evolution locks up to
where I have to use killev to kill it.
Comment 1 Sushma Rai 2005-12-08 04:47:54 UTC 
Can you please attach gdb to Evolution process and get the 
backtraces by using gdb the command "thread apply all bt", when
Evolution freezes ?
(see http://live.gnome.org/GettingTraces)

Also, start Evolution and evolution-data-server from the console 
and see if any debug messages are printed on the console when it hangs?
Comment 2 Poornima 2005-12-08 05:54:05 UTC 
*** Bug 323515 has been marked as a duplicate of this bug. ***
Comment 3 Robin Cook 2005-12-08 06:16:23 UTC 
I was unable to do anything as a user because evolution would crash almost
immeadiately after typing run in debug.

I logged in as root and was able to get something with just the bt command.

AS USER

(evolution-2.4:21429): camel-WARNING **: camel_exception_get_id called with NULL
parameter.
(gdb) run
Starting program: /usr/bin/evolution-2.4
adding hook target 'source'
Detaching after fork from child process 21434.

(evolution-2.4:21429): camel-WARNING **: camel_exception_get_id called with NULL
parameter.

Program exited with code 01.
(gdb) thread apply all bt
(gdb)


AS ROOT

(gdb) run
Starting program: /usr/bin/evolution-2.4
adding hook target 'source'
Detaching after fork from child process 21597.

(evolution-2.4:21591): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion
`GDK_IS_GC (gc)' failed

(evolution-2.4:21591): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion
`GDK_IS_GC (gc)' failed

Program received signal SIGSEGV, Segmentation fault.
0xb665f6ee in free () from /lib/libc.so.6
(gdb) thread apply all bt
(gdb) bt

+ Trace 64484

  • #0 free
    from /lib/libc.so.6
  • #1 malloc
    from /lib/libc.so.6
  • #2 g_malloc
    from /usr/lib/libglib-2.0.so.0
  • #3 gtk_tree_path_copy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 validate_visible_area
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 do_presize_handler
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 presize_handler_callback
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 main 






Comment 4


Sushma Rai





          2005-12-08 06:37:29 UTC
        



not sure why evolution crashes when you rin with gdb.
Could be some problem with the distro you are using.

Looking at the logs, i don't see nay evolution related information.







Comment 5


Robin Cook





          2005-12-09 12:44:24 UTC
        



Not sure why either but if I go back to 2.4.1 it doesn't do this.   Also noticed
that the count of the number unread doesn't clear after restarting until I go to
another folder then back.






Comment 6


Devashish Sharma





          2006-01-19 07:41:17 UTC
        




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