[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow

[Luca Manganelli]

https://bugs.kde.org/show_bug.cgi?id=384267

Luca Manganelli  changed:

   What|Removed |Added

 CC||luc...@gmail.com

--- Comment #19 from Luca Manganelli  ---
Please fix this bug. This is an accessibility issue to me (I cannot see much
difference from white and yellow for my eye problem)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 452340] Instant crash on Android

[Luca]

https://bugs.kde.org/show_bug.cgi?id=452340

--- Comment #2 from Luca  ---
(In reply to Albert Astals Cid from comment #1)
> Can you try installing this apk and confirming if it works for you? 
> 
> https://binary-factory.kde.org/job/Okular_Nightly_android-arm64/
> lastSuccessfulBuild/artifact/okularkirigami-arm64-v8a.apk

Sadly, it doesn't.
Yet this time, at least, Android says "Okular keeps closing, try to repair it
by clearing data" or something like that (I'm Italian, my phone is in Italian,
it's a rough translation).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 452340] Instant crash on Android

[Luca]

https://bugs.kde.org/show_bug.cgi?id=452340

Luca  changed:

   What|Removed |Added

   Platform|Other   |Android
 OS|Other   |Android 11.x

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 452340] New: Instant crash on Android

[Luca]

https://bugs.kde.org/show_bug.cgi?id=452340

Bug ID: 452340
   Summary: Instant crash on Android
   Product: okular
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: elle.ess...@protonmail.com
  Target Milestone: ---

Instant crash on Okular for Android (F-Droid version, Okular 1.3.0). No
feedback nor "the app does not respond" pops up, simply it doesn't open.
***

STEPS TO REPRODUCE
1. Buy a OnePlus Nord 2, I guess. Then install the app from F-Droid
2. Open Okular
3. Look at the screen to see nothing is happening

OBSERVED RESULT
Nothing

EXPECTED RESULT
At least, a welcome screen or something

SOFTWARE/OS VERSIONS
Android 11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 440120] New: hand written annotations with stylus are unreadable after being rendered

[Luca]

https://bugs.kde.org/show_bug.cgi?id=440120

Bug ID: 440120
   Summary: hand written annotations with stylus are unreadable
after being rendered
   Product: okular
   Version: 1.9.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-devel@kde.org
  Reporter: luca.tagliaco...@gmail.com
  Target Milestone: ---

Created attachment 140239
  --> https://bugs.kde.org/attachment.cgi?id=140239=edit
hand written annotations

SUMMARY


STEPS TO REPRODUCE
1. Open a pdf
2. use the handwritten annotation tool
3. it becomes unreadable as if ink would spread around
OBSERVED RESULT
Unreadable hand written annotation

EXPECTED RESULT
Nice and smooth hand written annotation

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.04 installed over ubuntu via tasksel
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
I have just updated from 18.04 where everything worked as expected,
so it is a bug of the version shipped with 20.04
Notice that this is not that bad with the mouse, 
only the part written with a Stylus is bad, 
the wacom setting in the kde disappeared so that could be one of the reasons...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 342003] Trim margins confuses ordering of zoom steps while zooming out

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=342003

Luca Weiss  changed:

   What|Removed |Added

 CC||l...@z3ntu.xyz

--- Comment #17 from Luca Weiss  ---
Still an issue in Okular v1.11.1 (KDE Applications 20.08.1)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 401999] Pictures inserted into PDF with other PDF Editor covered by stamp icon

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=401999

Luca Weiss  changed:

   What|Removed |Added

 CC||l...@z3ntu.xyz

--- Comment #9 from Luca Weiss  ---
I believe I'm seeing the same problem with a PDF document with Okular 1.10.3 on
Arch Linux. Right clicking on the "stamp" shows "Stamp symbol: #clipboard".

Moving the stamp keeps the actual image underneath (making it possible to view
it), but the image likes to just disappear completely when scrolling/zooming
and the document has to be re-opened to view the image again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 416176] Find menu: Shift + numpad enter does not go to previous match

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=416176

--- Comment #2 from Luca Weiss  ---
Yes, Shift+F3 works as well but as Shift+Enter is a standard shortcut (and it
*mostly* works in Okular) I am quite used to using Enter & Shift+Enter.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 416176] New: Find menu: Shift + numpad enter does not go to previous match

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=416176

Bug ID: 416176
   Summary: Find menu: Shift + numpad enter does not go to
previous match
   Product: okular
   Version: 19.12.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: l...@z3ntu.xyz
  Target Milestone: ---

SUMMARY
In the Okular search field (Ctrl+F) you can press Enter to go to the next match
and Shift+Enter to go to the previous match. Pressing the enter key on the
numpad goes to the next match but pressing Shift+numpad Enter still goes to the
next match and not to the previous.

STEPS TO REPRODUCE
1. Open search bar on a .pdf document and enter a search string
2. Press Shift+Enter ("Return") to get to the previous match
3. Press Shift+numpad enter ("KP_Enter") and observe that Okular jumps to the
next match instead of the previous


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION
I've just checked in KMail in the mail view search field and funnily enough
there the behavior is the other way around, numpad enter doesn't work but
shift+numpad enter works.
Also I've read through the Okular source code a bit and it doesn't seem like
the bug is caused by Okular because it uses the returnPressed signal from
KLineEdit (which is QLineEdit?, didn't check that) and then checks
"QApplication::keyboardModifiers() == Qt::ShiftModifier" and not much more.
Still, it's a bug that's present in Okular :)
Also maybe
https://cgit.kde.org/falkon.git/commit/?id=a237c8ff874a2adeed8588709f14fdb3b766fa2f
is useful

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 396761] menu items "no text"

[Luca]

https://bugs.kde.org/show_bug.cgi?id=396761

Luca  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 CC||lucabs2...@libero.it
 Resolution|WORKSFORME  |---

--- Comment #17 from Luca  ---
This problem is still present.

Okular 1.9.0

After I hide and restored the "page bar" some entries show "no text"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 407865] If rotating the view the annotations are not rotated

[Luca Tagliacozzo]

https://bugs.kde.org/show_bug.cgi?id=407865

--- Comment #2 from Luca Tagliacozzo  ---
(In reply to David Hurka from comment #1)
> If you use the highlighter tool, do you get a “lens-shaped yellow object
> arbitrary on the page”, like in Bug 334297?
> 


If it is rotated clockwise 90 degree yes it is a lens, while if it is inverted
(rotated twice in the same diraction) no. In that case it becomes a higlited
line symmetric with respect to the center of the screen, this is the way in
which it is easier to realize that the annotation tools have not been rotated. 
> It’s not really arbitrary, but positioned like you described it. The lens
> just looks pretty irritating. I will upload a screenshot in the other bug.
> 
> If you only have this issue with Highlighter, Underline, Squiggle, and
> Strike-Out, we can mark this as duplicate of Bug 334297.

I guess you are right, free hand drawing works as expected as the straight
lines does the stamp also works, and the geometric shapes. Not sure what
squiggle and strike-out are maybe I do not have them in my version of Okular,
sorry for submitting a duplicate

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 407865] New: If rotating the view the annotations are not rotated

[Luca Tagliacozzo]

https://bugs.kde.org/show_bug.cgi?id=407865

Bug ID: 407865
   Summary: If rotating the view the annotations are not rotated
   Product: okular
   Version: 1.3.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: luca.tagliaco...@fqa.ub.edu
  Target Milestone: ---

SUMMARY

While the document is rotated, the annotation are displayed in the wrong place
(as if the document wasn't rotated)
STEPS TO REPRODUCE
1. rotate a pdf document
2. use for example the highliter
3. the higlight appears in the wrong (unwanted place in the document) as if you
were higlithing the region of the document that would be placed in the same
position of the screen if the document was not rotated

OBSERVED RESULT

wrong positioning of the annotations
EXPECTED RESULT

annotations should appear where drawn 
SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kernel 4.15.0.50-generic kunutu 18.04
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44
Qt Version: 5.9.5

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

T10812: KDE Applications

[Luca Beltrame]

lbeltrame added a comment.


  In T10812#182255 , @ngraham wrote:
  
  >
  
  
  
  
  > e "GNOME" in their name (e.g. "GNOME Chess", "GNOME Photos", etc). Despite 
this, I see no indication that people confusedly think you can't use GNOME's 
apps without the GNOME DE itself. People seem to happily
  
  For KDE software it happend *so many times* over the course of the years:
  
  - "App XXX is cool but I don't want to install KDE"
  - "I don't need KDE, so I won't use App YYY"
  
  This was the first, real reason the rebranding was agreed upon. 
  And for example in openSUSE we have people that use KDE applications with 
totally different setups (e.g. XFCE).

TASK DETAIL
  https://phabricator.kde.org/T10812

To: ngraham, lbeltrame
Cc: lbeltrame, ltoscano, cfeck, aacid, #yakuake, #okular, #dolphin, #kate, 
#spectacle, #konsole, #gwenview, #kde_pim, #kde_games, #kde_applications, 
ngraham

D12352: Make it possible to disable the build of okularkirigami

[Luca Beltrame]

lbeltrame added inline comments.

INLINE COMMENTS

> Documents.qml:56
>  }
> -text: i18n("No Documents found. To start to read, put some files in 
> the Documents folder of your device.")
> -wrapMode: Text.WordWrap
> -horizontalAlignment: Text.AlignHCenter
> -verticalAlignment: Text.AlignVCenter
> +Kirigami.Label {
> +text: i18n("No Documents found. To start to read, put some files 
> in the Documents folder of your device.")

This, and all the changes in Document.qml are unrelated.

REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D12352

To: apol, #okular, mart, aacid, lbeltrame
Cc: ngraham, aacid

D12352: Make it possible to disable the build of okularkirigami

[Luca Beltrame]

lbeltrame added inline comments.

INLINE COMMENTS

> CMakeLists.txt:127
>  
> -add_subdirectory( mobile )
> +option(BUILD_OKULARKIRIGAMI "Builds the convergent application" ON)
> +if (BUILD_OKULARKIRIGAMI)

Doesn't specify much about what a "convergent" application is (unless it's 
specified elsewhere). Perhaps "Builds a Kirigami-based, convergent version of 
Okular"?

REPOSITORY
  R223 Okular

REVISION DETAIL
  https://phabricator.kde.org/D12352

To: apol, #okular, mart, aacid, lbeltrame
Cc: ngraham, aacid

[okular] [Bug 393119] New: No way to disable okularkirigami building

[Luca Beltrame]

https://bugs.kde.org/show_bug.cgi?id=393119

Bug ID: 393119
   Summary: No way to disable okularkirigami building
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: lbeltr...@kde.org
  Target Milestone: ---

The mobile version of Okular is built unconditionally, even on desktop systems.
While its impact is arguably smaller, it would make sense to have a build
switch (even default to ON) to enable/disable building.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 393119] No way to disable okularkirigami building

[Luca Beltrame]

https://bugs.kde.org/show_bug.cgi?id=393119

Luca Beltrame <lbeltr...@kde.org> changed:

   What|Removed |Added

 CC||aleix...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 392826] Crash when opening .xps file

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=392826

--- Comment #2 from Luca Weiss <l...@z3ntu.xyz> ---
Thanks for the quick fix! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 392826] New: Crash when opening .xps file

[Luca Weiss]

https://bugs.kde.org/show_bug.cgi?id=392826

Bug ID: 392826
   Summary: Crash when opening .xps file
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: XPS backend
  Assignee: okular-devel@kde.org
  Reporter: l...@z3ntu.xyz
  Target Milestone: ---

Created attachment 111885
  --> https://bugs.kde.org/attachment.cgi?id=111885=edit
demo file

Just opening the attached .xps file makes Okular crash. Version is master
branch today (revision b25979121fd3f28788a2958b0faed250f1d1054c)

Backtrace:
#0  0x7f99642bd89c in loadEntry(KZip*, QString const&, Qt::CaseSensitivity)
[clone .constprop.299] () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so  
#1  0x7f99642c2d6b in XpsPage::loadImageFromFile(QString const&) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#2  0x7f99642c301c in XpsHandler::processImageBrush(XpsRenderNode&) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#3  0x7f99642c3b0e in XpsHandler::processEndElement(XpsRenderNode&) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#4  0x7f99642c425d in XpsHandler::endElement(QString const&, QString
const&, QString const&) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#5  0x7f99876dc478 in ?? () from /usr/lib/libQt5Xml.so.5
#6  0x7f99876e58ff in ?? () from /usr/lib/libQt5Xml.so.5
#7  0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5
#8  0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5
#9  0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5
#10 0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5
#11 0x7f99876e4e48 in ?? () from /usr/lib/libQt5Xml.so.5
#12 0x7f99876e5880 in ?? () from /usr/lib/libQt5Xml.so.5
#13 0x7f99876e845c in ?? () from /usr/lib/libQt5Xml.so.5
#14 0x7f99876e8977 in QXmlSimpleReader::parse(QXmlInputSource const*, bool)
() from /usr/lib/libQt5Xml.so.5
#15 0x7f99642c2850 in XpsPage::renderToPainter(QPainter*) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#16 0x7f99642c2a32 in XpsPage::renderToImage(QImage*) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#17 0x7f99642c2b4d in XpsGenerator::image(Okular::PixmapRequest*) () from
/usr/lib/qt/plugins/okular/generators/okularGenerator_xps.so
#18 0x7f996eca15f5 in Okular::PixmapGenerationThread::run() () from
/usr/lib/libOkular5Core.so.9
#19 0x7f993acd in ?? () from /usr/lib/libQt5Core.so.5
#20 0x7f998517508c in start_thread () from /usr/lib/libpthread.so.0
#21 0x7f998818be7f in clone () from /usr/lib/libc.so.6

If the backtrace in the Qt5 libs is needed, I can recompile it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Okular-devel] [okular] [Bug 341747] Okular crashes on Save as...

[Luca Beltrame]

https://bugs.kde.org/show_bug.cgi?id=341747

Luca Beltrame lbeltr...@kde.org changed:

   What|Removed |Added

 CC||lbeltr...@kde.org

--- Comment #4 from Luca Beltrame lbeltr...@kde.org ---
Just FYI, the Unstable:Extra repository is *not* meant to hold released
applications, they're git snapshots and should be treated as such. I've
improved the wording on our repository page
(https://en.opensuse.org/SDB:KDE_repositories#KF5.2C_Plasma_5_and_KF5-based_Applications_Unstable).
 

@Albert: I suppose you (extended to everyone working on Okular) does not want
yet BRs against the KF5 port? If so, I'll ensure this is known.

-- 
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 315844] New: Highlighting pdfs doesn't work when using keyboard shortcuts

[Luca Cerone]

https://bugs.kde.org/show_bug.cgi?id=315844

Bug ID: 315844
   Summary: Highlighting pdfs doesn't work when using keyboard
shortcuts
Classification: Unclassified
   Product: okular
   Version: 0.14.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: PDF backend
  Assignee: okular-devel@kde.org
  Reporter: luca_cer...@yahoo.it

The highlighting function can not be activated by using only the keyboard
shortcuts.
I use the default shortcuts, F6 to open the annotation window and then 4 to
select highlight.
After pressing 4 I would expect to be able to highlight the text,
but rather what I get is that I move the page using the hand browse tool

Reproducible: Always

Steps to Reproduce:
1. Open annotation window pressing F6
2. Select Highlight by pressing 4
3. Try to highlight some text
Actual Results:  
The page is moved as if the browse tool is selected rather than the highlight.

Expected Results:  
I can highlight text

-- 
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 315844] Highlighting pdfs doesn't work when using keyboard shortcuts

[Luca Cerone]

https://bugs.kde.org/show_bug.cgi?id=315844

--- Comment #2 from Luca Cerone luca_cer...@yahoo.it ---
You are right Fabio, it is not always reproducible.
after closing and opening Okular, now it is working as intended (my bad).
But definitively it is an issue with pdf.
Maybe it is because I had more than one Okular with the same document open?

-- 
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 196590] [PDF 4.3beta2 regression] bad margins, printing cuts off parts of the document

[Luca]

https://bugs.kde.org/show_bug.cgi?id=196590


Luca lucazann...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #9 from Luca lucazanna89 gmail com  2009-06-22 11:29:54 ---
*** This bug has been confirmed by popular vote. ***

-- 
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 175644] Okular jumps to wrong page when rotating

[Luca Burelli]

http://bugs.kde.org/show_bug.cgi?id=175644


Luca Burelli burellil dei unipd it changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Comment #1 from Luca Burelli burellil dei unipd it  2008-11-21 13:09:21 
---
Should be resolved in SVN, by commit closing bug #175046 (thumb list scroll to
current page when filtering).


-- 
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 175046] New: thumb list scroll to current page when filtering

[Luca Burelli]

http://bugs.kde.org/show_bug.cgi?id=175046

   Summary: thumb list scroll to current page when filtering
   Product: okular
   Version: unspecified
  Platform: unspecified
OS/Version: unspecified
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: okular-devel@kde.org
ReportedBy: [EMAIL PROTECTED]


Version:(using KDE 4.1.2)
Installed from:Unspecified

I really appreciate thumbnail filtering by keyword and use it everyday. Many
times I want to see the location of a word on the current page, or in the
following ones. However, each time the thumbnail list is filtered, the
thumbnail scrollbar is reset to the top. 

I think it would be very useful if the thumbnail list would automatically
scroll to the current page (or to the closest shown thumbnail), so that one
would not need to look at the current page number, and then each time browse
through the thumbnails looking for a match. When browsing 1650-page PDFs that's
quite handy! :-)

Thanks a lot and keep up the amazing work: Okular rules also on Windows
already!


-- 
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 148527] I want more zoom with okular

[Luca Burelli]

http://bugs.kde.org/show_bug.cgi?id=148527


Luca Burelli burellil dei unipd it changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #1 from Luca Burelli burellil dei unipd it  2008-11-13 15:17:36 
---
*** This bug has been confirmed by popular vote. ***


-- 
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