Bug 297822

Summary: calligra plan crashes on closing
Product: [Applications] calligraplan Reporter: Robby Engelmann <robby.engelmann>
Component: generalAssignee: Dag Andersen <dag.andersen>
Status: RESOLVED FIXED    
Severity: crash CC: robby.engelmann
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: http://commits.kde.org/calligra/4a302d8df6eb5d5bdc86f49ab11ed2987246d698 Version Fixed In:
Sentry Crash Report:

Description Robby Engelmann 2012-04-10 05:08:43 UTC 
Application: calligraplan (2.4.0)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.3.1-030301-generic-pae i686
Distribution: Ubuntu precise (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Calligra Plan crashed on closing, when the opened file was not yet saved. After clicking "Save" in the appearing dialogue the program crashes

The crash can be reproduced some of the time.

-- Backtrace:
Application: Plan (calligraplan), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb3fec740 (LWP 18558))]

Thread 3 (Thread 0xac0f6b40 (LWP 18568)):
#0  0xb777e424 in __kernel_vsyscall ()
#1  0xb527996b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0xb76a03dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb0245029 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#4  0xb024506f in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#5  0xb5275d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb7692ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xa6a2fb40 (LWP 18569)):
#0  0xb777e424 in __kernel_vsyscall ()
#1  0xb768217b in read () from /lib/i386-linux-gnu/libc.so.6
#2  0xb51e26be in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb51a3af0 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb51a4002 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb51a41c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb65798e7 in QEventDispatcherGlib::processEvents (this=0xac200468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0xb654550d in QEventLoop::processEvents (this=0xa6a2f240, flags=...) at kernel/qeventloop.cpp:149
#8  0xb65457a9 in QEventLoop::exec (this=0xa6a2f240, flags=...) at kernel/qeventloop.cpp:204
#9  0xb642e94c in QThread::exec (this=0x9524c18) at thread/qthread.cpp:501
#10 0xb6522b5d in QInotifyFileSystemWatcherEngine::run (this=0x9524c18) at io/qfilesystemwatcher_inotify.cpp:248
#11 0xb6431de0 in QThreadPrivate::start (arg=0x9524c18) at thread/qthread_unix.cpp:298
#12 0xb5275d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#13 0xb7692ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb3fec740 (LWP 18558)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0xb6560fad in QObject::~QObject (this=0x9030948, __in_chrg=<optimized out>) at kernel/qobject.cpp:854
#9  0xb6561782 in QObject::~QObject (this=0x9030948, __in_chrg=<optimized out>) at kernel/qobject.cpp:940
#10 0xb53035d4 in QDBusConnectionPrivate::deleteYourself (this=0x9030948) at qdbusintegrator.cpp:1033
#11 0xb52faaee in QDBusConnection::~QDBusConnection (this=0x90482dc, __in_chrg=<optimized out>) at qdbusconnection.cpp:304
#12 0xb531ef2d in ~QDBusAbstractInterfacePrivate (this=0x9048290, __in_chrg=<optimized out>) at qdbusabstractinterface_p.h:88
#13 QDBusAbstractInterfacePrivate::~QDBusAbstractInterfacePrivate (this=0x9048290, __in_chrg=<optimized out>) at qdbusabstractinterface_p.h:88
#14 0xb65614bb in cleanup (pointer=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#15 ~QScopedPointer (this=0x90481bc, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#16 QObject::~QObject (this=0x90481b8, __in_chrg=<optimized out>) at kernel/qobject.cpp:817
#17 0xb5319be6 in ~QDBusAbstractInterfaceBase (this=0x90481b8, __in_chrg=<optimized out>) at qdbusabstractinterface.h:67
#18 QDBusAbstractInterface::~QDBusAbstractInterface (this=0x90481b8, __in_chrg=<optimized out>) at qdbusabstractinterface.cpp:329
#19 0xb52ff3d6 in QDBusConnectionInterface::~QDBusConnectionInterface (this=0x90481b8, __in_chrg=<optimized out>) at qdbusconnectioninterface.cpp:177
#20 0xb52ff402 in QDBusConnectionInterface::~QDBusConnectionInterface (this=0x90481b8, __in_chrg=<optimized out>) at qdbusconnectioninterface.cpp:179
#21 0xb655bd11 in QObjectPrivate::deleteChildren (this=0x90309c8) at kernel/qobject.cpp:1908
#22 0xb6561481 in QObject::~QObject (this=0x9030948, __in_chrg=<optimized out>) at kernel/qobject.cpp:927
#23 0xb5309eb9 in QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x9030948, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1003
#24 0xb530a1c2 in QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x9030948, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1021
#25 0xb53035d4 in QDBusConnectionPrivate::deleteYourself (this=0x9030948) at qdbusintegrator.cpp:1033
#26 0xb52faaee in QDBusConnection::~QDBusConnection (this=0x9038e68, __in_chrg=<optimized out>) at qdbusconnection.cpp:304
#27 0xb52fea67 in ~QDBusDefaultConnection (this=<optimized out>, __in_chrg=<optimized out>) at qdbusconnection.cpp:1120
#28 QGlobalStaticDeleter<QDBusDefaultConnection>::~QGlobalStaticDeleter (this=0xb536a648, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1923
#29 0xb75daf61 in ?? () from /lib/i386-linux-gnu/libc.so.6
#30 0xb75dafed in exit () from /lib/i386-linux-gnu/libc.so.6
#31 0xb75c14db in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#32 0x08048531 in _start ()

This bug may be a duplicate of or related to bug 281703.

Possible duplicates by query: bug 281703.

Reported using DrKonqi
Comment 1 Dag Andersen 2012-04-10 09:34:05 UTC 
Arghh, I thought I had fixed this when I cleaned up the dbus interface. I have not had a crash since then.
AFAIK there should be no data loss, as the crash happens after saving has finished.
Can you confirm this?
Comment 2 Robby Engelmann 2012-04-10 10:42:17 UTC 
I can confirm, that there is no data loss. All changes done are saved as far as I checked.
Comment 3 Dag Andersen 2012-04-10 11:12:26 UTC 
Tirsdag den 10. april 2012 10:42:17 skrev du:
> https://bugs.kde.org/show_bug.cgi?id=297822
> 
> Robby Engelmann <robby.engelmann@igfs-ev.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |robby.engelmann@igfs-ev.de
> 
> --- Comment #2 from Robby Engelmann <robby.engelmann@igfs-ev.de> ---
> I can confirm, that there is no data loss. All changes done are saved as far
> as I checked.
Ok, good. Will have to live with it for the 2.4.0 release then.
Comment 4 Dag Andersen 2012-05-22 09:32:03 UTC 
Git commit 4a302d8df6eb5d5bdc86f49ab11ed2987246d698 by Dag Andersen.
Committed on 22/05/2012 at 11:27.
Pushed by danders into branch 'master'.

Fix crash due to notification during file save

The reason is a notification issued in KoDocument::saveFile() which results in an async dbus message.
The reply to this message can be received (timing dependent) during deletion of the dbus conection in which case it will crash.

Also remove sheets.notifyrc file from sheets.

Review: https://git.reviewboard.kde.org/r/105010

M  +0    -7    libs/main/KoDocument.cpp
M  +1    -1    sheets/CMakeLists.txt
D  +0    -273  sheets/sheets.notifyrc

http://commits.kde.org/calligra/4a302d8df6eb5d5bdc86f49ab11ed2987246d698