| Summary: | Improper Highlighting | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | Looserof7 <looserof7> | 
| Component: | PDF backend | Assignee: | Okular developers <okular-devel> | 
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | aacid | 
| Priority: | NOR | Keywords: | triaged | 
| Version First Reported In: | 0.25.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Related Highlighting. Second Screenshot Third Screenshot Fourth ScreenShot fith ScreenShot | ||
| 
        
          Description
        
        
          Looserof7
        
        
        
        
          2016-08-09 00:06:58 UTC
        
       Created attachment 100501 [details]
Related Highlighting.Created attachment 100502 [details]
Second ScreenshotCreated attachment 100503 [details]
Third ScreenshotCreated attachment 100504 [details]
Fourth ScreenShotCreated attachment 100505 [details]
fith ScreenShotWhat is wrong in third and fourth screenshot? Sorry for the delay!, as I'm far away from internet, I was unable to reply. There was no problem with this and fourth screen shots, but I mean they were different. I did find a work around, with this command, where I was able to even do highlighting properly, without any loss of data. Command is:'qpdf input filename outputfilename'. I was able to open the same book in which I lost the data, without any problems, I don't known anything about qpdf, it just worked. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |