[okular] [Bug 451573] New: Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 Bug ID: 451573 Summary: Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors' Product: okular Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- Created attachment 147527 --> https://bugs.kde.org/attachment.cgi?id=147527&action=edit Settings - Configure Okular - Accessibility - Change colors - 'Change dark and light colors' Settings - Configure Okular - Accessibility - Change colors - 'Change dark and light colors' is an excellent option to display text in full yet adjustable dark mode. But the way the options are named is confusing, because it makes little sense saying "dark" or "light" when any color can be set there. In fact under "dark color" it's the font (foreground) color setting - the one under "light color" it's the background color. And that's how they should be called. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 cipricus changed: What|Removed |Added CC||cipri...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 --- Comment #1 from cipricus --- So, instead of : * "Change dark and light colors" >"Change foreground and background colors" * "Dark color">"Foreground color" * "Light color" >"Background color" -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 --- Comment #3 from cipricus --- (In reply to Bug Janitor Service from comment #2) > A possibly relevant merge request was started @ > https://invent.kde.org/graphics/okular/-/merge_requests/587 I have changed my mind after seeing reply by @davidhurka (https://invent.kde.org/graphics/okular/-/merge_requests/587#note_416624). I now think that the present terminology is preferable to the one mentioned in this bug report and that a change could be proposed in favor of "black" and "white'. My argument is here: https://invent.kde.org/graphics/okular/-/merge_requests/587#note_417031 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 --- Comment #4 from cipricus --- I think this is not the case, and should be closed. I have argued here: https://invent.kde.org/graphics/okular/-/merge_requests/587#note_417031 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451651] New: "Dark color" should be changed to "Black" and "Light color" to "White" under "Okular setting Accessibility - Change dark and light colors'
https://bugs.kde.org/show_bug.cgi?id=451651 Bug ID: 451651 Summary: "Dark color" should be changed to "Black" and "Light color" to "White" under "Okular setting Accessibility - Change dark and light colors' Product: okular Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- Created attachment 147581 --> https://bugs.kde.org/attachment.cgi?id=147581&action=edit the setting discussed here Within the discussion (https://invent.kde.org/graphics/okular/-/merge_requests/587#) of my previous bug report (https://bugs.kde.org/show_bug.cgi?id=451573) I was convinced that I was wrong, but the same line of argument that has convinced me imposes a further clarification. Those settings are not about foreground and background, nor about text or images. Any text or image would be treated as a monochrome one (with degrees of black and white), "Dark color" setting will replace black, "Light color" setting will replace white. For example, if "Dark color" is set to red and "Light color" is set to purple, the proportion of red and purple will follow the initial proportions of black and white from the monochrome base. That means that "black" should be used for "dark" and "white" for "light" as more adequate naming of those settings, because that's what is happening in fact: the color selected under "light color" setting (purple in example) will 100% replace light color only if that is fully white, otherwise (if it has some degree of black) it will mix it with the color set under the "dark color" setting (red in example)! The advantage of that would be to add more clarity: dark and light are relative terms, black and white correspond exactly to what is happening here. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451651] "Dark color" should be changed to "Black" and "Light color" to "White" under "Okular setting Accessibility - Change dark and light colors'
https://bugs.kde.org/show_bug.cgi?id=451651 --- Comment #1 from cipricus --- The setting discussed here imposes degrees of just 2 colors on a dark/light structure — and this structure can only by a monochrome one, with degrees of black and white. The 2 colors that can be selected here are proportionally replacing black and white within the monochrome structure. When we set a color (e.g. red, #aa) under "dark color" option, #aa will effectively replace absolute black (#00), and if we set it under "light color" it will replace full white (#ff). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451651] "Dark color" should be changed to "Black" and "Light color" to "White" under "Okular setting Accessibility - Change dark and light colors'
https://bugs.kde.org/show_bug.cgi?id=451651 --- Comment #2 from cipricus --- I mean that the name of the option 'Color mode: Change dark and light colors' should NOT be changed, because it describes well *what* it does, but that the 2 color selection options (which describe *how* it does it) should be renamed to "black" and "white". -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451651] "Dark color" should be changed to "Black" and "Light color" to "White" under "Okular setting Accessibility - Change dark and light colors'
https://bugs.kde.org/show_bug.cgi?id=451651 --- Comment #3 from cipricus --- In the present form, a real color (expressed in numerical form of complete clarity) is supposed to replace something called "dark" or "light color", which is not a real color but a relation between two colors, and thus cannot be replaced by a real color. (What that specific, numerically defined, real color replaces is pure black or pure white). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] New: Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 Bug ID: 457018 Summary: Full screen fails and displays a window without toolbar Product: okular Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- SUMMARY https://www.reddit.com/r/kde/comments/w5ab68/okuar_if_in_full_screen_while_tabs_are_disabled/ STEPS TO REPRODUCE 1. Option to open new documents in tab is disabled 2. Full screen is enabled for an open document (this first document can be then closed; the result is the same) 3. Open a new document from the file manager OBSERVED RESULT The new document is not full screen and it has no toolbar. If this is closed and the initial document is opened it is also affected. Menus and fullscreen can be triggered with shortcut. Toolbar can also be restored from shortcut - if that was set. EXPECTED RESULT The second document should be fullscreen or in normal view If a fullscreen document is closed and then re-opened it opens in fullscreen. But if instead a new one is opened this is not fullscreen and has no toolbar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 --- Comment #1 from cipricus --- If a fullscreen document is closed and then re-opened it opens in fullscreen. But if instead a new one is opened (if the first one is closed and stays closed) this (the second one) is not fullscreen and has no toolbar. If the first document opened in fullscreen is not closed, then the second one is also opened in fullscreen. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 --- Comment #3 from cipricus --- (In reply to Albert Astals Cid from comment #2) > i guess you're using Plasma/Wayland instead of Plasma/X11? Can you confirm > all works fine in Plasma/X11? No, it is not in Wayland, I only use X11. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 --- Comment #4 from cipricus --- (In reply to cipricus from comment #3) > (In reply to Albert Astals Cid from comment #2) > > i guess you're using Plasma/Wayland instead of Plasma/X11? Can you confirm > > all works fine in Plasma/X11? > > No, it is not in Wayland, I only use X11. Fedora 36 KDE, Plasma 5.25.3, Okular 22.04.1. I though this issue more severe before realizing I can set a shortcut for restoring toolbar. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 --- Comment #5 from cipricus --- I am changing my mind back - the settings should be called "background" and "text" - based on new arguments, detailed here: https://www.reddit.com/r/kde/comments/ydv4g7/comment/itubc9q/?utm_source=share&utm_medium=web2x&context=3 https://www.reddit.com/r/kde/comments/ydqsvc/comment/itubuzf/?utm_source=share&utm_medium=web2x&context=3 In fact this is related to the fact whether images should be affected by color change or not. it seems obvious to me that thay should not, as asked here: https://www.reddit.com/r/kde/comments/ydqsvc/okular_invert_colors_but_not_for_images/?utm_source=share&utm_medium=web2x&context=3 The contrary argument (namely: that the background can be light or dark) makes sense only for images. But if images should not be affected by color change then the color change settings are really only about background and foreground=text. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 --- Comment #6 from cipricus --- There is a case where images should be affected by color change: when these images are images of text, where again "background color" and "text color" would be useful terminology. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change foreground and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 cipricus changed: What|Removed |Added Version|21.12.3 |22.08.2 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 451573] Okular setting Accessibility - Change dark and light colors - should be renamed to 'Change text and background colors'
https://bugs.kde.org/show_bug.cgi?id=451573 cipricus changed: What|Removed |Added Summary|Okular setting |Okular setting |Accessibility - Change dark |Accessibility - Change dark |and light colors - should |and light colors - should |be renamed to 'Change |be renamed to 'Change text |foreground and background |and background colors' |colors' | -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461012] Add a possibility for image to ignore color change
https://bugs.kde.org/show_bug.cgi?id=461012 cipricus changed: What|Removed |Added CC||cipri...@gmail.com Summary|Add a possibility for image |Add a possibility for image |to ignore color mode|to ignore color change -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461012] Add a possibility for image to ignore color change
https://bugs.kde.org/show_bug.cgi?id=461012 --- Comment #1 from cipricus --- The only use for color change in images seem to be when the images are images of text. In many cases they are not, so changing their colors is not useful and should be optional. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461012] Feature request: Add a possibility for image to ignore color change
https://bugs.kde.org/show_bug.cgi?id=461012 cipricus changed: What|Removed |Added Summary|Add a possibility for image |Feature request: Add a |to ignore color change |possibility for image to ||ignore color change -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461015] New: Feature request: add option to set colors of background and text no matter their initial color
https://bugs.kde.org/show_bug.cgi?id=461015 Bug ID: 461015 Summary: Feature request: add option to set colors of background and text no matter their initial color Classification: Applications Product: okular Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- Created attachment 153215 --> https://bugs.kde.org/attachment.cgi?id=153215&action=edit image with pdf page colors Some pdf files have text pages that are in fact images of book text pages with multiple colors and shades. Inverting the colors or changing the colors only imposes two selected colors onto that and readability is not improved. STEPS TO REPRODUCE 1. Open a page like that in part 1 of attachment, setting a "light" (background) color of #1b1e20, and a "dark" (font) color of #1b1e20 OR: 2. invert colors. OBSERVED RESULT 1. it looks like the page part 2 of attachment; the background color is not uniform and lighter than expected (mostly about #434A50); the text color is darker than expected (about #C5D8E9) OR: 2. it looks like part 3 of attachment; the background is bright blue (#1F446E) EXPECTED RESULT The colors should be those selected initially. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.1 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461015] Feature request: add option to set colors of background and text no matter their initial color
https://bugs.kde.org/show_bug.cgi?id=461015 --- Comment #1 from cipricus --- Correction: STEPS TO REPRODUCE 1. Open a page like that in part 1 of attachment, setting a "light" (background) color of #1b1e20, and a "dark" (font) color of #d5e9fc -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461012] Feature request: Add a possibility for image to ignore color change
https://bugs.kde.org/show_bug.cgi?id=461012 --- Comment #3 from cipricus --- (In reply to David Hurka from comment #2) > You forget the superweapon of digitalization: scanned PDFs. ;) There are indeed many pdf files made out of images (that is: images of text), but not most of them, and many are a mix of text (not image) and image (pictures, pictural forms, not text). For the latter it makes no sense whatsoever to see them inverted or with their colors modified according to a setting that makes sense only for text. Therefore an option not to apply to image the color for text (non-image text) would be great. (e.g. such option is present in Foxit Reader for Linux). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 --- Comment #6 from cipricus --- I have this bug again from time to time always in relation to Okular being closed while in fullscreen. Kubuntu 22.10 with backports repos. Plasma 5.26.2 Okular 22.08.2 looking back this is an very very old bug! for example a report from 2009: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/329337 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 457018] Full screen fails and displays a window without toolbar
https://bugs.kde.org/show_bug.cgi?id=457018 cipricus changed: What|Removed |Added Platform|Fedora RPMs |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461876] New: Full-screen should also hide tabs
https://bugs.kde.org/show_bug.cgi?id=461876 Bug ID: 461876 Summary: Full-screen should also hide tabs Classification: Applications Product: okular Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- If opening new files in tabs is enabled, full-screen doesn't hide the tabs, which beats the purpose of using full-sceen. The expected result is to have the "full" full-srceen, no matter if tabs are enabled or not: as far as I know from other applications that support both tabs and full-screen view, tabs being part of the main GUI and full-screen being a way to hide that GUI, tabs should be hidden in full-screen, like it happens in internet browsers. It makes little sense to hide panels (and thus panel-tabs as it were, of other applications), window manager borders and the rest, while keeping different tabs within Okular visible. In full-screen view tabs should be hidden - and become visible only when pushing the upper margin. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] New: Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 Bug ID: 462304 Summary: Okular and other poppler related tools cannot handle some pdf pages Classification: Applications Product: okular Version: 22.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: cipri...@gmail.com Target Milestone: --- Created attachment 154078 --> https://bugs.kde.org/attachment.cgi?id=154078&action=edit example of the pdf page Okular views as blank Okular cannot see the content of many pages of an old scanned book. they appear blank although many other tools can see them just fine (internet browser except Falkon, Adobe Reader, Foxit, Master PDF, WPS PDF, LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer). The problem seems to be with poppler, because qpdfviewer and Falkon have the same problem. As far as I could test Evince cannot even open that pdf. I couldn't get technical details on that type of page, so I'll upload here a sample. More details at links posted here: https://www.reddit.com/r/kde/comments/z591ia/how_come_only_okular_cannot_see_this_pdf_page/?utm_source=share&utm_medium=web2x&context=3 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #1 from cipricus --- > internet browser except Falkon, Adobe Reader, Foxit, Master PDF, WPS PDF, > LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer What I mean is: only Okular, qpdfview, Falkon and Evince seem affected; the rest of the tools that I've tested (internet browsers - excepting Falkon -, Adobe Reader, Foxit, Master PDF, WPS PDF, LibreOffice Draw, ImageMagick, mupdf, PDF Studio Viewer) are not affected. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #2 from cipricus --- Comment on attachment 154078 --> https://bugs.kde.org/attachment.cgi?id=154078 example of the pdf page Okular views as blank Open that in Okular or qpdfview: only a footer is see. Open it in an internet browser other than Falkon, in adobe Reader, Foxit reader, mupdf, Master pdf etc and the page is seen in full. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #3 from cipricus --- If that page is printed as pdf in Firefox or (after selecting "print as image") in Chromium/Chrome-based browsers, the resulting pdf is seen ok in Okular. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #6 from cipricus --- (In reply to Oliver Sander from comment #5) > Can you post a poppler bug for this, please? Are you addressing me or the previous comment? Should I post that bug? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #8 from cipricus --- (In reply to Oliver Sander from comment #7) > Yes please. You should be able to reproduce the bug with the `pdftoppm` > tool (which is part of poppler). That way, your bug report becomes > independent from Okular. I see, I have tested with Atril and Evince and they are no better than Okular, clearly this is not Okular-specific. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #9 from cipricus --- (In reply to Oliver Sander from comment #7) > Yes please. You should be able to reproduce the bug with the `pdftoppm` > tool (which is part of poppler). That way, your bug report becomes > independent from Okular. Sorry, what is the exact package affected by the bug? Is it called "poppler"? Or "poppler-utils"? Should the bug report be posted here? Or because it'd not a kde bug must be posted under a different bug-reporting website? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 --- Comment #10 from cipricus --- (In reply to Oliver Sander from comment #7) > Yes please. You should be able to reproduce the bug with the `pdftoppm` > tool (which is part of poppler). That way, your bug report becomes > independent from Okular. I have posted as a popple bug here: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1319 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 cipricus changed: What|Removed |Added CC||cipri...@gmail.com --- Comment #53 from cipricus --- (In reply to medin from comment #50) > I solved my problem by removing "~/.local/share/kxmlgui5/okular/shell.rc" > file then Okular showed the correct menu entries, but that removed file is > never recreated again. Seeing this again in 23.08.1. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #54 from cipricus --- (In reply to medin from comment #50) > I solved my problem by removing "~/.local/share/kxmlgui5/okular/shell.rc" > file then Okular showed the correct menu entries, but that removed file is > never recreated again. In my case the file was recreated. Okular 23.08.1. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #55 from cipricus --- (In reply to cipricus from comment #54) > (In reply to medin from comment #50) > > I solved my problem by removing "~/.local/share/kxmlgui5/okular/shell.rc" > > file then Okular showed the correct menu entries, but that removed file is > > never recreated again. > > In my case the file was recreated. Okular 23.08.1. Kubuntu 23.10. The problem is also recurrent. I have removed the whole "~/.local/share/kxmlgui5/okular/" folder yesterday to fix the problem and now the problem and the folder is in place with both files part.rc and shell.rc. I think that what causes this is the configuring of the toolbar (adding buttons). I'll test that leaving it default is a "solution". -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #56 from cipricus --- (In reply to Albert Astals Cid from comment #14) > Can you send your .local/share/kxmlgui5/okular/part.rc file over? > > Do you remember doing any customization to your menus/toolbar/shortcuts? > > Can you confirm that removing your .local/share/kxmlgui5/okular/part.rc file > (save it first somewhere else) fixes this? I can confirm that on at least one occasion removing just part.rc file fixed it, and that on at least another one occasion I had to delete the shell.rc too (or maybe only that should have been removed, something confirmed by people on a reddit afaicr). Re-setting to defaults (Settings-Configure toolbars-Default) fixes it too, because that removes both files. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #57 from cipricus --- > Editing ~/.local/share/kxmlgui5/okular/shell.rc and removing noMerge="1" > fixes this issue. In that file I have 5 occurrences: `` line 4 ` ` line 20 line 25 line 38 line 53 What should I remove to fix it? Is that a permanent fix, so I don't have to reset my toolbar? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 402779] Okular, when printing 2 pages per sheet, prints the wrong pages.
https://bugs.kde.org/show_bug.cgi?id=402779 cipricus changed: What|Removed |Added CC||cipri...@gmail.com --- Comment #4 from cipricus --- I only see this behavior when I select landscape instead of portrait. (In other applications, when selecting two pages per sheet, there is no need for selecting landscape. The need for selecting landscape here is the result of a misleading image in the preview, where the 2 pages are not seen as expected parallel pages on the same sheet, but as two texts, one on top of the other. Selecting landscape doesn't fix the problem because the same two text appear one on top of the other, inner landscape form anyway, but the user is tempted to make some changes to fix the initial problem in preview. So it might end up with landscape setting which instead leads to this odd occurrence.) If two pages per sheet are selected with the default ”Portrait” setting, the printing is okay, although the image preview before printing is confusing. -- You are receiving this mail because: You are the assignee for the bug.
