# Second touch display not working

**URL:** <https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214>\
**Category:** Budgie Desktop\
**Created:** [March 18, 2020, 9:20am UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214 "2020-03-18T09:20:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![tf01](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@tf01](https://discourse.ubuntubudgie.org/u/tf01)\
**Post date:** [March 18, 2020, 9:20am UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214/1 "2020-03-18T09:20:10Z")

</div>

Hi everyone! I’m having a bit of an interesting issue:

I’ve installed the 18.04 LTS version of Budgie on an Asus Zenbook Duo, and it has been working well for the past couple of weeks. However, as of today, the second displays touch and pen capabilities have completely stopped working. Xinput output below:

```
⎡ Virtual core pointer id=2	[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4	[slave pointer (2)]
⎜ ↳ ELAN1207:00 04F3:310E Touchpad id=13	[slave pointer (2)]
⎜ ↳ Logitech M187 id=10	[slave pointer (2)]
⎣ Virtual core keyboard id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5	[slave keyboard (3)]
    ↳ Power Button id=6	[slave keyboard (3)]
    ↳ Video Bus id=7	[slave keyboard (3)]
    ↳ Video Bus id=8	[slave keyboard (3)]
    ↳ Power Button id=9	[slave keyboard (3)]
    ↳ Asus WMI hotkeys id=14	[slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15	[slave keyboard (3)]
    ↳ Logitech M187 id=16	[slave keyboard (3)]
    ↳ USB2.0 HD IR UVC WebCam: USB2.0 id=12	[slave keyboard (3)]
    ↳ USB2.0 HD IR UVC WebCam: USB2.0 id=11	[slave keyboard (3)]
```

Previously, the touchpad (and the pen, after it was used) would appear under the Virtual core pointer list.

I’ve already reinstalled Budgie (completely reformatted the partition, and re-partitioned the drive), and found that while the pen would work in the ‘Try Budgie’ boot option, it stopped working after a full install.

Any advice would be appreciated! Also, if this is the wrong place to ask, let me know.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [March 18, 2020, 10:40am UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214/2 "2020-03-18T10:40:36Z")

</div>

Interesting issue.

Just wondering if the latest kernel has broken things.

You can change to an earlier kernel via Grub - advanced options (press escape, space or shift immediately when booting if you dont normally see the Grub screen)

---

<div class="post-metadata">

**Author:** ![tf01](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@tf01](https://discourse.ubuntubudgie.org/u/tf01)\
**Post date:** [March 18, 2020, 9:06pm UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214/3 "2020-03-18T21:06:07Z")

</div>

That looks like it fixed it! In Xinput, the touch screen is showing up again.

Thanks! I’ll change the default boot kernel for now

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [March 18, 2020, 9:07pm UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214/4 "2020-03-18T21:07:32Z")

</div>

Please remember to report the broken kernel to launchpad otherwise the kernel devs will not be aware … thus cannot fix things

```
ubuntu-bug linux
```

---

<div class="post-metadata">

**Author:** ![tf01](https://avatars.discourse-cdn.com/v4/letter/t/cdc98d/32.png) [@tf01](https://discourse.ubuntubudgie.org/u/tf01)\
**Post date:** [March 18, 2020, 9:12pm UTC](https://discourse.ubuntubudgie.org/t/second-touch-display-not-working/3214/5 "2020-03-18T21:12:38Z")

</div>

Got it, will do. Thanks for your help