Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning
On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam In my case I don't think so- it's built into the frame of my laptop screen. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning
On 03/28/2013 09:55 AM, Jonathan Dowland wrote: On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam In my case I don't think so- it's built into the frame of my laptop screen. How about unloading the kernel module then? I guess it's probably an UVC camera, so modprobe -r uvcvideo should do the trick for most cameras (as most of them are UVC). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On Thu, Mar 28, 2013 at 11:13:34AM +0100, John Paul Adrian Glaubitz wrote: How about unloading the kernel module then? I guess it's probably an UVC camera, so modprobe -r uvcvideo should do the trick for most cameras (as most of them are UVC). Thanks for the tip. It is indeed uvcvideo, and unloading it means cheese draws its UI (No device found). Interesting stuff. I'm going to try splicing some debug statements into the code to see at what point it reaches and whether that helps get any further. FWIW some earlier verison of cheese worked with this webcam on this laptop. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)
I've just noticed that cheese is busy looping and mallocing whilst it's seemingly doing nothing: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 18958 jon 20 0 7513m 6.2g 3236 R 92.1 80.0 20:03.57 cheese -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
Package: cheese Version: 3.4.2-2 Followup-For: Bug #696727 I didn’t use Cheese before, but to test this bug I installed cheese from wheezy on my machine (which is running mostly experimental GNOME), and it segfaults. A full gdb stacktrace is attached. -- Dmitry Shachnev -- System Information: Debian Release: 7.0 APT prefers experimental APT policy: (500, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cheese depends on: ii cheese-common 3.4.2-2 ii gnome-video-effects 0.4.0-1 ii libc6 2.13-38 ii libcanberra-gtk3-00.28-6 ii libcheese-gtk21 3.4.2-2 ii libcheese33.4.2-2 ii libclutter-1.0-0 1.13.10-1 ii libclutter-gtk-1.0-0 1.4.4-2 ii libgdk-pixbuf2.0-02.28.0-1 ii libgee2 0.6.4-2 ii libglib2.0-0 2.36.0-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgstreamer0.10-00.10.36-1.1 ii libgtk-3-03.8.0-1 Versions of packages cheese recommends: ii gnome-icon-theme3.7.91-1 ii gvfs1.12.3-4 ii hicolor-icon-theme 0.12-1 pn nautilus-sendto none ii yelp3.4.2-1+b1 cheese suggests no packages. -- no debconf information (gdb) run Starting program: /usr/bin/cheese [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [New Thread 0xb3923b70 (LWP 20056)] (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): 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 (cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkGrid to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel (cheese:20053): 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 [New Thread 0xb30edb70 (LWP 20057)] Program received signal SIGSEGV, Segmentation fault. 0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, callback=callback@entry=0xb7d4f340 frame_cb, user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0) at ./cogl-onscreen.c:370 370 ./cogl-onscreen.c: No such file or directory. (gdb) bt full #0 0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, callback=callback@entry=0xb7d4f340 frame_cb, user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0) at ./cogl-onscreen.c:370 closure = 0x8566580 #1 0xb7d502f8 in clutter_stage_cogl_realize (stage_window=0x83f1c80) at ./cogl/clutter-stage-cogl.c:163 stage_cogl = 0x83f1c80 backend = optimized out framebuffer = optimized out error = 0x0 #2 0xb7d49c7f in clutter_stage_x11_realize (stage_window=0x83f1c80) at ./x11/clutter-stage-x11.c:609 stage_x11 = 0x83f1c80 stage_cogl = 0x83f1c80 backend = 0x8087800 backend_x11 = 0x8087800 device_manager = optimized out event_flags = optimized out width = 682 height = 450 #3 0xb7dd0573 in _clutter_stage_window_realize (window=0x83f1c80) at ./clutter-stage-window.c:88 No locals. #4 0xb7dc989d in clutter_stage_realize (self=0x84f17f0) at ./clutter-stage.c:761 priv = optimized out is_realized = optimized out #5 0xb755628a in g_cclosure_marshal_VOID__VOIDv (closure=0x84f04e0, return_value=0x0, instance=0x84f17f0, args=0xbfffe72c \241\062C\267\364?T\267@\nW\b\001, marshal_data=0xb7dc9850, n_params=0, param_types=0x0) at /tmp/buildd/glib2.0-2.36.0/./gobject/gmarshal.c:115 cc = 0x84f04e0 data1 = optimized out data2 = 0x84eb4a0 callback = 0xb7dc9850 clutter_stage_realize #6 0xb7552df7 in g_type_class_meta_marshalv (closure=closure@entry=0x84f04e0, return_value=return_value@entry=0x0, instance=instance@entry=0x84f17f0, args=args@entry=0xbfffe72c
Bug#696727: cheese does not start with Gtk-Warning
On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote:
UI (No device found). Interesting stuff. I'm going to try splicing some
debug statements into the code to see at what point it reaches and whether
that helps get any further.
I've poked around a little, attached is a backtrace taken when interrupting the
spinning process. It shows the last routine executed in cheese code as
cheese_camera_play. Poking around in the C,
cheese_camera_play (CheeseCamera *camera)
{
…
gst_element_set_state (priv-camerabin, GST_STATE_PLAYING);
^^
That's as far as cheese gets. So, is this a gstreamer bug? (or
gstreamer0.10-plugins-bad)? Seems it uses 'camerabin', which has been
deprecated in favour of 'camerabin2' in gst 0.10, and dropped by 1.0.
Cheese moved to camerabin2 between 3.5.5 and 3.5.091.
#0 type_check_is_value_type_U (type=optimized out)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4098
#1 g_type_check_value (value=value@entry=0x1dddfb0)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4140
#2 0x77769d9c in gst_value_init_and_copy (dest=0x1e33520,
src=0x1dddfb0) at gstvalue.c:4007
#3 0x7776a03f in copy_garray_of_gstvalue (
src=error reading variable: Unhandled dwarf expression opcode 0xfa,
src=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:230
#4 0x7776a130 in gst_value_copy_list_or_array (src_value=optimized
out,
dest_value=0x7fffd8b0) at gstvalue.c:241
#5 0x7776d35f in gst_value_list_append_value
(value=value@entry=0x7fffd970,
append_value=append_value@entry=0x7fffd8f0) at gstvalue.c:314
#6 0x7776da4b in gst_value_intersect_list (dest=0x7fffd970,
value2=0x1a40460,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2752
#7 0x7776d999 in gst_value_intersect_list (dest=0x7fffd9f0,
value2=0x1a40460,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#8 0x7776d999 in gst_value_intersect_list (dest=0x7fffda70,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#9 0x7776d999 in gst_value_intersect_list (dest=0x7fffdaf0,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#10 0x7776d999 in gst_value_intersect_list (dest=0x7fffdb70,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#11 0x7776d999 in gst_value_intersect_list (dest=0x7fffdbf0,
value2=0x1d84658,
value1=error reading variable: Unhandled dwarf expression opcode 0xfa) at
gstvalue.c:2746
#12 0x77750a73 in gst_structure_intersect_field1 (id=3915,
val1=0x1a3d4a8, data=0x7fffdc60)
at gststructure.c:2981
#13 0x77750fc1 in gst_structure_foreach (structure=0x1a5fb90,
func=0x77750a20 gst_structure_intersect_field1,
user_data=0x7fffdc60) at gststructure.c:1097
#14 0x77753c00 in gst_structure_intersect
(struct1=struct1@entry=0x1a5fb90, struct2=0x1c88330)
at gststructure.c:3030
#15 0x7770f3a4 in gst_caps_intersect_first (caps2=0x19d1e80,
caps1=0x198ce40) at gstcaps.c:1423
#16 gst_caps_intersect_full (caps1=caps1@entry=0x198ce40,
caps2=caps2@entry=0x19d1e80,
mode=mode@entry=GST_CAPS_INTERSECT_FIRST) at gstcaps.c:1454
#17 0x7fffefff4c94 in gst_base_transform_getcaps (pad=0x19c9d90) at
gstbasetransform.c:768
#18 0x7772cf96 in gst_pad_get_caps_unlocked (pad=pad@entry=0x19c9d90)
at gstpad.c:2254
#19 0x777305b5 in gst_pad_get_caps_reffed (pad=pad@entry=0x19c9d90) at
gstpad.c:2338
#20 0x7776148b in gst_element_get_compatible_pad
(element=element@entry=0x1b8e240,
pad=pad@entry=0x19c9d90, caps=caps@entry=0x0) at gstutils.c:1146
#21 0x7776216a in gst_element_link_pads_full (src=src@entry=0x1a16090,
srcpadname=srcpadname@entry=0x0, dest=dest@entry=0x1b8e240,
destpadname=destpadname@entry=0x0,
flags=flags@entry=GST_PAD_LINK_CHECK_CAPS) at gstutils.c:1799
#22 0x7fffe16020ea in gst_camerabin_try_add_element
(bin=bin@entry=0x196e020,
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:99
#23 0x7fffe160228f in gst_camerabin_add_element (bin=bin@entry=0x196e020,
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:56
#24 0x7fffe160247d in gst_camerabin_create_and_add_element
(bin=bin@entry=0x196e020,
elem_name=optimized out, elem_name@entry=0x7fffe16043fd videoscale,
instance_name=instance_name@entry=0x7fffe16043f9 src-videoscale) at
camerabingeneral.c:146
#25 0x7fffe15f67a0 in camerabin_create_src_elements (camera=0x196e020) at
gstcamerabin.c:623
#26 camerabin_create_elements (camera=0x196e020) at gstcamerabin.c:779
#27 gst_camerabin_change_state (element=0x196e020,
Bug#696727: cheese does not start with Gtk-Warning
On 03/28/2013 03:26 PM, Jonathan Dowland wrote:
On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote:
UI (No device found). Interesting stuff. I'm going to try splicing some
debug statements into the code to see at what point it reaches and whether
that helps get any further.
I've poked around a little, attached is a backtrace taken when interrupting
the
spinning process. It shows the last routine executed in cheese code as
cheese_camera_play. Poking around in the C,
cheese_camera_play (CheeseCamera *camera)
{
…
gst_element_set_state (priv-camerabin, GST_STATE_PLAYING);
^^
That's as far as cheese gets. So, is this a gstreamer bug? (or
gstreamer0.10-plugins-bad)? Seems it uses 'camerabin', which has been
deprecated in favour of 'camerabin2' in gst 0.10, and dropped by 1.0.
Cheese moved to camerabin2 between 3.5.5 and 3.5.091.
Most likely not a cheese bug; you can confirm that by trying e.g. empathy, which
will probably fail to use the webcam too. After that I'd try with another tool
that doesn't use gstreamer, then we can pinpoint whether this is a gstreamer bug
or not.
I remember from when I did video integration in empathy that some webcams will
only work once, and after that you have to unload the kernel module and load it
again for them to work. If that was the case here, the problem could be that
cheese is not stopping them properly.
Regards,
Emilio
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
severity 696727 important thanks (Downgrading since no evidence that it fails for the majority) On 28 Mar 2013, at 18:56, Emilio Pozuelo Monfort po...@debian.org wrote: After that I'd try with another tool that doesn't use gstreamer, then we can pinpoint whether this is a gstreamer bug or not. Already done I remember from when I did video integration in empathy that some webcams will only work once, and after that you have to unload the kernel module and load it again for them to work. If that was the case here, the problem could be that cheese is not stopping them properly. Cheese fails on first attempt after module reload without invoking any other webcam software first. Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#696727: cheese does not start with Gtk-Warning
Processing commands for cont...@bugs.debian.org: severity 696727 important Bug #696727 [cheese] cheese does not start with Gtk-Warning Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 696727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#696727: cheese does not start with Gtk-Warning
Processing commands for cont...@bugs.debian.org: severity 696727 grave Bug #696727 [cheese] cheese does not start with Gtk-Warning Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 696727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On 03/27/2013 06:22 PM, Jon Dowland wrote: severity 696727 grave thanks On Wed, Dec 26, 2012 at 03:36:44PM +0100, Giovanni74 wrote: cheese does not start at all. Here is the terminal output: Wow. I've just reproduced this. I'm mildly incredulous. Are we just unlucky? This makes the package entirely unusable for me. Can anyone use it? I'm going to take a chance and assume that my experience is the typical one, and thus the package is unusable or mostly so as it stands. I might try poking around at the source tonight but I know nothing about vala so I don't know if I'll get anywhere. Please get a backtrace with G_DEBUG=fatal-warnings set and libgtk-3-0-dbg libglib2.0-0-dbg installed. You may also need to rebuild cheese with DEB_BUILD_OPTIONS=nostrip if the backtrace isn't very useful. Thanks, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
Am 27.03.2013 18:22, schrieb Jon Dowland: severity 696727 grave thanks On Wed, Dec 26, 2012 at 03:36:44PM +0100, Giovanni74 wrote: cheese does not start at all. Here is the terminal output: Wow. I've just reproduced this. I'm mildly incredulous. Are we just unlucky? This makes the package entirely unusable for me. Can anyone use it? I'm going to take a chance and assume that my experience is the typical one, and thus the package is unusable or mostly so as it stands. Nope, cheese works fine here. I do get those warnings, but afaics they are a red herring. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#696727: cheese does not start with Gtk-Warning
On 03/27/2013 07:38 PM, Michael Biebl wrote: Am 27.03.2013 18:22, schrieb Jon Dowland: severity 696727 grave thanks On Wed, Dec 26, 2012 at 03:36:44PM +0100, Giovanni74 wrote: cheese does not start at all. Here is the terminal output: Wow. I've just reproduced this. I'm mildly incredulous. Are we just unlucky? This makes the package entirely unusable for me. Can anyone use it? I'm going to take a chance and assume that my experience is the typical one, and thus the package is unusable or mostly so as it stands. Nope, cheese works fine here. I do get those warnings, but afaics they are a red herring. Then the backtrace I requested should be without G_DEBUG. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
Am 27.03.2013 19:58, schrieb Emilio Pozuelo Monfort: On 03/27/2013 07:38 PM, Michael Biebl wrote: Am 27.03.2013 18:22, schrieb Jon Dowland: severity 696727 grave thanks On Wed, Dec 26, 2012 at 03:36:44PM +0100, Giovanni74 wrote: cheese does not start at all. Here is the terminal output: Wow. I've just reproduced this. I'm mildly incredulous. Are we just unlucky? This makes the package entirely unusable for me. Can anyone use it? I'm going to take a chance and assume that my experience is the typical one, and thus the package is unusable or mostly so as it stands. Nope, cheese works fine here. I do get those warnings, but afaics they are a red herring. Then the backtrace I requested should be without G_DEBUG. My guess would be that it is cogl/clutter/gl related. Jon, does gnome-shell (or other clutter using applications) work for you? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#696727: cheese does not start with Gtk-Warning
Hi Michael and Emilio, On Wed, Mar 27, 2013 at 08:00:06PM +0100, Michael Biebl wrote: My guess would be that it is cogl/clutter/gl related. Jon, does gnome-shell (or other clutter using applications) work for you? Yep I run GNOME 3 including gnome-shell without problems. I should probably expand on the report a bit: the process does not terminate after printing those errors, it sits there. Therefore, I don't have a core to backtrace by default. You are perhaps correct that those errors are a red herring. Nevertheless I have a bt with G_DEBUG=fatal-warnings, attached in case it's useful. -- Jonathan Dowland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On Wed, Mar 27, 2013 at 07:38:45PM +0100, Michael Biebl wrote: I do get those warnings, but afaics they are a red herring. Indeed, I've fixed the warnings using the tip at https://bugzilla.gnome.org/show_bug.cgi?id=671912 and I still have the same behaviour, process runs, remains running, but nothing is ever drawn to my screen. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)
Just FWIW I've installed camorama which works fine - just to confirm that my webcam is OK. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696727: cheese does not start with Gtk-Warning
On Wed, Mar 27, 2013 at 09:16:17PM +, Jonathan Dowland wrote: You are perhaps correct that those errors are a red herring. Nevertheless I have a bt with G_DEBUG=fatal-warnings, attached in case it's useful. Actually attached. $ gdb ./.libs/cheese GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /home/jon/wd/cheese-3.4.2/.libs/cheese...done. (gdb) run Starting program: /home/jon/wd/cheese-3.4.2/.libs/cheese warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe9385700 (LWP 13264)] [New Thread 0x7fffe88ea700 (LWP 13265)] (cheese:13261): Gtk-WARNING **: Attempting to add a widget with type GtkImage to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain one widget at a time; it already contains a widget of type GtkLabel Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x76592ff7 Gtk, log_level=G_LOG_LEVEL_WARNING, format=0x7659eb18 Attempting to add a widget with type %s to a %s, but as a GtkBin subclass a %s can only contain one widget at a time; it already contains a widget of type %s, args1=args1@entry=0x7fffda98) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gmessages.h:101 101 /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gmessages.h: No such file or directory. (gdb) bt #0 g_logv (log_domain=0x76592ff7 Gtk, log_level=G_LOG_LEVEL_WARNING, format=0x7659eb18 Attempting to add a widget with type %s to a %s, but as a GtkBin subclass a %s can only contain one widget at a time; it already contains a widget of type %s, args1=args1@entry=0x7fffda98) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gmessages.h:101 #1 0x755a2622 in g_log (log_domain=log_domain@entry=0x76592ff7 Gtk, log_level=log_level@entry=G_LOG_LEVEL_WARNING, format=format@entry=0x7659eb18 Attempting to add a widget with type %s to a %s, but as a GtkBin subclass a %s can only contain one widget at a time; it already contains a widget of type %s) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gmessages.c:792 #2 0x7633fc98 in gtk_bin_add (container=optimized out, child=0x17c8410) at /tmp/buildd/gtk+3.0-3.4.2/./gtk/gtkbin.c:124 #3 0x7585db54 in g_cclosure_marshal_VOID__OBJECTv (closure=0x64a460, return_value=optimized out, instance=0x17c02a0, args=optimized out, marshal_data=optimized out, n_params=optimized out, param_types=0x64a4d0) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gmarshal.c:1312 #4 0x7585a9a7 in _g_closure_invoke_va (closure=0x64a460, return_value=0x0, instance=0x17c02a0, args=0x7fffdec8, n_params=1, param_types=0x64a4d0) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gclosure.c:840 #5 0x75873006 in g_signal_emit_valist (instance=0x17c02a0, signal_id=optimized out, detail=0, var_args=var_args@entry=0x7fffdec8) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:3211 #6 0x75873852 in g_signal_emit (instance=optimized out, signal_id=optimized out, detail=optimized out) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:3356 #7 0x76346b42 in _gtk_builder_add (builder=0x16350f0, child_info=child_info@entry=0x1775500) at /tmp/buildd/gtk+3.0-3.4.2/./gtk/gtkbuilder.c:765 #8 0x7634b248 in end_element (error=0x7fffe058, user_data=0x174b4a0, element_name=0x17d94e0 child, context=optimized out) at /tmp/buildd/gtk+3.0-3.4.2/./gtk/gtkbuilderparser.c:1042 #9 end_element (context=optimized out, element_name=optimized out, user_data=0x174b4a0, error=0x7fffe058) at /tmp/buildd/gtk+3.0-3.4.2/./gtk/gtkbuilderparser.c:927 #10 0x7559f498 in g_markup_parse_context_parse (context=0x17bdd40, text=text@entry=0x17c3f90 ?xml version=\1.0\?\ninterface\n requires lib=\gtk+\ version=\2.16\/\n object class=\GtkGrid\ id=\mainbox_normal\\nproperty name=\orientation\vertical/property\nproperty name=\events..., text_len=optimized out, text_len@entry=13557, error=error@entry=0x7fffe118) at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gmarkup.c:1559 #11 0x7634b677 in _gtk_builder_parser_parse_buffer (builder=builder@entry=0x16350f0, filename=filename@entry=0x1647060 /usr/share/cheese/cheese-main-window.ui, buffer=0x17c3f90 ?xml
Bug#696727: cheese does not start with Gtk-Warning
Hi, could anyone who is seeing the issue with Cheese freezing try to disconnect their webcam? This might be an issue with the webcam failing to initialize which probably depends on the model of webcam being used. I cannot reproduce the problem either, but I also currently have no webcam attached to this computer. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
