GNOME Power Manager Login Issue

[TyD]

Hey guys, I recently upgraded to 9.10 (64 bit), and was mostly pleased with it. However, this morning when I tried to log on, I received an error message that said, "Install Problem! The configuration defaults for GNOME Power Manager have not been installed correctly. Please contact your computer administrator." I cannot log on to my computer now, as every time I try, I am sent back to the login screen.

My computer had been working well before this (besides not having sound) so I don't know where this could have come from. Any help would be greatly appreciated. Thanks!

[whitelight1]

Hey guys, I recently upgraded to 9.10 (64 bit), and was mostly pleased with it. However, this morning when I tried to log on, I received an error message that said, "Install Problem! The configuration defaults for GNOME Power Manager have not been installed correctly. Please contact your computer administrator." I cannot log on to my computer now, as every time I try, I am sent back to the login screen.

My computer had been working well before this (besides not having sound) so I don't know where this could have come from. Any help would be greatly appreciated. Thanks!

Same here.
I am using Xubuntu Karmic.
Everything was working properly until yesterday when i installed some updates. After doing so and rebooting i could not start applications which require my password.

So now i can not log in anymore. I can log in as 'root' (i created that account due to SWAT..).

Also, Totem does not play sound anymore. And I can not seek trough some videofiles.
This is very annoying so please if there is any help ...

[whitelight1]

This finally worked for me:

apt-get --reinstall install gnome-power-manager

After loggin in again, some of my Desktop and Panelsettings were gone. I have no idea why.
Totem is now working with sound again.

Programs like Gparted are working again as usual.

But since i have not changed anything on the system besides installing the updates, I am not shure how to 'trust' Ubuntu in the future.

[Ithiel]

This may or may not be your issue. I have had the problem to occur twice and finally found the culprit in MY case. It was simplebackup. In using SimpleBackup to back up my files to an external hard drive, occasionally it fails to mount the drive correctly. In such cases, if not configured correctly it will simply add a back up folder to your home folder and begin backing up there. That can quickly result in using up so much of your free space that your computer cannot boot properly.

Using a live CD, I went in and deleted the erroneous back ups and then everything booted fine. I also went back into SimpleBackUp Config and clicked the Destination tab and marked the Abort backup if destination directory does not exist box. Its all good now.

[pigphish]

I had the same issue with simple backup (simple backup). I couldnt find the confounded files until I did:

sudo find / -name '*' -size +1G

once i removed the backup files i was finally once again able to see available space using df command.

mine where in var/backup of my ubuntu partition. I even had the option selected to fail if destination folder not found. Very frustrating simple backup.

[John RG]

Thankyou. Saved me!

[KPDXHAM]

This may or may not be your issue. I have had the problem to occur twice and finally found the culprit in MY case. It was simplebackup. In using SimpleBackup to back up my files to an external hard drive, occasionally it fails to mount the drive correctly. In such cases, if not configured correctly it will simply add a back up folder to your home folder and begin backing up there. That can quickly result in using up so much of your free space that your computer cannot boot properly.

Using a live CD, I went in and deleted the erroneous back ups and then everything booted fine. I also went back into SimpleBackUp Config and clicked the Destination tab and marked the Abort backup if destination directory does not exist box. Its all good now.

Well now! I've been searching threads and find that someone else has had a problem using Sbackup.

Please look here:
http://ubuntuforums.org/showthread.php?t=1355880

In the mean time, while I wait for someone to help, I'll keep trying to figure out how to access the Karmac Koala via the live Ubuntu 9.10 cd.

Sorry for posting all over the place, but I really would like to be able to fix this system since it was all finely tuned to what I liked and there's files I would rather not loose. Instead of reinstalling again and again (newbie), It would be really great to be able to fix the problem and move on.

============================= Boot Info Summary: ==============================

=> Syslinux is installed in the MBR of /dev/sda
=> Syslinux is installed in the MBR of /dev/sdb
sda1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files/dirs: /boot.ini /ntldr /NTDETECT.COM /wubildr.mbr

sdb1: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows Vista/7
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs: /ubuntu/winboot/wubildr.mbr /ubuntu/disks/root.disk
/ubuntu/disks/swap.disk

sdb1/Wubi: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 9.10
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000001

Partition Boot Start End Size Id System

/dev/sda1 * 63 268,414,019 268,413,957 7 HPFS/NTFS


Drive: sdb ___________________ __________________________________________________ ___

Disk /dev/sdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders, total 320173056 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x4dc6038e

Partition Boot Start End Size Id System

/dev/sdb1 63 320,159,384 320,159,322 7 HPFS/NTFS


blkid -c /dev/null: __________________________________________________ __________

sda1: UUID="1CA81EC9A81EA176" LABEL="Hard Drive" TYPE="ntfs"
sdb1: UUID="25F6416015D78FD1" LABEL="Ubuntu" TYPE="ntfs"
sdb1/Wubi: UUID="2f413912-9705-4610-9eb2-58e809293511" TYPE="ext4"

=============================== "mount" output: ===============================

aufs on / type aufs (rw)
none on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
/dev/sr0 on /cdrom type iso9660 (rw)
/dev/loop0 on /rofs type squashfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)
/dev/sda1 on /media/Hard Drive type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)


================================ sda1/boot.ini: ================================

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Professional" /fastdetect
C:\wubildr.mbr="Ubuntu"

======================== sdb1/Wubi/boot/grub/grub.cfg: ========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
menuentry "Ubuntu, Linux 2.6.31-15-generic" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 2c4c10654c102c58
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-15-generic root=/dev/sdb1 loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.31-15-generic
}
menuentry "Ubuntu, Linux 2.6.31-15-generic (recovery mode)" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 2c4c10654c102c58
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-15-generic root=/dev/sdb1 loop=/ubuntu/disks/root.disk ro single
initrd /boot/initrd.img-2.6.31-15-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 2c4c10654c102c58
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sdb1 loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
insmod ntfs
set root=(hd1,1)
search --no-floppy --fs-uuid --set 2c4c10654c102c58
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sdb1 loop=/ubuntu/disks/root.disk ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows NT/2000/XP (on /dev/sda1)" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 1ca81ec9a81ea176
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

============================= sdb1/Wubi/etc/fstab: =============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/host/ubuntu/disks/root.disk / ext4 loop,errors=remount-ro 0 1
/host/ubuntu/disks/swap.disk none swap loop,sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

================= sdb1/Wubi: Location of files loaded by Grub: =================


.0GB: boot/grub/grub.cfg
.0GB: boot/initrd.img-2.6.31-14-generic
.0GB: boot/initrd.img-2.6.31-15-generic
.0GB: boot/vmlinuz-2.6.31-14-generic
.0GB: boot/vmlinuz-2.6.31-15-generic
.0GB: initrd.img
.0GB: initrd.img.old
.0GB: vmlinuz
.0GB: vmlinuz.old
_____________________________
Thanks for help in advance!

[HViktor]

In the mean time, while I wait for someone to help, I'll keep trying to figure out how to access the Karmac Koala via the live Ubuntu 9.10 cd.

Sorry for posting all over the place, but I really would like to be able to fix this system since it was all finely tuned to what I liked and there's files I would rather not loose. Instead of reinstalling again and again (newbie), It would be really great to be able to fix the problem and move on.

Hi All!

I think the mystic "GNOME Power Manager not installed correctly. Please contact your system administrator." message is only a symptom in the most of the cases. I was hit by this issue two week ago and I had to investigate a lot to find out the solution.

In my case I run out of free disk space because of an tricky sbackup setting and because I am a beginner Linux guy.
Behind the surface xserver (gnome) try to write important configuration files like xauthorization which has to be part of the new gnome session. Without that files you cannot log in.
A few problem solving tips around the out of space and Gnome login problem things:

• try to get a living console (from one of the recovery menus or hit CTRL+ALT+F1)
• Log in as usual
• try to make free space (use rm command carefully, try to delete older sbackup catalogues (as root) or a few unimportant files like avi-s or iso-s, some flac-s or something "big" . There are a nice tip from pigphis to to find them. Just follow with +50M at the end.
• After that you have a chance to solve the login issue. In my case I just deleted the /home/myusername/.gconf catalog (you can rename it also if you want).
• run startx
• I hope you will see a default gnome GUI and will feel more self-confidence to clean up your system and restore your settings manually or from backups.
• If not, you should continue with the other tips like install-reinstall gnome-power-manager or ubuntu-desktop...

The message: be careful with your disk space. It can initialise a lot of tricky issues in your system.

I hope you can use this ideas to fix your system. If I was wrong, sorry. If you request I can explain this process in more details (for instance with used commands). Sorry for my poor English too...

Best regards,
Viktor

[felipebarroeta]

Re: GNOME Power Manager Login Issue
This may or may not be your issue. I have had the problem to occur twice and finally found the culprit in MY case. It was simplebackup. In using SimpleBackup to back up my files to an external hard drive, occasionally it fails to mount the drive correctly. In such cases, if not configured correctly it will simply add a back up folder to your home folder and begin backing up there. That can quickly result in using up so much of your free space that your computer cannot boot properly.

Using a live CD, I went in and deleted the erroneous back ups and then everything booted fine. I also went back into SimpleBackUp Config and clicked the Destination tab and marked the Abort backup if destination directory does not exist box. Its all good now.

Hey man, thanks for that response, that's exactly the problem i'm having now. I could enter with the live Cd, but when I try to delete, it says I don't have the permission. How did you do it?

Cheers!