NetworkManager drops config on link down
by Chris Adams
I have a USB ethernet adapter on my desktop system that I use when
configuring new equipment (servers, routers, switches, etc.). I have a
variety of pre-set configs in NM, like 192.168.0.x, 10.0.0.x, etc.
Often while configuring something, I need to reboot it, which drops the
link. NM "helpfully" de-configures the interface, and I have to wait
for link to return and re-select the right config (because NM won't let
me select a config for an interface that is link-down).
Is there a way to disable this "helpfulness", so that for this USB
ethernet interface, once I select a config, it stays configured (even if
the link drops)? This is frustrating behavior in many cases.
--
Chris Adams <linux(a)cmadams.net>
7 years, 11 months
Upgrade, what to do -
by Bob Goodwin
I ran "# dnf system-upgrade download --refresh --releasever=24
--allowerasing" earlier this morning and got the following error message:
.... snip ......
installing package nss-softokn-freebl-3.24.0-1.0.fc24.i686 needs
1503MB on the / filesystem
installing package glibc-2.23.1-8.fc24.i686 needs 1517MB on the /
filesystem
installing package compat-libvpx1-1.3.0-4.fc24.i686 needs 1511MB on
the / filesystem
Error Summary
-------------
Disk Requirements:
At least 1598MB more space needed on the / filesystem.
Obliviously / is near full.
[root@Box10 bobg]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.7G 0 3.7G 0% /dev
tmpfs 3.7G 768K 3.7G 1% /dev/shm
tmpfs 3.7G 1.3M 3.7G 1% /run
tmpfs 3.7G 0 3.7G 0% /sys/fs/cgroup
/dev/sda3 50G 48G 0 100% /
tmpfs 3.7G 208K 3.7G 1% /tmp
/dev/sdc1 230G 6.6G 211G 4% /home2
/dev/sda2 173G 135G 30G 83% /home
/dev/sda1 477M 166M 282M 38% /boot
192.168.1.8:/home 818G 574G 203G 74% /mnt/DATA1
//192.168.1.48/myshare 686G 217G 435G 34% /mnt/box48
tmpfs 748M 12K 748M 1% /run/user/1000
Where can I look to delete a few files, will anything in root help or do
I have to be more specific? Better yet, how to fix this? It looks like I
could take some space from "home", home2 is another hard drive with some
backup files on it.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-23/64bit LINUX XFCE POP3
7 years, 11 months
yum update issue..
by bruce
Happy 4th guys..
I have a centos 6.5 box with a yum update error. (I know, this is fed, but
thought maybe I could get pointers here on this!)
The laptop runs kernel for elrepo, to be able to use the builtin wifi.
The update process, was the same as usual, as root, run "yum update" never
had an issue prior to this.
The error is:
Total 90 kB/s | 756 MB
144:00
Running rpm_check_debug
Running Transaction Test
Transaction Check Error:
file /lib/firmware/rtlwifi/rtl8192cfw.bin from install of
kernel-firmware-2.6.32-642.1.1.el6.noarch conflicts with file from package
rtlwifi-firmware-20131223git-1.el6.elrepo.noarch
file /lib/firmware/rtlwifi/rtl8192cfwU_B.bin from install of
kernel-firmware-2.6.32-642.1.1.el6.noarch conflicts with file from package
rtlwifi-firmware-20131223git-1.el6.elrepo.noarch
file /lib/firmware/rtlwifi/rtl8192defw.bin from install of
kernel-firmware-2.6.32-642.1.1.el6.noarch conflicts with file from package
rtlwifi-firmware-20131223git-1.el6.elrepo.noarch
Error Summary
-------------
so my question.. how/what do I need to do to resolve the error, and still
perfom the updates and not screw up the wifi.
By the way, in the event the wifi does screw up, I've got old spare usb
wifi dongles, but I'd prefer to be able to use the onbard wifi. The laptop
is a toshiba satellite
Thanks for any pointers!
7 years, 11 months
no sound after yum update
by bruce
Hi.
Forgive me for posting here on a centos issue... but, maybe it'll help
someone if they run into the same issue on centos/fed...
Did a yum update.... yum went through the process, did the update as
expected.
However, after the update.. sound was gone!
Checked for the cards:
cat /proc/asound/cards
only one card '0'
Did a
alsactl restore 0 (as root)
Followed this up with a
pulseaudio -k
pulseaudio -D --system (as root) in a sep window..
Sound appears to be running..
If you have additional info, feel free to add it, might help someone in the
future!
Thanks
7 years, 11 months
keyboard not bringing monitor back up after power management or
dpms screen suspend
by George Avrunin
After upgrading to F24, I'm having the following problem. I have KDE
Settings -> Power Management -> Energy Saving set to turn on "screen
energy saving" after 10 minutes. This blanks the screen after 10 minutes
of inactivity, as expected. (xset -q shows that DPMS is enabled, too,
of course.)
Previously, hitting the Alt key or clicking the mouse would bring back the
desktop quickly. Now (on two different machines), it's not coming back.
But the machine is recognizing the keyboard--I've found that if I do
Ctl-Alt-F2 to switch to a virtual terminal, the monitor quickly shows the
login prompt, and I can go back to X on VT-1 and my Plasma desktop is
there. But hitting other keys (Return, Alt, random letters) doesn't seem
to wake it up. The monitor acts as if there's no input from the
computer. It's the DPMS Suspend state that's the problem; the display
comes back when it's in the Standby one. One of the machines has screen
locking turned on but the other doesn't.
These are both Dell Precision workstations with Intel integrated graphics,
in case that matters (one with a Dell monitor and the other with a Samsung
monitor). I didn't (intentionally) change the settings until I started
trying to troubleshoot after the problem arose, so these should all have
been the same as under F23. I did find an very old bug that might have to
do with this, with a comment from March (747162).
I tried using xset to turn of DPMS; then the screen doesn't blank at all.
And the same sort of thing happens with the KDE settings version turned
off and DPMS on. Disabling DPMS means the monitor stays on. So it's
seems like it's really a problem with DPMS, not the KDE settings. The
workaround of switching to a VT means this isn't urgent, but it is
annoying. What am I missing?
George
7 years, 11 months
gdm: No users shown on bootup
by Richard Shaw
My wife's laptop recently started having an issue where GDM will come up
but no users are listed.
Any attempt to go to a VT shows the dreaded:
A start job is running for Wait for Plymouth Boot to Quit
Which is never does.
Switching the display manager to lightdm works around the login issue but
then screen saver/blanking/power off and locking doesn't work.
It may or may not be related but I've also found that switching to runlevel
3 from a remote ssh session completely locks up the session. No ctl-c or
ctl-d or ctl-z has any effect. I have to force quit the terminal and cannot
reconnect.
I can then login to the system locally because plymouth has been killed of
by changing into multi-user mode and systemctl status shows sshd strangely
running fine!
I can go back into graphical mode to the same gdm problem (no users listed)
and can connect remotely over ssh again.
This system appears to have completely lost it's mind. I've run "rpm -Va"
and nothing jumps out at me, forces fsck, relabeled the whole system. Tried
various incantations of downgraded systemd, gdm, and other packages, tried
the oldest kernel available, all with the same result.
I've probably spent an accumulated 10 hours on this problem and am about to
give up and reinstall...
Thanks,
Richard
7 years, 11 months
Chrome no longer working
by Timothy Murphy
I'm running Fedora-24/KDE.
I see that Google Chrome is no longer working -
when I choose it from Applications->Internet I get the message
"KDEinit could not launch /usr/bin/google-chrome-unstable".
The version of chrome is google-chrome-unstable-53.0.2783.2-1.x86_64
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
7 years, 11 months
NetworkManager-wait-online.service is not run
by Juan Orti Alcaine
Hi,
I'm having problems with some services which depend of network-online.target
Although I've enabled NetworkManager-wait-online.service, it is not
run at boot. Any idea?
[root@xenon ~]# systemctl status network-online.target
● network-online.target - Network is Online
Loaded: loaded (/usr/lib/systemd/system/network-online.target;
static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd.special(7)
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
[root@xenon ~]# systemctl status NetworkManager.service -n5
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service;
enabled; vendor preset: enabled)
Active: active (running) since lun 2016-07-04 10:58:19 CEST; 2h 38min ago
Main PID: 1191 (NetworkManager)
Tasks: 3 (limit: 512)
CGroup: /system.slice/NetworkManager.service
└─1191 /usr/sbin/NetworkManager --no-daemon
jul 04 10:58:27 xenon NetworkManager[1191]: <info> [1467622707.1465]
manager: startup complete
jul 04 10:58:51 xenon NetworkManager[1191]: <info> [1467622731.8390]
device (br-lan): link connected
jul 04 10:58:52 xenon NetworkManager[1191]: <info> [1467622732.2913]
connectivity: check for uri
'http://fedoraproject.org/static/hotspot.txt' failed with 'Error al
resolver «fedoraproject.org»: Name or service not known'
jul 04 10:58:52 xenon NetworkManager[1191]: <info> [1467622732.2940]
connectivity: check for uri
'http://fedoraproject.org/static/hotspot.txt' failed with 'Error al
resolver «fedoraproject.org»: Name or service not known'
jul 04 10:58:52 xenon NetworkManager[1191]: <info> [1467622732.6142]
manager: NetworkManager state is now CONNECTED_GLOBAL
[root@xenon ~]# systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled;
vendor preset: disabled)
Active: inactive (dead)
[root@xenon ~]# journalctl -b -u NetworkManager-wait-online.service
-- No entries --
--
Juan Orti
https://apuntesderootblog.wordpress.com/
7 years, 11 months
bluetooth applet
by Frank Elsner
Hi,
today I discovered that I can't enable bluetooth via the Blueman Applet.
When I click on "Turn Bluetooth On" nothing happend.
What might be the reason?
I should note that I upgraded the Fedora 23 before I discoverd
the problem.
--Frank Elsner
7 years, 11 months
