gnome power manager prevented gdm login

confirmed, reproducible

Same here...

After fresh UNR 9.10 install and using it 2 weeks, I can't login, same problem as described in this bug and here in forum:
http://ubuntuforums.org/showthread.php?t=1355880

I switched to console with Ctrl+Alt+F1, did update and upgrade, tried to install and use LXDE, Kdm, instead of Gnome and Gdm, nothing worked.

Looking to Xorg logs, found EE, saying that i845 module is not loaded, falling back to vesa. I tried to load that moduel manually with modprobe, but that didn't helped too.

Problem happened with Asus EeePC 701.

In my case problem was related with full disk. Because Asus Eee 701 has only 4GB, I created only on partition for root directory.

When I logged to console with Ctrl+Alt+F1, checked disk usage:
 $ df -h

And it showed, that there is no space left.

When I deleted some files, I could again log in.

Mantas:

This makes sense -- the machine that this occurred on was low on memory -- down to a few K ( if that )

I think we have a solid resolution

That being said, I have a hard time closing this bug. I think that GNOME Power Manager should handle this gracefully.

Anyway, user should be able to login and see notification about low space. Because now average user just can't use his computer... :/

I wonder if I'm having the same issue with Lucid. When the computer sleeps, if I restore the computer the login window pops up. If I attempt to login, it get's stuck at processing and I have to forcibly shutdown the system so I can use it.

Mantas Zimnickas solution did not work for me. As noted the bug states that one cannot login at all. For one thing, I cannot login at the command prompt. However, I do have a full disk. I have an Asus Eee 701 as well. I do believe that the problem relates to a full disk.

toddq, if you even can't login at the command prompt, then it is other solution, to boot your netbook from a USB flash drive and then free some spece to be able to login.

Dear Mantas, I tried your solution. I deleted 4GB of space and tried to reboot. That didn't solve the problem. I should mention that my drive is encrypted so some parts I cannot delete.

toddq, if you can't login with GDM, your home directory should have enough free space, also, probably /tmp directory. If you logging in at the command prompt, then only /tmp should have enough free space, I guess...

if you could post a log of the output of the command `df -h`

from the Live CD it says its still full.

Filesystem Size Used Avail Use% Mounted on
/dev/sda5 187G 183G 0 100% /media/disk

However, I removed some software with sudo apt-get remove and deleted some mysql backup files because it said that directory was full in the message logs so the size and actual are different but I see that the available is still 0.

Is some of it stuck in a .Trash folder? Try removing it by hand with the `rm` command, and check out what's using up so much memory with `du`

The original description of this bug report is far too vague to understand what is going on here (gnome-power-manager won't prevent you from logging in even if it was crashing. If gnome-power-manager was crashing, there is no stack trace to debug that anyway).

The last few comments about low disk space have nothing to do with gnome-power-manager anyway

Chris Axelrod - do you still get the issue you originally reported?

Paul Tagliamonte that might work but Ubuntu now has encrypted drives and most . (including .trash) are now encrypted so you can no longer delete the files in your .trash file if you use encryption which is all the more reason why this is an important bug.

@Chris Coulson: I fixed Chris' issue by cleaning his drive. gnome-power-manager was crashing because it had no place to store temporary data, because he had less then a K left.

This issue is reproducible and still very important to fix. At least crash without crashing gdm.

@Toddq: I did not know that, and I agree with you 100%.

Right, but gnome-power-manager has absolutely nothing to do with you not being able to log in to GDM when your disk is full. This bug is against gnome-power-manager, although I'm unconvinced that even the original reporters issue has anything to do with gnome-power-manager. You should open a new bug rather than hijacking other peoples bugs when it isn't clear that you have the same issue, otherwise it just becomes a mess and incredibly difficult for anyone working on it to extract useful information from.

As noted in my own bug report, which probably is some sort of duplicate
but I can't figure out where, I am getting a warning that it is an power management installation problem. If this warning is inaccurate, then I believe then some natural cross-referencing of these two ideas is
appropriate.

Please tell me if I'm wrong but I see a common thread among a lot of bugs and I believe I see a solution to many of them. I believe I've figured out a four part solution to this problem which has been going on since 2006. It's understandable that it has not been addressed because it is not a typical problem. The history itself (which is given below) reveals the solution. Actually, the history I give below is incomplete. The more I research this problem, the more threads I find that relate to this issue (e.g., https://answers.launchpad.net/ubuntu/+question/21286).

Part I https://bugzilla.gnome.org/show_bug.cgi?id=144473 has a partial fix for gdm which has not been assigned to anyone because the bug is delegated to linux. It should be redelegated back to gdm.

Part II The next part of the fix is that the ubuntu warning that your disk space is low is too weak. It should state that if you don't fix the problem before rebooting, you will lose everything. There should be additional warnings about the problem placed in ubuntu documentation.

Part III, ubuntu should abandon encryption until a method is found that allows you to recover a encrypted drive when you have a full-disk. At this point, it is my view that an encrypted drive is just do dangerous because you can lose everything if you have full disk. My proposed solutions of course would make some people unhappy but I believe they are more appropriate than what has been going on since 2006, which is basically to endlessly put off solutions to the problem but I'm certainly not trying to tell you how to do your job. I'm sure that you can come up with better ideas that I can. It's just my perception of the problem.

Part IV So my final proposed solution has to do with the tracker team. I'm sure we all appreciate the terrific job the tracker teams do in identifying and addressing problem. So why wasn't the problem solved in 2006? It appears the nature of problem and solution has befuddled the tracker team. The problem was difficult to recognize because a typical debug report is not possible because the user can't login. My proposed solution is to suggest that when a problem has been around for over a year that it is assigned to someone who goal is to identify similar problems in forums and other bug reports. If there is a pattern of a lot of similar bugs and/or questions not being dealt with and no one seems to have a constructive solutions, I would suggest that one person be assigned to come up with a workable solution to the more general problem. This approach would actually save time because instead of endlessly putting out small fires, you would identify an
 important underlying issue that is contributing to user dissatisfaction. It was quite striking to me when reading all this material, to see so many comments by experienced and highly competent progammers trivialize this issue...

I whole-hardly agree with you so I've done some research to try and find a common thread in what definitely has become a monumental number of bugs, forum posts etc. ... that probably relate to the same underlying problem and please believe me when I say that I appreciate how difficult it is for you Chris to take this on and we don't want to make your difficult job any more difficult that it already is. I hope the history if not my novice suggestions are helpful.

As noted in my own bug report, which probably is some sort of duplicate but I can't figure out where, I am getting a warning that it is an power management installation problem. If this warning is inaccurate, then I believe then some natural cross-referencing of these two ideas is appropriate.

Please tell me if I'm wrong but I see a common thread among a lot of bugs and I believe I see a solution to many of them. I believe I've figured out a four part solution to this problem which has been going on since 2006. It's understandable that it has not been addressed because it is not a typical problem. The history itself (which is given below) reveals the solution. Actually, the history I give below is incomplete. The more I research this problem, the more threads I find that relate to this issue (e.g., https://answers.launchpad.net/ubuntu/+question/21286).

Part I https://bugzilla.gnome.org/show_bug.cgi?id=144473 has a partial fix for gdm which has not been assigned to anyone because the bug is delegated to linux. It should be redelegated back to gdm.

Part II The next part of the fix is that the ubuntu warning that your disk space is low is too weak. It should state that if you don't fix the problem before rebooting, you will lose everything. There should be additional warnings about the problem placed in ubuntu documentation.

Part III, ubuntu should abandon encryption until a method is found that allows you to recover a encrypted drive when you have a full-disk. At this point, it is my view that an encrypted drive is just do dangerous because you can lose everything if you have full disk. My proposed solutions of course would make some people unhappy but I believe they are more appropriate than what has been going on since 2006, which is basically to endlessly put off solutions to the problem but I'm certainly not trying to tell you how to do your job. I'm sure that you can come up with better ideas that I can. It's just my perception of the problem.

Part IV So my final proposed solution has to do with the tracker team. I'm sure we all appreciate the terrific job the tracker teams do in identifying and addressing problem. So why wasn't the problem solved in 2006? It appears the nature of problem and solution has befuddled the tracker team. The problem was difficult to recognize because a typical debug report is not possible because the user can't login. My proposed solution is to suggest that when a problem has been around for over a year that it is assigned to someone who goal is to identify similar problems in forums and other bug reports. If there is a pattern of a lot of similar bugs and/or questions not being dealt with and no one seems to have a constructiv...

In my case problem was related with full disk.
When I logged to console with Ctrl+Alt+F1, checked disk usage:
 $ df -h

And it showed, that there is no space left.

When I deleted some files, I could again log in.

Thanks (Mantas Zimnickas)