Fedora 26 (no surprise) messed up several things while trying to install updates on a reboot. It got up to 93%. I waited an hour and gave up and restarted and the troubles began.

--- smb will not connect to a server. It won't see the server.

---- I know that network is working. ifconfig is showing things are good. I can ssh to a server, no problem.

--- when I go to the gui "activities/files it asks for my password in order to view files! It's never done that before. Very broken.

--- can't display settings at all, won't go to them, just spins the cursor.

So something's very broken. I don't think it's the kernel because dnf says there's nothing to upgrade. Going back to previous kernel of Fedora 26 doesn't fix the situation. I know I'm on the bleeding edge but I chose Fedora 26 for very specific reasons and I have to live with it until it matures.

Does anyone have any suggestions on what to do? I'm kicking myself in the can for not having made a clone BEFORE I did the update so a whole bunch of things I've done to get the app backuppc working and configured would be thrown to the wind. I could painfully install Fedora 26 fresh again from scratch and then rsync selective items from a clone but I dread that.

I'm so pissed :-(. Any ideas? Thanks in advance.

You know Fedora 26 is only an Alpha release at the moment? The Beta isn't out yet, and it's another month or so to the actual release.

https://communityblog.fedoraproject....ates-schedule/

Hi...

Honestly, unless someone here knows how to specifically fix the individual issues you've mentioned, it's probably best to back up everything you want to save and then reinstall Fedora 26 from scratch.

Regards...

I agree. In fact, I already gave up, though I'll follow this thread if anyone has any fixes for the issues if they come up again. I'm in the process of reinstalling and configuring Fedora 26 from scratch. I knew it was alpha and I was willing to take the risks. I should never have accepted an update without first cloning. Those are the practices that an alpha user must follow, as well as being willing to accept loss of data. I think I'll get another SSD as a third clone.

Thanks for your help!


Bob

Perfect opportunity to implement snapshot as I mentioned in your other thread.

1 members found this post helpful.

Start with rebuilding your RPM database:
... next it should work OK again.

PS: It's a known issue in libdb (https://bugzilla.redhat.com/show_bug.cgi?id=1394862) and fixed in libdb-5.3.28-21 (Fedora 24, 25 and 26).

You're welcome

Regards...

Please don't just demolish your system (as recommended by others). The steps I posted above should just work.

Thanks, Jens. Well, that's great to know! If it ever happens to me again. But anyway, in absence of your information, I bit the bullet and reinstalled my entire Fedora 25, upgraded to 26 and now I'm back in business ;-)

Apologizes for being a bit late, but I still find it unacceptable/disappointing from my fellow LQ-members to recommend a fresh install for a rather unproblematic (and well known) bug that hit most people and was easy to fix.

Anyway, glad you have it running again