Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
On Fri, Aug 09, 2019 at 08:18:53PM +0300, Timur Irikovich Davletshin wrote: > I believe bug is to be reopened again to fix dependencies. Package Did so (and fixed it in git) > libreoffice-mysql-connector does exist for LO 6.3 and to be upgraded > automatically or it will cause problem upgrading from Buster to > Testing. Not really if you did a complete "apt upgrade" etc since apt will upgrade libreoffice-mysql-connector, too and it will work. But you are right, if you do partial upgrades (like with -t buster-backports install libreoffice) it breaks. That's why I added the Conflicts: now. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
On Fri, Aug 09, 2019 at 08:21:55PM +0300, Timur Irikovich Davletshin wrote: > If it was optional I don't get why it was changed? As far I understand > it does exist in repo for LO 6.3. Just as a dummy to upgrade to the new libreoffice-sdbc-mysql so that it doesn't get lost in a upgrade. in 6.1 it was an extension. From 6.2 on it's a proper component of LibreOffice. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
tag 933835 + pending thanks Hi, On Fri, Aug 09, 2019 at 07:17:40PM +0200, Rene Engelhard wrote: > On Fri, Aug 09, 2019 at 07:54:21PM +0300, Timur Irikovich Davletshin wrote: > > I was wrong, problem is not in atk*. I rolled back snapshot of buster > > to it's original state and tried to reproduce behaviour. Problem is in > > libreoffice-mysql-connector which is not upgraded automatically. So > > OK, indeed. Reopening and adapting. > > Will be fixed. > > > dependencies... > > No, Conflicts:, libreoffice-mysql-connector is now a dummy and it seems > that the old ibreoffice-mysql-connector plays bad with the new LO :/ > And no, LibreOffice shouldn't depend on it :) (LO works without > libreoffice-sdbc-mysql installed, you just need it for a MySQL > connection.) > > We can't change the old package, but we can make -core Conflicts: > against the old libreoffice-mysql-connector.. https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/commit/22be2ede8d9c5ae4c6a1759602ba5cda2f9b8718 Will be in the next upload. Thanks for insisting, I'd have never have thought this extension would cause a failure like this if the new LO didn't have the new internal compnent installed even. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
If it was optional I don't get why it was changed? As far I understand it does exist in repo for LO 6.3. On Fri, 9 Aug 2019 19:10:28 +0200 Rene Engelhard wrote: > Or Conflicts. libreoffice-mysql-connector was an optional extension > until 6.2 >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
I believe bug is to be reopened again to fix dependencies. Package libreoffice-mysql-connector does exist for LO 6.3 and to be upgraded automatically or it will cause problem upgrading from Buster to Testing. Timur. On Fri, 9 Aug 2019 19:05:36 +0200 Rene Engelhard wrote: > close 933835 > thanks > > On Fri, Aug 09, 2019 at 07:36:59PM +0300, Timur Irikovich Davletshin wrote: > > My complain was not about LO 6.3 in Debian Testing but about LO 6.3 > > Aha. > > > from Buster backports. Well except me we have original reporter of this > > bug. Let's wait for him. > > Which is - as I said - built against busters atk (and on my system) > works with busters atk. (I cross-checked just now in the .buildinfo > file, just in the unlikely case I used the wrong chroot.) > What dependency would you suggest to something newer? As said, LO > doesn't use features of newer atks directly, ttbomk. > > And note that buster-backports is not part of this BTS at all. The > version tracking doesn't know bpo versions. > So even if this was a problem there this place would be wrong and > debian-backpo...@lists.backports.org would be the place to discuss it. > See backports.debian.org - Report Bugs: > https://backports.debian.org/Instructions/#index6h2: > "Report Bugs > Please report bugs that you found in the packages to the backports > mailing list and NOT to the Debian BTS!" > > Closing again. > > Regards, > > Rene > >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
reopen 933835 retitle 933835 libreoffice not start with fatal exception signal 11 when old libreoffice-mysql-connector is installed severity 933835 serious thanks Hi, On Fri, Aug 09, 2019 at 07:54:21PM +0300, Timur Irikovich Davletshin wrote: > I was wrong, problem is not in atk*. I rolled back snapshot of buster > to it's original state and tried to reproduce behaviour. Problem is in > libreoffice-mysql-connector which is not upgraded automatically. So OK, indeed. Reopening and adapting. Will be fixed. > dependencies... No, Conflicts:, libreoffice-mysql-connector is now a dummy and it seems that the old ibreoffice-mysql-connector plays bad with the new LO :/ And no, LibreOffice shouldn't depend on it :) (LO works without libreoffice-sdbc-mysql installed, you just need it for a MySQL connection.) We can't change the old package, but we can make -core Conflicts: against the old libreoffice-mysql-connector.. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
reopen 933835 retitle 933835 libreoffice not start with fatal exception signal 11 with old libreoffice-mysql-connector installed thanks On Fri, Aug 09, 2019 at 07:54:21PM +0300, Timur Irikovich Davletshin wrote: > I was wrong, problem is not in atk*. I rolled back snapshot of buster > to it's original state and tried to reproduce behaviour. Problem is in > libreoffice-mysql-connector which is not upgraded automatically. So OK, that makes it testing/unstable, too. > dependencies... Or Conflicts. libreoffice-mysql-connector was an optional extension until 6.2 So new LO needs to conflict against old libreoffice-mysql-connector when it was still an extension it seems... Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
close 933835 thanks On Fri, Aug 09, 2019 at 07:36:59PM +0300, Timur Irikovich Davletshin wrote: > My complain was not about LO 6.3 in Debian Testing but about LO 6.3 Aha. > from Buster backports. Well except me we have original reporter of this > bug. Let's wait for him. Which is - as I said - built against busters atk (and on my system) works with busters atk. (I cross-checked just now in the .buildinfo file, just in the unlikely case I used the wrong chroot.) What dependency would you suggest to something newer? As said, LO doesn't use features of newer atks directly, ttbomk. And note that buster-backports is not part of this BTS at all. The version tracking doesn't know bpo versions. So even if this was a problem there this place would be wrong and debian-backpo...@lists.backports.org would be the place to discuss it. See backports.debian.org - Report Bugs: https://backports.debian.org/Instructions/#index6h2: "Report Bugs Please report bugs that you found in the packages to the backports mailing list and NOT to the Debian BTS!" Closing again. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
I was wrong, problem is not in atk*. I rolled back snapshot of buster to it's original state and tried to reproduce behaviour. Problem is in libreoffice-mysql-connector which is not upgraded automatically. So dependencies... Timur. On Fri, 09 Aug 2019 19:36:59 +0300 Timur Irikovich Davletshin < timur.davlets...@gmail.com> wrote: > My complain was not about LO 6.3 in Debian Testing but about LO 6.3 > from Buster backports. Well except me we have original reporter of this > bug. Let's wait for him. > > On Fri, 9 Aug 2019 18:30:12 +0200 Rene Engelhard > wrote: > > On Fri, Aug 09, 2019 at 06:03:09PM +0200, Rene Engelhard wrote: > > > > If some version dependencies are wrong (it seems to be the > case)... > > > > > > That's what you say. But why does it start on my laptop with > busters atk > > > then? > > > And buster-backports' build is - of course - built against busters > atk. > > > So that can't be it. > > > > > > > they ought to be checked and fixed. But that means bug is to be > > > > reopened. > > > > > > If it was a atk thing when built against sids atk you might be > right, > > > but I see no confirmation here yet. > > > > So, what I did just now: > > > > - uptodate Debian testing VM. LO starts > > > > https://tracker.debian.org/pkg/atk1.0 said the version before was > > 2.30.0-2 and said when it migrated. > > > > - added that (http://snapshot.debian.org/package/atk1.0/2.30.0-2/ and > > thus > > > http://snapshot.debian.org/archive/debian/20180908T223035Z/pool/main/a/atk1.0/ > > and > > thus http://snapshot.debian.org/archive/debian/20180908T223035Z to > > sources.list) > > > > - downgraded libatk using > > > > apt install libatk...=2.30.2 for atk packages installed. > > > > Still starts. > > > > So still unreproducible. > > > > Regards, > > > > Rene > > > > > > >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
My complain was not about LO 6.3 in Debian Testing but about LO 6.3 from Buster backports. Well except me we have original reporter of this bug. Let's wait for him. On Fri, 9 Aug 2019 18:30:12 +0200 Rene Engelhard wrote: > On Fri, Aug 09, 2019 at 06:03:09PM +0200, Rene Engelhard wrote: > > > If some version dependencies are wrong (it seems to be the case)... > > > > That's what you say. But why does it start on my laptop with busters atk > > then? > > And buster-backports' build is - of course - built against busters atk. > > So that can't be it. > > > > > they ought to be checked and fixed. But that means bug is to be > > > reopened. > > > > If it was a atk thing when built against sids atk you might be right, > > but I see no confirmation here yet. > > So, what I did just now: > > - uptodate Debian testing VM. LO starts > > https://tracker.debian.org/pkg/atk1.0 said the version before was > 2.30.0-2 and said when it migrated. > > - added that (http://snapshot.debian.org/package/atk1.0/2.30.0-2/ and > thus > http://snapshot.debian.org/archive/debian/20180908T223035Z/pool/main/a/atk1.0/ > and > thus http://snapshot.debian.org/archive/debian/20180908T223035Z to > sources.list) > > - downgraded libatk using > > apt install libatk...=2.30.2 for atk packages installed. > > Still starts. > > So still unreproducible. > > Regards, > > Rene > >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
On Fri, Aug 09, 2019 at 06:03:09PM +0200, Rene Engelhard wrote: > > If some version dependencies are wrong (it seems to be the case)... > > That's what you say. But why does it start on my laptop with busters atk > then? > And buster-backports' build is - of course - built against busters atk. > So that can't be it. > > > they ought to be checked and fixed. But that means bug is to be > > reopened. > > If it was a atk thing when built against sids atk you might be right, > but I see no confirmation here yet. So, what I did just now: - uptodate Debian testing VM. LO starts https://tracker.debian.org/pkg/atk1.0 said the version before was 2.30.0-2 and said when it migrated. - added that (http://snapshot.debian.org/package/atk1.0/2.30.0-2/ and thus http://snapshot.debian.org/archive/debian/20180908T223035Z/pool/main/a/atk1.0/ and thus http://snapshot.debian.org/archive/debian/20180908T223035Z to sources.list) - downgraded libatk using apt install libatk...=2.30.2 for atk packages installed. Still starts. So still unreproducible. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
This is why I was insisting on checking all dependencies. I have two machines (laptop and desktop) with only darktable installed from 3rd party repos on one of them and result is the same — LO doesn't start. Timur. On Fri, 9 Aug 2019 18:03:09 +0200 Rene Engelhard wrote: > reopen 933835 > retitle 933835 too lax atk dependency? - libreoffice not start with fatal exception signal 11 > thanks > > Hi, > > On Fri, Aug 09, 2019 at 06:49:42PM +0300, Timur Irikovich Davletshin wrote: > > On Fri, 9 Aug 2019 10:30:50 +0200 Rene Engelhard > > wrote: > > > dependency information.. I could force a newer dependency, but... > > > > > > > > > > If some version dependencies are wrong (it seems to be the case)... > > That's what you say. But why does it start on my laptop with busters atk > then? > And buster-backports' build is - of course - built against busters atk. > So that can't be it. >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
IMHO, all deps should be checked. On Fri, 09 Aug 2019 18:49:42 +0300 Timur Irikovich Davletshin < timur.davlets...@gmail.com> wrote: > On Fri, 9 Aug 2019 10:30:50 +0200 Rene Engelhard > wrote: > > dependency information.. I could force a newer dependency, but... > > > > > > If some version dependencies are wrong (it seems to be the case)... > they ought to be checked and fixed. But that means bug is to be > reopened. > > Cheers, > > Timur. > > >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
reopen 933835 retitle 933835 too lax atk dependency? - libreoffice not start with fatal exception signal 11 thanks Hi, On Fri, Aug 09, 2019 at 06:49:42PM +0300, Timur Irikovich Davletshin wrote: > On Fri, 9 Aug 2019 10:30:50 +0200 Rene Engelhard > wrote: > > dependency information.. I could force a newer dependency, but... > > > > > > If some version dependencies are wrong (it seems to be the case)... That's what you say. But why does it start on my laptop with busters atk then? And buster-backports' build is - of course - built against busters atk. So that can't be it. > they ought to be checked and fixed. But that means bug is to be > reopened. If it was a atk thing when built against sids atk you might be right, but I see no confirmation here yet. *shrugs*, reopening this bug does not really help very much in this case, it'll still be + moreinfo, + unreproducible, so people (you?) need to give more information to this bug anyway. But we can do that anyway... But don't inflate the severity. I'll immediately downgrade it again. Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
On Fri, 9 Aug 2019 10:30:50 +0200 Rene Engelhard wrote: > dependency information.. I could force a newer dependency, but... > > If some version dependencies are wrong (it seems to be the case)... they ought to be checked and fixed. But that means bug is to be reopened. Cheers, Timur.
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
Hi, On Fri, Aug 09, 2019 at 07:51:55AM +0300, Timur Irikovich Davletshin wrote: > I believe this bug should be reopened. Not sure. > Right version of atk library is not in the dependencies of this build. OK, but that would be a bug in atk that they are not giving us correct dependency information.. I could force a newer dependency, but... The code is the same as in "official builds" so it has to be something with atk itself. But see below. > Regular installation via apt-get > -t buster-backports install libreoffice leads to non working state. Just did this on my buster. LO starts after that. atk from bster. Maybe the problem exhibits itself only if you enable some "special" accessibility? (My only accessibility-related option I enabled is "Big fonts" and "Visual warnings" in gnome-shells "panel". > P.S. Official builds work fine btw... Because they build with an old atk? (CentOS 7 TTBOMK) Regards, Rene
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
I believe this bug should be reopened. Right version of atk library is not in the dependencies of this build. Regular installation via apt-get -t buster-backports install libreoffice leads to non working state. Regards, Timur. P.S. Official builds work fine btw... On Sun, 4 Aug 2019 21:41:26 +0200 Rene Engelhard wrote: > Hi, > > On Sun, Aug 04, 2019 at 07:44:35PM +0200, sanskryt wrote: > > OK the problem was solved by today's upgrade. > > In it were upgraded cpid gir1.2-atk-1.0 gpicview libarmadillo9 > > libatk1.0-0 libatk1.0-0:i386 libatk1.0-data libatk1.0-dev libatk1.0-doc > > liblockfile-bin liblockfile1 libreoffice-mysql-connector wget. >^^^ > Besides the fact that this is a empty > dummy package this again shows your > system was not clean - as that package > got updated in the repos with exactly the > same version you reported against. > > > In effect libreoffice starts again in new version so the bug can be > > closed in my humble oppinion. > > In my humble opinion you should have not reported it in the first place. > > But thanks, closing. > > Regards, > > Rene > >
Bug#933835: Info received (Bug#933835: libreoffice not start with fatal exception signal 11)
OK the problem was solved by today's upgrade. In it were upgraded cpid gir1.2-atk-1.0 gpicview libarmadillo9 libatk1.0-0 libatk1.0-0:i386 libatk1.0-data libatk1.0-dev libatk1.0-doc liblockfile-bin liblockfile1 libreoffice-mysql-connector wget. In effect libreoffice starts again in new version so the bug can be closed in my humble oppinion. sanskryt On Sun, 2019-08-04 at 16:39 +, Debian Bug Tracking System wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due > course. > > Your message has been sent to the package maintainer(s): > Debian LibreOffice Maintainers > > If you wish to submit further information on this problem, please > send it to 933...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. >
