https://bugs.kde.org/show_bug.cgi?id=425188
Nate Graham changed:
What|Removed |Added
CC||rostislav.matveev@googlemai
|
https://bugs.kde.org/show_bug.cgi?id=425188
David Hurka changed:
What|Removed |Added
Version Fixed In||20.12
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=425188
Bug Janitor Service changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #14 from Bug Janitor
https://bugs.kde.org/show_bug.cgi?id=425188
David Hurka changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #12 from David ---
This makes a lot of sense. I suppose I can test the observation by swapping my
monitors around which will mean that (0, 0) is visible. I would be waiting for
OpenSuse to push the latest Qt out.
I'm wondering if this is al
https://bugs.kde.org/show_bug.cgi?id=425188
David Hurka changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=425188
David Hurka changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #9 from Albert Astals Cid ---
(In reply to David Hurka from comment #8)
> Another idea: Can this be an issue of broken ABI? Like when Qt Widgets was
> compiled against a different minor release of Qt Gui than our users are
> using, and Qt Gu
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #8 from David Hurka ---
Another idea: Can this be an issue of broken ABI? Like when Qt Widgets was
compiled against a different minor release of Qt Gui than our users are using,
and Qt Gui broke their ABI in this minor release. So that somet
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #7 from David Hurka ---
@anyone who can still reproduce this bug:
I created a small test application using Qt’s test framework in
https://invent.kde.org/davidhurka/qscrollertest . If you are able to run this
test on your setup and tell us t
https://bugs.kde.org/show_bug.cgi?id=425188
Nate Graham changed:
What|Removed |Added
CC||dav7...@yahoo.co.uk
--- Comment #6 from Nate Grah
https://bugs.kde.org/show_bug.cgi?id=425188
Albert Astals Cid changed:
What|Removed |Added
CC||kct...@juno.com
--- Comment #5 from Albert
https://bugs.kde.org/show_bug.cgi?id=425188
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
--- Comment #4 from Albert As
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #3 from David Hurka ---
Now my theory is that it will crash when you enable tabs and open a file from
File -> Open. Right? (Settings -> Configure Okular -> General -> Open new files
in tabs)
QScroller appears to access screen() of PageView
https://bugs.kde.org/show_bug.cgi?id=425188
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #2 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=425188
Corrado Mella changed:
What|Removed |Added
Summary|Okular crashes opening PDFs |Okular crashes opening PDFs
|
16 matches
Mail list logo