It's not possible to login through GUI when disk is full

Bug #47145 reported by Martin Olsson
10
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Currently when I try to login (through the X GUI normal ubuntu login screen) I get a message saying some auth file can't be written and then I'm returned to the login prompt. My / partition is full and I know this, but how can I login to fix it if ubuntu refuses me to login? This is "moment 22" kind of.

(as it turns out I could CTRL-ALT-Fx my way into a CLI mode terminal and delete some files but most users cannot do this and really, this is not something that we can expect from the average ubuntu user).

Last year, I ran into this exact problem on my schools Redhat systems too... all in all, this is one of those bugs that people run into every now and then and it generally causes a lot of problems for people. And it would be pretty easy to fix it...

Revision history for this message
towsonu2003 (towsonu2003) wrote :

may be a message in that error report mentioning ctrl+alt+f1 and cleaning up some files to be able to log in again?

Revision history for this message
Martin Olsson (mnemo) wrote :

Yea that would be nice as a short-term workaround. As a proper solution however, I would suggest:

1. Rewriting the GUI login process so that it does not write any additional data to the disk.

 OR

2. Making sure that the relevant files are stored separately; so that regardless of how many mp3s the user downloads or regardless of how big /var/log messages and other log files grow they will never interfer with system functionality.

Generally, I would prefer the second solution because I bet that there is a ton of other important programs that will crash and/or fail abruptly with zero bytes free. The login process if of course one of the most important programs... since most users can't use their computer at all when they can't login.

Revision history for this message
Alexandros Papadopoulos (apapadop) wrote :

Same problem with kubuntu 6.06 trying to login through KDM. Even worse, the user gets NO warning whatsoever - the KDM login screen just pops up again, with no indication of what went wrong.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

bumping importance to high

Revision history for this message
Paul Dufresne (paulduf) wrote :

I have removed duplicate on the general case of bug 22842, because I believe this programs (GDM, KDM) need special measure not touched by https://wiki.ubuntu.com/HandleNicelyLowDiskSpace?action=show
specification that I just began to wrote.

In fact I intend to separate kdm issue in it's own bug, as they are in fact two different problems, with both gdm and kdm needing to be patched.

Revision history for this message
Paul Dufresne (paulduf) wrote :

Making it as affecting gdm (will fill a separate bug for kdm) rather than Ubuntu.

Revision history for this message
Paul Dufresne (paulduf) wrote :

bug 62638 is related, but sufficiently different to not be considered a duplicate.

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Why shouldn't bug 62638 be duped to bug 35217 ?

Revision history for this message
Vincenzo Ciancia (vincenzo-ml) wrote :

I think that #62638 is about /home being full, while #35217 is about / being full - probably these should be tackled separately.

Revision history for this message
toddq (toddq) wrote :

This is not a duplicate. Rather 35217 does not seem to understand the problem where here it is understood. Perhaps, 35217 should be considered a duplicate of this thread. Clearly, this is an important problem that should be assigned to someone but it won't be with the attitude displayed on 25217. I would note that this issue occurs on Karmic most recent version. If you have encrypted files, then I do not believe there is a way to recover them but I am new and could be wrong about that. In 35217, the issue seems is also different because the proposed solution involves having the ability to login at the prompt which certainly isn't the case with this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.