PDA

View Full Version : Today's update seems broken


dd_wizard
11th March 2010, 11:11 PM
After today's update, I got crashes from gnome-panel in ABRT for lots of applets. I quit testing after gedit, Control Center, and Mouse all crashed. Downgrading gnome-panel came up with more packages to downgrade than were updated, so I just used "sudo yum history undo ###" where ### was 196 for me. I'm now updating with --exclude=gnome-panel and gnome-panel-libs. I'll let you know how that goes.

dd_wizard

---------- Post added at 12:34 PM CST ---------- Previous post was at 12:19 PM CST ----------

Excluding gnome-panel and gnome-panel-libs seems to fix the issue. I'm letting ABRT download the packages it needs to report the gnome-panel crashes. Are there any brave souls interested in seeing what happens with the gnome-panel update? My system is x86_64.

dd_wizard

---------- Post added at 03:11 PM CST ---------- Previous post was at 12:34 PM CST ----------

Nobody else is having any problems with gnome-panel 2.29.92-1.fc13.x86_64? I switched from openbox to metacity, updated gnome-panel again, and it still crashes. At least I was able to generate a backtrace in metacity. It never worked in openbox.

dd_wizard

CiaW
12th March 2010, 04:29 AM
I'm running i686 version, just updated this morning and all is well except for a selinux violation that I reported when I woke the system from hibernation and opened >system > admin > services. Possibly it's the x86_64 gnome-panel? Maybe I'll be brave and reboot shortly (I'm actually looking for mod_simple_vhost for lighttpd, I logged on to look for a link to koji since I can't find it in the repo's...) and report back if I have problems.

If I have problems I'll be booting to CentOS to report back.

Edit: rebooted just fine, as far as I can tell! Fully updated.

CSchwangler
12th March 2010, 07:16 AM

I am running i686 and have no problem either.

dd_wizard
12th March 2010, 06:50 PM
It must have been only x86_64, I'm guessing. Today I grabbed gnome-panel and gnome-panel-libs 2.29.92.1-1.fc13.x86_64 from koji, and the updated was successful. Something made 2.29.92-1.fc13.x86_64 segfault for me yesterday. I don't see 2.29.92.1-1.fc13.x86_64 on updates-testing yet, so x86_64 users may want to wait for it or grab it from koji.

dd_wizard