Hello. Thank you for your report. Unfortunately the backtrace is not complete. Could you install debugging packages provided by your distribution and reproduce the crash please? Instructions are given in this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports . Thanks.

Were you actually printing or just doing the print preview?

here the same with print preview.. I can't print any pdf :(

Anwendung: Okular (okular), Signal SIGSEGV
[?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f4c6d568700 (LWP 19002)]
[KCrash handler]
#5  0x00007f4c60a69308 in ?? () from /usr/lib64/kde4/okularGenerator_poppler.so
#6  0x00007f4c63c5980a in ?? () from /usr/lib64/kde4/okularpart.so
#7  0x00007f4c63c59d87 in ?? () from /usr/lib64/kde4/okularpart.so
#8  0x00007f4c63c6259d in ?? () from /usr/lib64/kde4/okularpart.so
#9  0x00007f4c6b90ce50 in QMetaObject::activate (sender=0x761090, 
    from_signal_index=<value optimized out>, to_signal_index=6, argv=0x660064)
    at kernel/qobject.cpp:3013
#10 0x00007f4c68b7fdb7 in QAction::triggered (this=0x7fff75599690, _t1=false)
    at .moc/release-shared/moc_qaction.cpp:216
#11 0x00007f4c68b80570 in QAction::activate (this=0x761090, 
    event=<value optimized out>) at kernel/qaction.cpp:1119
#12 0x00007f4c68ec79b3 in QMenuPrivate::activateAction (this=0x769150, 
    action=0x761090, action_e=QAction::Trigger, self=true)
    at widgets/qmenu.cpp:1005
#13 0x00007f4c6cc06f01 in KMenu::mouseReleaseEvent (this=0x74fea0, 
    e=0x7fff755996e0)
    at /usr/src/debug/kdelibs-4.1.0/kdeui/widgets/kmenu.cpp:452
#14 0x00007f4c68bd1eb4 in QWidget::event (this=0x7fff75599690, 
    event=0x7fff7559a520) at kernel/qwidget.cpp:7021
#15 0x00007f4c68ec8efb in QMenu::event (this=0x74fea0, e=0x7fff7559a520)
    at widgets/qmenu.cpp:2265
#16 0x00007f4c68b84ebd in QApplicationPrivate::notify_helper (this=0x624ab0, 
    receiver=0x74fea0, e=0x7fff7559a520) at kernel/qapplication.cpp:3800
#17 0x00007f4c68b8baf6 in QApplication::notify (this=<value optimized out>, 
    receiver=0x74fea0, e=0x7fff7559a520) at kernel/qapplication.cpp:3527
#18 0x00007f4c6cb53d1b in KApplication::notify (this=0x7fff7559b170, 
    receiver=0x74fea0, event=0x7fff7559a520)
    at /usr/src/debug/kdelibs-4.1.0/kdeui/kernel/kapplication.cpp:311
#19 0x00007f4c6b8fb78c in QCoreApplication::notifyInternal (
    this=0x7fff7559b170, receiver=0x74fea0, event=0x7fff7559a520)
    at kernel/qcoreapplication.cpp:587
#20 0x00007f4c68b8cea8 in QApplicationPrivate::sendMouseEvent (
    receiver=0x74fea0, event=0x7fff7559a520, alienWidget=0x0, 
    nativeWidget=0x74fea0, buttonDown=<value optimized out>, 
    lastMouseReceiver=@0x7f4c6941b6a0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#21 0x00007f4c68be34bb in QETWidget::translateMouseEvent (this=0x74fea0, 
    event=<value optimized out>) at kernel/qapplication_x11.cpp:3980
#22 0x00007f4c68be1f1b in QApplication::x11ProcessEvent (this=0x7fff7559b170, 
    event=0x7fff7559afa0) at kernel/qapplication_x11.cpp:3164
#23 0x00007f4c68c05ffc in QEventDispatcherX11::processEvents (this=0x624770, 
    flags={i = 1968812208}) at kernel/qeventdispatcher_x11.cpp:134
#24 0x00007f4c6b8fa0e2 in QEventLoop::processEvents (
    this=<value optimized out>, flags={i = 1968812256})
    at kernel/qeventloop.cpp:149
#25 0x00007f4c6b8fa275 in QEventLoop::exec (this=0x7fff7559b120, flags=
      {i = 1968812336}) at kernel/qeventloop.cpp:196
#26 0x00007f4c6b8fc315 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:849
#27 0x0000000000407a64 in _start ()
#0  0x00007f4c67597261 in nanosleep () from /lib64/libc.so.6

@sts (comment #3):
please please please, please, please, *read* comment #1 and follow the linked instructions. Crying with an unuseful backtrace is not going to help us. Thanks.

Hi,

It appears that the SuSE debugger doesn't produce any more information 
so I've tried to run okular inside gdb as suggested.

However, I'm not sure which bits you're interested in so I've copied the 
last bit where it falls over.

Can I just point out that okular is now not allowing me to print to the 
printer and simply prints to a local file. However, it did use to print 
to the printer so something's obviously got scrambled.

Anyway, for what it's worth...


(no debugging symbols found) 
 

(no debugging symbols found) 
 

[New Thread 0xb2b3bb90 (LWP 3437)] 
 

[New Thread 0xb333cb90 (LWP 3438)] 
 

[Thread 0xb2b3bb90 (LWP 3437) exited] 
 

[Thread 0xb333cb90 (LWP 3438) exited] 
 

(no debugging symbols found) 
 

(no debugging symbols found) 
 

(no debugging symbols found) 
 

---Type <return> to continue, or q <return> to quit--- 
 

(no debugging symbols found) 
 

(no debugging symbols found) 
 

[New Thread 0xb333cb90 (LWP 3445)] 
 

rangecheck -15 
 

okular(3432)/okular (Spectre) GSRendererThread::run: Generated image 
does not match wanted size  0   8   0   12 

QImage::scaled: Image is a null image 
 

syntaxerror -18 
 

okular(3432)/okular (Spectre) GSRendererThread::run: Generated image 
does not match wanted size  0   29   0   42 

QImage::scaled: Image is a null image 
 

syntaxerror -18 
 

okular(3432)/okular (Spectre) GSRendererThread::run: Generated image 
does not match wanted size  0   78   0   110 

QImage::scaled: Image is a null image 
 

syntaxerror -18 
 

okular(3432)/okular (Spectre) GSRendererThread::run: Generated image 
does not match wanted size  0   231   0   327 

QImage::scaled: Image is a null image 
 

syntaxerror -18 
 

okular(3432)/okular (Spectre) GSRendererThread::run: Generated image 
does not match wanted size  0   450   0   638 

QImage::scaled: Image is a null image 
 

[New Thread 0xb2b3bb90 (LWP 3446)] 
 

[New Thread 0xb1bd6b90 (LWP 3447)] 
 


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb65756d0 (LWP 3432)]
0xb6c1c563 in QWidget::windowTitle () from /usr/lib/libQtGui.so.4


Regards
Andy Bennett



Pino Toscano wrote:
[bugs.kde.org quoted mail]

Hi girobank,

unfortunately the output you posted is not that useful.
What you could do (if it is not what you already did) is:
$ gdb --args okular somedocument.pdf
(gdb) run
then work normally, waiting that it stucks
(gdb) thread apply all bt
and then paste its output here
(to quit gdb, write "quit" at its prompt.)

The second backtrace looks like the backtrace of bug #167822 to me...

(In reply to comment #7)
> The second backtrace looks like the backtrace of bug #167822 to me...

I guess you mean bug #167882, no? :)

I'm sure okular is heavily related to the "cdr-device without motor" :o)

Thanks for spotting this, your bug # is the correct one.

Any news about this problem?
Does it still happen with more recent Okular versions?

I haven't seen it with 4.1.3

FYI I am not using KDE now with SuSE and have changed to Ubuntu. I may change back at some point and will try it then

Thanks/Regards