Quassel IRC

phuzion wrote:

This was reported downstream to Fedora's bug tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2072127

Original bug report text from RHBZ:

Description of problem:
The application was in the background and unused for a relatively extended period of time when this error occured.

Version-Release number of selected component:
quassel-client-0.14.0-1.fc35

Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cmdline: quasselclient
crash_function: MessageModel::changeOfDay
executable: /usr/bin/quasselclient
journald_cursor: s=1fb5515a883d4f619e17f058f92eaec6;i=2ac7e;b=5c8798c1cfc54de69b304cb05ff3282c;m=2590b85761;t=5dbea0ef32555;x=577f48bc9571d990
kernel: 5.16.18-200.fc35.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1337

Truncated backtrace:
Thread no. 1 (10 frames)
#0 MessageModel::changeOfDay at /usr/src/debug/quassel-0.14.0-1.fc35.x86_64/src/client/messagemodel.cpp:368
#1 QtPrivate::QSlotObjectBase::call at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#2 doActivate<false> at kernel/qobject.cpp:3886
#3 QMetaObject::activate at kernel/qobject.cpp:3946
#4 QTimer::timeout at .moc/moc_qtimer.cpp:205
#5 QObject::event at kernel/qobject.cpp:1336
#6 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3632
#7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1064
#8 QTimerInfoList::activateTimers at kernel/qtimerinfo_unix.cpp:643
#9 timerSourceDispatch at kernel/qeventdispatcher_glib.cpp:183

This bug may be fixed thanks to https://github.com/quassel/quassel/pull/603.

Thanks for sharing the bug report details! It looks like the issue with `quassel-client-0.14.0-1.fc35` causing a crash in `MessageModel::changeOfDay` might be resolved thanks to the pull request on GitHub.

Is there anything specific you'd like to discuss or need help with regarding this bug?

phuzion wrote:

This was reported downstream to Fedora's bug tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2072127

Original bug report text from RHBZ:

Description of problem:
The application was in the background and unused for a relatively extended period of time when this error occured.

Version-Release number of selected component:
quassel-client-0.14.0-1.fc35

Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cmdline: quasselclient
crash_function: MessageModel::changeOfDay
executable: /usr/bin/quasselclient
journald_cursor: s=1fb5515a883d4f619e17f058f92eaec6;i=2ac7e;b=5c8798c1cfc54de69b304cb05ff3282c;m=2590b85761;t=5dbea0ef32555;x=577f48bc9571d990
kernel: 5.16.18-200.fc35.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1337

Truncated backtrace:
Thread no. 1 (10 frames)
#0 MessageModel::changeOfDay at /usr/src/debug/quassel-0.14.0-1.fc35.x86_64/src/client/messagemodel.cpp:368
#1 QtPrivate::QSlotObjectBase::call at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#2 doActivate<false> at kernel/qobject.cpp:3886
#3 QMetaObject::activate at kernel/qobject.cpp:3946
#4 QTimer::timeout at .moc/moc_qtimer.cpp:205
#5 QObject::event at kernel/qobject.cpp:1336
#6 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3632
#7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1064
#8 QTimerInfoList::activateTimers at kernel/qtimerinfo_unix.cpp:643
#9 timerSourceDispatch at kernel/qeventdispatcher_glib.cpp:183 https://www.marlboro-rewards.com

This bug may be fixed thanks to https://github.com/quassel/quassel/pull/603.

Thanks for sharing the bug report details! It looks like the issue with `quassel-client-0.14.0-1.fc35` causing a crash in `MessageModel::changeOfDay` might be resolved thanks to the pull request on GitHub.