Bug 19449 - Netscape wrapper confuses WindowMaker
Summary: Netscape wrapper confuses WindowMaker
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: WindowMaker
Version: 7.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Crutcher Dunnavant
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2000-10-20 07:39 UTC by dh_redhat
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2001-04-12 21:34:19 UTC

Attachments (Terms of Use)

Description dh_redhat 2000-10-20 07:39:11 UTC
If I invoke Netscape as /usr/bin/netscape (which is a sh wrapper 
around /usr/lib/netscape-communicator) then I cannot dock the application 
in WindowMaker, it cannot be saved in a WindowMaker session and  I cannot 
set other properties.

If I invoke it directly as /usr/lib/netscape-communicator then everything 
works as expected.

A 'ps' when invoked as /usr/bin/netscape shows two processes:

21654 21559 39 00:39 tty1     00:00:04 /usr/lib/netscape/netscape-commu
21667 21654  0 00:39 tty1     00:00:00 [netscape <defunct>]

I suspect it is related to the <defunct> process. Could it be because when 
the wrapper invokes the real executable it does not 'exec' it?

Comment 1 Bill Nottingham 2000-10-27 22:50:10 UTC
The defunct process is actually either
 A) a dns helper
 b) a previous dead netscape process

It doesn't really have anything to do with the wrapper.

Comment 2 dh_redhat 2000-10-28 20:37:24 UTC
How do you explain then the fact that the <defunct> process shows up *ONLY* 
when starting netscape through the wrapper? I just tried it again, I started 
Netscape directly and actively used it for a while to rule out the DNS process, 
after using it for about 15 min. there is still no <defunct> process. I quit, 
checked ps again, no sign of any running Netscape at all, then started Netscape 
using the wrapper, the <defunct> process showed up right away.

Comment 3 Bill Nottingham 2001-01-19 22:16:52 UTC
Hm, this appears to be a bug in WindowMaker's docking; it's
expecting the PID that it launched to stay running, but since
the shell script actually executes netscape, it's not being watched

Comment 4 Crutcher Dunnavant 2001-04-12 21:34:15 UTC
But the shell script 'exec's netscape. hmm.

Comment 5 Crutcher Dunnavant 2001-06-25 17:33:20 UTC
I dont think that this can be called a bug in WindowMaker.
What possible behaviour could it have than to wait on the process?
Should it wait on the process's children; which one?

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