Hello everyone,
> Basically, annotation color is set as a common attribute to all annotation
>> types at the end of the file and if we should bypass it with an if
>> condition that will set annotation color for type "typewriter" hardcoded
>> to
>> QColor(255,255,255,0).
>> I have tried harcoding
https://bugs.kde.org/show_bug.cgi?id=394556
Bug ID: 394556
Summary: Okular Segmentation Fault after starting application
after resuming from hibernation
Product: okular
Version: 1.4.1
Platform: openSUSE RPMs
chinmoyr abandoned this revision.
REPOSITORY
R223 Okular
REVISION DETAIL
https://phabricator.kde.org/D11725
To: chinmoyr, #okular
Cc: okular-devel, aacid, sander, ngraham
https://bugs.kde.org/show_bug.cgi?id=377688
--- Comment #19 from Michael Weghorn ---
This sounds a bit similar to bug 385456. Is there any useful output when
starting Okular from the command line?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=377688
--- Comment #20 from Ian Newton ---
There may be something here in the output from the command line. Once the print
preview is requested we get:
Settings::instance called after the first use - ignoring
invalidfont -10
invalidfont -10
org.kde.okular.gen
El diumenge, 20 de maig de 2018, a les 11:52:04 CEST, Dileep Sankhla va
escriure:
> Hi Albert,
>
>
> On Sun, May 20, 2018 at 3:02 PM, Albert Astals Cid wrote:
> > El divendres, 18 de maig de 2018, a les 17:04:09 CEST, Dileep Sankhla va
> >
> > escriure:
> > > Hello everyone,
> > >
> > > I'm
https://bugs.kde.org/show_bug.cgi?id=394540
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Resolution|---
Hello Albert,
> Are you speaking of not having that for the new tool or removing it
> altogether?
I'm just suggesting to not have the hover icon for the new typewriter tool.
We should not remove it for the inline note. What do you finally suggest?
Thanks and Regards,
Dileep
