Public bug reported:
the most bothersome, most notable, and most curious symptom of this bug
is the absolute degree to which the display locks up. xclock's seconds
are no longer changing, the mouse cursor won't move, and even ctl-alt-F1
does nothing.
meanwhile mplayer, playing in a hidden tmux window, is still playing
merrily along.
i logged in via sshd and copied this from htop:
0 [|||||||||||||||||||||||||||||||||||||||||100.0%] Tasks: 68; 3 running
1 [|| 1.3%] Load average: 1.00 0.91
0.53
Mem[|||||||||||||||||||||||||||||||||||||973M/1.91G] Time: 14:26:17
Swp[ 0K/1.86G]
PID START USER VIRT RES NI CPU% TIME+ S Command
1714 12:50 g 1713M 789M 0 0.0 6:37.92 S /usr/lib/firefox/firefox
2368 14:07 g 661M 57252 0 0.0 0:03.33 S /usr/bin/python3
/usr/bin/blueman-manager
794 12:49 root 269M 54988 0 99.3 10:12.88 R /usr/lib/xorg/Xorg -core
:0 -seat seat0 -auth /var/
2385 14:07 g 583M 53524 0 0.0 0:00.39 S /usr/bin/python3
/usr/bin/blueman-applet
2397 14:07 g 555M 42968 0 0.0 0:10.68 S pavucontrol
1926 12:57 g 282M 37752 0 0.7 0:02.46 S
/usr/lib/firefox/plugin-container /opt/google/talkp
1933 12:57 g 512M 36404 0 0.0 0:02.96 S
/opt/google/talkplugin/GoogleTalkPlugin
2403 14:07 g 823M 30352 0 0.0 0:03.52 S mplayer -ao pulse -af
channels=2 -framedrop -msgcol
F1Help F2Setup F3SearchF4FilterF5Tree F6SortByF7Nice -F8Nice +F9Kill F10Quit
ps also attached, taken before killing xorg.
i've filed this under xorg merely because xorg is the one stuck eating
all the CPU. i really suspect the display driver, and don't know how to
find or identify that.
i much more commonly saw these very same symptoms when i used to run
xscreensaver. i stopped running xscreensaver just to stop beating my
head against that wall. but many years and many releases later, it
looks like this display driver bug is still lurking around.
there was hardly anything running when this froze. i already mentioned
mplayer (sound only) and tmux, twm's the window manager, firefox was
running but iconized and idle tho running gmail and the googletalk
plugin, not that i suspect any of them in any way. xterm was occupying
most of the screen, showing tmux, and idle. the ones i'd more suspect
would be xclock & pavucontrol. pavucontrol was hidden but busily
showing it's audio level bar, xclock was visible and displaying the time
of day including seconds, so the most likely one to have tripped a
display driver bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 14:36:38 2016
InstallationDate: Installed on 2016-10-15 (43 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
** Attachment added: "ps taken before xorg killed"
https://bugs.launchpad.net/bugs/1645485/+attachment/4784403/+files/ps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1645485
Title:
very old display driver bug?
Status in xorg package in Ubuntu:
New
Bug description:
the most bothersome, most notable, and most curious symptom of this
bug is the absolute degree to which the display locks up. xclock's
seconds are no longer changing, the mouse cursor won't move, and even
ctl-alt-F1 does nothing.
meanwhile mplayer, playing in a hidden tmux window, is still playing
merrily along.
i logged in via sshd and copied this from htop:
0 [|||||||||||||||||||||||||||||||||||||||||100.0%] Tasks: 68; 3 running
1 [|| 1.3%] Load average: 1.00 0.91
0.53
Mem[|||||||||||||||||||||||||||||||||||||973M/1.91G] Time: 14:26:17
Swp[ 0K/1.86G]
PID START USER VIRT RES NI CPU% TIME+ S Command
1714 12:50 g 1713M 789M 0 0.0 6:37.92 S /usr/lib/firefox/firefox
2368 14:07 g 661M 57252 0 0.0 0:03.33 S /usr/bin/python3
/usr/bin/blueman-manager
794 12:49 root 269M 54988 0 99.3 10:12.88 R /usr/lib/xorg/Xorg
-core :0 -seat seat0 -auth /var/
2385 14:07 g 583M 53524 0 0.0 0:00.39 S /usr/bin/python3
/usr/bin/blueman-applet
2397 14:07 g 555M 42968 0 0.0 0:10.68 S pavucontrol
1926 12:57 g 282M 37752 0 0.7 0:02.46 S
/usr/lib/firefox/plugin-container /opt/google/talkp
1933 12:57 g 512M 36404 0 0.0 0:02.96 S
/opt/google/talkplugin/GoogleTalkPlugin
2403 14:07 g 823M 30352 0 0.0 0:03.52 S mplayer -ao pulse -af
channels=2 -framedrop -msgcol
F1Help F2Setup F3SearchF4FilterF5Tree F6SortByF7Nice -F8Nice +F9Kill
F10Quit
ps also attached, taken before killing xorg.
i've filed this under xorg merely because xorg is the one stuck eating
all the CPU. i really suspect the display driver, and don't know how
to find or identify that.
i much more commonly saw these very same symptoms when i used to run
xscreensaver. i stopped running xscreensaver just to stop beating my
head against that wall. but many years and many releases later, it
looks like this display driver bug is still lurking around.
there was hardly anything running when this froze. i already
mentioned mplayer (sound only) and tmux, twm's the window manager,
firefox was running but iconized and idle tho running gmail and the
googletalk plugin, not that i suspect any of them in any way. xterm
was occupying most of the screen, showing tmux, and idle. the ones
i'd more suspect would be xclock & pavucontrol. pavucontrol was
hidden but busily showing it's audio level bar, xclock was visible and
displaying the time of day including seconds, so the most likely one
to have tripped a display driver bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 28 14:36:38 2016
InstallationDate: Installed on 2016-10-15 (43 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645485/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
