[Bug 1728143] Re: Screen freezes after waking from suspend with Gnome on Wayland
Okay, I will try this with a fresh install of Ubuntu 17.10 and provide the necessary logs soon. I should be able to use the provided script over ssh, thanks. The problem with GDM freezing on Wayland after system resume/wakeup has been occurring ever since I ran the beta builds of 17.10, but it's clearly not fixed. I've been relatively busy lately, my apologies. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1728143 Title: Screen freezes after waking from suspend with Gnome on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1728143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728145] [NEW] gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10
Public bug reported: When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does not fill the screen at all when snapping the window to the right or left side. There are large gaps on the right and bottom edges of the terminal window in Wayland. On the same computer, with the same version of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the window fills screen space entirely and there is no problem. I am not using display scaling or hidpi features at all, my display resolution is set at default 1080p. This needs to be fixed or I'm ditching gnome- terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-terminal wayland ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Description changed: - When using a Wayland gnome-session or ubuntu-session in Ubuntu 17.10, - gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does - not fill the screen at all when snapping the window to the right or left - side.There are large gaps on the right and bottom edges of the terminal - window in Wayland. On the same computer, with the same version of gnome- - terminal in an Xorg gnome-session or Xorg ubuntu-session, the window - fills screen space entirely and there is no problem. I am not using - display scaling or hidpi features at all, my display resolution is set - at default 1080p. This needs to be fixed or I'm ditching gnome-terminal. + When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu + 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) + does not fill the screen at all when snapping the window to the right or + left side.There are large gaps on the right and bottom edges of the + terminal window in Wayland. On the same computer, with the same version + of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the + window fills screen space entirely and there is no problem. I am not + using display scaling or hidpi features at all, my display resolution is + set at default 1080p. This needs to be fixed or I'm ditching gnome- + terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Description changed: When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu 17.10, gnome-terminal (v3.24.2 is the version in the 17.10 repositories) does not fill the screen at all when snapping the window to the right or - left side.There are large gaps on the right and bottom edges of the + left side. There are large gaps on the right and bottom edges of the terminal window in Wayland. On the same computer, with the same version of gnome-terminal in an Xorg gnome-session or Xorg ubuntu-session, the window fills screen space entirely and there is no problem. I am not using display scaling or hidpi features at all, my display resolution is set at default 1080p. This needs to be fixed or I'm ditching gnome- terminal. Expected behavior: gnome-terminal window should fill right/left of screen when snapped to corner in a Wayland session What happened instead: gnome-terminal window does not fill screen space when snapped to right or left edge of desktop on Wayland session, there are large gaps below and to the right of the snapped window on either side. ** Summary changed: - gnome-terminal does not fill screen when window snapping on Wayland + gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1728145 Title: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728143] [NEW] Screen freezes after waking from suspend with Gnome on Wayland
Public bug reported: It appears that using Xorg instead of Wayland is the only way to fix this problem on Ubuntu 17.10. For some odd reason, whenever I wake my computer from suspend (especially after an extended period of time asleep) using Gnome in a Wayland session (gnome-session and stock ubuntu-session alike), my screen freezes completely on whatever was last there before suspending and I can't get any IO response at all. Nothing, the screen is totally frozen. I am also unable to exit into a recovery shell or kill GDM or gnome-session/ubuntu-session locally. I also can't seem to find any traces or indications for the freeze in the syslog, or maybe I'm just not sure where to look. I believe this is a problem with GDM on Wayland, not kernel related, as it happens on a totally stock install and when I use an upgraded/downgraded kernel. It literally necessitates restarting my computer. This problem is nonexistent when using Xorg instead of Wayland with GDM. Anyone else have this issue on Ubuntu 17.10 or figure out a solution better than simply switching to Xorg? I should clarify that I am not using nvidia drivers, I'm using Intel integrated graphics on a core-i7 5500U. Ubuntu 17.10 uses gnome-session v3.26.1. Expected behavior: When waking computer from suspend, expect GDM lock prompt and log back in. What happened instead: When waking computer from suspend, screen and IO is completely frozen, necessitating a force-shutdown. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: gdm gnome-17.10 gnome-session suspend-resume ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1728143 Title: Screen freezes after waking from suspend with Gnome on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1728143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1681295] [NEW] Problem in network-manager-openvpn, openvpn fails during and after downloads.
Public bug reported: So I've been using OpenVPN through the network-manager-openvpn package integrated into the network manager GUI. I experienced an odd problem where consistently, during or after downloading (in this case, I tested by just downloading the kernel tarball from kernel.org repeatedly, which is around 90MB) Every single time, without fail, the openvpn client would fail and my connection would go dead. To reconnect, I would have to manually restart the network manager. Now, I played around with .conf files and the CLI openvpn client and noticed EXACTLY the same behavior happening. I eventually arrived to the conclusion that the flag or option "auth-nocache" would cause a connection reset after or during downloads and streaming. I then got to reading the openvpn man pages and I stumbled across this message (you can easily find it by going 'man openvpn | grep nocache') about the guaranteed failure of key renegotiation if auth-user-pass and auth-nocache were used together: " Further, using --daemon together with --auth-user-pass (entered on console) and --auth-nocache will fail as soon as key renego‐ tiation (and reauthentication) occurs." When I removed auth-user-pass from my .conf files, the problem went away. Then I wondered. Now what if...network-manager-openvpn was actually passing both flags to openvpn? Then I downloaded the source tarball and found that indeed, this exact thing is happening on a SINGLE line. See line 1380 of network-manager-openvpn-1.1.93/src/nm-openvpn-service.c "add_openvpn_arg (args, "--auth-nocache");" So I decided to comment out that single line. I then rebuilt the packages network-manager-openvpn and network-manager-openvpn using 'dpkg-buildpackage -us -uc -nc', installed them, and tested downloading the source kernel repeatedly to see if the connection would hold. It does! Literally commenting out ONE line fixed weeks worth of extreme annoyance repeatedly reconnecting to my vpn. This issue is rather annoying and needs to be fixed so openvpn doesn't keep cutting out. I've attached a patch for the source. ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager network-manager-openvpn openvpn ** Patch added: "The following patch removes the single offending line which causes this issue." https://bugs.launchpad.net/bugs/1681295/+attachment/4859305/+files/nm-openvpn-service-fix.patch ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** No longer affects: network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1681295 Title: Problem in network-manager-openvpn, openvpn fails during and after downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1681295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
