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 481306 - crash in Tasks: Closed a mailbox quota w...
crash in Tasks: Closed a mailbox quota w...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 481307 481535 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-28 14:19 UTC by oliver
Modified: 2008-09-19 17:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description oliver 2007-09-28 14:19:38 UTC
Version: 2.10

What were you doing when the application crashed?
Closed a mailbox quota warning dialog.


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.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 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: 187871232 vsize: 187871232 resident: 76918784 share: 48427008 rss: 76918784 rss_rlim: 4294967295
CPU usage: start_time: 1190965159 rtime: 1894 utime: 1722 stime: 172 cutime:23 cstime: 11 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 -1208465696 (LWP 3668)]
[New Thread -1337558128 (LWP 3795)]
[New Thread -1349817456 (LWP 3763)]
[New Thread -1264583792 (LWP 3713)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208465696 (LWP 3668))

  • #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 __pthread_mutex_lock
    at pthread_mutex_lock.c line 46
  • #6 e_flag_set
    at e-flag.c line 83
  • #7 user_message_response
    at mail-session.c line 287
  • #8 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #9 IA__g_closure_invoke
    at gclosure.c line 490
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #12 IA__g_signal_emit
    at gsignal.c line 2243
  • #13 IA__gtk_dialog_response
    at gtkdialog.c line 835
  • #14 action_widget_activated
    at gtkdialog.c line 534
  • #15 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #19 IA__g_signal_emit
    at gsignal.c line 2243
  • #20 IA__gtk_button_clicked
    at gtkbutton.c line 889
  • #21 gtk_real_button_released
    at gtkbutton.c line 1484
  • #22 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #23 g_type_class_meta_marshal
    at gclosure.c line 567
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #27 IA__g_signal_emit
    at gsignal.c line 2243
  • #28 IA__gtk_button_released
    at gtkbutton.c line 881
  • #29 gtk_button_button_release
    at gtkbutton.c line 1377
  • #30 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #31 g_type_class_meta_marshal
    at gclosure.c line 567
  • #32 IA__g_closure_invoke
    at gclosure.c line 490
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #34 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #35 IA__g_signal_emit
    at gsignal.c line 2243
  • #36 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #37 IA__gtk_propagate_event
    at gtkmain.c line 2341
  • #38 IA__gtk_main_do_event
    at gtkmain.c line 1575
  • #39 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #40 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #41 g_main_context_iterate
    at gmain.c line 2677
  • #42 IA__g_main_loop_run
    at gmain.c line 2881
  • #43 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #44 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (9752 sec old) ---------------------
(evolution:3668): evolution-mail-WARNING **: Failed to refresh folders: No such folder Shared Folders/User/t204
(evolution:3668): evolution-mail-WARNING **: Failed to refresh folders: No such folder Shared Folders/User/t211
(evolution:3668): evolution-mail-WARNING **: Failed to refresh folders: No such folder Shared Folders/User/tpc4
WARNING: synergyc.cpp,265: failed to connect to server: Connection refused
DEBUG: synergyc.cpp,237: retry in 60 seconds
** Message: don't know how to handle video/x-xvid, framerate=(fraction)2997003/125000, width=(int)624, height=(int)352
totem-video-thumbnailer: 'file:///home/oli/Desktop/eureka.211.dsr.xvid.notv.%5BVTV%5D.avi.part' isn't thumbnailable
Reason: Media contains no supported video streams.
** Message: don't know how to handle video/x-xvid, framerate=(fraction)2997003/125000, width=(int)624, height=(int)352
totem-video-thumbnailer: 'file:///home/oli/Desktop/eureka.211.dsr.xvid.notv.%5BVTV%5D.avi.part' isn't thumbnailable
Reason: Media contains no supported video streams.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-01-17 09:25:23 UTC
Could be dup of bug 481307
Comment 2 Akhil Laddha 2008-05-02 10:44:15 UTC
*** Bug 481307 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2008-05-02 10:44:52 UTC
*** Bug 481535 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2008-07-03 13:10:14 UTC
I see only 2.10 duplicates and I guess the change here
http://svn.gnome.org/viewvc/evolution/trunk/mail/mail-session.c?r1=34873&r2=34977
fixed the issue, especially removing part
    if (m->allow_cancel && m->ismain) {
because in previous code, when have the ismain set and not the allow_cancel, then this leaded to only show the dialog, not modally, thus the 'm' was unreffed and freed in alert_user, thus on the response of the dialog we were accessing something already freed (and possible overwritten, so the allow_cancel could be !FALSE).

I guess it's kind of hard to reproduce it, though.

I'm so confident about this that I will mark as obsolete, but feel free to reopen if you'll see this in 2.22.x or later.
Comment 5 Milan Crha 2008-09-19 17:20:48 UTC
OK, have a duplicate in bug #530716 with 2.23.1. I'll keep this closed and let's look at it in that bug, with more recent sources.