After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 2006 - Three things to be fixed
Three things to be fixed
Status: RESOLVED FIXED
Product: gnome-core
Classification: Deprecated
Component: general
1.4.x
Other other
: Normal normal
: 1.4.1
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 1999-08-26 10:25 UTC by topiolli
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
My .gnome/session file that has the sawfish CurrentDirectory mis-set (5.23 KB, text/plain)
2001-07-13 08:09 UTC, toomim
Details

Description topiolli 2001-01-27 19:58:41 UTC
I don't know which package might cause the following, but anyway:

Most of the time I start gnome (gnome-session) it hangs after showing
the gnome logo in a window with no frames on a gray background grid.
After the window disappears I have to kill the X server and try again.
Nothing seems to help. I usually need to try at least three times before
I get it run. And, as you may guess, this is very annoying. When it
eventually starts it first shows the same window with no frames and then
adds the frames as the window manager (I'm using Enlightenment) starts.

Second thing (not that bad) is that the gnome terminal always starts at
~/.gnome-desktop/. I'd like it to start at ~/ and I couldn't find any
guidelines from the documentation on how to do thiss.

And the third one: when I open the desktop popup with right-click,
release the button and select new->terminal with left-click from the
newly opened submenu, I have to click twice before the terminal actually
opens. This bug occurs only the first time and opening a second terminal
works fine.

I'm using the standard RH 6.0 distribution.
-Topi-
<< http://ee.oulu.fi/~topiolli >>




------- Additional Comments From sopwith@redhat.com 1999-09-03 11:49:58 ----

Subject: More info needed
From: Elliot Lee <sopwith@redhat.com>
To: 2006@bugs.gnome.org
Message-Id: <Pine.LNX.4.10.9909031146070.17959-100000@lacrosse.corp.redhat.com>
Date: Fri, 3 Sep 1999 11:49:58 -0400 (EDT)

I don't have any ideas on how to reproduce this problem. Do you have
something like a strange hostname/DNS setup that would cause hangs?

-- Elliot
The time for action is past! Now is the time for senseless bickering!




------- Additional Comments From sopwith@redhat.com 1999-09-13 19:26:22 ----

Subject: No reply?
From: Elliot Lee <sopwith@redhat.com>
To: 2006@bugs.gnome.org
Message-Id: <Pine.LNX.4.10.9909131925580.20364-100000@lacrosse.corp.redhat.com>
Date: Mon, 13 Sep 1999 19:26:22 -0400 (EDT)

I'd love to get to work on fixing this bug, but I need more information
from you. Please reply.

-- Elliot
$400 million in gold bullion Ft. Bragg Peking Soviet cryptographic KGB
Ft. Meade plutonium genetic SDI explosion fissionable DES Waco, Texas
PLO




------- Additional Comments From ??? 1999-10-30 14:11:24 ----

Subject: More information
From: ??? ??? <???>
To: 2006@bugs.gnome.org
Message-Id: <19991030.18112400@mis.configured.host>
Date: Sat, 30 Oct 1999 18:11:24 GMT

I am not the person who originally reported this bug, but I'm also 
experiencing one of the problems (about starting gnome). I'm using 
Redhat 6 with Enlightenment as Gnome's Window Manager. My kernel 
version is 2.2.5-15.

When I first log in, the X server immediately dies and I am brought 
back to the login screen.
The second time, and often the third, the splash screen (saying rhad 
labs, etc) comes up, but with no title bar or border. It stays for 
30-60 seconds, and then finally the progress indicator shows up. The 
desktop also takes a long time to load, but once it has, everything 
works fine, except that the logout button/menu item doesn't work. I 
have to kill the X server to get out.
If I kill the X server before it has finished loading and try logging 
in again, it usually works (displays progress indicator, then splash 
screen with title bar and border, and then loads the desktop).

One additional thing: I recently recompiled my kernel, and it started 
working fine after that, for a while. Unfortunaltely, now the problem 
has come back.




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 14:58 -------
This bug was previously known as bug 2006 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=2006
Originally filed under the gnome-core product and general component.

The original reporter (topiolli@ees2.oulu.fi) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-core-maint@bugzilla.gnome.org.

Comment 1 Telsa Gwynne 2001-05-08 12:31:59 UTC
Just for information of anyone reading, the "gnome-terminal starts
in directory ~/foo" problem generally seems to mean "I started gnome
with startx whilst I was in directory ~/foo".

This is a really old bug report though. If either of the reporters
can confirm it happens with gnome 1.2 or gnome 1.4 that would help.
Comment 2 toomim 2001-07-13 08:09:47 UTC
Created attachment 738 [details]
My .gnome/session file that has the sawfish CurrentDirectory mis-set
Comment 3 toomim 2001-07-13 08:11:38 UTC
I can confirm this bug.



I'm using a version 1.4.0.4-4 debian gnome-session package, and have
experienced the bug many times before in other versions of gnome and
other linux distros.



The problem occurs when one runs startx from a directory other than
their home. Sawfish then has that directory set as its
CurrentDirectory, and the user's .gnome/session file gets an entry
like this:



8,CurrentDirectory=/mnt/hog/Sound/Music/Unsorted/



In their sawfish section.



For some reason, this will never leave their session file, no matter
what directory they run startx from after running it from
"/mnt/hog/Sound/Music/Unsorted".



I have to go. I hope this gets fixed, it's very annoying. I'm
attaching my .gnome/session.
Comment 4 Kjartan Maraas 2001-09-15 06:58:57 UTC
What version of sawfish is this? Has it been fixed in a later release
of sawfish?
Comment 5 Kjartan Maraas 2002-06-11 10:27:13 UTC
Closing this from lack of feedback. I also can't remember having seen
reports of gnome-session hanging on login for a long time, so I'm
assuming that's been fixed. Please report bugs against the latest
stable release.