GNOME Bugzilla – Bug 677849
Error Message: Could not negotiate format
Last modified: 2012-10-17 13:17:32 UTC
I use Citrix Receiver to connect to a remote Desktop. This remote desktop, resp. the application Lync, tries to connect to the Webcam installed in my PC. This apparently fails with the error message: Webcam cant be use. Report the following gstreamer error to the helpdesk Could not negotiate format Check your filtered caps, if any. What to do?
what does: gst-launch v4l2src ! fakesink -v say?
docb@T520:~> /usr/bin/gst-launch v4l2src ! fakesink -v > gst-launch.txt ^C docb@T520:~>
Created attachment 216377 [details] result
Ok, so the webcam works fine in principle. It's probably best to file a bug with the application where you got the error (Lync?) - they might be missing a colorspace converter in the pipeline (ffmpegcolorspace), or perhaps they are setting filtercaps that are not supported by your camera (a GST_DEBUG=v4l2*:5 log would tell them).
Have you ever tried to file a bug with Microsoft (Lync) or Citrix (Receiver)? You hardly can create an account with them without having a support contract. In fact I have posted this to Citrix http://forums.citrix.com/thread.jspa?threadID=307778&tstart=0 , but as mostly with commercial companies, there are only few hopes that this is picked up.....
If you could provide a (gzipped/bzipped) GST_DEBUG=*:5 log and attach it to this bug, we can take look. Usually this kind of error stems from something that needs fixing on the application side though.
Can you explain how I can record the log, or what I have to do to receive it? I'm calling the Citrix-frontend via a webpage, so there is no direct application call from my side. or do I have to start the above gst-launch with --gst-debug-level=5 ?
I don't know, sorry. Despite the (admittedly rather bad) error message, this is most likely a bug in the application and needs to be debugged in the application. I don't know what the setup is here, so I don't know how or if you can get a debug log, but without one there's not much we can do about this.
Sorry, no idea what to do about this, or even if there's anything to do on our side at all. Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!