On mer., 2010-06-23 at 10:27 -0400, Jerry Quinn wrote:
> And I'm reporting them upstream now too. I had to wait for 2.30 to
> enter testing before I could pick it up without breaking a bunch of
> other stuff on my system.
Once it's done, please add the forwarded tag to this bug report.
Thanks,
On Tue, 2010-06-22 at 18:28 +0200, Yves-Alexis Perez wrote:
> On 18/05/2010 08:31, Yves-Alexis Perez wrote:
> > On mar., 2010-05-18 at 02:27 -0400, Jerry Quinn wrote:
> >> Package: evolution
> >> Version: 2.28.3-1
> >> Severity: normal
> >> Tags: upstream
> >>
> >>
> >> I clicked on New Message and
On 18/05/2010 08:31, Yves-Alexis Perez wrote:
> On mar., 2010-05-18 at 02:27 -0400, Jerry Quinn wrote:
>> Package: evolution
>> Version: 2.28.3-1
>> Severity: normal
>> Tags: upstream
>>
>>
>> I clicked on New Message and got a segfault. Here's the gdb
>> backtrace:
>
> Upstream bug are to be re
On mar., 2010-05-18 at 02:27 -0400, Jerry Quinn wrote:
> Package: evolution
> Version: 2.28.3-1
> Severity: normal
> Tags: upstream
>
>
> I clicked on New Message and got a segfault. Here's the gdb
> backtrace:
Upstream bug are to be reported directly in upstream bugzilla, please.
And could y
Package: evolution
Version: 2.28.3-1
Severity: normal
Tags: upstream
I clicked on New Message and got a segfault. Here's the gdb backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffca135910 (LWP 24168)]
magazine_chain_pop_head (mem_size=16)
at /tmp/bui
5 matches
Mail list logo
