[Okular-devel] [okular] [Bug 329907] New: Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 Bug ID: 329907 Summary: Print from Okular crahses Classification: Unclassified Product: okular Version: 0.17.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: ol...@quickaudio.com Application: okular (0.17.5) KDE Platform Version: 4.11.5 Qt Version: 4.8.5 Operating System: Linux 3.12.6-200.fc19.x86_64 x86_64 Distribution: Fedora release 19 (Schrödinger’s Cat) -- Information about the crash: - What I was doing when the application crashed: While filling out a PDF with forms, I selected it to print while still in the show forms mode. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f0401e148c0 (LWP 25949))] Thread 2 (Thread 0x7f03f21b5700 (LWP 28037)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003d62a7b1e6 in wait (time=18446744073709551615, this=0x17c0b00) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=optimized out, mutex=mutex@entry=0x18a3750, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x003d62a7738b in QSemaphore::acquire (this=this@entry=0x18549b0, n=n@entry=1) at thread/qsemaphore.cpp:144 #4 0x7f03e3dfb5cf in GSRendererThread::run (this=0x18549a0) at /usr/src/debug/okular-4.11.5/generators/spectre/rendererthread.cpp:50 #5 0x003d62a7ad0f in QThreadPrivate::start (arg=0x18549a0) at thread/qthread_unix.cpp:338 #6 0x003d56e07c53 in start_thread (arg=0x7f03f21b5700) at pthread_create.c:308 #7 0x003d562f5dbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f0401e148c0 (LWP 25949)): [KCrash Handler] #6 gs_lcms2_malloc (id=0x0, size=3744) at base/gsicc_lcms2.c:49 #7 0x003d7c80e6ed in _cmsMallocZeroDefaultFn (ContextID=optimized out, size=3744) at cmserr.c:97 #8 0x003d7c814c12 in cmsCreateProfilePlaceholder (ContextID=ContextID@entry=0x0) at cmsio0.c:461 #9 0x003d7c816048 in cmsOpenProfileFromMemTHR (ContextID=0x0, MemPtr=0x18e4640, dwSize=725408) at cmsio0.c:1034 #10 0x7f03f38ff1e3 in GfxICCBasedColorSpace::parse (arr=optimized out, gfx=gfx@entry=0x18a1a60, recursion=recursion@entry=0) at GfxState.cc:1727 #11 0x7f03f38feca3 in GfxColorSpace::parse (csObj=0x72abae20, gfx=0x18a1a60, recursion=0) at GfxState.cc:294 #12 0x7f03f38dcbe6 in Gfx::opSetFillColorSpace (this=0x18a1a60, args=0x72abaf50, numArgs=optimized out) at Gfx.cc:1530 #13 0x7f03f38e7029 in Gfx::go (this=0x18a1a60, topLevel=optimized out) at Gfx.cc:715 #14 0x7f03f38e748d in Gfx::display (this=this@entry=0x18a1a60, obj=obj@entry=0x72abb240, topLevel=topLevel@entry=true) at Gfx.cc:681 #15 0x7f03f3927ddc in Page::displaySlice (this=this@entry=0xf7f800, out=out@entry=0xfde590, hDPI=hDPI@entry=72, vDPI=vDPI@entry=72, rotate=rotate@entry=0, useMediaBox=useMediaBox@entry=false, crop=optimized out, sliceX=sliceX@entry=-1, sliceY=sliceY@entry=-1, sliceW=sliceW@entry=-1, sliceH=sliceH@entry=-1, printing=printing@entry=true, abortCheckCbk=abortCheckCbk@entry=0x0, abortCheckCbkData=abortCheckCbkData@entry=0x0, annotDisplayDecideCbk=annotDisplayDecideCbk@entry=0x3b1a85c440 Poppler::annotDisplayDecideCbk(Annot*, void*), annotDisplayDecideCbkData=annotDisplayDecideCbkData@entry=0x72abb5ff) at Page.cc:523 #16 0x7f03f3942fdc in PSOutputDev::checkPageSlice (this=0x189a2d0, page=0xf7f800, rotateA=0, useMediaBox=optimized out, crop=true, sliceX=-1, sliceY=-1, sliceW=-1, sliceH=-1, printing=true, abortCheckCbk=0x0, abortCheckCbkData=0x0, annotDisplayDecideCbk=0x3b1a85c440 Poppler::annotDisplayDecideCbk(Annot*, void*), annotDisplayDecideCbkData=0x72abb5ff) at PSOutputDev.cc:3072 #17 0x7f03f3927d0e in Page::displaySlice (this=0xf7f800, out=0x189a2d0, out@entry=0x72abb610, hDPI=72, hDPI@entry=6.9533447591547972e-310, vDPI=72, vDPI@entry=6.8998712124876214e-310, rotate=0, rotate@entry=-1, useMediaBox=useMediaBox@entry=false, crop=true, crop@entry=255, sliceX=sliceX@entry=-1, sliceY=sliceY@entry=-1, sliceW=sliceW@entry=-1, sliceH=sliceH@entry=-1, printing=printing@entry=true, abortCheckCbk=abortCheckCbk@entry=0x0, abortCheckCbkData=abortCheckCbkData@entry=0x0, annotDisplayDecideCbk=annotDisplayDecideCbk@entry=0x3b1a85c440 Poppler::annotDisplayDecideCbk(Annot*, void*), annotDisplayDecideCbkData=annotDisplayDecideCbkData@entry=0x72abb5ff) at Page.cc:511 #18 0x7f03f3927f4e in Page::display (this=optimized out, out=out@entry=0x72abb610, hDPI=hDPI@entry=6.9533447591547972e-310, vDPI=vDPI@entry=6.8998712124876214e-310, rotate=rotate@entry=-1,
[Okular-devel] [okular] [Bug 329907] Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 --- Comment #1 from ol...@quickaudio.com --- I should have written that I selected Print Preview. -- 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] [okular] [Bug 329907] Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 --- Comment #3 from ol...@quickaudio.com --- Created attachment 84612 -- https://bugs.kde.org/attachment.cgi?id=84612action=edit The crashing pdf -- 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] [okular] [Bug 329907] Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 --- Comment #2 from ol...@quickaudio.com --- The recipe with the attached PDF file is: Select Print Preview: notice that the preview window is empty. Close the Print Preview window. Select Print Preview again. Okular crashes. -- 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] [okular] [Bug 208121] incorrect space characters in pdf form
https://bugs.kde.org/show_bug.cgi?id=208121 Egor glu...@gmail.com changed: What|Removed |Added CC||glu...@gmail.com --- Comment #24 from Egor glu...@gmail.com --- Hits me too. KDE SC 4.11.2 Okular 0.17.2 Forced rasterization is a viable workaround but produces low-quality image. -- 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] [okular] [Bug 208121] incorrect space characters in pdf form
https://bugs.kde.org/show_bug.cgi?id=208121 --- Comment #25 from Egor glu...@gmail.com --- (In reply to comment #24) Hits me too. KDE SC 4.11.2 Okular 0.17.2 Forced rasterization is a viable workaround but produces low-quality image. Ah, no, the quality is also fine. The glitches were just on the screen, where the page was scaled to fit width, 1.5x of its real size. Printed page is great, thanks for the option «Force rasterization» -- 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
Re: [Okular-devel] Review Request 111829: Use DPI of current screen for PDF rendering
On Jan. 13, 2014, 1:40 a.m., Albert Astals Cid wrote: I did some small changes on my own so we did not have to go back and forth more which would have just made it slow for all. Thanks for the patch :-) Thanks! Very happy that Okular now shows PDF in correct scale! - Eugene --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111829/#review47283 --- On Jan. 13, 2014, 1:39 a.m., Eugene Shalygin wrote: --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111829/ --- (Updated Jan. 13, 2014, 1:39 a.m.) Review request for Okular and Albert Astals Cid. Bugs: 268757 http://bugs.kde.org/show_bug.cgi?id=268757 Repository: okular Description --- This patch relies on master branch of LibKScreen. This patch does not solve the problem in bug completely, but makes Okular behaviour more correct (see below). The problem (in the bug) is that Okular uses fixed DPI for PDF rendering (72.0 dots per inch) and therefore scale of rendered document becomes incorrect. With current mainline laptop screens having DPI easily twice larger than this constant (72), the problem shows itself quiet strongly. Additional problems araise with multiscreen configuration, when 1) DPI of each individual screen may be different, and 2) there is no tools in Qt to detect DPI of individual screens in virtual desktop mode. Therefore XRandr has to be used for DPI detection. Raw XRandr is bad dependency for Okular and libkscreen is proposed instead. This patch approach to the solution in the following way: 1. libkscreen detection staff is added to CMakeLists.txt and config.h 2. It changes Utils::realDpi() function to use libkscreen if present. With libkscreen the function looks for output that contains maximal part of given widget (suppose to be used for document rendering) and returns DPI of that screen. 3. Genenerator interface is extended by adding UtilizeDPI feature and setDPI() method, that is called by Document class right before calling loadXXX() if the generator supports this feature 4. Poppler generator is changed to support UtilizeDPI feature. 5. PageSizeMetric enum is extended with Pixels value to explicitly say that page size is defined in screen pixels (see my posts in the bug); Poppler generator uses this case. To completetly fix the bug, Document must invalidate generated pixmaps after the widget movements into another screen. I do not know how to track this without subclassing the main window class. Therefore I decided to publish this part of work to get your responce, especially regarding item 3 (Generator class changes). In the current state, manual reloading of a document after moving Okular to another screen fixes the scale, that is, in my eyes, is quiet helpful already. Even if we subclass the Okular main window, I do not know what to do when Okular is used as KPart. Diffs - CMakeLists.txt 217337f config-okular.h.cmake 7217f8d core/document.cpp 3af92c8 core/generator.h a5a971b core/generator.cpp 41beb92 core/generator_p.h b59293a core/utils.h 8d5d5fc core/utils.cpp 5dd8448 generators/poppler/generator_pdf.h 5d5853a generators/poppler/generator_pdf.cpp 1a44523 Diff: https://git.reviewboard.kde.org/r/111829/diff/ Testing --- Manual. In all screens, that report correct physical size to XRandr, size of documents is correct Thanks, Eugene Shalygin ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 329881] Okular crashed opening the print dialogue
https://bugs.kde.org/show_bug.cgi?id=329881 --- Comment #3 from idoitprone monkeyboy...@yahoo.com --- https://bugreports.qt-project.org/browse/QTBUG-36146 Submitted the bug to qt. -- 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] [okular] [Bug 329881] Okular crashed opening the print dialogue
https://bugs.kde.org/show_bug.cgi?id=329881 John Layt jl...@kde.org changed: What|Removed |Added CC||jl...@kde.org --- Comment #4 from John Layt jl...@kde.org --- My comment on the Qt bug report: This is a Fedora-specific bug, they have patched Qt to use cupsEnumDests() which Qt doesn't normally use (see bug https://bugzilla.redhat.com/show_bug.cgi?id=980952 where they did so). Please raise this bug with Fedora, thanks! -- 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] vtable error [Was: Re: Review Request 111410: Selection tool: copy/extract as vector graphic by calling pdftocairo]
Hello, No, I am building on a RAM disk, empty build directory. No moc files in sources, just checked. Do you get the same error with my patch? This information would allow me to better trace back this error... Bye, Thomas Thomas Fischer wrote: I will upload a new patch soon. It should address the three issues, except for that I have problems linking the code (undefined reference to `vtable for PDFGenerator'). Maybe you can see what the problem is ... You usually get that where some .moc problem is happening. Make sure you have a clean build. signature.asc Description: OpenPGP digital signature ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
[Okular-devel] [okular] [Bug 329925] New: Use content negotiation to determine type of data to transfer for the X Windows selection
https://bugs.kde.org/show_bug.cgi?id=329925 Bug ID: 329925 Summary: Use content negotiation to determine type of data to transfer for the X Windows selection Classification: Unclassified Product: okular Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: hohy...@eml.cc Presently, when the selection can be interpreted as either text or graphics, Okular prompts the user with options to select text or graphics for the X Windows selection or clipboard. This feature is to not prompt the user for what type to use for the clipboard data, but instead to use the built in mechanism for content negotiation with the application receiving the selection. Here is some information about content negotiation. http://www.jwz.org/doc/x-cut-and-paste.html Reproducible: Always -- 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] [okular] [Bug 329925] Use content negotiation to determine type of data to transfer for the X Windows selection
https://bugs.kde.org/show_bug.cgi?id=329925 Albert Astals Cid aa...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||aa...@kde.org Ever confirmed|0 |1 --- Comment #1 from Albert Astals Cid aa...@kde.org --- I guess it makes sense. Thought it'd increase a bit the code complexity and honestly i think that at the point of doing the square selection you know what you want to do. But i'm not oposed to patches :-) -- 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] [okular] [Bug 329907] Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 Albert Astals Cid aa...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||aa...@kde.org Ever confirmed|0 |1 --- Comment #4 from Albert Astals Cid aa...@kde.org --- Bad interaction between libgs, liblcms and poppler :( -- 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] [okular] [Bug 329907] Print from Okular crahses
https://bugs.kde.org/show_bug.cgi?id=329907 --- Comment #5 from Albert Astals Cid aa...@kde.org --- For the record http://lists.freedesktop.org/archives/poppler/2014-January/010779.html -- 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
Re: [Okular-devel] Review Request 111410: Selection tool: copy/extract as vector graphic by calling pdftocairo
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111410/#review47351 --- ui/minibar.h https://git.reviewboard.kde.org/r/111410/#comment33714 I'd appreciate if you did not revert my code. - Albert Astals Cid On Jan. 12, 2014, 9:46 p.m., Thomas Fischer wrote: --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111410/ --- (Updated Jan. 12, 2014, 9:46 p.m.) Review request for Okular. Repository: okular Description --- This patch implements the feature request of bug 321350: if a PDF file is viewed, the selection tool offers the new extraction method vector which allows to save to a file (PDF, SVG, EPS, PostScript). The crop operation is performed by calling pdftocairo with matching arguments. The resulting file contains the original PDF file's content without rendering it to a pixmap. I am not sure if calling an external program is an acceptable solution for this problem. However, it is tested if the program is available before showing the new option. Alternatively, the code of pdftocairo (as part of poppler) would had to be copied and integrated into Okular increasing the solution's complexity. I am not aware of a similar solution available using poppler-qt4 only. Maybe using a QPrinter printing to PDF would have been an alternative, but again this seemed to be too complex. Diffs - core/document.h fe296e0 core/document.cpp fa6345f core/generator.h 3cf40c2 core/generator.cpp 41beb92 generators/poppler/generator_pdf.h 5d5853a generators/poppler/generator_pdf.cpp 839a324 ui/minibar.h 5654ad8 ui/minibar.cpp 6a501b8 ui/pageview.cpp 65967bf Diff: https://git.reviewboard.kde.org/r/111410/diff/ Testing --- Thanks, Thomas Fischer ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] vtable error [Was: Re: Review Request 111410: Selection tool: copy/extract as vector graphic by calling pdftocairo]
El Dilluns, 13 de gener de 2014, a les 09:26:35, Thomas Fischer va escriure: Hello, No, I am building on a RAM disk, empty build directory. No moc files in sources, just checked. Do you get the same error with my patch? This information would allow me to better trace back this error... Yes, it also fails to compile here, my suggestion, don't have a class with a Q_OBJECT in the .cpp file, may be confusing moc. Cheers, Albert Bye, Thomas Thomas Fischer wrote: I will upload a new patch soon. It should address the three issues, except for that I have problems linking the code (undefined reference to `vtable for PDFGenerator'). Maybe you can see what the problem is ... You usually get that where some .moc problem is happening. Make sure you have a clean build. ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
Re: [Okular-devel] Review Request 111829: Use DPI of current screen for PDF rendering
On Jan. 13, 2014, 12:40 a.m., Albert Astals Cid wrote: I did some small changes on my own so we did not have to go back and forth more which would have just made it slow for all. Thanks for the patch :-) Eugene Shalygin wrote: Thanks! Very happy that Okular now shows PDF in correct scale! Very nice, thanks for the work! I love it when software adapts :) - Christoph --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111829/#review47283 --- On Jan. 13, 2014, 12:39 a.m., Eugene Shalygin wrote: --- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/111829/ --- (Updated Jan. 13, 2014, 12:39 a.m.) Review request for Okular and Albert Astals Cid. Bugs: 268757 http://bugs.kde.org/show_bug.cgi?id=268757 Repository: okular Description --- This patch relies on master branch of LibKScreen. This patch does not solve the problem in bug completely, but makes Okular behaviour more correct (see below). The problem (in the bug) is that Okular uses fixed DPI for PDF rendering (72.0 dots per inch) and therefore scale of rendered document becomes incorrect. With current mainline laptop screens having DPI easily twice larger than this constant (72), the problem shows itself quiet strongly. Additional problems araise with multiscreen configuration, when 1) DPI of each individual screen may be different, and 2) there is no tools in Qt to detect DPI of individual screens in virtual desktop mode. Therefore XRandr has to be used for DPI detection. Raw XRandr is bad dependency for Okular and libkscreen is proposed instead. This patch approach to the solution in the following way: 1. libkscreen detection staff is added to CMakeLists.txt and config.h 2. It changes Utils::realDpi() function to use libkscreen if present. With libkscreen the function looks for output that contains maximal part of given widget (suppose to be used for document rendering) and returns DPI of that screen. 3. Genenerator interface is extended by adding UtilizeDPI feature and setDPI() method, that is called by Document class right before calling loadXXX() if the generator supports this feature 4. Poppler generator is changed to support UtilizeDPI feature. 5. PageSizeMetric enum is extended with Pixels value to explicitly say that page size is defined in screen pixels (see my posts in the bug); Poppler generator uses this case. To completetly fix the bug, Document must invalidate generated pixmaps after the widget movements into another screen. I do not know how to track this without subclassing the main window class. Therefore I decided to publish this part of work to get your responce, especially regarding item 3 (Generator class changes). In the current state, manual reloading of a document after moving Okular to another screen fixes the scale, that is, in my eyes, is quiet helpful already. Even if we subclass the Okular main window, I do not know what to do when Okular is used as KPart. Diffs - CMakeLists.txt 217337f config-okular.h.cmake 7217f8d core/document.cpp 3af92c8 core/generator.h a5a971b core/generator.cpp 41beb92 core/generator_p.h b59293a core/utils.h 8d5d5fc core/utils.cpp 5dd8448 generators/poppler/generator_pdf.h 5d5853a generators/poppler/generator_pdf.cpp 1a44523 Diff: https://git.reviewboard.kde.org/r/111829/diff/ Testing --- Manual. In all screens, that report correct physical size to XRandr, size of documents is correct Thanks, Eugene Shalygin ___ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
