Bug 160372 - Okular crashes on the attached EPS
Summary: Okular crashes on the attached EPS
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-04 19:27 UTC by Praveen Srinivasan
Modified: 2008-05-19 23:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
EPS file on which okular crashes (9.48 KB, image/x-eps)
2008-04-04 19:27 UTC, Praveen Srinivasan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Praveen Srinivasan 2008-04-04 19:27:12 UTC
Version:            (using KDE 4.0.3)
Installed from:    Ubuntu Packages

Hi,
I tried to view the attached EPS file, but okular crashes shortly after opening it. (I'll attach
the EPS in a 2nd entry for this bug).
Comment 1 Praveen Srinivasan 2008-04-04 19:27:59 UTC
Created attachment 24186 [details]
EPS file on which okular crashes
Comment 2 Albert Astals Cid 2008-04-04 19:33:35 UTC
Works here, do you have a backtrace?
Comment 3 Praveen Srinivasan 2008-04-04 21:48:24 UTC
Ok, If I load the file from okular, it works. But if I use okular on the command line and provide the filename as the argument, it crashes.
Comment 4 Praveen Srinivasan 2008-04-04 21:49:07 UTC
Hi,
Here's my backtrace. I launch okular from the command line with the
filename as the argument:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235900016 (LWP 19550)]
[New Thread -1296098416 (LWP 19551)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 19550)]

Thread 2 (Thread -1296098416 (LWP 19551)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6d7de96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6d7dca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7b14e20 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread -1235900016 (LWP 19550)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6db45e7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6928839 in ?? () from /usr/lib/libX11.so.6
#3  0x0806f270 in ?? ()
#4  0x00000001 in ?? ()
#5  0xffffffff in ?? ()
#6  0xb693167f in _X11TransWrite () from /usr/lib/libX11.so.6
#7  0xb6928c2f in _XRead () from /usr/lib/libX11.so.6
#8  0xb6929604 in _XReply () from /usr/lib/libX11.so.6
#9  0xb691d530 in XQueryPointer () from /usr/lib/libX11.so.6
#10 0xb70d2e5e in QCursor::pos () from /usr/lib/libQtGui.so.4
#11 0xb4f821cd in ?? () from /usr/lib/kde4/lib/kde4/okularpart.so
#12 0xbfa43758 in ?? ()
#13 0xbfa43f60 in ?? ()
#14 0x00000018 in ?? ()
#15 0xb7ab9e68 in KStyle::eventFilter () from /usr/lib/kde4/lib/libkdeui.so.5
#16 0xb4f8f3cb in ?? () from /usr/lib/kde4/lib/kde4/okularpart.so
#17 0x08343158 in ?? ()
#18 0xbfa43f60 in ?? ()
#19 0xbfa439f8 in ?? ()
#20 0xb70ace2f in QWidget::event () from /usr/lib/libQtGui.so.4
Backtrace stopped: frame did not save the PC
#0  0xffffe410 in __kernel_vsyscall ()

On Fri, Apr 4, 2008 at 1:33 PM, Albert Astals Cid <tsdgeos@terra.es> wrote:
[bugs.kde.org quoted mail]
Comment 5 Pino Toscano 2008-04-04 21:53:45 UTC
>  (no debugging symbols found) 

Unfortunately, this backtrace is not much useful.
Could you please install the debug packages (keeping in mind that Okular is part of kdegraphics), and get a better backtrace?
Thanks.
Comment 6 Praveen Srinivasan 2008-04-04 22:35:36 UTC
I can do that, but was anyone able to reproduce the crash by starting
okular from the command line with the filename as an argument?

-Praveen

On Fri, Apr 4, 2008 at 3:53 PM, Pino Toscano <pino@kde.org> wrote:
[bugs.kde.org quoted mail]
Comment 7 Albert Astals Cid 2008-04-04 23:15:35 UTC
Not really
Comment 8 Pino Toscano 2008-05-19 22:43:36 UTC
Ping? Any additional information about this issue? Is it valid yet?
Comment 9 Praveen Srinivasan 2008-05-19 23:03:11 UTC
It doesn't crash for me in kde 4.0.3.

-Praveen

On Mon, May 19, 2008 at 4:43 PM, Pino Toscano <pino@kde.org> wrote:

[bugs.kde.org quoted mail]



It doesn&#39;t crash for me in kde <a href="http://4.0.3.">4.0.3.</a><br><br>-Praveen<br><br><div class="gmail_quote">On Mon, May 19, 2008 at 4:43 PM, Pino Toscano &lt;<a href="mailto:pino@kde.org">pino@kde.org</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br>
You reported the bug, or are watching the reporter.<br>
<br>
<a href="http://bugs.kde.org/show_bug.cgi?id=160372" target="_blank">http://bugs.kde.org/show_bug.cgi?id=160372</a><br>
</div>pino kde org changed:<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; What &nbsp; &nbsp;|Removed &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Added<br>
----------------------------------------------------------------------------<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Severity|normal &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|crash<br>
<br>
<br>
<br>
------- Additional Comments From pino kde org &nbsp;2008-05-19 22:43 -------<br>
Ping? Any additional information about this issue? Is it valid yet?<br>
</blockquote></div><br><br clear="all"><br>-- <br>~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-<br>Praveen Srinivasan
Comment 10 Pino Toscano 2008-05-19 23:23:49 UTC
> It doesn't crash for me in kde 4.0.3.

Ok, closing then.

(PS: when replying, use the bugzilla web interface, otherwise there's all the html stuff...)