Resizing calendar items twice crashes Evolution

Bug #45033 reported by Bruce Cowan
10
Affects Status Importance Assigned to Milestone
Evolution
Invalid
Critical
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Dapper
Won't Fix
Medium
Ubuntu Desktop Bugs

Bug Description

Resizing an item twice in the calendar in Evolution causes a crash. I obtained this output from GDB :
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912630320736 (LWP 6652)]
0x00002aaaab105d07 in pvl_data () from /usr/lib/libecal-1.2.so.3

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote : Backtrace

Here is the backtrace

Revision history for this message
Adam Petaccia (mighmos) wrote :

I can confirm this bug; it is reproducable. Although sometimes it crashes after one resize, other times it takes more than two.

Changed in evolution:
status: Unconfirmed → Confirmed
Revision history for this message
Adam Petaccia (mighmos) wrote : Evolution backtrace 2.6.1-0ubuntu6

My backtrace looked like it was doing something different, although I don't know if that's due to debugging symbols or something else.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. I can't reproduce. Could you please install evolution-dbg evolution-data-server-dbg and libglib2.0-0-dbg and get another backtrace?

Changed in evolution:
assignee: nobody → desktop-bugs
status: Confirmed → Needs Info
Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

You have to resize them with the mouse, for instance the bottom part of a appoinment.

Revision history for this message
Sebastien Bacher (seb128) wrote :

how do you resize the item? what calendar view do you use? daily? weekly?

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

Daily. 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.

Revision history for this message
Adam Petaccia (mighmos) wrote : Updated backtrace

Hope this helps resolve this.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks - I added the information to http://bugzilla.gnome.org/show_bug.cgi?id=341430 which has a matching backtrace.

Changed in evolution:
status: Needs Info → Confirmed
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I can confirm. Sometime crashes at the first attempt to resizing, sometime no.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Oops. Sorry for the above silly comment. It happened to me too; but I discovered that in a freshly created user, virgin calendar it does not occur. To reproduce, I need to import a .ics file (will attach, nothing private here) from an old version of evolution. To reproduce:
Import the attached calendar.ics file
Go to 5th july.
Move the "reunión..." entry to 12:30 (with the mouse)
Try to extend the other entry "..junta"
Sometime it works. Repeat: often crashes, sometime lock solid.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote : old evolution calendar file

I can reproduce the bug after importing this file into evolution calendar.

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

I don't think this bug affects evolution 2.7.92

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Version in Dapper Drake is 2.6.1. Time to add upstream evolution to backports?

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

Apparently, Evolution 2.6.3 has been uploaded to dapper-proposed, but has not been approved yet. I am not sure if this version fixes this issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Marking as fixed according to the previous comment that states the bug probably doesn't concern edgy. Opening a dapper backport task too

Changed in evolution:
status: Confirmed → Fix Released
assignee: nobody → desktop-bugs
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

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

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

GDB backtrace (from evolution-dbg)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Right, there is a crasher on edgy too, the backtrace looks like http://bugzilla.gnome.org/show_bug.cgi?id=336555 upstream, I've mentioned that ubuntu bug on it

Changed in evolution:
status: Fix Released → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

fixed upstream

Changed in evolution:
status: Confirmed → Fix Committed
Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

This is fixed in 2.8.1.

Changed in evolution:
status: Fix Committed → Fix Released
Changed in evolution:
status: New → Invalid
Changed in evolution:
importance: Unknown → Critical
status: Invalid → Unknown
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

hmm? This has been positively fixed aged ago.

Or I do not understand the "Bug Watch Updater" update meaning?

Changed in evolution:
status: Unknown → Invalid
Rolf Leggewie (r0lf)
Changed in evolution (Ubuntu Dapper):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.