Bug 1456202

2 things, can you post output from these to konsole commands?

rpm -q kio-extras libsmbclient


ldd -r /usr/lib64/qt5/plugins/kf5/kio/smb.so

rpm -q kio-extras libsmbclient

kio-extras-16.12.3-1.fc26.x86_64
libsmbclient-4.6.4-0.fc26.x86_64

Interesting, kio-extras is still version 16.12, when most of the apps were updated recently to 17.04

and here is an output for the 2nd command: https://pastebin.com/mnWSmTqz

Problem here:
libwbclient.so.0 => not found

This *may* help:

dnf reinstall libwbclient

(In reply to Rex Dieter from comment #3)
> Problem here:
> libwbclient.so.0 => not found
> 
> This *may* help:
> 
> dnf reinstall libwbclient

Yes, that did help. Good question what broke it.

If I recall, samba packaging handles libwbclient via alternatives (which can be fragile/problematic sometimes)

(In reply to Rex Dieter from comment #5)
> If I recall, samba packaging handles libwbclient via alternatives (which can
> be fragile/problematic sometimes)

It is not problematic if dnf upgrade transaction is not interrupted.

Alex, was there a warning/error ... in recent updates of F26

(In reply to Lukas Slebodnik from comment #6)
> (In reply to Rex Dieter from comment #5)
> > If I recall, samba packaging handles libwbclient via alternatives (which can
> > be fragile/problematic sometimes)
> 
> It is not problematic if dnf upgrade transaction is not interrupted.
> 
> Alex, was there a warning/error ... in recent updates of F26

Yes, actually I think it was updated in a same batch when I got kmail update error

*** Bug 1456145 has been marked as a duplicate of this bug. ***

I don't know what the problem was, because I don't believe that I'd had any interrupted upgrade transactions, but my smbd on this week's Fedora 26 updates was refusing to start because of a missing libwbclient library.

Doing the reinstall fixed it. But I think there's a problem in that update process somewhere.

A posttrans script may just not be a reliable option.

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.