Yes, we can close it.
If I ever find the reason why, or it happens again, I will simply reopen and
post updates.
Thanks for your patience and work on Libreoffice in Debian, Rene.
Regards,
Witold
On Fri, 4 Dec 2020 at 08:13, wrote:
>
> Hi,
>
> Am 4. Dezember 2020 04:25:42 MEZ schrieb Witold B
Hi,
Am 4. Dezember 2020 04:25:42 MEZ schrieb Witold Baryluk
:
>Hi Rene and others,
>
>Libreoffice started working again for me, no more segfaults or apparmor
>issues.
>
>I can't reproduce the original issue anymore.
>
>linux-image-5.9.0-3-amd64 5.9.9-1
>libreoffice 1:7.0.3-4+b1
>apparmor 2.13.5-1
Hi Rene and others,
Libreoffice started working again for me, no more segfaults or apparmor issues.
I can't reproduce the original issue anymore.
linux-image-5.9.0-3-amd64 5.9.9-1
libreoffice 1:7.0.3-4+b1
apparmor 2.13.5-1+b1
Thanks,
Witold
Ok. Good to know.
I will try to construct more exact instructions with stable reproduction method.
Thanks Rene, for testing.
On Tue, 3 Nov 2020 at 05:52, Rene Engelhard wrote:
>
> Hi,
>
> Am 03.11.20 um 06:35 schrieb Rene Engelhard:
> >> As for reproduction, I believe the easiest is to grab the
Hi,
Am 2. November 2020 17:59:04 MEZ schrieb Rene Engelhard :
>Hmm, no, works here. (pure sid chroot + apt install libreoffice
For avoidance of doubt: yes, also apt install libreoffice-l10n-* and
libreoffice-help-* of course
> + apt
>install mythes
And mythes-* here of course.
Regards,
Rene
Hi,
Am 03.11.20 um 06:35 schrieb Rene Engelhard:
>> As for reproduction, I believe the easiest is to grab the Debian live
>> CD image and run it in qemu -kvm, and it will reproduce. It does for
>> me. If you can't, please let me know.
> Ah, Live?
>
> Does it only happen in Live and not in "real" s
Hi,
Am 02.11.20 um 23:30 schrieb Witold Baryluk:
> I did provide stack traces for example in February 2019.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921178
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940914
True, after which I said I simply can't reproduce it.
> There was ze
I did provide stack traces for example in February 2019.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921178
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940914
There was zero response from the maintainer, i.e. what other
information is required.
I am attaching a new stack trace to thi
Hi,
to answer myself:
Am 02.11.20 um 12:14 schrieb r...@rene-engelhard.de:
> Am 2. November 2020 10:23:49 MEZ schrieb Witold Baryluk
> :
>> I wasn't able to use libreoffice for almost 2 years on Debian, on
>> multiple machines.
> Then you should have provided needed info in those 2 years? It's n
Am 2. November 2020 10:23:49 MEZ schrieb Witold Baryluk
:
>I wasn't able to use libreoffice for almost 2 years on Debian, on
>multiple machines.
Then you should have provided needed info in those 2 years? It's not tagged
unreproducible, moreinfo just for fun. ;-)
Most people do not have your pr
Package: libreoffice
Version: 1:7.0.3-3
Followup-For: Bug #940914
X-Debbugs-Cc: witold.bary...@gmail.com
Still broken in 7.0.3.
I wasn't able to use libreoffice for almost 2 years on Debian, on
multiple machines.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
Package: libreoffice
Version: 1:6.4.2-2
Followup-For: Bug #940914
Dear Maintainer,
Any progress on this?
I am getting same issues with libreoffice 1:6.4.0~rc2-1 from sid.
(I know of apparmor workaround).
Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
Package: libreoffice
Version: 1:6.3.2-1+b1
Followup-For: Bug #940914
Same issue here:
Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
cppu::_copyConstructAnyFromData (mapping=0x0, acquire=0x7f42d3ba1eb0
, pTypeDescr=,
pType=, pSource=0x7ffe7c59db60, pDestAny=0x562e0b85a478)
Processing commands for cont...@bugs.debian.org:
> # merging this bug with 921178
> severity 940914 important
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
cppu::_copyConstructAnyFromData
Severity set to 'important' from 'grave'
> reassign 940914 libreoffice
Bug #940914 [uno-libs3] uno
# merging this bug with 921178
severity 940914 important
reassign 940914 libreoffice
found 940914 1:6.1.5-3+deb10u4
forcemerge 940914 921178
thanks
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
> 0x7f78d70
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> -- System Information:
> Debian Release: 10.1
> APT prefers stable-debug
> APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
> 'stable')
Just to see whether it had an affect I upgraded to proposed-updat
tag 940914 + moreinfo
tag 940914 + unreproducible
thanks
Hi,
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> Package: uno-libs3
> Version: 6.1.5-3+deb10u4
> Severity: grave
Why?
> Justification: renders package unusable
If this was true, yes.
Unfortunately
a) this version
Processing commands for cont...@bugs.debian.org:
> tag 940914 + moreinfo
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
cppu::_copyConstructAnyFromData
Added tag(s) moreinfo.
> tag 940914 + unreproducible
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
cppu::_copyConstructAnyF
Package: uno-libs3
Version: 6.1.5-3+deb10u4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
LibreOffice is crashing on launch with a segfault.
Fatal exception: Signal 11
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d523)[0x7f491d642523]
/usr/lib/libreoffice/pr
19 matches
Mail list logo
