[SOLVED] Getting Mega "Error Dump" message when I turn on the computer and Mega won't sync

Gregg Bell · 12-09-2017, 01:34 PM

It's happened twice in the last week or so. I have two computers synced via Mega (I guess it's technically called MegaSync) and it's worked great for years. The only variable in my computer use lately has been using FreeFileSync 9.5 to back up some folders. You can see my response to Mega in the attachment and here's the full error message:

Code:

MEGAprivate ERROR DUMP
Application: MEGAsync
Version code: 3500.0
Module name: megasync
Operating system: Linux
System version:  ubuntu 16.04/#126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017
System release:  4.4.0-103-generic
System arch: x86_64
Error info:
Segmentation fault (11) at address 0x10
Stacktrace:
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0xebc17) [0x7f2f3f69cc17]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0xebc17) [0x7f2f3f69cc17]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0xebfe0) [0x7f2f3f69cfe0]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0xf432e) [0x7f2f3f6a532e]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(_ZN10QSslSocketC1EP7QObject+0x1f) [0x7f2f3f69f39f]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0x58bca) [0x7f2f3f609bca]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0x526b7) [0x7f2f3f6036b7]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0x54d58) [0x7f2f3f605d58]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0x92145) [0x7f2f3f643145]
/usr/lib/x86_64-linux-gnu/libQtNetwork.so.4(+0x100155) [0x7f2f3f6b1155]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1d1) [0x7f2f3f262db1]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f2f3facafdc]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x2b6) [0x7f2f3fad1f16]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7f2f3f24890d]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x376) [0x7f2f3f24c3c6]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1bb13e) [0x7f2f3f27913e]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7) [0x7f2f3d263197]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7f2f3d2633f0]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f2f3d26349c]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f2f3f2792ae]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x3f) [0x7f2f3f24718f]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1b5) [0x7f2f3f2474f5]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QThread4execEv+0x139) [0x7f2f3f136549]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x7ae3c) [0x7f2f3f138e3c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f2f3eea86ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f2f3e33d3dd]

Thanks.

AwesomeMachine · 12-11-2017, 01:33 AM

Segmentation fault means an error in the software. There is probably nothing you can do except if instructed to do so by the developers.

Gregg Bell · 12-11-2017, 11:17 AM

Quote:

Originally Posted by AwesomeMachine

Segmentation fault means an error in the software. There is probably nothing you can do except if instructed to do so by the developers.

Thanks Awesome. I responded both times to Mega's error message and they got the sync working again, and so I'm fine with that. It's good to know it's an error in the software and not something I've done. Appreciate you responding.

P.S. I watched that Youtube/Stalllman link about Ubuntu/Canonical spying. Sheesh! So same goes for Xubuntu as well, right?