[apport] evolution crashed with SIGSEGV in gtk_drag_update_icon()

Bug #93055 reported by magilus
4
Affects Status Importance Assigned to Milestone
GTK+
Expired
Critical
gtk+2.0 (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I moved some mails to Trash. After doing that often, Evolution hung. After, it closed.

ProblemType: Crash
Architecture: i386
Date: Sat Mar 17 12:37:23 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/evolution
InterpreterPath: /usr/bin/evolution-2.10
Package: evolution 2.10.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: evolution --component=mail
ProcCwd: /home/martin
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgthread-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgthread-2.0.so.0
Uname: Linux martin-desktop 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Revision history for this message
magilus (magilus) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gtk_drag_update_icon (info=0x0) at gtkdnd.c:2846
g_idle_dispatch (source=0x8fda418, callback=0xb7ac0bc0 <gtk_drag_anim_timeout+240>, user_data=0x8d1af10)
IA__g_main_context_dispatch (context=0x8094ad8) at gmain.c:2045
g_main_context_iterate (context=0x8094ad8, block=1, dispatch=1, self=0x8067268) at gmain.c:2677
IA__g_main_loop_run (loop=0x80c5a68) at gmain.c:2881

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=420121

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Changed in gtk:
status: Unknown → Unconfirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

did you get the issue again since?

Changed in gtk+2.0:
status: Confirmed → Triaged
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gtk+2.0 (Ubuntu):
status: Triaged → Invalid
Changed in gtk:
importance: Unknown → Critical
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.