Hi Brad, did you save the corrupt workspace file? And if yes, can I have it to debug the crash.
You can ignore the warning. It's from GDAL. Oliver > Gesendet: Donnerstag, 19. Juli 2018 um 00:12 Uhr > Von: brad <[email protected]> > An: "Oliver Eichler" <[email protected]> > Cc: QlandkarteGT <[email protected]> > Betreff: Re: Aw: Re: [Qlandkartegt-users] seg fault, sql? > > It was the database. I removed it and it works fine now. If I run > from the command line I get this warning: > > "[warning] libpng warning: iCCP: known incorrect sRGB profile" > > Ignore it? > > > > On 07/18/2018 01:02 AM, Oliver Eichler wrote: > > Hi Brad, > > > > there have to be SQL plugins installed, too. A possible path could be > > /usr/lib64/qt5/plugins. > > > > However that does not explain the crash. I temporarily removed the plugins > > on my system and QMS simply gave me an error message and disabled database > > support. > > > > But your traceback shows that it happens while loading the workspace > > database. You can try to remove that database. It's in > > ~/.config/QLandkarte/workspace.db. > > > > For more information it would need a traceback from QMS with full debug > > information compiled in. And even better: A way to reproduce the crash. > > Right now I am not able to make it crash. > > > > HTH > > > > Oliver > > > >> Gesendet: Mittwoch, 18. Juli 2018 um 00:24 Uhr > >> Von: brad <[email protected]> > >> An: "Oliver Eichler" <[email protected]> > >> Betreff: Re: Aw: [Qlandkartegt-users] seg fault, sql? > >> > >> I do have lib5qt5sql5 installed. > >> > >> Is this helpful?: > >> > >> dt1:apport-retrace --stdout /var/crash/_usr_bin_qmapshack.1000.crash > >> E: You must put some 'source' URIs in your sources.list > >> dpkg-source: warning: -sn is not a valid option for > >> Dpkg::Source::Package::V3::Quilt > >> gpgv: Signature made Tue 26 Dec 2017 03:09:08 PM MST > >> gpgv: using RSA key 8182DE417056408D614650D16750F10AE88D4AF1 > >> gpgv: Can't check signature: No public key > >> dpkg-source: warning: failed to verify signature on > >> /tmp/tmpncdtq4e5/qmapshack_1.10.0-1.dsc > >> --- stack trace --- > >> #0 0x00007f598819bd3a in QCoreApplication::postEvent(QObject*, QEvent*, > >> int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #1 0x0000563604ce27a6 in CDBProject::~CDBProject() () > >> No symbol table info available. > >> #2 0x0000563604ce2839 in CDBProject::~CDBProject() () > >> No symbol table info available. > >> #3 0x0000563604cc31be in CGisListWks::slotLoadWorkspace() () > >> No symbol table info available. > >> #4 0x00007f59881c75b5 in QMetaObject::activate(QObject*, int, int, > >> void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #5 0x00007f59881d4113 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #6 0x00007f59881c80db in QObject::event(QEvent*) () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #7 0x00007f5988f1682c in QApplicationPrivate::notify_helper(QObject*, > >> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> No symbol table info available. > >> #8 0x00007f5988f1e0f4 in QApplication::notify(QObject*, QEvent*) () > >> from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> No symbol table info available. > >> #9 0x00007f59881989a8 in QCoreApplication::notifyInternal2(QObject*, > >> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #10 0x00007f59881f0d8e in QTimerInfoList::activateTimers() () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #11 0x00007f59881f1551 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #12 0x00007f597c9ec287 in g_main_context_dispatch () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> No symbol table info available. > >> #13 0x00007f597c9ec4c0 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> No symbol table info available. > >> #14 0x00007f597c9ec54c in g_main_context_iteration () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> No symbol table info available. > >> #15 0x00007f59881f18ef in > >> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) > >> () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #16 0x00007f59881969ea in > >> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> No symbol table info available. > >> #17 0x00007f5989100ec7 in QDialog::exec() () from > >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> No symbol table info available. > >> #18 0x00007f5989135355 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> No symbol table info available. > >> #19 0x0000563604cb20f7 in CGisListDB::CGisListDB(QWidget*) () > >> No symbol table info available. > >> #20 0x0000563604cadf32 in Ui_IGisDatabase::setupUi(QWidget*) () > >> No symbol table info available. > >> #21 0x0000563604cada0b in CGisDatabase::CGisDatabase(QWidget*) () > >> No symbol table info available. > >> #22 0x0000563604c7527f in CMainWindow::CMainWindow() () > >> No symbol table info available. > >> #23 0x0000563604c6b4b0 in main () > >> No symbol table info available. > >> --- source code stack trace --- > >> #0 0x00007f598819bd3a in QCoreApplication::postEvent(QObject*, QEvent*, > >> int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #1 0x0000563604ce27a6 in CDBProject::~CDBProject() () > >> #2 0x0000563604ce2839 in CDBProject::~CDBProject() () > >> #3 0x0000563604cc31be in CGisListWks::slotLoadWorkspace() () > >> #4 0x00007f59881c75b5 in QMetaObject::activate(QObject*, int, int, > >> void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #5 0x00007f59881d4113 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #6 0x00007f59881c80db in QObject::event(QEvent*) () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #7 0x00007f5988f1682c in QApplicationPrivate::notify_helper(QObject*, > >> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> #8 0x00007f5988f1e0f4 in QApplication::notify(QObject*, QEvent*) () > >> from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> #9 0x00007f59881989a8 in QCoreApplication::notifyInternal2(QObject*, > >> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #10 0x00007f59881f0d8e in QTimerInfoList::activateTimers() () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #11 0x00007f59881f1551 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #12 0x00007f597c9ec287 in g_main_context_dispatch () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> #13 0x00007f597c9ec4c0 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> #14 0x00007f597c9ec54c in g_main_context_iteration () from > >> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > >> #15 0x00007f59881f18ef in > >> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) > >> () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #16 0x00007f59881969ea in > >> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from > >> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > >> #17 0x00007f5989100ec7 in QDialog::exec() () from > >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> #18 0x00007f5989135355 in ?? () from > >> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > >> #19 0x0000563604cb20f7 in CGisListDB::CGisListDB(QWidget*) () > >> #20 0x0000563604cadf32 in Ui_IGisDatabase::setupUi(QWidget*) () > >> #21 0x0000563604cada0b in CGisDatabase::CGisDatabase(QWidget*) () > >> #22 0x0000563604c7527f in CMainWindow::CMainWindow() () > >> #23 0x0000563604c6b4b0 in main () > >> > >> > >> > >> > >> On 07/17/2018 01:14 AM, Oliver Eichler wrote: > >>> Hi, > >>> > >>> yes, there should be a QT5 Sql package. But I doubt that it is the root > >>> cause for the segfault. But give it a try. > >>> > >>> If it does not help, I need a backtrace. > >>> > >>> Oliver > >>> > >>>> Gesendet: Dienstag, 17. Juli 2018 um 04:22 Uhr > >>>> Von: brad <[email protected]> > >>>> An: "QMapShack MailingList" <[email protected]> > >>>> Betreff: [Qlandkartegt-users] seg fault, sql? > >>>> > >>>> I just upgraded from xubuntu 16.xx to 18.04 and updated qmapshack to > >>>> 1.10.0-1 with synaptic and it's seg faulting when I run it. Is there an > >>>> sql package I need to install? > >>>> > >>>> dt1:qmapshack -f > >>>> 2018-07-16 20:15:06.333 [warning] "no file found for translations > >>>> '/usr/share/qt5/translations/qt_en' (using default)." > >>>> 2018-07-16 20:15:06.346 [warning] "no file found for translations > >>>> '/usr/share/qmapshack/translations/qmapshack_en' (using default)." > >>>> 2018-07-16 20:15:07.183 [warning] libpng warning: iCCP: known incorrect > >>>> sRGB profile > >>>> 2018-07-16 20:15:07.184 [warning] libpng warning: iCCP: known incorrect > >>>> sRGB profile > >>>> 2018-07-16 20:15:10.115 [warning] QSqlQuery::prepare: database not open > >>>> 2018-07-16 20:15:10.115 [warning] Execution of SQL-Statement ` "" ` > >>>> failed: > >>>> 2018-07-16 20:15:10.115 [warning] QSqlError("", "Driver not loaded", > >>>> "Driver not loaded") > >>>> Segmentation fault (core dumped) > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> Check out the vibrant tech community on one of the world's most > >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >>>> _______________________________________________ > >>>> Qlandkartegt-users mailing list > >>>> [email protected] > >>>> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > >>>> > >> > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
