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 531081 - crash in Panel: Opening the calendar on ...
crash in Panel: Opening the calendar on ...
Status: RESOLVED DUPLICATE of bug 378854
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-02 15:29 UTC by barthezz
Modified: 2008-05-02 17:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description barthezz 2008-05-02 15:29:38 UTC 
Version: 2.20.3

What were you doing when the application crashed?
Opening the calendar on my desktop by clicking the date 


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 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: 50245632 vsize: 50245632 resident: 22056960 share: 13688832 rss: 22056960 rss_rlim: 4294967295
CPU usage: start_time: 1209741610 rtime: 186 utime: 160 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6db5720 (LWP 3865)]
[New Thread 0xb5d43b90 (LWP 19250)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 196691

Thread 1 (Thread 0xb6db5720 (LWP 3865))

  • #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 calendar_client_handle_query_completed
    at calendar-client.c line 1232
  • #13 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
  • #17 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (86 sec old) ---------------------
** (evolution:4116): DEBUG: mailto URL program: evolution
(evolution:4116): evolution-mail-WARNING **: couldn't get service zimbra://barthezz%40influx-gaming.com@email.influx-gaming.com/;command=ssh%20-C%20-l%20%25u%20%25h%20exec%20/usr/sbin/imapd;use_ssl=al
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
	StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
Amarok: [Loader] Amarok is taking a long time to load! Perhaps something has gone wrong?
addressbook_migrate (2.12.0)
CalDAV Eplugin starting up ...
** (evolution:19219): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:19219): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-02 17:09:14 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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