[Bug 1792085] Re: MTP not working/very slow on Bionic
For those experiencing the slowness problem: I've observed that if you turn on USB Debugging (by enabling Developer Mode) on your android phone, the mtp file transfer then becomes considerably faster. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390001] Leo here
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/390001 Title: Gnome visual effects not retained after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/390001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850001] [NEW] nautilus hangs on file delete
Public bug reported: Nautilus hangs when deleting a file. The file does not get deleted. This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT- CLICK attempt at deleting. This is reproducible in this boot session. This has never happened since the install of the OS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 18:12:36 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-10-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1850001 Title: nautilus hangs on file delete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
This doesn't fix the underlying bug, but I was able to find a workaround that repairs the corruption caused by the bug. See here: https://askubuntu.com/a/1184070/256054 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
I hope someone can fix this, is very annoying. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. + + In case it matters, these additional packages were also required for my + initial VPN setup: + + sudo apt-get install -y network-manager-l2tp network-manager-l2tp-gnome + strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2
[Bug 1849987] [NEW] empty space when on list view and when back to icon view
Public bug reported: Description: Ubuntu 19.10 Release: 19.10 nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Expected behavior: - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies all the space between the top bar and the bottom. - Switch to icon view - Icon view occupies all the space between the top bar and the bottom. Actual Behavior - (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then switch to list view - List view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). - Switch to icon view - Icon view occupies approximately 55% of the space between the top bar and the bottom. Approximately 45% of the space between the top bar and the bottom is blank (the upmost part). Observations: - The side bar doesn't seem to affect the bug. - By Starting nautilus in icon view the bug doesn't occur. In this case it's only triggered when switching to list view. - There are only 2 known ways to revert the bug: (1) when on icon view, clicking on "Other Locations", and then back to any section. (2) by restarting nautilus. There is no known way to revert the bug in list view. I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bug on Icon View screenshot" https://bugs.launchpad.net/bugs/1849987/+attachment/5300440/+files/Screenshot%20from%202019-10-26%2017-23-21.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1849987 Title: empty space when on list view and when back to icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
How is it possible that adding an additional VPN profile can corrupted an "already added and working" vpn? Which packages would be responsible for that type of corruption? Most importantly, short of reinstalling Ubuntu 19.10 what would be a workaround that may remove this corruption? For example, many times in the past, when I've had applications get corrupted, I could usually delete some .hiddenFolder or configuration file, and it would repair the corruption after rebooting. Do any of you know which files would have to be deleted to get my VPN situation back to "fresh install quality" (short of actually reinstalling)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I see this, too, on two different machines (one at home, one at work), both desktops with two monitors. Though for me the delay is usually longer then five seconds. The duration of the delay seems to increase with how long the machine's been up since its last reboot. This was not present when I first installed 18.04 a year ago, but seems to have arisen with some subsequent update. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
same issue i'm facing! thank youhttps://gtalovers.com/";>! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
I fear that GNOME is not the source of this issue. I had a look in the settings and noticed that many shortcuts have been changed from default. I did not do this manually. One suspicion is that it might got changed when changing from Unity to GNOME in an Ubuntu upgrade. After changing those shortcuts back to default, everything worked as expected. However there might have been some problem causing those default values to change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Well after commenting out the lines in /etc/gdm3/custom.conf and rebooting it worked for me. But currently i can not reenable the automatic login again. No matter what i do. Remove the comments, enable the option in the users menu. nothing works. even enabling the option in the users menu does little and after clicking away it does not save it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849965] [NEW] I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightdm but gdm3 i sudo a
Public bug reported: New upgrade failed with initial upgrade and i had to boot-repair to get to the normal ubuntu login window. The button Automatic Login in the settings does not work either... Using Ubuntu 19.10 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status After a few Logins the bug reappeared and i had to reinstall the gdm3 package once again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 16:42:18 2019 InstallationDate: Installed on 2018-09-23 (398 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1849965 Title: I got stuck in a Login-Loop. The solution with the .Xauthority permission would not fix it. Next i read about a lightdm bug. Since new ubuntu is using not lightdm but gdm3 i sudo apt-get purge gdm3 . Then reinstalled. After that i could login successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1849965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
I've added this to the 20.04 development blueprint, so let's revisit and discuss. If we can't solve the problem with packaging, let's document the mini.iso installation process so others have an easier time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849955] [NEW] Display jumps on dock/undock and on volume/brightness overlay
Public bug reported: I often dock/undock my laptop, introducing two additional displays. Every time I dock/undock (and when using the volume/brightness controls after undocking) the display jumps about. Here's a video showing it. https://www.youtube.com/watch?v=HfhPrh2y7Y8 Steps to reproduce. * Plug laptop into a docking station (possibly just attach an external display) * Configure the desktop running spanning all displays * Remove the external display / undock * Observe the laptop desktop jump around * Use the brightness or volume adjust keys * Observe the laptop desktop jump around Expected behaviour * The desktop should not jump around ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 14:15:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (628 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (36 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849955 Title: Display jumps on dock/undock and on volume/brightness overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1829 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1829 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1829 Importance: Unknown Status: Unknown ** Tags added: disco eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849950] [NEW] Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
You have been subscribed to a public bug: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment keyboard shortcuts tiling window -- Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work https://bugs.launchpad.net/bugs/1849950 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
The bug has been reported upstream and looks like the same bug https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1607 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
I have this problem as well. Virgin/Clean install of Eoan Desktop install in a KVM virtual machine. Install package cqrlog, which has a long startup time and usually causes the "not responding" dialog to raise, but can be dismissed. Under Eoan, the "CQRLOG is not responding" dialog cannot be dismissed - both "Force Quit" and "Wait" are greyed out and cannot be selected. gnome-shell then runs to 100% cpu utilisation (one thread/core) and repeatedly logs: gnome-shell[4157]: JS ERROR: TypeError: null has no properties#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 in syslog. Killing gnome-shell clears the "not responding" dialog. Not this is a virgin install to debug this problem, no extensions or anything else installed (except mariadb-server and cqrlog). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849081] Re: ZSH shells break Login screen
More updates. There was an issue with Powerlevel, at least as documented here. https://github.com/romkatv/powerlevel10k/issues/280 However, the issue seems to be lower level. An important issue seems to happen here: include this line at the top of .bashrc when using zsh ``` exec zsh ``` It seems this somehow breaks the login shell. I was able to reproduce this on my other laptop with 18.04. As long as that line is not there, the latest version of ZSH + oh_my_zsh + Powerlevel10k are working fine. This bug may be closed at your discretion, but it seems that there is benefit in somehow find out how to avoid this breaking in such case . -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1849081 Title: ZSH shells break Login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753070] Re: Cannot restore default alert sound (Ubuntu bell)
I was facing the same problem And after scavenging through the internet I found a fix Open a terminal And type dconf reset -f / Hope it works for y'all -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1753070 Title: Cannot restore default alert sound (Ubuntu bell) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849942] Re: 19.10 Gnome Settings and Tweak Tools Window Bar Bug
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Also affects: gnome-tweak-tool (Ubuntu) Importance: Undecided Status: New ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849942 Title: 19.10 Gnome Settings and Tweak Tools Window Bar Bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849942] [NEW] 19.10 Gnome Settings and Tweak Tools Window Bar Bug
You have been subscribed to a public bug: I upgraded from 19.04 to 19.10 and now there are some strange bugs with the Gnome Settings and the Tweak Tool: https://drive.google.com/file/d/1PpxTRKOqrrPfNLC_0fLSXNZTrsOIWDxg/view?usp=sharing ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 19.10 Gnome Settings and Tweak Tools Window Bar Bug https://bugs.launchpad.net/bugs/1849942 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Also affects: strongswan Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #746 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849931] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1844026 *** https://bugs.launchpad.net/bugs/1844026 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1844026, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1849931/+attachment/5300256/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300258/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300262/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300263/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300264/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300265/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1849931/+attachment/5300266/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1844026 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1849931 Title: nautilus crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1849931/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
I've attached the syslog for easier viewing. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/network-manager/+bug/1849930/+attachment/5300267/+files/syslog.txt ** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > - VPN setting, it works fine. + VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending pack
[Bug 1849930] [NEW] Additional VPN Breaks First VPN
Public bug reported: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 Net
[Bug 1849928] [NEW] Dock stays ontop of Xscreensaver
Public bug reported: Ubuntu 20.04 development version with kernel 5.3.0-18-generic up to date to latest @ 26/10/2019 The dock stays visible after Xscreensaver becomes active the screensaver flows under down the dock (see attachment) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 09:12:44 2019 InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1849928 Title: Dock stays ontop of Xscreensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
