Anyone ever run into this? And how to fix it?
This is a fresh install of F27. I tried to build a program called MakeMKV.
Here's the output of the configure script:
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> checking how to print strings... printf
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for fgrep... /usr/bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert x86_64-unknown-linux-gnu file names to
> x86_64-unknown-linux-gnu format... func_convert_file_noop
> checking how to convert x86_64-unknown-linux-gnu file names to
> toolchain format... func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking for gawk... gawk
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
> shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking for g++... no
> checking for c++... no
> checking for gpp... no
> checking for aCC... no
> checking for CC... no
> checking for cxx... no
> checking for cc++... no
> checking for cl.exe... no
> checking for FCC... no
> checking for KCC... no
> checking for RCC... no
> checking for xlC_r... no
> checking for xlC... no
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... no
> checking for -objcopy... no
> checking for objcopy... objcopy
> checking for -ld... /usr/bin/ld -m elf_x86_64
> checking for a BSD-compatible install... /usr/bin/install -c
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> checking for compress2 in -lz... yes
> checking openssl/opensslconf.h usability... no
> checking openssl/opensslconf.h presence... no
> checking for openssl/opensslconf.h... no
> configure: error: in
> configure: error: openssl library header files not found
> See `config.log' for more details
I completed my installation of solid-state drives and, of course, a new
installation of F27.
And now: what happened to my system configuration tools? How do I start
and stop services?
My biggest problem is Samba. I can't see any Windows computers on my
network, and they can't see me. (I can, however, see a network printer.
That, I configured in the System Settings app.)
This relates also to another thread I started, namely "where are my
system configuration tools." This problem comes after a "clean install"
of F27. My old system-config-samba applet is gone--dnf can't find it to
install. And I don't see any launcher for NetworkManager or whatever I'm
supposed to use.
Right now, the Fedora system can't see any Windows computer on my
network--can't find it even with a direct address input (and I wouldn't
know how to send one.) And the Windows boxes can't see the Fedora
system, either--I type "\\[hostname]" and get a message saying "Windows
can't access [that host]."
I've already edited the files /etc/hostname and /etc/hosts to reflect my
choice of hostname. I replaced "localdomain" with "home," in keeping
with the Windows domain.
How can I check that the services smb, nmb, and winbind are even running?
If you have followed my threads about:
SMB failing with F27
system hanging and requring repeated restarts,
then you've seen people suggest replacing my 1 TB HDD with an SSD. I
acquired a 1 TB SSD and then tried to clone the HDD to the SSD. The
clone /failed/. Reason: the disk is already showing some bad sectors.
The outputs of satactl and fsck make that undeniably clear.
On the advice of a professional installer, I have since acquired an
additional SSD (capacity 120 GB) and am now acquiring a mounting bracket
and some power and SATA data cables. I also downloaded the F27 KDE
Plasma 5 Spin as an ".iso" image.
My plan is to install F27 "clean" on the two SSD's, mounting the 120 GB
SSD at root ("/") and the 1 TB SSD at /home. I must then migrate my
data, browser cookies (Google Chrome, Firefox), e-mail
accounts/saved/messages/other settings (Thunderbird), and documents,
pictures, music, videos, and various downloads from the HDD to the SSD.
This machine has 8 GB of memory on board.
I now ask the community for some suggestions.
First, for partitioning:
1. Should I even try to accept /automatic/ partitioning when the
installer gets to that point?
2. Is 120 GB large enough for the information on the other directories
3. Should I create a separate /boot partition on the smaller SSD, and if
so, how large should I make it?
4. How large should the swap partition be, and where should I put it?
(That is, on the 120 GB or the 1 TB drive)?
5. In general, should I place a partition for anything other than /home
on the 1 TB SSD?
Now, as regards data migration: I have three user accounts to migrate,
plus another directory on /home called "lost and found."
1. Should I even try to migrate "lost and found," and if so, how?
2. I have at least two choices for migrating data and settings from the
various user accounts--three for some of them.
a. Connect the HDD to the SATA bus /after/ installing F27, and then
force-copying everything out of each /home directory to its
corresponding directory on the new configuration. (What command(s) would
you recommend using, and with what options/switches/etc.?)
b. Connect a large external HDD through a USB interface, transfer
all the data to it before modifying the hardware, then re-transfer it to
the system after installing the SSD's and F27.
c. Migrate the data to its "temporary refuge" over a Samba network
(possibly do-able for at least one account, and that's the biggest
account) and then re-migrate to the new system?
Which choice would you recommend?
3. Is it worth migrating every single hidden file or folder? Or should I
select only those folders that I know contain customization, account, or
similar settings, plus my saved documents/pictures/music/videos, and
Thanks in advance.
I have Fedora 26 on laptop. I have configured dhcp (client) on both
ethernet and wifi (for work and home).
Later in different environment I've configured second ethernet profile
manually. I want let it configured for future use in that environment but
now when I connect at work to ethernet I have to switch profile on ethernet
connection from manual profile to dhcp profile.
Is it way how to set priority on network profiles or set one profile
default? I couldn't find it in documentation.
Pavel Lisý <pavel.lisy(a)gmail.com>
I have existing systems with un-encrypted disks.
I have tried unsuccessfully to encrypt them using LUKS.
Has anyone out there been able to encrypt an existing system (after the
fact, so to speak)?
Roger Wells, P.E.
221 Third St
Newport, RI 02840
I have just upgraded my system to Fedora-27, which has caused Evolution
to upgrade to 3.26.3 (3.26.3-1.fc27). Evolution now has a "To Do"
pane, which I don't want, since I use another program for calendar and
How can I remove the "To Do" pane?
Thanks - jon
Within the next three weeks or so, barring any great surprises, I
hope to be putting Fedora 27 onto four PCs, a laptop, and a netbook. IIRC,
the netbook, which I haven't used recently, has F24 now; all the others
are running 26. I'll do all I can by upgrading, because every time I do a
fresh install, it costs me something more than a whole day per machine to
do the tweaking I need.
(I've been running Fedora since it was RedHat7; so my trifocal
fingers and arthritic eyeballs know their jobs IF I get all the tweaks
right -- a great boon and a bringer of cyber-survival, since I also keep
getting slower and more forgetful....)
A correspondent on another list says one used to be able to use
Mondo Rescue to grab all the settings on an existing install and clone
them onto a new one. That would save me vast tedium.
But the Mondo Rescue site lists only rpms for Fedora 23 and
before. And either I'm garbling my correspondent's directions, or they
don't work any more -- or both.
I tried a few variations on "dnf install Mondo-xyzq". I also
downloaded a few .rpms from Mondo's repository and ran "rpm -ivh" against
them. Both tries failed.
Is there a tutorial somewhere? Has Mondo Rescue forked into
something with another name? Have the Fedora Gurux and Alpha Plus
Technoids come up with a replacement while I wasn't looking??
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
Probably in connection with some version of yumex, I have somehow
gotten both */fc26.i686 and */fc26.x86_64 forms of a dozen or so rpms for
This has not been a problem till now. fc26 (and, unless I'm
misremembering, fc25 and fc24 before that) has just ignored the
superfluous ones. But now system-upgrade is choking on the ones for fc27.
The machine is actually .x86_64, as I have now discovered. I
tried adding --allowerasing and --allowerasing --best, but with no
Do I dare do something like "dnf remove compiz"?? (Or perhaps
"dnf remove */compiz/*/.i686 ???)
On 19 Dec 2017 07:49, <Francis.Montagnac(a)inria.fr> wrote:
On Mon, 18 Dec 2017 14:12:55 -0800 Gordon Messmer wrote:
> On 12/17/2017 01:17 PM, Francis.Montagnac(a)inria.fr wrote:
>> Dec 17 21:32:59 X systemd: Mounting /data2...
>> Dec 17 21:33:19 X mount: mount to NFS server 'Y' failed:
Resource temporarily unavailable, retrying
>> Dec 17 21:33:19 X systemd: Mounted /data2.
> Can you reproduce that condition and then get the output of "systemctl
> status NetworkManager-wait-online"? That should confirm that the
> ExecStart process does not include the -s flag.
Here it is:
systemctl status NetworkManager-wait-online
. NetworkManager-wait-online.service - Network Manager Wait Online
disabled; vendor preset: enabled)
Active: active (exited) since Tue 2017-12-19 07:58:05 CET; 4min 12s
Process: 743 ExecStart=/usr/bin/nm-online -q --timeout=30
Main PID: 743 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Dec 19 07:57:58 X systemd: Starting Network Manager Wait Online...
Dec 19 07:58:05 X systemd: Started Network Manager Wait Online.
journalctl -b -u data2.mount
-- Logs begin at Thu 2015-04-09 18:41:55 CEST, end at Tue 2017-12-19
08:01:55 CET. --
Dec 19 07:58:05 X systemd: Mounting /data2...
Dec 19 07:58:25 X mount: mount to NFS server 'Y' failed: Resource
temporarily unavailable, retrying
Dec 19 07:58:25 X systemd: Mounted /data2.
The setup of this server is:
eth0 static IP declaration with dns servers and gateway
eth0.2006 static IP declaration: additionnal vlan interface
with the associated port on a cisco switch configured as:
switchport trunk native vlan 390
switchport trunk allowed vlan 390,2006
switchport mode trunk
storm-control broadcast level 5.00 3.00
no cdp enable
/etc/resolv.conf was generated by NetworkManager at the same second
indicated by nm-online:
Size: 76 Blocks: 8 IO Block: 4096 regular file
Device: 806h/2054d Inode: 19924685 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-12-19 07:58:05.539740447 +0100
Modify: 2017-12-19 07:58:05.437735660 +0100
Change: 2017-12-19 07:58:05.438735707 +0100
The 'Y' server is in the eth0 subnet.
'Y' has to be resolved by the DNS.
As said before, even pinging the gateway IP succeeds only more than
20s after the routes (as seen by "ip route") are defined.
Cisco switch and that delay for traffic on a static address?
Sounds like symptoms of STP delaying s port from listening to forwarding...
Have you looked at disabling on that interface or setting portfast if it's
only host facing?