> Just because I am out of ideas at the moment could you try disabling
> IPv6 to see if that helps? You can do it without rebooting by (as root)
>
> echo 1 > /proc/sys/net/ipv6/conf/(name of interface)/disable_ipv6
> And then see if this makes any difference.
in fact, some time ago, I contacted m
> nss doesn't have a test client that I'm aware of, but since you're having
> trouble with an OpenSSL application, you might be able to get more
> information by using the "s_client" app:
>
> openssl s_client -connect docs.python.org:443
First try and apprently maybe a first error (write:errno=104
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 tho
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 w
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 y
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 cl
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
> s
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
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 -- u
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 (aft
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
___
On 04/10/17 11:50, Stephen Davies wrote:
> Yes. It is KDE.
>
> There is no entry for Networks in the Entries list.
Interesting
What do you get for
rpm -qa | grep plasma-nm
--
Fedora Users List - The place to go to get others to do the work for you
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 here
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 li
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?
__
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 othe
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 s
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 L
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 sh
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
non-graphica
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
hopeful
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
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
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 way.
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 left looking at a "froz
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 that in some cases I was seeing a
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
>> do
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 sup
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 pac
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 complete STDERR from t
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 FirePro
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 I
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) IPv
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:
Ver
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 user_foo@1.
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 place
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 te
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 e
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 /de
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 happe
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 "
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
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 th
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 secto
44 matches
Mail list logo
