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 341430 - crash when directly entering new appointment in day view
crash when directly entering new appointment in day view
Status: RESOLVED DUPLICATE of bug 333224
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-05-11 15:28 UTC by André Klapper
Modified: 2008-12-09 18:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description André Klapper 2006-05-11 15:28:44 UTC
go to day view. click on one time division (which already contains another event) so it gets marked. try to enter text. evo crashes.

this is NOT always reproducible (now when i try this, it works), perhaps it's only the slowness of cairo that some people reported? (at least rendering does not take so long here, but i also see that problem now...)

also, two double-click on that time division to get a "real" appointment editor window did not work. nothing happened. but i also cannot reproduce that right now. :-/

(cvs head checkout from today; haven't built the entire desktop though, only evolution-data-server > gail > libgnomecups > libgnomeprint > libgnomeprintui > gtkhtml > evolution)


$:andre\> gdb /opt/evo-cvs/bin/evolution-2.8
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /opt/evo-cvs/bin/evolution-2.8
[Thread debugging using libthread_db enabled]
[New Thread 1100825504 (LWP 8042)]
CalDAV Eplugin starting up ...

(evolution-2.8:8042): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[New Thread 1109814192 (LWP 8078)]
[New Thread 1111915440 (LWP 8079)]
[New Thread 1114016688 (LWP 8080)]
[New Thread 1117785008 (LWP 8081)]
[New Thread 1119886256 (LWP 8082)]
[New Thread 1121987504 (LWP 8083)]
[New Thread 1126190000 (LWP 8085)]
[New Thread 1124088752 (LWP 8084)]
[Thread 1111915440 (LWP 8079) exited]
[Thread 1117785008 (LWP 8081) exited]
[New Thread 1117785008 (LWP 8086)]
[Thread 1124088752 (LWP 8084) exited]
[Thread 1126190000 (LWP 8085) exited]
[New Thread 1126190000 (LWP 8087)]
[New Thread 1124088752 (LWP 8088)]
[New Thread 1128291248 (LWP 8089)]
[Thread 1117785008 (LWP 8086) exited]
[New Thread 1111915440 (LWP 8090)]
[Thread 1111915440 (LWP 8090) exited]
[Thread 1124088752 (LWP 8088) exited]
[Thread 1126190000 (LWP 8087) exited]
[Thread 1128291248 (LWP 8089) exited]
[New Thread 1128291248 (LWP 8091)]
[Thread 1128291248 (LWP 8091) exited]
[New Thread 1128291248 (LWP 8093)]
[New Thread 1126190000 (LWP 8092)]
[Thread 1128291248 (LWP 8093) exited]

(evolution-2.8:8042): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution-2.8:8042): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed

(evolution-2.8:8042): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution-2.8:8042): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed

(evolution-2.8:8042): Gtk-WARNING **: Attempting to add a widget with type GtkLabel to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkAlignment

(evolution-2.8:8042): Gtk-WARNING **: Attempting to add a widget with type GtkLabel to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkAlignment

[New Thread 1128291248 (LWP 8150)]

** (evolution-2.8:8042): WARNING **: could not get system bus: Failed to connect to socket /tmp/dbus-jcFEIAq5UY: Verbindungsaufbau abgelehnt


(evolution-2.8:8042): Gtk-WARNING **: Attempting to add a widget with type GtkLabel to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkAlignment

(evolution-2.8:8042): Gtk-WARNING **: Attempting to add a widget with type GtkLabel to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkAlignment
[New Thread 1131666352 (LWP 8232)]
[New Thread 1111915440 (LWP 8235)]
[New Thread 1124088752 (LWP 8236)]
[New Thread 1117785008 (LWP 8237)]
[New Thread 1133767600 (LWP 8238)]
[New Thread 1135868848 (LWP 8239)]
[New Thread 1137970096 (LWP 8240)]
[New Thread 1140071344 (LWP 8241)]
[Thread 1137970096 (LWP 8240) exited]
[Thread 1117785008 (LWP 8237) exited]
[Thread 1140071344 (LWP 8241) exited]

(evolution-2.8:8042): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `window->group == window_group' failed
[Thread 1111915440 (LWP 8235) exited]
[Thread 1124088752 (LWP 8236) exited]
[Thread 1133767600 (LWP 8238) exited]
[Thread 1135868848 (LWP 8239) exited]

(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window

[New Thread 1135868848 (LWP 8252)]
[Thread 1135868848 (LWP 8252) exited]
[New Thread 1135868848 (LWP 8263)]
calendar selection changed
[Thread 1135868848 (LWP 8263) exited]

(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window


(evolution-2.8:8042): calendar-gui-WARNING **: Couldn't find event window

[New Thread 1135868848 (LWP 8265)]
[Thread 1135868848 (LWP 8265) exited]
[New Thread 1135868848 (LWP 8267)]
calendar selection changed
calendar selection changed
[Thread 1135868848 (LWP 8267) exited]
calendar-gui-Message: Check if default client matches (1085492911.2187.24@embrace 1091364673.1412.4@embrace)
[New Thread 1135868848 (LWP 8280)]
[New Thread 1133767600 (LWP 8281)]
[New Thread 1124088752 (LWP 8282)]
[Thread 1133767600 (LWP 8281) exited]
[Thread 1124088752 (LWP 8282) exited]
calendar-gui-Message: Check if default client matches (1091364673.1412.4@embrace 1098457772.1683.0@embrace)
[New Thread 1124088752 (LWP 8283)]
[New Thread 1133767600 (LWP 8284)]
[Thread 1124088752 (LWP 8283) exited]
[Thread 1133767600 (LWP 8284) exited]
calendar-gui-Message: Check if default client matches (1098457772.1683.0@embrace 1103720156.4298.6@embrace)
[New Thread 1133767600 (LWP 8285)]
[New Thread 1124088752 (LWP 8286)]
[Thread 1133767600 (LWP 8285) exited]
[Thread 1124088752 (LWP 8286) exited]
calendar-gui-Message: Check if default client matches (1103720156.4298.6@embrace 1112784986.4129.46@embrace)
[New Thread 1124088752 (LWP 8287)]
[New Thread 1133767600 (LWP 8288)]
[Thread 1124088752 (LWP 8287) exited]
[Thread 1133767600 (LWP 8288) exited]
[Thread 1135868848 (LWP 8280) exited]
calendar-gui-Message: Check if default client matches (1112784986.4129.46@embrace 1133264502.28445.1@embrace)
[New Thread 1135868848 (LWP 8291)]
[New Thread 1133767600 (LWP 8294)]
[New Thread 1124088752 (LWP 8295)]
[New Thread 1111915440 (LWP 8296)]
[Thread 1111915440 (LWP 8296) exited]
[Thread 1133767600 (LWP 8294) exited]
[Thread 1135868848 (LWP 8291) exited]
[Thread 1124088752 (LWP 8295) exited]
calendar-gui-Message: Check if default client matches (1133264502.28445.1@embrace 1085492911.2187.27@embrace)
[New Thread 1135868848 (LWP 8300)]
[New Thread 1124088752 (LWP 8301)]
[New Thread 1133767600 (LWP 8302)]
[Thread 1124088752 (LWP 8301) exited]
[Thread 1133767600 (LWP 8302) exited]
[Thread 1135868848 (LWP 8300) exited]
calendar selection changed
calendar selection changed
[New Thread 1135868848 (LWP 8313)]
[Thread 1135868848 (LWP 8313) exited]
[New Thread 1135868848 (LWP 8315)]
[Thread 1135868848 (LWP 8315) exited]
[New Thread 1135868848 (LWP 8335)]
[Thread 1135868848 (LWP 8335) exited]
[New Thread 1135868848 (LWP 8391)]
[Thread 1135868848 (LWP 8391) exited]
[New Thread 1135868848 (LWP 8438)]
[New Thread 1133767600 (LWP 8439)]
[New Thread 1124088752 (LWP 8440)]
[Thread 1135868848 (LWP 8438) exited]
[Thread 1133767600 (LWP 8439) exited]
[Thread 1124088752 (LWP 8440) exited]
[New Thread 1124088752 (LWP 8454)]
[Thread 1124088752 (LWP 8454) exited]
[New Thread 1124088752 (LWP 8456)]
[New Thread 1133767600 (LWP 8457)]
calendar selection changed
calendar selection changed
[Thread 1124088752 (LWP 8456) exited]
[Thread 1133767600 (LWP 8457) exited]
[New Thread 1133767600 (LWP 8467)]
[Thread 1133767600 (LWP 8467) exited]
[New Thread 1133767600 (LWP 8468)]
[Thread 1133767600 (LWP 8468) exited]
[New Thread 1133767600 (LWP 8479)]
[New Thread 1124088752 (LWP 8480)]
[Thread 1133767600 (LWP 8479) exited]
[Thread 1124088752 (LWP 8480) exited]
[New Thread 1124088752 (LWP 8509)]
[New Thread 1133767600 (LWP 8510)]
[Thread 1124088752 (LWP 8509) exited]
[Thread 1133767600 (LWP 8510) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1100825504 (LWP 8042)]
0x40446377 in e_cal_get_timezone (ecal=0x417ef000, tzid=0x9e93130 "/softwarestudio.org/Olson_20011030_5/Europe/Berlin",
    zone=0xbfffe9b0, error=0x0) at e-cal.c:4692
4692            e_return_error_if_fail (ecal && E_IS_CAL (ecal), E_CALENDAR_STATUS_INVALID_ARG);
(gdb) thread apply all bt

Thread 1 (Thread 1100825504 (LWP 8042))

  • #0 e_cal_get_timezone
    at e-cal.c line 4692
  • #1 e_calendar_view_get_tooltips
    at e-calendar-view.c line 2218
  • #2 g_timeout_dispatch
    at gmain.c line 3292
  • #3 g_main_dispatch
    at gmain.c line 1916
  • #4 IA__g_main_context_dispatch
    at gmain.c line 2466
  • #5 g_main_context_iterate
    at gmain.c line 2547
  • #6 IA__g_main_loop_run
    at gmain.c line 2751
  • #7 bonobo_main
    at bonobo-main.c line 311
  • #8 main
    at main.c line 614

Comment 1 Daniel Holbach 2006-05-18 18:50:24 UTC
https://launchpad.net/distros/ubuntu/+source/evolution/+bug/45033 with followig use case

Resizing an item twice in the calendar in Evolution causes a crash. You have to resize them with the mouse, for instance the bottom part of a appoinment. Daily view. You just click and drag either the top or the bottom of an item. In my experience, you have to do this twice to cause a crash.


has this backtrace to it: 

GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run[K[K[Kset pagination 0
(gdb) run
Starting program: /usr/bin/evolution-2.6 
[Thread debugging using libthread_db enabled]
[New Thread 46912630341216 (LWP 18334)]
CalDAV Eplugin starting up ...
[New Thread 1075841376 (LWP 18341)]
[New Thread 1077942624 (LWP 18342)]
[New Thread 1080043872 (LWP 18343)]
[Thread 1080043872 (LWP 18343) exited]
[New Thread 1080043872 (LWP 18344)]
[Thread 1077942624 (LWP 18342) exited]
[New Thread 1077942624 (LWP 18345)]
[New Thread 1082145120 (LWP 18347)]
[New Thread 1084246368 (LWP 18348)]
[New Thread 1084512608 (LWP 18350)]
[New Thread 1086613856 (LWP 18356)]
[New Thread 1088715104 (LWP 18357)]
[New Thread 1090816352 (LWP 18358)]
[New Thread 1092917600 (LWP 18362)]
[New Thread 1095018848 (LWP 18363)]
[Thread 1090816352 (LWP 18358) exited]
[New Thread 1090816352 (LWP 18365)]
[Thread 1095018848 (LWP 18363) exited]
[New Thread 1095018848 (LWP 18369)]
[Thread 1090816352 (LWP 18365) exited]
[New Thread 1090816352 (LWP 18370)]
[Thread 1095018848 (LWP 18369) exited]
[Thread 1090816352 (LWP 18370) exited]
[New Thread 1090816352 (LWP 18371)]
[New Thread 1095018848 (LWP 18372)]
[New Thread 1097120096 (LWP 18373)]
[Thread 1090816352 (LWP 18371) exited]
[Thread 1095018848 (LWP 18372) exited]
[Thread 1097120096 (LWP 18373) exited]
[Thread 1086613856 (LWP 18356) exited]
[Thread 1088715104 (LWP 18357) exited]
[Thread 1092917600 (LWP 18362) exited]
[New Thread 1092917600 (LWP 18376)]
[New Thread 1088715104 (LWP 18377)]
[Thread 1088715104 (LWP 18377) exited]
[Thread 1092917600 (LWP 18376) exited]
[New Thread 1092917600 (LWP 18380)]
[Thread 1092917600 (LWP 18380) exited]
[New Thread 1092917600 (LWP 18382)]
[New Thread 1088715104 (LWP 18383)]
[Thread 1092917600 (LWP 18382) exited]
[Thread 1088715104 (LWP 18383) exited]
[New Thread 1088715104 (LWP 18387)]
[Thread 1088715104 (LWP 18387) exited]
[New Thread 1088715104 (LWP 18390)]
[Thread 1088715104 (LWP 18390) exited]
[New Thread 1088715104 (LWP 18392)]
[Thread 1088715104 (LWP 18392) exited]
[New Thread 1088715104 (LWP 18394)]
[Thread 1088715104 (LWP 18394) exited]
[New Thread 1088715104 (LWP 18397)]
[Thread 1088715104 (LWP 18397) exited]
[New Thread 1088715104 (LWP 18399)]
[Thread 1088715104 (LWP 18399) exited]
[New Thread 1088715104 (LWP 18402)]
[Thread 1088715104 (LWP 18402) exited]
[New Thread 1088715104 (LWP 18404)]
[Thread 1088715104 (LWP 18404) exited]
[New Thread 1088715104 (LWP 18409)]
[Thread 1088715104 (LWP 18409) exited]
[New Thread 1088715104 (LWP 18411)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912630341216 (LWP 18334)]
0x00002aaab4395c29 in e_calendar_view_get_tooltips (data=0x12b1280) at e-calendar-view.c:1991
	in e-calendar-view.c
(gdb) thread apply all backtrace

Thread 1 (Thread 46912630341216 (LWP 18334))

  • #0 e_calendar_view_get_tooltips
    at e-calendar-view.c line 1991
  • #1 g_timeout_dispatch
    at gmain.c line 3292
  • #2 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #3 g_main_context_iterate
    at gmain.c line 2547
  • #4 IA__g_main_loop_run
    at gmain.c line 2751
  • #5 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #6 main
    at main.c line 612
  • #0 e_calendar_view_get_tooltips
    at e-calendar-view.c line 1991
  • #1 g_timeout_dispatch
    at gmain.c line 3292
  • #2 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #3 g_main_context_iterate
    at gmain.c line 2547
  • #4 IA__g_main_loop_run
    at gmain.c line 2751
  • #5 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #6 main
    at main.c line 612

Comment 2 Niels Hamaker 2006-06-30 13:24:27 UTC
I'm having this same problemn in evolution 2.6.1 and 2.6.2. Just confirming.
If anything is wanted of me, please ask, with some details about what I should do.
Comment 3 André Klapper 2006-06-30 20:33:22 UTC
niels: do you get the same stacktrace?
i'm currently running the unstable developer version 2.7.3 and havent seen it for a long time.
Comment 4 Sebastien Bacher 2006-09-19 20:22:56 UTC
The Ubuntu bug submitter wrote: "I don't think this bug affects evolution 2.7.92"

Maybe that bug should be marked as fixed?
Comment 5 Bruce Cowan 2006-09-19 21:03:01 UTC
I assume this is reference to https://launchpad.net/distros/ubuntu/+source/evolution/+bug/45033
I was the submitter there, and it seems to be fixed in 2.16.0 anyway.
Comment 6 Sebastien Bacher 2006-09-20 10:06:01 UTC
other comment from the ubuntu bug:

"In fact it is now slightly different in Edgy. If I move the end of an appointment, and then move the beginning of it, it crashes:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47125332364160 (LWP 8437)]
0x00002adc3a41532c in e_calendar_view_get_tooltips ()
   from /usr/lib/evolution/2.8/components/libevolution-calendar.so"

looks similar to bug #336555
Comment 7 Bruce Cowan 2007-10-14 17:14:09 UTC
This could be closed surely, it is no longer an issue.
Comment 8 Matthew Barnes 2008-03-11 00:26:29 UTC
Bumping version to a stable release.
Comment 9 Milan Crha 2008-07-04 12:36:34 UTC
The trace from comment #1 belongs probably to bug #333224. The first backtrace is different, though.
Comment 10 Milan Crha 2008-12-09 18:26:55 UTC
I'm really not 100% sure, but I'll close this as a duplicate anyway. Maybe I'm wrong, thus feel free to reopen.

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