gnome power manager not installed correctly!!

[geoff123]

i'm running 10/11 on a toshiba satellite. i kinda got tired of loosing stuff because i mis-timed the battery discharge, so some months ago i pulled the battery and just ran on the adapter (back ground, i don't know if it's nothing, related to, or caused the problem).

monday morning fired her up - boom got the power "gnome manager not installed correctly"message. tuesday, googled gnome then power then... you get the route, and found Fedoraforum.org, read the stuff, did the yum remove...., did the yum install.... everthing seemed cool. 2nd reboot she stopped at the "f/infinity/balloon" kinda logo.

i went to verbose startup and - all sorts of services were failing; the word deprecate(d, ing, tion) came up a lot "device full..." came up a fair bit as well. when i tried the "yum remove" approach again i got [rpmdb: write: 0x1fd48b0, 8192: No space left on device]. similarily on "yum install" same kinda stuff - deprecation, BaseExpection, deprecated..... kinda long winded. up till now (13 years) i've been able to solve all my linux problems myself, but this one is beyond meee. HELP!!

geoff

[dmyersturnbull]

Hey, geoff123.

Sadly, I don't have a solution for your specific problem. So I'm left with some questions that I hope will assist future posters:

1. First and foremost: are you running Fedora 10 or 11?

2. Removing the battery shouldn't confuse power manager. Did you try booting with the battery after the problems started occurring? If so, what happened?

3. Could you post your boot messages?

4. What errors occur (if any) when you boot to runlevel 3?

And some notes:

1. F11 uses DeviceKit-power for some lower-level power management that hal handled in F10. You could try reinstalling both power-manager and DeviceKit.

2. I saw this error before on one of my Fedora systems when I ran rm -rf /tmp to clear my cache manually. When the /tmp directory was re-created, the permissions were different (something like 711) rather than the expected 777, so PowerManager, which runs as non-root, couldn't access it. You could check that the permissions are indeed 777.

3. Unless the errors are the result of hardware failures, reinstalling Fedora will probably solve your problem.

I'm sorry that I don't have a here's-how-to-fix-it solution, but hopefully my post helped. Good luck.

—Douglas

[geoff123]

mornin douglas:

ya; it's 11. it started out as 10 but some where along the line i did an on-line upgrade.

thanks for the reply. there does seem to be some link to the tmp file. i rm'ed it and rebooted. all the FAILED's vanished - except for the Avahi daemon. in addition, it got as far as the user log in dialogue box and the nasty gnome power management note. i rebooted and tried the YUM....... again at which point the "device full" messages came out again.

i'm going to try a few other things; aka hack a bit.

thanks geoff

[Turbo13]

I am having the same problem in F11. Just before the problem I uninstalled the Palimpsest Disk Utility . It was reporting that my hard disk was failing and no other checker was reporting a problem. Now when I try to boot into X-windows/Gnome the system hangs with an error box saying that the Gnome power manager configuration is installed incorrectly. I am able to boot to a console though. Can I restore the Gnome Power manager configuration via editing a configuration file or yum? If so how would I do that? What is the configuration file for Gnome power manager and is there a default backup agvailable?

Also, before I removed the Palimpsest Disk Utility I did a software update in Gnome. This was on 11/12/09. So possibly there could have been a problem with the update.

Prior to the above two events I was not having a problem with the Gnome power manager configuration.

This is a desktop computer not a laptop. ANy help will be appreciated.

[geoff123]

similar; i was working on the 8th or 9th in the evening.....UPDATES AVAILABLE... i was basically finshed, so i said go to the updates. i came back around and the mouse seamed a little sticky, and things were slow. nonetheless, i shut her down.

it was the next day when the "gnome power manager message(s)" appeared. i literally googled "gnome power manager not installing correctly" and saw the FedoraForum.org site.

there was three or more replies to and from others with a similar problem. i tried the things mentioned there and it seemed to work, but about 2 boots later it was back again. not only was it back, it was a real mess.

this morning, i hacked a bit more. on some reboots, the failed daemon starts vanished, but then for no apparent reason on susequent boots they were failing again. the fact that numerous devices are reporting..... "no space device full" ....makes me think something else is going on, but i don't know what.

[Turbo13]

geoff try this:

At the login hit ctrl-alt-f2

login and then su to root

type:

yum remove gnome-power-manager

when it is done type:

yum install gnome-power-manager

So far ot has worked for me.....

Good luck ....Turbo

[geoff123]

turbo13:

thats the stuff i tried. it worked for a while and then back to the problem.

[Turbo13]

I found mor information in the following thread:

Originally Posted by oldgold

This may be a candidate for the most misleading error message of all time!

You will get this message if gconf-sanity-check-2 tries to write a test file into /tmp and can't read it back. It can be caused if you erase the /tmp directory and allow the system to create a new one automatically. It does so with the permissions set to read and execute only, so the test file cannot be written.

Change the permissions of /tmp to 777 and it will fix it.


The command line is chmod 777 /tmp

Then Timlimm wrote:

Originally Posted by timliim

Oldgold,

Thanks for the tip! Very interesting to learn. Agree it's good
candidate for the most misleading category.

Re: changing the permission of /tmp/:
How about

chmod a+rwxt /tmp

Nowadays /tmp/ has a "sticky bit" with it:

[timliim@taiwan ~]$ ls -ld /tmp
drwxrwxrwt. 26 root root 4096 2009-09-01 23:35 /tmp

The sticky bit on a directory (eg. /tmp/) "prevents unprivileged
users from removing or renaming a file in the directory unless
they own the file or the directory" (from "man chmod"), which is
exactly what /tmp/ needs.

Thanks!
Tim Taiwanese Liim

I plan to try this after I finsh a run of fsck....Mine is back to not working also..good luck

[bear2bar]

This seems to be a re-occuring problem that doesn't want to go away!
F11
Tosh Satellite 4 GB & 250GB HD
Dual boot Vista(yuk) / F11

I have both gnome & kde installed, it seems that after a certain yum update, can't identify which, the problem occurs.

I tried to boot into a terminal session & yum groupremove gnome-power-manager - it wiped my entire desktop with all the files. did a yum groupinstall gnome-power-manager - which yielded a long list of errors, & yes I tried to chmod 777 /tmp.

Wiped the HD & reinstalled everything after a few yum upgrades same problem. Tried to used KDE but was restricted only to the root folders, my user files & gnome desktop were gone!
Tried again as above a terminal session & yum groupremove gnome-power-manager & yum groupinstall gnome-power-manager with the same results. Had to wipe the HD & reinstall everything again.
Having used RH since version 6 & every new version upto to 8 & all the FC versions this is the first time anything like this has happened!

I don't particularly like kde but it might be the only way around, by removing gnome completely & selecting KDE or other desktop mgr?????

Any enlightened comments / suggestions are appreciated

[Turbo13]

Well, I don't really know what happened. I have spent many hours trying to get my F11 install back. I am not experienced enough to know for sure what is going on. But, I have seen some things that lead me to believe it has something to do with LVM partitions. When I first installed F10 I did so with EXT3 partitions. I had had problems with LVM partitions in F9 . I was unable to bring a system back that I know I could have with EXT2 or 3 partitions. It was probably due to my inexperience with them. But, really I have no need for the added complexity if LVM partitions. ....Getting back to the present. When I upgraded from F10 to F11 I suspect that F11 installed on LVM partitions even though I was running EXT3 drives in F10. I think this because right after I installed F11 I lost a huge amount of space on my 250 gig SATA drive It was suddenly nearly full. I am sure that I choose upgrade when I installed. Also, as my system got worse and worse (since my last post) I got LVM type errors. In the end I wound up wiping my drive and installing F12 beta. I plan to run it till the final release comes out and then do a clean install of F12 final. By the way I installed on EXT4 partitions. I plan to definately stay away from LVM partitions untill I need them or understand them better.

Turbo

[geoff123]

mornin:
just an aside, i didn't know you could pop the hard drive out of a laptop and stick it in a desktop - and have it run! that's what i did and it worked.

by the weekend, i was trying everything. i finally did a;

lsof |less

and came across a log file that had basically eaten up my whole drive! i deleted it, rebooted, and it was like the last week never happened. everything and i mean everything was back to normal - nothing amiss.

again, i'm a true hacker. i keep trying things until i solve the problem or i kill the whole system. the problem: when i do solve a problem, i'm never sure which thing(s) did the trick.

geoff

[Turbo13]

So it was a log file that ate you drive. I wonder if that was what ate mine. It is too late to find out now. I installed F12 Beta. Everything seems ok except selinux won't let me add a user in Samba???

Enjoy the hack

[RoboCat]

Hello,

I had this problem yesterday and after make of V4L-dvb. I don't think it was V4L but rather that my 8GB FDM was low on memory. The first time I solved the problem by deleting the v4l-dvb make file and rebooting ...

<CTRL> <ALT> <F2> during login to get to text mode

...Problem solved. But i needed v4l-dvb so I put all my documents on a usb when I got back to the GUI and did another make and make install of v4l-dvb.

Then this morning I had the same problem!!! This time I solved the problem by doing a

# sudo make clean in the d4l-dvb file. Hope this helps!

[Sherlockfh]

well, i did something very simple.... deleted some unwanted data files, and it's sorted for good.... checking for free space really helps...

[bob]

Let's not resurrect dead threads here. This one's two years old and not involving F14, F15 or F16 in original content. Thread closed.