DELL M3800 Touchscreen not working after login (but works if fwupd is removed)

[altadeos]

Upgrade focal fwupd from 1.3.11 to 1.4.7.

[Impact]

 * touchscreen is working after login on certain HW
 * Current LTS is the OEM Project scope, so we need to SRU it.
 * It's a specific HW-related upstream fix.

[Test Plan]

 * Wit this upgraded, with specific HW, check if touchscreen still
   working after login.

[Where problems could occur]
[Other Info]

 * It's low risk given it's an HWE upstream fix.

-----

Hello,

I have freshly installed Ubuntu 20.04 and have a bug on my M3800.
The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it.

I'm on a dual boot computer and all is working well on Windows 10.

How can I help you to track this bug and solve it ?

Best regards

[altadeos (altadeos)]

add lspci attachment

[altadeos (altadeos)]

add dmesg log

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1886912/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[altadeos (altadeos)]

I Think this problem is related to kernel or Gnome.
Tried with Nvidia proprietary driver and Intel driver and the problem is the same.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/

[altadeos (altadeos)]

Hello,

Tried with the latest mainline kernel and the problem is the same.

uname -a

5.8.0-050800-generic #202007052030 SMP Mon Jul 6 00:37:33 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Best regards

[altadeos (altadeos)]

dmesg on latest mainline kernel

[altadeos (altadeos)]

lspci -vnvn on latest mainline kernel

[Kai-Heng Feng (kaihengfeng)]

Can you please add "dyndbg='file drivers/usb/* +p'" to kernel parameter, and attach dmesg here? Thanks!

[altadeos (altadeos)]

here you can find the result of this test

[altadeos (altadeos)]

this test was done on the actual kernel 5.4

[Kai-Heng Feng (kaihengfeng)]

Can you please test if enabling "automatic login" makes any difference? Thanks!

[altadeos (altadeos)]

I tried with live usb from original iso and all is working as expected.

uname -a
Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

you can find dmesg took with live usb in attachment

[altadeos (altadeos)]

lspci live usb

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport-collect with live usb from #17 to #24 with working touchscreen

[altadeos (altadeos)]

tried with auto login on installed system and it's not working.
I will do apport-collect on installed system now.
I think I will install the system again without installing any updates to check if it's one that produce this bug.

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

apport information

[altadeos (altadeos)]

I had reinstalled ubuntu 20.04 and all was working well with the touchscreen.
I installed all updates one by one and it was working too.
Changed on prime between intel mode, nvidia on demand and nvidia performance mode too.

I was able to reproduce the bug when I activated "fractional scaling" and set it to 150% on gnome settings.
Since this the touchscreen doesn't work anymore on my ubuntu session. I had disabled "fractional scaling" and set to 200% like just after the installation but it doesn't work anymore.

Tried again with nvidia and intel mode with the same result.

Can it be a bug related to gnome ?

[altadeos (altadeos)]

gnome shell log

[Daniel van Vugt (vanvugt)]

Please clarify:

 * Does disabling fractional scaling fix the problem?

 * Does logging into 'Ubuntu on Wayland' fix the problem?

Also when the problem is happening please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

[altadeos (altadeos)]

journalctl -b0 > journal.txt
when touchscreen is not working

[altadeos (altadeos)]

After found how to reproduce the bug I have disabled fractional scaling and the problem persists.
I tried on "Ubuntu on Wayland" session and the problem is the same.

journalctl -b0 > journal_on_wayland.txt

I tried to reset gnome settings using "dconf reset -f /org/gnome/" and the problem persists.

I created a new user called "test" and I don't have a bug on it until I enable fractional scaling.

[Daniel van Vugt (vanvugt)]

I assume the device in question is the 'SYNAPTICS Synaptics Large Touch Screen'. The log file in comment #56 shows that xserver-xorg-input-libinput is aware of the device but not using it.

It also looks like you have a Xorg config file that is trying to configure that device so that config file might be the problem. Please try removing any Xorg config files you have created.

[altadeos (altadeos)]

Just a little precision.

If I open my "rom1" session where I have enabled and disabled the fractional scaling, then I close it and open the "test" session my touchscreen is not working.

If I reboot the computer and open "test" session only my touchscreen is working.

It seems that open my "rom1" session first block something on the system that affect all users that log after. If I don't open this session after a reboot I have no problem on other users.

Please find the result of this command on my test session with working touchscreen:
journalctl -b0 > journal_working_touchscreen.txt

[altadeos (altadeos)]

I never created myself any xorg config file.
I will try to delete it. Do you have the file location please ?

[Daniel van Vugt (vanvugt)]

Oh actually don't delete any config files. I just noticed we ship some default ones like:

/usr/share/X11/xorg.conf.d/40-libinput.conf

[altadeos (altadeos)]

Hello,

Can I send more informations to help to track this bug ?

Best regards.

[altadeos (altadeos)]

Hello,

The bug is still present with 20.04.2.
Can't it be related to gnome ?
How can I help ?

Best regards.

[altadeos (altadeos)]

Hello,

Tried a fresh install of Ubuntu 20.04.2 and problem is the same even I haven't activated fractional scaling.
The touchscreen is working good on live iso.
It's also working good on GDM before a session is opened.

Hope you can fix this bug.

Best regards.

[altadeos (altadeos)]

It seems to be not related only to M3800 laptop but others like HP Spectre too.
Regarding this topic I'm able to have a working touchscreen when I removed fwupd.

https://askubuntu.com/questions/1234975/touchscreen-stops-working-a-few-seconds-after-login-to-gnome-ubuntu-session-ubu

I removed fwupd with the command "sudo apt remove fwupd" and rebooted the computer and now the touchscreen is working again.

Do you need more informations ?

[Mario Limonciello (superm1)]

> fwupd
It sounds like it might be part of the reason that this commit went in upstream:
https://github.com/fwupd/fwupd/commit/277347688427fd1bf68d68d8d8788bf67d42e01c

If you want to keep fwupd on your system, for now you can instead add synaptics_rmi into the BlacklistPlugins= or DsiabledPlugins= field of /etc/fwupd/daemon.conf

[Mario Limonciello (superm1)]

Fixed for 1_4_X: https://github.com/fwupd/fwupd/commit/42e01911cd683a659367e453737d49a50ce6308f
Fixed for 1_3_X: https://github.com/fwupd/fwupd/commit/67596cb1d8e5b8177de15ee29b53a058857c3056

[Daniel van Vugt (vanvugt)]

That commit is in fwupd 1.5.6 onward, so it's released as of hirsute.

[Łukasz Zemczak (sil2100)]

Ok, so I'm really not happy with the 'What could go wrong' section, as it basically has no info right now. But I'll let it pass this one time.

[Łukasz Zemczak (sil2100)]

Hello altadeos, or anyone else affected,

Accepted fwupd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.4.7-0~20.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello altadeos, or anyone else affected,

Accepted fwupd-signed into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd-signed/1.30.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[altadeos (altadeos)]

Hello Łukasz Zemczak.

I'm using 20.04.2 Focal on my computer.
Need to install Groovy to test the proposed package?
I checked the documentation and was not able to install the version.

Best regards.

[altadeos (altadeos)]

I have upgraded my computer from focal to groovy.
The version of fwupd was 1.4.5 and the touchscreen was not working. I installed the version 1.4.7 available in groovy-proposed and confirm that it solved my problem.
Best regards.

[altadeos (altadeos)]

Installed version is :
fwupd/groovy-proposed,now 1.4.7-0~20.10.1 amd64 [installé]
  Démon de mise à jour du micrologiciel

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd - 1.4.7-0~20.10.1

---------------
fwupd (1.4.7-0~20.10.1) groovy; urgency=medium

  * new upstream version (1.4.7)
  * Bug fixes:
    - Check returned volumes before accessing them
    - Correct a Thunderbolt assertion if kernel failed FW read
    - Do not dedupe NVMe devices
    - Do not match all HIDRAW\VEN_06CB devices
    - Don't allow device updates while needing activation
    - Fix adding multiple flags to devices
    - Fix critical warning regression with 'fwupdate -a'
    - Fix probe warning for the Logitech Unifying device
    - Fix the quirk key name for the Lenovo HDMI with power
    - Make TPM more optional
    - Make udisks2 errors more apparent
    - Only set the version format for ESRT entries
    - Remove the Hughski public key
    - Restore recognizing gpg and pkcs7 types still
    - Wait a few ms for the Logitech hardware to settle after detach
  * New features
    - Add support for SBAT. (LP: #1921539)
    - Adds support for Synaptics fingerprinter reader (LP:# 1900935)
  * Fixes TPM PCR0 reading failures if all characters are 0.
    (LP: #1909734)
  * Fixes Synaptics RMI probe causing touchscreen failures
    (LP: #1886912)
  * Backport a patch from upstream 1_4_X branch to fix SBAT character.
  * Backport a patch from upstream 1_4_X branch to fix vendor-id requirement
    error on Dell WD19 (LP: #1921544)

 -- Mario Limonciello <email address hidden> Fri, 26 Mar 2021 13:45:02 -0500

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd-signed - 1.30.1

---------------
fwupd-signed (1.30.1) groovy; urgency=medium

  * Build depend on fwupd 1.4.7-0~20.10.1
    - LP: #1921544
    - LP: #1921539
    - LP: #1909734
    - LP: #1886912
    - LP: #1900935

 -- Mario Limonciello <email address hidden> Fri, 26 Mar 2021 14:04:01 -0500

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for fwupd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Mario Limonciello (superm1)]

This should have gotten closed when fwupd 1.7.5 got upgraded in Focal.