Slow and lost keyboard and mouse events

[Brian Burch]

This was a fresh amd64 installation with 18.10 desktop, upgraded to 19.04 as soon as available. It has been getting worse over the last few weeks and is now so bad I can hardly type an email (or this bug report!) without having to fix many typos.

journalctl shows many different gnome errors, so it is difficult to figure out which is the underlying cause and which are simply collateral damage.

There are two sequences that appear first after a reboot, and the first of these has been reported many times on ubuntu releases going back for years:-

Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module "canberra-gtk-module"

.... and ....

Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.89/org/ayatana/NotificationItem/software_update_available
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon
Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable to update overlay icon
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

Is this a recent regression? I know for sure the system wasn't this unresponsive 3 weeks ago, but I cannot be sure when it started to go wrong. My mouse/keyboard combo has a USB-wireless dongle and I've fiddled around with distance and battery state until I was sure the problem was somewhere else and started to check the system log.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-software 3.30.6-2ubuntu4.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 5 11:53:37 2019
InstalledPlugins:
 gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1
 gnome-software-plugin-snap 3.30.6-2ubuntu4.19.04.1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.04
Package: mutter
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
Tags: disco
Uname: Linux 5.0.0-23-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-04-28 (99 days ago)
UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare scans sudo video wireshark
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
Package: mutter
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
Tags: eoan
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (131 days ago)
UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare scans sudo video wireshark
_MarkForUpload: True

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1838919

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Daniel van Vugt (vanvugt)]

The GL errors appear to be from Chrome/Chromium. Not Gnome Shell at all. Although it does sound like they're related to snaps too:

https://wiki.ubuntu.com/DesktopTeam/GNOMESnapStartup

[Brian Burch (brian-pingtoo)]

Daniel post #2. That was exactly how I opened this bug report, so what exactly are you missing?

Daniel post #3. I don't use Chromium, by preferred browser is stock vanilla Chrome from their own repository. I did not think Chrome was delivered as a snap - are you sure your comment is relevant?

[Daniel van Vugt (vanvugt)]

Because this bug was reported against the wrong project (comment #1) it has the wrong attachments. To correct that please run:

  apport-collect 1838919

Thanks for using 'ubuntu-bug' already. That's just a standard response which was not entirely appropriate in this case.

I know, Chrome/Chromium's involvement sounds weird, but:

  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: [4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-

is from the Chromium source code and not from any part of Gnome Shell.

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

Thanks for explaining Daniel #5. You will see I ran the command again.

However... It is interesting to see that even the apport-collect command from a new terminal session triggered the canberra error.

brian@schizo:~$ apport-collect 1838919

(apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Gtk-Message: 08:30:48.771: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.

(apport-gtk:21631): Gtk-WARNING **: 08:30:49.106: GTK+ module /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Gtk-Message: 08:30:49.106: Failed to load module "canberra-gtk-module"
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=t0cRSdJcr5xGQ4MLSbPG&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
brian@schizo:~$

[Brian Burch (brian-pingtoo)]

Also, I will attach journalctl -xb log taken as soon as I booted the system and logged on this morning. It seems to me that as soon as systemd started the gnome terminal server unit, related error messages began to be generated.

Chrome/chromium had not been started at the time - it was autostarted by your apport command quite a while later.

[Daniel van Vugt (vanvugt)]

Thanks again. Life is rarely simple enough to reveal the cause of a shell bug in the log. If it was though, then the canberra errors are the only ones I think could be relevant.

[Brian Burch (brian-pingtoo)]

What can I do to help you diagnose the problem further, Daniel?

I think something changed recently, and that must have been an update. I do not believe I have installed any new packages that might have called for GTK2, so my guess is that it has been there since the clean 18.10 install and not been in conflict with GTK3 until recently.

Searching on the conflict has not revealed anything helpful to me because this kind of error has popped up lots of times as far back as ubuntu 12.04. The packages recommended to be installed to "fix" these old problems all seem to be present on my system already.

Is there an easy way to discover what is calling for GTK2, or is that being done by canberra on behalf of some applications, but not others?

Is there any point in me booting recovery mode to see whether the errors (keyboard mapping too, don't forget) are logged from the simple tty console login?

[Daniel van Vugt (vanvugt)]

Just a couple of ideas:

* Please run 'top' and tell us if any process is using high CPU while the problem occurs.

* Please run 'snap list' and paste the output here.

[Daniel van Vugt (vanvugt)]

Please also run:

  dpkg -l > allpackages.txt

and attach the file 'allpackages.txt'.

[Brian Burch (brian-pingtoo)]

Hi Daniel, thanks for not giving up! First, here is snap list:-

Name Version Rev Tracking Publisher Notes
core 16-2.39.3 7270 stable canonical✓ core
core18 20190723 1074 stable canonical✓ base
gnome-3-26-1604 3.26.0.20190705 90 stable/… canonical✓ -
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 67 stable canonical✓ -
gnome-calculator 3.32.1 406 stable/… canonical✓ -
gnome-characters v3.32.1+git2.3367201 296 stable/… canonical✓ -
gnome-logs 3.32.0-4-ge8f3f37ca8 61 stable/… canonical✓ -
gnome-system-monitor 3.32.1-3-g0ea89b4922 100 stable/… canonical✓ -
gtk-common-themes 0.1-22-gab0a26b 1313 stable/… canonical✓ -
pdftk-smoser 2.02-4 18 stable smoser -

[Brian Burch (brian-pingtoo)]

top on 4 second intervals rotates the same 5 or 6 threads, so I set the interval to 20 seconds and copied the output to a file, which I have attached. I have also attached the dpkg list.

[Brian Burch (brian-pingtoo)]

dpkg list next...

[Brian Burch (brian-pingtoo)]

I had a bit of a brainwave this morning - or perhaps just awoke from my stupidity!

I also have a laptop which runs ubuntu studio 19.04 amd64. At the moment, my desktop which is suffering has the 5.0.0-23-generic kernel. The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all these problems.

The laptop also has gtk2 and gtk3 packages installed, although I haven't yet done a package-by-package diff.

As far as I can remember, they both have mostly the same applications, although studio has a lot more. The laptop currently has upgrades waiting to be installed for the kernel, chromium, chrome and mutter (and quite a few more packages).

Should I upgrade those packages on the laptop one at a time, to see whether the same problem appears?

[Traumflug (mah-jump-ing)]

If you're running on Wayland it might be related to this:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510

It looks like a busy gnome-shell (or -extension) can eat mouse movement events, so it might eat keystrokes as well. Second way to reproduce the issue (for testing whether you experience the same issue) is in

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510#note_577952

All this doesn't happen on X11, though.

[Brian Burch (brian-pingtoo)]

Thank you very much for your suggestion #21, Traumflug. I read the issue you quoted and to be honest, I was quite disappointed in the responses so far.

The symptoms sound very similar to those I reported here. I compared the wayland packages on my desktop (slow or lost mouse and keyboard events) with those on my laptop (ubuntu studio), which works satisfactorily. I will attach a file containing the two dpkg lists for comparison.

I really don't understand the wayland architecture, but was happy to use the recommended workaround when running sudo gui programs such as gparted.

I notice two differences and wonder whether either of them might account for the diference between my two systems?

1. The desktop has three i386 old packages not installed on the laptop. Perhaps I should delete them?

2. The desktop has the xwayland package installed, but the laptop does not.

What do you think? Is this helpful in tracking down the root cause of the problem? Is there anything I can do to assist with further diagnosis, given I have two systems side-by-side for comparison?

[Traumflug (mah-jump-ing)]

Installed packages don't matter if their content isn't in use. It does matter whether you run an X11 or a Wayland session.

To switch between both, log out to get to the login screen. There is a gears icon right above the password entry field, click on it. This should open a menu allowing to choose between "Ubuntu on Xorg" and "Ubuntu on Wayland". Having this choice done, log in, you'll be in the selected type of session.

Basically, all applications work in both session types, but there are a number of smaller visual distinctions. For example, Firefox draws its menu inside the window bar on Wayland, while it draws the menu under the window bar on X11. Also, on X11 there's a process "Xorg" running, while on Wayland there's a process "XWayland" (or similar).

[Brian Burch (brian-pingtoo)]

On 14/8/19 8:22 pm, Traumflug wrote:
> Installed packages don't matter if their content isn't in use. It does
> matter whether you run an X11 or a Wayland session.
>
> To switch between both, log out to get to the login screen. There is a
> gears icon right above the password entry field, click on it. This
> should open a menu allowing to choose between "Ubuntu on Xorg" and
> "Ubuntu on Wayland". Having this choice done, log in, you'll be in the
> selected type of session.

I had forgotten the gear wheel.. the last time I used it was when unity
came out as the new default and I preferred Gnome Classic. Thanks for
reminding me.

> Basically, all applications work in both session types, but there are a
> number of smaller visual distinctions. For example, Firefox draws its
> menu inside the window bar on Wayland, while it draws the menu under the
> window bar on X11. Also, on X11 there's a process "Xorg" running, while
> on Wayland there's a process "XWayland" (or similar).

The default on the desktop system was "ubuntu", so I changed to "Gnome
on Xorg". The presentation details are different (obviously) but don't
bother me. However, I get exactly the same errors logged and slow input
events:-

Aug 15 07:21:43 schizo gnome-control-c[8320]: GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded.
                                               GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:43 schizo gnome-control-c[8320]: Not loading module
"atk-bridge": The functionality is provided by GTK natively. Please try
to not load it.
Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so
cannot be loaded.
                                               GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module
"canberra-gtk-module"
Aug 15 07:21:44 schizo gnome-control-c[8320]: GTK+ module
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so
cannot be loaded.
                                               GTK+ 2.x symbols
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
Aug 15 07:21:44 schizo gnome-control-c[8320]: Failed to load module
"canberra-gtk-module"

I will try again but this time only start a terminal session. I realise
there is a lot of processes running to support a single graphical user
session, but I'll keep Chrome and Thunderbird out of the variables.

[Brian Burch (brian-pingtoo)]

I didn't see any problems logging on with gnome on xorg, or starting the first terminal session.

However, as soon as I started the second terminal, the GTK2/GTK3 error messages poured out. Opening a new tab on the same window does not generate the messages.

This sounds like your gnome bug report - it doesn't look like a widget, or an application, but something more fundamental.

I wonder why my system even has the i386 packages installed - were they pulled in by an application (such as wine) which isn't installed on my laptop? What is the best way to locate the culprit - I now know it isn't Chrome, thunderbird, nautilus or netbeans. It's hard to believe gnome-terminal is the root cause.

[Brian Burch (brian-pingtoo)]

I upgraded both my Ubuntu Desktop and UbuntuStudio systems to 19.10 Eoan (with gnome mostly at 3.34). The symptoms have not changed... my desktop still hangs, loses keyboard events, and the log fills with the GTK 2/3 conflict messages. Meanwhile my Studio system behaves perfectly!

The log messages are generated by nautilis, gnome terminal, thunderbird, and several other applications, but I do not think they are the culprits - just the victims of something unseen.

The Studio system also has many GTK2 packages installed alongside the GTK3 ones, so there isn't a simple explanation for the difference in behaviour. I will do a side-by-side comparison of installed packages to see if there is some sort of clue.

Meanwhile, I would be grateful if anyone could suggest how to identify the guilty component. I would love to purge it!

[Daniel van Vugt (vanvugt)]

It sounds like the affected system is uniquely broken. The simple answer would be to do a backup and then wipe/reinstall it from scratch.

The complex answer would be to check for gnome-shell extensions, uninstall any non-Ubuntu ones. And to remove the relevant gtk-2 libraries and see what else the system warns you is depending on those, which is likely inclusive of the cause of this bug.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Brian Burch (brian-pingtoo)]

Sorry for the delay. The problem still exists under 19.10 desktop, but does not occur quite as often. However, it is slightly harder to escape from... I either need to wait 20+ seconds uselessly pressing keys I will have to subsequently delete, or tab to another command prompt, type something in easily, then return to the "stuck" prompt.

My comment is only to bring the bug report up to date and keep it open. We are only a few weeks from the 20.04 release, where this bug will be much more important if still present.

[Daniel van Vugt (vanvugt)]

The conversation above is no longer fresh in my memory, but I can see a couple of problems worth mentioning:

* The bug description at the top doesn't clearly describe the problem. If the issue is "Slow and lost keyboard and mouse events" then please explain how you experience that issue in more detail; and...

* Avoid mentioning log messages in the discussion and bug description as they are usually irrelevant and misleading.

* Your attachment GsettingsChanges.txt seems to mention a few changes on the system that might relate to the problem:

b'org.gnome.desktop.a11y.keyboard' b'mousekeys-max-speed' b'750'
b'org.gnome.desktop.a11y.keyboard' b'mousekeys-init-delay' b'160'
b'org.gnome.desktop.a11y.keyboard' b'mousekeys-accel-time' b'1200'
b'org.gnome.desktop.a11y.keyboard' b'bouncekeys-beep-reject' b'true'
b'org.gnome.desktop.a11y.keyboard' b'mousekeys-enable' b'true'
b'org.gnome.desktop.a11y.keyboard' b'stickykeys-modifier-beep' b'true'
b'org.gnome.desktop.a11y.keyboard' b'stickykeys-two-key-off' b'true'
b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-accept' b'true'
b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-press' b'true'
b'org.gnome.desktop.a11y.keyboard' b'disable-timeout' b'120'

If you don't remember why you have those set then please remove them by running:

  dconf reset -f /org/gnome/desktop/a11y/

and then reboot.

[Daniel van Vugt (vanvugt)]

Actually I should have just continued from comment #27. To do that please run:

  mv ~/.local/share/gnome-shell/extensions ~/old-extensions

and then reboot. Any improvement?

[Daniel van Vugt (vanvugt)]

Also, if you have upgraded to 19.10 then please run this again to send us fresh system information:

  apport-collect 1838919

[Brian Burch (brian-pingtoo)]

On 24/2/20 3:12 pm, Daniel van Vugt wrote:
> Actually I should have just continued from comment #27. To do that
> please run:
>
> mv ~/.local/share/gnome-shell/extensions ~/old-extensions

Oops! I had already run the "dconf reset"!

Never mind, I was not aware of having changed the settings from their
original defaults. I presume they were residual from an earlier release.

> and then reboot. Any improvement?

The keyboard hang happens fairly frequently, but perhaps less often than
before the reset. Also, mouse hangs are rare and recover automatically,
so I can't be certain there is still a problem.

I will run the apport-collect, but I am content to live with the problem
and re-assess when 20.04 is available.

Thanks for caring!

Brian

> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mutter (Ubuntu)
> Status: New => Incomplete
>

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Brian Burch (brian-pingtoo)]

apport information

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Brian Burch (brian-pingtoo)]

Daniel

I am Brian's wife, Jane

I am devastated to let you know that Brian succumbed to his prostate
cancer and died a few weeks ago
Please let everyone know

Thanks

Jane Burch

On 7/8/20 7:50 pm, Daniel van Vugt wrote:
> Thank you for reporting this bug to Ubuntu.
> Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
>
> See this document for currently supported Ubuntu releases:
> https://wiki.ubuntu.com/Releases
>
> We appreciate that this bug may be old and you might not be interested
> in discussing it any more. But if you are then please upgrade to the
> latest Ubuntu version and re-test. If you then find the bug is still
> present in the newer Ubuntu version, please add a comment here telling
> us which new version it is in and change the bug status to Confirmed.
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: Incomplete => Won't Fix
>
> ** Changed in: mutter (Ubuntu)
> Status: Incomplete => Won't Fix
>