Bug 430070 – crash in Evolution: I was making a new appoi...

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 430070 - crash in Evolution: I was making a new appoi...


Summary:	crash in Evolution: I was making a new appoi...


Status:	RESOLVED DUPLICATE of bug 355701

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-15 19:05 UTC by gwayland
Modified:	2007-04-15 19:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description gwayland 2007-04-15 19:05:21 UTC

What were you doing when the application crashed?
I was making a new appointment. I had unchecked All Day Event and was inputting the start time. I accidentall entered 011:00 AM and it said that it was an invalid time. I closed the error box and attempted to click the drop down arrow to just select a time, then the program crashed.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 181284864 vsize: 0 resident: 181284864 share: 0 rss: 30625792 rss_rlim: 0
CPU usage: start_time: 1176663759 rtime: 0 utime: 422 stime: 0 cutime:408 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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

(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 -1232865616 (LWP 8768)]
[New Thread -1372599392 (LWP 8809)]
[New Thread -1277789280 (LWP 8788)]
[New Thread -1344443488 (LWP 8787)]
[New Thread -1335759968 (LWP 8783)]
[New Thread -1286218848 (LWP 8782)]
[New Thread -1295004768 (LWP 8778)]
[New Thread -1269396576 (LWP 8775)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128040

Thread 1 (Thread -1232865616 (LWP 8768))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#22 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#24 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#25 bonobo_main
from /usr/lib/libbonobo-2.so.0
#26 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-15 19:59:54 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 355701 ***