https://bugs.kde.org/show_bug.cgi?id=399473
RJVB <rjvber...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NOT A BUG |---
Ever confirmed|0 |1
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Reopening because the fact a normal exit happens in response to a SIGHUP under
a local session is apparently a coincidence. Citing the Qt "interest" ML:
>> > Exiting with exit() is not expected to work with Qt. Normal exit must
>> > return from main(), so you should simply ask the QCoreApplication main
>> > event loop to exit (quit() slot).
>>
>> A KDE dev told me a SIGHUP should already work (contrary to my experience).
>> So I tried it on a complex app running locally and it turns out that it
>> indeed went through its regular shut-down cycle. Including unsaved file
>> alerts.
>
> That might be a KF5 add-on. Qt doesn't do that by itself.
I have yet to find any evidence that anything in KDevelop's dependencies
installs a SIGHUP handler that does anything other than the default handler.
Either way, let me reiterate that my feature suggestion concerns a proper,
non-interactive exit. It should probably just close a number of resources that
would otherwise be marked dirty, and then call _exit() to avoid activating any
dtors that might make blocking calls to the X server.
--
You are receiving this mail because:
You are watching all bug changes.
