[Bug 1796549] Re: Xorg sessions have higher output lag than Wayland sessions
** Description changed: - https://gitlab.gnome.org/GNOME/mutter/issues/334 + Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/334 + Upstream fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/281 --- Xorg sessions have higher output lag than Wayland sessions. Test case: Grab a window with the mouse and drag it around smoothly. Expected: the same minimal gap between the cursor and the window's title bar in both Xorg and Wayland sessions. Observed: a bigger gap (higher latency) in Xorg sessions. I only realized this was a bug when I stumbled on a fix while experimenting with the presentation timing logic in mutter, so assigning to myself. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.0-4 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Sun Oct 7 17:22:48 2018 InstallationDate: Installed on 2018-05-26 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #334 https://gitlab.gnome.org/GNOME/mutter/issues/334 ** Also affects: fmutter via https://gitlab.gnome.org/GNOME/mutter/issues/334 Importance: Unknown Status: Unknown ** Project changed: fmutter => mutter -- 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/1796549 Title: Xorg sessions have higher output lag than Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1796549/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
** Changed in: nautilus Status: New => Fix Released -- 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/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1094841] Re: Often when copying large file over cifs mounted network share nautilus freezes after a while
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1094841 Title: Often when copying large file over cifs mounted network share nautilus freezes after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1094841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1323212] Re: sFTP very slow to connect and causes Nautilus to randomly freeze
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1323212 Title: sFTP very slow to connect and causes Nautilus to randomly freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1323212/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate
[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/1808908 Title: Screen not locked when coming out of suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721248] Re: "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report."
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report." To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1721248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820936] Re: When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux"
*** This bug is a duplicate of bug 1812527 *** https://bugs.launchpad.net/bugs/1812527 This sounds most likely to be bug 1812527. ** This bug has been marked a duplicate of bug 1812527 [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] -- 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/1820936 Title: When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548358] Re: Screenshot option shows error while listening to music
*** This bug is a duplicate of bug 1721248 *** https://bugs.launchpad.net/bugs/1721248 Ubuntu 10.04 is no longer supported. But the discussion continues in bug 1721248. ** This bug has been marked a duplicate of bug 1721248 "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/548358 Title: Screenshot option shows error while listening to music To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/548358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820869] Re: totem could not take screenshot
*** This bug is a duplicate of bug 1721248 *** https://bugs.launchpad.net/bugs/1721248 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1800840, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1800840 totem fails to create screenshot ** This bug is no longer a duplicate of bug 1800840 totem fails to create screenshot ** This bug has been marked a duplicate of bug 1721248 Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1820869 Title: totem could not take screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1820869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
** Tags added: bionic ** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Confirmed ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Confirmed ** Changed in: mutter (Ubuntu) Status: Triaged => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #146 https://gitlab.gnome.org/GNOME/mutter/issues/146 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/146 Importance: Unknown Status: Unknown ** Summary changed: - Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos + "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report." -- 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/1721248 Title: "Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report." To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1721248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800840] Re: totem fails to create screenshot
*** This bug is a duplicate of bug 1721248 *** https://bugs.launchpad.net/bugs/1721248 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1721248, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: disco ** This bug has been marked a duplicate of bug 1721248 Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1800840 Title: totem fails to create screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1800840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820883] Re: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"]
** Summary changed: - totem comma key does not go 1 frame back + totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"] ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1820883 Title: totem comma key does not go 1 frame back ["gst_segment_do_seek: assertion 'start <= stop' failed"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1820883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items
Yes, gnome-shell should still be smart enough to put the right and down arrows in alignment. Please log a bug: https://gitlab.gnome.org/GNOME /gnome-shell/issues Although upstream the GNOME developers might argue that the bug is hidden without extensions, and therefore may choose to not fix 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/1820775 Title: gnome-shell's user menu/item is not aligned like other menu items To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: Confirmed => 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820866] Re: File dialog extremely slow
It looks like the file dialog is being slowed by scanning network shares. Please try removing those (temporarily) and tell us if the problem goes away. Please also reproduce the problem and then run: dmesg > dmesg.txt and attach the file 'dmesg.txt' to this bug. ** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)
Please: 1. Reproduce the problem. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the file 'prevboot.txt' to this bug. -- 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/1817682 Title: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)
If the problem relates to workspace switching in 18.04 then there's also a good chance that this is bug 1812527. Sorry I am unable to reproduce any such problems here, yet. -- 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/1817682 Title: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
This is a bug/limitation of the graphics driver itself. So I will reassign this bug to NVIDIA. Also Mitchell, please let us know which AMD Xorg graphics driver you are using (attach a Xorg.log?). As luck would have it, one user upstream found a solution for NVIDIA documented here: https://gitlab.gnome.org/GNOME/mutter/issues/503#note_463305 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #503 https://gitlab.gnome.org/GNOME/mutter/issues/503 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/503 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-418 (Ubuntu) -- 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
dreamcat4, NVIDIA driver version 415 doesn't exist in Ubuntu so we can't log bugs against that. I have instead logged it against version 418, assuming the problem is still there. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Invalid ** Tags added: multimonitor -- 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820936] [NEW] When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux"
Public bug reported: I use "PlayOnLinux" to run a windows application "KakaoTalk". But recently, when I run the "KakaoTalk" on "PlayOnLinux", if I switch the workspace, gnome-shell is easy to crash, sometimes I will be log out, I need to log in again. But If "KakaoTalk" on "PlayOnLinux" not open, it just on system tray, the probability of occurrence is much lower. The bug just happen after one day I update the system. When I disabled animation between workspace, the probability of occurrence is much lower, but it still happened. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 09:33:59 2019 DisplayManager: lightdm InstallationDate: Installed on 2017-12-29 (445 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-14 (217 days ago) ** 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/1820936 Title: When I switch workspace, gnome-shell will have a very high chance of crashing, especially running "PlayOnLinux" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820282] Re: FTBFS: test failure during build in lp
This bug was fixed in the package zeromq3 - 4.3.1-3ubuntu2 --- zeromq3 (4.3.1-3ubuntu2) disco; urgency=medium * d/libzmq5.symbols: revert previous symbols update, as that came from a draft API that was mistakenly enabled in a local build when a .git directory was detected. -- Andreas Hasenack Tue, 19 Mar 2019 17:01:01 + ** Changed in: zeromq3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1820282 Title: FTBFS: test failure during build in lp To manage notifications about this bug go to: https://bugs.launchpad.net/zeromq/+bug/1820282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816264] Re: software center stuck on Chrome package dialog
I previously launched it through the UI, so I didn't see the console output; now I've launched it from the terminal. In the freshly booted VM: 1. open two terminal windows (window A and window B) 2. in terminal window A, run "gnome-software" 3. click on a random app (I'm clicking on "powershell" under "Editor's Picks") 4. press the "X" in the top-right corner to close the window [note: gnome-software stays running in the background!] 5. in window B, run "gnome-software" 6. focus the window that just opened 7. attempt to click the left-arrow in the upper-right corner of the window At this point, window A shows the following (with an assertion failure that sounds relevant): user@ubuntu1810vm:~$ gnome-software 01:13:19:0703 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, shell-extensions, ubuntuone, appstream, desktop-menu-path, hardcoded-blacklist, hardcoded-featured, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, steam, ubuntu-reviews, packagekit-history, provenance, snap, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 01:13:19:0703 Gs disabled plugins: dpkg, dummy, repos, epiphany, odrs 01:13:20:0828 Gs Only 0 apps for recent list, hiding 01:13:33:0176 Gs gs_shell_go_back: assertion '!g_queue_is_empty (priv->back_entry_stack)' failed journalctl doesn't show anything interesting: Mär 20 02:13:13 ubuntu1810vm systemd-timesyncd[368]: Timed out waiting for reply from [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com). Mär 20 02:13:19 ubuntu1810vm dbus-daemon[497]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.190' (uid=1000 pid=1759 comm="gnome-software " label="unconfined") Mär 20 02:13:19 ubuntu1810vm systemd[1]: Starting Firmware update daemon... Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to startup redfish: no SMBIOS table Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to startup dell_esrt: token 1122 is not boolean Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to startup dell: Firmware updating not supported Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to startup uefi: kernel efivars support missing: /sys/firmware/efi/efivars Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to coldplug amt: Unable to find a ME interface Mär 20 02:13:19 ubuntu1810vm dbus-daemon[497]: [system] Activating via systemd: service name='org.freedesktop.bolt' unit='bolt.service' requested by ':1.193' (uid=0 pid=1767 comm="/usr/lib/fwupd/fwupd " label="unconfined") Mär 20 02:13:19 ubuntu1810vm systemd[1]: Starting Thunderbolt system service... Mär 20 02:13:19 ubuntu1810vm boltd[1791]: bolt 0.5 starting up. Mär 20 02:13:19 ubuntu1810vm boltd[1791]: config: loading user config Mär 20 02:13:19 ubuntu1810vm boltd[1791]: bouncer: initializing polkit Mär 20 02:13:19 ubuntu1810vm boltd[1791]: udev: initializing udev Mär 20 02:13:19 ubuntu1810vm boltd[1791]: store: loading devices Mär 20 02:13:19 ubuntu1810vm boltd[1791]: power: force power support: no Mär 20 02:13:19 ubuntu1810vm boltd[1791]: udev: enumerating devices Mär 20 02:13:19 ubuntu1810vm dbus-daemon[497]: [system] Successfully activated service 'org.freedesktop.bolt' Mär 20 02:13:19 ubuntu1810vm systemd[1]: Started Thunderbolt system service. Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: disabling plugin because: failed to coldplug thunderbolt_power: No support for force power via kernel or bolt Mär 20 02:13:19 ubuntu1810vm fwupd[1767]: Daemon ready for requests Mär 20 02:13:19 ubuntu1810vm dbus-daemon[497]: [system] Successfully activated service 'org.freedesktop.fwupd' Mär 20 02:13:19 ubuntu1810vm systemd[1]: Started Firmware update daemon. Mär 20 02:13:20 ubuntu1810vm PackageKit[1329]: get-updates transaction /111_caaeddde from uid 1000 finished with success after 756ms Mär 20 02:13:21 ubuntu1810vm PackageKit[1329]: resolve transaction /112_bebaccdd from uid 1000 finished with success after 481ms Mär 20 02:13:22 ubuntu1810vm PackageKit[1329]: search-file transaction /113_eeebcbec from uid 1000 finished with success after 950ms Mär 20 02:13:22 ubuntu1810vm PackageKit[1329]: search-file transaction /114_eeaceced from uid 1000 finished with success after 408ms Mär 20 02:13:23 ubuntu1810vm PackageKit[1329]: search-file transaction /115_edaedddc from uid 1000 finished with success after 422ms Mär 20 02:13:23 ubuntu1810vm systemd-timesyncd[368]: Timed out waiting for reply from [2001:67c:1560:8003::c8]:123 (ntp.ubuntu.com). Mär 20 02:13:23 ubuntu1810vm PackageKit[1329]: search-file transaction /116_edeaeceb from uid 1000 finished with success after 387ms Mär 20 02:13:24 ubuntu1810vm PackageKit[1329]: get-details
[Bug 1820924] [NEW] DNS Servers added to resolv.conf, but not remived afterwards
Public bug reported: My openvpn setup pushes internal DNS servers to clients. a) The DNS server is added to resolv.conf, but at the end of the list, instead as the first DNS b) same for the search domain After the connection has been cut, the DNS servers and search domain REMAIN in /etc/resolv.conf. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager-openvpn 1.8.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 20 00:04:12 2019 InstallationDate: Installed on 2014-02-07 (1866 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to cosmic on 2018-09-29 (171 days ago) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1820924 Title: DNS Servers added to resolv.conf, but not remived afterwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1820924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820904] [NEW] Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04
Public bug reported: Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04. Below is the screenshot comparing Evince and Okular on the same Ubuntu 16.04 box. Before the upgrade from 14.04, Evince worked fine. https://i.stack.imgur.com/CWIPY.png please let me know if there is an easy fix. thanks ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1820904 Title: Evince stop rendering text with anti-aliasing after upgrading to Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1820904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820869] Re: totem could not take screenshot
** Summary changed: - totem Could not take screenshot + totem could not take screenshot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1820869 Title: totem could not take screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1820869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820282] Re: FTBFS: test failure during build in lp
** Changed in: zeromq Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1820282 Title: FTBFS: test failure during build in lp To manage notifications about this bug go to: https://bugs.launchpad.net/zeromq/+bug/1820282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
This bug was fixed in the package nautilus - 1:3.32.0-0ubuntu1 --- nautilus (1:3.32.0-0ubuntu1) disco; urgency=medium * New upstream version (lp: #1820683) * debian/control.in: - build-depends on libgstreamer-plugins-base1.0-dev, the audio/video properties code has been moved from totem to nautilu - updated the glib requirement * debian/patches/git_init_segfault.patch: - include a patch from Andrea to fix a segfault (lp: #1819757) -- Sebastien Bacher Tue, 19 Mar 2019 17:11:27 +0100 ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- 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/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820683] Re: [disco-proposed] The new version came out on 13/03 and we still have not received an update.
This bug was fixed in the package nautilus - 1:3.32.0-0ubuntu1 --- nautilus (1:3.32.0-0ubuntu1) disco; urgency=medium * New upstream version (lp: #1820683) * debian/control.in: - build-depends on libgstreamer-plugins-base1.0-dev, the audio/video properties code has been moved from totem to nautilu - updated the glib requirement * debian/patches/git_init_segfault.patch: - include a patch from Andrea to fix a segfault (lp: #1819757) -- Sebastien Bacher Tue, 19 Mar 2019 17:11:27 +0100 ** Changed in: nautilus (Ubuntu) Status: In Progress => Fix Released -- 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/1820683 Title: [disco-proposed] The new version came out on 13/03 and we still have not received an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
This bug was fixed in the package gnome-settings-daemon - 3.28.1-0ubuntu1.2 --- gnome-settings-daemon (3.28.1-0ubuntu1.2) bionic; urgency=medium * debian/patches/keyboard-Enable-ibus-for-OSK-purposes.patch: - Enable IBus for OSK (LP: #1760399) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 20:31:01 + ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820883] [NEW] totem comma key does not go 1 frame back
Public bug reported: According help the ',' (comma) key should go 1 frame back. I press the ',' key once: nothing happens; press again goes forward to end video after pressing ',' the '.' (dot) key does nothing but i have a message: (totem:31585): GStreamer-CRITICAL **: 18:15:31.465: gst_segment_do_seek: assertion 'start <= stop' failed pressing dot again it goes 1 frame forward ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 18:17:34 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2019-03-14 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1820883 Title: totem comma key does not go 1 frame back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1820883/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819757] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
** Changed in: nautilus (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819757 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1819757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1505769] Re: Contents of files saved to FTP are not preserved
Looks like a duplicate of bug #708829 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1505769 Title: Contents of files saved to FTP are not preserved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1505769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
** Tags removed: rls-dd-incoming ** Tags added: rls-dd-tracking ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1817924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740869] Re: is not responding window is constantly showing when debugging a program
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1740869 Title: is not responding window is constantly showing when debugging a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740869] Automatically added comment
Added to Trello: https://trello.com/c/42jbJczE/286-bug1740869-something- is-not-responding-window-is-constantly-showing-when-debugging-a-program ** Tags removed: desktop-trello-import -- 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/1740869 Title: is not responding window is constantly showing when debugging a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740869] Re: is not responding window is constantly showing when debugging a program
Marking as not fixing for release. That doesn't mean this won't be fixed, just that we won't block release on waiting for it to get fixed. This will be picked up in the 19.10 cycle for fixing. ** Tags removed: rls-dd-incoming ** Tags added: desktop-trello-import rls-dd-notfixing -- 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/1740869 Title: is not responding window is constantly showing when debugging a program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown
** Summary changed: - monitors.xml is not parsed or applied correctly after reboot or shutdown + monitors.xml is not parsed or applied correctly during login after reboot or shutdown ** Description changed: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver + numlockx(optionally) TL;DR After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting - a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a 4K + a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a FHD projector and then configuring the logical monitor layout in the "Displays" settings dialog, I can successfully create and use a multi monitor setup in my current session. However, upon a reboot or power cycle of the computer and a successful login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even though I set it as 'Primary' in the "Displays" dialog. The monitors.xml file, attached, shows the correct layout and survives the reboot without alteration. I am unable to see anything on the 'Primary' display, which has incorrectly been given to the HDMI projector. Unseating the HDMI cable does not restore the VGA to 'Primary' display automatically and I must reboot the computer while leaving the HDMI unplugged in order to restore my ability to see the 'Primary' display on the VGA connection. Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is repeatedly provable through multiple reboots or changes to the logical layout of the screens in the 'Displays' settings of gnome-control- center. ERRORS(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary monitor and HDMI(wireless Tx) as secondary to projector and then apply custom monitor positioning using g-c-c "Displays" panel. RESULT = correct positioning and working of multiple displays until reboot or shutdown and then subsequent login from gdm3. HDMI monitor(projector) goes blank and the VGA monitor only shows 'Secondary' monitor screen without any user visible controls or windows as they are all being painted to the now blanked 'Primary' HDMI connected display. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1820423 Title: monitors.xml is not parsed or applied correctly during login after reboot or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1820423/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820866] [NEW] File dialog extremely slow
Public bug reported: >From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport 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'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic ** Attachment added: "Screen recording of gedit open and close" https://bugs.launchpad.net/bugs/1820866/+attachment/5247541/+files/slow%20screen.mkv -- 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/1820866 Title: File dialog extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820866/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820869] [NEW] totem Could not take screenshot
Public bug reported: 3.32.0-1ubuntu1 on Ubuntu 19.04 Disco fails to create a screenshot. The error produced is "Totem could not get a screenshot of the video. This is not supposed to happen please file a bug report." Steps to reproduce: Open a video and choose Take screenshot from the totem menu. note: i have the problem with many .webm videos but not with .avi corrado@corrado-p6-dd-0314:~$ totem ~/Videos/cincia.webm (totem:22902): Gtk-WARNING **: 15:30:27.854: gtk_window_present_with_time() should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the timestamp should instead be gathered at the time the user initiated the request for the window to be shown (totem:22902): Gtk-WARNING **: 15:30:27.990: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) (totem:22902): Gtk-WARNING **: 15:30:28.012: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale) ** (totem:22902): WARNING **: 15:30:39.279: Could not take screenshot: failed to retrieve or convert video frame ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 15:31:58 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2019-03-14 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190314) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1820869 Title: totem Could not take screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1820869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820862] Re: /usr/bin/gnome-control-center:11:cc_display_config_equal:update_apply_button:reset_current_config:on_screen_changed:g_closure_invoke
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1820862 Title: /usr/bin/gnome-control- center:11:cc_display_config_equal:update_apply_button:reset_current_config:on_screen_changed:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820861] Re: /usr/bin/gnome-control-center:11:cc_display_mode_get_freq_f:cc_display_settings_rebuild_ui:cc_display_settings_rebuild_ui:cc_display_settings_set_selected_output:set_current_output
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1820861 Title: /usr/bin/gnome-control- center:11:cc_display_mode_get_freq_f:cc_display_settings_rebuild_ui:cc_display_settings_rebuild_ui:cc_display_settings_set_selected_output:set_current_output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820861] [NEW] /usr/bin/gnome-control-center:11:cc_display_mode_get_freq_f:cc_display_settings_rebuild_ui:cc_display_settings_rebuild_ui:cc_display_settings_set_selected_output:set_current_output
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.32.0.1-1ubuntu5, the problem page at https://errors.ubuntu.com/problem/7a54ef028f10a8cf38077010cfb7da2fb117c988 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-control-center (Ubuntu) Importance: High Status: Confirmed ** Tags: disco -- 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/1820861 Title: /usr/bin/gnome-control- center:11:cc_display_mode_get_freq_f:cc_display_settings_rebuild_ui:cc_display_settings_rebuild_ui:cc_display_settings_set_selected_output:set_current_output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800840] Re: totem fails to create screenshot
same as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721248 https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204 and i still have the same problem with 3.32.0-1ubuntu1 on Ubuntu 19.04 Disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1800840 Title: totem fails to create screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1800840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820859] [NEW] /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: disco kylin-19.04 -- 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/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820862] [NEW] /usr/bin/gnome-control-center:11:cc_display_config_equal:update_apply_button:reset_current_config:on_screen_changed:g_closure_invoke
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.32.0.1-1ubuntu5, the problem page at https://errors.ubuntu.com/problem/1bc3125947aaf960fdb992affcde17fac12890e1 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-control-center (Ubuntu) Importance: High Status: Confirmed ** Tags: disco -- 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/1820862 Title: /usr/bin/gnome-control- center:11:cc_display_config_equal:update_apply_button:reset_current_config:on_screen_changed:g_closure_invoke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820862/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800840] Re: totem fails to create screenshot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1800840 Title: totem fails to create screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1800840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820857] [NEW] Skype snap does not launch from gnome-software
Public bug reported: Steps: 1. Install the Skype snap from gnome-software 2. Launch Skype from gnome-software 3. It does not launch ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 14:59:12 2019 InstallationDate: Installed on 2018-11-29 (109 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.8 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1820857 Title: Skype snap does not launch from gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1820857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820854] [NEW] Don't hide GdkWindow on grab failure
Public bug reported: I have problem when always-on-top window appears on screen or after it closing for example terminal menu panel does not react to keyboard button pressing and mouse pointer events. To recreate this problem: 1.Login into ubuntu session; 2.Open terminal; 3.Run for exmaple 'ssh-askpass' (which creates always-on-top-window); 4.Try to press terminal menu buttons (they will not respond); 5.Close 'ssh-askpass' and try again to press terminal toolbar menu buttons (they will not respond); But I found a sollution which helps application panel to react for events while showing or after closing always-on-top window here https://gitlab.gnome.org/GNOME/gtk/commit/2c8b95a518bea2192145efe11219f2e36091b37a This sollution is added to upstream in gtk3.0 for Ubuntu 18.10. I use gtk+3.0_3.22.30-1ubuntu2 version. My OS is - Ubuntu 18.04.2 LTS Release: 18.04. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820854 Title: Don't hide GdkWindow on grab failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
** Description changed: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. - Ubuntu 18.10 + Applies to Ubuntu 18.10 and 19.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/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
** Description changed: The first part of our work on better handling of HI-DPI screens got merged upstream in 3.32, but it's for wayland only https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/ Since our default session in Ubuntu is based on xorg we would like to distro patch the x11 equivalent for Disco so our users can benefit from the feature. Updates packages are up for testing in that ppa https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling The main change is https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz The ppa also includes a bugfix and a settings change to allow easy configuration. Note that the feature is behind an experimental gsettings key and the code has no impact on the rendering for users who don't enable it, which means it shouldn't be too risk. It's available as a opt-in for those who want to test it. - From our testing it works fine and we feel like it's ready to be included. We do plan to get that work merged upstream in the next cycle so it should be an Ubuntu delta to carry over forever. + From our testing it works fine and we feel like it's ready to be included. We do plan to get that work merged upstream in the next cycle so it should not be an Ubuntu delta to carry over forever. -- 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/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820683] Re: [disco-proposed] The new version came out on 13/03 and we still have not received an update.
Hey Edson, sorry if you found the tone not cordial. I was just trying to put out that we do have tooling to see outdated package such manual bugs reports are not required. My goal was mainly to make us both not waste efforts in doing paperwork when not needed in the futur. Meanwhile you contributions and reports have been useful so please keep testing Ubuntu and telling us about the problems you find! -- 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/1820683 Title: [disco-proposed] The new version came out on 13/03 and we still have not received an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Just confirming that this issue affects me also. Here's my post from the other other bug: I'm using Xorg with an AMD Vega 64. Both displays are connected to the GPU. My main 144hz display is connected via Display Port, and my second 60hz display is connected via HDMI. I'm using Mesa 19.1.0-devel - padoka PPA When I perform the test case in the first post, I get high framerates when the secondary display is disabled, and only 60 fps when it's enabled. -- 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820683] Re: [disco-proposed] The new version came out on 13/03 and we still have not received an update.
Hi Sebatsian OK! I see it's in progress, good! Be more cordial with your collaborators, okay? The fact that it was announced that it was already released, made me wonder if it was still not available for download in [disk-proposed], that's it! If we can not question something for which a collaborator serves? Thank you for your attention. -- 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/1820683 Title: [disco-proposed] The new version came out on 13/03 and we still have not received an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820850] [NEW] [FFe] Distro patch GNOME hi-dpi support for x11 sessions
Public bug reported: The first part of our work on better handling of HI-DPI screens got merged upstream in 3.32, but it's for wayland only https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/ Since our default session in Ubuntu is based on xorg we would like to distro patch the x11 equivalent for Disco so our users can benefit from the feature. Updates packages are up for testing in that ppa https://launchpad.net/~3v1n0/+archive/ubuntu/mutter-x11-fractional-scaling The main change is https://launchpadlibrarian.net/415722066/mutter_3.32.0-1_3.32.0-1ubuntu1~xrandrscaling3.diff.gz The ppa also includes a bugfix and a settings change to allow easy configuration. Note that the feature is behind an experimental gsettings key and the code has no impact on the rendering for users who don't enable it, which means it shouldn't be too risk. It's available as a opt-in for those who want to test it. >From our testing it works fine and we feel like it's ready to be included. We >do plan to get that work merged upstream in the next cycle so it should be an >Ubuntu delta to carry over forever. ** Affects: gnome-control-center (Ubuntu) Importance: High Status: New ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High -- 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/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items
I have hibernate-status-button and suspend-button and that's probably user menu is extended since the buttons don't fit. Should I still file an upstream bug? On Tue, Mar 19, 2019 at 2:55 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > It looks like the most likely triggers of this bug are: > > suspend-button@laserb > show-desktop-button@amivaleo > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820775 > > Title: > gnome-shell's user menu/item is not aligned like other menu items > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820775/+subscriptions > -- 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/1820775 Title: gnome-shell's user menu/item is not aligned like other menu items To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] [NEW] (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Public bug reported: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 144hz 60hz mutter xorg -- 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions
multi-monitor FPS bug for xorg, discussion moved to ---> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832 -- 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/1730460 Title: Very poor multi-monitor performance in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1730460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817682] Re: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom)
A possible workaround is to just stop using multiple workspaces (put everything on the default one) and don't switch between them. >From my point of view a developer should easily reproduce that crash. I believe the steps to reproduce are pretty clear. Thanks for your support Daniel - I'll stick to the workaround (even though it's pretty disappointing). -- 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/1817682 Title: Ubuntu 18.04 interface freeze - during video call or screen sharing (using Slack or Zoom) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Thank you Daniel. The new bug is https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832 -- 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/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820683] Re: [disco-proposed] The new version came out on 13/03 and we still have not received an update.
The new version has been out only a few days, people are just busy, please don't create paperwork when not needed. We have tools to track our current versions and outdated packages, we don't need manual reports every time we take a week to do an update ** Changed in: nautilus (Ubuntu) Status: Incomplete => In Progress -- 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/1820683 Title: [disco-proposed] The new version came out on 13/03 and we still have not received an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
** Changed in: gtk Status: Unknown => Fix Released ** 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/1820542 Title: In a wayland session opening text file in gedit causes busy cursor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820775] Re: gnome-shell's user menu/item is not aligned like other menu items
It looks like the most likely triggers of this bug are: suspend-button@laserb show-desktop-button@amivaleo -- 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/1820775 Title: gnome-shell's user menu/item is not aligned like other menu items To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
The bug seems to have been fixed upstream in mutter: https://gitlab.gnome.org/GNOME/mutter/issues/501 but there are some other upstream bug links too. Probably not required. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1754 https://gitlab.gnome.org/GNOME/gtk/issues/1754 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/issues/1754 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #501 https://gitlab.gnome.org/GNOME/mutter/issues/501 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/501 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Tags added: 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/1820542 Title: In a wayland session opening text file in gedit causes busy cursor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
** Changed in: gnome-shell 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/1820542 Title: In a wayland session opening text file in gedit causes busy cursor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
