[Bug 1859955] Re: Long delays and repeated flashing when docking laptop with multiple monitors
** Summary changed: - Display freaks out when external monitors are attached + Long delays and repeated flashing when docking laptop with multiple monitors ** Tags added: performance -- 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/1859955 Title: Long delays and repeated flashing when docking laptop with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844853] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: automake-1.16/1:1.16.1-4ubuntu3 (s390x) libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el) umockdev/0.13.2-1 (armhf, i386) asterisk/1:16.2.1~dfsg-2build2 (arm64) tracker/2.3.0-1 (armhf) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) cmake-extras/1.3+17.04.20170310-5 (armhf) netplan.io/0.98-0ubuntu1 (ppc64el, i386) dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386) ocaml-cairo2/unknown (armhf) netplan.io/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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 1850932] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: automake-1.16/1:1.16.1-4ubuntu3 (s390x) libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el) umockdev/0.13.2-1 (armhf, i386) asterisk/1:16.2.1~dfsg-2build2 (arm64) tracker/2.3.0-1 (armhf) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) cmake-extras/1.3+17.04.20170310-5 (armhf) netplan.io/0.98-0ubuntu1 (ppc64el, i386) dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386) ocaml-cairo2/unknown (armhf) netplan.io/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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.3-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 1848202] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: automake-1.16/1:1.16.1-4ubuntu3 (s390x) libreoffice/1:6.3.4-0ubuntu0.19.10.1 (ppc64el) umockdev/0.13.2-1 (armhf, i386) asterisk/1:16.2.1~dfsg-2build2 (arm64) tracker/2.3.0-1 (armhf) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) cmake-extras/1.3+17.04.20170310-5 (armhf) netplan.io/0.98-0ubuntu1 (ppc64el, i386) dbus-test-runner/15.04.0+19.04.20190115-0ubuntu1 (armhf, i386) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64, i386) ocaml-cairo2/unknown (armhf) netplan.io/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) openssh/1:8.0p1-6build1 (amd64, armhf, arm64, s390x, i386, ppc64el) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848202 Title: Use after free in gdbus leads to eds segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Can you please run: gsettings list-recursively | grep scal and share the output? -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Thanks. It's very strange that the dimensions of neither image match actual screen resolutions. I guess that's one possible reason why they're not staying full screen -- the window size is not supportable. Another issue I notice from your screenshots is the unusual panel and icons hanging down. This makes me think you might be using some extensions(?). Please try uninstalling all gnome-shell extensions, reboot and retest. We need to uninstall extensions and not just disable them because broken extensions might also fail to honour the disable request. -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Launchpad has imported 23 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=782530. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-05-11T18:58:52+00:00 BenjaminBerg wrote: Because of the method that the dbus proxies are created there is currently a race condition. When an adapter is added it can have an initial "Powered" state of off which is turned on immediately afterwards. However, the signal connect to get the update only happens later. This can be easily reproduced on thinkpads by running "rfkill block 0" and "rfkill unblock 0" while looking at the gnome-control-center bluetooth panel. Attaching a patch that should fix the issue. I hope I didn't totally misunderstand how the whole DBus proxy stuff is supposed to work. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/0 On 2017-05-11T19:03:39+00:00 BenjaminBerg wrote: Created attachment 351663 lib: Rework adapter and device proxy registrations. This fixes a race condition when a property was updated right after the object appeared on the bus. Due to the old implementation the property change would not be registered in that case. This moves the code to use GDBusObjectManagerClient and using the provided GObject properties instead of a separate proxy to avoid the race condition. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/1 On 2017-05-16T09:15:35+00:00 Bugzilla-x wrote: Review of attachment 351663: The patch is unreviewable. Make the hunks bigger and try to split up the changes if at all possible. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/2 On 2017-05-16T11:48:04+00:00 BenjaminBerg wrote: Created attachment 351966 lib: Rework adapter and device proxy registrations. This fixes a race condition when a property was updated right after the object appeared on the bus. Due to the old implementation the property change would not be registered in that case. This moves the code to use GDBusObjectManagerClient and using the provided GObject properties instead of a separate proxy to avoid the race condition. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/3 On 2017-05-16T11:48:15+00:00 BenjaminBerg wrote: Created attachment 351967 lib: Always send "default-adapter-powered" Fix sending of default-adapter-powered in the case that the default adapter is being disabled. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/4 On 2017-05-16T11:48:38+00:00 BenjaminBerg wrote: Created attachment 351968 lib: Force custom icon code override to run The property setter currently contains some magic to modify the icon for certain device types. Send a property change notification to force this code to run after a device has been added. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/5 On 2017-05-16T11:49:01+00:00 BenjaminBerg wrote: There, that is all logical changes split out. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/6 On 2017-05-16T12:27:56+00:00 Bugzilla-x wrote: I won't have time to review this in the short-term, but a dbusmock regression test which shows the problem before, and shows it fixed afterwards would be really useful. See those in gnome-settings-daemon (though they've been broken for a while for different reasons...): https://git.gnome.org//browse/gnome-settings-daemon/tree/tests/gsdtestcase.py https://git.gnome.org//browse/gnome-settings-daemon/tree/plugins/power/test.py Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/7 On 2017-05-16T17:23:35+00:00 BenjaminBerg wrote: The patch might be hard to read as it changes all the property accessors, but really it all boils down to the two questions: * Is it correct to use GDBusObjectManagerClient to keep track of the objects? * Is it good to use GObject properties on the Adapter1/Device1 proxies (instead of manually driving a DBus properties interface proxy)? I agree that dbusmock test would be nice in here. But I
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Launchpad has imported 9 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=789110. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-10-17T16:50:14+00:00 Mario Sánchez Prada wrote: Created attachment 361759 Inconsistency in the bluetooth menu In Endless's fork of GNOME Shell 3.24, we sometimes get an inconsistent state in the system menu for the Bluetooth, that leads to weird situations where you see the menu item as "Off" even if bluetooth is active (and we know that because we can use the BT mouse), with a submenu item showing "Turn Off". See the attached picture for a better visual description of the problem. As far as I can see, this is a problem in master too, patch will be coming soon.. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/9 On 2017-10-17T17:01:17+00:00 Mario Sánchez Prada wrote: Created attachment 361760 1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/10 On 2017-10-17T17:01:34+00:00 Mario Sánchez Prada wrote: Created attachment 361761 2. bluetooth: Be consistent when determining whether Bluetooth is off Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/11 On 2017-10-17T17:13:36+00:00 Florian-muellner wrote: Review of attachment 361760: Whoops Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/12 On 2017-10-17T17:39:40+00:00 Florian-muellner wrote: Review of attachment 361761: > otherwise we risk showing inconsistent states in each place if. I'd be interested in how that sentence continues :-p Joking aside, I don't think this is correct. As far as I can see, "nConnectedDevices == -1" means there is no Bluetooth adapter that is powered on - we can toggle the AirplaneMode property as much as we want (that's what "Turn On/Off" does after all), that's not going to change. So a better option may be to do this._toggleItem.actor.visible = nConnectedDevices > -1; instead ... ::: js/ui/status/bluetooth.js @@ +134,3 @@ +// Bluetooth will be considered 'Off' if either the adapter +// is not available or it's set in irplane mode. *airplane Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/13 On 2017-10-17T19:20:09+00:00 Mario Sánchez Prada wrote: Comment on attachment 361760 1. bluetooth: Add missing 'BluetoothHardwareAirplaneMode' to D-Bus interface (In reply to Florian Müllner from comment #3) > Review of attachment 361760 [details] [review]: > > Whoops Thanks for the review. Commmitted: https://git.gnome.org/browse/gnome-shell/commit/?id=fb3070981c549ad9812d62f8ab868c323ed2ccf5 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1738838/comments/14 On 2017-10-17T19:27:40+00:00 Mario Sánchez Prada wrote: (In reply to Florian Müllner from comment #4) > Review of attachment 361761 [details] [review]: > > > otherwise we risk showing inconsistent states in each place if. > > I'd be interested in how that sentence continues :-p I'd be too, but I can't remember what I had in there :). I suppose it' was something along the lines of "...if the adapter is available but it's set in airplane mode". > Joking aside, I don't think this is correct. As far as I can see, > "nConnectedDevices == -1" means there is no Bluetooth adapter that is > powered on - we can toggle the AirplaneMode property as much as we want > (that's what "Turn On/Off" does after all), that's not going to change. So a > better option may be to do > > this._toggleItem.actor.visible = nConnectedDevices > -1; > > instead ... > > ::: js/ui/status/bluetooth.js > @@ +134,3 @@ > > +// Bluetooth will be considered 'Off' if either the adapter > +// is not available or it's set in irplane mode. > > *airplane I thought the same thing, but I'm not 100% sure on whether it's possible to have a BT adapter that would be "powered on"/"available" and would still report to be in airplane mode (either soft or hard), so I thought the sane thing to do was to check both things, just in case. What looks more clear to me, is that the same condition should be used in both places, since what you want to
[Bug 1849055] Re: gnome-extensions fails to load after boot
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1849055 Title: gnome-extensions fails to load after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
The screenshot was not done perfectly, and it is a tad difficult to get it that way, because it is uncertain how much of the window title bar to include. The dimensions I get are 764x436 on the inset part. (See attachments.) ** Attachment added: "gnome-shell-bug_inset3.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5321008/+files/gnome-shell-bug_inset3.png -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Here is the whole window showing the inset. ** Attachment added: "gnome-shell-bug_3.png.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5321009/+files/gnome-shell-bug_3.png.png -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
I'm not so sure about the waking from suspend triggering it now. I just tried three times, with no problem. -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Confirmed the same bug is still in gnome-shell master (version 3.35). ** Bug watch added: bugzilla.gnome.org/ #789110 https://bugzilla.gnome.org/show_bug.cgi?id=789110 ** Changed in: gnome-shell Importance: Medium => Unknown ** Changed in: gnome-shell Status: Expired => Unknown ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #789110 => bugzilla.gnome.org/ #789110 ** Tags added: focal ** Bug watch added: bugzilla.gnome.org/ #782530 https://bugzilla.gnome.org/show_bug.cgi?id=782530 ** Changed in: gnome-bluetooth Remote watch: GNOME Bug Tracker #782530 => bugzilla.gnome.org/ #782530 ** Changed in: gnome-bluetooth (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-bluetooth (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857236] Re: Failed to load module "canberra-gtk-module"
I searched Synaptic and noticed that the "canberra-gtk-module" package was not installed. I installed the package and I do not get this error any more. Maybe there should be a "Is canberra-gtk-module package installed?" -- 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/1857236 Title: Failed to load module "canberra-gtk-module" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1857236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859970] Re: Screenshots from an area selection have tinted colour when running wayland
** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1859970 Title: Screenshots from an area selection have tinted colour when running wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1859970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859970] Re: orange tint in screenshots when running wayland
Different colour theme, but same bug: https://gitlab.gnome.org/GNOME /gnome-shell/issues/1999 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1999 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1999 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1999 Importance: Unknown Status: Unknown ** Summary changed: - orange tint in screenshots when running wayland + Screenshots from an area selection have tinted colour when running wayland ** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- 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/1859970 Title: Screenshots from an area selection have tinted colour when running wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1859970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
I can imagine some delays could be mutter's fault... (just a theory) If we get a burst of a number of new connector/hotplug/udev events and mutter tries to action each one immediately then it will take a long time and lots of flashing to get through all of them. To avoid that, mutter should be ignoring such events for some short period so that it can group them into a single config change that will complete faster. -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860036] Re: Samsung 85" TV worked for short time, now doesn't
Please run these commands on the machine while the problem is occurring: xrandr > xrandr.txt lspci -k > lspcik.txt dmesg > dmesg.txt and then attach the resulting files. ** 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/1860036 Title: Samsung 85" TV worked for short time, now doesn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860052] Re: gnome-shell crash when typing into file browser dialog in Discord app
[308904.167775] shaggy gnome-shell[29086]: JS object wrapper for GObject 0x55863e548a60 (GSettings) is being released while toggle references are still pending. [308904.168190] shaggy gnome-shell[29086]: GNOME Shell crashed with signal 5 [308904.168190] shaggy gnome-shell[29086]: == Stack trace for context 0x558634ec2380 == (missing stack trace) ** Summary changed: - gnome-shell crash when typing into file browser dialog in Discord app + gnome-shell crash when typing into file browser dialog in Discord app [JS object wrapper for GObject 0x55863e548a60 (GSettings) is being released while toggle references are still pending.] ** Also affects: gjs (Ubuntu) Importance: Undecided Status: 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/1860052 Title: gnome-shell crash when typing into file browser dialog in Discord app [JS object wrapper for GObject 0x55863e548a60 (GSettings) is being released while toggle references are still pending.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1860052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
I would like to understand if the long delay is just the time it takes for the kernel to advertise the new connectors, or if it's some delay in mutter. Separately, yes the desktop should never appear cut in the middle of the screen like that so that part sounds like a mutter bug. We potentially have two separate bugs here. -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
Wow. Already reported, by the same person, 1 bugs ago. Bug 1849955. ** Tags added: eoan ** Also 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695036] Re: multiple screens cannot align askew
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1695036 Title: multiple screens cannot align askew To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1695036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687253] Re: Correct desktop scaling factor not used when hotplugging a monitor (until after rebooting)
Is this problem still happening in current Ubuntu releases? ** Changed in: ubuntu-gnome Status: New => Incomplete ** Changed in: gnome-desktop (Ubuntu) Status: New => Incomplete ** 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-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1687253 Title: Correct desktop scaling factor not used when hotplugging a monitor (until after rebooting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1687253/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849955] Re: Display jumps on dock/undock and on volume/brightness overlay
*** This bug is a duplicate of bug 1859955 *** https://bugs.launchpad.net/bugs/1859955 ** This bug has been marked a duplicate of bug 1859955 Display freaks out when external monitors are attached -- 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/1849955 Title: Display jumps on dock/undock and on volume/brightness overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
Yeah the data we would like to see attached automatically are: lspci -k xrandr Alan, can you please run 'xrandr' before and after docking, and attach them? I suspect the trigger for this confusion is the introduction of new monitor connectors (not just new monitors). Also please run: ls /sys/class/drm before and after docking to see if the results are changing. ** Tags added: multimonitor -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Thanks. That shows your screen is natively 1920x1080 but the current mode is 1600x900. Can you please take a screenshot and tell us the dimensions of the screenshot image vs the dimensions of the the small fullscreen window within it? 1920x1080 60.05 + 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82* Also, if the problem continues then please try to write down the steps required to reproduce it. -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.
** Changed in: gnome-settings-daemon 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/1859867 Title: The bluetooth gets started automatically whenever a network is selected after turning on the wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1859867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860057] [NEW] /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 1849249 *** https://bugs.launchpad.net/bugs/1849249 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 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/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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Also tracking in: https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 as well the existing: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b ** Tags added: focal ** 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/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 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 1849249 *** https://bugs.launchpad.net/bugs/1849249 ** This bug has been marked a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) -- 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 1859879] Re: PNG images are not displayed
** Changed in: ubuntuone-shotwell-plugin Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1859879 Title: PNG images are not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1859879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.
I reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2113 but that then moved to: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/288 ** Project changed: gnome-shell => gnome-settings-daemon ** Changed in: gnome-settings-daemon Status: New => Unknown ** Changed in: gnome-settings-daemon Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #2113 => gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #288 ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Triaged -- 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/1859867 Title: The bluetooth gets started automatically whenever a network is selected after turning on the wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1859867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_uni
^^^ Looks like a typo. See bug 1860052 instead. -- 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/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+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)
This is still 100% reproducible with with an up-to-date Ubuntu 20.04. -- 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 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_uni
I have created a more specific bug report, for a crash triggered from the file browser in the Discord app, here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664 -- 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/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860052] [NEW] gnome-shell crash when typing into file browser dialog in Discord app
Public bug reported: This is a specific instance of https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1736664 I cannot see the journal that will be attached to the bug in advance, so I can't copy the error message to the summary. While using the Discord app I clicked the (+) button in order to select a file to upload into a chat, which led to the normal file browser dialog. I then typed either "/hom" or "~/.l" or ".loc" and before the interface could update to show that I had typed anything it froze, then a few seconds later almost all programs had closed and gnome-shell was restarting after having crashed. I am running Ubuntu 19.10, gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_1065_75_oem_61 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 15:18:26 2020 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 InstallationDate: Installed on 2019-12-28 (19 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-12-30 (17 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1860052 Title: gnome-shell crash when typing into file browser dialog in Discord app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_uni
https://errors.ubuntu.com/oops/89b39b4a-38b3-11ea-b8ae-fa163e102db1 https://errors.ubuntu.com/oops/9d568826-30e1-11ea-a775-fa163ee63de6 these two crashes seem to be this bug. this is a recurring (but not easily reproducible) problem for me, most often triggered by typing into the File > Open dialog in various applications (typing in order to navigate to a file path, often starting with / or .) -- 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/1736664 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv() from g_log() from gjs_callback_closure() from ffi_closure_unix64_inner() [any error message logged from JavaScript will look like this] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751593] Re: Weird black border flickers around windows in Wayland sessions
** Changed in: mutter Status: New => Fix Released -- 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/1751593 Title: Weird black border flickers around windows in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1751593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
Unfortunately it is back. I did notice this time that it happened just after waking from suspend, and I think that has been the pattern. This should be useful. Here is the xrandr output. ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320968/+files/xrandr.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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860037] Re: Typo in the Russian interface of the package
Thanks for your report! It's an upstream issue, and should preferably be corrected there. https://l10n.gnome.org/vertimus/gnome-control-center/master/po/ru/ It may be fixed in Ubuntu only for now via the Launchpad interface. https://translations.launchpad.net/ubuntu/focal/+source/gnome-control- center/+pots/gnome-control- center-2.0/ru/+translate?search=%D0%B2%D1%85%D0%BE%D0%B4%D0%B5+%D1%81 ** Package changed: gnome-control-center (Ubuntu) => ubuntu-translations ** Changed in: ubuntu-translations Importance: Undecided => Medium ** Changed in: ubuntu-translations Status: New => Triaged ** Changed in: ubuntu-translations Assignee: (unassigned) => Russian Ubuntu Translators (ubuntu-l10n-ru) -- 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/1860037 Title: Typo in the Russian interface of the package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1860037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859879] Re: PNG images are not displayed
I think I know what the problem is now. I opened the .png file with "Shotwell" instead of "Shotwell Viewer". Maybe the .jpg/.tif/.bmp files were displayed in Shotwell Viewer instead of Shotwell? That must be correct because I can not reproduce the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1859879 Title: PNG images are not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1859879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860037] [NEW] Typo in the Russian interface of the package
Public bug reported: The Russian interface of the gnome-control-center package contains a typo. A typo is highlighted in the attached screenshot. Instead of "входе с систему" you must specify "входе в систему". Ubuntu version is 18.04.3 LTS gnome-control-center version is 1:3.28.2-0ubuntu0.18.04.5 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: typo ** Attachment added: "Снимок экрана от 2020-01-16 22-32-14.png" https://bugs.launchpad.net/bugs/1860037/+attachment/5320936/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-01-16%2022-32-14.png -- 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/1860037 Title: Typo in the Russian interface of the package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1860037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860036] [NEW] Samsung 85" TV worked for short time, now doesn't
Public bug reported: I installed Ubuntu 18.04 on a media PC connected to a samsung smart TV. this morning the TV was no longer displaying, and reporting that the resolution was not possible to display. I tinkered with the settings, and now the TV will not connect to the PC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:47:50 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' b'org.gnome.desktop.interface' b'gtk-theme' b"'Adwaita-dark'" InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860036 Title: Samsung 85" TV worked for short time, now doesn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860005] Re: "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop
** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop- icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1860005 Title: "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1860005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860005] [NEW] "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop
Public bug reported: Ubuntu 19.10 Nautilus (Files) 3.34.1-stable (nautilus: Installed: 1:3.34.1-1ubuntu1) Asking whether "Run", "Run in Terminal" or "Display" script after double clicking is expected. "Ask what to do" option is set in Nautilus (Files) Behavior preferences (see attached screenshots). "Ask what to do" popup dialogue doesn't appear after double clicking Bash/shell script file from Desktop SHELL. When script is executed from Desktop and other FOLDERS, "Ask what to do" popup appears. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 17:50:44 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(683, 700)' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 amd64 apport-bug bash eoan files gnome nautilus scripts ** Attachment added: "screensots are inside the attached zip archive" https://bugs.launchpad.net/bugs/1860005/+attachment/5320874/+files/Screens.zip -- 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/1860005 Title: "Ask what to do" popup doesn't appear when scripts are executed directly from Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1860005/+subscriptions -- 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
Hello Adam, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-eoan ** Tags added: verification-needed-eoan -- 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 1850932] Re: [SRU] Backport 2.62.3-2
Hello Iain, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-eoan -- 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.3-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 1848202] Re: Use after free in gdbus leads to eds segfaults
Hello errors.ubuntu.com, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.3-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-eoan ** Tags added: verification-needed verification-needed-eoan -- 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/1848202 Title: Use after free in gdbus leads to eds segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1283874] Re: rhythmbox crashed with SIGABRT in do_sigtimedwait()
Bug report won't expire due to bug watch. No reply to comment #8 from reporter so closing. ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Invalid -- 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/1283874 Title: rhythmbox crashed with SIGABRT in do_sigtimedwait() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1283874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859260] Re: Cant go back to primary monitor when app indicator menu is open
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1859260 Title: Cant go back to primary monitor when app indicator menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1859260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734034] Re: Cannot Use the Character U07AE on any Editor
It's maybe worth reporting upstream on https://gitlab.gnome.org/GNOME/gtk/issues ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1734034 Title: Cannot Use the Character U07AE on any Editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859899] Re: Please add a ZFS gui
** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1859899 Title: Please add a ZFS gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1859899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859879] Re: PNG images are not displayed
Thank you for your bug report. Could you provide the details requested on the gitlab ticket? ' Please open the file from the commandline with shotwell /path/to/png >shotwell-viewer.log 2>&1 and attach that file here, please' ** Changed in: shotwell (Ubuntu) Importance: Undecided => Low ** Changed in: shotwell (Ubuntu) Status: New => Triaged ** Also affects: ubuntuone-shotwell-plugin via https://gitlab.gnome.org/GNOME/shotwell/issues/186 Importance: Unknown Status: Unknown ** Changed in: shotwell (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1859879 Title: PNG images are not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1859879/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
Thank you for your bug report. could you attach the full 'journalctl -b 0' log from the system after triggering the bug? Also could you give some details on the videocard/driver you are using (Daniel, Marco, should we update the apport hook to include those informations?) -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859970] Re: orange tint in screenshots when running wayland
The screenshoting is handled by gnome-shell itself nowadays, reassigning there ** Package changed: gnome-screenshot (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/1859970 Title: orange tint in screenshots when running wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859970] [NEW] orange tint in screenshots when running wayland
You have been subscribed to a public bug: All my screenshots taken on 20.04 with wayland have an orange tint to them. This appears to be the overlay which you get when selecting an area. Full screen screenshots and window screenshots are unaffected, only area screenshots appear to have the problem. Steps to reproduce Login to a wayland session Hold down Shift and Press PrintScreen Select an area to screenshot Navigate to ~/Pictures Open the picture you just took Expected outcome Screenshot of area taken as it would have been on screen Actual outcome Screenshot is taken, but has an orange border and overlay. (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:50:50 2020 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug focal wayland-session -- orange tint in screenshots when running wayland https://bugs.launchpad.net/bugs/1859970 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 1731070] Re: "_Skip" button label translation not correctly applied
Sebastien, the translated string is not applied only in install-only mode. Not sure what causes the issue, other translated strings are showing without any problem. I checked it multiple times and it is the same every time. -- 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/1731070 Title: "_Skip" button label translation not correctly applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1731070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731070] Re: "_Skip" button label translation not correctly applied
@Asciiwolf, thanks for the feedback. The edit you did is a bit unclear to me is 'not correctly applied' or 'not correctly applied in install- only mode'? I'm unsure what's the difference/why ubiquity would behave differently from a live session than it does for an ubiqity-install -- 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/1731070 Title: "_Skip" button label translation not correctly applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1731070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
** Tags added: fixed-in-3.35.4 fixed-upstream -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+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%)
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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 1731070] Re: "_Skip" button label not translatable
** Changed in: ubiquity (Ubuntu) Status: Fix Released => Confirmed ** Tags added: focal ** Summary changed: - "_Skip" button label not translatable + "_Skip" button label translation not correctly applied ** Description changed: The "Skip" string is showing as untranslated in non-English Ubuntu installation. This is because "Skip" is in the translation template, but "_Skip" is not. (See comment #7.) + + edit: I have re-opened this ticket. The "_Skip" button is now + translatable, however the translation is still not correctly applied, + see comment #17. -- 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/1731070 Title: "_Skip" button label translation not correctly applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1731070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859963] [NEW] Info package on Ubuntu Focal comes preinstalled with desktop file
You have been subscribed to a public bug by AsciiWolf (asciiwolf): The "info" package that is preinstalled on Ubuntu Focal ships with a "info.desktop" file that adds a "TeXInfo" desktop launcher displayed among other apps. The launcher opens a terminal application that is confusing and user unfriendly for many users. Users that actually want to use info can do it using a terminal. Please, consider removing the desktop file or at least set it to not show among other apps. ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- Info package on Ubuntu Focal comes preinstalled with desktop file https://bugs.launchpad.net/bugs/1859963 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731070] Re: "_Skip" button label not translatable
I have just tried installing Ubuntu Focal from latest daily iso and the Skip button was correctly translated only when clicking "Try Ubuntu" on the Ubiquity main screen, then running the installer manually using a desktop icon. When I ran the installer directly using "Install Ubuntu" button, the Skip button was still untranslated for some reason. -- 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/1731070 Title: "_Skip" button label not translatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1731070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859960] [NEW] Livepatch polkit rules strings are not translatable
Public bug reported: The "Manage Livepatch" and "Authentication is required to enable Livepatch" translatable strings from /usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to be available to translate on Launchpad. They were translatable and their translation was correctly applied in Bionic, however since then (Cosmic, Disco, Eoan, Focal), they are untranslated and not available on Launchpad. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- 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/1859960 Title: Livepatch polkit rules strings are not translatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1859960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859960] [NEW] Livepatch polkit rules strings are not translatable
You have been subscribed to a public bug by AsciiWolf (asciiwolf): The "Manage Livepatch" and "Authentication is required to enable Livepatch" translatable strings from /usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to be available to translate on Launchpad. They were translatable and their translation was correctly applied in Bionic, however since then (Cosmic, Disco, Eoan, Focal), they are untranslated and not available on Launchpad. ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal l10n -- Livepatch polkit rules strings are not translatable https://bugs.launchpad.net/bugs/1859960 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
Comparison: Ubuntu on Wayland on same hardware: https://www.youtube.com/watch?v=rw0cq5FwpHU Less flicker than Ubuntu, and faster it seems. Around 13 seconds. -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] Re: Display freaks out when external monitors are attached
Comparison: Windows 10 on the same hardware: https://www.youtube.com/watch?v=VEvidzgedGk Process takes 5 seconds, no flicker. -- 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859955] [NEW] Display freaks out when external monitors are attached
Public bug reported: Running Focal on my ThinkPad T450, but not unique to this release as it happened on 19.10 (and probably older releases too). Steps to reproduce. While running GNOME Shell, attach the laptop to additional external monitors. (I'm using a docking station, but equally you can attach them via the video ports on the laptop itself) Expected outcome Desktop on 1 monitor goes away. Desktop comes back on N monitors. Actual outcome Laptop display goes black Laptop display comes back, moved 50% horizontally One external monitor comes on Laptop display goes back to normal Second external monitor comes on All three displays go off again Laptop display comes on again alone Laptop display goes off again laptop display comes on again External monitors come back on again System is usable. The entire process takes twenty seconds. https://www.youtube.com/watch?v=QuSudpxVOao ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 10:21:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (710 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-08 (7 days ago) ** 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/1859955 Title: Display freaks out when external monitors are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
Launchpad has imported 16 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=787568. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-09-12T01:16:46+00:00 Adamw-c wrote: There's some discussion of this in https://bugzilla.gnome.org/show_bug.cgi?id=787240 , but that's really about another crash, so I figure this deserves its own report. Julian Andres Klode (in #787240), myself and Mikhail Gavrilov (in https://bugzilla.redhat.com/show_bug.cgi?id=1490072 ), and Jean-Baptiste Lallement (in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1715330 ) have all seen gnome-shell crash this way (taking down our entire sessions, natch) - a segfault in mutter _cogl_boxed_value_set_x , apparently because somehow it's getting called with NULL as its target. Myself, Julian and Mikhail saw it when opening / starting VMs in virt-manager and Boxes; the Ubuntu reproducer seems to possibly involve some kind of Ubuntu-specific update thing, but these are the cited steps: Test Case: Pre-requisites: Package update that downloads a payload and download fails (ie flash plugin) 1. Wait until the update-notifier dialog informing the user about the download failure shows up 2. Click on the 'Execute' buitton 3. Enter your credentials 4. Proceed with the download Expected result The package is downloaded Actual result This crash happens when the authentication window is displayed Myself, Mikhail and Jean-Baptiste all reported from 3.25.91, but I think Julian may have tested with something more recent. I don't see any changes between 3.25.91 and 3.25.92 which really look like they ought to fix this in any case. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/8 On 2017-09-12T04:13:13+00:00 Jonas Ådahl wrote: The bug is in gnome-shell, so moving there. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/10 On 2017-09-12T04:25:03+00:00 Jonas Ådahl wrote: Created attachment 359569 inhibitShortcuts: Don't destroy actor when hiding The same dialog can be shown multiple times; to not crash when that happens we need to avoid destroying the actor when hiding, otherwise we'll crash when running code that assumes it is still valid. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/11 On 2017-09-12T04:27:26+00:00 Jonas Ådahl wrote: To actually reproduce this reliably, the patch from bug 787570 is needed. On my set up, this exposes a gtk+/virt-manager bug resulting in the inhibit request being created and destroyed repeatedly. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/12 On 2017-09-12T04:28:08+00:00 Jonas Ådahl wrote: Uh, must have slipped. Reopening. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/13 On 2017-09-12T07:04:47+00:00 Ofourdan wrote: The issue is that virt-manager issues a grab() when it gains keyboard focus, and an ungrab() when it loses the keyboard focus. On Wayland, the grab()/ungrab() being wired to the shortcut inhibit mechanism, which in turn shows the dialog, therefore takes focus away from the virt-manager causes the continuous flickering. The solution, or at least a compromise, is to keep the dialog around even if the shortcut inhibit is cancelled by the client, so that the user is forced to make a choice that we can reuse on the next request. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1715330/comments/14 On 2017-09-12T08:33:34+00:00 Ofourdan wrote: Created attachment 359585 [PATCH] wayland: Keep the inhibit shortcut dialog On Wayland, the grab()/ungrab() in gtk+/gdk are wired to the shortcut inhibitor mechanism, which in turn shows the dialog, which can take focus away from the client window when the dialog is shown. If the client issues an ungrab() when the keyboard focus is lost, we would hide the dialog, causing the keyboard focus to be returned to the client surface, which in turn would issue a new grab(), so forth and so on, causing a continuous show/hide of the shortcut inhibitor dialog. To avoid this issue, keep the dialog around even if the shortcut inhibit is canceled by the client, so that the user is forced to make a choice that we can reuse on the next request without showing the dialog
[Bug 1720838] Re: Nvidia gnome control center scale gets overridden on reboot
Launchpad has imported 3 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=788483. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-10-03T20:18:57+00:00 Thomas Cross wrote: Created attachment 360874 screenshot of where I go to keep setting the scale Operating System: Ubuntu 17.10 Beta 2 How to reproduce: When I set the scale to 200% on Ubuntu 17.10 Beta 2 it sets it correctly for my session. If I reboot then the scale is reset back to 100% but the value on the control center "displays" section shows "200%". I don't think this happens till I install the Nvidia driver by performing: ubuntu-drivers devices sudo apt-get install nvidia-xxx Work Around: To work around it I save the scale to 100% then save it back to 200%. After rebooting I have to do this every time. Logs, settings, screenshots, more details, etc: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720838 Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720838/comments/2 On 2017-10-03T21:03:10+00:00 Andre Klapper wrote: Thanks for reporting this. Which mutter version is this about? Setting the "Version" field is welcome. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720838/comments/3 On 2017-10-03T22:31:58+00:00 Thomas Cross wrote: Hi Andre, Thanks for asking. Please continue to let me know how I can help. tcross@karen:~$ mutter --version mutter 3.26.0 Copyright © 2001-2011 Havoc Pennington, Red Hat, Inc., and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720838/comments/4 ** Changed in: mutter Status: Unknown => Confirmed ** Changed in: mutter Importance: Unknown => Medium -- 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/1720838 Title: Nvidia gnome control center scale gets overridden on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1720838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728412] Re: Titlebar of firefox does not respond to touch screen
Launchpad has imported 22 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=770185. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-08-21T05:42:58+00:00 Strangiato Xanadu wrote: steps to reproduce start Gnome on Wayland session from GDM login manager open any gtk2 (gimp), qt4 (vlc player) or qt5 (qupzilla or smplayer) app use touchscreen to drag or close the app window nothing happens, touchscreen does no effect on window title bar This problem does not happen with gtk3 apps running under Wayland. Tested on Antergos (Arch-based). Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/0 On 2017-03-18T21:25:05+00:00 Strangiato Xanadu wrote: This problem is still present on 3.24 RC. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/1 On 2017-06-17T01:10:03+00:00 Gnome-k wrote: Identical behaviour still seen on 3.24.2 Weirdly enough it also seems to affect Firefox, despite that having been built with --enable-default-toolkit=cairo-gtk3 Is this on any dev's radar? It's been a problem for two releases now. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/2 On 2017-06-17T01:13:46+00:00 Gnome-k wrote: Strangely enough, I see the inverse behaviour with a pen (on a Surface Pro 3) - GIMP, SMPlayer, Firefox are all movable via the titlebar with the pen, whereas e.g. Files, Evolution, gedit are not. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/3 On 2017-06-17T01:18:54+00:00 Gnome-k wrote: Sorry for spamming this bug... when using the pen, the close button works in all cases, but for touch, the functionality of close matches that of drag. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/4 On 2017-06-17T01:28:18+00:00 Strangiato Xanadu wrote: (In reply to Stephen from comment #2) > Weirdly enough it also seems to affect Firefox, despite that having been > built with --enable-default-toolkit=cairo-gtk3 > Firefox gtk3 runs under xwayland. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/5 On 2017-09-02T01:55:55+00:00 dngreengas wrote: I can confirm this with Firefox. If I use a theme that has its own close button, it works just fine. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/6 On 2017-09-20T03:27:58+00:00 Strangiato Xanadu wrote: Gnome 3.26 has the same problem. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/7 On 2017-10-31T21:29:52+00:00 Sebastien Bacher wrote: reported on Ubuntu as well, https://bugs.launchpad.net/gnome- shell/+bug/1728412 Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/32 On 2017-11-02T04:31:02+00:00 Jonas Ådahl wrote: *** Bug 786910 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/33 On 2017-11-02T04:31:22+00:00 Jonas Ådahl wrote: *** Bug 774947 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/34 On 2017-11-18T23:29:18+00:00 WilloVincent wrote: Can confirm this for Shell 3.26.2 and mutter 3.26.2 on Arch Linux. I can't interact with the titlebar of XWayland apps via touchscreen. After dismissing the onscreen keyboard I can't get it back by tapping on a text entry field. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/36 On 2018-03-16T21:32:00+00:00 Strangiato Xanadu wrote: Gnome 3.28 has the same problem on Arch Linux. Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/37 On 2018-03-17T14:55:51+00:00 Badshah400-s wrote: Not only on Arch; confirming it's also present on openSUSE Tumbleweed with Gnome 3.28 Reply at: https://bugs.launchpad.net/mutter/+bug/1728412/comments/38
[Bug 1716434] Re: Please revert "Call cogl_xlib_renderer_set_threaded_swap_wait_enabled()" to avoid high cpu usage when constantly rendering
Launchpad has imported 111 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=781835. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-04-27T13:41:23+00:00 Ht990332 wrote: As per bug 779039#c14, this checkin https://git.gnome.org/browse/mutter/commit/?id=383ba566bd7c2a76d0856015a66e47caedef06b6 makes gnome-shell use ~80% cpu of one core out of 4 (I am running a skylake corei5) constantly when running something like glxgears. Reverting the patch brings down cpu usage to around 3% when running glxgears. In addition, this makes my cpu temperature increase by ~5 degrees. GPU temperature and usage don't seem to be affect. Only CPU usage is. I am using a NVIDIA kepler card. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/0 On 2017-04-27T13:46:22+00:00 Ht990332 wrote: I forgot to mention that I had asked a nvidia developer about this and he said it was due to the overhead of many xlib calls. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/1 On 2017-04-27T18:36:03+00:00 apemax wrote: I can also confirm this issue, gnome-shell hits around 80% CPU usage on one core when running glxgears, It also causes stuttering in all games I have tried as well. Reverting the patch mentioned by Hussam brings the CPU usage back down to normal levels. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/2 On 2017-04-27T18:44:19+00:00 Alec wrote: I have also encountered this issue on the Nvidia proprietary driver. Reverting the patch fixes the problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/3 On 2017-04-27T22:18:42+00:00 DeadMetaler wrote: I make a screenshot of cpu usage before and after applying Call-coglxlibrenderersetthreadedswapwaitenabled.patch http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62.png I also noticed that this patch have improved responsiveness when moving windows. But now, the animations of the Gnome Shell to lag even more. Now without the load on the CPU, the decrease in FPS became visible. This is all tested on a proprietary Nvidia + 650GTX. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/4 On 2017-04-28T17:39:11+00:00 Alec wrote: (In reply to Maxim from comment #4) > I make a screenshot of cpu usage before and after applying > Call-coglxlibrenderersetthreadedswapwaitenabled.patch > http://storage4.static.itmages.ru/i/17/0411/h_1491948046_9928347_1598f98b62. > png > > > I also noticed that this patch have improved responsiveness when moving > windows. But now, the animations of the Gnome Shell to lag even more. Now > without the load on the CPU, the decrease in FPS became visible. This is all > tested on a proprietary Nvidia + 650GTX. I have also noticed this behaviour Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/5 On 2017-04-29T18:44:20+00:00 Promolecule wrote: I am seriously wondering why no devs have noticed this yet. This bug seems to affect literally everyone who uses an NVIDIA gpu. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/6 On 2017-05-03T01:51:44+00:00 Fau-l wrote: I've been experiencing sluggish animations in gnome-shell after updating to v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no integrated GPU is present. The previous Gnome version did not show this behaviour. I reverted the commit: https://git.gnome.org/browse/mutter/commit?id=383ba566bd7c2a76d0856015a66e47caedef06b6 as mentioned by somebody on the Arch Forums and this fixed the issue for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1716434/comments/7 On 2017-05-03T02:06:35+00:00 Fau-l wrote: (In reply to Frank from comment #7) > I've been experiencing sluggish animations in gnome-shell after updating to > v3.24.1 on ArchLinux on my laptop with dedicated Nvidia GPU (NVS 5100M); no > integrated GPU is present. > > The previous Gnome version did not show this behaviour. > > I reverted the commit: > https://git.gnome.org/browse/mutter/ >
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I do not have any GNOME shell extension, and extensions are disable in "Tweaks", but problem with copy paste/paste exits. I can also confirm that double-copy works in some cases. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751593] Re: Weird black border flickers around windows in Wayland sessions
** Tags added: fixed-in-3.35.4 fixed-upstream -- 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/1751593 Title: Weird black border flickers around windows in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1751593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740484] Re: video corruption with amd RX560 and 2k display
** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix -- 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/1740484 Title: video corruption with amd RX560 and 2k display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730410] Re: Window full-screen size when Firefox starts
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1730410 Title: Window full-screen size when Firefox starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1730410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1729170] Re: gnome window manager lacks keybindings
*** This bug is a duplicate of bug 1710421 *** https://bugs.launchpad.net/bugs/1710421 Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1710421 Keyboard accelerators for window menus aren't implemented -- 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/1729170 Title: gnome window manager lacks keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729170/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734034] Re: Cannot Use the Character U07AE on any Editor
** Tags removed: artful -- 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/1734034 Title: Cannot Use the Character U07AE on any Editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state()
** Tags added: fixed-in-3.34.4 -- 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/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1859259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state()
** Changed in: mutter Status: Unknown => Fix Released -- 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/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1859259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518757] Re: no window shadows after maximizing with double click and dragging down window to restore
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1518757 Title: no window shadows after maximizing with double click and dragging down window to restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1518757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1469173] Re: Bottom portion of screen is black/blank with 4 monitor display
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1469173 Title: Bottom portion of screen is black/blank with 4 monitor display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1469173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1357008] Re: Doesn't look for themes in user's directory
Thank you for reporting this bug to Ubuntu. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1357008 Title: Doesn't look for themes in user's directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1357008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644342] Re: Cannot select list item overlap with top panel using mouse
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1644342 Title: Cannot select list item overlap with top panel using mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1644342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1649307] Re: LibreOffice Does Not Bring Windows to Front on GNOME/Wayland
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1649307 Title: LibreOffice Does Not Bring Windows to Front on GNOME/Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1649307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647084] Re: i915 multiple display halt system when moving windows
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1647084 Title: i915 multiple display halt system when moving windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1647084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715330] Re: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x()
** Bug watch added: bugzilla.gnome.org/ #787568 https://bugzilla.gnome.org/show_bug.cgi?id=787568 ** Changed in: mutter Importance: Critical => Unknown ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #787568 => bugzilla.gnome.org/ #787568 ** No longer affects: mutter (Ubuntu Artful) ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released -- 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/1715330 Title: gnome-shell crashed with SIGSEGV in _cogl_boxed_value_set_x() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1715330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716434] Re: Please revert "Call cogl_xlib_renderer_set_threaded_swap_wait_enabled()" to avoid high cpu usage when constantly rendering
** Bug watch added: bugzilla.gnome.org/ #781835 https://bugzilla.gnome.org/show_bug.cgi?id=781835 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Confirmed => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #781835 => bugzilla.gnome.org/ #781835 ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- 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/1716434 Title: Please revert "Call cogl_xlib_renderer_set_threaded_swap_wait_enabled()" to avoid high cpu usage when constantly rendering To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1716434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728412] Re: Titlebar of firefox does not respond to touch screen
** Bug watch added: bugzilla.gnome.org/ #770185 https://bugzilla.gnome.org/show_bug.cgi?id=770185 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #770185 => bugzilla.gnome.org/ #770185 ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: gnome-shell (Ubuntu) -- 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/1728412 Title: Titlebar of firefox does not respond to touch screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1728412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720838] Re: Nvidia gnome control center scale gets overridden on reboot
** Bug watch added: bugzilla.gnome.org/ #788483 https://bugzilla.gnome.org/show_bug.cgi?id=788483 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Confirmed => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #788483 => bugzilla.gnome.org/ #788483 ** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix -- 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/1720838 Title: Nvidia gnome control center scale gets overridden on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1720838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720760] Re: Under Xorg app windows unscaled until gnome tweaks is launched.
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1720760 Title: Under Xorg app windows unscaled until gnome tweaks is launched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848951] Re: High CPU when just moving the mouse
** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- 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/1848951 Title: High CPU when just moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1848951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717446] Re: Window menus close as soon as they open
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/1717446 Title: Window menus close as soon as they open To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1717446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
