Bug 131817 - can't kill nabi
Summary: can't kill nabi
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nabi
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lawrence Lim
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-09-05 08:27 UTC by Colin Charles
Modified: 2014-03-26 00:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-17 21:03:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Colin Charles 2004-09-05 08:27:12 UTC
Description of problem: nabi refuses to die or quite, which gets
mighty annoying


Version-Release number of selected component (if applicable):
nabi-0.13-1

How reproducible:
100%

Steps to Reproduce:
1. start Nabi (either from console or menu)
2. If started from console, hit Ctrl+C to terminate the process
  
Actual results:
It restarts/respawns back instantly

Expected results:
It gets shut off.

Additional info:
I can reproduce this on PPC, and this comes mainly from a complaint (I
presume on x86) from Paul on fedora-test-list

Comment 1 Paul F. Johnson 2004-09-05 09:33:46 UTC
x86 version has the same problem

Comment 2 Leon Ho 2004-10-22 04:38:33 UTC
This is the reply from upstream:
"Anyway, you should use session manager to stop nabi if you run your
desktop with session manager. So selecting quit menu of nabi does not
work. This is intentional behavior.
If some problem accurrs and XIM is dead unexpectedly, XIM should
be respawned, I think.
Some implementation has watch dog process for it, but it is too
expensive for
such a small xim program. So I deside to use session manager. Using
session mananger is quite easy, I think."

Comment 3 Leon Ho 2005-01-17 21:03:16 UTC
NetworkManager has similar feature. 
You can disable this through gnome-session-properties tho.

Closing this out unless there are other concerns on this issue.


Note You need to log in before you can comment on or make changes to this bug.