Bug 1021234
Summary: | cheese don't run | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Łukasz Posadowski <mail> |
Component: | cheese | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | amigadave, fab128, hdegoede, mclasen, pierre.juhen, pprzemal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-09-10 17:32:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Łukasz Posadowski
2013-10-20 16:36:44 UTC
Totem (movie player) doesn't working, too. And also hangs on totem --version What version of taglib do you have installed? (In reply to Przemysław Palacz from comment #2) > What version of taglib do you have installed? # rpm -q taglib taglib-1.9.1-1.fc20.i686 I checked some things. As silly as it may sound it's Nvidia drivers fault. But cheese and totem run smoothly with nvidia drivers on Fedora 19. I tried to build modules using akmodsbuild from rpmfusion and rebuilding while nvidia-kmod srpm from them and it did nothing. I would understand window to crash, or buggy blue background in a movie, but "totem/cheese --version"? It should just send some test to stdout, what a display driver could possibly break? (In reply to Łukasz Posadowski from comment #3) while -> whole test -> text sorry for the typos Well, it works now. I don't know why. Thanks. Cheese loops endlessly in init phase. It seems to deadlock itself; hereafter is a gdb trace : #0 0x00000031d8c0b1fe in pthread_mutex_unlock () from /lib64/libpthread.so.0 #1 0x00000031d7801099 in tls_get_addr_tail () from /lib64/ld-linux-x86-64.so.2 #2 0x000000320fa10d0e in getprocattrcon_raw () from /lib64/libselinux.so.1 #3 0x000000320fa0aa6e in is_selinux_enabled () from /lib64/libselinux.so.1 #4 0x0000003fafca5da6 in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #5 0x0000003fafc8505b in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #6 0x00000031d780f2dd in call_init.part.0 () from /lib64/ld-linux-x86-64.so.2 #7 0x00000031d780f403 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2 #8 0x00000031d780122a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #9 0x0000000000000001 in ?? () #10 0x00007fffffffe0ce in ?? () #11 0x0000000000000000 in ?? () (gdb) continue Continuing. ^C Program received signal SIGINT, Interrupt. 0x00000031d8c09ff3 in pthread_mutex_lock () from /lib64/libpthread.so.0 (gdb) bt #0 0x00000031d8c09ff3 in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x00000031d7801069 in tls_get_addr_tail () from /lib64/ld-linux-x86-64.so.2 #2 0x000000320fa10d0e in getprocattrcon_raw () from /lib64/libselinux.so.1 #3 0x000000320fa0aa6e in is_selinux_enabled () from /lib64/libselinux.so.1 #4 0x0000003fafca5da6 in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #5 0x0000003fafc8505b in ?? () from /usr/lib64/nvidia-304xx/libGL.so.1 #6 0x00000031d780f2dd in call_init.part.0 () from /lib64/ld-linux-x86-64.so.2 #7 0x00000031d780f403 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2 #8 0x00000031d780122a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #9 0x0000000000000001 in ?? () #10 0x00007fffffffe0ce in ?? () #11 0x0000000000000000 in ?? () (gdb) cheese stays in pthread mutex lock / unlock of the nvidia driver. Tested today on Fedora 20 with kernel 3.12.6-300.fc20.x86_64. Thank you, Hello I'm experiencing extacly the same problem on fedora 20/mate with nvidia drivers. Did you found any workaround ? Thanks. If this problem affects both Cheese and Totem, it is probably due to an interaction between the proprietary nVidia driver and Clutter, which is used by both. If you can debug this further, it is probably worth filing a bug with nVidia with the details. |