Public bug reported:
15.10/16.04 amd64
With the Linux kernel's "debug" parameter set systemd spams the logs to
such a degree that boot fails with the plymouth progress indicator
constantly cycling, only tty1 available, and no clear indication from
the last messages displayed on console as to
GRUB_CRYPTODISK_ENABLE=y
will cause UEFI Secure Boot to fail until the Canonical signed GRUB
images include the necessary modules for crypto algorithms, cryptodisk
and luks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: GNOME Bug Tracker #766615
https://bugzilla.gnome.org/show_bug.cgi?id=766615
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=766615
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
There's an up-to-date github repo containing a DKMS package which has
been confirmed to work with 16.04.
sudo apt install git dkms
cd /usr/src
git clone https://github.com/f1u77y/rtbth.git rtbth-3.9.4.1
sudo dkms install rtbth/3.9.4.1
modinfo rtbth
sudo modprobe rtbth
hcitool dev
at this
** Description changed:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
- server failed due to being unable to configure linux-
+ server ISO installer failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote
** Description changed:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
server failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote session later we seem to have
narrowed it down to the installer.
- The
After ensuring the "normal" option (not "live") was selecting in the
"Install the System" step I checked which processes were running when it
paused to ask which kernel should be installed.
This confirms the live-installer.postinst script is running:
$ grep -Ev '\]$' ~/installer-ps.log
PID
After noticing /var/lib/dpkg/info/live-installer.postinst and seeing it
has the crucial step commented out I think the source of the issue is
now identified.
live-installer debian/live-installer.postinst:
waypoint 1 check_target
waypoint 1 get_mirror_info
waypoint 100install_live_system
** Also affects: live-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device
In expert mode the kernel command-line carries "priority=low" which is a
debconf configuration parameter. It suggests that it affects the order
of functions called such that "setup_dev" isn't being called before
"install_kernel", which would make sense because in tests after a manual
I mis-read the code in the previous comment; the condition is fine. To
figure it out I added some lines that do each test independently so as
to identify which of the three fails. That reveals the problem is the
block-device test:
Examining /etc/kernel/postinst.d.
run-parts: executing
I added "set -x" to the start of /usr/share/initramfs-tools/hook-
functions::dep_add_modules_mount() and after it failed I grabbed the
output from /var/log/apt/term.log:
The link /initrd.img is a dangling linkto /boot/initrd.img-4.4.0-21-generic
vmlinuz(/boot/vmlinuz-4.4.0-21-generic
) points to
This is triggered by the debconf setting in base-installer's
library.sh:install_kernel_linux():
Where it writes out the alternate module policy for initramfs-tools:
root@tmpstorage:/# cat /etc/initramfs-tools/conf.d/driver-policy
+ cat /etc/initramfs-tools/conf.d/driver-policy
# Driver
I've now successfully reproduced the issue in the virtual machine.
Firstly, at the installer boot menu, choose Expert Mode.
This allows selection of each installer step from a menu and causes
debconf to ask many more questions.
At "Install the System" choose a "normal" installation and then for
Using a virtual machine I'm able to reproduce the differing UUIDs but
not able to reproduce the failure of the initrd generation.
The code that fires the error is /usr/share/initramfs-tools/hook-
functions::dep_add_modules_mount()
--
You received this bug notification because you are a member
** Attachment added: "apt term.log"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664936/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
** Attachment added: "partman log"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664935/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582899
** Attachment added: "syslog from installer"
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+attachment/4664934/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
server failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote session later we seem to have
narrowed it down to the installer.
The cause of the error
Public bug reported:
This seems to be identical to Bug #1413193 which affected 15.04 and was
marked Fix Released.
On a 16.04 host with a 16.04 container:
$ lxc-create -t download -n vpn01 -- -d ubuntu -r xenial -a amd64
$ lxc-start -n vpn02 -d
the container syslog shows repeated instances of
Which display manager are these systems using?
I noticed this affects sddm (which is installed with KDE) but not with
lightdm.
I've attached a debug log whilst using sddm that indicates the cause may
be a NULL DBus path:
[init_session_id] gs-listener-dbus.c:2011 (12:28:15):Got session-id:
"GRUB loading" message comes from the bootstrap MBR code (the ~440 bytes
in sector 0) of the boot device and is activated whilst shift is
detected.
The boot-strap code then loads GRUB's core image which is what we might
call the real GRUB code, where the $timeout value has an effect.
The only
@Sebastian: No, this isn't the same as bug #1492443 (which as I read it
is about failing to display the authentication prompt).
This particular bug has had me confused at times between symptoms of
that issue, another issue with a BT regression in the kernel that
affects some BT host adapters, and
There was a mistake in the change for my 0.62 whereby it out the PNGs in
a sub-dir of lubuntu-logo/lubuntu-logo/.
Fix is in the revised 0.63~tj:
lubuntu-artwork (0.63~tj) xenial; urgency=medium
* plymouth-theme-lubuntu-logo: also install PNG files (LP: 1574317)
-- TJ <ubu...@iam.tj>
ce this.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401318
Title:
GRUB menu doesn't appear after showing "GRUB loading.&qu
If this occurs on a BIOS system (or UEFI system booting in CSM/Legacy
mode) please update this report with exact make/model/firmware version
using:
sudo dmidecode -t bios -t system
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
UEFI issue is bug 425979
** Summary changed:
- grub does not appear when holding down shift key
+ [BIOS only (not UEFI)] grub does not appear when holding down shift key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 425979 ***
https://bugs.launchpad.net/bugs/425979
** This bug has been marked a duplicate of bug 425979
[UEFI boot only] Holding shift fails to display grub2 menu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850908
Title:
grub refuses to display at all, but still runs
To manage notifications
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/983546
Title:
Please disable hidden timeout behaviour when using serial cons
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942361
Title:
Keyboard is not detected on grub menu when plugged in to USB3 port
To
Setting this to Fix Released since 30_osprober was modified since 2010
and this no longer affects any Ubuntu release.
An issue that may be confused with this is bug 425979 "[UEFI boot only]
Holding shift fails to display grub2 menu"
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/519131
Title:
Latest two versions of grub-common do not honor shift key.
To manage
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832156
Title:
The grub screen is not visible on boot up
To manage notifications about
** Description changed:
Binary package hint: grub2
- Grub2 has switched away from a minimum 1 second delay to hit enter, in
- preference to simply holding down shift during the boot sequence.
- However, this behaviour doesn't work on all machines.
+ Ubuntu added a patch on top of mainline
(Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
There's a test package available from my PPA:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes
lubuntu-artwork (0.62) xenial; urgency=medium
* plymouth-theme-lubuntu-logo: also install PNG files (LP: 1574317)
-- TJ <ubu...@iam.tj> Mon, 09 May 2016 22:28:32 +0100
--
You re
=> In Progress
** Changed in: lubuntu-artwork (Ubuntu)
Importance: Undecided => High
** Changed in: lubuntu-artwork (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: lubuntu-artwork (Ubuntu)
Milestone: None => xenial-updates
--
You received this bug notifica
Public bug reported:
16.04 amd64.
$HOME/.xsession-errors contains cryptic messages that do not indicate
where they come from. They turn out to be harmless but it would be good
if they at least were prefixed with the source.
openConnection: connect: No such file or directory
cannot connect to
** Description changed:
16.04 amd64.
The applet icon in the status area shows the opposing vertical arrows
(Wired) symbol rather than the classic WiFi radiating symbol after
adding a Wifi Access Point Hotspot, enabling it, having it fail to start
(see bug #1579512 "Hotspot Access
Public bug reported:
16.04 amd64.
The applet icon in the status area shows the opposing vertical arrows
(Wired) symbol rather than the classic WiFi radiating symbol after
adding a Wifi Access Point Hotspot, enabling it, having it fail to start
(see bug #1579512 "Hotspot Access Point mode fails
rol
[1462706989.5562] device (wlp2s0): driver supports Access Point (AP) mode
...
[1462708489.5782] Config: added 'ssid' value 'TJ'
[1462708489.5782] Config: added 'mode' value '2'
[1462708489.5782] Config: added 'frequency' value '5180'
[1462708489.5783] Config: added 'freq_list' value '5035 5040
I notice that the 16.10 console-setup has expanded the /etc/init.d
/console-setup script to call 'setupcon'. Maybe we just need a backport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511975
Should this bug be renamed to "console-setup doesn't configure Virtual
Console font at start-up" ?
This seems to be what it is about and if so it still affects 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
16.04 amd64.
plymouth-start.service refers to a non-existent keyboard-setup.service:
$ grep keyboard -r /lib/systemd/system/*
/lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service
systemd-udevd.service keyboard-setup.service
tj@T300CHI:~$ apt-file
Clean install of 16.04 amd64.
Testing with an updated kernel won't help since I've so far been unable
to determine a scenario which can reliably reproduce the issue. If/when
that is possible I'll test.
I do however routinely operate with my own mainline kernel builds so
reproducing may be
I've been unable to reproduce this since. It's possible installing the
hibernation support made some subtle change, but after a week it seem to
be stable so marking as invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
Just realised this bug is specific to the Input/Output error so I've
filed mine as bug 1578863 "unable to make backup link of
before installing new version: Operation not permitted". Sorry for the
noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I accidentally reported this against bug 559127 via a duplicate but then
realised that bug is specific to "Input/Output Error" so I'm reposting
here.
I've just encountered this with 16.04 whilst developing a bash script
that cross-builds (on amd64) a complete custom armhf
Additional debug info using dpkg -D ...
...
D000100: setupvnamevbs main='/boot' tmp='/boot.dpkg-tmp' new='/boot.dpkg-new'
D000100: tarobject already exists
D000100: tarobject directory exists
D10: tarobject ti->name='./boot/config-4.5.0-v7+' mode=100644 owner=0:0
type=48(-)
I've just encountered this with 16.04 whilst developing a bash script
that cross-builds (on amd64) a complete custom armhf RasPi 2/3
installation image.
It triggered when linux-image packages were being unpacked by 'dpkg' to
the chroot target /boot/ directory.
The amd64 system has
().
The actual config file(s) used are reported.
$ /bin/setupcon -v tj
Unable to find keyboard.tj.
setupcon: using configuration from /etc/default/console-setup.tj
Configuring /dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6
The charmap is UTF-8
BackSpace is ^?
We are not on the console
$ sh -x /bin/setupcon tj
+ do_font=yes
+ do_kbd=yes
+ do_check=yes
+ do_verbose=
+ do_save=
+ savekbdfile=
+ setupdir=
+ SETUP=
+ TMPFILE=
+ [ tj ]
+ [ -z ]
+ VARIANT=tj
+ shift
+ [ ]
+ installdir=/bin
+ installdir=
+ [ -n -a -d /bin ]
+ installdir=/usr
+ [ tj ]
+ VARIANT=.tj
+ USER_CONFIG
Public bug reported:
On 16.04 amd64:
$ ls /etc/default/console-setup*
/etc/default/console-setup /etc/default/console-setup.tj
$ sudo setupcon -v tj
[sudo] password for tj:
setupcon: None of /usr/etc/default/keyboard.tj nor /home/tj/.console-setup.tj
exists.
** Affects: console-setup
Public bug reported:
16.04 on an Asus T300CHI (Intel GPU).
$ uname -a
Linux T300CHI 4.4.0-21-lowlatency #37-Ubuntu SMP PREEMPT Mon Apr 18 20:20:26
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I found today that switching from X to the VT consoles resulted in a
blank screen. Switching between VTs
** Bug watch added: Linux Kernel Bug Tracker #117601
http://bugzilla.kernel.org/show_bug.cgi?id=117601
** Also affects: xinput-calibrator via
http://bugzilla.kernel.org/show_bug.cgi?id=117601
Importance: Unknown
Status: Unknown
** No longer affects: xinput-calibrator
** Also
** Summary changed:
- Asus T300 CHI bluetooth Touchpad is recognized incorrectly
+ [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I opened up the keyboard dock today to identify the touchpad chip. It is
an ELAN 3320KD-3100 in a 64 pin QFN package. It links over Bluetooth
using the Broadcom BCM20730 A1KFBG.
The device presents over Bluetooth with an ASUS ID: 0B05:8502.
ELAN call the touchpad the "Smart Pad":
Public bug reported:
Fresh install of 16.04 amd64.
Installed the package and noticed whilst update-initramfs is running
that cryptsetup reports two swap devices, one - a UUID - of which
doesn't exist on the system. Eventually tracked it down to a UUID in
/etc/uswsups.conf but have not been able
** Bug watch added: Linux Kernel Bug Tracker #117451
http://bugzilla.kernel.org/show_bug.cgi?id=117451
** Also affects: xinput-calibrator via
http://bugzilla.kernel.org/show_bug.cgi?id=117451
Importance: Unknown
Status: Unknown
** Project changed: xinput-calibrator => linux
**
Update for the following overnight suspend: worked correctly with a
suspend of around 8 hours.
No significant changes in hardware configuration or kernel options
(added "initcall_debug").
I did install 'uswsusp' to support hibernation in addition to S3 suspend
and modified
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG0 S4*disabled
PEGP S4*disabled
PEG1 S4*disabled
PEGP S4*disabled
PEG2 S4*disabled
PEGP S4*disabled
RP01 S4*disabled pci::00:1c.0
RP02 S4*disabled
RP03
>From syslog some associated suspicious systemd-suspend messages with
>correlating timestamps:
$ grep 'systemd-suspend.service: Executing' /var/log/syslog.1
Apr 28 21:34:56 T300CHI systemd[10799]: systemd-suspend.service: Executing:
/lib/systemd/systemd-sleep suspend
Apr 28 21:36:49 T300CHI
** Attachment added: "syslog showing the system seems to remain awake"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651194/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
16.04 amd64 on an Asus T300 CHI.
I commanded the PC to S3 suspend around 21:30 last evening. Returned to
the PC around 08:00 this morning and discovered the PC wouldn't resume
from suspend and had fully discharged its battery.
After a cold boot restart I
** Attachment removed: "kern.log starting from a cold boot just before
commanded suspend"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651152/+files/kern.log
** Attachment added: "kern.log starting from a cold boot just before commanded
suspend"
** Attachment added: "lsusb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651154/+files/lsusb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576571
Title:
S3
** Attachment added: "lspci -knn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576571/+attachment/4651153/+files/lspci-nnk.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576571
Public bug reported:
16.04 amd64 on an Asus T300 CHI.
I commanded the PC to S3 suspend around 21:30 last evening. Returned to
the PC around 08:00 this morning and discovered the PC wouldn't resume
from suspend and had fully discharged its battery.
After a cold boot restart I investigated the
:05 a recent update fucked up something, on all servers
running 15.10
...
19:05 magento_rocks: package install history is in /var/log/apt/
19:06 magento_rocks: specific package changelogs under
/usr/share/doc//changelog*
19:07 TJ- thanks
...
19:08 php5-common:amd64 (5.6.11+dfsg-1ubuntu3.1,
5.6
Looks like revision 1839 could be responsible. Will try a bisect later
today.
http://bazaar.launchpad.net/~unity-greeter-team/unity-
greeter/16.04/revision/1839
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the matching timestamps extract from lightdm.log, centred around
0.62s.
** Attachment added: "lightdm.log matching timestamps of x-0-greeter.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1571640/+attachment/4647723/+files/lightdm.log
--
You received this bug
Robert; the greeter run by lightdm. I was going to do some debugging on
it myself today. First time I've installed a Unity desktop in several
years so I thought it was intended to ensure the greeter elements were
readable on high DPI displays.
Here it's on an Asus T300 Chi with a 2560x1440
Yes, I saw this... assumed it was supposed to happen.
Were you able to confirm the actual resolution as reported by xrandr had
changed, rather than just the scaling of the display elements ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Having looked more closely this bug was a result of user error; I did in
fact repartition the installation device and had a separate partition
for /boot/ which was also LUKS/dm_crypt. I had forgotten I needed to
edit the /target/etc/default/grub whilst ubiquity was installing GRUB,
and had to do
This was fixed in:
grub2 (2.00+20131208-1) experimental; urgency=low
* New upstream snapshot.
- Skip issuing cursor on/off sequences on Macs (closes: #683068).
- Move grub-mknetdir to /usr/bin (closes: #688799).
- Apply program name transformations at build-time rather than at
This isn't a duplicate of bug #1232237. In this case the config option
variable wasn't added to /etc/default/grub.
I've done so many permutations of these encrypted installations now I
cannot recall whether I did any manual partitioning in this particular
session. The partman log appears to
Public bug reported:
After upgrade to 16.04 ssh client will not connect to any host,
reporting
/home/tj/.ssh/config line 109: Bad protocol spec '1'.
The entry is:
Host ups-01
Hostname 10.254.0.1
User hostmaster
IdentityFile ~/.ssh/id_hostmaster
IdentitiesOnly yes
Protocol 1
If this were
ith
the A1016. It reflects using
tj@T300CHI:~$ bluetoothctl
[NEW] Controller 34:02:86:FC:AD:59 T300CHI [default]
[NEW] Device 00:0A:95:44:37:11 Apple Wireless Keyboard
[NEW] Device 1C:B7:2C:04:C7:FE ASUS T300CHI DOCKING
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI: Synaptics
- Touch Digitizer - missing at boot".
+ Affecting this digitizer is also bug
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
- touchscreen digitiser missing at boot".
+ Affecting this digitizer is also bug
** Changed in: xinput (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480673
Title:
Asus T300 CHI bluetooth Touchpad is recognized incorrectly
To manage
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
+ Asus T300 CHI: Synaptics Touch Digitizer - missing at boot
** Changed in: xinput (Ubuntu)
Status: New => Triaged
** Changed in: xinput (Ubuntu)
Importance: Undecided => Medium
--
You received this
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
+
+ Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
+ touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
Public bug reported:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
In this case the
** Description changed:
+ Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics
+ Touch Digitizer V04 - no multitouch".
+
The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
Both (touchscreen, touchpad) only work like a mouse (moving pointer, left
I've found a workaround that works reliably. Add to the kernel command-
line:
acpi_osi=! acpi_osi="Windows 2013"
Edit "/etc/default/grub" to include those options in GRUB_CMDLINE_LINUX
(there can be other options there too):
GRUB_CMDLINE_LINUX="debug acpi_osi=! acpi_osi=\"Windows 2013\""
It seems that the touchscreen digitiser is disabled if AC power is
connected during boot-up. Leaving the AC plug disconnected and the touch
is reliably available.
This definitely looks like an ACPI DSDT issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Working on 16.04 and trying to solve some unrelated issues due to a
complex initrd set-up I discovered that the included "modinfo" tool
doesn't work, whether given just a module name or an absolute path to
the .ko file.
In this case it always reports, e.g:
(initramfs) pwd
** Attachment added: "ACPI DSDT decompiled"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574028/+attachment/4644326/+files/dsdt.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574028
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen missing at boot
+ 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
** Attachment added: "lsusb after cold boot"
** Attachment added: "lsusb after S3 resume showing device"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574028/+attachment/4644316/+files/lsusb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Using 16.04 amd64 on an Asus T300 CHI 2-in-1 transformer-book (tablet +
docking Bluetooth keyboard/trackpad).
At boot-time the USB-connected Synaptics touchscreen digitiser is not
recognised but after an S3 sleep/resume it is. Smells like an ACPI issue
but so far testing
1 root root 4096 Apr 23 12:59 unbind
tj@T300CHI:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 06cb:11ef Synaptics, Inc.
Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Devi
My loss of the touchscreen seems to be due to my doing a lot of
experimenting with evtest and udev's hwdb. After an S3 resume this
morning the touchscreen Synaptic devices re-appeared. Thinking about it,
it may also be due to some ACPI DSDT experimentation I was doing to try
to get the Fn+F5-F7
Confirmed here too... although with 16.04 / Unity there was touchscreen
input during live session but after booting the installed system I just
realised there is no touchscreen input device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
No idea why ubiquity crashed; maybe post mortem will reveal something.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.60 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux
I'm still having to use the shell and bluetoothctl to re-connect the
device when it has disconnected.
I think there are two causes for the same symptom here:
1) bluetooth agent/GUI not functioning correctly (as with the T300Chi)
2) no PIN-code entry as first reported, with no work around, due to
I've managed to connect the Asus Transformer T300Chi; this may work for
other tablets/hybrids/modern Bluetooth devices.
I am working from the 16.04 GUI installer in 'Try' mode. Touch-screen
and stylus input was working so I first went to System Settings >
Universal Access and enabled the
Yes, confirmed still affecting 16.04, and now on a different PC - a 2105
Asus Transformer T300Chi with a dockable Bluetooth keyboard/mouse.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490347
601 - 700 of 2979 matches
Mail list logo
