Shut down error, restarts to useless black screen

Bug #76246 reported by llirium
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Release: Edgy Eft, Ubuntu

After I tried to change the folder permissions of my Home folder in Nautilus, I haven't been able to do a proper shut down or restart without using the manual switches on my PC. Nautilus became unresponsive, so I was forced to restart the PC.

It didn't restart with GRUB nor begin Ubuntu startup proper, just hung at a black screen until I manually pressed Reset.

**As well, now whenever I log in, this error dialog box appears:

"User's $HOME/.dmrc is being ignored. This provents the default session and language from being saved. File should be owned by user and have 644 permissions. User's $HOME directory must be owned by user and not writable by other users."

**And when I use the 'sudo' command in the terminal, it starts the command, but not without this error message:

"libgnomevfs-WARNING **: Failed to open session DBUS connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Volume monitoring will not work."

On top of this, sometimes programs will just crash to the desktop for no reason.

Thanks for reading and I'm sorry for this report being so long.

Revision history for this message
Ryan Maki (ryan.maki) wrote :

Hello llirium,

Thank you for taking the time to report this bug and helping to make Ubuntu better.

These issues sound like common side effects of bad permissions. I suspect that when you restarted your system your permissions were left in an unstable state.

You reported this bug a while ago and there hasn't been any activity in it recently. Is this still an issue for you? Thanks in advance.

Revision history for this message
llirium (llirium) wrote : Belated Update

I'm up to Feisty as of now and to be honest, it's been so long that I don't remember exactly what caused the problem. But, yes, I was a noob and repermissioned some things unwisely, IIRC.

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.