Bug 211432 - I can't now import poscript files with the sot okular. It was working yesterday
Summary: I can't now import poscript files with the sot okular. It was working yesterday
Status: RESOLVED DUPLICATE of bug 211376
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 0.8.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 13:07 UTC by patrice lemonnier
Modified: 2009-10-26 10:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description patrice lemonnier 2009-10-22 13:07:28 UTC
Version:           0.8.4 (using 4.2.4 (KDE 4.2.4), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-14-generic

When i try to import a poscript file with okular, It open the file during one second and after it crash.
I have try to reinstall okular but it's alway the same problem.
Many thanks
Comment 1 Dario Andres 2009-10-22 14:55:54 UTC
- Does it happens with every PostScript file ?
- Do you get the Crash Handler window ? Can you get the backtrace as explained in here http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports ?
Thanks
Comment 2 patrice lemonnier 2009-10-22 15:45:02 UTC
In fact okular create a file pdf in the directory home/.kde/temp
I have open this file with nautilus.
I Think it's a problem of KDE

And I have discovered that okular can't  open this file.
I don't know why.

Very sincerely
Patrice Lemonnier
Le jeudi 22 octobre 2009 à 14:55 +0200, Dario Andres a écrit :
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |andresbajotierra@gmail.com
>          Resolution|                            |WAITINGFORINFO
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2009-10-22 14:55:54 ---
> - Does it happens with every PostScript file ?
> - Do you get the Crash Handler window ? Can you get the backtrace as explained
> in here
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> ?
> Thanks
>
Comment 3 patrice lemonnier 2009-10-22 15:46:07 UTC
Yes with all the files
Sincerely
Patrice Lemonnier
Le jeudi 22 octobre 2009 à 14:55 +0200, Dario Andres a écrit :
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |andresbajotierra@gmail.com
>          Resolution|                            |WAITINGFORINFO
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2009-10-22 14:55:54 ---
> - Does it happens with every PostScript file ?
> - Do you get the Crash Handler window ? Can you get the backtrace as explained
> in here
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> ?
> Thanks
>
Comment 4 Dario Andres 2009-10-22 15:49:40 UTC
Try to get the crash information ("backtrace") as explained in http://techbase.kde.org/User:DarioAndres/CreateUsefulReports#Reproducing_the_crash

You may need to install the "kdegraphics-dbg" package in order to get a complete trace. 

Regards
Comment 5 patrice lemonnier 2009-10-22 16:10:23 UTC
I have installed kdegraphics-dbg

and I have try again to import a poscript file.

I send to you all the informations I have gotten
Best regard
Patrice Lemonnier

The application Okular (okular) crashed and caused the signal 11
(SIGSEGV).

Cette pile des appels apparaît être inutilisable.

C'est probablement dû au fait que votre paquetage a été construit d'une
manière qui empêche de créer des piles d'appels corrects, ou que le
cadre de pile a été sérieusement corrompu dans l'incident.

[Thread debugging using libthread_db enabled]

[New Thread 0xb5f84700 (LWP 12557)]

[New Thread 0xb116eb90 (LWP 12569)]

[New Thread 0xb2489b90 (LWP 12561)]

0xb7f95430 in __kernel_vsyscall ()

[Current thread is 0 (LWP 12557)]

Thread 3 (Thread 0xb2489b90 (LWP 12561)):

#0 0xb7f95430 in __kernel_vsyscall ()

#1 0xb67317b1 in select () from /lib/tls/i686/cmov/libc.so.6

#2 0xb73f3380 in ?? () from /usr/lib/libQtCore.so.4

#3 0xb732196e in ?? () from /usr/lib/libQtCore.so.4

#4 0xb63bf4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0

#5 0xb673949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 2 (Thread 0xb116eb90 (LWP 12569)):

#0 0xb7f95430 in __kernel_vsyscall ()

#1 0xb66f47a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6

#2 0xb66f45be in sleep () from /lib/tls/i686/cmov/libc.so.6

#3 0xb7a28d82 in ?? () from /usr/lib/libkdeui.so.5

#4 0xb7a29744 in KCrash::defaultCrashHandler ()
from /usr/lib/libkdeui.so.5

#5 <signal handler called>

#6 0xb754ef46 in ?? () from /usr/lib/libQtDBus.so.4

#7 0xb754f8dc in ?? () from /usr/lib/libQtDBus.so.4

#8 0xb742bca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4

#9 0xb742c0e0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4

#10 0xb742c16b in QObject::destroyed () from /usr/lib/libQtCore.so.4

#11 0xb742cfa9 in QObject::~QObject () from /usr/lib/libQtCore.so.4

#12 0xb7e2d5ad in KIO::Scheduler::~Scheduler ()
from /usr/lib/libkio.so.5

#13 0xb7e30d24 in ?? () from /usr/lib/libkio.so.5

#14 0xb7d7049b in ?? () from /usr/lib/libkio.so.5

#15 0xb6683bb9 in exit () from /lib/tls/i686/cmov/libc.so.6

#16 0xb1b5c0f1 in gmallocn () from /usr/lib/libpoppler.so.4

#17 0xb1b7e123 in SplashFTFont::makeGlyph ()
from /usr/lib/libpoppler.so.4

#18 0xb1b7f88e in SplashFont::getGlyph () from /usr/lib/libpoppler.so.4

#19 0xb1b7e206 in SplashFTFont::getGlyph ()
from /usr/lib/libpoppler.so.4

#20 0xb1b7344f in Splash::fillChar () from /usr/lib/libpoppler.so.4

#21 0xb1a9b866 in SplashOutputDev::drawChar ()
from /usr/lib/libpoppler.so.4

#22 0xb1add7aa in Gfx::doShowText () from /usr/lib/libpoppler.so.4

#23 0xb1addb0c in Gfx::opShowText () from /usr/lib/libpoppler.so.4

#24 0xb1ad5aba in Gfx::execOp () from /usr/lib/libpoppler.so.4

#25 0xb1ad607f in Gfx::go () from /usr/lib/libpoppler.so.4

#26 0xb1ad8aef in Gfx::display () from /usr/lib/libpoppler.so.4

#27 0xb1b1f69d in Page::displaySlice () from /usr/lib/libpoppler.so.4

#28 0xb1b22f40 in PDFDoc::displayPageSlice ()
from /usr/lib/libpoppler.so.4

#29 0xb1c1dda5 in Poppler::Page::renderToImage ()
from /usr/lib/libpoppler-qt4.so.3

#30 0xb3d68a83 in PDFPixmapGeneratorThread::run (this=0x9387b80)
at /build/buildd/kdegraphics-4.2.4/okular/generators/poppler/generator_pdf.cpp:1824

#31 0xb732196e in ?? () from /usr/lib/libQtCore.so.4

#32 0xb63bf4ff in start_thread ()
from /lib/tls/i686/cmov/libpthread.so.0

#33 0xb673949e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5f84700 (LWP 12557)):

#0 0xb7f95430 in __kernel_vsyscall ()

#1 0xb63c30e5 in pthread_cond_wait@@GLIBC_2.3.2 ()
from /lib/tls/i686/cmov/libpthread.so.0

#2 0xb67482ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6

#3 0xb73229b2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4

#4 0xb7321b13 in QThread::wait () from /usr/lib/libQtCore.so.4

#5 0xb73f62fe in ?? () from /usr/lib/libQtCore.so.4

#6 0xb73f681a in ?? () from /usr/lib/libQtCore.so.4

#7 0xb6683bb9 in exit () from /lib/tls/i686/cmov/libc.so.6

#8 0xb585a165 in gdk_x_io_error (display=0x8dd72f8) at /build/buildd/gtk
+2.0-2.16.1/gdk/x11/gdkmain-x11.c:699

#9 0xb79b87ba in KApplication::xioErrhandler ()
from /usr/lib/libkdeui.so.5

#10 0xb79b87f6 in ?? () from /usr/lib/libkdeui.so.5

#11 0xb6451f22 in _XIOError () from /usr/lib/libX11.so.6

#12 0xb6459743 in ?? () from /usr/lib/libX11.so.6

#13 0xb6459ccd in _XReply () from /usr/lib/libX11.so.6

#14 0xb644d507 in XSync () from /usr/lib/libX11.so.6

#15 0xb642d0ee in XCloseDisplay () from /usr/lib/libX11.so.6

#16 0xb554f734 in spi_atk_bridge_exit_func () at bridge.c:657

#17 0xb6683bb9 in exit () from /lib/tls/i686/cmov/libc.so.6

#18 0xb585a165 in gdk_x_io_error (display=0x8d9c298)
at /build/buildd/gtk+2.0-2.16.1/gdk/x11/gdkmain-x11.c:699

#19 0xb79b87ba in KApplication::xioErrhandler ()
from /usr/lib/libkdeui.so.5

#20 0xb79b87f6 in ?? () from /usr/lib/libkdeui.so.5

#21 0xb6451f22 in _XIOError () from /usr/lib/libX11.so.6

#22 0xb6459743 in ?? () from /usr/lib/libX11.so.6

#23 0xb645a0e5 in _XEventsQueued () from /usr/lib/libX11.so.6

#24 0xb6442738 in XPending () from /usr/lib/libX11.so.6

#25 0xb584d805 in gdk_event_prepare (source=0x8dafee8,
timeout=0xbfcb3328) at /build/buildd/gtk
+2.0-2.16.1/gdk/x11/gdkevents-x11.c:154

#26 0xb62f19c0 in IA__g_main_context_prepare (context=0x8d45890,
priority=0xbfcb3398) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2134

#27 0xb62f1dda in g_main_context_iterate (context=0x8d45890, block=1,
dispatch=1, self=0x8d42ee0)
at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2428

#28 0xb62f2268 in IA__g_main_context_iteration (context=0x8d45890,
may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511

#29 0xb7441457 in QEventDispatcherGlib::processEvents ()
from /usr/lib/libQtCore.so.4

#30 0xb6abf365 in ?? () from /usr/lib/libQtGui.so.4

#31 0xb741406a in QEventLoop::processEvents ()
from /usr/lib/libQtCore.so.4

#32 0xb74144aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4

#33 0xb7416959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4

#34 0xb6a1dd17 in QApplication::exec () from /usr/lib/libQtGui.so.4

#35 0x0804e457 in main (argc=)
at /build/buildd/kdegraphics-4.2.4/okular/shell/main.cpp:81

#0 0xb7f95430 in __kernel_vsyscall ()







Please help us improve the software you use by filing a report at
http://bugs.kde.org. Useful details include how to reproduce the error,
documents that were loaded, etc.


Le jeudi 22 octobre 2009 à 15:49 +0200, Dario Andres a écrit : 
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> 
> 
> 
> --- Comment #4 from Dario Andres <andresbajotierra gmail com>  2009-10-22 15:49:40 ---
> Try to get the crash information ("backtrace") as explained in
> http://techbase.kde.org/User:DarioAndres/CreateUsefulReports#Reproducing_the_crash
> 
> You may need to install the "kdegraphics-dbg" package in order to get a
> complete trace. 
> 
> Regards
>
Comment 6 Dario Andres 2009-10-22 16:13:30 UTC
I wonder if this could be related to bug 211376.
Thanks
Comment 7 Pino Toscano 2009-10-22 16:20:07 UTC
Hi,

if you are really opening a PostScript document (eg those ending with .ps) and NOT a PDF document, open it normally instead of using the File -> Import function.

Anyway, bug 211376.

*** This bug has been marked as a duplicate of bug 211376 ***
Comment 8 patrice lemonnier 2009-10-22 16:35:24 UTC
Yes Ok but you open a file.ps of several pages, only one page is open.
If you want to see you document you need to import the file.

Perhaps okular could open in the new version  a complet document but for
the moment it's not possible.
Best regard
Patrice Lemonnier

Le jeudi 22 octobre 2009 à 16:20 +0200, Pino Toscano a écrit :
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> Pino Toscano <pino@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>           Component|general                     |PDF backend
>          Resolution|                            |DUPLICATE
> 
> 
> 
> 
> --- Comment #7 from Pino Toscano <pino kde org>  2009-10-22 16:20:07 ---
> Hi,
> 
> if you are really opening a PostScript document (eg those ending with .ps) and
> NOT a PDF document, open it normally instead of using the File -> Import
> function.
> 
> Anyway, bug 211376.
> 
> *** This bug has been marked as a duplicate of bug 211376 ***
>
Comment 9 Albert Astals Cid 2009-10-22 20:11:33 UTC
Do i understand that you have a PostScript file that you know has multiple pages but if you open (NOT import) it with okular you only get one page?
Comment 10 patrice lemonnier 2009-10-23 10:04:31 UTC
Yes
When you open a poscript file with multiple pages with okular only you
only get the last page of the file.

If you want all the pages you need to import the file
Best regard
Patrice Lemonnier
Le jeudi 22 octobre 2009 à 20:11 +0200, Albert Astals Cid a écrit :
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> 
> 
> 
> --- Comment #9 from Albert Astals Cid <tsdgeos terra es>  2009-10-22 20:11:33 ---
> Do i understand that you have a PostScript file that you know has multiple
> pages but if you open (NOT import) it with okular you only get one page?
>
Comment 11 Albert Astals Cid 2009-10-23 19:43:50 UTC
No, that's not the intented behaviour, can you please attach a postscript file with this problem?
Comment 12 patrice lemonnier 2009-10-26 10:32:51 UTC
Ok I have created a poscript file of 155 pages.

You could import this file and you will see all the document
If you open the file you will only see the last page.
Best regard



Le vendredi 23 octobre 2009 à 19:43 +0200, Albert Astals Cid a écrit :
> https://bugs.kde.org/show_bug.cgi?id=211432
> 
> 
> 
> 
> 
> --- Comment #11 from Albert Astals Cid <tsdgeos terra es>  2009-10-23 19:43:50 ---
> No, that's not the intented behaviour, can you please attach a postscript file
> with this problem?
>
Comment 13 Albert Astals Cid 2009-10-26 10:39:07 UTC
Can you please attach that document to this bug using https://bugs.kde.org/attachment.cgi?bugid=211432&action=enter ?