Install error: Config defaults for GNOME for GNOME power manager have not been installed correctly.

Hi folks, things were running fine until GNOME misbehaved;

GNOME failed to load telling me:

Install error, Configuration defaults for GNOME power manager have not been installed correctly.

So I

ctrl alt f2 

to the shell and check the logs in gdm and find this:

Could not ask power manager if user can suspend, launch helper exited with unknown return code 0.

gdm-simple-greeter[4150]: libgrade-warning:unexpected element inside

So I try

useradd mary 

to see if another user will get the desktop; I get the error

cant create etc/passwd no space left on device.

So I

df -h 

and get the following

sda8 45% used
sda9 35% used
sda1 49% used
sda5 12% used
/dev 1% used

I insert a usb drive to prepare for back up; Run

mount

on the shell to get the usb device name;
Then run

mount 	-t usbfs 	/dev/sdb      /proc/bus/usb 

to mount the device.
I end up with:

Cant create lock file /etc/mtab~ 4610 No space left on device(use -n flag to override)

So, I

sfdisk -l

and see 9 partitionitions

partition1 is HPFS/NTFS and bootable
partition2 is W95 Ext`d(LBA)
partition3 is unknown and empty
partition4 is also unknown and empty
partition5 is HPFS/NTFS
partition6 is W95 FAT 16(LBA)
partition7 is Linux swap /solaris
partition8 is Linux
partition9 is Linux

I

mount

again to check which ones are loaded at boot up time and get

partition8 ext3 on /
partition9 ext3 on /home
partition1 on /windows/C
partition5 on /windows/D

plus some other file systems mounted at boot up, but not mapping to any physical partitionition.
I try

fsck -t  ext3 /dev/sda9 

on partition9 and get warnings because its mounted, so I chicken out and try

umount /dev/sda9

and run into the error:

cant create lock file /etc/mtab~4832 no space left on device (use -n flag to override)

Good thing is there is a

boot.rootfsck
in
init.d
to

fcsk

the file system for the device mounted on root.
Since space is a problem, I

mkfs -t  ext3 /dev/sda6 

on partition6 which is not mounted at boot up time and try to

mount -t  ext3  /dev/sda6  /home/Boss

I still get the error

cant create lock file /etc/mtab~4735 no space left on device (use -n flag to override

zypper

for package update tells me

cant open /var/run/zypp.pid in mode w

pm

for power management tells me its not even recognised as a command.

Please all help is highly appreciated.

On 03/04/2010 11:36 AM, kawalya wrote:
>
> Hi folks, things were running fine until GNOME misbehaved;
>
> GNOME failed to load telling me:
>> Install error, Configuration defaults for GNOME power manager have not
>> been installed correctly.
>>
>
> So I
> Code:
> --------------------
> ctrl alt f2
> --------------------
> to the shell and check the logs in gdm and find this:
>> Could not ask power manager if user can suspend, launch helper exited
>> with unknown return code 0.
>> gdm-simple-greeter[4150]: libgrade-warning:unexpected element<requires
>> version> inside <glade-interface>
> So I try
> Code:
> --------------------
> useradd mary
> --------------------
> to see if another user will get the desktop; I get the error > cant create etc/passwd no space left on device.
> So I
> Code:
> --------------------
> df -h
> --------------------
> and get the following
>> sda8 45% used
>> sda9 35% used
>> sda1 49% used
>> sda5 12% used
>> /dev 1% used
>>
> I insert a usb drive to prepare for back up; Run
> Code:
> --------------------
> mount
> --------------------
> on the shell to get the usb device name;
> Then run
> Code:
> --------------------
> mount -t usbfs /dev/sdb /proc/bus/usb
> --------------------
> to mount the device.
> I end up with:> Cant create lock file /etc/mtab~ 4610 No space left on device(use -n
>> flag to override)
> So, I
> Code:
> --------------------
> sfdisk -l
> --------------------
> and see 9 partitionitions
>> partition1 is HPFS/NTFS and bootable
>> partition2 is W95 Ext`d(LBA)
>> partition3 is unknown and empty
>> partition4 is also unknown and empty
>> partition5 is HPFS/NTFS
>> partition6 is W95 FAT 16(LBA)
>> partition7 is Linux swap /solaris
>> partition8 is Linux
>> partition9 is Linux
>>
> I
> Code:
> --------------------
> mount
> --------------------
> again to check which ones are loaded at boot up time and get
>> partition8 ext3 on /
>> partition9 ext3 on /home
>> partition1 on /windows/C
>> partition5 on /windows/D
>> plus some other file systems mounted at boot up, but not mapping to any
> physical partitionition.
> I try
> Code:
> --------------------
> fsck -t ext3 /dev/sda9
> --------------------
> on partition9 and get warnings because its mounted, so I chicken out and
> try
> Code:
> --------------------
> umount /dev/sda9
> --------------------
> and run into the error: > cant create lock file /etc/mtab~4832 no space left on device (use -n
>> flag to override)
> Good thing is there is a > boot.rootfsck in> init.dto
> Code:
> --------------------
> fcsk
> --------------------
> the file system for the device mounted on root.
> Since space is a problem, I
> Code:
> --------------------
> mkfs -t ext3 /dev/sda6
> --------------------
> on partition6 which is not mounted at boot up time and try to
> Code:
> --------------------
> mount -t ext3 /dev/sda6 /home/Boss
> --------------------
> I still get the error> cant create lock file /etc/mtab~4735 no space left on device (use -n
>> flag to override
>
> Code:
> --------------------
> zypper
> --------------------
> for package update tells me > cant open /var/run/zypp.pid in mode w
>
> Code:
> --------------------
> pm
> --------------------
> for power management tells me its not even recognised as a command.
>
> Please all help is highly appreciated.
>
>
A lot of stuff done but I don’t know what’s your Gnome problem. Other
than uninstall / reinstall Power Manager software package what else
would you need to do?

Thanks folks, dont bother any more;
I solved the problem; it was a virus rendering my /tmp useless.

kawalya wrote:
> Thanks folks, dont bother any more;
> I solved the problem; it was a virus rendering my /tmp useless.

i highly doubt that!!

how did you determine it was a virus?
did you save a copy of it? (i ask because it could be VERY valuable!!!)


palladium