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 312513 - crash in gtk while using evolution
crash in gtk while using evolution
Status: RESOLVED DUPLICATE of bug 339369
Product: evolution
Classification: Applications
Component: general
2.4.x (obsolete)
Other other
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-08-03 22:30 UTC by Tom Duffy
Modified: 2013-09-13 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Tom Duffy 2005-08-03 22:30:54 UTC 
Distribution: Fedora Core release 4 (Stentz)
Package: gtk+
Severity: normal
Version: GNOME2.11.4 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: crash in gtk while using evolution
Bugzilla-Product: gtk+
Bugzilla-Component: gtk
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.11.1)
Description:
gtk 2.7.4
evolution 2.3.6.1


Debugging Information:

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496461120 (LWP 13498)]
[New Thread 1157925216 (LWP 14280)]
[New Thread 1157658976 (LWP 14279)]
[New Thread 1147169120 (LWP 13582)]
[New Thread 1136679264 (LWP 13579)]
[New Thread 1126189408 (LWP 13578)]
[New Thread 1115699552 (LWP 13577)]
[New Thread 1105209696 (LWP 13572)]
[New Thread 1094719840 (LWP 13571)]
[New Thread 1084229984 (LWP 13570)]
0x00000037cd80bfa9 in waitpid () from /lib64/libpthread.so.0

+ Trace 62185

Thread 1 (Thread 46912496461120 (LWP 13498))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 749 




------- Bug moved to this database by unknown@gnome.bugs 2005-08-03 22:30 UTC -------
Comment 1 Teppo Turtiainen 2005-08-04 06:28:26 UTC 
According to simple-dup-finder this is a unique stack trace.
Comment 2 Daniel Llano 2005-09-17 16:36:33 UTC 
Could you try more up to date software versions and try again to reproduce the bug?
Comment 3 Tom Duffy 2005-09-19 22:57:11 UTC 
I have no idea how to reproduce.
Comment 4 Matthias Clasen 2006-03-28 20:16:36 UTC 
menu_deactivate_callback is a function in evolution
Comment 5 André Klapper 2006-06-20 22:54:23 UTC 
same stacktrace as bug 339369

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