display freezes after recent apt update/upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
After a recent upgrade (which includes linux,xorg-
below), the display periodically freezes and is completely unresponsive to
keyboard and mouse (other than pointer movement), after attempting to drag a
window across the workspace. This is a problem for both of two modes of window
dragging: <ALT>+<left mouse button>+drag and <super>+s then drag. Other than
when dragging windows, no other activity on the desktop/display appears to be a
problem. The system is otherwise quite stable.
But...
In addition (and this is also new since the upgrade and probably related), the
display and input goes dead after closing the lid on the laptop. This happens
whether displaying the desktop, or in a virtual terminal, or when logged out with
the login screen displayed. The display goes blank (per the usual), but does not
go active again when the lid is raised (bad). The system is configured to "never
suspend" and to "do nothing" when the lid is closed and to "never" turn the screen
off due to inactivity.
The noted behavior is now on exhibit with both the upgraded kernel and the "old"
kernel (4.4.0-38-generic and 4.4.0-36-generic, respectively). Prior to the
upgrade, this laptop was perfectly stable (booting 4.4.0-36), and (for what it's
worth) windows10 (ughhh) is still quite stable, suggesting that this is not a case
of hardware gone flaky.
I strongly suspect an interaction between the upgraded compiz package and the
upgraded xorg-server as the source of the problem, since the underlying system
continues to operate even though the display and input are dead (deduced by the
fact that scheduled cron jobs run to completion well after the display has gone
dead), and because the first problem only occurs when dragging a window. (It
would help if I were able to switch into a virtual terminal, but the keyboard is
totally deceased.)
There is no indication of a problem in the log files that I have been able to
discern. However, there is at least one instance of dumped core (so to speak) by
upstart in /var/crash since the upgrade.
I realize that this is not enough detail to be of much help, and not much of the
bug reporting docs seem to apply to this case, so please do let me know what more
I can do to assist in tracking down the problem.
Ubuntu release 16.04... all upgrades are current as of 2016-10-07
ideapad 100S laptop
Intel Atom CPU Z3735F @ 1.33GHz × 4
Graphics: Intel Bay Trail
uname -a
Linux khampton-
15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
lspci
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC
Transaction Register (rev 0f)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx
Series Graphics & Display (rev 0f)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron
N2000 Series USB xHCI (rev 0f)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx
Series Trusted Execution Engine (rev 0f)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power
Control Unit (rev 0f)
The upgrade included the following packages, as output by dpkg-log-summary, with
the obvious innocents stripped out:
u accountsservice 2016-10-07 11:32:34 0.6.40-
2ubuntu11.1 0.6.40-2ubuntu11.2
u accountsservice
2ubuntu11.1 0.6.40-2ubuntu11.2
u bamf 2016-10-07 11:33:27
0.5.3~bzr0+
u bind9 2016-10-07 11:28:56
1:9.10.
u compiz:all 2016-10-07 11:33:33
1:0.9.12.
u gdk-pixbuf 2016-10-07 11:33:05 2.32.2-1ubuntu1
u gtk2-engines-
0ubuntu2.1 0.98.2-0ubuntu2.2
u ifupdown:amd64 2016-10-07 11:27:23 0.8.10ubuntu1
u initramfs-tools 2016-10-07 11:28:54 0.122ubuntu8.1
u initramfs-tools:all 2016-10-07 11:28:53 0.122ubuntu8.1
u isc-dhcp 2016-10-07 11:28:57 4.3.3-
5ubuntu12.1 4.3.3-5ubuntu12.3
u klibc 2016-10-07 11:28:52 2.0.4-
8ubuntu1.16.04.1 2.0.4-8ubuntu1.
u libunity 2016-10-07 11:34:55
7.1.4+15.
u linux 2016-10-07 11:36:17 4.4.0-36.55
u linux-meta 2016-10-07 11:43:39 4.4.0.36.38
u network-manager 2016-10-07 11:35:58 1.2.0-
0ubuntu0.16.04.3 1.2.2-0ubuntu0.
u network-
0ubuntu0.16.04.3 1.2.2-0ubuntu0.
u ntp:amd64 2016-10-07 11:31:53 1:4.2.8p4+dfsg-
3ubuntu5.1 1:4.2.8p4+
u snap-confine 2016-10-07 11:32:05 1.0.38-
0ubuntu0.16.04.8 1.0.38-
u snap-confine:amd64 2016-10-07 11:31:55 1.0.38-
0ubuntu0.16.04.8 1.0.38-
u snapd:amd64 2016-10-07 11:49:11 2.12+0.16.04
u systemd 2016-10-07 11:27:08 229-4ubuntu7
u systemd:amd64 2016-10-07 11:27:39 229-4ubuntu7
u ubuntu-
u unity 2016-10-07 11:36:14
7.4.0+16.
u unity:amd64 2016-10-07 11:36:00
7.4.0+16.
u xorg-server 2016-10-07 11:27:14 2:1.18.3-
1ubuntu2.3 2:1.18.4-0ubuntu0.1
tags: | added: regression-update xenial |
affects: | ubuntu → compiz (Ubuntu) |
Changed in compiz (Ubuntu): | |
importance: | Undecided → High |
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/ FindRightPackag e. 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/1632197/ +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.]