[Bug 938751] Re: Images are washed out or colors are skewed in some apps
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => jon grahaqm (skyking2630) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850995] Re: gnome-shell: freeze and high CPU usage
I also played it on VM: https://youtu.be/knTm-WYdT6Y -- 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/1850995 Title: gnome-shell: freeze and high CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850995/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
There is one more change I did after upgrading from 19.04 to 19.10. This is a KVM VM - and for some reason, the GUI (X) sometimes freezes after the VM is paused/saved/resumed, while SSH still works (this was also before 19.10 and behaviour did not improve in 19.10). I've changed to Wayland to see if it this kind of freezing happens there as well (so far, it doesn't). High CPU usage on all cores happens with Wayland only. I've just checked, it doesn't happen with regular X; CPU usage is normal/low there. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850995] [NEW] gnome-shell: freeze and high CPU usage
Public bug reported: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-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-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "log crash" https://bugs.launchpad.net/bugs/1850995/+attachment/5302128/+files/logg -- 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/1850995 Title: gnome-shell: freeze and high CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850995/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841051] Re: gpg password cache is never cleared
** Package changed: gnupg2 (Ubuntu) => seahorse (Ubuntu) ** Changed in: seahorse (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1841051 Title: gpg password cache is never cleared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1841051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850977] [NEW] gnome-software installs software without user having sudo access
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy gnome-software gnome-software: Installed: 3.28.1-0ubuntu4.18.04.8 Candidate: 3.28.1-0ubuntu4.18.04.12 Version table: 3.28.1-0ubuntu4.18.04.12 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 3.28.1-0ubuntu4.18.04.8 100 100 /var/lib/dpkg/status 3.28.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 What I expect to happen: Software is not installed for a user without sudo access. What does happen: I'm logging in with an LDAP user. This user does not have sudo access. When I select software from gnome-software ("Ubuntu Software"), it pops up and asks for my users password. I enter this in, and the software then installs (tested with blender, libreoffice, opencl driver). My user does *not* have sudo access on the system. $ sudo su - [sudo] password for jason: jason is not in the sudoers file. This incident will be reported. It appears these *may* be being installed with Snaps ... which still: How, without having root access, can an unprivileged user install something onto the system? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 13:53:03 2019 InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1850977 Title: gnome-software installs software without user having sudo access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1850977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841051] [NEW] gpg password cache is never cleared
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: The gpg password never expires - not even after reboot. I tried to set in dconf-editor: org.gnome.crypto.cache gpg-cache-method 'idle' org.gnome.crypto.cache gpg-cache-ttl 300 and created the following file: ~/.gnupg/gpg-agent.conf default-cache-ttl 300 None of these methods help. In case this could be helpful I add this (from Amir on https://superuser.com/questions/1347956/gnome-keyring-cant-clear- passphrase): user@machine:~$ gpgconf --list-dirs agent-socket /run/user/1000/gnupg/S.gpg-agent user@machine:~$ systemctl --user status gpg-agent.socket Failed to dump process list, ignoring: No such file or directory ● gpg-agent.socket - GnuPG cryptographic agent and passphrase cache Loaded: loaded (/usr/lib/systemd/user/gpg-agent.socket; disabled; vendor preset: enabled) Active: active (running) since Wed 2019-08-21 14:53:28 CEST; 5min ago Docs: man:gpg-agent(1) Listen: /run/user/1000/gnupg/S.gpg-agent (Stream) CGroup: /user.slice/user-1000.slice/user@1000.service/gpg-agent.socket Aug 21 14:53:28 machine systemd[1726]: Listening on GnuPG cryptographic agent and passphrase cache. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gpg-agent 2.2.4-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 22 14:14:08 2019 InstallationDate: Installed on 2018-08-01 (386 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnupg2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- gpg password cache is never cleared https://bugs.launchpad.net/bugs/1841051 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
I've sponsored all the SRUs now. I also backported the testcase for bionic. On xenial the same testcase *hangs*. That is likely to be due to some assumptions about gdbus that aren't true back then, but be sure to verify this release extra carefully. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
I'm seeing very similar behavior on Ubuntu 19.10 with X11 and a single monitor: I've noticed on Ubuntu 19.10 with X11 fractional scaling set to 1.25x, the pointer duplicates itself when I login to a new session. The original pointer sticks on the screen at 1x size, and I get a new pointer to use that's scaled for the 1.25x session. The new pointer follows the mouse, but the original pointer is stationary. If I disable/re-enable fractional scaling in the same session, the duplicate pointer disappears. ** Attachment added: "two-pointers.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+attachment/5302082/+files/two-pointers.jpg -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+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.
I want to add further details here. I have GeForce GTX 550 Ti card. When I was in 19.04, there was no such issue. After upgrading to 19.10 I started facing this auto login issue. No version of nvidia driver can solves this (both older or newer). When I moved to Nouveau driver, this particular autologin issue disappears, but sometimes my system freezes totally. I mean I can't even access keyboard or mouse. I have to do hard reboot. This freezing issue is intermittent and was not there when I was on 19.04. Not sure if this issue is related or not, but want to put my 2 cents here if it helps. On a separate note, I never have experienced a ubuntu upgrade going smoothly. Everytime there are some glitches and OS slows down a bit after every upgrade. It is very annoying for a daily driver setup like mine. I mean it is okay when you are using it occasionally for fun, but for daily driver fresh install is not an option every time. There are visible differences between fresh install and upgrade. Whenever a new release comes I have a dilemma, should I upgrade or ignore? If I upgrade God knows what will break? This situation never improves. -- 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 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850960] Re: Coming back from suspend, tabs and window are broken
** Description changed: When coming back from a suspend on eoan, the tabs and gnome-terminal window are all broken. Some are maximized, some are not, some have huge fonts, some don't. I have to double click on the title bar (if I can find it), and then double-click again to maximize and restore the state I had before the suspend. Attached is a screenshot, which captured the garbled state. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-13 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-terminal 3.34.0-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True + + lenovo X1 5th gen + 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) -- 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/1850960 Title: Coming back from suspend, tabs and window are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850960] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850960/+attachment/5302064/+files/Dependencies.txt -- 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/1850960 Title: Coming back from suspend, tabs and window are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850960] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850960/+attachment/5302066/+files/ProcEnviron.txt -- 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/1850960 Title: Coming back from suspend, tabs and window are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850960] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850960/+attachment/5302065/+files/ProcCpuinfoMinimal.txt -- 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/1850960 Title: Coming back from suspend, tabs and window are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850960] [NEW] Coming back from suspend, tabs and window are broken
Public bug reported: When coming back from a suspend on eoan, the tabs and gnome-terminal window are all broken. Some are maximized, some are not, some have huge fonts, some don't. I have to double click on the title bar (if I can find it), and then double-click again to maximize and restore the state I had before the suspend. Attached is a screenshot, which captured the garbled state. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-13 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-terminal 3.34.0-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected eoan ** Attachment added: "Screenshot from 2019-11-01 13-33-05.png" https://bugs.launchpad.net/bugs/1850960/+attachment/5302063/+files/Screenshot%20from%202019-11-01%2013-33-05.png ** Tags added: apport-collected eoan ** Description changed: When coming back from a suspend on eoan, the tabs and gnome-terminal window are all broken. Some are maximized, some are not, some have huge fonts, some don't. I have to double click on the title bar (if I can find it), and then double-click again to maximize and restore the state I had before the suspend. Attached is a screenshot, which captured the garbled state. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-10-13 (18 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-terminal 3.34.0-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 + Tags: eoan + Uname: Linux 5.3.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo + _MarkForUpload: True -- 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/1850960 Title: Coming back from suspend, tabs and window are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1850960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850951] Re: GIMP crashed after clicking discard to save changes, when closing
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately you failed to tell us which version of gimp or Ubuntu you are using. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1850951 and then change the status of the bug back to 'New'. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gimp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1850951 Title: GIMP crashed after clicking discard to save changes, when closing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1850951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Additional thought on my scenario ... I was also working in a duel monitor mode when gnome crashed. In my case Thunderbird was on my primary monitor, and the thunderbird dialog came up on my secondary monitor. Interacting with this dialog is when gnome crashes. -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850951] [NEW] GIMP crashed after clicking discard to save changes, when closing
Public bug reported: about 6 unsaved files. Clicked close window. Was prompted about the unsaved changes. Clicked discard. The window closed, as if gimp had closed as usually. After a few seconds, got the error message about a segmentation fault. Asked to report the bug. Reporting the bug. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1850951 Title: GIMP crashed after clicking discard to save changes, when closing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1850951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850727] Re: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover
I wasn't able to recreate it until we added our PPA to get the following version: 3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7 -- 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/1850727 Title: [nvidia] Let GDM timeout and it changes to a blank screen where there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1850727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Regarding comment #10 that this may be this user's specific issue. I have opened bug #1850833 that is classified as a duplicate of this bug. I have also provided in that bug a cleaner path to reproduce. -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850932] [NEW] [SRU] Backport 2.62.2-2
Public bug reported: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.2-2 from focal. The main purpose of this backport (as opposed to -1) is to fix bug #1844853. But there are several other changes. There are many cherry-picks to improve the testsuite's reliability. At the time of upload they weren't in the stable branch, but now they almost all are. These commits can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The two that are not are: commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 Author: Simon McVittie Date: Tue Oct 29 16:27:53 2019 + gdbus-server-auth test: Create temporary directory for Unix socket This avoids failure to listen on the given address on non-Linux Unix kernels, where abstract sockets do not exist and so unix:tmpdir is equivalent to unix:dir. To avoid bugs like this one recurring, run most of these tests using the unix:dir address type, where Linux is equivalent to other Unix kernels; just do one unix:tmpdir test, to check that we still interoperate with libdbus when using abstract sockets on Linux. Resolves: GNOME/glib#1920 Fixes: 9f962ebe "Add a test for GDBusServer authentication" Signed-off-by: Simon McVittie commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 Author: Simon McVittie Date: Fri Oct 11 19:02:55 2019 +0100 Add a test for GDBusServer authentication In particular, if libbdus is available, we test interoperability with a libdbus client: see GNOME/glib#1831. Because that issue describes a race condition, we do each test repeatedly to try to hit the failing case. Signed-off-by: Simon McVittie which are both testsuite fixes. There are some additional non-upstream changes: * d/p/debian/mimeapps-test-Mark-as-flaky.patch: Drop patch, hopefully no longer needed with #941550 fixed * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: Make taptestrunner non-executable to avoid a Lintian warning the former is again a testsuite fix. The latter is a fix to the test runner, which is relevant for the installed tests (run via autopkgtest) but not otherwise. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. [ Regression potential ] all test fixes> Build failures or autopkgtest failures. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Eoan) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Eoan) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: glib2.0 (Ubuntu Eoan) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.2-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Project changed: l2tp-ipsec-vpn => ubuntu ** Changed in: ubuntu Status: New => Confirmed ** Package changed: ubuntu => network-manager-l2tp (Ubuntu) -- 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 L2TP 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