Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  Nextcloud-Desktop segmentation error  (Read 5023 times)

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Nextcloud-Desktop segmentation error
« on: 2019/11/25, 11:54:25 »
Are few months that my Nextcloud desktop client is not working.
So I was hoping that the latest release was fixing but nevermind the problem is still going.So I chosen ti compile the package on my own but... it still crashing anyway.
The cmd version is working but not the gui version and I think that is something with Qt.
Running gdb on the exectuable:
Code: [Select]
Starting program: /home/mte90/Desktop/kde/nextcloud-desktop-2.6.1/debian/tmp/usr/bin/nextcloud
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe0f9a700 (LWP 26130)]
[New Thread 0x7fffdb2a6700 (LWP 26131)]
[New Thread 0x7fffd3fff700 (LWP 26133)]
[New Thread 0x7fffd2289700 (LWP 26134)]
[New Thread 0x7fffd1a67700 (LWP 26135)]
[New Thread 0x7fffd1256700 (LWP 26136)]
[Detaching after fork from child process 26137]
[Detaching after fork from child process 26141]
[New Thread 0x7fffd085c700 (LWP 26147)]

** (process:26124): CRITICAL **: 11:51:14.204: cloud_providers_dbus_object_skeleton_new: assertion 'g_variant_is_object_path (object_path)' failed

(process:26124): GLib-GObject-CRITICAL **: 11:51:14.204: g_object_set: assertion 'G_IS_OBJECT (object)' failed
[New Thread 0x7fffbbfff700 (LWP 26148)]

Thread 1 "nextcloud" received signal SIGSEGV, Segmentation fault.
0x00007ffff7d99619 in g_dbus_object_get_object_path () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(gdb) backtrace
#0  0x00007ffff7d99619 in g_dbus_object_get_object_path () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1  0x00007ffff7d9f8e3 in g_dbus_object_manager_server_export () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2  0x00007ffff7c172e6 in cloud_providers_provider_exporter_add_account () at /usr/lib/x86_64-linux-gnu/libcloudproviders.so.0
#3  0x00007ffff7c15cfd in  () at /usr/lib/x86_64-linux-gnu/libcloudproviders.so.0
#4  0x00007ffff7c398e6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x00007ffff7c3b4f9 in g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x00007ffff7c3b849 in g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x000055555573e3eb in CloudProviderWrapper::CloudProviderWrapper(QObject*, OCC::Folder*, _CloudProvidersProviderExporter*)
    (this=0x55555612d190, parent=<optimized out>, folder=0x5555563458d0, cloudprovider=0x7fffc800d520) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:208
#8  0x000055555573a9ce in CloudProviderManager::slotFolderListChanged(QMap<QString, OCC::Folder*> const&) (this=0x555556122b40, folderMap=...)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:1292
#9  0x000055555573ac04 in CloudProviderManager::registerSignals() (this=0x555556122b40) at ./src/gui/cloudproviders/cloudprovidermanager.cpp:49
#10 0x00007ffff7d89677 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x00007ffff7d898a8 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#12 0x00007ffff7d27f69 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#13 0x00007ffff7d28a8d in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#14 0x00007ffff7d8120f in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x00007ffff7d27f69 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#16 0x00007ffff7d27fa9 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x00007ffff7e9dd7e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff7e9e130 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--c
#19 0x00007ffff7e9e1bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fffecb327f1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fffecadb71b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fffecae31c2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000055555560f526 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./src/gui/main.cpp:167
GDB on the binary shipped with Debian sid the log is similar:
Code: [Select]
Thread 1 "nextcloud" received signal SIGSEGV, Segmentation fault.
0x00007ffff7d99619 in g_dbus_object_get_object_path () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(gdb) backtrace
#0  0x00007ffff7d99619 in g_dbus_object_get_object_path () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1  0x00007ffff7d9f8e3 in g_dbus_object_manager_server_export () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2  0x00007ffff7c172e6 in cloud_providers_provider_exporter_add_account () at /usr/lib/x86_64-linux-gnu/libcloudproviders.so.0
#3  0x00007ffff7c15cfd in  () at /usr/lib/x86_64-linux-gnu/libcloudproviders.so.0
#4  0x00007ffff7c398e6 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5  0x00007ffff7c3b4f9 in g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x00007ffff7c3b849 in g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x000055555573e3eb in CloudProviderWrapper::CloudProviderWrapper(QObject*, OCC::Folder*, _CloudProvidersProviderExporter*)
    (this=0x555556bb3c00, parent=<optimized out>, folder=0x555556651800, cloudprovider=0x7fffc800d520) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:208
#8  0x000055555573a9ce in CloudProviderManager::slotFolderListChanged(QMap<QString, OCC::Folder*> const&) (this=0x5555560694d0, folderMap=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:1292
#9  0x000055555573ac04 in CloudProviderManager::registerSignals() (this=0x5555560694d0) at ./src/gui/cloudproviders/cloudprovidermanager.cpp:49
#10 0x00007ffff7d89677 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x00007ffff7d898a8 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#12 0x00007ffff7d27f69 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#13 0x00007ffff7d28a8d in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#14 0x00007ffff7d8120f in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x00007ffff7d27f69 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#16 0x00007ffff7d27fa9 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x00007ffff7e9dd7e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff7e9e130 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff7e9e1bf in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fffecb327f1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fffecadb71b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fffecae31c2 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x000055555560f526 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./src/gui/main.cpp:167
Someone has suggestions?

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #1 on: 2019/11/25, 12:12:53 »
I installed also the experimental package of https://packages.debian.org/experimental/libglib2.0-0 just to see if fix the problem but it didn't.

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: Nextcloud-Desktop segmentation error
« Reply #2 on: 2019/11/25, 22:37:40 »
a) try a new machine and a new installation
b) try pure debian

really - it isn't reproducible, if it would be there would be at least one user out of over 2500 with popcon on who will complain about the same bug.

Edit: So my best bet is that your installation is messed up - do you have any self built packges installed, no matter what - the infamous triple "configure; make; make install" or " cmake; make; make install" ??
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #3 on: 2019/11/26, 11:36:38 »
I have some package compiled on myself (neovim as example) but no debian packages rebuilted.
I use KDE and a lot of qt apps but this is the only one that crashes since I think 2 months I think.

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: Nextcloud-Desktop segmentation error
« Reply #4 on: 2019/11/26, 14:32:23 »
Quote from: Mte90
Starting program: /home/mte90/Desktop/(...)

That's scary. Why not from /opt?

If you need it now and you don't find the cause yet, you could (temporarily) use a daily 2.7.0 AppImage (or the stable 2.6.1).

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #5 on: 2019/11/26, 14:50:16 »
This path was from testing :-)I don't like appimage because of the huge size and because I have already all the dependence, so I more interested to understand what is the problem :-/

Offline axt

  • User
  • Posts: 494
    • axebase.net
Re: Nextcloud-Desktop segmentation error
« Reply #6 on: 2019/11/26, 15:18:06 »
Quote from: Mte90
I don't like appimage

Just so we're clear, neither do I. That's why I wrote "now", "temporarily" and so on.

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: Nextcloud-Desktop segmentation error
« Reply #7 on: 2019/11/26, 20:08:39 »
if the appimage would work - it would solve nothing - it would only mean: Hey, something is wrong with the current installation, so my bet is: Fix the mess and be happy. And there is also no magic in git builds if two versions are faulty on exactly one machine. Hmm - maybe i don't know enough about debian and Qt - i should really learn this stuff ...

Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #8 on: 2019/11/27, 11:20:46 »
Do you have any issue on investigating what is the problem?
Right now a ldd: https://pastebin.com/SvNQMBx5
I don't see anything wrong there for path and also the stuff I compiled doesn't involve new libraries but only specific software.

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: Nextcloud-Desktop segmentation error
« Reply #9 on: 2019/11/27, 17:43:16 »
ok - easy to answer:
* i cant't reproduce it - so i don't care about. The packages has enough users, so if the bug would be reproducible the debian bts would be flooded with grave, important or serious bugs - nothing of that happend right now. Same for ubuntu users. Just not happend. So my suggestion is that the problem is in your installation, not in debian.
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #10 on: 2019/12/09, 13:02:19 »
Just to update, I tested on my laptop where I have too siduction and the problem doesn't happen.So I am investigating more and I will open a bug to nextcloud-desktop just to understand where is the error.Because I don't know specifically what is happening.

Offline Mte90

  • User
  • Posts: 216
  • KDE & Debian lover
    • http://www.mte90.net
Re: Nextcloud-Desktop segmentation error
« Reply #11 on: 2020/01/02, 11:44:21 »
Just for reference there is a bug with nextcloud on parsing the settings https://github.com/nextcloud/desktop/issues/1669