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 325889 - crash on customize alarm
crash on customize alarm
Status: RESOLVED DUPLICATE of bug 325759
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-05 16:31 UTC by Pascal Fresnay
Modified: 2006-01-06 11:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Pascal Fresnay 2006-01-05 16:31:09 UTC
Distribution: Ubuntu 6.04 (dapper)
Package: Evolution
Priority: Normal
Version: GNOME2.13.4 unspecified
Gnome-Distributor: Ubuntu
Synopsis: crash on customize alarm
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.13.0)
Description:
Description of the crash:
application crash after pressing "cancel" in customize alarm dialog box

Steps to reproduce the crash:
1. Create an item in calendar
2. Click alarm in item editor
3. Check "set alarm"
4. Press "Customize"
5. Press Cancel

Expected Results:
no crash of course :)

How often does this happen?
every time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231390016 (LWP 2867)]
[New Thread -1283535952 (LWP 2914)]
[New Thread -1274877008 (LWP 2883)]
[New Thread -1265730640 (LWP 2874)]
[New Thread -1247691856 (LWP 2873)]
[New Thread -1256096848 (LWP 2871)]
[New Thread -1238869072 (LWP 2869)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1231390016 (LWP 2867))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #7 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #8 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-01-05 16:31 -------

Comment 1 André Klapper 2006-01-06 11:40:09 UTC
this is exactly the same stacktrace as bug 325797 which has been marked as a duplicate of bug 325759.

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