Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upGUID crashes Xorg when playing video in fullscreen mode #695
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by marmarek on 17 Dec 2012 13:25 UTC
First of all I don't believe in "nothing in the logs". Check /var/log/Xorg.0.log and/or ~/.xsession-errors.
You had the same problem some time ago, when fullscreen was enabled from KDE window menu (before implementing it in guid), it looks like video driver crash, not connected with guid at all.
|
Comment by marmarek on 17 Dec 2012 13:25 UTC You had the same problem some time ago, when fullscreen was enabled from KDE window menu (before implementing it in guid), it looks like video driver crash, not connected with guid at all. |
marmarek
added this to the Release 2 Beta 2 milestone
Mar 8, 2015
marmarek
added
bug
C: gui-virtualization
P: critical
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 19 Dec 2012 12:06 UTC
Ah, you've been quite right :)
-
Indeed this behaviour (white screen upon entering full screen, then Xorg crash upon an attempt to exit it e.g. via Alt-F4) can also be reproduced with just any GUID window, not only with flash movie player.
-
I was also able to extract some info from Xorg log (which I missed previously because it was in the .old log, obviously, because of the Xorg restart). I also filtered out some info from xsessions-errors, but I think it provides little info beyond what is already in Xorg log.
The piece from Xorg.log:
[
[108217.385](108217.385]) Backtrace:
[0: /usr/bin/X (xorg_backtrace+0x36) [0x465be6](108217.386])
[1: /usr/bin/X (0x400000+0x6aef9) [0x46aef9](108217.386])
[2: /lib64/libpthread.so.0 (0x7f7898cbb000+0xf440) [0x7f7898cca440](108217.386])
[3: /usr/lib64/dri/i965_dri.so (0x7f78946ca000+0x4755e) [0x7f789471155e](108217.386])
[4: /usr/lib64/dri/i965_dri.so (0x7f78946ca000+0x86706) [0x7f7894750706](108217.386])
[5: /usr/lib64/dri/i965_dri.so (0x7f78946ca000+0x713f8) [0x7f789473b3f8](108217.386])
[6: /usr/lib64/dri/i965_dri.so (0x7f78946ca000+0x60062) [0x7f789472a062](108217.386])
[7: /usr/lib64/dri/i965_dri.so (0x7f78946ca000+0x148efb) [0x7f7894812efb](108217.386])
[8: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f789642e000+0x3d8d4) [0x7f789646b8d4](108217.386])
[9: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f789642e000+0x37624) [0x7f7896465624](108217.386])
[10: /usr/lib64/xorg/modules/extensions/libglx.so (0x7f789642e000+0x3c304) [0x7f789646a304](108217.386])
[11: /usr/bin/X (0x400000+0x32909) [0x432909](108217.386])
[12: /usr/bin/X (0x400000+0x74c6a) [0x474c6a](108217.386])
[13: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f78979f2c5d](108217.386])
[14: /usr/bin/X (0x400000+0x21509) [0x421509](108217.386])
[
[108217.386](108217.386]) Segmentation fault at address 0xc
[
Fatal server error:
[108217.386](108217.386]) Caught signal 11 (Segmentation fault). Server aborting
[
[108217.386](108217.386])
Please consult the Fedora Project support
at http://wiki.x.org
for help.
[Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[108217.386](108217.386])
... and from the xsession-errors:
kdeinit4: preparing to launch /usr/bin/qvm-run
/* Now entered fullscreen using KDE menu, got white screen, then exited it via Alt-F4 */
kdeinit4: Fatal IO error: client killed
ksmserver: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kwin: Fatal IO error: client killed
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
kded4: Fatal IO error: client killed
Unexpected response from KInit (response = 0).
startkde: Could not start ksmserver. Check your installation.
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
- It's interesting to note that this behaviour applies only to GUID windows, and not to any other window (e.g. Dom0's konsole window enters and exits fullscreen just fine). This suggests a problem with how our GUI handles fullscreen.
|
Comment by joanna on 19 Dec 2012 12:06 UTC
The piece from Xorg.log: ... and from the xsession-errors:
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by marmarek on 8 Jan 2013 03:02 UTC
Does it still happens? Can you install debuginfo package and check how backtrace looks then?
sudo qubes-dom0-update --enablerepo=fedora-debuginfo xorg-x11-server-debuginfo xorg-x11-drv-intel-debuginfo
|
Comment by marmarek on 8 Jan 2013 03:02 UTC |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 20 Feb 2013 19:08 UTC |
marmarek
added
P: major
and removed
P: critical
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 20 Feb 2013 19:09 UTC
Upgrading to KDE 4.9 solved the problem :)
|
Comment by joanna on 20 Feb 2013 19:09 UTC |
marmarek commentedMar 8, 2015
Reported by joanna on 17 Dec 2012 10:41 UTC
When fullscreen mode is allowed for the AppVM, some video playback (youtube, vimeo) causes the following effect when one switches to the full screen mode (using the player's fullscreen mode button):
The video that constantly causes this effect is this one:
http://www.youtube.com/watch?v=N9v4kHFrFHs&feature=endscreen&NR=1
This crash doesn't occur when VM is not allowed to own the fullscreen (via /etc/guid.conf).
It seems to me like this is more related to some race when entering/exiting full screen mode (by guid) rather then related to the actual playback behaviour. Perhaps the very video referenced above puts some high load on vchan or Xorg and just makes this race more likely to happen.
Another interesting thin, is that one this crash ocurs, and one logs in to X again and uses the same AppVM to play other videos, now it seems that almost any video causes this effect. After I reboot the faulty AppVM, now only this particular video from above seems to be needed to cause the crash.
Migrated-From: https://wiki.qubes-os.org/ticket/695