Summary: | Plasma desktop crash after pkilling -9 NetworkManager | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | Jaak Ristioja <jaak> |
Component: | general | Assignee: | Lamarque V. Souza <lamarque> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 0.9 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jaak Ristioja
2013-01-04 20:24:49 UTC
When you kill NetworkManager using -9 parameter you do not give NetworkManager time to signal other programs that it is quiting. That is not the normal way of closing NetworkManager, so we do not need to support that. NetworkManager might also crash which would result in the same behaviour (crash of Plasma desktop). I and many others consider it bad quality if software doesn't handle such cases properly. Either way, THIS IS STILL A BUG unless you can prove that 1) NetworkManager will never crash, or 2) if it would, Plasma wouldn't crash, or 3) Plasma handles cases where NetworkManager terminates with SIGSEGV, SIGABRT or similar, but not SIGKILL and the like, and 4) none of the items above will be a problem in the future. "We don't support cases where processes we communicate with crash." is not an excuse! Good programmers DO CONSIDER such cases. I suggest You be one of them! But of course, who am I to force KDE devs to write quality software... :-( *** This bug has been marked as a duplicate of bug 314200 *** |