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 547307 - crash in calendar_client_handle_query_completed
crash in calendar_client_handle_query_completed
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: general
2.30.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 564662 588916 589442 602721 613608 641826 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-11 15:54 UTC by barthezz
Modified: 2020-11-06 20:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description barthezz 2008-08-11 15:54:14 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 58695680 vsize: 58695680 resident: 27975680 share: 14954496 rss: 27975680 rss_rlim: 4294967295
CPU usage: start_time: 1218447476 rtime: 3711 utime: 3433 stime: 278 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6d02700 (LWP 3573)]
[New Thread 0xb59c9b90 (LWP 4130)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d02700 (LWP 3573))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.4/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.4/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 IA__g_assertion_message
  • #10 IA__g_assertion_message_expr
    at /tmp/buildd/glib2.0-2.16.4/glib/gtestutils.c line 1229
  • #11 calendar_client_handle_query_completed
    at calendar-client.c line 1232
  • #12 IA__g_cclosure_marshal_VOID__INT
    at /tmp/buildd/glib2.0-2.16.4/gobject/gmarshal.c line 216
  • #13 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.16.4/gobject/gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.16.4/gobject/gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.16.4/gobject/gsignal.c line 2199
  • #16 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.16.4/gobject/gsignal.c line 2243
  • #17 ??
    from /usr/lib/libecal-1.2.so.7
  • #18 ??
  • #19 ??
  • #20 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
(evolution:22157): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3407600 specified for 0x3407ae6 (Delete acc).
(evolution:22157): e-utils-WARNING **: can't load plugin '/usr/lib/evolution/2.22/plugins/libcom-zimbra-account-setup.so': libcares.so.2: cannot open shared object file: No such file or directory
(evolution:22157): e-utils-WARNING **: can't load plugin '/usr/lib/evolution/2.22/plugins/libcom-zimbra-account-setup.so': libcares.so.2: cannot open shared object file: No such file or directory
** (evolution:22157): WARNING **: Zimbra Account Setup
(evolution:22157): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(evolution:22157): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
commit
**
** ERROR:(calendar-client.c:1232):calendar_client_handle_query_completed: assertion failed: (source->query_in_progress != FALSE)
--------------------------------------------------
Comment 1 palfrey 2008-12-16 13:44:48 UTC
*** Bug 564662 has been marked as a duplicate of this bug. ***
Comment 2 Bruno Boaventura 2009-07-18 01:25:27 UTC
*** Bug 588916 has been marked as a duplicate of this bug. ***
Comment 3 Fabio Durán Verdugo 2009-07-23 14:14:16 UTC
*** Bug 589442 has been marked as a duplicate of this bug. ***
Comment 4 Fabio Durán Verdugo 2009-11-23 12:27:11 UTC
*** Bug 602721 has been marked as a duplicate of this bug. ***
Comment 5 Rune Schjellerup Philosof 2010-03-10 09:09:14 UTC
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/442931
has been linked to this bug.

This bug report suggests that using Evolution MAPI accounts cause the crash.

I also use an Evolution MAPI account (connection protocol to exchange servers) and has seen this crash.
Furthermore, in the calendar applet, some of the dates where I have appointments in my exchange calendar are marked with bold, but there are no further information when I select them.
So, sometimes some information manages to get through the evolution-data-server to the calendar applet, but not all, and often it causes crashes.
Comment 6 Fabio Durán Verdugo 2010-03-22 17:50:19 UTC
*** Bug 613608 has been marked as a duplicate of this bug. ***
Comment 7 Akhil Laddha 2010-12-28 05:14:56 UTC
last dupe in 2.30.x
Comment 8 Jonathan Matthew 2011-02-03 07:05:00 UTC
I'm seeing this on F14 in gnome-shell, which now includes the same calendar code.
Comment 9 Akhil Laddha 2011-02-08 12:06:11 UTC
*** Bug 641826 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2020-11-06 20:24:11 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.