Bug 526504 – crash in Panel:

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 526504 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 453173

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-04-06 14:02 UTC by barthezz
Modified:	2008-04-06 14:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description barthezz 2008-04-06 14:02:23 UTC

Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 51109888 vsize: 51109888 resident: 17768448 share: 11329536 rss: 17768448 rss_rlim: 4294967295
CPU usage: start_time: 1207487863 rtime: 594 utime: 514 stime: 80 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e86720 (LWP 3808)]
[New Thread 0xb5e0cb90 (LWP 6321)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 194387

Thread 1 (Thread 0xb6e86720 (LWP 3808))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#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 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#12 ??
from /usr/lib/gnome-panel/libclock-applet.so
#13 ??
#0 __kernel_vsyscall



----------- .xsession-errors (10 sec old) ---------------------
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
CalDAV Eplugin starting up ...
INFO   6137   Sun Apr  6 15:54:51 2008 glog.c(461):glog_add_log_function appended log function 0xb6373fe0 (user data (nil)) to log functions
DEBUG  6137   Sun Apr  6 15:54:51 2008 glog.c(189):glog_init glog was initialized.
LOG    6137   Sun Apr  6 15:54:51 2008 glog.c(165):glog_init glog has already been initialized, just bumping refcount.
** (evolution:6137): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6137): DEBUG: mailto URL program: evolution
get barthezz@influx-gaming.com zimbra://barthezz%40influx-gaming.com@email.influx-gaming.com/
Find Items 0
get barthezz@influx-gaming.com zimbra://barthezz%40influx-gaming.com@email.influx-gaming.com:80/10
Find Items 0
** ERROR **: file calendar-client.c: line 1232 (calendar_client_handle_query_completed): assertion failed: (source->query_in_progress != FALSE)
aborting...
--------------------------------------------------

Comment 1 Philip Withnall 2008-04-06 14:41:10 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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