[Okular-devel] [Bug 279714] New: let user duplicate the current window
https://bugs.kde.org/show_bug.cgi?id=279714 Summary: let user duplicate the current window Product: okular Version: 0.13 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Version: 0.13 (using KDE 4.7.0) OS:Linux Like evince allows, okular could allow users to press ctrl-n to duplicate the current window. This is useful especially when one is reading a pdf with references. In one window they read, in the other they look what [1], [2], [100] correspond to... Reproducible: Always Steps to Reproduce: 1.) Open an article in okular 2.) Find a reference in the text which you want to now 3.) Have an easy way to duplicate the current window to have the document opened twice. Expected Results: Have a shortcut to duplicate the current okular window. OS: Linux (x86_64) release 2.6.37.6-0.7-desktop Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 262696] Mimetype problem for fictionbook downloads.
https://bugs.kde.org/show_bug.cgi?id=262696 --- Comment #5 from Christian Trippe 2011-01-14 22:05:54 --- I use KDE 4.6 RC2 and shared-mime-info-0.71. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 262696] Mimetype problem for fictionbook downloads.
https://bugs.kde.org/show_bug.cgi?id=262696 --- Comment #2 from Christian Trippe 2011-01-14 21:31:26 --- Thanks for the feedback. For reference I reported this at https://bugs.freedesktop.org/show_bug.cgi?id=33133 And thanks for okular! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 262696] New: Mimetype problem for fictionbook downloads.
https://bugs.kde.org/show_bug.cgi?id=262696 Summary: Mimetype problem for fictionbook downloads. Product: okular Version: 0.5.81 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Version: 0.5.81 (using KDE 4.5.95) OS:Linux I tried viewing a fictionbook from http://manybooks.net/titles/vernejul3351633516-8.html Choosing download for the FictionBook2, I get a dialog which tells me it is of mimetype: application/x-fictionbook And gives the options to save it or choose an application to open it with. Choosing okular there works fine. The other way downloading it and trying to open it locally also works. There it even launches okular directly. But locally it says it has the Mimetype: application/x-fictionbook-xml. Please note the additional "xml". IMHO it would be nice the other mimetype which is reported when trying to open it directly would also be supported. I found a somehow related report: bug 233301 Reproducible: Always OS: Linux (i686) release 2.6.37-default Compiler: gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 242472] New: okular crashed when trying to open the print dialog
https://bugs.kde.org/show_bug.cgi?id=242472 Summary: okular crashed when trying to open the print dialog Product: okular Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Application: okular (0.10.80) KDE Platform Version: 4.4.86 (KDE 4.4.86 (KDE 4.5 >= 20100616)) "release 3" Qt Version: 4.6.3 Operating System: Linux 2.6.34-9-default i686 Distribution: "openSUSE 11.3 RC 1 (i586)" -- Information about the crash: I tried to open the print dialog of okular. Then okular crashed. It is possible that the server on which I want to print via cups (using cups via BrowsePoll) was not ready/still booting at that moment. So it is possible that no printer was available at that time. This is the same as in the suggested duplicate bug 233890. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [Current thread is 1 (Thread 0xb51dd710 (LWP 29764))] Thread 4 (Thread 0xaed0eb70 (LWP 2253)): #0 0xe430 in __kernel_vsyscall () #1 0xb5efa0b1 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb623e538 in QProcessManager::run (this=0xb637c888) at io/qprocess_unix.cpp:245 #3 0xb616504f in QThreadPrivate::start (arg=0xb637c888) at thread/qthread_unix.cpp:248 #4 0xb5994b25 in start_thread (arg=0xaed0eb70) at pthread_create.c:297 #5 0xb5f0146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xb0116b70 (LWP 2512)): #0 0xe430 in __kernel_vsyscall () #1 0xb5999125 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122 #2 0xb5f0f24c in __pthread_cond_wait (cond=0x8a59230, mutex=0x8a59218) at forward.c:139 #3 0xb6165710 in wait (this=0x8ca2820, mutex=0x8ca281c, time=4294967295) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (this=0x8ca2820, mutex=0x8ca281c, time=4294967295) at thread/qwaitcondition_unix.cpp:159 #5 0xb6cd1753 in QFileInfoGatherer::run (this=0x8ca2814) at dialogs/qfileinfogatherer.cpp:203 #6 0xb616504f in QThreadPrivate::start (arg=0x8ca2814) at thread/qthread_unix.cpp:248 #7 0xb5994b25 in start_thread (arg=0xb0116b70) at pthread_create.c:297 #8 0xb5f0146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xaf50fb70 (LWP 2514)): #0 0xe430 in __kernel_vsyscall () #1 0xb5ef675e in __poll (fds=0x8234118, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb57f21db in g_poll () from /usr/lib/libglib-2.0.so.0 #3 0xb57e2286 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb57e260e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0xb628ad4b in QEventDispatcherGlib::processEvents (this=0x8acc688, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #6 0xb625e11d in QEventLoop::processEvents (this=0xaf50f2c0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb625e319 in QEventLoop::exec (this=0xaf50f2c0, flags=...) at kernel/qeventloop.cpp:201 #8 0xb6162403 in QThread::exec (this=0x8ca2990) at thread/qthread.cpp:487 #9 0xb623eafd in QInotifyFileSystemWatcherEngine::run (this=0x8ca2990) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb616504f in QThreadPrivate::start (arg=0x8ca2990) at thread/qthread_unix.cpp:248 #11 0xb5994b25 in start_thread (arg=0xaf50fb70) at pthread_create.c:297 #12 0xb5f0146e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb51dd710 (LWP 29764)): [KCrash Handler] #7 0xb699ed34 in QCUPSSupport::printerOption (this=0x893a6b0, key=...) at painting/qcups.cpp:251 #8 0xb6c7a778 in QUnixPrintWidgetPrivate::_q_printerChanged (this=0x8778af8, index=-1074064296) at dialogs/qprintdialog_unix.cpp:799 #9 0xb6c7b55b in QUnixPrintWidgetPrivate::QUnixPrintWidgetPrivate (this=0x8778af8, p=0x0) at dialogs/qprintdialog_unix.cpp:706 #10 0xb6c7b8bb in QUnixPrintWidget::QUnixPrintWidget (this=0x88e9038, printer=0x0, parent=0x88e9058) at dialogs/qprintdialog_unix.cpp:1031 #11 0xb6c7b94e in QPrintDialogPrivate::init (this=0x87788c0) at dialogs/qprintdialog_unix.cpp:388 #12 0xb6c7c1cc in QPrintDialog::QPrintDialog (this=0x88e9058, printer=0xbffb16f0, parent=0x8178968) at dialogs/qprintdialog_unix.cpp:584 #13 0xb71deb6c in KdePrint::createPrintDialog (printer=0xbffb16f0, pageSelectPolicy=KdePrint::ApplicationSelectsPages, customTabs=..., parent=0x8178968) at /usr/src/debug/kdelibs-4.4.86svn1138650/kdeui/dialogs/kdeprintdialog.cpp:44 #14 0xb71dee73 in KdePrint::createPrintDialog (printer=0xbffb16f0, customTabs=..., parent=0x8178968) at /usr/src/debug/kdelibs-4.4.86svn1138650/kdeui/dialogs/kdeprintdialog.cpp:81 #15 0xb29f2705 in ?? () from /usr/lib/kde4/okularpart.so #16 0xb29f2d25 in ?? () from /usr/lib/kde4/okularpart.so #17 0xb6264efd in QMetaObject::metacall (object=0x8172c70, cl=QMetaObject::InvokeMetaMethod, idx=66, argv=0xbffb1848) at kerne
[Okular-devel] [Bug 228427] inconsistency between dvi and pdf forward search
https://bugs.kde.org/show_bug.cgi?id=228427 --- Comment #4 from Christian Trippe 2010-02-26 08:12:31 --- No it is not crucial, but at least Kile hat to change its code for PDF forward search, see https://bugs.kde.org/show_bug.cgi?id=226718 and the Kile maintainer suggested to report this. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 228427] New: inconsistency between dvi and pdf forward search
https://bugs.kde.org/show_bug.cgi?id=228427 Summary: inconsistency between dvi and pdf forward search Product: okular Version: 0.10 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Version: 0.10 (using 4.4.00 (KDE 4.4.0) "release 2", KDE:KDE4:Factory:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (i686) release 2.6.31.12-0.1-default First thanks for having pdf forward search available in okular. However I noticed a small inconsistency between the way okular handles forward search for dvi and pdf documents. I will attach documents which allow to test the behaviour You can use okular test.(dvi|pdf)#src:test.tex to run forward search. It also works if you use absolute pathes for your files or relative pathes. However if your relative path starts with './', it only works for dvi files. To reproduce run okular loremipsum.dvi#src:25./loremipsum.tex and compare with okular loremipsum.pdf#src:25./loremipsum.tex with the attached files -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 228427] inconsistency between dvi and pdf forward search
https://bugs.kde.org/show_bug.cgi?id=228427 --- Comment #1 from Christian Trippe 2010-02-25 10:47:23 --- Created an attachment (id=41090) --> (http://bugs.kde.org/attachment.cgi?id=41090) example document for foward search -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 226976] New: okular crashed after save copy as
https://bugs.kde.org/show_bug.cgi?id=226976 Summary: okular crashed after save copy as Product: okular Version: 0.10 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Application: okular (0.10) KDE Platform Version: 4.4.00 (KDE 4.4.0) "release 223" Qt Version: 4.6.1 Operating System: Linux 2.6.31.12-0.1-default i686 Distribution: "openSUSE 11.2 (i586)" -- Information about the crash: 1.) Open a pdf 2.) Save copy as 3.) Type in a name 4.) press OK => okular crashes (but the document is saved) The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #6 0xb6c08421 in isSignalConnected (signal_index=, this=) at kernel/qobject_p.h:225 #7 QMetaObject::activate (signal_index=, this=) at kernel/qobject.cpp:3200 #8 0xb749ff35 in KDirWatch::dirty (this=0x8653748, _t1=...) at /usr/src/debug/kdelibs-4.4.0/build/kio/kdirwatch.moc:89 #9 0xb74a0033 in KDirWatch::setDirty (this=0x8653748, _file=...) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1839 #10 0xb75098b0 in KDirWatchPrivate::emitEvent (this=0x82f7ea0, e=0x87476ec, event=1, fileName=...) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1272 #11 0xb7629f45 in KDirWatchPrivate::slotRescan (this=0x82f7ea0) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1395 #12 0xb762a76c in KDirWatchPrivate::qt_metacall (this=0x82f7ea0, _c=InvokeMetaMethod, _id=4, _a=0xbfafe03c) at /usr/src/debug/kdelibs-4.4.0/build/kio/kdirwatch_p.moc:81 #13 0xb6bf932d in QMetaObject::metacall (object=0x82f7ea0, cl=InvokeMetaMethod, idx=4, argv=0xbfafe03c) at kernel/qmetaobject.cpp:237 #14 0xb6c0818a in QMetaObject::activate (sender=0x82f7ee8, m=0xb6d0a5a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3275 #15 0xb6c5b785 in QTimer::timeout (this=0x82f7ee8) at .moc/release-shared/moc_qtimer.cpp:134 #16 0xb6c10476 in QTimer::timerEvent (this=0x82f7ee8, e=0xbfafe594) at kernel/qtimer.cpp:271 #17 0xb6c04c94 in QObject::event (this=0x82f7ee8, e=0x29) at kernel/qobject.cpp:1212 #18 0xb611e2ac in QApplicationPrivate::notify_helper (this=0x8071c28, receiver=0x82f7ee8, e=0xbfafe594) at kernel/qapplication.cpp:4298 #19 0xb61250f8 in QApplication::notify (this=0xbfafe940, receiver=0x82f7ee8, e=0xbfafe594) at kernel/qapplication.cpp:4181 #20 0xb718db71 in KApplication::notify (this=0xbfafe940, receiver=0x82f7ee8, event=0xbfafe594) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302 #21 0xb6bf3fbe in QCoreApplication::notifyInternal (this=0xbfafe940, receiver=0x82f7ee8, event=0xbfafe594) at kernel/qcoreapplication.cpp:704 #22 0xb6c241fe in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:215 #23 QTimerInfoList::activateTimers (event=, receiver=) at kernel/qeventdispatcher_unix.cpp:617 #24 0xb6c20e95 in timerSourceDispatch (source=0x8074e00) at kernel/qeventdispatcher_glib.cpp:184 #25 idleTimerSourceDispatch (source=0x8074e00) at kernel/qeventdispatcher_glib.cpp:231 #26 0xb578a4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0xb578dd98 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0xb578debe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0xb6c20b31 in QEventDispatcherGlib::processEvents (this=0x805db08, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #30 0xb61de6ca in QGuiEventDispatcherGlib::processEvents (this=0x805db08, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0xb6bf262d in QEventLoop::processEvents (this=0xbfafe844, flags=) at kernel/qeventloop.cpp:149 #32 0xb6bf2a79 in QEventLoop::exec (this=0xbfafe844, flags=...) at kernel/qeventloop.cpp:201 #33 0xb6bf6bf0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #34 0xb611e354 in QApplication::exec () at kernel/qapplication.cpp:3577 #35 0x0804ef29 in main (argc=6, argv=0xbfafeb24) at /usr/src/debug/kdegraphics-4.4.0/okular/shell/main.cpp:82 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218895] Okular crashed when refreshing a dvi file
https://bugs.kde.org/show_bug.cgi?id=218895 --- Comment #5 from Christian Trippe 2010-01-11 20:41:02 --- After installing KDE SC 4.4 RC 1, I have used okular intensively in the last days and did not have a single crash for okular. So thanks for the quick fix! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218895] Okular crashed when refreshing a dvi file
https://bugs.kde.org/show_bug.cgi?id=218895 --- Comment #4 from Christian Trippe 2009-12-23 10:09:14 --- Yes it was always the same backtrace, as far as I remember. I have upgraded to KDE 4.4 beta 2 in the meantime, I will report back if I still see the crash with the next (beta) release. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218895] Okular crashed when refreshing a dvi file
https://bugs.kde.org/show_bug.cgi?id=218895 --- Comment #1 from Christian Trippe 2009-12-21 10:37:15 --- In the meantime I could reproduce this crash twice. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218892] okular doesn’t display ‘u’ in certain documents
https://bugs.kde.org/show_bug.cgi?id=218892 --- Comment #4 from Christian Trippe 2009-12-16 10:54:53 --- > this is a bug in the Poppler library, please report it to > https://bugs.freedesktop.org, "poppler" product "splash backend" component. > Done, see https://bugs.freedesktop.org/show_bug.cgi?id=25667 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218895] New: Okular crashed when refreshing a dvi file
https://bugs.kde.org/show_bug.cgi?id=218895 Summary: Okular crashed when refreshing a dvi file Product: okular Version: 0.9.4 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Version: 0.9.4 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:KDE4:STABLE:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (i686) release 2.6.31.5-0.1-default Application that crashed: okular Version of the application: 0.9.4 KDE Version: 4.3.4 (KDE 4.3.4) "release 2" Qt Version: 4.5.3 Operating System: Linux 2.6.31.5-0.1-default i686 Distribution: "openSUSE 11.2 (i586)" What I was doing when the application crashed: I run latex on a tex-file where the correspondent dvi-file was opened. Then I wanted to switch to okular to view the dvi and found DrKonqi. DrKonqi does not reports a possible duplicate. However the symptom is similar to bug https://bugs.kde.org/show_bug.cgi?id=211765 but this time it crashed before I closed okular. The next latex run did not show the problem. However I can sent you the tex-file which caused the crash by private mail. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #6 0xb3e89f00 in findNode (akey=, this=) at /usr/include/QtCore/qmap.h:428 #7 constFind (akey=, this=) at /usr/include/QtCore/qmap.h:559 #8 Okular::Page::hasPixmap (akey=, this=) at /usr/src/debug/kdegraphics-4.3.4/okular/core/page.cpp:203 #9 0xb3e76519 in Okular::DocumentPrivate::sendGeneratorRequest (this=0x81327d8) at /usr/src/debug/kdegraphics-4.3.4/okular/core/document.cpp:837 #10 0xb3e7c699 in Okular::Document::qt_metacall (this=0x8130b58, _c=InvokeMetaMethod, _id=23, _a=0xbfa01f2c) at /usr/src/debug/kdegraphics-4.3.4/build/okular/document.moc:145 #11 0xb6ca8864 in QMetaObject::activate (sender=0xafb06fc8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #12 0xb6ca9585 in QMetaObject::activate (sender=0xafb06fc8, m=0xb6d84908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #13 0xb6cadb25 in QSingleShotTimer::timeout (this=0xafb06fc8) at .moc/release-shared/qtimer.moc:76 #14 0xb6cadc5c in QSingleShotTimer::timerEvent (this=0xafb06fc8) at kernel/qtimer.cpp:298 #15 0xb6ca251b in QObject::event (this=0xafb06fc8, e=0xbfa023b4) at kernel/qobject.cpp:1075 #16 0xb62d88fc in QApplicationPrivate::notify_helper (this=0x8070940, receiver=0xafb06fc8, e=0xbfa023b4) at kernel/qapplication.cpp:4065 #17 0xb62e034e in QApplication::notify (this=0xbfa02768, receiver=0xafb06fc8, e=0xbfa023b4) at kernel/qapplication.cpp:3605 #18 0xb7243451 in KApplication::notify (this=0xbfa02768, receiver=0xafb06fc8, event=0xbfa023b4) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #19 0xb6c9232e in QCoreApplication::notifyInternal (this=0xbfa02768, receiver=0xafb06fc8, event=0xbfa023b4) at kernel/qcoreapplication.cpp:610 #20 0xb6cc1356 in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:213 #21 QTimerInfoList::activateTimers (event=, receiver=) at kernel/qeventdispatcher_unix.cpp:594 #22 0xb6cbe325 in timerSourceDispatch (source=0x80736c0) at kernel/qeventdispatcher_glib.cpp:184 #23 idleTimerSourceDispatch (source=0x80736c0) at kernel/qeventdispatcher_glib.cpp:231 #24 0xb599c4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0xb599fd98 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0xb599febe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0xb6cbe011 in QEventDispatcherGlib::processEvents (this=0x805ae40, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #28 0xb637a29a in QGuiEventDispatcherGlib::processEvents (this=0x805ae40, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #29 0xb6c9098d in QEventLoop::processEvents (this=0xbfa02664, flags=) at kernel/qeventloop.cpp:149 #30 0xb6c90dd9 in QEventLoop::exec (this=0xbfa02664, flags=...) at kernel/qeventloop.cpp:201 #31 0xb6c93270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #32 0xb62d8774 in QApplication::exec () at kernel/qapplication.cpp:3525 #33 0x0804efb9 in main (argc=3, argv=0xbfa02944) at /usr/src/debug/kdegraphics-4.3.4/okular/shell/main.cpp:81 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218892] okular doesn’t display ‘u’ in certain documents
https://bugs.kde.org/show_bug.cgi?id=218892 --- Comment #2 from Christian Trippe 2009-12-16 08:08:36 --- Created an attachment (id=39088) --> (http://bugs.kde.org/attachment.cgi?id=39088) screenshot of evince vs okular showing the bug -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218892] okular doesn’t display ‘u’ in certain documents
https://bugs.kde.org/show_bug.cgi?id=218892 --- Comment #1 from Christian Trippe 2009-12-16 08:07:49 --- Created an attachment (id=39087) --> (http://bugs.kde.org/attachment.cgi?id=39087) Document in which 'u' is missing when dispalyed with okular -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218892] New: okular doesn ’t display ‘u’ in certain documents
https://bugs.kde.org/show_bug.cgi?id=218892 Summary: okular doesn’t display ‘u’ in certain documents Product: okular Version: 0.9.4 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Version: 0.9.4 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:KDE4:STABLE:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (i686) release 2.6.31.5-0.1-default okular doesn’t display ‘u’ in certain documents. I will attach an effected document. evince does display the attached document correctly. This bug was reported downstream at https://bugzilla.novell.com/show_bug.cgi?id=462784 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 218789] New: Okular crashed after I clicked the close button
https://bugs.kde.org/show_bug.cgi?id=218789 Summary: Okular crashed after I clicked the close button Product: okular Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: christiande...@web.de Application that crashed: okular Version of the application: 0.9.4 KDE Version: 4.3.4 (KDE 4.3.4) "release 2" Qt Version: 4.5.3 Operating System: Linux 2.6.31.5-0.1-default i686 Distribution: "openSUSE 11.2 (i586)" What I was doing when the application crashed: I viewed a dvi file in okular. After a latex run, okular did no longer reload the dvi-file. After retrying, I decided to close okular, which crashed after I hit the close button. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [Current thread is 1 (Thread 0xb56e9920 (LWP 22085))] Thread 2 (Thread 0xaf7d8b70 (LWP 20774)): #0 0xe430 in __kernel_vsyscall () #1 0xb5f9bd95 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb60d027c in pthread_cond_wait () from /lib/libc.so.6 #3 0xb6c27750 in wait (time=, this=) at thread/qwaitcondition_unix.cpp:87 #4 QWaitCondition::wait (time=, this=) at thread/qwaitcondition_unix.cpp:159 #5 0xb5defa04 in QHostInfoAgent::run (this=0x85140a8) at kernel/qhostinfo.cpp:260 #6 0xb6c26623 in QThreadPrivate::start (arg=0x85140a8) at thread/qthread_unix.cpp:188 #7 0xb5f976e5 in start_thread () from /lib/libpthread.so.0 #8 0xb5f97600 in ?? () from /lib/libpthread.so.0 Thread 1 (Thread 0xb56e9920 (LWP 22085)): [KCrash Handler] #6 0xb3efbd75 in Okular::Document::closeDocument (this=0x81349e0) at /usr/src/debug/kdegraphics-4.3.4/okular/core/document.cpp:1798 #7 0xb3fcd8b0 in Okular::Part::closeUrl (this=0x8115a00) at /usr/src/debug/kdegraphics-4.3.4/okular/part.cpp:1099 #8 0xb3fcde40 in Okular::Part::~Part (this=0x8115a00, __in_chrg=, __vtt_parm=) at /usr/src/debug/kdegraphics-4.3.4/okular/part.cpp:624 #9 0x0804fd08 in Shell::~Shell (this=0x81000e8, __in_chrg=, __vtt_parm=) at /usr/src/debug/kdegraphics-4.3.4/okular/shell/shell.cpp:145 #10 0xb6d2c253 in qDeleteInEventHandler (o=0x11) at kernel/qobject.cpp:3815 #11 0xb6d2d7c7 in QObject::event (this=0x81000e8, e=0x8684c38) at kernel/qobject.cpp:1094 #12 0xb63ba230 in QWidget::event (this=0x81000e8, event=0x8684c38) at kernel/qwidget.cpp:7951 #13 0xb6775aa4 in QMainWindow::event (this=0x81000e8, event=0x8684c38) at widgets/qmainwindow.cpp:1399 #14 0xb73ba114 in KMainWindow::event (this=0x81000e8, ev=0x8684c38) at /usr/src/debug/kdelibs-4.3.4/kdeui/widgets/kmainwindow.cpp:1101 #15 0xb7401c92 in KXmlGuiWindow::event (this=0x81000e8, ev=0x8684c38) at /usr/src/debug/kdelibs-4.3.4/kdeui/xmlgui/kxmlguiwindow.cpp:131 #16 0xb63638fc in QApplicationPrivate::notify_helper (this=0x8070938, receiver=0x81000e8, e=0x8684c38) at kernel/qapplication.cpp:4065 #17 0xb636b29e in QApplication::notify (this=0xbff61338, receiver=0x81000e8, e=0x8684c38) at kernel/qapplication.cpp:4030 #18 0xb72ce451 in KApplication::notify (this=0xbff61338, receiver=0x81000e8, event=0x8684c38) at /usr/src/debug/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302 #19 0xb6d1d32e in QCoreApplication::notifyInternal (this=0xbff61338, receiver=0x81000e8, event=0x8684c38) at kernel/qcoreapplication.cpp:610 #20 0xb6d1dfdc in sendEvent (event=, receiver=) at kernel/qcoreapplication.h:213 #21 QCoreApplicationPrivate::sendPostedEvents (event=, receiver=) at kernel/qcoreapplication.cpp:1247 #22 0xb6d1e19c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #23 0xb6d494dd in sendPostedEvents () at kernel/qcoreapplication.h:218 #24 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:276 #25 0xb5a274c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26 0xb5a2ad98 in ?? () from /usr/lib/libglib-2.0.so.0 #27 0xb5a2aebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #28 0xb6d49011 in QEventDispatcherGlib::processEvents (this=0x805ae40, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #29 0xb640529a in QGuiEventDispatcherGlib::processEvents (this=0x805ae40, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #30 0xb6d1e403 in QCoreApplication::processEvents (flags=) at kernel/qcoreapplication.cpp:803 #31 0xb25a9d8b in fontPool::locateFonts (this=0x9647050, makePK=false, locateTFMonly=false, virtualFontsFound=0xbff603cf) at /usr/src/debug/kdegraphics-4.3.4/okular/generators/dvi/fontpool.cpp:378 #32 0xb25aab29 in fontPool::locateFonts (this=0x9647050) at /usr/src/debug/kdegraphics-4.3.4/okular/generators/dvi/fontpool.cpp:261 #33 0xb2578a34 in dviRenderer::setFile (this=0x9647030, fname=..., base=...) at /usr/src/debug/kdegraphics-4.3.4/okular/generators/dvi/dviRenderer.cpp:523 #34 0xb257397b in DviGenerator::loadDocument (this=0x827adf0, fileName=..., pagesVector=...) a
[Okular-devel] [Bug 196590] bad margins, printing cuts off parts of the document
https://bugs.kde.org/show_bug.cgi?id=196590 Christian Trippe changed: What|Removed |Added CC||christiande...@web.de --- Comment #1 from Christian Trippe 2009-06-15 20:34:26 --- I have the same problem also using openSUSE packages. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 159074] Implement DVI specials as in KDVI
http://bugs.kde.org/show_bug.cgi?id=159074 Christian Trippe christiandehne web de changed: What|Removed |Added CC||christiande...@web.de --- Comment #2 from Christian Trippe 2009-01-22 08:25:29 --- b) is implemented with okular from KDE4.2 RC, but I could not figure out a way to trigger the inverse search. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 171416] Okular does not display the second page of ps_guide.ps from the gnuplot doc
http://bugs.kde.org/show_bug.cgi?id=171416 --- Comment #1 from Christian Trippe 2008-09-21 19:28:36 --- Created an attachment (id=27503) --> (http://bugs.kde.org/attachment.cgi?id=27503) Document where the second page is displayed empty -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [Bug 171416] New: Okular does not display the second page of ps_guide.ps from the gnuplot doc
http://bugs.kde.org/show_bug.cgi?id=171416 Summary: Okular does not display the second page of ps_guide.ps from the gnuplot doc Product: okular Version: 0.7.1 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: okular-devel@kde.org ReportedBy: [EMAIL PROTECTED] Version: 0.7.1 (using 4.1.2 (KDE 4.1.1 (KDE 4.1 >= 20080828)) "release 52.2", KDE:KDE4:Factory:Desktop / openSUSE_11.0) Compiler: gcc OS:Linux (i686) release 2.6.25.16-0.1-default Okular does not display the second page of ps_guide.ps from the gnuplot doc. The page is displayed as empty, which is not the case when viewed with kghostview. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
