PDA

View Full Version : WARNING: This morning's updates may be bad



DennyCrane
24th August 2009, 02:46 PM
(Fedora 11)

My computer was actually a little buggy since last night, so naturally I was eager to perform the new updates that came in this morning. I restarted after the updates, though that wasn't a requirement, but when I get to the login screen, I had a million notifications about Gnome Power Manager's configuration not being installed correctly ("Install Problem -- The configuration defaults for GNOME Power Manager have not been installed correctly. Please contact your computer administrator."). In addition, the background and icons are wrong for the login screen. Upon attempting to log-in, everything seems to freeze but the mouse. It appears that my panels never come up, nor the window decorations, etc. It just shows my Thunderbird window.

Any ideas how I can address this?

kulbirsaini
24th August 2009, 02:51 PM
If you use compiz or any other 3D effects thingie, then it may be your video drivers creating the mess. In that case you can restore your old xorg.conf (in console mode) and see if things work out. Other thing you may try is yum-complete-transaction in case something went wrong while updating.

DennyCrane
24th August 2009, 02:55 PM
No compiz. I do have the basic Gnome compositing turned on. I'll try your suggestions -- thanks.

DennyCrane
24th August 2009, 03:06 PM
No success with yum-complete-transaction.

I don't have an old xorg.conf file, since I don't have an xorg.conf file to begin with. Fedora and/or xorg got rid of the conf file, didn't they?

Dan
24th August 2009, 03:14 PM
Yes. By default it doesn't build one.

And I'm not entirely surprised this morning's update breaks things. Seems right in keeping with the rich tradition established with most F11 updates. (The last of which ... quasi-bricked my wife's new laptop.) <..:cool:..>

bob
24th August 2009, 03:21 PM
HERESY! HERESY! :eek: User Error, User Error! :confused: Must File Bugzilla!

(Bob runs around the room with hands over ears at the notion that Fedora's imperfect. :eek:)


:D

DennyCrane
24th August 2009, 03:44 PM
I believe gconf has been corrupted. It looks more like all of my settings were ruined. I'm posting now from F11 (more or less (who am I kidding -- less)) after uninstalling gnome-settings-daemon and then reinstalling along with all the things that had uninstalled with it. It lets me log-in now, but get some error messages from programs, and all sorts of interface bugs.

I think I should be able to restore a nightly backup of the gconf from last night or the night before.

Dan
24th August 2009, 04:11 PM
HERESY! HERESY! :eek: User Error, User Error! :confused: Must File Bugzilla!

(Bob runs around the room with hands over ears at the notion that Fedora's imperfect. :eek:)


:D *Dan raises one eyebrow, flips through the ward rolodex, and checks Bob's current meds dosages.*

<..:p..>


Bugzilla filed.



<..:D..>

DennyCrane
24th August 2009, 05:14 PM
I thought I could just restore ~/.gconf and~/.gconfd, but that doesn't seem to address the issue. Perhaps my guess is wrong or this is not the way to go about restoring my settings? Actually, I tried restoring my entire home folder from Sunday morning backup, and there were still as many or more issues when I tried to log in.

R3353
24th August 2009, 05:38 PM
I updated this morning and received:

ktorrent-3.2.3-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: kdelibs4(x86-32) >= 4.3.00 is needed by package ktorrent-3.2.3-1.fc11.i586 (updates)
Error: Missing Dependency: kdelibs4(x86-32) >= 4.3.00 is needed by package ktorrent-3.2.3-1.fc11.i586 (updates)

I then updated again skipping this one and all is well.

Perhaps the gnome-power-manager-2.26.4-1.fc11.i586 update fails on some configurations?

JerichoKru
24th August 2009, 06:05 PM
ktorrent-3.2.3-1.fc11.i586 from updates has depsolving problems
--> Missing Dependency: kdelibs4(x86-32) >= 4.3.00 is needed by package ktorrent-3.2.3-1.fc11.i586 (updates)
Error: Missing Dependency: kdelibs4(x86-32) >= 4.3.00 is needed by package ktorrent-3.2.3-1.fc11.i586 (updates)

Got the same error with F10

DennyCrane
24th August 2009, 06:19 PM
I thought I could just restore ~/.gconf and~/.gconfd, but that doesn't seem to address the issue. Perhaps my guess is wrong or this is not the way to go about restoring my settings? Actually, I tried restoring my entire home folder from Sunday morning backup, and there were still as many or more issues when I tried to log in.

Ah, well of course there is. All these error messages are talking about there not being a default configuration, and I have problems before even logging-in to my account, so the root gconf is probably the one that's corrupted? Does that sound right? How on Earth might I correct this? I don't backup root's files and settings....


EDIT:
Some of the keys for programs which are spitting out errors say "this key has no schema"

gauchao
24th August 2009, 09:37 PM
No problems in my system after update...

ArthurDent123
26th August 2009, 09:25 AM
Well my system is completely borked! I need some urgent advice...

I updated yesterday (Tue 25 August) and rebooted with no problem. This morning after a cold restart I get the following just before the GDM loging screen:

There is a problem with the configuration server
(/usr/libexec/gconf-sanity-check-2 exited with status 265)Pressing OK to that I get to the GDM loging screen but the deault background is missing (just a black background) and I get the following error displayed:

The configuration defaults for Gnome Power Manager have not been installed correctly.
Please contact your system administratorI am able to select my user and enter the password, but the login hangs - the screen goes black and the sanity-check error is displayed again.

I have tried uninstalling gnome-power-manager (using yum from the terminal) but this simply removes the second error message - the sanity-check one remains and still I cannot login. Re-installing gnome-power-manager simply gives me the above problem again.

I list below all the updates done since yesterday. If this problem is not related to these updates I will start another thread (with apologies to the OP of this one) but if it is can anyone tell me how to fix it? I am unable to use my F11 system at all and have had to resort to a Windows laptop to post this! Please help!

Thanks

Mark


Aug 25 13:11:30 Updated: xz-libs-4.999.8-0.8.beta.20090817git.fc11.i586
Aug 25 13:11:31 Updated: libksba-1.0.6-1.fc11.i586
Aug 25 13:11:32 Updated: strigi-libs-0.7.0-1.fc11.i586
Aug 25 13:11:32 Updated: sip-4.8.2-1.fc11.i586
Aug 25 13:11:33 Updated: soprano-2.3.0-2.fc11.i586
Aug 25 13:11:34 Updated: dirmngr-1.0.3-2.fc11.i586
Aug 25 13:11:34 Updated: pinentry-0.7.6-1.fc11.i586
Aug 25 13:11:36 Updated: gnupg2-2.0.12-1.fc11.i586
Aug 25 13:11:37 Updated: gpgme-1.1.8-1.fc11.i586
Aug 25 13:11:37 Updated: xz-4.999.8-0.8.beta.20090817git.fc11.i586
Aug 25 13:12:04 Updated: foomatic-4.0.2-4.fc11.i586
Aug 25 13:12:05 Updated: amarok-utils-2.1.1-4.fc11.i586
Aug 25 13:12:05 Updated: xz-lzma-compat-4.999.8-0.8.beta.20090817git.fc11.i586
Aug 25 13:12:07 Updated: PyQt4-4.5.4-1.fc11.i586
Aug 25 13:12:08 Updated: PyQt-3.18.1-1.fc11.i586
Aug 25 13:12:27 Updated: gnome-power-manager-2.26.4-3.fc11.i586
Aug 25 13:12:28 Updated: 6:kdelibs-common-4.3.0-6.fc11.i586
Aug 25 13:12:29 Updated: xz-devel-4.999.8-0.8.beta.20090817git.fc11.i586
Aug 25 13:12:29 Updated: leonidas-kde-theme-11.0.2-1.fc11.noarch
Aug 25 13:12:30 Updated: grub-0.97-51.fc11.i586
Aug 25 13:12:47 Updated: oxygen-icon-theme-4.3.0-1.fc11.noarch
Aug 25 13:12:49 Updated: system-config-services-0.99.35-1.fc11.noarch
Aug 25 13:12:59 Updated: 6:kdelibs-4.3.0-6.fc11.i586
Aug 25 13:13:03 Updated: amarok-2.1.1-4.fc11.i586
Aug 26 07:08:42 Updated: cups-pk-helper-0.0.4-3.fc11.i586
Aug 26 07:08:42 Updated: 12:dhclient-4.1.0p1-2.fc11.i586
Aug 26 07:40:18 Erased: gnome-power-manager
Aug 26 07:59:41 Installed: gnome-power-manager-2.26.4-3.fc11.i586

ArthurDent123
26th August 2009, 10:11 AM
OK - Apologies everyone. It was me that borked my system (though I am still not entirely sure why).

I have for a while had my /tmp directory mounted as tmpfs in /etc/fstab (following advice on another forum) to give me a self-cleaning /tmp directory on reboot. This has worked fine thus far.

Last night I decided to re-set it to what it was (vmware didn't launch properly and I wondered if that was the problem).

On this morning's start I got the errors I described above. re-re-setting fstab (back to where /tmp is mounted as tmpfs) seems to have fixed my problems. But I don't know why!

Sorry for the noise...

Mark

DennyCrane
26th August 2009, 01:21 PM
Strange.

In any case, I ended up having to re-install Fedora 11. I think there is still something wrong with the settings daemon though, since I often get a message about it not closing when I try to log off or restart.

oldgold
29th August 2009, 04:40 PM
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.

oldgold
29th August 2009, 04:41 PM
Probably should have included the command line in my previous post:

chmod 777 /tmp