Hi all,
Le 13/02/2014 23:53, Joel Madero a écrit :
> Hi All,
>
> For those on QA mailing list it would be good to have most (or all ;) )
> install 4.2.1.1 rc and put it through the tests to try to catch any
> nasty regressions quickly. As you know, it's not for production so using
> on really impo
Hi All,
For those on QA mailing list it would be good to have most (or all ;) )
install 4.2.1.1 rc and put it through the tests to try to catch any
nasty regressions quickly. As you know, it's not for production so using
on really important things is not recommended but if at all possible,
install
2014-02-13 18:39 GMT+01:00 Kohei Yoshida :
> On Thu, 2014-02-13 at 11:33 +0100, M Henri Day wrote:
>
>
> > Kohei, any chance of a patch for Linux (in my specific case, deb)
> > users being posted in the near future, in addition to those you've
> > already posted for Windows and Mac users, respec
Hi *,
for the upcoming new version 4.2.1, the builds for rc1 are now
available on pre-releases (some windows helppacks still uploading)
Besides the usual builds, there are also 64bit builds for Mac
available for testing.
See
https://wiki.documentfoundation.org/ReleasePlan/4.2#4.2.1_release
for
On 13/02/14 18:39, Kohei Yoshida wrote:
> On Thu, 2014-02-13 at 11:33 +0100, M Henri Day wrote:
>
>
>> Kohei, any chance of a patch for Linux (in my specific case, deb)
>> users being posted in the near future, in addition to those you've
>> already posted for Windows and Mac users, respectivel
On Thu, 2014-02-13 at 11:33 +0100, M Henri Day wrote:
> Kohei, any chance of a patch for Linux (in my specific case, deb)
> users being posted in the near future, in addition to those you've
> already posted for Windows and Mac users, respectively ?...
Actually, I don't know personally. Let m
Hi Joel,
On Wed, 2014-02-12 at 22:22 -0800, Joel Madero wrote:
> Thanks Kohei for your work - I'm sure you're swamped. That being said,
> is there something QA can do to help organize for you? Or is a bug being
> marked a regression against 4.2 sufficient?
Yeah. What you guys have been doing is
Hi Bjoern,
Le 13/02/2014 17:54, Bjoern Michaelsen a écrit :
> On Thu, Feb 13, 2014 at 04:55:15PM +0100, Sophie wrote:
>> I've installed libreoffice-dbg, but the package is based on 4.1.3, and
>> if I run soffice --backtrace this version is launched, which seems correct.
>> If I run gdb /opt/libreof
On Thu, Feb 13, 2014 at 04:55:15PM +0100, Sophie wrote:
> I've installed libreoffice-dbg, but the package is based on 4.1.3, and
> if I run soffice --backtrace this version is launched, which seems correct.
> If I run gdb /opt/libreoffice4.2/program/soffice.bin, I've no symbols
> here :)
So, /opt/
Hi All,
Instead of doing a doodle right off the bat with 48 times per day (every
half hour x 24) I'm going with asking if particular days are much better
for people. Maybe we can narrow it down to a day or two and then I can
build a doodle. Else it's a headache for me and for everyone filling out
Le 13/02/2014 16:49, Bjoern Michaelsen a écrit :
> On Thu, Feb 13, 2014 at 04:29:37PM +0100, Sophie wrote:
>> Currently, the dbg packages available for Ubuntu to get backtraces are
>> based on 1.4.3.
>> If I want to get a backtrace with symbols on a crash in 4.2.0, how do I do?
>> see here for a no
On Thu, Feb 13, 2014 at 04:29:37PM +0100, Sophie wrote:
> Currently, the dbg packages available for Ubuntu to get backtraces are
> based on 1.4.3.
> If I want to get a backtrace with symbols on a crash in 4.2.0, how do I do?
> see here for a not useful backtrace I provided ;)
> https://bugs.freedes
Hi all,
Currently, the dbg packages available for Ubuntu to get backtraces are
based on 1.4.3.
If I want to get a backtrace with symbols on a crash in 4.2.0, how do I do?
see here for a not useful backtrace I provided ;)
https://bugs.freedesktop.org/attachment.cgi?id=94005
Thanks in advance
Cheers
2014-02-07 14:59 GMT+01:00 Kohei Yoshida :
> Hi there,
>
> FYI, a large number of Calc freeze problems may be attributed to the
> same root cause, which I fixed for Bug 72470
>
> https://bugs.freedesktop.org/show_bug.cgi?id=72470
>
> The problem code kicks in when you have a document that has at l
14 matches
Mail list logo
