** Description changed:
+ [Impact]
+
+ * The software fails to start, so is rendered useless to an end user
+
+ * Until recently LTO had not been enabled for the builds.
+
+
+ [Test Plan]
+
+ * Start the client. The client should start normally.
+
+ * Test the normal functionality as use
I got the following error, fixed by moving ~/.config/Nextcloud
2021-04-22 12:46:20:892 [ fatal default ]: ENFORCE: "allow_failure" in
file ./src/common/ownsql.cpp, line 265 with message: SQLITE Prepare error
Aborted (core dumped)
The startup SEGFAULT is gone in the no-lto build
--
You rec
Test rebuild of the hirsute package is done with LTO disabled. Can be
tested from
sudo add-apt-repository ppa:rikmills/nexcloud-no-lto
sudo apt-get update
(yes I did make a typo when doing the ppa name)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: nextcloud-desktop (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
nextcloud crashed with SIGSEGV.
To manage notifications about
This appears to be due to building with LTO enabled on amd64
https://github.com/nextcloud/desktop/issues/2790
** Bug watch added: github.com/nextcloud/desktop/issues #2790
https://github.com/nextcloud/desktop/issues/2790
--
You received this bug notification because you are a member of Ubunt
https://github.com/nextcloud/desktop/issues/3090
** Bug watch added: github.com/nextcloud/desktop/issues #3090
https://github.com/nextcloud/desktop/issues/3090
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
What i noticed is, that the Ubuntu Version of the package has two dependencies,
that the Debian version does not have:
- libqt5websockets5
- qml-module-qtqml
So the segfault might be in one of these and not the nextcloud code
itself.
--
You received this bug notification because you are a membe
can confirm that with libnextcloudsync0_3.1.1-1_amd64.deb and nextcloud-
desktop_3.1.1-1_amd64.deb from debian bullseye it works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
n
nextcloud 3.1.1 debian unstable packages works for me too (amd64)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
nextcloud crashed with SIGSEGV.
To manage notifications about this bug
I do not get the crash on arm, this is a raspberry pi 400 machine.
$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
$ apt-cache policy nextcloud-desktop
nextcloud-desktop:
Installed: 3.1.1-1ubuntu1
Candidate: 3.1.1-1ubuntu1
Version table:
*** 3.1.1-1ubuntu1 500
I have the same bug, nextcloud-devs ppa is also concerned by the problem.
After manually installed nextcloud 3.1.1 debian unstable packages,
nextcloud-desktop works.
I think there is maybe something wrong with compilation (lto?).
--
You received this bug notification because you are a member of
This problem exists on X, too -- not only on Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
nextcloud crashed with SIGSEGV.
To manage notifications about this bug go to:
http
I have the same issue in Wayland.
Program received signal SIGSEGV, Segmentation fault.
doActivate (sender=0x0, signal_index=9, argv=0x7fffb1f0) at
kernel/qobject.cpp:3768
3768kernel/qobject.cpp: No such file or directory.
(gdb) bt
#0 doActivate(QObject*, int, void**) (sender=0x0, signal_
i tried with the appimage version of the client and that works ootb with
the user configs etc.
wget
https://github.com/nextcloud/desktop/releases/download/v3.2.0/Nextcloud-3.2.0-x86_64.AppImage
chmod +x Nextcloud-3.2.0-x86_64.AppImage
./Nextcloud-3.2.0-x86_64.AppImage
So something is broken on t
Maybe this is not caused by the nextcloud client itself but by some
(qt?) library the client is using?
(Version 3.2.0 is working on previous Ubuntu versions - older than
hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I have updated to version 3.2.0-20210410.072919.14fbf1b10-1.0~hirsute1
from http://ppa.launchpad.net/nextcloud-devs/client/ubuntu
But nextcloud-desktop is still segfaulting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I'm having this issue as well. Here's a backtrace from GDB, with some
debug symbols:
(gdb) bt
#0 doActivate (sender=0x0, signal_index=9,
argv=argv@entry=0x7fffb9a0) at kernel/qobject.cpp:3768
#1 0x7fffeafb5cb8 in QMetaObject::activate (sender=,
m=m@entry=0x7fffebed30a0 ,
local_signal_
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nextcloud-desktop (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
T
Confirmed. Since the latest update to 3.1.1-1ubuntu1 nextcloud desktop
is segfaulting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923053
Title:
nextcloud crashed with SIGSEGV.
To manage notific
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+attachment/5485597/+files/CoreDump.gz
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
20 matches
Mail list logo