Bug 19720 - skrooge stopped working (crash)
Summary: skrooge stopped working (crash)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-04 17:54 CET by Pana Sum
Modified: 2016-11-04 22:27 CET (History)
1 user (show)

See Also:
Source RPM: skrooge-2.5.0-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Pana Sum 2016-11-04 17:54:25 CET
Description of problem:
skrooge crashes right after opening it. It does not show any window.
I think it started crashing after yesterday updates.

Backtrace:
Application: Skrooge (skrooge), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8a3c161840 (LWP 6668))]

Thread 3 (Thread 0x7f8a311ac700 (LWP 6671)):
#0  0x00007f8a4fbf5f9d in poll () at /lib64/libc.so.6
#1  0x00007f8a4b40fa54 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f8a4b40fb5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f8a504fe8fb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007f8a504a9f3a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007f8a502e335c in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00007f8a4d1cd615 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#7  0x00007f8a502e7f99 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#8  0x00007f8a4bb4966d in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8a4fc01ded in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f8a3275e700 (LWP 6669)):
#0  0x00007f8a4fbf5f9d in poll () at /lib64/libc.so.6
#1  0x00007f8a43ed3902 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x00007f8a43ed5657 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x00007f8a3492a779 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x00007f8a502e7f99 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5  0x00007f8a4bb4966d in start_thread () at /lib64/libpthread.so.0
#6  0x00007f8a4fc01ded in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f8a3c161840 (LWP 6668)):
[KCrash Handler]
#6  0x00007f8a4fb3f828 in raise () at /lib64/libc.so.6
#7  0x00007f8a4fb40f3a in abort () at /lib64/libc.so.6
#8  0x000000000040432b in SKGMessageOutput(QtMsgType, QMessageLogContext const&, QString const&) ()
#9  0x00007f8a502ce648 in qt_message(QtMsgType, QMessageLogContext const&, char const*, __va_list_tag*) () at /lib64/libQt5Core.so.5
#10 0x00007f8a502cfed6 in QMessageLogger::fatal(char const*, ...) const () at /lib64/libQt5Core.so.5
#11 0x00007f8a504d4c4d in  () at /lib64/libQt5Core.so.5
#12 0x00007f8a307647c8 in QSQLiteDriver::QSQLiteDriver(QObject*) () at /usr/lib64/qt5/plugins/sqldrivers/libskgsqlcipher.so
#13 0x00007f8a3076305f in SKGSQLCipherDriverPlugin::create(QString const&) () at /usr/lib64/qt5/plugins/sqldrivers/libskgsqlcipher.so
#14 0x00007f8a52532da2 in QSqlDatabasePrivate::init(QString const&) () at /lib64/libQt5Sql.so.5
#15 0x00007f8a52533291 in QSqlDatabase::addDatabase(QString const&, QString const&) () at /lib64/libQt5Sql.so.5
#16 0x00007f8a51c9fd0e in SKGDocument::load(QString const&, QString const&, bool, bool) () at /lib64/libskgbasemodeler.so.2
#17 0x00007f8a51c89ea7 in SKGDocument::initialize() () at /lib64/libskgbasemodeler.so.2
#18 0x0000000000403c83 in main ()



Version-Release number of selected component (if applicable):
2.5.0

How reproducible:
Always

Steps to Reproduce:
1. Install yesterday updates
2. Open skrooge
3.
Comment 1 David GEIGER 2016-11-04 18:14:05 CET
This come from new Qt 5.6.2 stack update, so should be fixed in next skrooge update!

CC: (none) => geiger.david68210

Comment 2 David GEIGER 2016-11-04 22:27:16 CET
I confirm that it is fixed now!

So closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.