Bug 415012 - okularkirigami with Qt 5.9.8
Summary: okularkirigami with Qt 5.9.8
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-10 11:18 UTC by RJVB
Modified: 2020-02-27 15:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
backtrace (12.89 KB, text/plain)
2019-12-10 11:18 UTC, RJVB
Details
patch to make things work (5.62 KB, text/plain)
2019-12-10 11:18 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2019-12-10 11:18:08 UTC
Created attachment 124422 [details]
backtrace

SUMMARY
Okular claims it supports Qt 5.9 yet okularkirigami seems to require at least Qt 5.10 . After addressing this I observed the attached crash.

This is with the git/master head.

STEPS TO REPRODUCE
1. Apply the QML patches from the attached patch file
2. rebuild and run okularkirigami
3. click the unlabeled lower-right control to open the page selector
4. click it again

OBSERVED RESULT
Crash

EXPECTED RESULT
I suppose the page selector should close again.

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.60.0
Qt Version: 5.9.8

ADDITIONAL INFORMATION
The PageItem::paint() method may never be called with a null window() when using a newer Qt version but given that other member functions check the property it may be wise to do so here. Idem for the change to DocumentPrivate::requestDone() (though one may wonder why a null observer would be held in m_observers).
Comment 1 RJVB 2019-12-10 11:18:42 UTC
Created attachment 124423 [details]
patch to make things work
Comment 2 Albert Astals Cid 2019-12-10 22:09:39 UTC
René, you know you don't send patches in bugzilla.
Comment 3 RJVB 2019-12-10 23:08:37 UTC
So sue me ... or remove the possibility to attach them.
Comment 4 Nate Graham 2019-12-13 14:30:26 UTC
We did, by explicitly removing the text that recommends submitting patches in the attachments view, and we replaced it with text saying:

> KDE uses Phabricator for patch submissions. Please read our instructions on
> how to submit a patch through Phabricator. Bugzilla is not monitored for
> patches, so your patch is likely to be missed."

Maybe you missed that?

Either way, please submit using Phabricator.
Comment 5 RJVB 2019-12-13 17:28:27 UTC
No, neither did I miss the fact there are no guarantees.

This is an issue tracker, used among others for reporting what could be bugs that need triaging. I consider it a courtesy to attach a patch if I have one, for something that's not important enough to me to request a patch review process (or because I don't want to allocate the time necessary to do the project devs' work for them the way they want it to be done).

Feel free to ignore the patch, feel free even to ignore the whole ticket, I'm planning to cut the pointless gadget out of my okular packaging anyway.
Comment 6 Oliver Sander 2019-12-16 16:01:53 UTC
Guys, don't fight.  The patch is now at https://invent.kde.org/kde/okular/merge_requests/80.