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 72541 - Out of disk space handling
Out of disk space handling
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
Trevor Curtis
: 135835 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-02-25 17:47 UTC by Havoc Pennington
Modified: 2005-02-08 21:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Havoc Pennington 2002-02-25 17:47:26 UTC 
Forwarding a RH bug you've seen before:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=54452
Comment 1 Luis Villa 2002-02-26 22:15:31 UTC 
George: could you remove the GNOME2 keyword if this is in fact fixed
in G2?
[disk space]
Comment 2 Ryan Murray 2002-03-26 07:49:26 UTC 
There's a series of similar problems that have been reported to the
Debian BTS, specifically http://bugs.debian.org/114469
GDM should probably detect that a session lasted less than a short
timeout (similar to how it detects if X starts and is useful), as well
as check for low disk space before allowing the user to login. 
(minimum freespace as an option, perhaps?), as this could be very
confusing to a user with a quota that doesn't have enough space to
create the Xauthority file, or write config information to the .gnome
dir, etc...
Comment 3 George Lebl 2002-05-21 17:53:53 UTC 
This is not completely fixed, though the original problem should be
fixed.  There still needs to be a lot of work on handling out of disk
space sanely and user friendly.  However it should no longer be
critical as the really bad problems don't exist anymore
Comment 4 Trevor Curtis 2002-07-18 02:45:59 UTC 
George,

What is the status on this then? Has the above been fixed sufficiently
to close this bug, or is there still more work to be done?

TC
Comment 5 Elijah Newren 2002-10-30 00:11:37 UTC 
George,

It's been a while.  What's the status on this bug?  Should it be
closed/reopened/ignored?
Comment 6 Kjartan Maraas 2003-10-29 11:34:32 UTC 
George, do you have an update on this situation?
Comment 7 Kjartan Maraas 2004-09-01 22:50:44 UTC 
Reopening this based on George's last comment. Please close it out if it has
been fixed since.
Comment 8 Brian Cameron 2005-02-03 21:47:08 UTC 
*** Bug 135835 has been marked as a duplicate of this bug. ***
Comment 9 Brian Cameron 2005-02-08 21:31:55 UTC 
After talking to George, I'm closing this bug.  This bug is being kept open
because George wasn't sure his fixes would solve the problem completely, but
nobody has complained in several years.  If there are any problems in this area,
new bugs explaining the situation can be opened.