After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 760078 - Crashes everything and logs out when playing full screen
Crashes everything and logs out when playing full screen
Status: RESOLVED NOTGNOME
Product: totem
Classification: Core
Component: Movie player
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-01-02 18:55 UTC by Børge / forteller
Modified: 2016-01-04 12:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Børge / forteller 2016-01-02 18:55:08 UTC
I've tried playing both mkv and avi files in Totem in a almost totally newly installed Ubuntu Gnome 15.10 64 bit.

Every time I play the files in full screen mode the screen turns black and I'm logged out of my session. When I log back in I see that all programs are closed.

This happens at different times after going to full screen mode. Some times after a second, other times after a few minutes.

I don't know how to find the log files from the crash, but please let me know how to do that if it can help.

Thanks!
Comment 1 Bastien Nocera 2016-01-02 23:51:32 UTC
This is the X server crashing, not Totem. It's just triggering a bug in your display driver. Report this to Ubuntu instead.
Comment 2 Børge / forteller 2016-01-04 12:04:14 UTC
Bastien Nocera: Are you totally sure? Because I can play videos in Totem in non-full screen and in VLC in full screen without any problems. It's just Totem in full screen that crashes.

If you are sure, would you please point me in the right direction as to where (in Launchpad I presume) I should file this IMO quite critical bug?

Thanks!
Comment 3 Bastien Nocera 2016-01-04 12:11:45 UTC
I'm certain. If X crashes, then it's a bug in X whether it's Totem or something else triggering it.

I don't know where to file your Ubuntu bug, but I'm sure there's plenty of folks that can point you in the right direction.