Open 07Excel opened 3 years ago
Thanks for the report @07Excel. As a part of our tests we check to make sure Ethernet connections survive the suspend/wake cycle. Would you mind giving us more information about your system including the make and model of your NIC? We could also use the output from 'journalctl' run sudo journalctl -r > journal.txt
in the terminal and attach it to this issue.
My Laptop: MSI-CX61-2PF My NIC card details, Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet & Network controller: Realtek Semiconductor Co., Ltd. RTL8723AE PCIe Wireless Network Adapter Journalctl output is attached below...
On Wed, Jul 21, 2021 at 8:34 PM Ben Flanagin @.***> wrote:
Thanks for the report @07Excel https://github.com/07Excel. As a part of our tests we check to make sure Ethernet connections survive the suspend/wake cycle. Would you mind giving us more information about your system including the make and model of your NIC? We could also use the output from 'journalctl' run sudo journalctl -r > journal.txt in the terminal and attach it to this issue.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/1827#issuecomment-884251029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHA7XWA6UDBK24PECNC2HTTY3NAPANCNFSM5AXVQZ2A .
-- Journal begins at Wed 2021-07-21 18:02:18 +0545, ends at Wed 2021-07-21 20:58:53 +0545. --
Jul 21 20:58:53 pop-os sudo[20782]: pam_unix(sudo:session): session opened for user root by (uid=1000)
Jul 21 20:58:53 pop-os sudo[20782]: parash : TTY=pts/0 ; PWD=/home/parash ; USER=root ; COMMAND=/usr/bin/journalctl -r
Jul 21 20:58:53 pop-os sudo[20782]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Jul 21 20:58:52 pop-os systemd[1484]: Started Tracker metadata database store and lookup manager.
Jul 21 20:58:52 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.freedesktop.Tracker1'
Jul 21 20:58:52 pop-os systemd[1484]: Starting Tracker metadata database store and lookup manager...
Jul 21 20:58:52 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.3' (uid=1000 pid=1501 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Jul 21 20:58:50 pop-os sudo[20782]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
Jul 21 20:55:24 pop-os gnome-shell[2113]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x34000f8
Jul 21 20:55:22 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.gedit'
Jul 21 20:55:22 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating service name='org.gnome.gedit' requested by ':1.42' (uid=1000 pid=2113 comm="/usr/bin/gnome-shell " label="unconfined")
Jul 21 20:54:31 pop-os systemd[1484]: app-gnome-org.gnome.Terminal-20626.scope: Succeeded.
Jul 21 20:54:31 pop-os systemd[1484]: Started VTE child process 20642 launched by gnome-terminal-server process 20634.
Jul 21 20:54:31 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:54:31 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:54:31 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:54:31 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.317' (uid=1000 pid=20629 comm="/usr/bin/gnome-terminal.real --window " label="unconfined")
Jul 21 20:54:31 pop-os systemd[1484]: Started Application launched by gnome-shell.
Jul 21 20:53:13 pop-os gnome-keyring-daemon[1515]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Jul 21 20:53:11 pop-os gnome-shell[20324]: [20325:20325:0721/205311.511799:ERROR:sharing_service.cc(218)] Device registration failed with fatal error
Jul 21 20:53:11 pop-os gnome-shell[20324]: [20325:20325:0721/205311.003691:ERROR:profile_attributes_storage.cc(547)] Failed to PNG encode the image.
Jul 21 20:53:10 pop-os gnome-keyring-daemon[1515]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Jul 21 20:53:10 pop-os systemd[1484]: Started Application launched by gnome-shell.
Jul 21 20:51:27 pop-os systemd[1484]: gnome-terminal-server.service: Succeeded.
Jul 21 20:51:27 pop-os systemd[1484]: app-gnome-x\x2dterminal\x2demulator-20283.scope: Succeeded.
Jul 21 20:51:27 pop-os systemd[1484]: vte-spawn-47241737-937c-4d96-82d9-fd3f61a121dd.scope: Succeeded.
Jul 21 20:51:19 pop-os systemd[1484]: Started VTE child process 20299 launched by gnome-terminal-server process 20291.
Jul 21 20:51:19 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:51:19 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:51:19 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:51:19 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.311' (uid=1000 pid=20286 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jul 21 20:51:18 pop-os systemd[1484]: Started Application launched by gsd-media-keys.
Jul 21 20:46:03 pop-os systemd[1484]: gnome-terminal-server.service: Succeeded.
Jul 21 20:46:03 pop-os systemd[1484]: app-gnome-x\x2dterminal\x2demulator-20187.scope: Succeeded.
Jul 21 20:46:03 pop-os systemd[1484]: vte-spawn-26bad867-d8a0-4896-a177-1d0477a43eb1.scope: Succeeded.
Jul 21 20:45:32 pop-os systemd[1484]: Started VTE child process 20204 launched by gnome-terminal-server process 20195.
Jul 21 20:45:32 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:45:32 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:45:31 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:45:31 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.309' (uid=1000 pid=20190 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jul 21 20:45:31 pop-os systemd[1484]: Started Application launched by gsd-media-keys.
Jul 21 20:45:31 pop-os gnome-shell[2113]: Window manager warning: Overwriting existing binding of keysym 6f with keysym 6f (keycode 20).
Jul 21 20:42:08 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x480008e.
Jul 21 20:41:57 pop-os gnome-shell[2113]: Window manager warning: Overwriting existing binding of keysym 6f with keysym 6f (keycode 20).
Jul 21 20:40:03 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x4800086.
Jul 21 20:40:02 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x480007e.
Jul 21 20:37:50 pop-os systemd[1484]: gnome-terminal-server.service: Succeeded.
Jul 21 20:37:50 pop-os systemd[1484]: app-gnome-x\x2dterminal\x2demulator-20055.scope: Succeeded.
Jul 21 20:37:50 pop-os systemd[1484]: vte-spawn-86303b95-3a17-4513-8dd6-d39149d6e047.scope: Succeeded.
Jul 21 20:37:17 pop-os systemd[1484]: Started VTE child process 20071 launched by gnome-terminal-server process 20063.
Jul 21 20:37:16 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:37:16 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:37:16 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:37:16 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.307' (uid=1000 pid=20058 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jul 21 20:37:16 pop-os systemd[1484]: Started Application launched by gsd-media-keys.
Jul 21 20:30:36 pop-os systemd[1484]: flatpak-portal.service: Succeeded.
Jul 21 20:28:29 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x480006f.
Jul 21 20:28:28 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x4800067.
Jul 21 20:28:23 pop-os gnome-shell[2113]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x480000c specified for 0x480005f.
Jul 21 20:27:26 pop-os systemd[1484]: gnome-terminal-server.service: Succeeded.
Jul 21 20:27:26 pop-os systemd[1484]: app-gnome-x\x2dterminal\x2demulator-19958.scope: Succeeded.
Jul 21 20:27:26 pop-os systemd[1484]: vte-spawn-98271a14-3d55-4eb4-b697-178a33b44c50.scope: Succeeded.
Jul 21 20:27:20 pop-os systemd[1484]: Started VTE child process 19975 launched by gnome-terminal-server process 19966.
Jul 21 20:27:20 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:27:20 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:27:20 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:27:20 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.305' (uid=1000 pid=19961 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jul 21 20:27:20 pop-os systemd[1484]: Started Application launched by gsd-media-keys.
Jul 21 20:23:39 pop-os systemd[1484]: gnome-terminal-server.service: Succeeded.
Jul 21 20:23:39 pop-os systemd[1484]: app-gnome-x\x2dterminal\x2demulator-19887.scope: Succeeded.
Jul 21 20:23:39 pop-os systemd[1484]: vte-spawn-b3690dac-8b05-4523-a58b-45c8fa0e212e.scope: Succeeded.
Jul 21 20:23:29 pop-os systemd[1484]: Started VTE child process 19903 launched by gnome-terminal-server process 19895.
Jul 21 20:23:29 pop-os systemd[1484]: Started GNOME Terminal Server.
Jul 21 20:23:29 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Successfully activated service 'org.gnome.Terminal'
Jul 21 20:23:28 pop-os systemd[1484]: Starting GNOME Terminal Server...
Jul 21 20:23:28 pop-os dbus-daemon[1507]: [session uid=1000 pid=1507] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.302' (uid=1000 pid=19890 comm="/usr/bin/gnome-terminal.real --wait " label="unconfined")
Jul 21 20:23:28 pop-os systemd[1484]: Started Application launched by gsd-media-keys.
Jul 21 20:21:10 pop-os systemd[1]: fwupd.service: Succeeded.
Jul 21 20:20:36 pop-os systemd[1484]: app-flatpak-com.discordapp.Discord-19001.scope: Succeeded.
Jul 21 20:20:36 pop-os systemd[1484]: app-flatpak-com.discordapp.Discord-19037.scope: Succeeded.
Jul 21 20:20:29 pop-os systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jul 21 20:20:19 pop-os dbus-daemon[788]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 21 20:20:19 pop-os systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 21 20:20:19 pop-os dbus-daemon[788]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.15' (uid=0 pid=789 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jul 21 20:20:19 pop-os systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 21 20:20:19 pop-os NetworkManager[789]:
If this isn't a System76 computer, then this would typically be an issue that MSI or Qualcomm would need to fix in the upstream Linux kernel. Does this issue also occur in Ubuntu, or is it only in Pop?
Only in Pop, and no it is not a hardware problem lol. This problem was not there even in a weird riced-arch distro I used let alone ubuntu.
On Thu, Jul 22, 2021 at 8:20 PM Jacob Kauffmann @.***> wrote:
If this isn't a System76 computer, then this would typically be an issue that MSI or Qualcomm would need to fix in the upstream Linux kernel. Does this issue also occur in Ubuntu, or is it only in Pop?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/1827#issuecomment-884963681, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHA7XW4WLU7WE3QEU6S3A3TZAUERANCNFSM5AXVQZ2A .
This problem was not there even in a weird riced-arch distro I used let alone ubuntu.
I'm not sure what "riced-arch distro" is referring to, but can you please clarify if you've actually tried Ubuntu or if you tried another distribution such as Arch? If it was Ubuntu, which version was it? Pop!_OS is based on Ubuntu, and both Pop 20.04 and 21.04 are using the Ubuntu 21.04 kernel at this time, so Ubuntu 21.04 is what we would want to check in order to confirm if this is being caused by Pop!_OS patches or not.
System76 customers can reach out to support for technical assistance. For non-System76 hardware, you can seek community support on Reddit or Mattermost.
Just a shot in the dark, but would you happen to be using ProtonVPN? It seems they have a known bug where their ipv6 leak protection feature can cause DNS problems if the machine is shut down while connected to their VPN service. I'm pretty sure I've seen my machine do the same thing after waking from suspend, but it seems less frequent. It has also made me more diligent about disconnecting the VPN before shutting down or suspending, so I probably just don't run into it as frequently anymore. From what I've heard, ProtonVPN is aware of it and is working on a fix.
When it's in this state, you can fix it with these commands:
protonvpn-cli d
protonvpn ks --off
nmcli connection delete pvpn-ipv6leak-protection
(credit to julz in chat.pop-os.org for the fix)
ubuntu 20.04 the lts one. I am sure this issue is not that hard to fix because this was not even an issue in a weird riced arch distro maintained by one man lol.
On Thu, Jul 22, 2021 at 9:00 PM Jacob Kauffmann @.***> wrote:
This problem was not there even in a weird riced-arch distro I used let alone ubuntu.
I'm not sure what "riced-arch distro" is referring to, but can you please clarify if you've actually tried Ubuntu or if you tried another distribution such as Arch? If it was Ubuntu, which version was it? Pop!_OS is based on Ubuntu, and both Pop 20.04 and 21.04 are using the Ubuntu 21.04 kernel at this time, so Ubuntu 21.04 is what we would want to check in order to confirm if this is being caused by Pop!_OS patches or not.
System76 customers can reach out to support https://support.system76.com/ for technical assistance. For non-System76 hardware, you can seek community support on Reddit https://reddit.com/r/pop_os/ or Mattermost https://chat.pop-os.org.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/1827#issuecomment-884995208, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHA7XVRISOJC7MWDIKQQ2LTZAYYXANCNFSM5AXVQZ2A .
no, i dont use ProtonVPN
On Thu, Jul 22, 2021 at 9:04 PM leviport @.***> wrote:
Just a shot in the dark, but would you happen to be using ProtonVPN? It seems they have a known bug where their ipv6 leak protection feature can cause DNS problems if the machine is shut down while connected to their VPN service. I'm pretty sure I've seen my machine do the same thing after waking from suspend, but it seems less frequent. It has also made me more diligent about disconnecting the VPN before shutting down or suspending, so I probably just don't run into it as frequently anymore. From what I've heard, ProtonVPN is aware of it and is working on a fix.
When it's in this state, you can fix it with these commands:
protonvpn-cli d protonvpn ks --off nmcli connection delete pvpn-ipv6leak-protection
(credit to julz in chat.pop-os.org for the fix)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/1827#issuecomment-884998531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHA7XU3PWIPVOAKTBBUPRTTZAZJFANCNFSM5AXVQZ2A .
ubuntu 20.04 the lts one.
As I mentioned, our kernel is currently the Ubuntu 21.04 kernel on both Pop 20.04 and 21.04. The next step in troubleshooting would be trying an Ubuntu 21.04 live disk, to check if this was a kernel regression between 5.4 and 5.11.
just checked it on a live disk of ubuntu 21.04, turns out this happens in there as well...yikes, isn't ubuntu supposed to be the most stable...but i dont think this is a kernel 5.11 problem, because I have used 5.11 in manjaro and it worked fine...5.12 is fine as well...
On Thu, Jul 22, 2021 at 9:16 PM Jacob Kauffmann @.***> wrote:
ubuntu 20.04 the lts one.
As I mentioned, our kernel is currently the Ubuntu 21.04 kernel on both Pop 20.04 and 21.04. The next step in troubleshooting would be trying an Ubuntu 21.04 live disk, to check if this was a kernel regression between 5.4 and 5.11.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pop-os/pop/issues/1827#issuecomment-885007307, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMHA7XV6GPFW37ZO44UCGELTZA2UJANCNFSM5AXVQZ2A .
Thank you for confirming. If the issue is present in Ubuntu, then it makes sense to report it to Ubuntu in their bug tracker: https://launchpad.net/ubuntu/+bugs
Searching the tracker for your wireless card model number, I see three bugs with names that sound relevant, although they all look too old to apply to 21.04:
If 5.11 and 5.12 work in other distributions, you could try installing an upstream Linux kernel using an app such as Mainline. We generally don't recommend this for System76 hardware (since we make sure our hardware and kernel work together), but since your hardware is third-party and experiencing an issue anyway, the third-party kernel could provide a temporary solution until a fix makes its way into Ubuntu.
Also experiencing this issue with an AsRock X99 Killer motherboard and on-board "Killer E220x Gigabit Ethernet Controller". Is there an Ubuntu issue created for this yet?
Additional information: Issue began on the Pop! OS 20.10 release. I updated around 2 weeks before the 21.04 release and the issue started there.
Is there an Ubuntu issue created for this yet?
You can search using the link that I posted before: https://launchpad.net/ubuntu/+bugs
I see one that mentions the E220x here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301 This one has recent activity.
I see one that mentions the E220x here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301 This one has recent activity.
Thank you for the link, I have gone ahead and marked myself as affected there as well.
Distribution (run
cat /etc/os-release
): 21.04 NvidiaRelated Application and/or Package Version (run
apt policy $PACKAGE NAME
): EthernetIssue/Bug Description: Ethernet connection doesn't work after waking up from suspend (to 'fix' the issue, I have to restart the laptop), but wifi works fine.
Steps to reproduce (if you know): Suspend, then wake up and log back in
Expected behavior: Ethernet should be working correctly
Other Notes: I haven't tried sudo systemctl restart NetworkManager, yet....but pls fix this annoying and basic issue...