Prompt shows wrong version -
. This is an updated Fedora 29 beta however the prompt indicates 28: [bobg@Box83-F28-workstation ~]$ uname -a Linux Box83-F28-workstation 4.18.17-300.fc29.x86_64 #1 SMP Mon Nov 5 17:56:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux What do I need to do, simply change the prompt? Bob -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-29/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On Mon, 2018-11-12 at 20:39 -0800, Samuel Sieb wrote: > On 11/6/18 1:43 PM, Stephen Morris wrote: > > When I start one of the two vpn definitions, that have been in > > networkmanager for years and used to work fine (I haven't used them in > > quite a while), it starts and I get a pop-up message saying that > > interface tun0 has been activated in the firewall default zone (being > > fedoraworkstation). This interface remains active for about a minute or > > so until I get the pop-up message that interface tun0 has been > > deactivated in the firewall default zone, and the vpn is no longer > > connected. The vpn connection is using Openvpn. > > > > I have checked dmesg for any message relative to tun0 or firewall > > and there are no messages for either. How do I determine why the vpn > > won't stay active? > > Run "sudo journalctl -b -t openvpn" to find all the journal entries. Slightly OT, but '-t' requires a SYSLOG_IDENTIFIER as argument. However the man page for journalctl doesn't specify what that means. It's clearly not just a substring (you can get that with '-g') so what exactly is it? poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Prompt shows wrong version -
On 11/13/18 6:20 PM, Bob Goodwin wrote: > . > This is an updated Fedora 29 beta however the prompt indicates 28: > > [bobg@Box83-F28-workstation ~]$ uname -a > Linux Box83-F28-workstation 4.18.17-300.fc29.x86_64 #1 SMP Mon Nov 5 17:56:16 > UTC 2018 > x86_64 x86_64 x86_64 GNU/Linux > > What do I need to do, simply change the prompt? > > Bob > The prompt is your system's hostname. Run sudo hostnamectl set-hostname NAME to change -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Prompt shows wrong version -
On 11/13/18 05:33, Ed Greshko wrote: Run sudo hostnamectl set-hostname NAME to change . Ok, I will do that. I thought perhaps it was an indication of something else that needed to be done when starting with a beta installation. It was anew installation from Fedora29 Live on a clean hard drive so the F28 designation came with the install and I just ignored it until this morning. Thanks, Bob -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD box10 FEDORA-29/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Prompt shows wrong version -
On 11/13/18 6:48 PM, Bob Goodwin wrote: > On 11/13/18 05:33, Ed Greshko wrote: >> Run >> >> sudo hostnamectl set-hostname NAME >> >> to change > . > Ok, I will do that. I thought perhaps it was an indication of something else > that needed > to be done when starting with a beta installation. It was anew installation > from > Fedora29 Live on a clean hard drive so the F28 designation came with the > install and I > just ignored it until this morning. Thanks, > > Welcome. FYI, [bobg@Box83-F28-workstation ~], is the bash prompt whose format is defined by the environment variable PS1. Unless you change it, the system defines it as [egreshko@meimei ~]$ echo $PS1 [\u@\h \W]\$ \u = the user @ a symbol \h = your hostname " " a space \W = current working directory -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 11/13/18 12:39 PM, Samuel Sieb wrote: > On 11/6/18 1:43 PM, Stephen Morris wrote: >> When I start one of the two vpn definitions, that have been in >> networkmanager for >> years and used to work fine (I haven't used them in quite a while), it >> starts and I get >> a pop-up message saying that interface tun0 has been activated in the >> firewall default >> zone (being fedoraworkstation). This interface remains active for about a >> minute or so >> until I get the pop-up message that interface tun0 has been deactivated in >> the firewall >> default zone, and the vpn is no longer connected. The vpn connection is >> using Openvpn. >> >> I have checked dmesg for any message relative to tun0 or firewall and >> there are no >> messages for either. How do I determine why the vpn won't stay active? > > Run "sudo journalctl -b -t openvpn" to find all the journal entries. That would actually be journalctl -b -t nm-openvpn -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Slow gnome-shell, gnome-files
Hi, after installing the new Fedora 29 with Gnome 3.30 there is one really annoying thing. Gnome-shell or gnome-files becomes extremely slow. Nautilus used to load within one second (I use SSDs), the list of folders and files appeared immediately. Also, when I would save attachments from within Evolution, the dialogue appeared immediately. Now, Nautilus still launches fast, but it takes a moment for the list of folders and files to load. If I want to save attachments from within Evolution, the third such operation in a row slows down the whole system. I don't see in the save dialogue for some minutes anything. Than folders and files (if there are any) appear slowly and the path gets visible. Did someone else observe this? Thanks in advance Tibor -- Tibor Anca I use OpenSource! signature.asc Description: This is a digitally signed message part ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 11/13/18 3:07 AM, Ed Greshko wrote: On 11/13/18 12:39 PM, Samuel Sieb wrote: Run "sudo journalctl -b -t openvpn" to find all the journal entries. That would actually be journalctl -b -t nm-openvpn Thank you. I've been running the openvpn client directly from the command line, so what I wrote works for me. But I see it might be different if run from NetworkManager. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Network Manager not Retaining Wifi Password
On 13/11/18 8:13 am, Ed Greshko wrote: On 11/13/18 4:56 AM, Stephen Morris wrote: On 7/11/18 8:26 am, Stephen Morris wrote: On 1/10/18 7:35 am, Stephen Morris wrote: On 29/9/18 1:25 am, Ed Greshko wrote: On 9/28/18 11:49 AM, Stephen Morris wrote: I switched my wife definition in networkmanager back to "Store password for this user only (encrypted)" and that put a uuid entry into the maps area, while I was watching, that matched the uuid in the ifcfg file with my wifi password. Having rebooted the issue has now been resolved. Good to know that the issue has been resolved. I really hope it wasn't due to switching your "wife definition". :-) I don't think it was switching the wifi definition. The encrypted definition is what I have always used, but it stopped working when I changed the wifi router and adapter and the kernel wouldn't load the adapter driver because of the compile options I used. Thankyou for all your help. regards, Steve Having just revisited this issue after rectifying the issue with my wifi definition, it has resurfaced again with my two vpn definitions. The two vpn definitions don't have the password recorded even though I have specified it in the past. If I bring up knetworkmanager5 and look in there the password is there, and if I transfer it into the vpn definition in networkmanager and 'apply' it, select 'ok' to exit the edit process, and then re-edit the definition, the password is not there (this is the same issue I originally had with the wifi definition), and then when I connect to the definition I am prompted for the vpn password (I don't get prompted for the kwallet password as I have pam-kwallet installed). Do I need to change the definition from 'save password encrypted' to 'save not encrypted' to get the appropriate file created with the password, and then change it back to 'save password encrypted' to get the password retained (as worked with the wifi password issue)? If so, why is networkmanager now working like this? This is indeed what I had to do to get networkmanager to retain the passwords. I had to change the password setting to all users to build a config file with the password in plain text, then switch it back to the current user mode to get it encrypted again and the password saved in the definition, is this a bug in Networkmanager functionality? Well, I've not had any of the issues you're seeing. So, if there is a problem with NM it must be due to something triggering it on your system. It's possible it is environmental, but if it is how do I identify what is causing it given that this was not always the functionality with nm on my system, and from my perspective it surfaced on a cold boot after putting on system maintenance. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Link-Local Only option not available on NetworkManager
On 9/11/18 9:47 am, Ed Greshko wrote: On 11/9/18 4:03 AM, Rick Stevens wrote: On 11/8/18 11:38 AM, Ed Greshko wrote: On 11/9/18 3:12 AM, Rick Stevens wrote: That oughta do it. And no, the GUI doesn't offer this setting that I can find. Interesting. I don't have a Gnome system up at 03:30 but KDE has that option available. I'm on Xfce and nm-connection-editor doesn't seem to show it. If we are talking about the VPN configuration GUI. (I don't use L2TP) On Xfce there is no IPv6 Tab during creation. But, once created there is, and Link-local Only isn't an option. On KDE there is no IPv6 Tab on creation or after creation. For me, in KDE, in the networkmanager app that sits in the system tray to show the network connection, when I enter into edit mode, irrespective of whether I am editing an existing definition or creating a new definition there is both an IPv4 and IPv6 tab in the definition. I used to have the IPv6 tab set to link-local as my isp didn't support IPv6, but that seems to not be an issue any more so I have that now set to automatic. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Network Manager not Retaining Wifi Password
On 11/14/18 5:03 AM, Stephen Morris wrote: > It's possible it is environmental, but if it is how do I identify what is > causing it > given that this was not always the functionality with nm on my system, and > from my > perspective it surfaced on a cold boot after putting on system maintenance. Well, the first thing I would do is to create a new user account and see if that account acts the same as the one you are using now. That should narrow it down to user space or system wide. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: grub menu
On 13/11/18 9:42 am, Tom Horsley wrote: On Tue, 13 Nov 2018 07:30:05 +1100 Stephen Morris wrote: I would be questioning where that timeout code in grub.cfg came from Brand new in fedora 29 (possibly only if you install from scratch, not upgrade). Maybe that's new functionality in F29, I'm still on F28. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Link-Local Only option not available on NetworkManager
On 11/14/18 5:13 AM, Stephen Morris wrote: > On 9/11/18 9:47 am, Ed Greshko wrote: >> On 11/9/18 4:03 AM, Rick Stevens wrote: >>> On 11/8/18 11:38 AM, Ed Greshko wrote: On 11/9/18 3:12 AM, Rick Stevens wrote: > That oughta do it. And no, the GUI doesn't offer this setting that I can > find. Interesting. I don't have a Gnome system up at 03:30 but KDE has that option available. >>> I'm on Xfce and nm-connection-editor doesn't seem to show it. >> If we are talking about the VPN configuration GUI. (I don't use L2TP) >> >> On Xfce there is no IPv6 Tab during creation. But, once created there is, >> and Link-local >> Only isn't an option. >> >> On KDE there is no IPv6 Tab on creation or after creation. >> > For me, in KDE, in the networkmanager app that sits in the system tray to > show the > network connection, when I enter into edit mode, irrespective of whether I am > editing an > existing definition or creating a new definition there is both an IPv4 and > IPv6 tab in > the definition. I used to have the IPv6 tab set to link-local as my isp > didn't support > IPv6, but that seems to not be an issue any more so I have that now set to > automatic. > This is in an L2TP VPN add connection/edit connection? -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: grub menu
On 11/13/18 1:17 PM, Stephen Morris wrote: On 13/11/18 9:42 am, Tom Horsley wrote: On Tue, 13 Nov 2018 07:30:05 +1100 Stephen Morris wrote: I would be questioning where that timeout code in grub.cfg came from Brand new in fedora 29 (possibly only if you install from scratch, not upgrade). Maybe that's new functionality in F29, I'm still on F28. It's an F29 feature: https://fedoraproject.org/wiki/Changes/HiddenGrubMenu ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 13/11/18 8:52 am, Ed Greshko wrote: On 11/13/18 4:49 AM, Stephen Morris wrote: So given all this, when searching journalctl for boot messages across particular datetime ranges, how do you find them when the timestamps in the journals are blatantly wrong, potentially up until the desktop loads? I don't know. I've not had this sort of problem since years ago when my HW clock was not set to GMT/UTC. FWIW, [root@meimei ~]# date ; hwclock ; uptime Tue Nov 13 05:47:36 CST 2018 2018-11-13 05:47:28.405437+08:00 05:47:36 up 3 days So, you can see my HW clock is running a bit slow. The hwclock command always shows time as local. (see the man page) But if I reboot and go into the BIOS it will show 2018-11-12 21:47... My hardware clock is running a couple of seconds slow as well. Just as a matter of curiosity, when you say if you issue hwclock from the bios (how have you done that) what does journalctl show for the same time? Does it show, using your example, 2018-11-12 21:47 or does it show 2018-11-13 21:47? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 14/11/18 4:36 am, Samuel Sieb wrote: On 11/13/18 3:07 AM, Ed Greshko wrote: On 11/13/18 12:39 PM, Samuel Sieb wrote: Run "sudo journalctl -b -t openvpn" to find all the journal entries. That would actually be journalctl -b -t nm-openvpn Thank you. I've been running the openvpn client directly from the command line, so what I wrote works for me. But I see it might be different if run from NetworkManager. Thankyou. I issued the command and got the following output but I'm not sure what it means. -- Logs begin at Wed 2016-01-06 07:29:31 AEDT, end at Wed 2018-11-14 08:36:39 AEDT. -- Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: OpenVPN 2.4.6 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: library versions: OpenSSL 1.1.0i-fips 14 Aug 2018, LZO 2.08 Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: TCP/UDP: Preserving recently used remote address: [AF_INET]199.195.193.181:443 Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: UDP link local: (not bound) Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: UDP link remote: [AF_INET]199.195.193.181:443 Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1558', remote='link-mtu 1557' Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo' Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: [VPN] Peer Connection Initiated with [AF_INET]199.195.193.181:443 Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: TUN/TAP device tun0 opened Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 3872 --bus-name org.freedesktop.NetworkManager.openvpn.Conn> Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: GID set to nm-openvpn Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: UID set to nm-openvpn Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: Initialization Sequence Completed Nov 14 08:34:06 localhost.localdomain nm-openvpn[3877]: Bad LZO decompression header byte: 42 Nov 14 08:34:14 localhost.localdomain nm-openvpn[3877]: [VPN] Inactivity timeout (--ping-restart), restarting Nov 14 08:34:14 localhost.localdomain nm-openvpn[3877]: SIGUSR1[soft,ping-restart] received, process restarting Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: TCP/UDP: Preserving recently used remote address: [AF_INET]199.195.193.181:443 Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: UDP link local: (not bound) Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: UDP link remote: [AF_INET]199.195.193.181:443 Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1558', remote='link-mtu 1557' Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo' Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: [VPN] Peer Connection Initiated with [AF_INET]199.195.193.181:443 Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: Preserving previous TUN/TAP instance: tun0 Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 3872 --bus-name org.freedesktop.NetworkManager.openvpn.Conn> Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: NOTE: Pulled options changed on restart, will need to close and reopen TUN/TAP device. Nov 14 08:34:22 localhost.localdomain nm-openvpn[3877]: ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1) regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedor
Re: Network Manager not Retaining Wifi Password
On 14/11/18 8:14 am, Ed Greshko wrote: On 11/14/18 5:03 AM, Stephen Morris wrote: It's possible it is environmental, but if it is how do I identify what is causing it given that this was not always the functionality with nm on my system, and from my perspective it surfaced on a cold boot after putting on system maintenance. Well, the first thing I would do is to create a new user account and see if that account acts the same as the one you are using now. That should narrow it down to user space or system wide. Thanks Ed, I'll try that. I've also got some existing accounts created for my children that haven't been used for at least 3 years, so I'll try one of those too. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 11/14/18 5:32 AM, Stephen Morris wrote: > My hardware clock is running a couple of seconds slow as well. > > Just as a matter of curiosity, when you say if you issue hwclock from the > bios (how have > you done that) what does journalctl show for the same time? Does it show, > using your > example, 2018-11-12 21:47 or does it show 2018-11-13 21:47? I did not say what you think I said. I said, "But if I reboot and go into the BIOS it will show 2018-11-12 21:47", which I thought was clear. To expound. I reboot, enter F2 when the Boot (not grub) splash screen comes up and enter the BIOS setup of the motherboard. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 11/14/18 5:43 AM, Stephen Morris wrote: > On 14/11/18 4:36 am, Samuel Sieb wrote: >> On 11/13/18 3:07 AM, Ed Greshko wrote: >>> On 11/13/18 12:39 PM, Samuel Sieb wrote: Run "sudo journalctl -b -t openvpn" to find all the journal entries. >>> >>> That would actually be >>> >>> journalctl -b -t nm-openvpn >> >> Thank you. I've been running the openvpn client directly from the command >> line, so >> what I wrote works for me. But I see it might be different if run from >> NetworkManager. > > Thankyou. I issued the command and got the following output but I'm not sure > what it means. > > > -- Logs begin at Wed 2016-01-06 07:29:31 AEDT, end at Wed 2018-11-14 08:36:39 > AEDT. -- > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: OpenVPN 2.4.6 > x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] > [MH/PKTINFO] [AEAD] > built on Apr > > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: library versions: > OpenSSL > 1.1.0i-fips 14 Aug 2018, LZO 2.08 > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: NOTE: the current > --script-security setting may allow this configuration to call user-defined > scripts > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: TCP/UDP: Preserving > recently > used remote address: [AF_INET]199.195.193.181:443 > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: UDP link local: (not > bound) > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: UDP link remote: > [AF_INET]199.195.193.181:443 > Nov 14 08:33:42 localhost.localdomain nm-openvpn[3877]: NOTE: UID/GID > downgrade will be > delayed because of --client, --pull, or --up-delay > Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'link-mtu' > is used > inconsistently, local='link-mtu 1558', remote='link-mtu 1557' > Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'comp-lzo' > is present > in local config but missing in remote config, local='comp-lzo' > Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: [VPN] Peer Connection > Initiated > with [AF_INET]199.195.193.181:443 > Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: TUN/TAP device tun0 > opened > Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: > /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 3872 --bus-name > org.freedesktop.NetworkManager.openvpn.Conn> > Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: GID set to nm-openvpn > Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: UID set to nm-openvpn > Nov 14 08:33:44 localhost.localdomain nm-openvpn[3877]: Initialization > Sequence Completed > Nov 14 08:34:06 localhost.localdomain nm-openvpn[3877]: Bad LZO decompression > header > byte: 42 > Nov 14 08:34:14 localhost.localdomain nm-openvpn[3877]: [VPN] Inactivity > timeout > (--ping-restart), restarting > Nov 14 08:34:14 localhost.localdomain nm-openvpn[3877]: > SIGUSR1[soft,ping-restart] > received, process restarting > Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: NOTE: the current > --script-security setting may allow this configuration to call user-defined > scripts > Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: TCP/UDP: Preserving > recently > used remote address: [AF_INET]199.195.193.181:443 > Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: UDP link local: (not > bound) > Nov 14 08:34:19 localhost.localdomain nm-openvpn[3877]: UDP link remote: > [AF_INET]199.195.193.181:443 > Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: WARNING: 'link-mtu' > is used > inconsistently, local='link-mtu 1558', remote='link-mtu 1557' > Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: WARNING: 'comp-lzo' > is present > in local config but missing in remote config, local='comp-lzo' > Nov 14 08:34:20 localhost.localdomain nm-openvpn[3877]: [VPN] Peer Connection > Initiated > with [AF_INET]199.195.193.181:443 > Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: Preserving previous > TUN/TAP > instance: tun0 > Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: > /usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 3872 --bus-name > org.freedesktop.NetworkManager.openvpn.Conn> > Nov 14 08:34:21 localhost.localdomain nm-openvpn[3877]: NOTE: Pulled options > changed on > restart, will need to close and reopen TUN/TAP device. > Nov 14 08:34:22 localhost.localdomain nm-openvpn[3877]: ERROR: Cannot ioctl > TUNSETIFF > tun: Operation not permitted (errno=1) > > Sorry for not mentioning this before. But I would actually use journalctl -b -t nm-dispatcher -t nm-openvpn Anyway, just looking at the above, I would edit my openvpn connection and under "Advanced" I would set "Use LZO compression to "No" as well as unchecking the box. -- Fedora Users - The place to go to beat OT dead horses :-) :-) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Con
[Resolved]: How do I Systemd Disable Userspace Service no Longer Needed?
On 13/11/18 3:43 pm, Samuel Sieb wrote: On 11/12/18 1:37 PM, Stephen Morris wrote: sudo systemctl disable openrazer-daemon.service --user Failed to connect to bus: No such file or directory It's a user service, so don't use "sudo". Given the above how do I stop systemd from trying to start the unneeded service? The previous command should work without the sudo. Thankyou to everyone who helped with this, issuing the systemctl user space command without sudo did remove the service. This also highlights that when I was looking manually for the service file I overlooked /usr/lib/systemd/user. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: VPN Interface not Remaining Active With Firewall?
On 11/13/18 1:43 PM, Stephen Morris wrote: Thankyou. I issued the command and got the following output but I'm not sure what it means. Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1558', remote='link-mtu 1557' Nov 14 08:33:43 localhost.localdomain nm-openvpn[3877]: WARNING: 'comp-lzo' is present in local config but missing in remote config, local='comp-lzo' You have different options set for the client than the server is expecting. Nov 14 08:34:06 localhost.localdomain nm-openvpn[3877]: Bad LZO decompression header byte: 42 Causing this. They probably can't communicate at all. Nov 14 08:34:14 localhost.localdomain nm-openvpn[3877]: [VPN] Inactivity timeout (--ping-restart), restarting You seem to have a very short timeout. Where did you get your settings from? Maybe you need to find out what the server settings are again and recreate the VPN connection. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
