Fatal IO error 11 on totem startup when using the Nvidia binary driver and VAAPI enabled

Bug #1780475 reported by Julien Olivier
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Whenever I try to launch totem, I get the following error:
Gdk-Message: 20:51:41.044: totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

Then, it just crashes.

This bug only occurs when using the Nvidia binary driver. However, even using the Nvidia binary driver, it doesn't occur on VLC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 6 20:52:08 2018
InstallationDate: Installed on 2018-05-14 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Julien Olivier (julo) wrote :
tags: added: nvidia
summary: - Fatal IO error 11 on startup
+ Fatal IO error 11 on totem startup when using the Nvidia binary driver
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: Fatal IO error 11 on totem startup when using the Nvidia binary driver

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

Changed in totem (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in totem (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Julien Olivier (julo) wrote :

I tried steps 1, 2 and 3, but it doesn't change a thing: the crash occurs, the message "totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1." is spawned in the terminal, but no .crash file is generated.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK. Can you please attach a log file showing the IO error with some more context?

Revision history for this message
Julien Olivier (julo) wrote :

Sorry Daniel, I don't understand what you need. The bug occurs immediately after I try to launch totem:

juloliv@juloliv:~$ totem
Gdk-Message: 10:52:39.290: totem: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

There is no particular "context": it crashes all the time, as soon as it's launched, and there is no log to attach that I know of.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry, I spend so much time debugging Xorg server crashes that for a moment I forgot this was about totem...

Please try running the following commands before running totem:

  ulimit -c unlimited
  export GDK_SYNCHRONIZE=1
  totem

Hopefully the crash still occurs.

Now look in either:
  * the current directory; or
  * your home directory; or
  * /var/crash
for a new core file or crash file. When found, run:

  ubuntu-bug THEFILE

and tell us the new bug ID created.

Revision history for this message
Julien Olivier (julo) wrote :

I've done that and the bug still occurs, but it doesn't generate any core or crash file.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I've tracked down the offending source code:

  https://gitlab.gnome.org/GNOME/gtk/blob/master/gdk/x11/gdkmain-x11.c#L242

and unfortunately it will just exit without leaving a crash or dump file :(

Just an idea: Please try this to see if it stops the problem from happening:

  sudo apt remove mesa-va-drivers gstreamer1.0-vaapi

If that doesn't fix it then the next step I think is to ask for help from the Totem developers. So please open a new "issue" here:

  https://gitlab.gnome.org/GNOME/totem/issues

Revision history for this message
Julien Olivier (julo) wrote :

Removing mesa-va-drivers and gstreamer-1.0-vaapi fixed the bug. Thanks a lot for your help!

summary: Fatal IO error 11 on totem startup when using the Nvidia binary driver
+ and VAAPI enabled
Changed in totem (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
Meluco (daniel-banobre-dopico) wrote :

Hi.
I'm affected too.
I solved by removing packages indicated in #9 by @vanvugt.
Thanks a lot!

Revision history for this message
Massimo Bacilieri (massimo-bacilieri) wrote :

The solution at #9 solved the same issue in "Parole" (the eq. of Totem in Xfce4)!!!
Thankyou!!!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.