Re: Segment violation on Quartus II 13.0sp1 - Fedora 26

Altera_Forum · ‎08-15-2017

After upgrading to Fedora 26 was working, but then some minor package updates seem to have broken it. Command line tools still work but would like to get UI working. Any ideas? Stack trace below.

I would upgrade to a newer version of Quartus except we still use some DE2-70's at school so I need Quartus 13 for grading.

 
 *** Fatal Error: Segment Violation at 0x5
 Module: quartus
 Stack Trace:
 
 
     0xd3c1c: QSslCertificate::fromData(QByteArray const&, QSsl::EncodingFormat) + 0x4c (QtNetwork.so.4)
     0xd442e: QSslCertificate::fromPath(QString const&, QSsl::EncodingFormat, QRegExp::PatternSyntax) + 0x74e (QtNetwork.so.4)
 
 
     0xd35bf: QSslCertificate::QSslCertificate(QByteArray const&, QSsl::EncodingFormat) + 0x8f (QtNetwork.so.4)
 
 
     0xdf973: QSslSocket::QSslSocket(QObject*) + 0x33 (QtNetwork.so.4)
 
 
 
 
 
    0x18f960: QMetaCallEvent::placeMetaCall(QObject*) + 0x40 (QtCore.so.4)
    0x193feb: QObject::event(QEvent*) + 0x22b (QtCore.so.4)
    0x1566b4: QApplicationPrivate::notify_helper(QObject*, QEvent*) + 0xb4 (QtGui.so.4)
    0x15b31e: QApplication::notify(QObject*, QEvent*) + 0x15e (QtGui.so.4)
    0x17defb: QCoreApplication::notifyInternal(QObject*, QEvent*) + 0x7b (QtCore.so.4)
    0x1818e5: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 0x355 (QtCore.so.4)
    0x181c4d: QCoreApplication::sendPostedEvents(QObject*, int) + 0x2d (QtCore.so.4)
 
    0x17caa9: QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 0x49 (QtCore.so.4)
    0x17cdba: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 0x16a (QtCore.so.4)
    0x181d0f: QCoreApplication::exec() + 0xaf (QtCore.so.4)
    0x154507: QApplication::exec() + 0x27 (QtGui.so.4)
      0x645f: __gxx_personality_v0 + 0x367 (quartus)
     0x23908: msg_main_thread(void*) + 0x18 (ccl_msg)
      0x5f9e: thr_final_wrapper + 0xe (ccl_thr)
     0x24625: msg_thread_wrapper(void* (*)(void*), void*) + 0x6c (ccl_msg)
     0x15e1d: mem_thread_wrapper(void* (*)(void*), void*) + 0xdd (quartus)
      0xffd8: err_thread_wrapper(void* (*)(void*), void*) + 0x2a (ccl_err)
      0x63fa: thr_thread_wrapper + 0x2f (ccl_thr)
     0x36e9a: msg_exe_main(int, char const**, int (*)(int, char const**)) + 0xb7 (ccl_msg)
      0x6531: __gxx_personality_v0 + 0x439 (quartus)
     0x182f3: __libc_start_main + 0xf3 (c.so.6)
      0x6311: __gxx_personality_v0 + 0x219 (quartus)
 
 End-trace
 
 Quartus II 32-bit Version 13.0.1 Build 232 06/12/2013 SJ Web Edition
 Service Pack Installed:  1

Altera_Forum · ‎08-24-2017

HipChat has a similiar issue, with a workaround here: https://jira.atlassian.com/browse/hcpub-3280?focusedcommentid=1565619&page=com.atlassian.jira.plugin.system.issuetabpanels%3acomment-tabpanel#comment-1565619

Creating the specified symlinks in the linux64 directory fixed the problem for now