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 353809 - Clock applet crash if evolution is not installed
Clock applet crash if evolution is not installed
Status: RESOLVED DUPLICATE of bug 340622
Product: gnome-panel
Classification: Other
Component: clock
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-01 10:25 UTC by Sebastien Bacher
Modified: 2006-09-02 09:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sebastien Bacher 2006-09-01 10:25:15 UTC 
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/58428

"If evolution is not installed, when double click a day in the clock applet, gnome-panel will crash.

Steps to reproduce:
1. sudo apt-get remove evolution
2. Click the the clock applet in the panel, it will show a calendar
3. Double-click a day"

Backtrace from gnome-panel 2.15.92:

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1224538448 (LWP 5551)]
[New Thread -1254016096 (LWP 7993)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71351

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 871
  • #3 <signal handler called>
  • #4 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #5 _IO_vfprintf_internal
    from /lib/tls/i686/cmov/libc.so.6
  • #6 _IO_vasprintf
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_vasprintf
    at gprintf.c line 311
  • #8 IA__g_strdup_vprintf
    at gstrfuncs.c line 188
  • #9 IA__g_printerr
    at gmessages.c line 1008
  • #10 calendar_day_activated
    at clock.c line 1290
  • #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 2438
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #15 IA__g_signal_emit
    at gsignal.c line 2241
  • #16 gtk_calendar_button_press
    at gtkcalendar.c line 2502
  • #17 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #18 g_type_class_meta_marshal
    at gclosure.c line 567
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #22 IA__g_signal_emit
    at gsignal.c line 2241
  • #23 gtk_widget_event_internal
    at gtkwidget.c line 3901
  • #24 IA__gtk_propagate_event
    at gtkmain.c line 2210
  • #25 IA__gtk_main_do_event
    at gtkmain.c line 1444
  • #26 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #27 IA__g_main_context_dispatch
    at gmain.c line 2043
  • #28 g_main_context_iterate
    at gmain.c line 2675
  • #29 IA__g_main_loop_run
    at gmain.c line 2879
  • #30 IA__gtk_main
    at gtkmain.c line 1023
  • #31 main
    at main.c line 95 






Comment 1


Sebastien Bacher





          2006-09-02 09:32:31 UTC
        



likely to be the same issue than bug #340622, marking as duplicated

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