The problem is that we do not have any information with what commit this
problem has been solved for what version
My results with server installation of "Version 4.1.0.0.alpha0+ (Build
ID: bdfd8de57bf5767ce5c179a5e8705c7587f7b32) TinderBox: Win-x86@6,
Branch:master, Pull Time: 2013-02-06_22:06:22" ENGLISH UI / German
Locale on German WIN7 Home Premium (64bit) with own separate User
Profile:
Original report crash: reproducible
Comment 10 crash: No longer reproducible (and imho very different thing)
Comment 19 crash: Still reproducible
Comment 22 crash: Still reproducible
Comment 23 crash: Still reproducible (only more precise description of
proceeding due to comment 20
I would prefer to mark this one as WFM becauss Fix is unknown, but to
avoid lots of mails because of MAB relation I will wait few days, may be
we can get commit info.
@Michael, David
Can you contribute commit information?
@tommy27
I answer for Joel: no, we should not reopen this one. This Bug report has
become rather unclear, it's unknown what has been fixed ....
If I can reproduce my results with latest Master I will report new bugs
for crashes due to Comments 19 / 22 (and may be C 10) to avoid any
"hodgepodge", please wait some moments.
@Joel:
Please cite the complete LibO/About info (it's so easy). Only the version code
is rather useless, most of us can't find out the pull time info with it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785518
Title:
[Upstream] soffice.bin crashed with SIGSEGV in SdrEndTextEdit()
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/785518/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
