Bug 346197

Summary:	Calligra Words crash when changing pagelayout
Product:	[Applications] calligrawords	Reporter:	wingfielda
Component:	general	Assignee:	Calligra Words Bugs <calligra-words-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	cbo
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	attachment-31362-0.html

Description wingfielda 2015-04-15 01:47:11 UTC

Application: calligrawords (2.9.1)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.16.7-7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
attempted to change the page layout from A4 to Letter on an existing docement. Also you are not able to force a diffrent layout when you print a document.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007f86ab23d871 in KWPage::isValid() const () at /usr/lib64/libwordsprivate.so.14
#6  0x00007f86ab23d8b0 in KWPage::setVisiblePageNumber(int) () at /usr/lib64/libwordsprivate.so.14
#7  0x00007f86ab2606a3 in  () at /usr/lib64/libwordsprivate.so.14
#8  0x00007f86b207594b in KoTextDocumentLayout::doLayout() () at /usr/lib64/libkotextlayout.so.14
#9  0x00007f86b20761a8 in KoTextDocumentLayout::layout() () at /usr/lib64/libkotextlayout.so.14
#10 0x00007f86c68be59e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#11 0x00007f86c5a2276c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#12 0x00007f86c5a28cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#13 0x00007f86b25dd227 in KoApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkomain.so.14
#14 0x00007f86c68a62ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4
#15 0x00007f86c68a957d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#16 0x00007f86c68d38fe in  () at /usr/lib64/libQtCore.so.4
#17 0x00007f86c2385a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f86c2385c48 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f86c2385cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#20 0x00007f86c68d30be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#21 0x00007f86c5abf676 in  () at /usr/lib64/libQtGui.so.4
#22 0x00007f86c68a4e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#23 0x00007f86c68a5165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#24 0x00007f86c68aa5b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4
#25 0x00007f86b288ef65 in kdemain () at /usr/lib64/libkdeinit4_calligrawords.so
#26 0x0000000000408815 in _start ()

Reported using DrKonqi

Comment 1 Camilla Boemann 2015-04-15 06:12:23 UTC

upgrade to 2.9.2 - bug is already solved

Comment 2 wingfielda 2015-04-15 06:24:49 UTC

Created attachment 92037 [details]
attachment-31362-0.html

Is there a work around for this issue?  OpenSUSE has just updated to 2.9.1.
There is no 2.9.2 in the unstable branch for KDE:EXTRA or for Tumbleweed.

Thank-you in advance

Adam

On Wed, Apr 15, 2015 at 2:12 AM, Camilla Boemann <cbo@boemann.dk> wrote:

> https://bugs.kde.org/show_bug.cgi?id=346197
>
> Camilla Boemann <cbo@boemann.dk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |cbo@boemann.dk
>          Resolution|---                         |WORKSFORME
>              Status|UNCONFIRMED                 |RESOLVED
>
> --- Comment #1 from Camilla Boemann <cbo@boemann.dk> ---
> upgrade to 2.9.2 - bug is already solved
>
> --
> You are receiving this mail because:
> You reported the bug.
>

Comment 3 Camilla Boemann 2015-04-15 06:26:26 UTC

Not except not doing any page formatting at all :(