dnf-utils conflicts with yum-utils
by Neal Becker
Today's update, which wanted to install dnf-utils, failed due to conflicts
with yum-utils. I was able to remove yum-utils and then transactions
completed.
5 years, 1 month
- 2
- 1
Laptop overheating on Fedora 29
by Sudheer Satyanarayana
Hello,
I have installed Fedora 29 on Lenovo W540. The laptop overheats up soon
after booting.
cat /etc/fedora-release
Fedora release 29 (Twenty Nine)
lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation 8 Series/C220 Series
Chipset Family KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection
I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset
High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset
Family PCI Express Root Port #1 (rev d4)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset
Family PCI Express Root Port #2 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset
Family PCI Express Root Port #3 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset
Family PCI Express Root Port #5 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset
Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family
SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GK106GLM [Quadro
K2100M] (rev a1)
02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller
(rev 01)
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
The same laptop has been tested on Windows and Ubuntu. The heating issue
was present on those operating systems.
It seems to be a Fedora specific issue. How do I go about fixing it?
-
Sudheer S
5 years, 1 month
- 5
- 15
Network issue 2
by Patrick Dupre
This is a repost because the previous did not got through without an approval.
The entire journal is available on request.
Sorry for any distrubance.
Is it a problem with the NetworkManager?
Hello,
When I boot my machine, it takes a long time (~5 mn!) before I get the network connected
to the rest of the word (i.e. leaving my institute).
It seems that even after a time of inactivity, I can lost the connection
and that I have to "wake up" the NetworkManager.
"sleeping" or not, the out of ifconfig and of route -n are the same
I am attaching the journalctl
ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.13.3 netmask 255.255.252.0 broadcast 192.168.15.255
inet6 fe80::c2c9:faa6:83fa:222e prefixlen 64 scopeid 0x20<link>
ether 8c:ec:4b:b5:55:6a txqueuelen 1000 (Ethernet)
RX packets 6395 bytes 1590290 (1.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1620 bytes 259955 (253.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92b00000-92b20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 4 bytes 200 (200.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 200 (200.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
route -n
kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.12.1 0.0.0.0 UG 100 0 0 eno1
192.168.12.0 0.0.0.0 255.255.252.0 U 100 0 0 eno1
++++++++++++++++++
The journal with only the NetworkManager items
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.5356] modem-manager: ModemManager no longer available
Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8544] caught SIGTERM, shutting down normally.
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8586] exiting (success)
Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7456] NetworkManager (version 1.10.12-3.fc28) is starting... (for the first time)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7458] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7510] manager[0x55f65db5f0e0]: monitoring kernel firmware directory '/lib/firmware'.
Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname: using hostnamed
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname changed from (none) to "homere"
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8264] dns-mgr[0x55f65db79930]: init: dns=default, rc-manager=symlink
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8268] manager[0x55f65db5f0e0]: rfkill: WiFi hardware radio set enabled
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8269] manager[0x55f65db5f0e0]: rfkill: WWAN hardware radio set enabled
Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8485] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8510] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8511] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8518] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eno1 (e418d605-b034-3bdb-a1c5-c18642d7e304,"eno1")
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8665] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: Networking is enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8668] dhcp-init: Using DHCP client 'dhclient'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBondDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBridgeDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMDummyDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMEthernetDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacsecDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMPppDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMTunDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVethDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVxlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8720] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8780] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8796] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8826] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8837] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8850] device (lo): carrier: link connected
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8855] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8863] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8868] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 25 18:26:23 homere NetworkManager[1273]: <info> [1551115583.1068] modem-manager: ModemManager available
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9163] device (eno1): carrier: link connected
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9181] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9201] policy: auto-activating connection 'eno1'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9230] device (eno1): Activation: starting connection 'eno1' (e418d605-b034-3bdb-a1c5-c18642d7e304)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9236] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9240] manager: NetworkManager state is now CONNECTING
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9252] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9350] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9358] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9408] dhcp4 (eno1): dhclient started with pid 1845
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): address 192.168.13.3
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): plen 22 (255.255.252.0)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): gateway 192.168.12.1
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): lease time 86400
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.7'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.2'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): domain name 'icb-cnrs.net'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): state changed unknown -> bound
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9860] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9957] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9959] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9960] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9990] manager: NetworkManager state is now CONNECTED_SITEHello,
When I boot my machine, it takes a long time (~5 mn!) before I get the network connected
to the rest of the word (i.e. leaving my institute).
It seems that even after a time of inactivity, I can lost the connection
and that I have to "wake up" the NetworkManager.
"sleeping" or not, the out of ifconfig and of route -n are the same
I am attaching the journalctl
ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.13.3 netmask 255.255.252.0 broadcast 192.168.15.255
inet6 fe80::c2c9:faa6:83fa:222e prefixlen 64 scopeid 0x20<link>
ether 8c:ec:4b:b5:55:6a txqueuelen 1000 (Ethernet)
RX packets 6395 bytes 1590290 (1.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1620 bytes 259955 (253.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0x92b00000-92b20000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 4 bytes 200 (200.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 200 (200.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
route -n
kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.12.1 0.0.0.0 UG 100 0 0 eno1
192.168.12.0 0.0.0.0 255.255.252.0 U 100 0 0 eno1
++++++++++++++++++
The journal with only the NetworkManager items
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.5356] modem-manager: ModemManager no longer available
Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8544] caught SIGTERM, shutting down normally.
Feb 25 18:25:32 homere NetworkManager[1287]: <info> [1551115532.8586] exiting (success)
Feb 25 18:25:32 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:25:32 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7456] NetworkManager (version 1.10.12-3.fc28) is starting... (for the first time)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7458] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.7510] manager[0x55f65db5f0e0]: monitoring kernel firmware directory '/lib/firmware'.
Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname: using hostnamed
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8262] hostname: hostname changed from (none) to "homere"
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8264] dns-mgr[0x55f65db79930]: init: dns=default, rc-manager=symlink
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8268] manager[0x55f65db5f0e0]: rfkill: WiFi hardware radio set enabled
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8269] manager[0x55f65db5f0e0]: rfkill: WWAN hardware radio set enabled
Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:22 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8485] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8510] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8511] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8518] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eno1 (e418d605-b034-3bdb-a1c5-c18642d7e304,"eno1")
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8665] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8666] manager: Networking is enabled by state file
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8668] dhcp-init: Using DHCP client 'dhclient'
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBondDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMBridgeDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMDummyDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMEthernetDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacsecDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8681] Loaded device plugin: NMPppDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMTunDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVethDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8682] Loaded device plugin: NMVxlanDeviceFactory (internal)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8720] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8780] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8796] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8826] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8837] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8850] device (lo): carrier: link connected
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8855] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8863] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 25 18:26:22 homere NetworkManager[1273]: <info> [1551115582.8868] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 25 18:26:23 homere NetworkManager[1273]: <info> [1551115583.1068] modem-manager: ModemManager available
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9163] device (eno1): carrier: link connected
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9181] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9201] policy: auto-activating connection 'eno1'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9230] device (eno1): Activation: starting connection 'eno1' (e418d605-b034-3bdb-a1c5-c18642d7e304)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9236] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9240] manager: NetworkManager state is now CONNECTING
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9252] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9350] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9358] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9408] dhcp4 (eno1): dhclient started with pid 1845
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): address 192.168.13.3
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9851] dhcp4 (eno1): plen 22 (255.255.252.0)
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): gateway 192.168.12.1
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): lease time 86400
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.7'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): nameserver '192.168.4.2'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): domain name 'icb-cnrs.net'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9852] dhcp4 (eno1): state changed unknown -> bound
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9860] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9957] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9959] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9960] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9990] manager: NetworkManager state is now CONNECTED_SITE
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9991] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0027] device (eno1): Activation: successful, device activated.
Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0032] manager: startup complete
Feb 25 18:26:27 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out
Feb 25 18:26:56 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:56 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:27:06 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:31:52 homere NetworkManager[1273]: <info> [1551115912.9518] connectivity: (eno1) timed out
Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:36:33 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:26 homere NetworkManager[1273]: <info> [1551115586.9991] policy: set 'eno1' (eno1) as default for IPv4 routing and DNS
Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0027] device (eno1): Activation: successful, device activated.
Feb 25 18:26:27 homere NetworkManager[1273]: <info> [1551115587.0032] manager: startup complete
Feb 25 18:26:27 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-online comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:36 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:26:56 homere NetworkManager[1273]: <info> [1551115616.9518] connectivity: (eno1) timed out
Feb 25 18:26:56 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:26:56 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:27:06 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:31:52 homere NetworkManager[1273]: <info> [1551115912.9518] connectivity: (eno1) timed out
Feb 25 18:36:23 homere NetworkManager[1273]: <info> [1551116183.3831] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 25 18:36:23 homere dbus-daemon[1104]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=1273 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 25 18:36:23 homere audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 25 18:36:33 homere audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
5 years, 1 month
- 1
- 0
Stuck Kernel Version.....
by Eddie O'Connor
Ok I have gone nuts trying to figure this out, and I'm just about ready to
just re-install the OS. (Fedora 29) I have been using Fedora since
like....version 12, and have experienced all kinds of issues but this one
baffles me. So:
I had updated from fc26 to fc27 successfully, but I have noticed that since
upgrading from 27 to 28 that the kernel versions while they have gone up
(e.g. from 3.12.203 >> 3.12.207 and these numbers I use are for example
only!) I notice that the "fc" number has remained the same (in other words
the "fc27" bit of the kernel name!) I have tried everything I have found
online from trying to upgrade the kernel through the Terminal to trying to
download, install, and compile a newer kernel version and no matter what
I've tried that part remains the same. So my last attempt/effort will be a
transfer of all my data and a complete re-install of F29. But it would be
nice to know what might have caused this...in case it happens again!
EGO II
5 years, 1 month
- 4
- 4
Re: update failed
by Frank McCormick
On 2019-02-25 10:01 a.m., Jakub Jelen wrote:
> On Mon, 2019-02-25 at 09:33 -0500, Frank McCormick wrote:
>> Tried to update my Fedora 29 this morning. It failed
>>
>> with this error:
>>
>>
>> [SKIPPED] google-chrome-stable-72.0.3626.119-1.x86_64.rpm: Already
>> downloaded
>> Package ffmpeg-4.1.1-7.fc29.x86_64.rpm is not signed
>> Package ffmpeg-libs-4.1.1-7.fc29.x86_64.rpm is not signed
>> Package libavdevice-4.1.1-7.fc29.x86_64.rpm is not signed
>> The downloaded packages were saved in cache until the next
>> successful
>> transaction.
>> You can remove cached packages by executing 'dnf clean packages'.
>> Error: GPG check FAILED
>>
>>
>> Is there a work around or should I just wait ?
> $ dnf info google-chrome-stable
> Error: No matching Packages to list
>
> There is no chrome package in Fedora. If you have issues with updates
> from third party repositories, it is probably better to ask where you
> got these repositories from.
>
> Note, that chromium works fine.
>
> Regards,
My google-chrome comes from Google itself, but that wasn't
the problem. I had added a 3rd party repository a long time
ago (UnitedRPM)...I have long since forgotten the reason, but
the ffmpeg package if was offering conflcited with the package(s)
from rpm fusion. I dumped UnitedRPM and the problem is gone.
Thanks
Frank
5 years, 1 month
- 2
- 1
Patching oddity
by Chris Kottaridis
The history of this machine is that Fedora 25 was initially installed
and then I have been using the system upgrade to keep upgrading it to
the newer release. I just upgraded it to Fedora29 two weeks ago.
I use dnfdragora GUI tool to do the patching. When I selected ALL of the
packages "to update" I got a transaction error complaining that
dnf-utils and yum-utils were in conflict on some files. When I ran it
from the command line the dnf-utils package was in a category to be
installed with a note about "weak dependency". Not exactly sure what
that means.
I figured I would apply subsets of the packages available to update but
avoid anything that looked like it had anything to do with dnf, such as
other dnf-* packages and packages referring to repositories and such. I
figured I'd come back to them later. I didn't want a dependency to pull
in dnf-utils and get me back in the problem I had.
So, I'd select a dozen or so packages in dnfdragora and apply them and
then select another group. I apparently wasn't to good at selecting
packages that didn't have dnf-* dependencies because every once in a
while one of the dnf-* files was brought in due to dependencies. Since
none ever included dnf-utils I went and ahead and selected apply.
In the end all the packages ended up applying without errors and
dnfdragora claimed everything is up to date and there is nothing to do.
When I looked dnf-utils is not installed, yum-utils still is.
So, I am confused why when I try to apply ALL the updates at once dnf
claims dnf-utils needs to be installed, but if I apply them in small
groups dnf says everything is up to date but dnf-utils isn't installed ?
I am concerned that I will continue to run into this.
Is dnf-utils supposed to replace yum-utils ?
Is this a ramification of continually upgrading the OS instead of
installing a new version and moving over my application ?
This was always my concern about upgrading OS's. Experience taught me
that an upgrade to a release doesn't leave you in the same place as a
fresh install of the same release. But, I should say I love this OS
upgrade system. It definitely made my life easier and has gone off with
little hitches. Fedora versions cycle so quickly that I would have used
a different OS for this project without it. Cudos to the team that
implemented it! But if there are minor cleanups necessary, such as
cleaning out older packages that are no longer needed and may conflict
with newer packages, that would be good to know.
Thanks
Chris K
5 years, 1 month
- 2
- 1
Gnome settings -> Online accounts and tor hidden services
by Robin Lee
Hi
I wonder if there's away to configure a Nextcloud account in Online
Accounts or otherwise that would connect to a Nextcloud server that
resides on a tor hidden service, i.e. it would need to connect to an
onion address.
Cheers
Robin
5 years, 1 month
- 3
- 10
Re: update failed
by Frank McCormick
On 2019-02-25 9:59 a.m., Ed Greshko wrote:
> On 2/25/19 10:33 PM, Frank McCormick wrote:
>> Tried to update my Fedora 29 this morning. It failed
>>
>> with this error:
>>
>>
>> [SKIPPED] google-chrome-stable-72.0.3626.119-1.x86_64.rpm: Already downloaded
>> Package ffmpeg-4.1.1-7.fc29.x86_64.rpm is not signed
>> Package ffmpeg-libs-4.1.1-7.fc29.x86_64.rpm is not signed
>> Package libavdevice-4.1.1-7.fc29.x86_64.rpm is not signed
>> The downloaded packages were saved in cache until the next successful transaction.
>> You can remove cached packages by executing 'dnf clean packages'.
>> Error: GPG check FAILED
>>
>>
>> Is there a work around or should I just wait ?
>>
> I don't believe ffmpeg and libavdevice packages are part of fedora. Mine come from rpmfusion.
>
> If you do a "dnf info ffmpeg" what do you see in "From repo" section?
>
Yup. They came from UnitedRPM, which was in conflict with the ones
from rpmfusion.
I don't recall why I added the UnitedRPM repository....but it's gone now.
Thanks
Frank
5 years, 1 month
- 1
- 0
update failed
by Frank McCormick
Tried to update my Fedora 29 this morning. It failed
with this error:
[SKIPPED] google-chrome-stable-72.0.3626.119-1.x86_64.rpm: Already
downloaded
Package ffmpeg-4.1.1-7.fc29.x86_64.rpm is not signed
Package ffmpeg-libs-4.1.1-7.fc29.x86_64.rpm is not signed
Package libavdevice-4.1.1-7.fc29.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
Is there a work around or should I just wait ?
Thanks
5 years, 1 month
- 3
- 2
usb devices in gnome boxes with windows
by Alessandro
Hi everyone,
I write this post to ask for information about a problem I encounter on
gnome boxes. I tried to install both Windows 7 and Windows 10 ltsb, but
neither of them for having installed Windows guest tools for Spice when I
insert a USB key (usb2, usb3 etc.) and from the settings of boxes I apply
the shared USB stick, this is detected in Windows, but not configured and
therefore remains unusable. I wanted to know if someone has encountered the
same problem and possibly help me to solve it or to virtualize windows is
better to use Virtualbox?
I thank you all
5 years, 1 month
- 1
- 0