Bug 345040 - Calligra Sheets crash KDE5 Kubuntu 15.04 Beta
Summary: Calligra Sheets crash KDE5 Kubuntu 15.04 Beta
Status: RESOLVED DUPLICATE of bug 343659
Alias: None
Product: calligrasheets
Classification: Applications
Component: general (show other bugs)
Version: 2.9.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-03-11 06:39 UTC by kratez
Modified: 2015-03-11 09:10 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 kratez 2015-03-11 06:39:26 UTC
Application: calligrasheets (2.9.0)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 3.19.0-7-generic x86_64
Distribution: Ubuntu Vivid Vervet (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Simple math operation on a almos new blank document. I was put some values and make some sums and the app suddenly crash

-- Backtrace:
Application: Calligra Sheets (calligrasheets), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feb9f44a800 (LWP 4915))]

Thread 2 (Thread 0x7feb7bbed700 (LWP 4916)):
#0  0x00007feb9eeaf0cd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007feb99e3febc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007feb99e3ffcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007feb9d5ac82e in QEventDispatcherGlib::processEvents (this=0x7feb740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007feb9d57bcd1 in QEventLoop::processEvents (this=this@entry=0x7feb7bbecd80, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007feb9d57c035 in QEventLoop::exec (this=this@entry=0x7feb7bbecd80, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007feb9d46fe89 in QThread::exec (this=this@entry=0x25e1e80) at thread/qthread.cpp:538
#7  0x00007feb9d55c443 in QInotifyFileSystemWatcherEngine::run (this=0x25e1e80) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007feb9d4726ff in QThreadPrivate::start (arg=0x25e1e80) at thread/qthread_unix.cpp:349
#9  0x00007feb9a3260a5 in start_thread (arg=0x7feb7bbed700) at pthread_create.c:309
#10 0x00007feb9eeb957d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7feb9f44a800 (LWP 4915)):
[KCrash Handler]
#6  QWidget::mapFromParent (this=this@entry=0x0, pos=...) at kernel/qwidget.cpp:4325
#7  0x00007feb9dfcab33 in QWidget::mapFrom (this=<optimized out>, parent=0x2b053d0, pos=...) at kernel/qwidget.cpp:4292
#8  0x00007feb907ac742 in ?? () from /usr/lib/kde4/plugins/styles/breeze.so
#9  0x00007feb9d57d2e6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x22df830, receiver=receiver@entry=0x2b053d0, event=event@entry=0x7fff8d7733a0) at kernel/qcoreapplication.cpp:1065
#10 0x00007feb9df8a99c in QApplicationPrivate::notify_helper (this=this@entry=0x22df830, receiver=receiver@entry=0x2b053d0, e=e@entry=0x7fff8d7733a0) at kernel/qapplication.cpp:4566
#11 0x00007feb9df9163f in QApplication::notify (this=<optimized out>, receiver=receiver@entry=0x29aa0e0, e=e@entry=0x7fff8d773680) at kernel/qapplication.cpp:4113
#12 0x00007feb9eb07fd7 in KoApplication::notify (this=<optimized out>, receiver=0x29aa0e0, event=0x7fff8d773680) at /build/buildd/calligra-2.9.0/libs/main/KoApplication.cpp:623
#13 0x00007feb9d57d17d in QCoreApplication::notifyInternal (this=0x7fff8d773f00, receiver=receiver@entry=0x29aa0e0, event=event@entry=0x7fff8d773680) at kernel/qcoreapplication.cpp:955
#14 0x00007feb9df90c9f in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x29aa0e0, event=event@entry=0x7fff8d773680, alienWidget=alienWidget@entry=0x29aa0e0, nativeWidget=nativeWidget@entry=0x25bcd60, buttonDown=buttonDown@entry=0x7feb9eab8578 <qt_button_down>, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178
#16 0x00007feb9e00a9a2 in QETWidget::translateMouseEvent (this=this@entry=0x25bcd60, event=event@entry=0x7fff8d7739e0) at kernel/qapplication_x11.cpp:4632
#17 0x00007feb9e00a24c in QApplication::x11ProcessEvent (this=0x7fff8d773f00, event=event@entry=0x7fff8d7739e0) at kernel/qapplication_x11.cpp:3626
#18 0x00007feb9e032ba2 in x11EventSourceDispatch (s=0x22e0370, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#19 0x00007feb99e3fc3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007feb99e3ff20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007feb99e3ffcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007feb9d5ac80e in QEventDispatcherGlib::processEvents (this=0x2276be0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#23 0x00007feb9e032c66 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007feb9d57bcd1 in QEventLoop::processEvents (this=this@entry=0x7fff8d773dc0, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007feb9d57c035 in QEventLoop::exec (this=this@entry=0x7fff8d773dc0, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007feb9d581ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#27 0x00007feb9df88c1c in QApplication::exec () at kernel/qapplication.cpp:3828
#28 0x00007feb9f186752 in kdemain (argc=1, argv=0x7fff8d774048) at /build/buildd/calligra-2.9.0/sheets/part/Main.cpp:44
#29 0x00007feb9ede0ec5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=1, argv=0x7fff8d774048, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff8d774038) at libc-start.c:287
#30 0x00000000004006fe in _start ()

Possible duplicates by query: bug 344808, bug 344310.

Reported using DrKonqi
Comment 1 Tomas Mecir 2015-03-11 09:10:18 UTC
This is fixed in the upcoming version of the breeze style. As a workaround until then, you can switch to a different widget style.

*** This bug has been marked as a duplicate of bug 343659 ***