[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
In isolation I don't think it's correct to say that Wayland sessions have "no external monitors". Wayland sessions do work with external monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've confirmed this on a desktop at least. It sounds like you're describing some other laptop-specific or Optimus- specific bug. So I think to avoid confusion that should have its own separate bug report. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from
It appears there's only one caller of this function in gnome-shell: js/ui/osdMonitorLabeler.js:let monitor = this._monitorManager.get_monitor_for_connector(connector); ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** 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/1833558 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector()
Tracking in: https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f ** Description changed: + https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f + gnome shell crashes when I go to Settings -> Devices -> Displays ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 19 11:01:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-04-29 (1146 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f49b8116bf0 :mov0x18(%rax),%eax PC (0x7f49b8116bf0) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_manager_get_monitor_for_connector () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev sambashare sudo ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() + gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from -- 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/1833558 Title: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833642] Re: /usr/bin/gnome-shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call
*** This bug is a duplicate of bug 1833558 *** https://bugs.launchpad.net/bugs/1833558 ** This bug has been marked a duplicate of private bug 1833558 -- 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/1833642 Title: /usr/bin/gnome- shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833642/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833642] [NEW] /usr/bin/gnome-shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call
*** This bug is a duplicate of bug 1833558 *** https://bugs.launchpad.net/bugs/1833558 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.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f 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: artful bionic cosmic disco -- 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/1833642 Title: /usr/bin/gnome- shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833642/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
gnome-shell!587 only says it fixes gnome-shell#1325. If you think it also fixes gnome-shell#1370 then you should probably add a comment here: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587 -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
just one last thing, possibly you are not aware that 19.04 Ubuntu wayland sessions have exactly the same problem: no external monitors. While this bug refers to Xorg, the problem is not limited to Xorg. At least on my Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode, no monitors work, not even the laptop panel. On Fri, 21 Jun 2019 at 12:50, Daniel van Vugt wrote: > Actually, maybe those other DMs don't run as root. My memory is failing. > So again maybe we do want a similar workaround in gdm3. But that doesn't > seem to be the root cause of the bug. > > ** Changed in: gdm3 (Ubuntu) >Status: Invalid => Opinion > > ** No longer affects: mutter (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Actually, maybe those other DMs don't run as root. My memory is failing. So again maybe we do want a similar workaround in gdm3. But that doesn't seem to be the root cause of the bug. ** Changed in: gdm3 (Ubuntu) Status: Invalid => Opinion ** No longer affects: mutter (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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
> If you need modeset=1 for wayland, then why is there any effort to support nvidia and wayland under gnome, since it won't work (or are only optimus systems affected by this?) I don't understand the question, sorry. The statement "it won't work" is wrong. Wayland does work. This bug is about Xorg, not Wayland. > So it looks like a gdm3 bug. Yes I understand that's how it looks, but we have established the root cause of this bug is in the Nvidia driver. Maybe we will be able to work around it with some gdm3 change, but that's not where the root cause of the problem is. Other display managers are managing to work around the Nvidia driver bug here because they run as root. gdm3 does not run as root because it is trying to be more secure and avoid running as root. Calling this a gdm3 bug is probably wrong. I can reproduce the bug without gdm3. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I think his point was to isolate the problem as being gdm3's wayland code. If you need modeset=1 for wayland, then why is there any effort to support nvidia and wayland under gnome, since it won't work (or are only optimus systems affected by this?) my point was that you marked this as invalid, but the only way to avoid this bug is to avoid using gdm3. You don't have to change anything else. So it looks like a gdm3 bug. On Fri, 21 Jun 2019 at 11:50, Daniel van Vugt wrote: > Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind > of pointless. It's pointless because the most common reason for using > nvidia-drm.modeset=1 is to get Wayland support. I know there are other > reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in > PRIME setups. But mostly if people use modeset=1 it is to get Wayland > support. > > If we can't get a fix from Nvidia then some kind of workaround that runs > Xorg as root (like comment #26) is probably the next best option. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1716857 > > Title: > nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind of pointless. It's pointless because the most common reason for using nvidia-drm.modeset=1 is to get Wayland support. I know there are other reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in PRIME setups. But mostly if people use modeset=1 it is to get Wayland support. If we can't get a fix from Nvidia then some kind of workaround that runs Xorg as root (like comment #26) is probably the next best option. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Description changed: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. It can't be worse than actual situation where the login never appears. + + As per commit description: + + " + This should be transparent to to user space, as long as it doesn't + compare the time against the result of gettimeofday(). + " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Ok, including my own testing we got 4 positive feedback. With that being said, I have just submitted the patch to our kernel team a few minutes ago. This will be part of the next cycle 01-July through 21-July. Thanks for the pre-SRU testing, we will need you guys one more time during the testing phase of bionic-proposed in a couple of weeks. - Eric ** Tags added: sts -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
What we know about this bug is that gdm3, nvidia and modeset=1 is broken under configurations which are not broken when sddm and lightdm are used. we know that gdm3 sessions with external monitors work with root permissions. we know that gdm3 compiled with wayland also works (according to the gentoo user generix). And neither gnome developers nor nvidia acknowledge a bug. If you make a venn diagram of all of this, gdm3 is the intersection of every observation. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
"gdm3 compile without wayland", I meant -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50
I should add that the "fix" I reported is only a narrow fix. The internal display works. But external displays don't work if you have nvidia drivers, gdm3 and if you are using modeset=1 -- 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/1706474 Title: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Additional confirmation... Looks like this updated kernel fixes the issue on the affected test VM I created. Using the detailed directions in comment #75, I was able to install the new test kernel and reboot. Verified the expected version value with uname and then installed the packages that were previously hanging from the copies I archived with the test VM and rebooted. Login showed up and functioned as normal. This appears to be the ideal 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Description changed: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] - Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it - can't be worse than actual situation where the login doesn't appears at - all. + Low, it should fix vmwgfx and stop using the wrong clock. + + A test kernel (pre-sru) has been made available to impact users for them + to test and conclude it works. It does work as expected, and no + regression has been found during the pre-sru testing phase. + + It can't be worse than actual situation where the login never appears. [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/587 -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/587 -- 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/1831161 Title: App-switcher icons too small with hidpi monitor and 1.25 scaling To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1831161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Additional confirmation... Working under VMware Workstation v12.5.7 running kernel 4.15.0.52: Having performed the workaround of uncommenting the WaylandEnable=false... - Re-commented the line & rebooted to experience the hang with the Ubuntu logo before the login screen - Using your ppa, installed the test kernel. - Rebooted. Login proceeded normally: Linux linuxTest 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP Thu Jun 20 13:18:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Thank you! -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Great for the quick feedback. I have until June 26th to submit the patch for the next cycle[0] It's giving me a couple of more days to get other impacted users feedback. [0] - https://kernel.ubuntu.com/ - Eric -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Eric, your new test kernel works for... and screen-resizing works this time too. To confirm, I am running the correct kernel build; uname -a Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP Thu Jun 20 13:18:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Bionic) Importance: Critical => High -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Detailled instructions on how to use my ppa : $ sudo add-apt-repository ppa:slashd/kernel-builder $ sudo apt-get update $ sudo apt install linux-image-unsigned-4.15.0-53-generic linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic then reboot, and once login you can confirm if you run my test kernel with "uname -a" which should report "4.15.0-53.57+hf231164v20190620b11" -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: libbonobo 2.32.1-3 in eoan libbonobo2-0 2.32.1-3 in eoan amd64 libbonobo2-0 2.32.1-3 in eoan arm64 libbonobo2-0 2.32.1-3 in eoan armhf libbonobo2-0 2.32.1-3 in eoan i386 libbonobo2-0 2.32.1-3 in eoan ppc64el libbonobo2-0 2.32.1-3 in eoan s390x libbonobo2-bin 2.32.1-3 in eoan amd64 libbonobo2-bin 2.32.1-3 in eoan arm64 libbonobo2-bin 2.32.1-3 in eoan armhf libbonobo2-bin 2.32.1-3 in eoan i386 libbonobo2-bin 2.32.1-3 in eoan ppc64el libbonobo2-bin 2.32.1-3 in eoan s390x libbonobo2-common 2.32.1-3 in eoan amd64 libbonobo2-common 2.32.1-3 in eoan arm64 libbonobo2-common 2.32.1-3 in eoan armhf libbonobo2-common 2.32.1-3 in eoan i386 libbonobo2-common 2.32.1-3 in eoan ppc64el libbonobo2-common 2.32.1-3 in eoan s390x libbonobo2-dev 2.32.1-3 in eoan amd64 libbonobo2-dev 2.32.1-3 in eoan arm64 libbonobo2-dev 2.32.1-3 in eoan armhf libbonobo2-dev 2.32.1-3 in eoan i386 libbonobo2-dev 2.32.1-3 in eoan ppc64el libbonobo2-dev 2.32.1-3 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885770 1 package successfully removed. ** Changed in: libbonobo (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: libgnome 2.32.1-6 in eoan libgnome-2-0 2.32.1-6 in eoan amd64 libgnome-2-0 2.32.1-6 in eoan arm64 libgnome-2-0 2.32.1-6 in eoan armhf libgnome-2-0 2.32.1-6 in eoan i386 libgnome-2-0 2.32.1-6 in eoan ppc64el libgnome-2-0 2.32.1-6 in eoan s390x libgnome2-0 2.32.1-6 in eoan amd64 libgnome2-0 2.32.1-6 in eoan arm64 libgnome2-0 2.32.1-6 in eoan armhf libgnome2-0 2.32.1-6 in eoan i386 libgnome2-0 2.32.1-6 in eoan ppc64el libgnome2-0 2.32.1-6 in eoan s390x libgnome2-bin 2.32.1-6 in eoan amd64 libgnome2-bin 2.32.1-6 in eoan arm64 libgnome2-bin 2.32.1-6 in eoan armhf libgnome2-bin 2.32.1-6 in eoan i386 libgnome2-bin 2.32.1-6 in eoan ppc64el libgnome2-bin 2.32.1-6 in eoan s390x libgnome2-common 2.32.1-6 in eoan amd64 libgnome2-common 2.32.1-6 in eoan arm64 libgnome2-common 2.32.1-6 in eoan armhf libgnome2-common 2.32.1-6 in eoan i386 libgnome2-common 2.32.1-6 in eoan ppc64el libgnome2-common 2.32.1-6 in eoan s390x libgnome2-dev 2.32.1-6 in eoan amd64 libgnome2-dev 2.32.1-6 in eoan arm64 libgnome2-dev 2.32.1-6 in eoan armhf libgnome2-dev 2.32.1-6 in eoan i386 libgnome2-dev 2.32.1-6 in eoan ppc64el libgnome2-dev 2.32.1-6 in eoan s390x libgnome2-doc 2.32.1-6 in eoan amd64 libgnome2-doc 2.32.1-6 in eoan arm64 libgnome2-doc 2.32.1-6 in eoan armhf libgnome2-doc 2.32.1-6 in eoan i386 libgnome2-doc 2.32.1-6 in eoan ppc64el libgnome2-doc 2.32.1-6 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885768 1 package successfully removed. ** Changed in: libgnome (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: libgnome-keyring 3.12.0-1build1 in eoan gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64 gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64 gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan i386 gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan ppc64el gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan s390x libgnome-keyring-common 3.12.0-1build1 in eoan amd64 libgnome-keyring-common 3.12.0-1build1 in eoan arm64 libgnome-keyring-common 3.12.0-1build1 in eoan armhf libgnome-keyring-common 3.12.0-1build1 in eoan i386 libgnome-keyring-common 3.12.0-1build1 in eoan ppc64el libgnome-keyring-common 3.12.0-1build1 in eoan s390x libgnome-keyring-dev 3.12.0-1build1 in eoan amd64 libgnome-keyring-dev 3.12.0-1build1 in eoan arm64 libgnome-keyring-dev 3.12.0-1build1 in eoan armhf libgnome-keyring-dev 3.12.0-1build1 in eoan i386 libgnome-keyring-dev 3.12.0-1build1 in eoan ppc64el libgnome-keyring-dev 3.12.0-1build1 in eoan s390x libgnome-keyring0 3.12.0-1build1 in eoan amd64 libgnome-keyring0 3.12.0-1build1 in eoan arm64 libgnome-keyring0 3.12.0-1build1 in eoan armhf libgnome-keyring0 3.12.0-1build1 in eoan i386 libgnome-keyring0 3.12.0-1build1 in eoan ppc64el libgnome-keyring0 3.12.0-1build1 in eoan s390x libgnome-keyring0-dbg 3.12.0-1build1 in eoan amd64 libgnome-keyring0-dbg 3.12.0-1build1 in eoan arm64 libgnome-keyring0-dbg 3.12.0-1build1 in eoan armhf libgnome-keyring0-dbg 3.12.0-1build1 in eoan i386 libgnome-keyring0-dbg 3.12.0-1build1 in eoan ppc64el libgnome-keyring0-dbg 3.12.0-1build1 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #892359 1 package successfully removed. ** Changed in: libgnome-keyring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: orbit2 1:2.14.19-4 in eoan liborbit-2-0 1:2.14.19-4 in eoan amd64 liborbit-2-0 1:2.14.19-4 in eoan arm64 liborbit-2-0 1:2.14.19-4 in eoan armhf liborbit-2-0 1:2.14.19-4 in eoan i386 liborbit-2-0 1:2.14.19-4 in eoan ppc64el liborbit-2-0 1:2.14.19-4 in eoan s390x liborbit2 1:2.14.19-4 in eoan amd64 liborbit2 1:2.14.19-4 in eoan arm64 liborbit2 1:2.14.19-4 in eoan armhf liborbit2 1:2.14.19-4 in eoan i386 liborbit2 1:2.14.19-4 in eoan ppc64el liborbit2 1:2.14.19-4 in eoan s390x liborbit2-dev 1:2.14.19-4 in eoan amd64 liborbit2-dev 1:2.14.19-4 in eoan arm64 liborbit2-dev 1:2.14.19-4 in eoan armhf liborbit2-dev 1:2.14.19-4 in eoan i386 liborbit2-dev 1:2.14.19-4 in eoan ppc64el liborbit2-dev 1:2.14.19-4 in eoan s390x orbit2 1:2.14.19-4 in eoan amd64 orbit2 1:2.14.19-4 in eoan arm64 orbit2 1:2.14.19-4 in eoan armhf orbit2 1:2.14.19-4 in eoan i386 orbit2 1:2.14.19-4 in eoan ppc64el orbit2 1:2.14.19-4 in eoan s390x orbit2-nameserver 1:2.14.19-4 in eoan amd64 orbit2-nameserver 1:2.14.19-4 in eoan arm64 orbit2-nameserver 1:2.14.19-4 in eoan armhf orbit2-nameserver 1:2.14.19-4 in eoan i386 orbit2-nameserver 1:2.14.19-4 in eoan ppc64el orbit2-nameserver 1:2.14.19-4 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #890459 1 package successfully removed. ** Changed in: orbit2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan s390x libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-0-dbg 1:2.24.4-6.1ubuntu2 in eoan s390x libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-bin 1:2.24.4-6.1ubuntu2 in eoan s390x libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-common 1:2.24.4-6.1ubuntu2 in eoan s390x libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-dev 1:2.24.4-6.1ubuntu2 in eoan s390x libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan amd64 libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan arm64 libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan armhf libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan i386 libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan ppc64el libgnomevfs2-extra 1:2.24.4-6.1ubuntu2 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #893922 1 package successfully removed. ** Changed in: gnome-vfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825972] Re: Remove gnome 2 stack + linsmith from eoan
Removing packages from eoan: libbonoboui 2.24.5-4 in eoan libbonoboui2-0 2.24.5-4 in eoan amd64 libbonoboui2-0 2.24.5-4 in eoan arm64 libbonoboui2-0 2.24.5-4 in eoan armhf libbonoboui2-0 2.24.5-4 in eoan i386 libbonoboui2-0 2.24.5-4 in eoan ppc64el libbonoboui2-0 2.24.5-4 in eoan s390x libbonoboui2-bin 2.24.5-4 in eoan amd64 libbonoboui2-bin 2.24.5-4 in eoan arm64 libbonoboui2-bin 2.24.5-4 in eoan armhf libbonoboui2-bin 2.24.5-4 in eoan i386 libbonoboui2-bin 2.24.5-4 in eoan ppc64el libbonoboui2-bin 2.24.5-4 in eoan s390x libbonoboui2-common 2.24.5-4 in eoan amd64 libbonoboui2-common 2.24.5-4 in eoan arm64 libbonoboui2-common 2.24.5-4 in eoan armhf libbonoboui2-common 2.24.5-4 in eoan i386 libbonoboui2-common 2.24.5-4 in eoan ppc64el libbonoboui2-common 2.24.5-4 in eoan s390x libbonoboui2-dev 2.24.5-4 in eoan amd64 libbonoboui2-dev 2.24.5-4 in eoan arm64 libbonoboui2-dev 2.24.5-4 in eoan armhf libbonoboui2-dev 2.24.5-4 in eoan i386 libbonoboui2-dev 2.24.5-4 in eoan ppc64el libbonoboui2-dev 2.24.5-4 in eoan s390x Comment: Obsolete gnome2 library, removed from Debian testing; LP: #1825972, Debian bug #885769 1 package successfully removed. ** Changed in: libbonoboui (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1825972 Title: Remove gnome 2 stack + linsmith from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/1825972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting
** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Tags added: fixed-in-3.33.3 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/1652282 Title: Xwayland not using XAUTHORITY, prevents root applications from connecting To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1652282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Here is the last of the output after running the first test repo update command in comment #73 on the Bug1832138VM.zip VM I built. I'm guessing either there is an integrity issue upstream or more likely there is a missing step so that a system that has been using the default repo settings is superseded by the test repo for the updated package(s). If I ignore these errors and upgrade after update I get the 49 year hang on reboot. E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/Packages.xz File has unexpected size (543836 != 543620). Mirror sync in progress? [IP: 91.189.91.23 80] Hashes of expected file: - Filesize:543620 [weak] - SHA256:3b6cc1e3be5322bc0c88e8dbeecee75d75ed68460ef281d94e9d59ed432224bb - SHA1:022b402b91b0d22d1e2c321c2417c875a2ee8428 [weak] - MD5Sum:a3e4b55f39d2645601f31ea6835092ad [weak] Release file created at: Thu, 20 Jun 2019 17:41:04 + E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/Packages.xz E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/dep11/icons-64x64.tar.gz E: Some index files failed to download. They have been ignored, or old ones used instead. -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Description changed: + [Impact] + + With most recent version of mutter installed. + If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive) and if the login screen uses wayland, then the login prompt doesn't appears. + All we see is the purple background with ubuntu at the bottom, nothing else. + + The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) + before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. + + [Test case] + + 1) Use Virtualbox or VMware ESxi (if you have the infra) + - [vbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 'lspci -nnvv' command. + 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) + 4) apt-get dist-upgrade + 5) Reboot + + with 4.15 it will fails + with hwe kernel 4.18 it will work as expected. + + [Potential regression] + + Low, it should fix vmwgfx and stop using the wrong clock. Sure thing, it + can't be worst than current situation where the login doesn't appears at + all. + + [Other informations] + + upstream fix: + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f + + [Original description] + I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: - VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) -Subsystem: VMware SVGA II Adapter [15ad:0405] + VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) + Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
After building and testing: " 9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57 " the above seems to do the trick ^ which will make the SRU easier (only one commit). I just don't know why the kernel git bisect testing found another commit, but anyway. Anybody impacted want to test this testpkg to double-check before I submit the patch to the kernel team ? sudo add-apt-repository ppa:slashd/kernel-builder sudo apt-get update Version: 4.15.0-53.57+hf231164v20190620b11 -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833471] Re: Can not enable Wifi Hotspot
Here the journalctl info I tested the Hotspot option with or without docking station. Let me know if you need anything else ** Attachment added: "journal.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+attachment/5271861/+files/journal.zip -- 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/1833471 Title: Can not enable Wifi Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829377] Re: Remove this package
cdebconf-terminal also build-depends on libvte-dev, this should be resolved first before we do an Ubuntu-specific removal. ** Also affects: cdebconf-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1829377 Title: Remove this package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdebconf-terminal/+bug/1829377/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
I already did that test ^ using the upstream kernel with 37efe80ce85f being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't continue to pursue that commit, since it wasn't the first introduction of the fix. But based on last duflu update, I as I said I will now give a try again but this time using Ubuntu kernel as follow: 9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57 Let's see what will be the outcome in a couple of hours. -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome. Should be able to provide an update by EOD. -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786344] Re: Default IBus input method ignored in live session
This bug was fixed in the package gnome-settings-daemon - 3.32.1-1ubuntu2 --- gnome-settings-daemon (3.32.1-1ubuntu2) eoan; urgency=medium * debian/patches/ubuntu_ibus_configs.patch: - Always call add_ibus_sources_from_locale() during the first run of g-s-d. This ensures that an IBus method is included in "live sessions" when applicable (LP: #1786344). -- Gunnar Hjalmarsson Thu, 20 Jun 2019 11:57:11 +0100 ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => 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/1786344 Title: Default IBus input method ignored in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
In the .H files of the libappindicator I have found 2 authors' e-mails: Ted Gould and Cody Russell . I have written email and received the email-daemon answer that this e-mails are not valid. I see the problem and want to know who can help me to find the decision. Could you be so kind to direct me in the right way and say the real email or website where I can ask how to resolve the 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/1830422 Title: Shell boxpointer menus don't have scroll buttons when they exceed the screen height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Workaround for mutter proposed here: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083 -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832457] Re: [SRU] 2.60.4
This bug was fixed in the package glib2.0 - 2.60.4-1 --- glib2.0 (2.60.4-1) experimental; urgency=medium * New upstream release (LP: #1832457) + Fixes to improved network status detection with NetworkManager (#1788) + Leak fixes to some `glib-genmarshal` generated code + Further fixes to the Happy Eyeballs (RFC 8305) implementation + File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450) + Bugs fixed: - Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC * gfile-Limit-access-to-files-when-copying.patch: Drop. It's in this version upstream. * d/p/*: Refresh through gbp pq -- Iain Lane Wed, 12 Jun 2019 09:15:11 +0100 ** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12450 -- 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/1832457 Title: [SRU] 2.60.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
And the problem is indeed the kernel advertising DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is the fix, but it may well have some prerequisite commits we haven't fully worked out... https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f I'll see if I can hack around it, but the simplicity of the mistake in the vmwgfx kernel code makes me think we should be preferring a kernel fix still. -- 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
UPDATE: No, removing djvulibre-desktop solved the problem only for the _multipage_ DjVu files, but not for the single-page ones. So, for a single-page djvu files I still get the above-mentioned error message, unless I manually add "image/vnd.djvu" to the end of MimeTypes in /usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument.evince-backend file. -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832374] Re: Media keys stop working due to missing service file
** Description changed: + * Impact + Sometime multimedia keys stop working + + * Test case + - start playing an audio file in VLC/totem/smplayer + - pause + - open a video in another player + - exit the other player + - try to resume the music play from the first one using the play key + + -> it should work + + * Regression potential + Make sure that multimedia play/pause keys keep working + + -- + Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) -- 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/1832374 Title: Media keys stop working due to missing service file To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
Oops, typo in the previous comment: I wrote "evince filename,djvu" but of course I meant "evince filename.djvu", i.e. with dot "." rather than comma ",". ** Bug watch added: Debian Bug tracker #876710 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710 ** Bug watch added: Red Hat Bugzilla #1507305 https://bugzilla.redhat.com/show_bug.cgi?id=1507305 -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
Here are the links to the posts where this bug is mentioned: https://ubuntuforums.org/showthread.php?t=2390953=2 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710 https://bugzilla.redhat.com/show_bug.cgi?id=1507305 -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
Also, here is some useful info for you: $ apt list --installed | grep djvu WARNING: apt does not have a stable CLI interface. Use with caution in scripts. djvubind/bionic,bionic,now 1.2.1-5 all [installed] djvulibre-bin/bionic,now 3.5.27.1-8 amd64 [installed,automatic] djvulibre-desktop/bionic,bionic,now 3.5.27.1-8 all [installed,automatic] libdjvulibre-text/bionic,bionic,now 3.5.27.1-8 all [installed] libdjvulibre21/bionic,now 3.5.27.1-8 amd64 [installed] libminidjvu0/bionic,now 0.8.svn.2010.05.06+dfsg-5build1 amd64 [installed,automatic] minidjvu/bionic,now 0.8.svn.2010.05.06+dfsg-5build1 amd64 [installed,automatic] pdf2djvu/bionic,now 0.9.8-0ubuntu1 amd64 [installed,automatic] And, following the suggestion on bugs.debian.org I have uninstalled the package djvulibre-desktop and this solved the problem, i.e. evince can open djvu files without the "image/vnd.djvu" at the end of MimeTypes in /usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument.evince-backend file. -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
Oh sorry, I forgot to include the info you requested. I am using Ubuntu Linux 18.04.2 and I don't use "nautilus". I always open djvu files using the command "evince filename,djvu" from within terminal. Well, sometimes I use "djview filename.djvu" (when I want to find out the resolution), but normally evince is more convenient. I thought this bug is well-known because for about a year (or maybe longer) I saw it mentioned on stackexchange and that is where I learned about the workaround of adding "image/vnd.djvu" to the end of MimeTypes in the file /usr/lib/x86_64-linux-gnu/evince/4/backends/djvudocument .evince-backend. As for the file example --- just get ANY djvu file from anywhere you like, e.g. from my website: http://www.bibles.org.uk/guardian-plates.html Of course it fails not only with the files produced by myself, but with any other djvu files. The error message from evince is always "File type DjVu image (image/vnd.djvu) is not supported". -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831143] Re: evolution crash with message "Creating pipes for GWakeup: Too many open files"
Please use journalctl to get the ProcessID (in the example you posted above that would be "4764" or "4983" or "16717", then make sure that debug packages are installed for evolution and glib2 and get a stacktrace of that crash via the command: coredumpctl gdb ProcessID (please replace ProcessID by the corresponding number) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1831143 Title: evolution crash with message "Creating pipes for GWakeup: Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1831143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1830824] Re: Consistently pops up notifications for meetings hours in the past
Which calendar type is this about? Local? Remote? Google? EWS? Something else? Are those meetings created by yourself? If not, are those meetings created by someone in the same timezone? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1830824 Title: Consistently pops up notifications for meetings hours in the past To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1830824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815127] Re: Evolution fails to properly parse Date: header
No problem here parsing and displaying the line Date: Thu, 31 Jan 2019 19:15:39 + (UTC) in Evolution 3.32.3. This should not be reported upstream until there is a testcase (exported email message) and until successfully re-tested in a version supported by upstream developers (currently: 3.32). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1815127 Title: Evolution fails to properly parse Date: header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1815127/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1584465] Re: I closed the window but the sound is still playing
That's a feature, see bug #38512 ** Changed in: rhythmbox (Ubuntu) Status: Confirmed => 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/1584465 Title: I closed the window but the sound is still playing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1584465/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833498] Re: Upgrading evince always breaks djvu support
Thank you for your bug report. What version of Ubuntu are you using? How does it fail to open the files is it just that nautilus doesn't list is as an option? Can you add a file ewample to the bug? ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
It seems I stumbled on a workaround. Just install the kernel that comes in the 18.04.2 ISO: https://launchpad.net/ubuntu/+source/linux-hwe ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-hwe (Ubuntu Eoan) Status: New => Invalid -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833500] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchable exception")
*** This bug is a duplicate of bug 1736664 ***
https://bugs.launchpad.net/bugs/1736664
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 1736664, 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.
** Summary changed:
- gnome-shell crashed with signal 5
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
allocate terminated with uncatchable exception")
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1736664
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
allocate terminated with uncatchable exception") from g_log()
--
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/1833500
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from
g_logv("Function allocate terminated with uncatchable exception")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833500/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
Using VirtualBox 6 and VMSVGA as recommended by Eric I still can't reproduce the bug. But I think I can see why now: Ubuntu 18.04.2 comes with kernel 4.18 Let me try 18.04.1... -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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("Function allocate terminated with uncatchable exception") from
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/1736664
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from
g_logv("Function allocate terminated with uncatchable exception") from
g_log()
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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
I can reproduce this bug by creating a guest OS using a 18.04.1 .iso I downloaded last year and attempting to update. I created another guest OS using the 18.04.2 .iso I downloaded yesterday works fine after updating. -- 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/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+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("Function allocate terminated with uncatchable exception") from
** Summary changed:
- gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
AsyncReadyCallback terminated with uncatchable exception") from g_log()
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
allocate terminated with uncatchable exception") from g_log()
--
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("Function allocate terminated with uncatchable exception") from
g_log()
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 1833498] [NEW] Upgrading evince always breaks djvu support
Public bug reported: Every time I upgrade evince (as part of "sudo apt update; sudo apt upgrade") I have to remember to edit the file /usr/lib/x86_64-linux- gnu/evince/4/backends/djvudocument.evince-backend and add "image/vnd.djvu" to the end of MimeType list. If I don't do this then evince is unable to view djvu files. Please add "image/vnd.djvu" to MimeType in the official version of this file so that I (and presumably all other millions of Ubuntu Linux users, who are too lazy to open a bugreport for it) don't have to edit it manually. Thank you. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Description changed: Every time I upgrade evince (as part of "sudo apt update; sudo apt upgrade") I have to remember to edit the file /usr/lib/x86_64-linux- gnu/evince/4/backends/djvudocument.evince-backend and add "image/vnd.djvu" to the end of MimeType list. If I don't do this then evince is unable to view djvu files. Please add "image/vnd.djvu" to MimeType in the official version of this file so that I (and presumably - all other millions of Ubuntu Linux, who are too lazy to open a bugreport - for it) don't have to edit it manually. Thank you. + all other millions of Ubuntu Linux users, who are too lazy to open a + bugreport for it) don't have to edit it manually. Thank you. -- 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/1833498 Title: Upgrading evince always breaks djvu support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
