https://bugs.documentfoundation.org/show_bug.cgi?id=95957
QA Administrators changed:
What|Removed |Added
Resolution|--- |INSUFFICIENTDATA
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #33 from QA Administrators ---
Dear Thomas Schweikle,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #32 from QA Administrators ---
Dear Thomas Schweikle,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED.
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Julien Nabet changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #31 from
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Julien Nabet changed:
What|Removed |Added
CC||serval2...@yahoo.fr
--- Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #29 from QA Administrators ---
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Buovjaga changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #27 from Keith Refson ---
Adi - your symptoms seem different and point to a different bug.
I see the same behaviour first reported, namely, LO will start up without any
file. However any attempt to open a
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #26 from Adi Meyerhofer ---
(In reply to Keith Refson from comment #25)
> Sorry about the delay with this. I was not yet able to get debugging symbol
> information.
>
> However I have managed to narrow
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #25 from Keith Refson ---
Sorry about the delay with this. I was not yet able to get debugging symbol
information.
However I have managed to narrow down the cause a lot further, after recovering
the
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #24 from Keith Refson ---
Created attachment 127999
--> https://bugs.documentfoundation.org/attachment.cgi?id=127999=edit
Python site-package which causes LO to fail
--
You are receiving this mail
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #23 from robin.r...@kit.edu ---
The same error message occured for me on OpenSUSE Leap 42.1. After search
around and realizing that a freshly created useraccount didn't have this
problem it turned out to be caused by a set env
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #22 from Adi Meyerhofer ---
(In reply to Buovjaga from comment #21)
> Keith: I chatted with Michael on IRC about getting debuginfo for openSUSE
> and he said: "you have to add the debuginfo repository and
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #21 from Buovjaga ---
Keith: I chatted with Michael on IRC about getting debuginfo for openSUSE and
he said: "you have to add the debuginfo repository and the updates repository
too for some reason"
I
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #20 from Michael Meeks ---
Extremely interesting analysis - thanks ! =)
The valgrind trace is unfortunately not useful, since the build has no
debuginfo installed - which is a shame ! thanks for
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Buovjaga changed:
What|Removed |Added
Attachment #127276|text/x-log |text/plain
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #19 from Keith Refson ---
I found this bug report when investigating near identical symptoms with LO
5.1.3
under OpenSuse Leap 42.1
Linux PHTCM1001 4.1.27-27-default #1 SMP PREEMPT Fri Jul 15 12:46:41 UTC
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Keith Refson changed:
What|Removed |Added
CC|
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Michael Meeks changed:
What|Removed |Added
Status|UNCONFIRMED
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #16 from Pierre C ---
I've the same crash with LO 5.1.2 So, back to 4.4.7.2
Pb occurs only with writer, when working with au document. I can't reproduce
way to the crash.
I Just noticed, th the
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #15 from Adi Meyerhofer ---
Patch https://www.suse.com/support/update/announcement/2016/suse-ru-20160333-1.html;>SUSE-RU-2016:0333-1
(References: #679938 #889755 #939996 #945047 #951579 #954345 #9),
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #14 from jbernon ---
Hello,
Same problem using Libreoffice 5.0.4.2 with Debian 8.3 and Gnome 3.14 Many odt
files cannot be fully opened : loop of recovery tries, then file opening is
immediately followed by
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #13 from Beluga ---
Adi: ok, I guess you will file a report to KDE's bug tracker.
Thomas is probably using Ubuntu with Unity and not KDE..?
--
You are receiving this mail because:
You are the assignee
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #12 from Adi Meyerhofer ---
By now, after having used Suse Leap with the Qt5/Plasma desktop for about a
week I strongly suspect that the root of the problem is in Plasma/KDEFrameworks
or whatever else is
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #11 from Thomas Schweikle ---
Same for 5.1rc1
--
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #10 from Adi Meyerhofer ---
Persists with 5.0.4.2 installed from the suse-Tumbleweed Repo.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #9 from Beluga ---
Ah, now I linked to pre-releases even though 5.0.4 is stable.. well, test with
5.1 RC1 while you're at it :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #8 from Beluga ---
To all: you could also verify that the crash is present on 5.0.4
https://wiki.documentfoundation.org/Installing_in_parallel/Linux
http://www.libreoffice.org/download/pre-releases/
--
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Adi Meyerhofer changed:
What|Removed |Added
CC|
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
--- Comment #6 from Beluga ---
Comments from IRC #libreoffice-dev:
std::bad_alloc is an out of memory exception
the backtrace does not show a std::bad_alloc, it looks like a SIGSEGV in the
sidebar code while
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Thomas Schweikle changed:
What|Removed |Added
Assignee|t...@vr-web.de
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Thomas Schweikle changed:
What|Removed |Added
Status|NEEDINFO|UNCONFIRMED
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Beluga changed:
What|Removed |Added
Keywords||have-backtrace
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Beluga changed:
What|Removed |Added
Attachment #121465|text/x-log |text/plain
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
tommy27 changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
Beluga changed:
What|Removed |Added
CC|
https://bugs.documentfoundation.org/show_bug.cgi?id=95957
raal changed:
What|Removed |Added
CC||r...@post.cz
--- Comment #1
37 matches
Mail list logo