Your message dated Sun, 17 Jan 2010 20:02:10 +0100
with message-id <[email protected]>
and subject line Bug#367974: fixed in evolution 2.26.1.1-1: Segmentation fault 
when appointment lengthened
has caused the Debian Bug report #367974,
regarding Segmentation fault when appointment lengthened
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
367974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367974
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: evolution
Version: 2.6.1-2

When I extend an appointment by dragging its lower limit down, then
choose to apply the change to all instances of it, Evolution has a
segmentation fault.  Here's the backtrace:

> #0  0x0d820de8 in e_calendar_view_get_tooltips () from 
> /usr/lib/evolution/2.6/components/libevolution-calendar.so
> #1  0x0ddefeb4 in g_main_context_is_owner () from /usr/lib/libglib-2.0.so.0
> #2  0x0dded5a4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #3  0x0ddf199c in g_main_context_check () from /usr/lib/libglib-2.0.so.0
> #4  0x0ddf1df4 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> #5  0x0eeb17d4 in bonobo_main () from /usr/lib/libbonobo-2.so.0
> #6  0x1001846c in main ()

This appears to be the same bug as

 http://bugzilla.gnome.org/show_bug.cgi?id=333224

-- 
Matt

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 2.26.1.1-1

On Mon, Jan 12, 2009 at 09:31:05PM +0000, 
[email protected] wrote:
> # remote status report for #367974
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=333224
> #  * remote status changed: ASSIGNED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 367974 + fixed-upstream
> usertags 367974 - status-ASSIGNED
> usertags 367974 + status-RESOLVED resolution-FIXED

Upstream bugzilla and git say this bug has been fixed in commit
4d269fdc404863e16f62de4f301d7aca29f69f06 and released first in EVOLUTION_2_25_3

If unfortunately, you still experience this bug, please reopen it using 'found
bugnumber version' in the syntax to [email protected]:
http://www.debian.org/Bugs/server-control#found

-- 
Simon Paillard


--- End Message ---
_______________________________________________
Pkg-evolution-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-evolution-maintainers

Reply via email to