Subsurface doesn't load

Ciarán Norrby

unread,

Mar 20, 2019, 5:37:56 AM3/20/19

to Subsurface Divelog

Hi

I'm using Subsurface v4.8.5 on Ubuntu 16.04 LTS and yesterday after updating my dive log and then trying to re-open subsurface it wouldn't load. When I run it from the command line with -vv i get:

QEventLoop: Cannot be used without QApplication
QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
Subsurface v4.8.5,
built with libdivecomputer v0.7.0-devel-Subsurface-NG (072bef16666e0ec397b8236e92722b2f1347b59b)
built with Qt Version 5.5.1, runtime from Qt Version 5.5.1
built with libgit2 0.26.0
"validateGL(): created OpenGLContext."
"validateGL(): obtained QOpenGLFunctions."
"validateGL(): detected OpenGL version 3.0."
can't find Qt localization for locale "en-IE" searching in "/usr/share/qt5/translations"
can't find Subsurface localization for locale "en-IE"
Plugins Directory: QDir( "/usr/bin" , nameFilters = { "*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters( Dirs|Files|Drives|AllEntries ) )
Segmentation fault (core dumped)

I'm not exactly sure what any of this means, I have done sudo apt remove subsurface && sudo apt purge subsurface and then re-installed but it didn't fix the issue. any help would be greatly appreciated.

Thanks

Ciaran

Miika Turkia

unread,

Mar 21, 2019, 1:50:14 AM3/21/19

to subsurfac...@googlegroups.com

Fo you use cloud or local log file? I wonder if it is something in your log that is not parsed properly, and in that case it would be helpful to have your log to debug the problem.

You could also start Subsurface with test user to see if that works

subsurface —user=test

test is just a random username that doesn't have log on your computer, so that we start with clean data.

If the test user also crashes, run

ldd /usr/bin/subsurface

That would reveal if some required library is missing.

Also running Subsurface in gdb and grabbing backtrace after the crash should give us some info on where the problem might be.

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/c5b8070f-058f-426f-b9cc-7fb3c36ca4b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ciarán Norrby

unread,

Mar 22, 2019, 7:40:08 AM3/22/19

to Subsurface Divelog

Hi Miika,

Thank you for this, I ran this "subsurface —user=test" and although it did start up I also get this output on the command line:

subsurface --user=test

QEventLoop: Cannot be used without QApplication
QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.

can't find Subsurface localization for locale "en-IE"

Not sure if that output is terribly helpful, which particular log file would you need?

Thanks again!

Ciaran

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Miika Turkia

unread,

Mar 23, 2019, 1:39:55 AM3/23/19

to subsurfac...@googlegroups.com

As everything works with a fresh account, the problem is most likely with user settings or your dive log file.

Do you use cloud or local storage for saving the dive log? We could first try by exporting your dives to Subsurface format and sending that to me (no need to post it publicly). Right click on the divelist, select export, all dives, and Subsurface format.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/d7536711-9acd-41ff-90ec-b1d92b618121%40googlegroups.com.

Ciarán Norrby

unread,

Mar 23, 2019, 3:45:15 AM3/23/19

to Subsurface Divelog

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/d7536711-9acd-41ff-90ec-b1d92b618121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi I use a mixture of both but I get the feeling that the problem is with local storage. I'm sending you the file, I hope it's the right one

Regards,

Ciaran

Jon Mclin

unread,

Mar 23, 2019, 4:22:42 PM3/23/19

to Subsurface Divelog

Same symptoms, same platform (ss 4.8.5 on Ubuntu 16.04 LTS).

Trigger may have been one of two events today, since it worked last week and this morning before I did these two items:

- added a georeference dive site location

- synched to cloud storage

Starting with "--user=test" works okay, and it opens and displays my "jon.xml" file okay.

I also moved "jon.xml" to a Windows 10 box, where it opens okay.

gdb output below:

Starting program: /usr/bin/subsurface
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe3fb3700 (LWP 4534)]

QEventLoop: Cannot be used without QApplication
QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.

[New Thread 0x7fffe0e45700 (LWP 4535)]
[New Thread 0x7fffd3185700 (LWP 4536)]
[New Thread 0x7fffd2984700 (LWP 4537)]
[New Thread 0x7fffd2183700 (LWP 4538)]
[New Thread 0x7fffc26bf700 (LWP 4540)]
[New Thread 0x7fffc1ebe700 (LWP 4541)]
[New Thread 0x7fffb3989700 (LWP 4542)]
[Thread 0x7fffc26bf700 (LWP 4540) exited]
[New Thread 0x7fffc26bf700 (LWP 4543)]
[New Thread 0x7fffb160e700 (LWP 4546)]

Thread 1 "subsurface" received signal SIGSEGV, Segmentation fault.
0x00007ffff31123f0 in QOpenGLFramebufferObject::handle() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(gdb) bt
#0 0x00007ffff31123f0 in QOpenGLFramebufferObject::handle() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#1 0x00007ffff7e5a20f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#2 0x00007ffff37e2fc8 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3 0x00007ffff37a005c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4 0x00007ffff37a5516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x00007ffff24a838b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007ffff37dfac6 in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7 0x00007ffff37df7b6 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8 0x00007ffff37df84f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9 0x00007ffff37df7b6 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007ffff37df84f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ffff37e263d in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff37df7c8 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff37df84f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007ffff37e263d in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ffff37df7c8 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007ffff37df84f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007ffff37e263d in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007ffff37df7c8 in QWidgetPrivate::showChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007ffff37df84f in QWidgetPrivate::show_helper() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007ffff37e263d in QWidget::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x000000000052bc4b in MainWindow::initialUiSetup() ()
#22 0x000000000052decb in MainWindow::MainWindow() ()
#23 0x0000000000521e25 in init_ui() ()
#24 0x000000000051c60d in main ()
(gdb)

Miika Turkia

unread,

Mar 24, 2019, 2:10:19 AM3/24/19

to Subsurface Divelog

Does the crash still occur, if you try the latest development version of Subsurface? AppImage should work on your distro and is a mostly self-contained package of latest development version of Subsurface. It is available from:

https://github.com/Subsurface-divelog/subsurface/releases (even though the file name clames 4.8.4-333 this is newer version than 4.8.5)

It the problem persists with the development version, then it would be great if you could try to create minimal XML log that crashes on startup. However, if the problem is related to cloud storage, then an XML log is not going to cause a crash.

HTH

Ciarán Norrby

unread,

Mar 25, 2019, 7:43:51 AM3/25/19

to Subsurface Divelog

Hi,

It loads fine using the AppImage :) Thank you!

Now I have a different in that I think I just wrote over my dives that I have logged in cloud storage, is there a way to retrieve them? (sorry for being a torture)

Miika Turkia

unread,

Mar 25, 2019, 8:28:08 AM3/25/19

to subsurfac...@googlegroups.com

If you are familiar with git, the log is stored in git repository and you can do all the appropriate tricks with it. If unfamiliar, send dirk an email from the registered address and describe what kind of save you need (dirk at hohndel dot org)

IIRC the local repo is under your home directory in .subsurface/cloudstorage/<hash>

HTH

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/0c2c2a30-df77-4d54-b27f-beb72c6b27c5%40googlegroups.com.

Ciarán Norrby

unread,

Mar 25, 2019, 10:28:43 AM3/25/19

to Subsurface Divelog

awesome, thank you so much for all your help, i really appreciate it

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

Jon Mclin

unread,

Mar 30, 2019, 5:18:21 PM3/30/19

to Subsurface Divelog

App Image version works with the log. I tried both the Dev version, and the 4.8.5 (release.

Resynched with Cloud Storage, then restarted to see if it crashed (since that was one of the possible triggers for the original crash). Restarted fine.

Alas, still no luck opening my Cobalt 2...

Thanks!

Dirk Hohndel

unread,

Mar 30, 2019, 6:30:37 PM3/30/19

to subsurfac...@googlegroups.com

I must have missed that part. What's not working with the Cobalt 2?

/D

Jon Mclin

unread,

Mar 31, 2019, 3:05:57 PM3/31/19

to Subsurface Divelog

I'd posted my Cobalt issue as a separate thread, here:

https://subsurface-divelog.org/user-forum/?place=msg%2Fsubsurface-divelog%2FWM2QGvK0lZM%2FFeJk1RMMAQAJ

Reply all

Reply to author

Forward