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 524139 - crash in Panel: Changing a calendar entr...
crash in Panel: Changing a calendar entr...
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-03-24 15:09 UTC by Armando Di Cianno
Modified: 2008-03-25 12:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Armando Di Cianno 2008-03-24 15:09:50 UTC 
Version: 2.20.3

What were you doing when the application crashed?
Changing a calendar entry's recurrence.


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.20.3 2008-03-22 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-gentoo-r3-adc0 #1 SMP PREEMPT Wed Feb 27 13:22:56 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Nerdy-Lines

Memory status: size: 121319424 vsize: 121319424 resident: 42885120 share: 18587648 rss: 42885120 rss_rlim: 4294967295
CPU usage: start_time: 1206279502 rtime: 11276 utime: 10270 stime: 1006 cutime:0 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb63c66e0 (LWP 32277)]
[New Thread 0xb43cdb90 (LWP 1585)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 193214

Thread 1 (Thread 0xb63c66e0 (LWP 32277))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 IA__g_slist_remove
    at gslist.c line 207
  • #10 backend_died_cb
    at calendar-sources.c line 432
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 490
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #15 IA__g_signal_emit
    at gsignal.c line 2243
  • #16 backend_died_cb
    at e-cal.c line 428
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 connection_listen_cb
    at e-component-listener.c line 50
  • #23 link_connection_emit_broken
    at linc-connection.c line 146
  • #24 link_connection_broken_idle
    at linc-connection.c line 167
  • #25 g_idle_dispatch
    at gmain.c line 4132
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #27 g_main_context_iterate
    at gmain.c line 2694
  • #28 IA__g_main_loop_run
    at gmain.c line 2898
  • #29 IA__gtk_main
    at gtkmain.c line 1163
  • #30 main
    at main.c line 95
  • #0 __kernel_vsyscall 


----------- .xsession-errors (52420 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-03-25 12:53:26 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 378854 ***