Bug 305641 - Okteta crash when shutting system down from KDE menu
Summary: Okteta crash when shutting system down from KDE menu
Status: RESOLVED WORKSFORME
Alias: None
Product: okteta
Classification: Applications
Component: general (other bugs)
Version First Reported In: 0.9.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Friedrich W. H. Kossebau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-23 00:09 UTC by titombitel
Modified: 2021-01-03 04:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description titombitel 2012-08-23 00:09:12 UTC
Application: okteta (0.9.0)
KDE Platform Version: 4.9.00 "release 559"
Qt Version: 4.8.2
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Opened a mp3 file, no editions, no save. Okteta was idle for few hours. Segfault occured when the system was shutting down.

- Unusual behavior I noticed:
Segfault occured when the GUI was almost shut down. There were no window decorations visible and no ability to move windows. Like if KWin ended its job but X still running.

-- Backtrace:
Application: Okteta (okteta), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f142abce760 (LWP 5169))]

Thread 2 (Thread 0x7f141864d700 (LWP 5170)):
#0  0x00007f142392e014 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x00007f142239fba3 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f14223a097d in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f14223a0fa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f1428d29e36 in QEventDispatcherGlib::processEvents (this=0x7f14100008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#5  0x00007f1428cf9842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f1428cf9a97 in QEventLoop::exec (this=0x7f141864cdf0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f1428bf95f7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x00007f1428cd962f in QInotifyFileSystemWatcherEngine::run (this=0xd82ba0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f1428bfc61b in QThreadPrivate::start (arg=0xd82ba0) at thread/qthread_unix.cpp:307
#10 0x00007f142392bf05 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f14278e110d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f142abce760 (LWP 5169)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007f142a040dad in Kasten2::ModifiedBarController::onSynchronizerDeleted (this=0x8375a0, synchronizer=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/controllers/document/modified/modifiedbarcontroller.cpp:184
#8  0x00007f142a03b9ac in Kasten2::ModifiedBarController::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/build/okteta/libs/kasten/controllers/moc_modifiedbarcontroller.cpp:65
#9  0x00007f1428d0ec41 in QMetaObject::activate (sender=0x804960, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffb4f09050) at kernel/qobject.cpp:3556
#10 0x00007f1428d0f59f in QObject::destroyed (this=<optimized out>, _t1=0x804960) at .moc/release-shared/moc_qobject.cpp:149
#11 0x00007f1428d1304e in QObject::~QObject (this=0x804960, __in_chrg=<optimized out>) at kernel/qobject.cpp:844
#12 0x00007f142a25f917 in ~ByteArrayRawFileSynchronizer (this=0x804960, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/kasten/core/io/filesystem/bytearrayrawfilesynchronizer.h:37
#13 Kasten2::ByteArrayRawFileSynchronizer::~ByteArrayRawFileSynchronizer (this=0x804960, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/kasten/core/io/filesystem/bytearrayrawfilesynchronizer.h:37
#14 0x00007f1429bcc69d in ~AbstractDocumentPrivate (this=0x7f140c002590, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/core/document/abstractdocument_p.h:85
#15 Kasten2::AbstractDocumentPrivate::~AbstractDocumentPrivate (this=0x7f140c002590, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/core/document/abstractdocument_p.h:86
#16 0x00007f1429bcc361 in Kasten2::AbstractModel::~AbstractModel (this=0x7f140c002310, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/core/document/abstractmodel.cpp:57
#17 0x00007f142a260619 in Kasten2::ByteArrayDocument::~ByteArrayDocument (this=0x7f140c002310, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/kasten/core/document/bytearraydocument.cpp:138
#18 0x00007f1429bd16be in qDeleteAll<QList<Kasten2::AbstractDocument*>::const_iterator> (end=<optimized out>, begin=<optimized out>) at /usr/include/QtCore/qalgorithms.h:322
#19 qDeleteAll<QList<Kasten2::AbstractDocument*> > (c=...) at /usr/include/QtCore/qalgorithms.h:330
#20 Kasten2::DocumentManager::~DocumentManager (this=0x61da10, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/core/system/documentmanager.cpp:189
#21 0x00007f1429bd1719 in Kasten2::DocumentManager::~DocumentManager (this=0x61da10, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/libs/kasten/core/system/documentmanager.cpp:194
#22 0x0000000000409e32 in Kasten2::OktetaProgram::~OktetaProgram (this=0x7fffb4f09160, __in_chrg=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/program/program.cpp:151
#23 0x0000000000409694 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kdesdk-4.9.0/okteta/program/main.cpp:29

Reported using DrKonqi
Comment 1 Friedrich W. H. Kossebau 2012-08-23 19:05:58 UTC
Thanks for the report. I have seen this before, so this seems to be not just a local issue just for me.

Do you use session management, so that the running programs are automatically restarted on relogin? And it does not crash if you close a similar Okteta windpw yourself, right?
Comment 2 titombitel 2012-08-23 22:55:13 UTC
>Do you use session management
I do. That's default in KDE as far as i know.

> And it does not crash if you close a similar Okteta windpw yourself, right?
It doesn't.


I've done some research on an almost unused user accout. I had been logging out with Okteta running (and other KDE stuff like Akonadi, etc.).
C means crash, P means pass (no crash)

Test: logging out while having Okteta running with a file opened.

Case 1: file contained 50 NULL chars (00h):
C, C, C, C, C => 5 crashes, 5 tests, 100%

Case 2: No file opened:
P, P, P, P, P => 0 crashes, 5 tests, 0%

Case 3: file contained 1 NULL character:
C, C, P, P, P, P, C, P, P, P => 3 crashes, 10 tests, 30%
Comment 3 Justin Zobel 2020-12-04 05:04:34 UTC
Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 4 Bug Janitor Service 2020-12-19 04:34:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2021-01-03 04:34:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!