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 714533 - [norepro] ReplayQueue assertion
[norepro] ReplayQueue assertion
Status: RESOLVED INVALID
Product: geary
Classification: Other
Component: engine
unspecified
Other All
: High normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
: 713541 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-03-13 09:45 UTC by Eric Gregory
Modified: 2019-03-31 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:28:29 UTC


---- Reported by eric@yorba.org 2013-03-13 14:45:00 -0700 ----

Original Redmine bug id: 6535
Original URL: http://redmine.yorba.org/issues/6535
Searchable id: yorba-bug-6535
Original author: Eric Gregory
Original description:

I started up my Precise VM and ran Geary. After a few minutes, the following
appeared twice on the console:

    
    
    ** (geary:4534): CRITICAL **: geary_imap_engine_replay_queue_schedule: assertion `GEARY_IMAP_ENGINE_IS_REPLAY_QUEUE (self)' failed
    

Unfortunately I wasn't running with a debugger at the time so I don't have a
backtrace.



---- Additional Comments From geary-maint@gnome.bugs 2013-05-15 14:30:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 8 months ago

  * **Category** set to _engine_

####

#2

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.3.0_ to _0.4.0_

####

#3

Updated by Jim Nelson 6 months ago

  * **Subject** changed from _ReplayQueue assertion_ to _[norepro] ReplayQueue assertion_

####

#4

Updated by Jim Nelson 6 months ago

  * **Target version** deleted (<strike>_0.4.0_</strike>)



--- Bug imported by chaz@yorba.org 2013-11-21 20:28 UTC  ---

This bug was previously known as _bug_ 6535 at http://redmine.yorba.org/show_bug.cgi?id=6535

Unknown version " in product geary. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Charles Lindsay 2014-01-30 22:58:45 UTC
*** Bug 713541 has been marked as a duplicate of this bug. ***
Comment 2 Charles Lindsay 2014-01-30 23:01:54 UTC
This just happened to me again.  See my first stack trace in bug #714533.  Here's the stack trace now:

  • #0 g_logv
    at /build/buildd/glib2.0-2.38.1/./glib/gmessages.c line 989
  • #1 g_log
    at /build/buildd/glib2.0-2.38.1/./glib/gmessages.c line 1025
  • #2 g_return_if_fail_warning
  • #3 geary_imap_engine_replay_queue_schedule
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-replay-queue.vala line 143
  • #4 geary_imap_engine_generic_folder_do_list_email_by_id_async_co
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-generic-folder.vala line 1034
  • #5 geary_imap_engine_generic_folder_do_list_email_by_id_async
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-generic-folder.vala line 7
  • #6 geary_imap_engine_generic_folder_real_list_email_by_id_async_co
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-generic-folder.vala line 993
  • #7 geary_imap_engine_email_flag_watcher_do_flag_watch_async_co
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-email-flag-watcher.vala line 117
  • #8 geary_imap_engine_email_flag_watcher_do_flag_watch_async
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-email-flag-watcher.vala line 17
  • #9 geary_imap_engine_email_flag_watcher_flag_watch_async_co
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-email-flag-watcher.vala line 100
  • #10 geary_imap_engine_email_flag_watcher_flag_watch_async
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-email-flag-watcher.vala line 17
  • #11 geary_imap_engine_email_flag_watcher_on_flag_watch
    at /home/chaz/devel/geary-stable/src/engine/imap-engine/imap-engine-email-flag-watcher.vala line 88
  • #12 _geary_imap_engine_email_flag_watcher_on_flag_watch_gsource_func
    at imap-engine-email-flag-watcher.c line 824
  • #13 g_timeout_dispatch
    at /build/buildd/glib2.0-2.38.1/./glib/gmain.c line 4450
  • #14 g_main_dispatch
    at /build/buildd/glib2.0-2.38.1/./glib/gmain.c line 3065
  • #15 g_main_context_dispatch
    at /build/buildd/glib2.0-2.38.1/./glib/gmain.c line 3641
  • #16 g_main_context_iterate
    at /build/buildd/glib2.0-2.38.1/./glib/gmain.c line 3712
  • #17 g_main_context_iteration
    at /build/buildd/glib2.0-2.38.1/./glib/gmain.c line 3773
  • #18 g_application_run
    at /build/buildd/glib2.0-2.38.1/./gio/gapplication.c line 1635
  • #19 _vala_main
    at /home/chaz/devel/geary-stable/src/client/application/main.vala line 10
  • #20 __libc_start_main
    at libc-start.c line 260
  • #21 _start

Comment 3 Michael Gratton 2019-03-31 14:09:08 UTC
I don't think I've ever seen this, and the code around those parts has changed o much the stack isn't any help any more. :(