Okular crashes while starting the presentation mode

Bug #323908 reported by sputnik
8
Affects Status Importance Assigned to Milestone
KDE Graphics
Fix Released
High
kdegraphics (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

KDE Version 0.8 (KDE 4.2.00 (KDE 4.2.0), Kubuntu packages)
 Application Universal document viewer
 Operating System Linux (i686) release 2.6.27-11-generic
 Compiler cc

okular:
  Installiert: 4:4.2.0-0ubuntu1~intrepid1~ppa3

This is the backtrace:

Anwendung: Okular (okular), Signal SIGABRT

Thread 1 (Thread 0xb60db8d0 (LWP 4322)):
[KCrash Handler]
#6 0xb7fd3430 in __kernel_vsyscall ()
#7 0xb67998a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb679b268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7341795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7341872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb73418cc in qt_assert_x () from /usr/lib/libQtCore.so.4
#12 0xb4728a89 in PresentationWidget::changePage (this=0x85a9fc8, newPage=0) at /usr/include/qt4/QtCore/qvector.h:325
#13 0xb4729b66 in PresentationWidget::mousePressEvent (this=0x85a9fc8, e=0xbfdd2538) at /build/buildd/kdegraphics-4.2.0/okular/ui/presentationwidget.cpp:464
#14 0xb6b81949 in QWidget::event () from /usr/lib/libQtGui.so.4
#15 0xb47230c3 in PresentationWidget::event (this=0x85a9fc8, e=0xbfdd2538) at /build/buildd/kdegraphics-4.2.0/okular/ui/presentationwidget.cpp:393
#16 0xb6b298ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#17 0xb6b320e1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0xb79db06d in KApplication::notify (this=0xbfdd2e4c, receiver=0x85a9fc8, event=0xbfdd2538) at /build/buildd/kde4libs-4.2.0/kdeui/kernel/kapplication.cpp:307
#19 0xb7439e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#20 0xb6b3136e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#21 0xb6b9b656 in ?? () from /usr/lib/libQtGui.so.4
#22 0xb6b9a9e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#23 0xb6bc47aa in ?? () from /usr/lib/libQtGui.so.4
#24 0xb64116f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb6414da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb6414f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb7464478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb6bc3ea5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb743852a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb74386ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb743ada5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6b29767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x0804e497 in main (argc=) at /build/buildd/kdegraphics-4.2.0/okular/shell/main.cpp:81

Changed in okular:
importance: Undecided → Low
status: New → Triaged
Changed in kdegraphics:
status: Unknown → New
Revision history for this message
Giovanni Masucci (gio-grifis) wrote :

Hello,
I can confirm your bug (desktop effects ON, intel card) on intrepid with 4.2 packages.
Could you please try to REMOVE the costum okular rule in kwin settings?
To do so:
- Close okular
- Open System Settings
- Click on "Window behaviour"
- Click on "Window-Specific"
- You'll see a list: look for okular, select it, click on "remove" and then Apply.
- Open okular and try again presentation mode
Is the crash fixed?

Revision history for this message
sputnik (sputnik) wrote :

Hello Giovanni!

This solves the problem! - Thank you very much for your idea and answer! - For me this works!

Changed in kdegraphics:
status: New → Fix Released
Revision history for this message
Jorge Olivares Rossetti (jorge-rossetti) wrote :

Hello Giovanni, the problem is not only with Intel Cards, I have an ATI X1400 GPU and it happens the same. Fortunately the solution you have post works too!!.

Thanks!

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in KDE 4.2.2

Changed in kdegraphics (Ubuntu):
status: Triaged → Fix Released
Changed in kdegraphics:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.