Public bug reported:
Suspend to hibernate is a new feature that will put the system into
hibernate after a period of time spent in the system's supported sleep
state. This mode will be used on some systems that take suspend to idle
in the future with Ubuntu 18.04.
This feature is available in
No, not on modern system. We haven't used that technology for a while.
--
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/1756006
Title:
FFe: Support
Unfortunately this stack trace is client side, but we don't know what
actually happened on the daemon during this situation to get to the
bottom of the problem.
Can you reproduce this again? If so, it would be really useful if you
could run the daemon under debug (or possibly valgrind) to figure
Thanks for confirming. I'll close this issue then. If it happens
again for anyone, please open a new issue .
** Also affects: appstream-glib (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Xenial)
Importance: Undecided
Status: New
**
** Also affects: klibc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In 4.17 a new attribute is introduced to configure the hibernation
resume offset. Since Ubuntu enables a swapfile by default this attribute
is important to be able to make hibernation work
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760106
Title:
Enable configuring resume offset via
The rename is done upstream, it's now suspend-then-hibernate. I'm
uploading systemd with these patches.
As for G-S-D, I've adjusted it for the rename too but it's still waiting
to be merged.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Summary changed:
- FFe: Support
Gsd is pushing for the name change in systemd, so I'm going to get that
upstreamed before bringing this into Ubuntu. (Suspend to hibernate to
suspend then hibernate).
In terms of UI where would it Land? I figure it should be a policy setting
on systems that ship with it, but you're probably right
Hi All,
Those affected by this, can anyone readily reproduce it still?
If so, can you please try to upgrade to the version of fwupd in xenial-proposed
to see if it persists?
Thanks,
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu)
** Description changed:
+ The fix for this particular issue is tracked in SRU bug
+ https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999
+
+ Regression potential:
+ Fixes for this particular bug would have the risk to manifest in devices not
showing up in gnome-software, but this risk
fwupd
--
This has been fixed upstream in the 1.1.3 release, so marking the development
release task complete.
The 1.0.9 SRU bug for bionic is here:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999
gnome-software
There is an SRU in progress for
*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795
** This bug is no longer a duplicate of bug 1756695
gnome-software crashed with signal 5 in g_dbus_proxy_call_sync →
fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates →
*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795
I'll mark it as such, if we have evidence it's not at some point we can
re-visit.
** This bug has been marked a duplicate of bug 1760795
gnome-software leaks file descriptors
--
You received this bug
*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795
** This bug is no longer a duplicate of bug 1756695
gnome-software crashed with signal 5 in g_dbus_proxy_call_sync →
fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates →
*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795
** This bug is no longer a duplicate of bug 1756695
gnome-software crashed with signal 5 in g_dbus_proxy_call_sync →
fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates →
This particular issue hasn't received reports in anything newer than
Ubuntu 16.04. The fwupd version in 16.04 is in deep maintenance mode
and issues on the branches contained there (0.7.x and 0.8.x) will not be
fixed.
** Changed in: appstream-glib (Ubuntu)
Status: Triaged => Invalid
**
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
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
Public bug reported:
[Impact]
Double clicking a composite CAB file containing multiple firmware files
displays an error message in gnome-software.
This prevents installing composite firmware CAB files via a GUI unless
they come from LVFS.
[Test Case]
* Double click a composite CAB file
*
$ gnome-software --version
gnome-software 3.30.2
$ xdg-open DellUsbCDockFirmwareUpdateLinux_00.00.07.cab
Now does the right thing
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop
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:
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
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
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.
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.
** 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
I see the same behavior on a display with the same dimensions on a different
laptop:
Asus ZenBook Flip 15 UX561UD
15.6 inch 16:9, 3840 x 2160 pixel, 282 PPI
On both the Dell and the Asus:
Without the experimental setting, options offered are 100, 200 (too small), 300
(too large), 400%.
With the
For my 15" display with 3840*2160, without the workaround I get 100, 200 (too
small), 300 (too large), and 400. Is it intentional that with the experimental
workaround from the first comment enabled, I have 125, 150, 175 and 200% but
nothing above it?
The maximum of 200% is too small and I use
** Description changed:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
- scaling options in the Gnome 3.30.1 (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
Daniel, new gnome-control-center bug #1795483
--
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
Public bug reported:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
scaling options in the Gnome 3.30.1 (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
When I did those PR upstream I did it with a swapfile actually on
Ubuntu. The key comes down to how initramfs-tools hands off the
offsets. It's kinda a jumbled mess though.
I started a discussion here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950
but it got stalled and I got busy
Try d-feet as root. I think I recalled seeing this too.
--
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/1756006
Title:
FFe: Support suspend-then-hibernate
To manage
nic)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: fwupd (Ubuntu Bionic)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
** Changed in: fwupd (Ubuntu)
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
--
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
Following upstream suggestion
** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config
(Ubuntu)
--
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/1791367
>From the upstream report:
"A possible explanation would be that gnome-settings-daemon is not handling one
of the keys that it should be handling. And gnome-settings-daemon also disables
the kernels handling of the RFKill keys at the same time.
What you could do:
Check which key is emitted
In the upstream report for gnome-shell (https://gitlab.gnome.org/GNOME
/gnome-shell/issues/555) some analysis steps were kindly provided. It
seems that the actual cause is that gnome-settings-daemon's rfkill
plugin fails to turn on airplane mode. Following the instructions, I can
turn it on with
As per analysis result in upstream report
** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon
(Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
@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
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
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
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
@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
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
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.
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
--
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
*** This bug is a duplicate of bug 1694076 ***
https://bugs.launchpad.net/bugs/1694076
** This bug has been marked a duplicate of bug 1694076
No error message on firmware update fail
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Since this was in 3-26 and now at 3-28 in bionic, closing this issue.
** Changed in: gnome-software (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
** Package changed: caribou (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730211
Title:
Unable to type capital letters using onscreen keyboard
To
*** This bug is a duplicate of bug 1719797 ***
https://bugs.launchpad.net/bugs/1719797
So this is actually a duplicate of a previous issue which links to this
upstream issue.
https://gitlab.gnome.org/GNOME/gnome-software/issues/341
Please subscribe to the upstream issue and add comments
** Bug watch added: Red Hat Bugzilla #1580450
https://bugzilla.redhat.com/show_bug.cgi?id=1580450
** Also affects: gnome-software (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1580450
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Sorry my earlier removal of the tag was unintentional, readding
** Tags added: universalaccess
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen
*** This bug is a duplicate of bug 1719797 ***
https://bugs.launchpad.net/bugs/1719797
@Will,
I'm pretty sure this is that issue;
https://gitlab.gnome.org/GNOME/gnome-software/issues/341
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Changed in: gnome-software (Ubuntu)
*** This bug is a duplicate of bug 1719797 ***
https://bugs.launchpad.net/bugs/1719797
I can't seem to add it as an upstream tracker for whatever reason
though.
** This bug has been marked a duplicate of bug 1719797
Firmware update seemingly not working
--
You received this bug
This issue has been fixed upstream. It requires fixes in both gnome-
software and fwupd.
gnome-software fix (on the Gnome Software 3-28 branch):
https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e
fwupd fix (on the 1_0_X branch):
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
** 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
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
(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
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
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
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
(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.
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
** 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
(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.
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
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:
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
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-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
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
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
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
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:
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
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
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
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.
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
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
*** 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
@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
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
@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.
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
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
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
@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
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:
** 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
@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
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
** 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
+
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]
@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
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
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
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
701 - 800 of 871 matches
Mail list logo
