Created attachment 638900 [details] dmesg -Description of problem: Starting first time cheese 3.6.1, watch black screen. -Version-Release number of selected component (if applicable): cheese-3.6.1-1.fc18.x86_64 -How reproducible: Always first time starting cheese -Steps to Reproduce: 1. Start first time cheese 2. Watch black screen 3. -Actual results: Black screen -Expected results: Capture cam -Additional info: (cheese:1912): GStreamer-CRITICAL **: gst_query_add_allocation_pool: assertion `size != 0' failed libv4l2: error dequeuing buf: Invalid argument (cheese:1912): cheese-WARNING **: Internal data flow error. When the resolution is switched from the default 640x480 to one of other resolution, it works properly. After that each change of resolution freezes a moment the image.
Created attachment 638901 [details] lspci
Created attachment 638904 [details] Xorg.0.log
Created attachment 638905 [details] lsusb -v
Clicking the Video Mode button causes the image to freeze and the program attempts to record a zero byte file when clicking the Record button. I also am experiencing the screen being black when starting cheese. Effects also work less than about 50% of the time. Much of the time I see only white text with no effects. When the picture does work in Picture Mode the video is very slow and choppy. I experienced none of these problems with either 3.5.5-1 or 3.5.5-2. Both of these previous versions worked flawlessly so whatever happened to cause these problems happened after 3.5.5-2. I'd roll back to the previous working release and keep those for now but the current version of User Accounts does not work properly or often does not even load when the flawlessly-working older versions of cheese and cheese-libs are installed. I rolled back to the previous versions of cheese and cheese-libs and both 3.5.5-1 and 3.5.5-2 work as before--flawlessly. Unfortunately, User Accounts ceases to work due to dependencies on newer versions of cheese-libs. I also tried a hybrid approach by using an older version of cheese and the newer version of cheese-libs symlinked but that worked less than satisfactorily. Perhaps there is a code regression somewhere in the newer releases from a missed patch that was included in 3.5.5-1 and 3.5.5-2? $ rpm -qa cheese cheese-libs gnome-shell cheese-3.6.2-1.fc18.x86_64 cheese-libs-3.6.2-1.fc18.x86_64 gnome-shell-3.6.2-5.fc18.x86_64 I also see the following error when run in Terminal, on clicking VIdeo Mode button: $ cheese (cheese:12031): cheese-WARNING **: Internal data flow error.
Created attachment 662583 [details] lsusb output Here is lsusb output in the text file.
Camorama works fine with the same webcam.
guvcview also works fine with the same webcam.
Created attachment 671226 [details] Screenshot of latest cheese behavior I just had my copy of cheese do something really strange. It loaded with an effect running. I cannot turn it off or choose no effects like I used to be able to do. It has difficulty deciding which video source to use, whether /dev/video0 or /dev/video1. I choose the webcam at /dev/video0, whereas it was set at /dev/video1, which is my Hauppauge video capture card. I try to load effects to choose 'No Effects' and the effects take a few minutes to load. The effects then display /dev/video1 (Hauppauge HVR-1600) instead of /dev/video0 (Logitech C910 HD webcam). The webcam is still active as the indicator lights are still lit. I try to open preferences and it comes up with no features but is blank. At about this time the hard drive light is lit up solidly. After a few minutes of this my entire screen went black and the DE hard-locked. I could not even reach another tty. I had to press the power button and force the computer to power off just to reboot. I rebuilt for F18 and installed version 3.7.3-1, as well, and it is not much better or different from the situation I am now experiencing. 3.5.5-2 was the last working version of cheese for me. That version worked flawlessly. No version since has worked. Unfortunately, I cannot downgrade to version 3.5.5-2 because gnome-control-center user-accounts ceases to function due to dependencies on cheese-libs newer than 3.5.5-2. I've already tried that three times using different methodologies. Whatever the problems, the varying kinds of crashes and program failures have been 100% repeatable since 3.5.91-1. The problems lie within changes made after 3.5.5-2, whereas 3.5.5-2 ran flawlessly. I could take photos, use effects, and record videos in that version. Now, I get zero byte movie files, no pictures, and errors regarding data flow in the terminal window. I also saw the following in terminal window: radeon: The kernel rejected CS, see dmesg for more information. I go to dmesg and see the following: [ 1346.558890] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! I am running only FOSS drivers. I have never seen these errors before. All other webcam softwares I have installed work. Only cheese doesn't.
Saw this in terminal following previous errors above: libv4l2: error set_fmt gave us a different result then try_fmt! (cheese:3245): cheese-WARNING **: Device '/dev/video0' cannot capture in the specified format (cheese:3245): cheese-WARNING **: Internal data flow error.
Switching back and forth between devices and back to the camera produced the following after webcam at first began sending data to cheese and froze: (cheese:3245): cheese-WARNING **: Resource busy or not available.: gstbasecamerasrc.c(195): gst_base_camera_src_start_capture (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source
I think I have narrowed down the location of the problem. I now think that it is a problem in cheese-libs and cheese-libs-devel rather than in the cheese application itself. I copied the libraries from the latest cheese version for F18 to a backup folder, forced a downgrade to the last working cheese and cheese-libs for me, 3.5.5-2.fc18, and then recopied the newer libraries to cover dependencies for user-accounts so that I can use both cheese and user-accounts (which has a dependency on the newer version of cheese-libs). User-accounts has the same slow action with the webcam data stream that the newer version of cheese did whereas cheese is now working again in the lesser version with its accompanying cheese-libs. So, it would seem to me that something in cheese-libs following version 3.5.5-2 is the culprit in the above problems I and others have been experiencing.
cheese-3.8.2-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/cheese-3.8.2-3.fc19
Hi arithmos and Charles, Thanks for reporting this. Note I'm not sure the issues you are both seeing are the same issue. I've recently been giving cheese some much needed loving, testing it with various cams and video devices, etc. As a result I've written a number of patches which should make cheese behave and work much better with high resolution cameras such as the Logitech c910 Charles has. Can you please give the new cheese-3.8.2-3.fc19 build a try and see if that works better with your cameras? I esp. expect it to help Charles case, arithmos' case may need some more debugging first. Unfortunately my recent cheese work is non trivial to backport to F-18 so I'm keeping it on F-19 for now, so yes if you want to test this you will need to upgrade to F-19 (or use a F-19 livecd). F-19 is nearing its final release and as such is quite stable and could really use some testing, so besides testing cheese, you would also be helping Fedora by testing F-19 and providing valuable feedback before it goes gold! Thanks & Regards, Hans
I've just installed the new cheese packages and cheese now is working like it did in 3.5.5-2. The video is smoother and the application no longer crashes the way it did in version after 3.5.5-2. I've got smooth video in the user-accounts control panel again, too. The only thing that does not work now is the effects. No effects are working. I am not sure why at the moment. Thanks for your work on this. Headed over to give positive karma right now...
Hi, (In reply to D. Charles Pyle from comment #14) > I've just installed the new cheese packages and cheese now is working like > it did in 3.5.5-2. The video is smoother and the application no longer > crashes the way it did in version after 3.5.5-2. I've got smooth video in > the user-accounts control panel again, too. > > The only thing that does not work now is the effects. No effects are > working. I am not sure why at the moment. Thanks for your work on this. > Headed over to give positive karma right now... Thanks for the quick test, and good to hear that your cam is working again. Not so good to hear that effects are not working though :| Some questions to help debug this: 1) If you start cheese from a terminal, do you get any error messages to the terminal ? 2) In what way are the effects not working ? Do you get a screen with 9 effect names, but no previews, or ? 3) If you get effect names but no preview, what happens if you click on an effect name ? Thanks & Regards, Hans
I ran cheese and tried to run choose effects. They all show up in the window but I cannot click on them. When I do the video and picture always defaults back to no effect. I also noticed the following in the terminal window during that time when I checked video playback: (totem:26842): Gtk-WARNING **: GtkMenuBar 0xebb690 is mapped but visible=1 child_visible=1 parent GtkApplicationWindow 0xaa22b0 mapped=0 (cheese:26783): Cogl-WARNING **: Over 50 separate fragment shaders have been generated which is very unusual, so something is probably wrong! Let me know what else you might need for troubleshooting purposes.
1) If you start cheese from a terminal, do you get any error messages to the terminal ? See comment 16. 2) In what way are the effects not working ? Do you get a screen with 9 effect names, but no previews, or ? I get previews of 9 effects. 3) If you get effect names but no preview, what happens if you click on an effect name ? Clicking on them has no effect. No effect starts or is applied to the image. Clicking on the button to return to the image leaves it with no effect applied even after clicking each effect preview or even multiple ones multiple times. I do not know whether or not this is related but I noticed also that when I run gstreamer-properties, I see the following: $ gstreamer-properties (gstreamer-properties:27026): Gtk-WARNING **: Unknown property: GtkDialog.has-separator (gstreamer-properties:27026): Gtk-WARNING **: Unknown property: GtkDialog.has-separator gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosink' gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'v4lsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosrc' Video is very choppy in that application. I am sure that is upstream but what about the missing plugins? Might that have anything to do with the cheese effects problem I am experiencing now?
Created attachment 762065 [details] Screenshot of current cheese version running Here is a screenshot showing that effects show up in previews. However, I still cannot get them to take effect when clicking on them. I have tried all sorts of clicks, left-clicks, right-clicks, middle-clicks, etc. Nothing works at the moment.
Hi, (In reply to D. Charles Pyle from comment #16) >? I also noticed the following in the terminal > window during that time when I checked video playback: > > (totem:26842): Gtk-WARNING **: GtkMenuBar 0xebb690 is mapped but visible=1 > child_visible=1 parent GtkApplicationWindow 0xaa22b0 mapped=0 That is from totem-video-thumbnailer which gets called to make thumbnails to show in the bottom / side bar with previous pictures / recordings. > (cheese:26783): Cogl-WARNING **: Over 50 separate fragment shaders have been > generated which is very unusual, so something is probably wrong! This is a more or less "normal" message with cheese atm I'm afraid. (In reply to D. Charles Pyle from comment #17) > 1) If you start cheese from a terminal, do you get any error messages to the > terminal ? > > See comment 16. > > 2) In what way are the effects not working ? Do you get a screen with 9 > effect names, but no previews, or ? > > I get previews of 9 effects. Are the previews animated, or just a single still picture? If they are animated (they should be), do they show a smooth framerate ? Can you try "slow" clicking so click on a preview hold the button for 1 second, and then release? > > 3) If you get effect names but no preview, what happens if you click on an > effect name ? > > Clicking on them has no effect. No effect starts or is applied to the > image. Clicking on the button to return to the image leaves it with no > effect applied even after clicking each effect preview or even multiple ones > multiple times. > > I do not know whether or not this is related but I noticed also that when I > run gstreamer-properties, I see the following: > > $ gstreamer-properties > (gstreamer-properties:27026): Gtk-WARNING **: Unknown property: > GtkDialog.has-separator > > (gstreamer-properties:27026): Gtk-WARNING **: Unknown property: > GtkDialog.has-separator > gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' > gstreamer-properties-Message: Skipping unavailable plugin 'esdsink' > gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosink' > gstreamer-properties-Message: Skipping unavailable plugin 'glimagesink' > gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' > gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' > gstreamer-properties-Message: Skipping unavailable plugin 'v4lsrc' > gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' > gstreamer-properties-Message: Skipping unavailable plugin 'sunaudiosrc' That is unrelated. > > Video is very choppy in that application. I am sure that is upstream but > what about the missing plugins? Might that have anything to do with the > cheese effects problem I am experiencing now? It is likely defaulting to the highest resolution your camera can do, which is quite high (and thus has a low framerate because of usb bandwidth limitations). Also the high resolution may make things choppy simply because your CPU cannot keep up. What kind of CPU do you have? The new cheese has code to pick a better default resolution when first started, avoiding resolutions with framerates below 15 fps. But since you've started cheese before, it will have recorded its old default choice, which is likely sub-optimal. Can you go to your preferences menu (click on the cheese logo in the gnome top-panel to get there under gnome-3.x) and under the webcam tab: 1) Write down which resolution is currently selected for photo and video 2) Select something like 1024x768, or a similar not too high resolution and try the effects again Thanks, Hans
Video is smooth in the effects previews and all are animated. My CPU is Intel Pentium Dual Core, 3.2 GHz. 4 Gbytes DDR3. But clicking of any kind did not work, including slow-clocking. Now comes the weird part. I have been using the Cinnamon DE all during this past couple weeks, trying to assist where I can in finding bugs and workarounds. The effects do not work there as no click registers in cheese to change the effects. I can go to the menu and change settings. Clicking works fine there. But, no effects. I just logged into Gnome Shell 3.8.3-2. I launched cheese and I was able to click on the effects and they all work fine there. Pretty bizarre, if you ask me. I have no idea why clicking registers in Gnome Shell but not in Cinnamon. It is only cheese that has this issue. Not sure why. But, cheese works flawlessly again in Gnome Shell 3.8.3-2.
It is just these recent versions that exhibit the problem with mouse clicks in the effects previews in Cinnamon. 3.5.5-2 worked fine in it after a forced downgrade to that version. There was an issue, however, where just clicking the effects preview of choice did not return me to the main window. I had to click the effects button to dismiss the effects previews. But, whatever effect I selected was applied. Not the case with the current version, for some odd reason. I am at 3.8.2-3 now as I write this. It still works perfectly, however on Gnome 3.8 Shell.
cheese-3.8.2-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to D. Charles Pyle from comment #20) > Now comes the weird part. I have been using the Cinnamon DE all during this > past couple weeks, trying to assist where I can in finding bugs and > workarounds. The effects do not work there as no click registers in cheese > to change the effects. I can go to the menu and change settings. Clicking > works fine there. But, no effects. > > I just logged into Gnome Shell 3.8.3-2. I launched cheese and I was able to > click on the effects and they all work fine there. That is good to hear! > Pretty bizarre, if you > ask me. I have no idea why clicking registers in Gnome Shell but not in > Cinnamon. It is only cheese that has this issue. Not sure why. But, > cheese works flawlessly again in Gnome Shell 3.8.3-2. That is weird, very weird given that Cinnamon basically is Gnome Shell with some tweaks, maybe a lot of tweaks but the underlying technology, window-manager, etc. All is the same. Can you ask one of the Cinnamon devs to take a look at this ?
I fired off an email yesterday.
I tested the new cheese packages in GNOME, GNOME Classic, KDE, LXDE, Openbox, Cinnamon, and Cinnamon (software rendering). It works in all except Cinnamon and Cinnamon (software rendering). In both of the latter, the mouse click problem exists. No problems to report in the others as the software works as expected in the other mentioned here.
Hi, (In reply to D. Charles Pyle from comment #25) > I tested the new cheese packages in GNOME, GNOME Classic, KDE, LXDE, > Openbox, Cinnamon, and Cinnamon (software rendering). It works in all > except Cinnamon and Cinnamon (software rendering). In both of the latter, > the mouse click problem exists. No problems to report in the others as the > software works as expected in the other mentioned here. Thanks for all the testing! And good to hear this only happens in Cinnamon. Regards, Hans
Would this cause(In reply to Hans de Goede from comment #23) > > Pretty bizarre, if you > > ask me. I have no idea why clicking registers in Gnome Shell but not in > > Cinnamon. It is only cheese that has this issue. Not sure why. But, > > cheese works flawlessly again in Gnome Shell 3.8.3-2. > > That is weird, very weird given that Cinnamon basically is Gnome Shell with > some tweaks, maybe a lot of tweaks but the underlying technology, > window-manager, etc. All is the same. > > Can you ask one of the Cinnamon devs to take a look at this ? Would adding CLUTTER_DISABLE_XINPUT=1 to environment on session startup cause this? https://github.com/linuxmint/cinnamon-session/commit/3d56843b82542083a88afb2db0774105084850f3
I am not sure about that being the cause. I poked around in the source code for the version I had installed and could not even find the lines discussed at the link in comment 27. I was trying to rebuild a copy of cinnamon without the environment setting to see if that would make a difference. But found no matching code in what was in the tar file contained within. In any case, the problem remains.
I found the file containing the line, commented out the line, and rebuilt and repackaged cinnamon-session. Following that I installed the rebuilt package without that variable, and began testing Cheese again. The problem remains in spite of the change. I am open to further suggestions.
I tried another test. This time I kept the line of code uncommented but explicitly set it to the equivalent of CLUTTER_DISABLE_XINPUT=0. I then rebuilt and repackaged and re-installed it. I rebooted and then logged in to try and see if there were any differences. It had no effect. The problem remains. My money still is on something involving Muffin and/or Cheese, whether it be a missing/incompatible feature due to forking or code that somehow blocks or does not pass the "mouse up" event to the Cheese window whenever running in Cinnamon.
Someone there over at github suggested that the above is caused by Cheese being dependent on libclutter and libclutter-gtk. Apparently other applications dependent on these also do not work correctly. For some reason Cinnamon does not interact with those libraries.
cinnamon-2.0.14-16.fc19,cinnamon-session-2.0.6-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/cinnamon-2.0.14-16.fc19,cinnamon-session-2.0.6-1.fc19
cinnamon-2.0.14-16.fc20,cinnamon-session-2.0.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/cinnamon-2.0.14-16.fc20,cinnamon-session-2.0.6-1.fc20
cinnamon-2.0.14-16.fc20, cinnamon-session-2.0.6-1.fc20, muffin-2.0.5-5.fc20, cinnamon-settings-daemon-2.0.8-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
cinnamon-2.0.14-16.fc19, cinnamon-session-2.0.6-1.fc19, muffin-2.0.5-5.fc19, cinnamon-settings-daemon-2.0.8-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.