[Bug 1838919] Re: Slow and lost keyboard and mouse events
Actually I should have just continued from comment #27. To do that please run: mv ~/.local/share/gnome-shell/extensions ~/old-extensions and then reboot. Any improvement? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Also, if you have upgraded to 19.10 then please run this again to send us fresh system information: apport-collect 1838919 -- 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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
The conversation above is no longer fresh in my memory, but I can see a couple of problems worth mentioning: * The bug description at the top doesn't clearly describe the problem. If the issue is "Slow and lost keyboard and mouse events" then please explain how you experience that issue in more detail; and... * Avoid mentioning log messages in the discussion and bug description as they are usually irrelevant and misleading. * Your attachment GsettingsChanges.txt seems to mention a few changes on the system that might relate to the problem: b'org.gnome.desktop.a11y.keyboard' b'mousekeys-max-speed' b'750' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-init-delay' b'160' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-accel-time' b'1200' b'org.gnome.desktop.a11y.keyboard' b'bouncekeys-beep-reject' b'true' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-enable' b'true' b'org.gnome.desktop.a11y.keyboard' b'stickykeys-modifier-beep' b'true' b'org.gnome.desktop.a11y.keyboard' b'stickykeys-two-key-off' b'true' b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-accept' b'true' b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-press' b'true' b'org.gnome.desktop.a11y.keyboard' b'disable-timeout' b'120' If you don't remember why you have those set then please remove them by running: dconf reset -f /org/gnome/desktop/a11y/ and then reboot. -- 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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
** Tags removed: disco ** Tags added: eoan ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => New ** Changed in: mutter (Ubuntu) Status: Won't Fix => New -- 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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+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)
** 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/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/gnome-shell/+bug/1849249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
** 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Sorry for the delay. The problem still exists under 19.10 desktop, but does not occur quite as often. However, it is slightly harder to escape from... I either need to wait 20+ seconds uselessly pressing keys I will have to subsequently delete, or tab to another command prompt, type something in easily, then return to the "stuck" prompt. My comment is only to bring the bug report up to date and keep it open. We are only a few weeks from the 20.04 release, where this bug will be much more important if still present. -- 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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
I can't seem to reproduce this bug in 20.04. Although LibreOffice is a little slow and unresponsive the rest of the shell continues to animate smoothly the whole time (I left another window animating on top). So I wonder if this bug is either fixed already or caused by some modification to your machine. Please run this command to send us more information about the system: apport-collect 1864301 And if you can please also try booting Ubuntu 20.04 from USB and tell us if you can reproduce it there: http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+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)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #944 https://gitlab.gnome.org/GNOME/mutter/issues/944 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/issues/944 Importance: Unknown Status: Unknown -- 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/gnome-shell/+bug/1849249/+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)
** Description changed: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b - https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- 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/gnome-shell/+bug/1849249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860057] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new
*** This bug is a duplicate of bug 1864326 *** https://bugs.launchpad.net/bugs/1864326 ** This bug is no longer a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) ** This bug has been marked a duplicate of bug 1864326 gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE -- 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/1860057 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860057/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
Tracking in https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 ** Description changed: + https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 + Gnome Shell crashes and restarts when I try to open a dialog window. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 21:15:33 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-02-04 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2020-02-22 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- 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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private to Public -- 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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864325] Re: On press of space key, lock screen got into a loop of trying to show the password field
I've never seen this behaviour before so wonder if it's caused by any of the modifications you've made to this system. Please start by uninstalling all of these extensions: 'openweather-extens...@jenslody.de', 'dash-to-d...@micxgx.gmail.com', 'clipboard-indica...@tudmotu.com', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'refresh-w...@kgshank.net', 'NotificationCounter@coolllsk', 'permanent-notificati...@bonzini.gnu.org', 'removeaccesibility@lomegor', 'variety_control@manjaro' and then reboot. We need to look at extensions first because so many bugs are caused by extensions. And we require that you uninstall extensions and not just disable them because buggy extensions can still interfere with the system. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1864325 Title: On press of space key, lock screen got into a loop of trying to show the password field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864325/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
** Tags added: eoan ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2225 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225 Importance: Unknown Status: Unknown ** Tags added: performance -- 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
That would probably be because a window in the foreground prevents fullscreen unredirect from being used. I suggest if you need both fullscreen window support and fractional scaling then logging into "Ubuntu on Wayland" might be a better option right now. -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
Though if you use "Ubuntu on Wayland" then you need to set: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862081/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby
Please note Ubuntu 19.04 has reached end-of-life and is no longer supported. https://wiki.ubuntu.com/Releases -- 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/1855757 Title: [nvidia] Background image corrupted after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797734] Re: slow calculator startup
** Tags added: focal ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Yes, Gnome 3.36 will be in Ubuntu 20.04 before April. -- 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/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857869] Re: Red fill the search stop icon
Hi Clinton Thanks for taking the time to report this. I've forwarded your request to the Yaru team here: https://github.com/ubuntu/yaru/issues/1980 ** Bug watch added: github.com/ubuntu/yaru/issues #1980 https://github.com/ubuntu/yaru/issues/1980 -- 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/1857869 Title: Red fill the search stop icon To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate
I fixed this upstream https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/commit/c031de0a3469faf5020768de506c6169e1e71ac0, not sure if there will be a release before focal or if this should be cherrypicked. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1862478 Title: gnome-system-monitor can't measure network transfer rate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863473] Re: Network History graph not showing actual network throughput.
*** This bug is a duplicate of bug 1862478 *** https://bugs.launchpad.net/bugs/1862478 ** This bug has been marked a duplicate of bug 1862478 gnome-system-monitor can't measure network transfer rate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1863473 Title: Network History graph not showing actual network throughput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1863473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796464] Re: Merge steam 1.0.0.61-2 from Debian
This bug was fixed in the package steam - 1:1.0.0.61-2ubuntu1 --- steam (1:1.0.0.61-2ubuntu1) focal; urgency=medium * Merge from Debian Sid (LP: #1796464). - Add an epoch to the version number. - Add steam-installer package that depends on steam and contains appstream metadata to allow Steam to be installed via appsteam enabled software centers. - Drop debian/steam.preinst because the dconf question it is not supported by all software centers. - Modify template-helper script for Ubuntu. - Modify debian/steam.bug-control for Ubuntu. - Disable copyright-helper script in debian/rules. - Standards-Version: 4.5.0 (no changes required) steam (1.0.0.61-2) unstable; urgency=medium * Upload to unstable * d/control: Make Homepage more specific * Standards-Version: 4.4.0 (no changes required) * Use debhelper-compat 12 steam (1.0.0.61-1) experimental; urgency=medium * New upstream release - Adds udev rules for NVIDIA Shield input hardware - d/p/udev-uinput.patch: Drop, applied upstream - d/p/udev-permissions.patch: Drop, mostly applied upstream. The only remaining differences in our package were: + Setting TAG+="uaccess" twice on SteamVR device nodes, which we can drop since it's redundant (once is enough) + Setting MODE="0660" on /dev/uinput, which is the default anyway steam (1.0.0.59-4) unstable; urgency=medium * Demote steam-devices to a recommendation. steam (1.0.0.59-3) unstable; urgency=medium * Add Conflicts/Replaces on steam-launcher. steam-launcher is a Valve-provided package containing the same launcher as Debian's steam package, and the same udev rules as Debian's steam-devices package. They are not co-installable: please install the steam and steam-devices packages from Debian non-free, *or* the steam and steam-launcher packages from Valve, but do not mix the two sources. * steam-devices: Add Breaks/Replaces on non-matching versions of steam. This should prevent mixing Debian's steam and steam-devices with Valve's steam-launcher and steam, while allowing switching between the two to work. (Closes: #920600) * d/scripts/steam: Delete libxcb-dri3.so.0 from the Steam Runtime, and add a versioned dependency on a newer version for the host system. This library added ABI without increasing the -version-info, which means the Steam launcher script can't decide that Debian's copy is newer and use it in preference to the Steam Runtime copy. (Closes: #921026) * Version the dependencies on libgpg-error0 and libxinerama1 to make sure the copies on the host system are at least as new as those provided by the Steam Runtime. * d/steam.bug-control: Add more information to bug reports steam (1.0.0.59-2) unstable; urgency=medium * Revert "Adjust VCS metadata for debian/experimental branch" * Use DEP-14 branch name debian/master * Upload to unstable steam (1.0.0.59-1) experimental; urgency=medium * New upstream release * get-orig-source: Use chdist to download Valve's "source" package with secure-APT authentication - d/valve-steam-keyring.gpg: Add the signing key for Valve's apt repository * d/p/udev-permissions.patch: Update for new upstream udev rules - new HID device 28de:2102 is now included in 60-steam-vr.rules * d/gbp.conf: Explicitly disable pristine-tar for this package. We don't keep upstream "source" in the git repository since that mostly consists of binary blobs. * Display a debconf note if the Nvidia proprietary kernel module is loaded, but the corresponding i386 libraries are not found. This seems to be the best we can do without adding a Recommends on the i386 libraries, which would pull in the binary driver even on systems that do not have Nvidia hardware. (See #918996) * d/scripts/steam: Cope with different installation directories, such as ~/.local/share/Steam from Valve's official packaging, without data loss (Closes: #919467) * d/scripts/steam: Install to a subdirectory of ~/.steam for new installations, to avoid ~/.steam/steam trying to be two things at once (Closes: #916303) * Adjust VCS metadata for debian/experimental branch steam (1.0.0.56-2) unstable; urgency=medium * Add myself to Uploaders * Import debian/ into salsa.debian.org git (Closes: #913651) * d/copyright.in: Really refer to the https form of copyright-format. d/copyright is generated from d/copyright.in and license files. (Closes: #916300) * Upgrade steam-devices to a hard dependency. The udev rules are increasingly used by the Steam client for input remapping, even if no Steam-specific hardware is used. (Closes: #916298) * Allow cross-compilation for i386 on a non-i386 build machine (Closes: #916301) * steam-devices: Mark as Multi-Arch: foreign. Otherwise, this package can't satisfy the steam package's dependency when
[Bug 1792085] Re: Regression: MTP not working/very slow
If that can be of interest, the "unlistable" folder has 124 files. I erased all the content from the phone, then I tried to copy 127 items; 124 of them were copied, then Nautilus hang, the last three were never copied and the folder became unaccessible. -- 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: Regression: MTP not working/very slow 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 1792085] Re: Regression: MTP not working/very slow
I am also affected by this bug, on Ubuntu 18.04. I can't get the list of
files from a folder on the phone ("could not get object handles"). No
brackets in file names, just a folder named "Camera" and default Android
names for pictures.
Manually installing and linking version 1-1-17 does not help. And, by
the way, release documentation is wrong, since in the archive there is
no "configure" file but one has to run "autogen.sh" first, then
"configure" is created.
--
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:
Regression: MTP not working/very slow
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 1796464] Re: Merge steam 1.0.0.61-2 from Debian
** Changed in: steam (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1796464 Title: Merge steam 1.0.0.61-2 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1796464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
On Ubuntu 18.04.3 I started experiencing the same problem. CD burning worked fine with Brasero in December when I last burned a CD for my car. I have suddenly had this problem since January, Brasero is hanging at "Starting to Record" I ran the commands from this thread: sudo chmod 4711 /usr/bin/cdrdao sudo chmod 4711 /usr/bin/wodim sudo chmod 0755 /user/bin/growisfs And now it gets a bit further but hangs at "Writing CD-Text Information" I am forced to End Process for Brasero and then the CD appears as no longer blank and I cannot use it again. I have also tried K3b and XFBurn which have the same problem. I have just clean installed this computer to 19.10 and again I have the same problem. Can anyone give me some help? I need to get a bunch of CDs burned urgently by next weekend. I have now wasted a whole bunch of blank CDs and I really do not want to have to change to another OS to fix this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby
I am also getting this issue (19.04), I might add that it also seems to affect VS code quite a lot. e.g. any open terminals go blank. -- 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/1855757 Title: [nvidia] Background image corrupted after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
