Fullscreen Freeze.

[Vindicator]

Related?:
http://askubuntu.com/questions/692405/ubuntu-15-10-unity-freezes-after-escaping-full-screen-video
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622

I've been having cases of unusual screen behavior, particularly when Kodi 16 is being used (maybe it's just a Kodi thing).
There have been times before when coming out of fullscreen video using either Chrome or Kodi would drop me to a console screen with no input.
I think I would be able to kill the gnome session in tty1.

Now, after a bios upgrade as well as the latest display manager and kernel update, Kodi has frozen in fullscreen a couple of times and yet audio will still play from Kodi.
I created the bug report in tty1.

I've also been noticing that if I pause a Kodi video, other non-Kodi applications may not update their window content.
For example, I may be in a webpage in Chrome and I try to mousewheel scroll, yet not see the scrolling effect. Or I will click on a different tab and the window doesn't show the switch. BUT, if I continue playing the Kodi video, Chrome will update it's screen, and if I switch back to the tab I scrolled, the scroll will have already occurred.

I will say that I have at least not had a fullscreen GUI crash me out to console.

Another peculiarity is when booting Ubuntu, I used to be able to press ESC to view the kernel/system booting output, but now it just shows a black screen with a cursor.
The downside to that in 15.04 was I'd lose my mouse cursor when the GUI login screen came up.

Let me know what other output you'd like (or whatever test you'd like me to try) "when" it happens again.
---
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DistUpgraded: Fresh install
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:041e]
InstallationDate: Installed on 2015-10-28 (26 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash elevator=cfq vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Tags: wily ubuntu compiz-0.9
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H97M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Nov 23 21:36:32 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 47908
 vendor BBY
xserver.version: 2:1.17.2-1ubuntu9.1

[penalvch (penalvch)]

Vindicator, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1516531

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

apport information

[Vindicator (vindicator)]

Alright, so it happened again.
I'm sure it would have happened sooner, but I stopped myself from putting Kodi into full screen because I was scanning a drive, I pulled from another computer, for badblocks, and it happened while in the 1st stage of the 74 hour scan and I had to start over.

This time, xorg DID boot me out into a non-interactive console view. I switched over to tty1 to try the apport, but apport-collect needs a gui. The thing is, while in tty1, before I logged in, it switched me back to the gui login (tty7?).
I DID see a kodi entry along with xorg at the time of the crash in the journal.

For the times/cases when xorg only freezes in fullscreen (though mouse still moves), what parameters should I use for apport-cli, for when I switch to tty1?

[penalvch (penalvch)]

Vindicator, after the freeze, are there crash files in /var/crash?

[Vindicator (vindicator)]

Yes, there are _usr_bin_Xorg.0.{crash,upload,uploaded} files, where .crash is 10MB and the other 2 are 0 bytes.

[Vindicator (vindicator)]

Hey Christopher, I see you are still self-subscribed so I hope you see this update.
I had a few more instances occur between Kodi and Chrome (viewing youtube) while in full-screen.

First, I want to say that there are NO crash reports when the freeze occurs. Crash reports do get created such as one relating to gnome when I was transcoding rough videos (I think relating to thumbnail generation with the output file).

I also am able to confirm what I thought was a possible cause in a particular case.
Sometimes the freeze occurs while coming out of fullscreen (ESC for chrome or \ for kodi).
But what happened just now which made it very clear was a desktop notification from skype caused the freeze to occur even though I wasn't trying to come out of fullscreen.

I went to tty1 while still in the system, and like I just mentioned, there were no crash logs.
I DID run apport-cli to save 2 files to my desktop. 1) for xorg by process name and 2) for gnome-session by pid.

If you think either of these will be helpful or have something else you want me to try/capture, let my know and I'll make the file submissions.

[Vindicator (vindicator)]

I see the status changed, but did you want me to attach those 2 new apport files (xorg and gnome-session by pid)?

[Vindicator (vindicator)]

To add to the bug data, some debug output I managed to get from Kodi
(area of interest looks to be at 20:26:36. I believe this is when it froze again after I heard Skype alert me of an IM notification).
*****
20:24:54 T:140568642451200 DEBUG: CDVDPlayer::HandleMessages - player started 2
20:24:54 T:140568642451200 DEBUG: CDVDPlayer::SetCaching - caching state 4
20:24:54 T:140568598345472 DEBUG: CDVDPlayerVideo::CalcDropRequirement - hurry: 0
20:24:54 T:140568598345472 DEBUG: CDVDPlayerVideo::CalcDropRequirement - hurry: 1
20:24:54 T:140568642451200 DEBUG: CDVDPlayer::SetCaching - caching state 0
20:24:54 T:140568589952768 NOTICE: CDVDPlayerAudio::OutputPacket skipping a packets of duration 32
20:24:54 T:140568589952768 NOTICE: Previous line repeats 1 times.
20:24:54 T:140568589952768 DEBUG: CDVDPlayerAudio::HandleSyncError - average error -669.773351 below threshold of 50000.000000
20:24:57 T:140570840144000 DEBUG: ------ Window Deinit (DialogSeekBar.xml) ------
20:24:58 T:140568598345472 DEBUG: CPullupCorrection: detected pattern of length 1: 16683.33, frameduration: 16683.333333
20:26:36 T:140568598345472 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
20:26:38 T:140568589952768 WARNING: Previous line repeats 2 times.
20:26:38 T:140568589952768 DEBUG: CDVDClock::Discontinuity - CDVDPlayerAudio::HandleSyncError2 - was:1689577422.344335, should be:1689551050.248257, error:-26372.096077
20:26:40 T:140568589952768 DEBUG: CDVDClock::Discontinuity - CDVDPlayerAudio::HandleSyncError2 - was:1691571648.191257, should be:1691589893.382828, error:18245.191570
20:26:55 T:140568589952768 ERROR: CDVDAudio::AddPacketsRenderer - timeout adding data to renderer
20:26:55 T:140568589952768 DEBUG: CDVDClock::Discontinuity - CDVDPlayerAudio::HandleSyncError2 - was:1706789333.706828, should be:1706756445.354551, error:-32888.352277
20:26:56 T:140568589952768 ERROR: CDVDAudio::AddPacketsRenderer - timeout adding data to renderer
20:26:58 T:140568589952768 ERROR: Previous line repeats 1 times.
20:26:58 T:140568589952768 DEBUG: CDVDPlayerAudio::HandleSyncError - average error -3761538.502023 above threshold of 100000.000000
20:26:58 T:140568589952768 NOTICE: CDVDPlayerAudio::OutputPacket skipping a packets of duration 32
20:26:58 T:140568589952768 NOTICE: Previous line repeats 156 times.
20:26:58 T:140568589952768 NOTICE: CDVDPlayerAudio::OutputPacket duplicate 1 packets of duration 32
20:26:59 T:140568589952768 NOTICE: CDVDPlayerAudio::OutputPacket skipping a packets of duration 32
20:26:59 T:140568589952768 NOTICE: CDVDPlayerAudio::OutputPacket duplicate 1 packets of duration 32
20:26:59 T:140568589952768 DEBUG: CDVDPlayerAudio::HandleSyncError - average error 5154.219960 below threshold of 50000.000000
20:27:00 T:140568589952768 DEBUG: CDVDClock::Discontinuity - CDVDPlayerAudio::HandleSyncError2 - was:1711702185.329551, should be:1711674374.594601, error:-27810.734949
20:27:13 T:140568589952768 WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available
*****

[penalvch (penalvch)]

Vindicator, to clarify, attaching manually generated apport files wouldn't be necessary.

However, what would be helpful is if you tested for this freeze in Xenial by either in-place upgrade or via http://cdimage.ubuntu.com/daily-live/current/ .

[Vindicator (vindicator)]

You know Christopher, I am VERY reluctant to try xenial.
I had tried Wily in the very early stages (I think I may have also upgraded gnome and bluez as well) and it was very problematic.

The thing is, I had transitioned from Vista to 15.04 and the process was horrible. Bugs left and right and I had to write up a procedure to set things up right for myself as I went along.
I had NOT written anything up for a clean 15.10 install until I could be sure I wouldn't go back to 15.04.

THIS is the perfect reason for me to go back to 15.04 and causes the greatest of fears for moving to 16.04.
I hate backing up and restoring my home profile because it isn't straight forward and I have to fudge things. (restoring encrypted home. trying to restore live...)

One thing I will ask you: What is it about Xenial that makes you think it may fix my freeze issue? I had NO freeze issue in 15.04.
The reason I ask is because of a different bug I reported (mouse cursor disappears) and the guy's only request of me was to upgrade my kernel. With each upgrade (multiple requests) and no change, I finally asked what made him think the kernel upgrade would do it, especially since it was a longstanding issue based on a web search. No response was ever given. That torqued me off in a bad way.
There was some patch in 15.10 that broke what worked in 15.04 and I want to know the patch was resolved/addressed for 16.04.

Summary: I'd be very reluctant to upgrade to xenial and am more apt to go back to 15.04 since there were no freeze issues.

[Vindicator (vindicator)]

You know, I was curious about that other bug I referenced where the guy never mentioned what testing each kernel upgrade was supposed to do.
And what do I find? It was you Christopher. There was too much of a similarity for me to just let it pass, and I just had to look that bug up again to see for sure.

I'm disappointed and surprised if this is the level of "bug triage".
I looked at your wiki and a handful of bugs that you've triaged and all I have seen is you asking for a newer kernel/bios/os to be tested.
It's like dealing with 1st-tier phone support (with any company).

I wouldn't be surprised if you dump this comment, close or invalidate this bug for personal reasons, but I own and stand by my comments based on what I've seen and experienced.

Like I said, if anything I'd just as soon revert to 15.04. But with Ubuntu having been my primary experience with any linux dist, I may just see what kind of stability others have to offer.

[penalvch (penalvch)]

Vindicator, I'm not sure how attacking me, and not providing previously requested information is going to either solve your problem, or motivate others to want to help you with it.

Here in Ubuntu, we don't put down others for contributing on any level they choose to provide, whether it's documentation, triage, or development. So, if you feel compelled to put people down for their contribution, please feel free to mark your report as Invalid, and take it elsewhere as it's not welcomed here in Launchpad.

Despite this, if one would care to read comments fully before attacking the poster, why one is asked to test a newer version of the kernel, BIOS, or OS respectively is fully documented, both in those comments you glanced at, and throughout the publicly available Ubuntu documentation. You are welcome to start familiarizing yourself with this at https://wiki.ubuntu.com/ReportingBugs .

To further clarify https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/comments/28 , xorg bugs aren't considered triaged unless the latest version of Ubuntu is tested, or the root cause commit is identified. As neither has occurred, this report is pretty much a standstill.

[Vindicator (vindicator)]

I must say I'm glad you did respond as it means you take it seriously.

While you take it as a personal attack, it was merely a description of what I have seen and experienced.
Attacking is something I associate with name-calling with nothing backing it up.
A performance-review from a boss that describes problems with an employee's results is not something I would consider an attack.

I know 1st-tier phone support where the person I'm speaking with has no idea regarding the issue and is reading from a script that is not applicable to the issue, when all that is needed is to advance me to someone who would be able to provide deeper support (test a patch).
It's the kind of support that would be equal to "reboot your computer 3 times" when Excel is selecting multiple cells with a single click. It would be more appropriate to see if the mouse button has bounce, but even then it could still be a software bug.
That is the impression I get when I'm asked to test a newer kernel or OS to see if it would fix the issue.
It was never said "why" it was thought it would fix the issue (eg, reference a pull-request that addresses an issue that might be remotely applicable to the current issue).
I can see the value of 1st-tier in order to filter out "newbs" for the developers when a configuration/setting change is all that is needed, but as much as the tier can be helpful for the developers (and newbs), they can also be headaches for those with issues that need deeper triage.

"... why one is asked... documented, both in those comments..."
I must be missing those comments you are referencing that provides the "why".
My "why" questions:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/comments/29 "What is it about Xenial..."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465862/comments/11 "...wondering what this 'testing' is supposed to be doing..."
Other's bug's that ask for a test with an upgrade, but no "why" given:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/comments/4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/comments/4 "Can someone please explain what..."

With the wiki, I think you are probably referencing "Please do not complain because someone sent what one perceives to be a automated or "canned" response."
I also see this issue as "Please check to see if you(r) problem is a regression." so I'd say bisecting should be done rather than about testing upstream. But I know by saying just that goes against "Please avoid arguing with triagers and developers".

For me, testing a newer kernel is less complicated than testing a whole new OS that is only in the early testing stages when I'm dealing with a "production" (day-to-day use) computer.
It would involve:
1) backing things up and hoping that backup worked.
2) upgrading (in my case, I always start with a fresh install)
3) restore, which never goes well with an encrypted home. something I have to do from live-cd.
4) installing programs, which also means building some from scratch like kodi which also means building the addons.
Even if I got there after hours (day(s)?) of work, the testing OS may not fix the issue and may also have other unusable prob...

[penalvch (penalvch)]

Vindicator:

1) Regarding the first 50% that has nothing to do with fixing this issue, I'll PM you directly about it to avoid derailing this report further with discussion that has nothing to do with getting this issue fixed.

2) Regarding your comment:
>"For me, testing a newer kernel... may also have other unusable problems."

As you have made it clear you won't be testing Xenial, no problem here. I'll mark it New and this may go forward on that.

3) Regarding the rest of your comment, it falls into 1).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Miklos Juhasz (mjuhasz)]

Christopher, I tried the Xenial daily image and the issue is present there.

[penalvch (penalvch)]

Miklos , it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Vindicator (vindicator)]

What motherboard and CPU are you using Miklos?

I never bothered trying xenial and went straight to archlinux w/kde.

The issue seems to be driver/xorg related and I had submitted a bug report to KDE when I encountered a similar issue (kde drops back out to login screen instead of freezing the gui).
There is a workaround and if your motherboard and cpu look like the workaround will be applicable, I'll post the link to the report.

[Miklos Juhasz (mjuhasz)]

Vindicator, I can reproduce it on my desktop (SandyBridge CPU, Asus P8Z68-V PRO GEN3) and on a laptop (Haswell) as well. To me it looks like it's Mesa related. The related Chrome bug report (with my comment): https://code.google.com/p/chromium/issues/detail?id=568560

[Vindicator (vindicator)]

Yup, I am running with Haswell myself, so with the intel gpu being used, I think this bug-"fix" may very well work for you too:
https://bugs.kde.org/show_bug.cgi?id=358991#c7
Kodi (nor chrome videos in fullscreen) hasn't been an issue for me since I changed that value.
Remember to reboot after making the change.

[Wayne Scott (wsc9tt)]

For what it is worth, I have 15.10 installed on a Thinkpad X1 with an Ivy Bridge processor (i5-3427U) and Intel HD 4000 graphics and I am seeing very similar behavior. Full screen video from Chrome or games on Steam cause the freeze.

The freeze is usually when switching away from the video/game or when using the volume keys which causes the onscreen popup to occur.

This is new in 15.10. It didn't have this problem when I first upgraded to 15.10 (from 14.04) but seems like it started a couple weeks ago.

[penalvch (penalvch)]

Wayne Scott, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Michael Kasprzak (mike-sykhronics)]

FWIW I have an identical setup to Wayne Scott, but My Thinkpad is an X230 with swivel touchscreen. I upgraded to 15.10 almost immediately after it was released, and have been suffering from this issue ever since (15.04 worked way better than 14.04, so I had high hopes). It mainly crops up for me in Chrome, and ruins my day when I accidentally press YouTube's fullscreen shortcut key. The only way out has been to "killall -u myname". I had hoped to find this problem resolved, but with Ubuntu 16.04 looming, it's kinda crazy that it isn't.

It's worth noting it isn't a typical crash. Video becomes mostly unresponsive, with the exception of the mouse cursor that can still be moved (has no effect though). Audio continues to work, even YouTube and Twitch that are streaming, there is just no longer any useful display. Other reports seem to suggest disabling hardware acceleration in Chrome works around the issue, but that's not really acceptable because of the need for WebGL and such.

I ran "ubuntu-bug xorg" as suggested above.

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1561795

[Luigi R. (xluigi84)]

when it happen in fullscreen mode I get this error message in the terminal:

libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
libEGL warning: bad surface attribute 0x3081
libEGL warning: bad surface attribute 0x3081
^C^C^C^C^ClibEGL warning: bad surface attribute 0x3081
WARNING: Invalid RefPicListX[] entry!!! It is not included in DPB

I'm using kodi 17 un ubuntu 16.04 kernel 4.4.0-64-generic

[Jan Kozusznik (i-jan-1)]

In CompizConfig Settings Manager and tab Composite plugin helps to DISABLE "Unredirect Fullscreen Windows".
KODI doesn't crash with this settings in fullscreen mode.

[saurav kumar (thekumar101)]

Whenever I switch a video or image to fullscreen mode, keyboard and mouse event stop working.

[Martin (martin3000)]

My system was always freezing when I was using chrome or chromium in fullscreen (F11). After disabling "unredirect windows" with ccsm, it seems to be fixed.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.