[Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
It's marked failed to upload on all architectures right now: INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 I guess that means an epoch is needed? -- 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/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039757] Re: Fix race condition in gdm with simpledrm and real drm drivers
I've loaded up a system with a hand built kernel that has simpledrm enabled, and then verified the problem occurred. I then updated to proposed and verified it went away. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2039757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046992] Re: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch)
Do you have something in /usr/local perhaps? Or did you have a snap installed for fwupd? ** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu) ** Changed in: fwupd (Ubuntu) Status: New => Incomplete -- 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/2046992 Title: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2046992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
OK thanks for clarifying. Can you please still try latest 6.5.13 and 6.6.6 and see if it happens in either of those? -- 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/2039570 Title: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Is this happening possibly when there is a resolution change for the eDP? If so, can you please try the latest linux-6.5.y kernel: https://kernel.ubuntu.com/mainline/v6.5.13/ -- 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/2039570 Title: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => mesa (Ubuntu) ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Also affects: mesa via https://gitlab.freedesktop.org/drm/amd/-/issues/2971 Importance: Unknown Status: Unknown -- 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/2043640 Title: amdgpu: GPU Recovery fails, frequent hangs To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This should be a different issue than the mutter issue; please open it up separately for investigation. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
#75 You can turn on proposed and then use ppa-purge command to remove my PPA. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Sure. It wasn't opened yet when I uploaded to mantic a few days ago. Since it's open now I've: 1. uploaded a *ubuntu4 version to noble (after a local test build with noble archive worked). 2. uploaded a *ubuntu3.1 version to mantic to make sure the version string doesn't conflict since they will be different binaries. Please reject the *ubuntu4 version from the mantic-proposed queue and accept the *ubuntu3.1 version (if it looks good). ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
The fixes are identified, I don't think this should wait until GNOME 45.1 release. This issue is totally breaking suspend on several of my test systems. I've backported the fixes from the GNOME 45 branch onto this PPA build: https://launchpad.net/~superm1/+archive/ubuntu/lp2034619/+packages I've also uploaded the mutter package into the proposed queue for SRU team to look at. ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => In Progress ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Mario Limonciello (superm1) -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039958] Re: gnome-shell session dies when locking laptop screen
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- 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/2039958 Title: gnome-shell session dies when locking laptop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This is the upstream fix for this issue: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039757] Re: Fix race condition in gdm with simpledrm and real drm drivers
** Description changed: [ Impact ] When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a series of events can occur that cause simpledrm to race with GDM. When GDM loses the race then a user is left with a black screen. This series of events doesn't currently happen in Jammy kernels, but can happen from a mainline kernel or HWE kernel that enables it. To protect users from this circumstance it is better to fix the race condition. - This issue has been readily reproduced in Ubuntu and reported to upstream mutter. + This issue has been readily reproduced in Ubuntu and reported to upstream mutter. It's also already fixed in GNOME 45, included in Mantic and later. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * GDM can take longer to start up while settling [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 * the changes needed to enable this in the kernel are tracked in bug 1965303 -- 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/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've split up the GDM for Jammy change into https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757 ** No longer affects: gdm3 (Ubuntu Jammy) -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
> Oh, wait. You are just fixing the race condition? Yeah; I see the confusion. This issue got caught up by making sure the GDM race condition was fixed at the same as when this feature is enabled. Perhaps it's better to split the GDM part of it off to it's own bug instead then. > In that case, why can you not revert the kernel config change in the HWE backport to Jammy? That's certainly a possible solution, but what happens when people run mainline kernels for testing another issue and are exposed to this? That's how I discovered it, reported it upstream and got it fixed in GDM. It's a trivial fix. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The problem is specifically when 24.04's kernel backports to 22.04 it will expose the race condition to GDM. If that kernel will never backport then it won't be a problem. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The issue won't occur in Lunar. It's only specifically a problem with gdm when a kernel has been configured this way. It's not a problem in Jammy yet, but will be a problem when such a kernel gets backported as HWE. ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Lunar) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: gdm3 (Ubuntu Lunar) Status: New => Invalid ** Changed in: gdm3 (Ubuntu Jammy) Status: Incomplete => In Progress -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The kernel part yes. The bug fix in GDM to prepare for whenever the kernel part happens I would think not. -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've uploaded the jammy backport of this patch into the queue, so assigning it to myself. As I have readily seen this problem on my own test kernels I'll validate it with a local kernel with the matching kconfig options when it's accepted. This can then be done in advance of waiting for matching changes landing in OEM-6.5, or HWE-6.5. ** Changed in: gdm3 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Mario Limonciello (superm1) ** Description changed: - [ Impact ] + [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. + This issue has been readily reproduced in Ubuntu and reported to upstream mutter. + https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 + [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Description changed: - The fbdev subsystem has been deprecated for a long time. We should drop - it in favour of using simpledrm with fbdev emulation layer. + [ Impact ] + The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. - This requires config changes: + This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer - fedora bug: - https://bugzilla.redhat.com/show_bug.cgi?id=2022385 + When this stack is enabled, it changes boot timing such that some + drivers may take a longer time to boot and GDM may hang in a black + screen. + + [ Test Plan ] + * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) + + [ Where Problems could occur ] + * Race conditions could be exposed to DE environments + * Software that expects to find DRM device at /dev/dri/card0 may have a problem. + * Some older versions of NVIDIA driver might not work properly. + + [ Other Info ] + * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2909 https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2022385 https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2022385 Importance: Unknown Status: Unknown -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is still open. ** Changed in: gdm3 (Ubuntu Mantic) Status: Triaged => Fix Released -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036190] Re: fwupd running in WSL 2 in Ubuntu-22.04 fails to start
I think that this should be changed in gnome software not to try to start fwupd then when in WSL2. ** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu) -- 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/2036190 Title: fwupd running in WSL 2 in Ubuntu-22.04 fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2036190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Also affects: gdm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gdm (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Confirmed ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gdm (Ubuntu Mantic) Status: New => Triaged ** Changed in: gdm (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I'm adding a task for gdm to this bug. The reason is that if simpledrm is used, we've found race conditions that occur where the transition from simpledrm to the proper KMS driver may race with gdm starting up the login screen. When gdm loses the race you end up with a black screen. So please make sure that any kernels that do adopt simpledrm the matching GDM for OS releases that run this kernel (think about HWE!) will need to pick up this GDM fix as well. https://gitlab.gnome.org/GNOME/gdm/-/commit/04e119c8332a564cfad05dfb9cb6ec547d5ba954 ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979118] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT") from IA__FcConfigGetSysRoot()
> Crashing in getenv with a valid parameter like this should not be
possible so I think some heap corruption must have occurred before the
crash.
So at least as a hint coming from a report that was marked as a
duplicate of this - at least for me it's specifically when the system
had a monitor connected and it was disconnected that this issue occurs.
--
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/1979118
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
from IA__FcConfigGetSysRoot()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979118/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1985856] Re: Update Mutter to 42.5
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change) and can confirm it's working with Wayland and the non-functional resolutions are no longer offered. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1985856 Title: Update Mutter to 42.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
> A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". It's not a function of the OS, it's a function of the underlying hardware, firmware, and firmware configuration for your given system. The "!" in the HSI string is controlled by OS behavior (such as encrypted swap, taint, etc). At least on a pre-production Lenovo Z13 I can get HSI-2, depending on whether Lenovo has SPI replay protection in the production hardware I might be able to get all the way to HSI 4. Host Security ID: HSI:2! (v1.8.4) HSI-1 ✔ Fused platform:Locked ✔ Rollback protection: Enabled ✔ Supported CPU: Valid ✔ TPM empty PCRs:Valid ✔ TPM v2.0: Found ✔ UEFI platform key: Valid HSI-2 ✔ IOMMU: Enabled ✔ Platform Debugging:Locked ✔ SPI write protection: Enabled ✔ TPM PCR0 reconstruction: Valid HSI-3 ✔ Pre-boot DMA protection: Enabled ✔ Suspend-to-idle: Enabled ✔ Suspend-to-ram:Disabled ✘ SPI replay protection: Disabled HSI-4 ✔ Encrypted RAM: Encrypted -- 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/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
FYI - 1.8.4 synced from Debian to Ubuntu kinetic now. -- 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/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) > $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf > [Service] > DynamicUser=no The whole point of using DynamicUser in this case was so that fwupdmgr didn't run as root when it reached out to the web to get data. Yes, certainly turning off DynamicUser in fwupd-refresh.service will solve the problem, but that is then a different threat vector. I think if turning off DynamicUser=1, then we probably need to also create a new service account for that systemd service to use. I'll open a new bug to move this discussion to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976 -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962277] Re: To support Synaptics fp device
** Also affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
Reproduced again: 1. Logged out from Xorg session 2. Logged in again with default of Xorg selected, it logs into Wayland 3. Logged out once more and clicked the selected Xorg menu entry again. 4. Logged back in - now into Xorg. 5. Created the attached journal.txt. There are no crash reports in /var/crash and nothing relevant on the whoopsie website for my ID, the last one there is from June before upgrade and different anyway. If I understand it right I don't have to do the apport workaround thing as this is not a stable release. Let me know if otherwise pls. Sorry that my tardiness caused unhappiness, I was just busy and not abandoning Ubuntu after 15 years due to a minor bug in a beta :) ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+attachment/5531770/+files/journal.txt ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
** Summary changed: - Log in with Wayland although Xorg looks selected in session menu. Need to reselect + Logs in with Wayland although Xorg looks selected in session menu. Need to reselect -- 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/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] [NEW] Log in with Wayland although Xorg looks selected in session menu. Need to reselect
Public bug reported: After upgrade to Impish. 1. Log in with Xorg session 2. Log out 3. Check gdm session menu > Xorg is displayed as selected 4. Log in > Wayland is running 5. Log out 6. Check gdm session menu > Xorg is displayed as selected 7. Choose Xorg again anyway 8. Log in 9. Success. Xorg is running Reproduces every time for me. Despite Xorg always showing as selected, it uses Wayland unless I click the Xorg session again ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 21:05:34 2021 InstallationDate: Installed on 2018-09-13 (1106 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gdm3 UpgradeStatus: Upgraded to impish on 2021-09-24 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- 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/1945008 Title: Log in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1914821] Re: Disks won't execute
I am having the same issue in Fedora 34 / gnome-disk-utility 40.1 / Gnome 40. Probably not an Ubuntu specific issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1914821 Title: Disks won't execute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1914821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Thank you, I tested the new values and it all works as expected for me. However, not sure what it is but the 225% value seems to change the rendering in an unpleasant way. Not sure if it's only not being used to it, but for the time being it feels more "comfortable" reverting to 200% and upping the font scaling a bit, as I did before. -- 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/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Daniel, I am affected as well like in the previous bug. Model is Dell XPS 9575 2-in-1. Shall I run the apport-collect as well? -- 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/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
@albertvaka I realize it stopped working for me as well, 20.04 with mutter 3.36.6-1ubuntu0.20.04.2 Still same machine as in above posts, Dell XPS 9575 2-in-1 No idea if same problem reappeared or it's an entirely new one -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+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
@michel.ekimia, please see bug #1880596 -- 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/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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Maybe I should add that I qualify the OSK appearing in laptop mode under X as "Success" because: -This is how it behaved until 19.10 both under X and Wayland -In the upstream bug it was mentioned that the laptop vs tablet mode detection would not work under X and so the new behavior under Wayland (no OSK in laptop mode) could not (yet) be duplicated -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Fix released, see the new bug #1880596. Should this one be marked a duplicate of bug #1880596? -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Installed mutter 3.36.3-0ubuntu0.20.04.1 from -proposed. This fixes the bug for me on the Dell XPS 9575 (could not test on the Asus Zenbook) Tested: 1. Logged into Xorg session 2. In laptop mode (physical keyboard enabled): - Touch Activities > Search: Success, OSK appears - Touch Show Applications > Search: Success, OSK appears - Open gnome-term > touch input area: Success, OSK appears - Open gedit > touch test areas: Success, OSK appears - Open Firefox > touch search box: Success, OSK appears - Open GnuCash (gtk application) > touch: OSK appears, but is flakey. This is as I remember it always to be - Swiped up from bottom of screen to summon OSK as needed: Success, OSK appears - In all test cases: touched DownArrow button on OSK: Success, OSK disappears 3. Folded display to tablet mode (physical keyboard disabled): - Same tests, same behavior 4. Log out and into Wayland session: - Same tests and successes in tablet mode. In laptop mode, the OSK never appears as expected due to the design decision mentioned above* * Still rather infuriating that you can touch a textfield but are not allowed to enter anything ** Tags removed: verification-needed ** Tags added: verification-done-focal ** Tags removed: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
And 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Will be fixed in 3.36.3: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242#note_823253 -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2378. I set one for the other and then Launchpad
somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
- 3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
+ 3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
sudo libinput list-devices > list-devices.txt:
was generated in laptop mode i.e. with the physical keyboard enabled.
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bugs:
+ Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+
+ [Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
+ /gnome-shell/-/issues/2378. I set one for the other and then Launchpad
+ somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
-
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Attachment added: "list-devices.txt"
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+attachment/5376642/+files/list-devices.txt
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertable laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode when physical keyboard disabled
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@seb128: Created the new bug #1880596 -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+ Related upstream bugs:
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
+ https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
- (On Wayland there is a different changed behavior with the OSK not
- appearing in the device's laptop mode, i.e. with the physical keyboard
- enabled. This seems intended and a different issue as per
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872)
+ (On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
- This bug report was created on Dell XPS 9575 2-in-1, where the bug
reproduces.
+
+ This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] [NEW] [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
Public bug reported:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell fields
like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text fields
of foreign toolkits that are expected not to trigger the OSK automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing in
the device's laptop mode, i.e. with the physical keyboard enabled. This seems
intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly Wayland
and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Affects: gnome-shell
Importance: Unknown
Status: Unknown
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1242
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@seb128: A new bug for each device? I am the OP and I reproduced this on two different foldable laptops (Dell XPS and Asus Flip), should I open a new bug for each? (When opening this here bug, I used ubuntu-bug on the Dell XPS) -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Related Bug #1851931 ? -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. It does look to me that the keyboard issue is probably separate and certainly warrants a bug, in particular if it is a regression and those 2-in-1s switched fine with Ubuntu 19.10. But I am just a mere user here, @vanvugt will know. -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. So it seems as follows, correct? This here bug report refers only to running under Xorg in Focal, where ... - the OSK does not work at all on the properly supported devices (at least the ones listed), - neither per autosummon nor on demand by swiping, - regardless of a physical keyboard not being available. This is a regression compared to Eoan. However the OSK is working in Focal as expected [1] on Wayland, on supported devices where the physical keyboard gets properly disabled. As far as I know, it is not expected for autosummon to work for KeePassXC etc., but in this case I can summon on demand in Wayland by swiping from bottom of screen. (But can't under Xorg) [1] It seems it is expected that even in Wayland the OSK is only available when the physical keyboard is disabled, according to discussion on this gnome-shell report: "On Screen Keyboard shows up on Wayland despite there is a physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 The above gnome-shell #2353 is linked from the gnome-shell report that seems to be related to the issue in this here bug, as @esjarc mentioned in the duplicate Bug #1874017, i.e.: "OSK isn't activated without physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2353 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@esjarc, does the keyboard get disabled when you fold your machines? It does on mine, as it should be. I'm just wondering where the difference comes 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@esjrac, you wrote in the duplicate Bug #1874017 that the issue occurs for you under Wayland as well. Can you repro this also in the tablet mode of the foldable devices that you mentioned there? I am asking because for me this occurs under Wayland only if the devices are laptop mode. In tablet mode, the OSK comes up fine (both auto by touching textfield and when summoned by swiping). I can still repro this (with gnome 3.36.1 on Focal) with foldable devices as described in the OP above, i.e. with: Dell XPS 9575 2-in-1 Asus Zenbook Flip UX561UD However under Xorg the OSK does not come up in tablet mode either -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
*** This bug is a duplicate of bug 1807276 *** https://bugs.launchpad.net/bugs/1807276 @esjarc, as the OP of this report I agree and also commented as much in the other #1807276 already. -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Still reproducible with Ubuntu 20.04 beta with gnome-control-center 1:3.36.1-1ubuntu4 and gnome-3.36.1, where the option to enable fractional scaling is exposed in the GUI -- 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/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1807276] Re: Cannot open Onscreen Keyboard in Xorg
But it worked before for me before, see duplicate https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556 And the part where it does not appear at all occurred in the past and was fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 -- 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/1807276 Title: Cannot open Onscreen Keyboard in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] [NEW] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Public bug reported: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Summary changed: - On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg + On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal ** Description changed: After upgrading to Focal, the OSK never appears for me under Xorg - - Does appear automatically when selecting text fields - - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan) + - Does not appear automatically when selecting text fields + - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) - Under Wayland, both these things work if the laptop is in tablet mode - (but not if it is in regular laptop mode). + Under Wayland, both these things continued to work after the Focal + upgrade if the laptop is in tablet mode (but not if it is in regular + laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 - Asus Zenbook flip UX561UD. + Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Sadly, I am not having Nvidia drivers installed and the fix about GRUB_CMDLINE_LINUX_DEFAULT="" doesn't work either for me. The only way I was able to suspend the login loop was to uninstall gdm3 and switch back to lightdm. I think it is not useful that I open up a new issue therefore I am posting my comment here. To sum it up: If I like to use gdm3 I am unable to login. Note: This is an upgraded laptop from 19.04 -> 19.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
I'm the OP and I can't. Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+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
On Eoan (on the Dell XPS 9575 mentioned before), the OSK auto-summons nearly everywhere as far as I can tell, incl. Chrome. The only application I use and found so far where this does not work is Gnucash. There is even an improvement in X that helps in this case: the OSK now can be summoned by swiping up from the bottom screen edge, in the same way as it previously worked only on Wayland. -- 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/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 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Holy cow, I completely misunderstood the UI. Sorry for bothering!!! ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
And regarding "Can you recall when was the last time the cursor showed up correctly for you? (Like, about 1 day ago, about 1 week ago...?) Was that on disco, or eoan beta?" I cannot be sure, but it probably was within the last week that it still worked with the custom theme I had. I am tempted to say that this was "definitely" on eoan beta: - As mentioned, I had switched to the custom theme because of a change of background color due to the system theme, and that was definitely well after my upgrade to eoan (which was nearly a month ago) - I am "pretty" sure that I would have noticed if the cursor had disappeared right after switching to the custom theme as you can't edit a command line without a cursor -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Thanks. My results: No cursor visible with the command running. No cursor with any of the three cursor shapes selected (and blinking off). Colors: This did it. My system theme option was unchecked (I did that recently after some Yaru (I think) update in Eoan changed the background color from purple to gray). Therefore I had a custom theme, which did work before the cursor problem appeared: Default: white text (#FF), purple background (#3E0937) Bold: checked, same colors Cursor color: checked, same colors So now I checked the system theme option again and restarted the gnome- terminal. The background color is back to purple as it should be and the cursor is back. Thanks! However, there still seems to be a problem: When I uncheck the system theme option again (using the same custom colors) and restart the terminal, the cursor is gone again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846255] [NEW] No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Public bug reported: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
Sorry, "appear *behind* the Ubuntu dock" the -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
gnome-shell-extension-workspaces-to-dock universe, version: 51-1 When active, the Activities and Application menus stop working, incl. Super key. In addition the window management breaks, windows appear being the Ubuntu dock. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
With GNOME Shell 3.33.91: gpaste 3.30.2-1ubuntu3 (universe) gnome-shell-extension-suspend-button 0~git20180827-2 (universe) Both marked as "Error loading extension" in Tweaks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832124] Re: Moving file to Trash frequently crashes gnome-shell
** Summary changed: - Moving file to Trash requently crashes gnome-shell + Moving file to Trash frequently crashes gnome-shell ** Summary changed: - Moving file to Trash frequently crashes gnome-shell + Right-click file on desktop > Move to Trash frequently crashes gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832124] [NEW] Moving file to Trash requently crashes gnome-shell
Public bug reported: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 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: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Moving file to Trash requently crashes gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I reported this upstream here: https://github.com/hughsie/lvfs- website/issues/335 It looks like it's related to the metadata being too big. ** No longer affects: appstream-glib (Ubuntu) ** Bug watch added: github.com/hughsie/lvfs-website/issues #335 https://github.com/hughsie/lvfs-website/issues/335 ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
That message is coming from appstream-glib, somewhere around here: https://github.com/hughsie/appstream- glib/blob/843caabdeca6ae15f400f38536bc666340c30465/libappstream-glib/as- store.c#L2329 I would recommend to start out with trying a newer appstream-glib to see if that helps. ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1829813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
(I still get the "Failed to apply DRM plane", but the immediate unrotation does not happen anymore. This is at least in Wayland, could not check X) -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
I cannot reproduce this anymore on Ubuntu 19.04, gnome-shell 3.32 -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820088] Re: GIMP doesn't start in disco dev
I had libgegl-0.4-0 from Otto's PPA that was claiming to be newer than the version in Disco. I used Synaptic to force downgrade to the Disco version, now everything works fine. It could be this or you have an old version of libgegl in /usr/local/bin from another install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1820088 Title: GIMP doesn't start in disco dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1820088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826391] [NEW] UI allows dangerous mistakes
Public bug reported: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1826391 Title: UI allows dangerous mistakes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1826391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty
** Changed in: libxmlb (Ubuntu) Status: Triaged => Fix Released ** Changed in: libxmlb (Ubuntu Disco) Status: Won't Fix => Fix Released ** Changed in: libxmlb (Ubuntu) Assignee: Robert Ancell (robert-ancell) => Mario Limonciello (superm1) -- 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/1817223 Title: [disco-proposed] The list of applications in Ubuntu Software is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+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
FYI, fix for Wayland: bug #1816808 -- 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 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Sorry for spamming, I should have clicked the source link on OMGUbuntu, experimental is apparently expected: https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling- in-wayland-landed/ -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
(Note that adding scale-monitor-framebuffer to experimental mutter settings was already the workaround mentioned in Bug Description, so not 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I have this now on Disco in Wayland and with update to mutter 3.32 (incl. proposed, except gnome-settings-daemon at 3.31.91-1ubuntu1), but apparently I had to add scale-monitor-framebuffer to the gsettings key org.gnome.mutter.experimental-features (as mentioned by https://www.omgubuntu.co.uk/2019/03/best-gnome-3-32-features). Is this expected? I also still have the limited options as in gnome-control-center bug #1795483 from my comment #34 above. (100, 125, 150, 175, 200), with 200 still too small on this display (15" with 3840*2160) -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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
I can confirm on Disco that this is definitely better, but not completely solved for me: gnome-settings-daemon 3.30.2-2ubuntu1 Screen Keyboard is off in Universal Access settings * Good in both X and Wayland: 1. Touch Activities on panel 2. Touch "type to search" box -> OSK comes up. 3. Close OSK with ArrowDown icon 4. Touch "type to search" box again -> OSK comes up again. (Same good behavior for: Applications on dock -> "Type to search" GDM login screen -> password field) * Good only in X, not good in Wayland: 1. Two applications side by side e.g. gnome-term and gedit 2. Switch windows by touching -> In X, OSK comes up on focus change, but not in Wayland . So in X it is good so far but ... 3. Close OSK by ArrowDown icon 4. Touch _same_ window again (and hence no focus switch) -> no OSK even in X 1. Start on an empty workspace: Firefox, nautilus, epiphany, and others: 2. Touch text entry fields -> OSK comes up in X but not in Wayland * Bad in both X and Wayland: 1. Go to empty workspace 2. Launch gnome-term, LibreOffice Writer or Calc, others: -> no OSK. However in X (but not Wayland) ... 3. Switch focus by touching any menu on Gnome panel 4. Touch gnome-term again -> Now OSK comes up * Bad in X when OSK does not come up automatically: When OSK does not appear automatically, there is still no way to summon it on demand. (While in Wayland swiping up still works as workaround but remains difficult to discover) -- 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 1720089] Re: Desktop isn't part of "places" (left bar) in artful
(This is in Disco, nautilus 1:3.31.90-1ubuntu2) -- 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/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720089] Re: Desktop isn't part of "places" (left bar) in artful
Confirming what Olivier wrote, I see it in X but not Wayland -- 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/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811169] Re: Device firmware update does not detect AC power
To me this sounds like it's probably Gnome Software not fwupd. ** Changed in: fwupd (Ubuntu) Status: New => Invalid -- 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/1811169 Title: Device firmware update does not detect AC power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1811169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
Yes, confirmed this is still fixed in 3.18.1-0ubuntu4.18.04.8. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-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/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I just downgraded an XPS 9370 and then upgraded it again using gnome- software 3.28.1-0ubuntu4.18.04.8 and it works like I expected. ** Tags removed: artful verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-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/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805047] Re: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by-lid-close in Wayland session
Oopsie, indeed the crash on lid close is gone after disabling extensions. Even the very act of turning off the overall extension switch in Tweaks crashes the session. Will figure out the culprit extension then. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1805047 Title: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by- lid-close in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
@Joe, at least in Wayland (did not test in X yet) the touch does not register when I touch anywhere right at the edge of the display. That goes for the whole perimeter of the display. E.g., srollbars of maximized windows on the right, dock launchers on the left, and the Gnome panel menu top right are not triggered in this case. The same goes for the Activities menu, but when I aim e.g. for the middle of Activities or the middle of the panel menu, they are triggered fine. And I can never repro this "flash", either the touch is ignored or the Activities open properly. -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
@Joe: Can you confirm that you see the unrotation behavior and the log entry, "gnome-shell[5422]: Failed to apply DRM plane transform 1: Invalid argument" only in a Wayland session? I just realized that this is the case for me. In an X session, the rotation works perfectly whatever the display angle (below or above 180 degrees) and the error does not appear in the 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1805047] [NEW] [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by-lid-close in Wayland session
Public bug reported: In an X session, suspend and wakeup works when initiated either by lid close or from panel menu. In a Wayland session, suspend and wakeup works only when initiated from panel menu. However, gnome-shell segfaults when suspend is initiated by lid close. When reopening the lid, I am back at the login screen for a new session. (When suspend-on-lid-close is disabled in Gnome Tweaks, gnome-shell and the Wayland session survive the lid close) In dmesg I find the gnome-shell segfault every time, here on the second line: [ 139.420519] wlp2s0: deauthenticating from e0:28:6d:5d:ab:1b by local choice (Reason: 3=DEAUTH_LEAVING) [ 139.964629] gnome-shell[4166]: segfault at fbc8 ip 7fd049223eb8 sp 7ffdda00d6e0 error 5 in libst-1.0.so[7fd0491fd000+2b000] [ 139.964633] Code: 00 00 48 8d 3d 67 78 00 00 e9 44 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d eb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d [ 140.063376] rfkill: input handler enabled [ 140.603550] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 140.723020] [drm] UVD and UVD ENC initialized successfully. [ 140.832956] [drm] VCE initialized successfully. [ 140.951177] PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 21:13:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (72 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed third-party-packages wayland-session -- 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/1805047 Title: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by- lid-close in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" - After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. - [Note: either something changed with latest updates from today or I made a mistake before and overlooked the 100%. I get *5* experimental options: - 100, 125, 150, 175, and 200%] + After applying and rebooting, the options offered change to 100, 125, + 150, 175, and 200%. Note that there is no value larger than 200% which + is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791454] Re: system-monitor produces many apparmor permission denied warnings
iotop is showing systemd-journal writing to disk at around 1MBs while system-monitor is running. 420 entries per seconds. Cheers -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1791454 Title: system-monitor produces many apparmor permission denied warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575 -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
I've upgraded on a bionic machine to 3.28.1-0ubuntu4.18.04.5. xdg-open FirmwareUpdateLinux_00.00.07.cab opens a composite CAB file in gnome-software now. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I've tested the fwupd half of this SRU (couldn't test the gnome-software as it's not yet in place). The fwupd half works properly. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
I cannot confirm this on my machine. I do not know if what I see it intended behavior, but what I see is still not what either the Gnome 2.28 release notes or the Ubuntu help say should happen. When I enable the OSK in universal access, the OSK opens way too often but not always when it should. This is same in X or Wayland: - Opens when typing on keyboard into Activities or Applications search box. (I don't know if this is good behavior for universal access, but it is not good behavior for general touch use: When I type on the keyboard I don't need an OSK. ) - Opens when I touch into Activities or Applications search box. (OK) - Opens when I start a gnome-term even before I touch it or type into it. But it does not open when I switch focus and touch into an already-open gnome-term. (Not OK) - Does not open with Firefox or Chrome. (May be technically unavoidable, but then requires a way to open the OSK on demand) - In Wayland, swiping up of from the bottom of the screen opens OSK. This does not work in X and I don't see another way) Turning OSK off in Universal access, the behavior becomes better for general touch use as the OSK does not uselessly appear when typing, only when touching - at least in those cases when it does. Otherwise the behavior is unchanged compared to being on in Universal Access. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Thanks Efthimios. I am still a little unclear about what the intended behavior is. Should it auto open when touching a text field e.g. in Chrome? And are you using X or Wayland and it you enable the OSK in Universal Access? Thanks. FWIW, for me on Cosmic it is still as described in the description at least on Wayland, I did not try X recently -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
Thank you. I had written bug #1792813 about the sensors not being found with kernel 4.18. This is fixed in the mainline 4.19 (see the other report). The incorrect automatic back rotation also happens with 4.19. However, note that what exactly happens depends on whether the keyboard vs display angle is smaller or larger than 180 degrees. I am copying my description from the other bug with some edits for brevity and to fix errors: monitor-sensor output detects the correct orientation in all attempts. When the screen auto-rotates back, monitor-sensor does NOT output a switch to "normal". So I suppose the sensor outputs remain correctly detected and the switching back happens elsewhere. The issue may be connected to a hardware quirk in how the rotation is implemented on the Dell XPS, which similarly also occurs in Windows (https://www.dell.com/community/XPS/Dell-XPS-13-9365-Rotation-lock-unavailable-grayed-out-EXPLAINED/td-p/6075400): * Laptop mode, i.e. keyboard-to-screen angle SMALLER than 180 degrees: In Windows, this automatically engages the rotation lock, i.e. the screen does not rotate at all. * Tent/tablet mode, i.e. keyboard-to-screen angle LARGER than 180 degrees: In Windows, this releases the rotation lock automatically. In Ubuntu, the rotation lock in the Gnome panel does NOT automatically engage if the angle is smaller than 180 degrees, but rotation behavior depends on angle: * Angle SMALLER than 180: - Orientation "left-up": screen rotates to portrait correctly, but immediately switches back to normal. - Orientation "right-up": screen rotates to portrait correctly and in most attempts stays like this, but occasionally it immediately switches back to normal. - Orientation "bottom-up": screen rotates rotates upside-down correctly, but immediately switches back to normal. - Orientation "normal": screen always rotates back correctly (if it didn't automatically switch back anyway). * Angle LARGER than 180: - Orientation "left-up": screen rotates to portrait correctly and in most attempts stays like this, but occasionally it immediately switches back to normal. - Orientation "right-up": screen rotates to portrait correctly and apparently randomly either stays like this or immediately switches back to normal. - Orientation "bottom-up": screen rotates rotates upside down correctly most of the time (but occasionally doesn't). - Orientation "normal": screen always rotates back correctly (if it didn't automatically switch back anyway). So the "left-up" and "right-up" behaviors seem somewhat (but not entirely) swapped depending on the keyboard-screen angle. -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
