Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30147 - [cheese] 3.4.2 doesn't work
Attached to Project:
Arch Linux
Opened by Giuseppe De Luca (pep1ko) - Tuesday, 05 June 2012, 21:15 GMT
Last edited by Jan de Groot (JGC) - Saturday, 20 October 2012, 09:23 GMT
Opened by Giuseppe De Luca (pep1ko) - Tuesday, 05 June 2012, 21:15 GMT
Last edited by Jan de Groot (JGC) - Saturday, 20 October 2012, 09:23 GMT
|
DetailsDescription:
this is what I get when I execute cheese and it hangs there with 100% cpu Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one widget at a time; it already contains a widget of type GtkLabel Additional info: cheese 3.4.2 Steps to reproduce: Type cheese in terminal |
This task depends upon
I am using NVIDIA driver 295.59.
I tried with nouveau but it's the same.
lenovo laptop, integrated camera
kernel 3.4.2-1-ARCH, cheese 3.4.2 with intel drivers for integrated chipset.
I'm not sure it is an Arch-related problem, since I found a Ubuntu-related report : http://askubuntu.com/questions/118206/cheese-wont-start.
However, I found an exact match to my error message in this bug report, so until I haven't some clues it is an upstream revelant problem, I'll file some things here. Please Jan do not take them personnaly. Not to say I hate the bugzilla tracker and find myself home with flyspray, no.
My current guess that it has to deal with non-complete gnome environments. I run myself a minimalist Arch-Xorg-AwesomeWM box. Just to say.
However, I tried an strace and a --debug-level=4 and did not find any relevant info actually, Do you Jan know any mean to have some more clues about this ?
We need to wait until gnome 3.6?
After running cheese :
[New Thread 0x7fffdb56b700 (LWP 14756)]
[New Thread 0x7fffd8d6a700 (LWP 14757)]
libv4l2: warning v4l2 mmap buffers still mapped on close()
[New Thread 0x7fffd098c700 (LWP 14770)]
[New Thread 0x7fffcbfff700 (LWP 14771)]
[Thread 0x7fffcbfff700 (LWP 14771) exited]
[Thread 0x7fffd098c700 (LWP 14770) exited]
[New Thread 0x7fffd098c700 (LWP 14772)]
[New Thread 0x7fffcbfff700 (LWP 14773)]
** (cheese:14751): WARNING **: Could not get buffers from device '/dev/video0'.
** (cheese:14751): WARNING **: Could not map buffers from device '/dev/video0'
** (cheese:14751): WARNING **: Could not negotiate format
** (cheese:14751): WARNING **: Could not get buffers from device '/dev/video0'.
** (cheese:14751): WARNING **: Could not map buffers from device '/dev/video0'
** (cheese:14751): WARNING **: Could not negotiate format
[Thread 0x7fffd8d6a700 (LWP 14757) exited]
I clicked on video tab, then on record.
Program received signal SIGINT, Interrupt.
0x00007ffff508debd in poll () from /lib/libc.so.6
and bt full :
#0 0x00007ffff508debd in poll () from /lib/libc.so.6
No symbol table info available.
#1 0x00007ffff55b9744 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#2 0x00007ffff55b9864 in g_main_context_iteration ()
from /lib/libglib-2.0.so.0
No symbol table info available.
#3 0x00007ffff5d6dd7c in g_application_run () from /lib/libgio-2.0.so.0
No symbol table info available.
#4 0x0000000000417798 in _vala_main ()
No symbol table info available.
#5 0x00007ffff4fd3725 in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#6 0x000000000040c791 in _start ()
No symbol table info available.
Maybe a debug package could help a little ?
In my case I have a blank window, see my screen attached.
I also joined the backtrace, maybe someone will find something I missed. See the 8.2K version because Flyspray did not let me remove previous version.