[Desktop-packages] [Bug 1438587] [NEW] connect button is grey when connecting to Ad-hoc SSID
Public bug reported: First, I created an adhoc network through nm-applet->create new wifi network. Network Name: 111 wi-fi security: WEP 128-bit Passphrase key: 222 Then click create button and wait for its ready. using another machine to connect to this "111", enter password 222 and you can find that the connect button is grey, you can not click it. ** Affects: network-manager Importance: Undecided Status: New ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/trusty Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1438587 Title: connect button is grey when connecting to Ad-hoc SSID Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in network-manager package in Ubuntu: New Bug description: First, I created an adhoc network through nm-applet->create new wifi network. Network Name: 111 wi-fi security: WEP 128-bit Passphrase key: 222 Then click create button and wait for its ready. using another machine to connect to this "111", enter password 222 and you can find that the connect button is grey, you can not click it. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1438587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1418400] Re: 'Failed to add/activate connection' error pops up when user try to connect guest wifi in login interface.
** Also affects: network-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1418400 Title: 'Failed to add/activate connection' error pops up when user try to connect guest wifi in login interface. Status in NetworkManager: New Status in network-manager package in Ubuntu: New Bug description: Steps: 1. Install stock ubuntu image 2. Do not connect wifi on OOBE stage 3. Log in 'Guest' session 4. Connect a available wifi 5. Log out 6. In login interface, select the user whom configured on OOBE stage 7. Try to connect previous wifi which 'Guest' connected in login interface 8. Verify the result Actual result: 'Failed to add/activate connection' error pops up Expected result: User could connect the wifi successfully without error message To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1418400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407865] Re: "Super+Alt+S" did not function at the login screen
Installed a fresh trusty and upgraded (w/o trusty-proposed), super+alt+s can not open screen reader during login screen. After enabling proposed and install unity-greeter from trusty-proposed, super+alt+s can open screen reader during login screen. Add tag "verification-done" ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1407865 Title: "Super+Alt+S" did not function at the login screen Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: New Status in unity-greeter package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Fix Committed Status in unity-greeter source package in Vivid: Fix Released Bug description: [Impact] Lenovo customer require to fix it. From users experience this function is missing. Some accessibility features of the Ubuntu operating system did not function. The hotkey to toggle the Orca screen reader on and off (super+alt+S) did not function at the Login screen. [Test Case] 1. Boot into the system. 2. Go the login screen. 3. Press "super+alt+s" to enable the orca screen reader. 4. Observe the orca screen reader is enable or not. Expected result: The screen reader should be enabled. Actual result: It doesn't work. [Regression Potential] N/A [Other Info] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1407865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407867] Re: There are some incorrect button reminder of Software center when using orca screen reader.
** Also affects: software-center (Ubuntu) Importance: Undecided Status: New ** Also affects: software-center Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1407867 Title: There are some incorrect button reminder of Software center when using orca screen reader. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Ubuntu Software Center: New Status in orca package in Ubuntu: New Status in software-center package in Ubuntu: New Bug description: Summary: There are some incorrect button reminder of Software center when using orca screen reader. Steps to reproduce: 1. Boot into the system. 2. Login the system and enable the orca screen reader. 3. Start the software center and click "AllSoftware/Installed/History". Expected result:The screen reader should be reminder the words as label. Actual result: Only speak"Page toggle." To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1407867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407865] Re: "Super+Alt+S" did not function at the login screen
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1407865 Title: "Super+Alt+S" did not function at the login screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in lightdm package in Ubuntu: New Status in orca package in Ubuntu: New Bug description: Summary:Some accessibility features of the Ubuntu operating system did not function. The command to toggle the Orca screen reader on and off (super+alt+S) did not function at the Login screen. Steps to reproduce: 1. Boot into the system. 2. Press "super+alt+s" to enable the orca screen reader. Expected result:The screen reader should be enabled. Actual result:It doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1407865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407865] [NEW] "Super+Alt+S" did not function at the login screen
Public bug reported: Summary:Some accessibility features of the Ubuntu operating system did not function. The command to toggle the Orca screen reader on and off (super+alt+S) did not function at the Login screen. Steps to reproduce: 1. Boot into the system. 2. Press "super+alt+s" to enable the orca screen reader. Expected result:The screen reader should be enabled. Actual result:It doesn't work. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Affects: orca (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1407865 Title: "Super+Alt+S" did not function at the login screen Status in OEM Priority Project: New Status in lightdm package in Ubuntu: New Status in orca package in Ubuntu: New Bug description: Summary:Some accessibility features of the Ubuntu operating system did not function. The command to toggle the Orca screen reader on and off (super+alt+S) did not function at the Login screen. Steps to reproduce: 1. Boot into the system. 2. Press "super+alt+s" to enable the orca screen reader. Expected result:The screen reader should be enabled. Actual result:It doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1407865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: [lts] Switch VGA mode will become black screen
Tried with a fresh installation of 12.04.3. The xorg stack is lts- raring. Without 2:2.21.6-0ubuntu4.3~precise1 in precise-proposed, this issue can be reproduced. After installing this package, this issue is fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: [lts] Switch VGA mode will become black screen Status in HWE Next Project: In Progress Status in OEM Priority Project: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel” source package in Precise: New Status in “xserver-xorg-video-intel-lts-quantal” source package in Precise: Fix Committed Status in “xserver-xorg-video-intel-lts-raring” source package in Precise: Fix Committed Status in “xserver-xorg-video-intel” source package in Quantal: Fix Committed Status in “xserver-xorg-video-intel-lts-quantal” source package in Quantal: Invalid Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Status in “xserver-xorg-video-intel-lts-raring” source package in Raring: Invalid Bug description: [Impact] system hang in a common use-case with external monitor [Test case] hit the hotkey combo to switch modes and it'll hang [Regression potential] slim, this has been upstream for some time now -- On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: [lts] Switch VGA mode will become black screen
Tried to install ubuntu 12.10 on that machine but failed. The kernel in the installation iso is 3.5.0-17, there is no i915-hsw module. So I tried to do a fresh installation of 12.04.2. The xorg stack is lts- quantal. Without 2:2.20.9-0ubuntu2.3~precise1 in precise-proposed, this issue can be reproduced. After installing this package, this issue is fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: [lts] Switch VGA mode will become black screen Status in HWE Next Project: In Progress Status in OEM Priority Project: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel” source package in Quantal: Fix Committed Status in “xserver-xorg-video-intel-lts-quantal” source package in Quantal: New Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Status in “xserver-xorg-video-intel-lts-raring” source package in Raring: Fix Committed Bug description: [Impact] system hang in a common use-case with external monitor [Test case] hit the hotkey combo to switch modes and it'll hang [Regression potential] slim, this has been upstream for some time now -- On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: [lts] Switch VGA mode will become black screen
on a fresh installed and updated (without proposed) raring system, this issue happens. And after enabling proposed and upgrade to xserver-xorg- video-intel 2:2.21.6-0ubuntu4.3, this issue is fixed. set tag verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: [lts] Switch VGA mode will become black screen Status in HWE Next Project: In Progress Status in OEM Priority Project: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel” source package in Quantal: In Progress Status in “xserver-xorg-video-intel-lts-quantal” source package in Quantal: New Status in “xserver-xorg-video-intel” source package in Raring: Fix Committed Status in “xserver-xorg-video-intel-lts-raring” source package in Raring: New Bug description: [Impact] system hang in a common use-case with external monitor [Test case] hit the hotkey combo to switch modes and it'll hang [Regression potential] slim, this has been upstream for some time now -- On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: Switch VGA mode will become black screen
@Timo, So if quantal uses uxa, the second one is not necessary with default settings but if users change to sna, the issue will be triggered. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: Switch VGA mode will become black screen Status in HWE Next Project: New Status in OEM Priority Project: New Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Bug description: On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: Switch VGA mode will become black screen
@Timo, IMO, the first patch changes action both for uxa and sna, and the second one chages sna. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: Switch VGA mode will become black screen Status in HWE Next Project: New Status in OEM Priority Project: New Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Bug description: On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202524] Re: Switch VGA mode will become black screen
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1202524 Title: Switch VGA mode will become black screen Status in HWE Next Project: New Status in OEM Priority Project: New Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu: Triaged Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu: Triaged Bug description: On a lenovo notebook running precise with quantal LTS stack has this issue. When connecting through VGA port, laptop monitor and external monitor will enter extend mode. But after pressing FN+F3 to switching mode, both laptop monitor and external monitor will become black screen, and system is hang, you need to force to power off. When connecting external monitor through HDMI, everything is OK. CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 992163] Re: Cheese crashes on 2nd effects page
Hi there, I can not reproduce this problem on my own computer, could you please install those packages and re-generate the Backtrace? gstreamer0.10-plugins-ugly-dbg gstreamer0.10-plugins-bad-dbg gstreamer0.10-plugins-base-dbg gstreamer0.10-plugins-good-dbg Thanks, Yang -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/992163 Title: Cheese crashes on 2nd effects page Status in “cheese” package in Ubuntu: New Bug description: Cheese crashes when one clicks on Effects and then Next Effects. Terminal output: (cheese:31694): 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:31694): 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:31694): 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:31694): 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:31694): 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:31694): 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:31694): Cogl-WARNING **: X Error received while making drawable 0x03E00037 current ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink9: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink8: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink7: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink6: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink5: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink4: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink3: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink2: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink1: Received buffer without a new-segment. Assuming timestamps start from 0. ** (cheese:31694): WARNING **: Internal data flow problem.: gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstCameraBin:camerabin/GstBin:video_filter_bin/ClutterGstVideoSink:cluttergstvideosink18: Received buffer without a new-segment. Assuming timestamps start from 0.
