Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Tim
Allegedly, on or about 10 April 2017, Stephen Morris sent: > am I correct in understanding that you are saying that even > though I have IPv6 set to link-local, that IPv6 is still being > attempted across the internet gateway, and in my case because my ISP > doesn't support IPv6, I am assuming

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Stephen Davies
On 10/04/17 14:26, Ed Greshko wrote: On 04/10/17 12:47, Stephen Davies wrote: That's what I guessed but clicking the left box does nothing and it stays unchecked. Hummm. If you don't have rfkill installed, install it. And then rfkill list wifi Thank you yet again! rfkill list

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Ed Greshko
On 04/10/17 12:47, Stephen Davies wrote: > That's what I guessed but clicking the left box does nothing and it > stays unchecked. Hummm. If you don't have rfkill installed, install it. And then rfkill list wifi -- Fedora Users List - The place to go to get others to do the work for

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Stephen Davies
On 10/04/17 14:15, Ed Greshko wrote: On 04/10/17 12:36, Stephen Davies wrote: I was checking out the restored network manager and somehow managed to disable all wireless interfaces. I'm guessing that it is one of the little squares at the top beside a wireless icon and a flight mode icon but

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Ed Greshko
On 04/10/17 12:36, Stephen Davies wrote: > I was checking out the restored network manager and somehow managed to > disable all wireless interfaces. > > I'm guessing that it is one of the little squares at the top beside a > wireless icon and a flight mode icon but clicking the left hand square >

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Stephen Davies
On 10/04/17 13:40, Stephen Davies wrote: On 10/04/17 13:30, Ed Greshko wrote: On 04/10/17 11:50, Stephen Davies wrote: Yes. It is KDE. There is no entry for Networks in the Entries list. Oh, and is "Networks" checked in the "Extra Items" list in the General section? You got it again. I

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Ed Greshko
On 04/10/17 12:10, Stephen Davies wrote: > Hopefully that is the end of my F25 upgrade woes. Fingers crossed. :-) > > Cheers and thanks, Welcome -- Fedora Users List - The place to go to get others to do the work for you ___ users mailing list --

Re: No Network Manager in task bar after upgrade to F25 (solved)

2017-04-09 Thread Stephen Davies
On 10/04/17 13:30, Ed Greshko wrote: On 04/10/17 11:50, Stephen Davies wrote: Yes. It is KDE. There is no entry for Networks in the Entries list. Oh, and is "Networks" checked in the "Extra Items" list in the General section? You got it again. I installed plasma-nm and all came good

Re: No Network Manager in task bar after upgrade to F25

2017-04-09 Thread Ed Greshko
On 04/10/17 11:50, Stephen Davies wrote: > Yes. It is KDE. > > There is no entry for Networks in the Entries list. Oh, and is "Networks" checked in the "Extra Items" list in the General section? -- Fedora Users List - The place to go to get others to do the work for you

Re: No Network Manager in task bar after upgrade to F25

2017-04-09 Thread Stephen Davies
On 10/04/17 13:15, Ed Greshko wrote: On 04/10/17 11:35, Stephen Davies wrote: With no network icon in the task bar, I eventually got my ethernet and wireless connections working again using nm-connection-editor but would prefer to get the icon interface back too. I think we're talking KDE

Re: No Network Manager in task bar after upgrade to F25

2017-04-09 Thread Ed Greshko
On 04/10/17 11:35, Stephen Davies wrote: > With no network icon in the task bar, I eventually got my ethernet and > wireless connections working again using nm-connection-editor but > would prefer to get the icon interface back too. I think we're talking KDE here. If so Right click on the

No Network Manager in task bar after upgrade to F25

2017-04-09 Thread Stephen Davies
With no network icon in the task bar, I eventually got my ethernet and wireless connections working again using nm-connection-editor but would prefer to get the icon interface back too. If/when I get that back, does it include the connection status notifications?

Re: No X after booting F25

2017-04-09 Thread Ed Greshko
On 04/10/17 11:09, Stephen Davies wrote: > That did the trick thank you. Good... > > Any idea how this bit got lost in the upgrade? I've heard of this happening when desktop is KDE and the previous version was using kdm as the display manager. -- Fedora Users List - The place to go to get

Re: No X after booting F25

2017-04-09 Thread Stephen Davies
On 10/04/17 12:27, Ed Greshko wrote: On 04/10/17 10:42, Stephen Davies wrote: 2. No. display-manager.service does not exist below /etc/systemd or /usr/lib/systemd Then systemctl --force enable whatdmyouwant.service e.g. systemctl --force disable gdm.service systemctl --force disable

Re: No X after booting F25

2017-04-09 Thread Ed Greshko
On 04/10/17 10:42, Stephen Davies wrote: > 2. No. display-manager.service does not exist below /etc/systemd or > /usr/lib/systemd Then systemctl --force enable whatdmyouwant.service e.g. systemctl --force disable gdm.service systemctl --force disable sddm.service -- Fedora Users

Re: ssh stderr question

2017-04-09 Thread Samuel Sieb
On 04/09/2017 07:25 PM, JD wrote: On 04/09/2017 06:02 PM, Samuel Sieb wrote: ssh user_foo@1.2.3.4 "pgrep -f 'master_app' | wc -l" 2> stderr.log would write any errors to the file "stderr.log" on the local box. Those stderr messages would be coming from wc and NOT from ssh. The OP's command

Re: No X after booting F25

2017-04-09 Thread Stephen Davies
On 10/04/17 11:25, Ed Greshko wrote: On 04/10/17 09:46, Stephen Davies wrote: Since upgrading to F25, I no longer get a graphical login page. I have run systemctl set-default graphical.target and runlevel5.target and default.target both point to graphical.target but I still get the

Re: ssh stderr question

2017-04-09 Thread JD
On 04/09/2017 06:02 PM, Samuel Sieb wrote: On 04/09/2017 04:34 PM, bruce wrote: the cmd -->> ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l works, as it runs the pgrep 'xxx' | wc -l all on the remote box.. Actually, it doesn't. The "wc -l" will be run on the local box, but

Re: No X after booting F25

2017-04-09 Thread Ed Greshko
On 04/10/17 09:46, Stephen Davies wrote: > Since upgrading to F25, I no longer get a graphical login page. > > I have run systemctl set-default graphical.target and runlevel5.target > and default.target both point to graphical.target but I still get the > non-graphical login. Two questions come

No X after booting F25

2017-04-09 Thread Stephen Davies
Since upgrading to F25, I no longer get a graphical login page. I have run systemctl set-default graphical.target and runlevel5.target and default.target both point to graphical.target but I still get the non-graphical login. ___ users mailing list

Re: ssh stderr question

2017-04-09 Thread Samuel Sieb
On 04/09/2017 04:34 PM, bruce wrote: the cmd -->> ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l works, as it runs the pgrep 'xxx' | wc -l all on the remote box.. Actually, it doesn't. The "wc -l" will be run on the local box, but hopefully you're getting the same result either

Re: Cannot chvt away from X (with radeon driver)

2017-04-09 Thread stan
On Sun, 9 Apr 2017 16:50:44 -0500 Ian Pilcher wrote: > I'm not sure when this started, but I am unable to switch away from my > X VT (usually VT 1) to a text VT. > > Actually, blind-typing shows that I am actually able to switch to the > text VT, but nothing shows up; I'm

Re: ssh stderr question

2017-04-09 Thread bruce
On Sun, Apr 9, 2017 at 6:23 PM, Cameron Simpson wrote: > On 09Apr2017 13:57, Samuel Sieb wrote: >> >> On 04/09/2017 07:23 AM, bruce wrote: >>> >>> the following test works.. >>> >>> ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l >>> >>> however, i realized

Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Ed Greshko
On 04/10/17 06:39, Ed Greshko wrote: > On 04/10/17 05:33, Stephen Morris wrote: >> Thanks Rick, am I correct in understanding that you are saying that >> even though I have IPv6 set to link-local, that IPv6 is still being >> attempted across the internet gateway, and in my case because my ISP >>

Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Ed Greshko
On 04/10/17 05:27, Stephen Morris wrote: > If I use your suggestion to disable IPv6, that was in the thread for > the person that is having trouble accessing sites with Firefox, will > that cause the IPv6 not ready messages to start appearing in the boot > log again? No. If you disable IPv6

Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Ed Greshko
On 04/10/17 05:33, Stephen Morris wrote: > Thanks Rick, am I correct in understanding that you are saying that > even though I have IPv6 set to link-local, that IPv6 is still being > attempted across the internet gateway, and in my case because my ISP > doesn't support IPv6, I am assuming those

Re: ssh stderr question

2017-04-09 Thread Cameron Simpson
On 09Apr2017 13:57, Samuel Sieb wrote: On 04/09/2017 07:23 AM, bruce wrote: the following test works.. ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l however, i realized that in some cases I was seeing a "ssh connection timeout" so I looked into how to capture the

Cannot chvt away from X (with radeon driver)

2017-04-09 Thread Ian Pilcher
I'm not sure when this started, but I am unable to switch away from my X VT (usually VT 1) to a text VT. Actually, blind-typing shows that I am actually able to switch to the text VT, but nothing shows up; I'm left looking at a "frozen" version of the X VT contents. I am using an AMD/ATI

Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Stephen Morris
On 4/7/17 10:17 AM, Rick Stevens wrote: On 04/06/2017 02:45 PM, Stephen Morris wrote: On 4/6/17 9:20 AM, Ed Greshko wrote: On 04/06/17 06:57, Stephen Morris wrote: Hi Ed, just as a side issue to this, because my ISP (I don't know about my VPN provider) IPv6 at all for anything, I was setting

Re: Is there a way to stop ipv6 leakage without turning off ipv6?

2017-04-09 Thread Stephen Morris
On 4/7/17 10:29 AM, Ed Greshko wrote: On 04/07/17 08:17, Rick Stevens wrote: On 04/06/2017 02:45 PM, Stephen Morris wrote: On 4/6/17 9:20 AM, Ed Greshko wrote: On 04/06/17 06:57, Stephen Morris wrote: Hi Ed, just as a side issue to this, because my ISP (I don't know about my VPN provider)

Re: [F25] issue with SSL connexions: Failure of SSL transaction with

2017-04-09 Thread Stephen Morris
On 4/7/17 3:39 PM, Ed Greshko wrote: On 04/07/17 12:32, Frédéric Bron wrote: gnutls has this on its web page: Support for TLS 1.2, TLS 1.1, TLS 1.0, and SSL 3.0 protocols I have Name: gnutls Version : 3.5.10 Release : 1.fc25 installed. Do you have gnutls installed? gnutls:

Re: ssh stderr question

2017-04-09 Thread Samuel Sieb
On 04/09/2017 07:23 AM, bruce wrote: hey... the following test works.. ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l however, i realized that in some cases I was seeing a "ssh connection timeout" so I looked into how to capture the complete STDERR from the local side. ssh

Re: strange log message

2017-04-09 Thread Ed Greshko
On 04/09/17 23:27, François Patte wrote: >> Are you wanting to recover some data from the drives? > No, they perfectly work! If you don't want to recover any data then why not just unmount them. re-partition, and create new file systems on the drives as needed? -- Fedora Users List - The

rsyslog logging kernel errors to /dev/console even after config change (was mcelog error output going to all open terminals)

2017-04-09 Thread ProPAAS DBA
Hi all; Fedora 25 - KDE spin on a thinkpad x1 carbon 4th gen - Getting kernel errors to all screens I changed this line in /etc/rsyslog.conf #kern.* /dev/console to this: kern.* /var/log/messages but kernel messages are still going to all

Re: mcelog error output going to all open terminals

2017-04-09 Thread ProPAAS DBA
It turns out this is syslogd doing this, not mce. anyone know how to disable this behavior? I tried "dmesg -n 1" but no change On 04/09/2017 09:03 AM, ProPAAS DBA wrote: Hi all; I've been seeing mcelog errors since a few updates back. After much, much digging it seems that the mcelog

Re: strange log message

2017-04-09 Thread François Patte
Le 09/04/2017 à 15:47, Ed Greshko a écrit : > On 04/09/17 17:28, François Patte wrote: >> logwatch send a strange warning: >> >> WARNING: Device /dev/md1 has size of 0 sectors which is smaller than >> corresponding PV size of 976508928 sectors. Was device resized?: 1 Time(s) >> WARNING: Device

mcelog error output going to all open terminals

2017-04-09 Thread ProPAAS DBA
Hi all; I've been seeing mcelog errors since a few updates back. After much, much digging it seems that the mcelog errors are due to spikes in cpu temperature. I have a Thinkpad x1 Carbon 4th generation running Fedora 25 - KDE I get why I'm seeing the cpu temp spikes since it usually

ssh stderr question

2017-04-09 Thread bruce
hey... the following test works.. ssh user_foo@1.2.3.4 pgrep -f 'master_app' | wc -l however, i realized that in some cases I was seeing a "ssh connection timeout" so I looked into how to capture the complete STDERR from the local side. ssh user_foo@1.2.3.4 "pgrep -f 'master_app' | wc -l

Re: strange log message

2017-04-09 Thread Ed Greshko
On 04/09/17 17:28, François Patte wrote: > logwatch send a strange warning: > > WARNING: Device /dev/md1 has size of 0 sectors which is smaller than > corresponding PV size of 976508928 sectors. Was device resized?: 1 Time(s) > WARNING: Device /dev/md11 has size of 0 sectors which is smaller than

Re: strange log message

2017-04-09 Thread John Pilkington
On 09/04/17 10:28, François Patte wrote: Bonjour, logwatch send a strange warning: WARNING: Device /dev/md1 has size of 0 sectors which is smaller than corresponding PV size of 976508928 sectors. Was device resized?: 1 Time(s) WARNING: Device /dev/md11 has size of 0 sectors which is smaller

strange log message

2017-04-09 Thread François Patte
Bonjour, logwatch send a strange warning: WARNING: Device /dev/md1 has size of 0 sectors which is smaller than corresponding PV size of 976508928 sectors. Was device resized?: 1 Time(s) WARNING: Device /dev/md11 has size of 0 sectors which is smaller than corresponding PV size of 104346496