[Bug 1890533] Re: Overview stuttering with 4K & Intel
** Description changed: This was first described upstream in https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697 I'm reporting it here as requested in https://discourse.ubuntu.com/t /gnome-shell-performance-improvements-in- ubuntu-20-04/15972/38?u=memeplex + + Please don't be mislead by the enabled-extensions value in the attached + log (['cpuf...@zdyb.tk', 'impatie...@gfxmonk.net', 'clipboard- + indica...@tudmotu.com', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu- + d...@ubuntu.com']). This is just a residual value, the only extensions + installed in my system are the ones provided by Ubuntu and clipboard- + indicator. And desktop-icons is indeed disabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 02:23:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This was first described upstream in https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697 I'm reporting it here as requested in https://discourse.ubuntu.com/t /gnome-shell-performance-improvements-in- ubuntu-20-04/15972/38?u=memeplex Please don't be mislead by the enabled-extensions value in the attached log (['cpuf...@zdyb.tk', 'impatie...@gfxmonk.net', 'clipboard- indica...@tudmotu.com', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu- d...@ubuntu.com']). This is just a residual value, the only extensions installed in my system are the ones provided by Ubuntu and clipboard- indicator. And desktop-icons is indeed disabled. + + Besides I'm perfectly able to reproduce the same problem in a vanilla + Gnome installation both in Arch and in Fedora using a wide range of + kernels (from 5.4 to 5.8). Despite some variations, performance is + consistently poor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 02:23:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1890533 Title: Overview stuttering with 4K & Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890533] [NEW] Overview stuttering with 4K & Intel
Public bug reported: This was first described upstream in https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697 I'm reporting it here as requested in https://discourse.ubuntu.com/t /gnome-shell-performance-improvements-in- ubuntu-20-04/15972/38?u=memeplex ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 02:23:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1890533 Title: Overview stuttering with 4K & Intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
Actually the problem might just be that the Linux kernel doesn't understand extended vendor-specific display timings. I've decoded your monitor's EDID and it reveals that 3840x2160 30Hz is mentioned: edid-decode (hex): 00 ff ff ff ff ff ff 00 04 69 a3 28 24 51 00 00 0e 1b 01 03 80 3e 22 78 3a 1c b5 a3 57 4f a0 27 0d 50 54 bf ef 00 d1 c0 81 40 81 80 95 00 b3 00 71 4f 81 c0 01 01 04 74 00 30 f2 70 5a 80 b0 58 8a 00 6d 55 21 00 00 1a 02 3a 80 18 71 38 2d 40 58 2c 45 00 6d 55 21 00 00 1e 00 00 00 fd 00 1e 50 18 a0 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 41 53 55 53 20 50 42 32 38 37 51 0a 20 01 83 02 03 2c f1 51 01 02 03 11 12 13 04 14 05 0e 0f 1d 1e 1f 90 20 22 23 09 17 07 83 01 00 00 6d 03 0c 00 20 00 00 3c 20 00 60 01 02 03 56 5e 00 a0 a0 a0 29 50 30 20 35 00 6d 55 21 00 00 1e e2 68 00 a0 a0 40 2e 60 30 20 36 00 6d 55 21 00 00 1a 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 6d 55 21 00 00 1e 8c 0a d0 90 20 40 31 20 0c 40 55 00 6d 55 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 5e EDID version: 1.3 Manufacturer: ACI Model 10403 Serial Number 20772 Made in week 14 of 2017 Digital display Maximum image size: 62 cm x 34 cm Gamma: 2.20 DPMS levels: Off Undefined display color type First detailed timing is preferred timing Color Characteristics Red: 0.6367, 0.3408 Green: 0.3115, 0.6250 Blue: 0.1542, 0.0537 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48066.667 Hz 4:335.000 kHz 30.240 MHz (Apple) 640x48072.809 Hz 4:337.861 kHz 31.500 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60056.250 Hz 4:335.156 kHz 36.000 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60072.188 Hz 4:348.077 kHz 50.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76870.069 Hz 4:356.476 kHz 75.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) Standard Timings 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x96060.000 Hz 4:360.000 kHz 108.000 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1440x90059.887 Hz 16:10 55.935 kHz 106.500 MHz (DMT) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) Detailed mode: Clock 297.000 MHz, 621 mm x 341 mm 3840 4016 4104 4400 (176 88 296) 2160 2168 2178 2250 ( 8 10 72) +hsync -vsync VertFreq: 30.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 148.500 MHz, 621 mm x 341 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Display Range Limits Monitor ranges (GTF): 30-80 Hz V, 24-160 kHz H, max dotclock 300 MHz Display Product Name: ASUS PB287Q Has 1 extension block Checksum: 0x83 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 40 bytes of CTA data blocks Video Data Block 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 720x48059.940 Hz 4:331.469 kHz 27.000 MHz (VIC 2) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 720x57650.000 Hz 4:331.250 kHz 27.000 MHz (VIC 17) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 1920x1080i 50.000 Hz 16:928.125 kHz 74.250 MHz (VIC 20) 1920x1080i 60.000 Hz 16:933.750 kHz 74.250 MHz (VIC 5) 1440x48059.940 Hz 4:331.469 kHz 54.000 MHz (VIC 14) 1440x48059.940 Hz 16:931.469 kHz 54.000 MHz (VIC 15) 1440x57650.000 Hz 4:331.250 kHz 54.000 MHz (VIC 29) 1440x57650.000 Hz 16:931.250 kHz 54.000 MHz (VIC 30) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1920x1080 24.000 Hz 16:927.000 kHz 74.250 MHz (VIC 32) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 96 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR -
[Bug 1890418] Re: External monitor will not display to 4k
Thanks. The file xrandr.txt indeed shows the HDMI connection is limited to 1920x1080. It also shows that's the "current" mode but it lists no "preferred" mode, which does support the idea that the monitor can do higher resolution... The manufacturer's specs mention that 4K is limited to 30Hz over HDMI. But that should be fine. It just means the monitor can't do HDMI 2.0. Most likely the monitor only supports HDMI 1.3 or 1.4. I think the main problem here is probably the HDMI cable. If it can only handle HDMI 1.2 or lower then you will not see the 3840×2160 30Hz option. So I suggest getting a newer cable that supports at least HDMI 1.3. Why Windows 10 doesn't have the same issue, I don't know. -- 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
Done. Thanks -- 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399092/+files/journal.txt -- 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399093/+files/lspcik.txt -- 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399094/+files/xrandr.txt -- 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] Re: External monitor will not display to 4k
Please run this command to attach more information about the system: apport-collect 1890418 Please also run these commands: lspci -k > lspcik.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** Tags added: focal ** 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890001] Re: Random stuttering while in game
*** This bug is a duplicate of bug 1849142 *** https://bugs.launchpad.net/bugs/1849142 You may also need to log out and in again. If the problem persists then please provide a new log by running: journalctl -b0 > journal-again.txt -- 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/1890001 Title: Random stuttering while in game To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing
** Tags added: focal -- 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/1715602 Title: ubiquity-dm / Install Ubuntu - Power button/menu does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890271] Re: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode
*** This bug is a duplicate of bug 1715602 *** https://bugs.launchpad.net/bugs/1715602 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1715602, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1715602 ubiquity-dm / Install Ubuntu - Power button/menu does nothing -- 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/1890271 Title: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Given that we've implemented the only known solution for this in bug 1877075, the remaining explanation for it might not be thread-related. Some kind of memory corruption (even single threaded) could have the same effect. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Yes that stack looks the same as before. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873026] Re: File manager grabs favorites folders on left
Hi All, As described on June 20, the bug went away, but it is back now, so there must be some way to make it come and go, but I haven't figured out what I did. Rob -- 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/1873026 Title: File manager grabs favorites folders on left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
After restarting the machine, launching rhythmbox from the command line does not print messages. Subsequent launches do however -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
I am talking about the pause/play, previous song and next song keys. On my Dell xps 13 laptop, those are f4, f5 and f6 (or fn + f4, fn + f5, fn + f6) When opening Rhythmbox from the command line: (this is after having opened and closed it once, so the media keys were already not working) Opening and using rhythmbox does not print error messages, but closing does: /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12157' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12156' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '40060' return func(*args, **kwargs) I will now restart my machine to launch rhythmbox the first time from the command line (with working media keys) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
Thank you for your bug report. Could you start rhythmbox from a command line and see if any error is printed? What media keys are you talking about exactly? ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => Low ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890494] [NEW] Closing Rhythmbox does not free the media keys
Public bug reported: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 Version table: *** 3.4.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1036489] Re: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-binding behavior
This still affects me in Ubuntu 20.04. Fully closing Rhythmbox does not free up the media keys, and if you reopen it later the media keys will not work (and won't work for other programs either) Different ways to reproduce (note that the only way to have the media keys working again is to restart the machine) 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1036489 Title: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key- binding behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1036489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890001] Re: Random stuttering while in game
*** This bug is a duplicate of bug 1849142 *** https://bugs.launchpad.net/bugs/1849142 I looked and I already had Ubuntu AppIndicators turned off. -- 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/1890001 Title: Random stuttering while in game To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
** Tags added: rls-bb-incoming -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
I've just got a similar crash when just clicking on a menu item, I've
got some more complete stacktrace, but don't think is really helpful
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558,
559, 15822592872050180864, 94249823962208, 94249845226528}}
pid =
tid =
#1 0x55b83f47052a in ()
#2 0x7f45908a3210 in () at
/lib/x86_64-linux-gnu/libc.so.6
#3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 139936754804816, 94252984795136, 94250118475456,
94250118475557, 94250118475456, 94250118475456, 94250118475568, 94250118475756,
94250118475456, 94250118475756, 0, 0, 0, 0, 0}}
pid =
tid =
#4 0x7f4590882859 in __GI_abort () at abort.c:79
save_stage = 1
act =
{__sigaction_handler = {sa_handler = 0x5, sa_sigaction = 0x5},
sa_mask = {__val = {112, 4, 48320015904, 0, 0, 139936755958789, 0, 21474836480,
140735042337344, 139936638613175, 139936638613175, 0, 15822592872050180864,
139936755958789, 139935137267712, 139936638613175}}, sa_flags = -1874503997,
sa_restorer = 0x104}
sigs = {__val = {32, 0 }}
#5 0x7f4590882729 in __assert_fail_base
(fmt=0x7f4589a2b6b7 , assertion=0x7f4590455858 "!xcb_xlib_threads_sequence_lost",
file=0x7f45904556c3 "../../src/xcb_io.c", line=260, function=)
at assert.c:92
str = 0x55b850d16780 "\220ŻE\270U"
total = 4096
#6 0x7f4590893f36 in __GI___assert_fail
(assertion=assertion@entry=0x7f4590455858
"!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f45904556c3
"../../src/xcb_io.c", line=line@entry=260,
function=function@entry=0x7f4590455b10 <__PRETTY_FUNCTION__.14999>
"poll_for_event") at assert.c:101
#7 0x7f45903e1493 in poll_for_event (dpy=dpy@entry=0x55b83fee4000,
queued_only=queued_only@entry=0)
at ../../src/xcb_io.c:260
request =
req =
event =
event_sequence =
__PRETTY_FUNCTION__ = "poll_for_event"
#8 0x7f45903e153d in poll_for_response (dpy=dpy@entry=0x55b83fee4000) at
../../src/xcb_io.c:278
response =
error = 0x55b83fee4000
req =
__PRETTY_FUNCTION__ = "poll_for_response"
#9 0x7f45903e183a in _XEventsQueued (mode=,
dpy=0x55b83fee4000)
at ../../src/xcb_io.c:362
response =
#10 _XEventsQueued (dpy=0x55b83fee4000, mode=) at
../../src/xcb_io.c:344
#11 0x7f45903e482d in _XGetRequest
(dpy=dpy@entry=0x55b83fee4000, type=type@entry=43 '+', len=len@entry=4) at
../../src/XlibInt.c:1764
req =
--Type for more, q to quit, c to continue without paging--
#12 0x7f45903dd62f in XSync (dpy=0x55b83fee4000, discard=discard@entry=0)
at ../../src/Sync.c:43
rep =
{type = 48 '0', revertTo = 236 '\354', sequenceNumber = 16408, length
= 21944, focus = 1073049456, pad1 = 21944, pad2 = 1, pad3 = 0, pad4 =
2288196592, pad5 = 32581}
#13 0x7f459054ba53 in _cogl_winsys_onscreen_bind (onscreen=)
at ../cogl/cogl/winsys/cogl-winsys-glx.c:1553
context = 0x55b83ff3aaa0
glx_context = 0x55b83ff3b450
glx_display =
xlib_renderer = 0x7f457c001d60
glx_renderer =
xlib_onscreen =
glx_onscreen =
old_state = {old_error_handler = 0x7f459073bc70, trapped_error_code =
0, old_state = 0x0}
drawable = 2097170
#14 0x7f459050a8eb in _cogl_framebuffer_gl_bind
(framebuffer=0x55b84018e7d0, target=36160)
at ../cogl/cogl/driver/gl/cogl-framebuffer-gl.c:284
winsys =
ctx = 0x55b83ff3aaa0
#15 0x7f459050aec5 in _cogl_framebuffer_gl_flush_state
(draw_buffer=0x55b84018e7d0, read_buffer=0x55b84018e7d0,
state=(COGL_FRAMEBUFFER_STATE_BIND | COGL_FRAMEBUFFER_STATE_VIEWPORT |
COGL_FRAMEBUFFER_STATE_CLIP | COGL_FRAMEBUFFER_STATE_DITHER |
COGL_FRAMEBUFFER_STATE_MODELVIEW | COGL_FRAMEBUFFER_STATE_PROJECTION |
COGL_FRAMEBUFFER_STATE_FRONT_FACE_WINDING | COGL_FRAMEBUFFER_STATE_DEPTH_WRITE
| COGL_FRAMEBUFFER_STATE_STEREO_MODE))
at ../cogl/cogl/driver/gl/cogl-framebuffer-gl.c:386
ctx = 0x55b83ff3aaa0
differences = 511
bit =
__func__ = "_cogl_framebuffer_gl_flush_state"
#16 0x7f4590541c5a in _cogl_framebuffer_flush_state
(state=(COGL_FRAMEBUFFER_STATE_BIND | COGL_FRAMEBUFFER_STATE_VIEWPORT |
COGL_FRAMEBUFFER_STATE_CLIP | COGL_FRAMEBUFFER_STATE_DITHER |
COGL_FRAMEBUFFER_STATE_MODELVIEW | COGL_FRAMEBUFFER_STATE_PROJECTION |
COGL_FRAMEBUFFER_STATE_FRONT_FACE_WINDING | COGL_FRAMEBUFFER_STATE_DEPTH_WRITE
| COGL_FRAMEBUFFER_STATE_STEREO_MODE), read_buffer=0x55b84018e7d0,
draw_buffer=0x55b84018e7d0) at ../cogl/cogl/cogl-framebuffer.c:887
ctx =
clip_stack =
had_depth_and_color_buffer_bits =
scissor_x0 = 0
scissor_y0 = 0
scissor_x1 = 2147483647
scissor_y1 = 2147483647
#17
[Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from c
This crash doesn't seem to reproduce anymore, and there's no trace of it in e.u.c since version 3.36.4 went in proposed. ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876894] Re: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling
Reverting to both 100% and 200% works fine, without issues. g-c-c now requires a further "apply" to turn it off, and mutter reacts properly when setting it back to both 200% and 100%. marco-ThinkPad-X1-Carbon-7th ~ 13:22:00 ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages marco-ThinkPad-X1-Carbon-7th ~ 13:22:02 ❯ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1876894 Title: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Marking this verified again, as it was verified as fixed in version 3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in .2 [3] do not affect this behavior, we can safely consider it already verified. [1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/comments/30 [2] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/31 [3] https://launchpadlibrarian.net/490341554/mutter_3.36.4-0ubuntu0.20.04.1_3.36.4-0ubuntu0.20.04.2.diff.gz ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows
Marking this verified again, as it was verified as fixed in version 3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in .2 [3] do not affect this behavior, we can safely consider it already verified. [1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/16 [2] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/18 [3] https://launchpadlibrarian.net/490341554/mutter_3.36.4-0ubuntu0.20.04.1_3.36.4-0ubuntu0.20.04.2.diff.gz ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1884754 Title: Fractional scaling does not persist while resizing or rebooting in VM windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886996] Re: Restore previous configuration after turning off fractional scaling does not work
Confirm the test case works correctly here: ❯ apt-cache policy libmutter-6-0 libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ❯ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1886996 Title: Restore previous configuration after turning off fractional scaling does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890427] Re: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyr
** Tags removed: need-duplicate-check -- 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/1890427 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.36.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1890427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890427] [NEW] package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-ke
Public bug reported: bug while installing wine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libp11-kit-gnome-keyring (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 5 12:37:37 2020 DuplicateSignature: package:libp11-kit-gnome-keyring:(not installed) Unpacking libpng12-0:i386 (1.2.50-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-FSmyoz/000-libpng12-0_1.2.50-1ubuntu2_i386.deb (--unpack): unable to install new version of '/usr/lib/i386-linux-gnu/libpng12.so.0': No such file or directory ErrorMessage: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 InstallationDate: Installed on 2020-07-20 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-minimal, 2.7.5-5ubuntu3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gnome-keyring Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules/gnome-keyring.module', which is also in package gnome-keyring-pkcs11:amd64 3.36.0-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1890427 Title: package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: trying to overwrite '/usr/share/p11-kit/modules /gnome-keyring.module', which is also in package gnome-keyring- pkcs11:amd64 3.36.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1890427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1888480] Re: problem in menu graphic
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1888480 Title: problem in menu graphic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1888480/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890261] Re: I am not prompted for my password when booting after running out of power (e.g. empty battery)
Thank you for your bug report. Could you add your 'journalctl -b 0' after the system start? When the battery gets empty the system does try to suspend or hibernate depending of your configuration so the next boot is not a standard one but a resume which could explain you don't get prompted to log in ** Package changed: gnome-screensaver (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** 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/1890261 Title: I am not prompted for my password when booting after running out of power (e.g. empty battery) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890271] Re: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode
It's reproducible in a VM. There is no related message in the journal. ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1890271 Title: [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1886162 Title: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862713] Re: Failed to verify signature archive-contents.sig
I had the same issue with emacs-nox, but I have installed it on Windows 10 inside of WSL2 with Ubuntu 18.04. I was able to workaround the issue with: gpg --homedir ~/.emacs.d/elpa/gnupg --keyserver hkps://keyserver.ubuntu.com:443 --receive-keys 066DAFCB81E42C40 After successfully importing the key, a package-refresh-contents worked fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1862713 Title: Failed to verify signature archive-contents.sig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1862713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890271] [NEW] [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode
You have been subscribed to a public bug: [Summary] After entering the OEM installation mode and then clicking the "Power off" option, the system cannot be powered off. [Steps to reproduce] 1. Plug the USB key which has the 20.04.01 build 2. Power on the system 3. Select USB drive to launch the grub menu 4. Select "OEM installation" to run the installation 5. After entering the OEM installation page, click the "Power off" option. 6. Check if the system can be powered off [Expected result] The system can be powered off after clicking the "Power off" option [Actual result] There is no response after clicking the "Power off" option [Failure rate] 3/3 [Additional information] system-manufacturer: LENOVO system-product-name: P920 CPU: Intel(R) Xeon(R) Gold 6230N CPU @ 2.30GHz GPU: nVidia - 10de:1e30 ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Confirmed ** Tags: bot-comment -- [20.04.01] The system cannot be shut down after clicking the "Power off" option on the OEM installation mode https://bugs.launchpad.net/bugs/1890271 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 1862713] Re: Failed to verify signature archive-contents.sig
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: emacs25 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1862713 Title: Failed to verify signature archive-contents.sig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1862713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890418] [NEW] External monitor will not display to 4k
Public bug reported: I have a Toshiba radius 11 laptop which has a 4 k native screen. I have connected an Asus PB287Q 28" external monitor (https://www.asus.com/us /Commercial-Monitors/PB287Q/specifications/) over HDMI which displays the full 4K resolution when running under windows10 but will only reach a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just dual booting. Under Monitor Preferences this monitor is detected as an "Ancor Communications inc 28" and the monitor preferences provides a number of resolution steps up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this resolution is added to the monitor preferences pick list but attempting to apply it results in "the selected configuration for displays could not ..." message ** Affects: mutter (Ubuntu) Importance: Undecided Status: 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/1890418 Title: External monitor will not display to 4k To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
I found a work-around: disabling animations in GNOME Tweaks solves the issue and the whole Top Bar (not a ghost of it) and the Dock are visible for a very short time until the window becomes fullscreen. I suggest to include an option to disable these animations when fullscreen windows are present because they also cause frame drops. As for upgrading I'm patiently waiting for the dot release. Fingers crossed tomorrow is the day. :) -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
it's fixed in upstream git now ** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- 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/1718135 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1718135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
I think this bug might have already been fixed before Ubuntu 20.04 was released. So there's another reason to upgrade :) -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
Thanks for the quick response! Another detail I want to add is that it only happens after invoking the switcher. I can control volume or screen brightness all good without any problems but as soon as I switch windows and go back to my game the top bar keeps appearing whenever the volume or screen brightness controls are accessed. The switcher is definitely the culprit here. It happens on X, it happens on Wayland. On X, the bar usually disappears as soon as the switching animation stops or volume and screen brightness control pop-ups fade away. On Wayland, the bug persists until I re-open the affected window through Activities, not the Switcher. GNOME Shell 3.28.4-0ubuntu18.04.3 Mutter 3.28.4-0ubuntu18.04.2 -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
This bug is open again now so we don't need another report. Thanks. -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
Hey, Daniel! You sent me here from #1890281 #1725649 is said to be fixed but the bug is still present on Ubuntu 18.04.4 running X. I've recently upgraded to Bionic and noticed this bug immediately as I often play games. Shall I file a new bug report? Thanks in advance. -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890382] [NEW] Gnome-terminal maximize loses one line of terminal output
Public bug reported: Gnome-terminal maximize loses one line of terminal output. Summary: 1. Assume the gnome-terminal currently contains output that exceeds the maximum number of characters of its current display area (ie the text is wrapped) 2. Maximise the gnome-terminal 3. Note that one line of the original content is lost Replication: cd ~/gnomeTerminalBug/replicationTest touch 01.txt touch 02.txt touch 03.txt touch 04.txt touch 05.txt touch 06.txt touch 07.txt touch 08.txt touch 09.txt touch 10.txt touch 11.txt touch 12.txt touch 13.txt touch 14.txt touch 15.txt touch 16.txt touch 17.txt touch 18.txt touch 19.txt touch 20.txt touch 21.txt touch 22.txt touch 23.txt touch 24.txt touch 25.txt touch 26.txt touch 27.txt touch 28.txt touch 29.txt touch 30.txt touch 31.txt touch 32.txt touch 33.txt touch 34.txt touch 35.txt touch 36.txt touch 37.txt touch 38.txt touch 39.txt touch 40.txt touch 41.txt touch 42.txt touch 43.txt touch 44.txt touch 45.txt touch 46.txt touch 47.txt touch 48.txt touch 49.txt touch 50.txt touch 51.txt touch
