NetworkManager hangs update (fc8 x86-64)

[dsmithhfx]

On my last couple of security updates, several NetworkManager updates are included. After all updates are downloaded, the update hangs with NetworkManager conflict error messages. If I then deselect all NetworkManager entries from the list of updates, the update proceeds normally. (I applied a whole raft of security updates this morning, including kernel 2.6.25.11-60.fc8).

I'm guessing the offending NetworkManager updates are coming from development repositories, which I seem to have enabled for some reason.

I'm using the current fglrx module from the livna repositories, otherwise I can't think why I *might* need development repositories enabled. Can I disable them with no ill effects? Is it safe to do this through a gui package manager (e.g., Smart), or better to cli it? Will this resolve the NetworkManager update issue?

Apart from the annoying update hiccup it causes, I am not experiencing any network problems.

Thanks!

[joe.pelayo]

Originally Posted by dsmithhfx

On my last couple of security updates, several NetworkManager updates are included. After all updates are downloaded, the update hangs with NetworkManager conflict error messages. If I then deselect all NetworkManager entries from the list of updates, the update proceeds normally. (I applied a whole raft of security updates this morning, including kernel 2.6.25.11-60.fc8).

I'm guessing the offending NetworkManager updates are coming from development repositories, which I seem to have enabled for some reason.

I'm using the current fglrx module from the livna repositories, otherwise I can't think why I *might* need development repositories enabled. Can I disable them with no ill effects? Is it safe to do this through a gui package manager (e.g., Smart), or better to cli it? Will this resolve the NetworkManager update issue?

Apart from the annoying update hiccup it causes, I am not experiencing any network problems.

Thanks!

Hello dsmithhfx.

That problem started a while back to other fellow members (myself included). The solution, posted by someone else in another thread (don't have a link right now), is to uninstall NetworkManager-glibc.i386 (or something like that) and then proceed with the update.

It should take care of the problem.

Thanks.
Joe.

[dsmithhfx]

I'll try it and let you know if it works.

Thanks.

[dsmithhfx]

It worked. I deleted the NetworkManager glib for 32-bit (which also took out the other 32-bit N-M stuff). I decided to leave well enough alone, not delete the 64-bit versions, and try the update. It went through with nary a complaint.

Thanks!

[joe.pelayo]

Originally Posted by dsmithhfx

It worked. I deleted the NetworkManager glib for 32-bit (which also took out the other 32-bit N-M stuff). I decided to leave well enough alone, not delete the 64-bit versions, and try the update. It went through with nary a complaint.

Thanks!

It's good to know it worked for you, the credit though goes for someone else who originally came up with that solution.

Thanks.
Joe.