Bug 406728

Summary:	Shutdown inhibited when multiple tabs are opened
Product:	[Applications] okular	Reporter:	Øystein Steffensen-Alværvik <epost.kde>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	1.7.0
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Øystein Steffensen-Alværvik 2019-04-21 12:08:11 UTC

SUMMARY
Not possible to shutdown the system from Plasma's shutdown dialog (launched from Kickoff/Kicker) when Okular has tabs opened.

STEPS TO REPRODUCE
1. Use Okular's tab feature. Settings → Check 'Open new files in tabs'
2. Open two documents
3. With Okular running with the tabs opened, attempt to shutdown or logout using Kicker or Kickoff.

OBSERVED RESULT
Okular displays a dialog asking whether you really want to close Okular. If you choose 'Cancel', a pop-up dialog informs you that logout was prevented by '/usr/bin/okular'. 

EXPECTED RESULT
It should be possible to shutdown the system with Okular running, even when tabs are opened (this is possible when using Okular with multiple *windows* opened). This is useful in combination with Plasma's session restore feature, allowing you to return to work quickly.

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Kernel Version: 5.0.0-13-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz
Memory: 11,6 GiB

Comment 1 Nate Graham 2019-04-23 15:49:47 UTC

Doesn't the dialog have a "Don't show this again" checkbox? If so, you can check than and then in the future shutdown win't be inhibited when there are multiple tabs open.

Comment 2 Øystein Steffensen-Alværvik 2019-04-23 17:31:56 UTC

(In reply to Nate Graham from comment #1)
> Doesn't the dialog have a "Don't show this again" checkbox? If so, you can
> check than and then in the future shutdown win't be inhibited when there are
> multiple tabs open.

You are right, that fixes it. I supposed I assumed that it wouldn't. Then this must be intended behaviour; marking it as such.