Re: FVWM: Re: Please HELP, fvwm taking a looooong time to start up

From: Michael Lindner <michael.lindner_at_ascend.com>
Date: Mon, 17 Aug 1998 10:21:17 -0400

At 11:15 AM 8/10/98 -0400, Brad Giaccio wrote:
>
>Tell me exactlly how you are starting fvwm and what files you have edited
>and I'll see if I can help

OK, this may not even be an FVWM problem, but thanks in advance for any
help you can give me. I have tried starting fvwm 3 different ways:

1. I edited my .Xdefaults file and added

        *wmStartupCommand: /usr/openwin/bin/fvwm2
        *waitWmTimeout: 1

    and started a CDE session.

2. I set and exported OW_WINDOW_MANAGER=/usr/openwin/bin/fvwm2 in my .profile
    and started an OpenLook session.

3. I followed the advice of a post in the archives and set up an FVWM
session from the
    login screen.

ALL of these methods starts up fvwm2, but all of them suffer from the same
problem. I have since learned that even a "straight" CDE session, using
dtwm, or a "straight" OpenLook session using olwm suffers from this problem
- after the window manager starts, it sits there for EXACTLY 10 minutes,
then starts the home or current session (i.e. starts up apps).

During the 10 minutes, the cursor is an hourglass, and the WM is
unresponsive. What's even worse is that this problem only affects me.
Other users using the machine, even with the identical environment and
$HOME/.* files don't see the 10 minute delay. I tried removing my $HOME
and making an empty one, thinking I had some wierd file in there, but it
still takes 10 minutes.

I tried doing a "ps" during the 10 minute hang and after, and they are
identical - no processes are started or finished (except, of course, for my
session apps), and no CPU is used during the 10 minutes.

Since there are no man pages available to me on any of the "dt" commands, I
tried copying all the startup files and adding "set -x" to them. I though
the command "ttsession" was the culprit, but I'm not so sure.

Has anyone seen this behavior, or have a clue where there's a 10 minute
time out in the Solaris startup cr*p?

Since I'm seeing this with dtwm and olwm, I'm assuming this is NOT an FVWM
problem, so I will not trouble this list further with this issue, and thank
you for your indulgence in ranging off-topic.

---
Michael Lindner
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Aug 17 1998 - 09:25:46 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:01 BST