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 734044 - Totem does not start with NVIDIA driver
Totem does not start with NVIDIA driver
Status: RESOLVED NOTGNOME
Product: totem
Classification: Core
Component: Movie player
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-07-31 14:36 UTC by Giulio A.
Modified: 2014-10-14 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Giulio A. 2014-07-31 14:36:41 UTC
Environment: FEDORA 20.

Kernel: 3.15.6-200.fc20.x86_64

Driver: NVIDIA kmod-nvidia-304xx-3.15.4-200.fc20.x86_64-304.123-1.fc20.x86_64

From CLI, totem starts and freeze; no windows, nothing at all, just blinking cursor. Totem CPU usage goes to 99%.

This bug affected Totem in FEDORA 20 since first upgrading from FEDORA 19.

GStreamer packages installed:

gstreamer-ffmpeg-0.10.13-12.fc20.x86_64
gstreamer-plugins-bad-free-0.10.23-20.fc20.i686
gstreamer-plugins-bad-0.10.23-5.fc20.x86_64
gstreamer-plugins-ugly-0.10.19-14.fc20.x86_64
gstreamer-plugins-good-0.10.31-10.fc20.x86_64
gstreamer1-plugins-bad-free-1.2.4-1.fc20.x86_64
gstreamer1-plugins-good-1.2.4-2.fc20.x86_64
gstreamer-python-0.10.22-5.fc20.x86_64
gstreamer-plugins-espeak-0.4.0-2.fc19.x86_64
gstreamer-plugins-base-0.10.36-6.fc20.i686
gstreamer1-1.2.4-1.fc20.x86_64
gstreamer-tools-0.10.36-6.fc20.x86_64
gstreamer-plugins-bad-free-0.10.23-20.fc20.x86_64
gstreamer-plugins-base-0.10.36-6.fc20.x86_64
gstreamer1-plugins-bad-freeworld-1.2.4-1.fc20.x86_64
gstreamer-0.10.36-6.fc20.x86_64
PackageKit-gstreamer-plugin-0.8.17-1.fc20.x86_64
gstreamer1-plugins-base-1.2.4-1.fc20.x86_64
gstreamer1-libav-1.2.4-1.fc20.x86_64
gstreamer-0.10.36-6.fc20.i686
gstreamer1-plugins-ugly-1.2.4-1.fc20.x86_64
gstreamer-plugin-crystalhd-3.10.0-6.fc20.x86_64
Comment 2 Giulio A. 2014-08-01 07:27:39 UTC
(In reply to comment #1)
> See https://wiki.gnome.org/Apps/Videos/BugReporting , plus
> https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for
> running it under gdb.

Output of

gst-launch-0.10 playbin2 uri=file://path/of/myvideofile

is correct. Video and audio are correctly played.

Output of totem stack trace:

Thread 1 (Thread 0x7ffff73b8a40 (LWP 3548))

  • #0 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #1 tls_get_addr_tail
    from /lib64/ld-linux-x86-64.so.2
  • #2 getprocattrcon_raw
    from /lib64/libselinux.so.1
  • #3 is_selinux_enabled
    from /lib64/libselinux.so.1
  • #4 ??
    from /usr/lib64/nvidia-304xx/libGL.so.1
  • #5 ??
    from /usr/lib64/nvidia-304xx/libGL.so.1
  • #6 call_init.part
    from /lib64/ld-linux-x86-64.so.2
  • #7 _dl_init_internal
    from /lib64/ld-linux-x86-64.so.2
  • #8 _dl_start_user
    from /lib64/ld-linux-x86-64.so.2
  • #9 ??
  • #10 ??
  • #11 ??

Comment 3 Bastien Nocera 2014-08-08 17:57:53 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > See https://wiki.gnome.org/Apps/Videos/BugReporting , plus
> > https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for
> > running it under gdb.
> 
> Output of
> 
> gst-launch-0.10 playbin2 uri=file://path/of/myvideofile

The wiki page is outdated, you should try to run:
gst-launch-1.0 playbin uri=file:///path/to/myfile.avi video-sink=cluttersink

> is correct. Video and audio are correctly played.

Do any other clutter applications crash, such as cheese?
Comment 4 Giulio A. 2014-08-13 16:04:01 UTC
Output of

gst-launch-1.0 playbin uri=file:///path/to/myfile.avi video-sink=cluttersink

is correct. Video and audio are correctly played.

Cheese app has the same behaviour of totem. From CLI, it starts, and then freeze; no windows, nothing at all, just blinking cursor. CPU usage goes to 99%, exactly like Totem app.
Comment 5 Bastien Nocera 2014-08-17 22:38:15 UTC
The backtrace is unfortunately useless, because there's only one thread in the backtrace (use "threads apply all bt" to get them all) and there's no debug information either.
Comment 6 Giulio A. 2014-08-24 21:52:50 UTC
The stack trace reported in comment #2 _is_ the output of command "thread apply all bt" into GDB environment.
Comment 7 André Klapper 2014-08-24 22:04:12 UTC
Weird. In any case, the stacktrace in comment 2 is missing debug symbols (plus does not show anything from Totem) - might require to install some additional debug packages.
And just to clarify and make sure we're following the same steps:
* gdb totem
* run
*    (make it crash)
* thread apply all bt
*    (copy output into bug report)
* quit
Comment 8 josef.hruska 2014-10-14 18:44:09 UTC
I'd like to confirm the bug.

kernel: 3.16.4-200.fc20.x86_64
driver: kmod-nvidia-304xx-3.16.4-200.fc20.x86_64-304.123-1.fc20.13.x86_64


My stacktrace:

Thread 1 (Thread 0x7ffff7fb0a40 (LWP 3521))

  • #0 __pthread_mutex_unlock_usercnt
    at pthread_mutex_unlock.c line 57
  • #1 __GI___pthread_mutex_unlock
    at pthread_mutex_unlock.c line 310
  • #2 tls_get_addr_tail
    at dl-tls.c line 730
  • #3 getprocattrcon_raw
    from /lib64/libselinux.so.1
  • #4 is_selinux_enabled
    from /lib64/libselinux.so.1
  • #5 ??
    from /usr/lib64/nvidia-304xx/libGL.so.1
  • #6 ??
    from /usr/lib64/nvidia-304xx/libGL.so.1
  • #7 call_init
    at dl-init.c line 67
  • #8 call_init
    at dl-init.c line 34
  • #9 _dl_init
    at dl-init.c line 130
  • #10 _dl_start_user
    from /lib64/ld-linux-x86-64.so.2
  • #11 ??
  • #12 ??
  • #13 ??


Hope this will help and thank you for looking into.
Comment 9 Bastien Nocera 2014-10-14 18:59:46 UTC
This is a bug in the NVidia libGL implementation, most likely. Please report this to NVidia.